pdf-aviat-pv-user-manual compress

PROVISION ® USER MANUAL Version 7.1.2 614-330055-001 ProVision Copyright and Terms of Use December 2015 This documentation incorporates features and functions provided with ProVision, version 7.1.2 Copyright Cop yright © 2015 by A viat Network Networks, s, 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 techpubs@aviatnet.com. Warranty Aviat Networks makes no representation or warranties with respect to the contents hereof and specifically disclaims any implied warranties or merchantability or fitness for any particular purpose. Further, Aviat 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 Recommendations The following safety recommendations must be considered to avoid injuries to persons and/or damage to the equipment: 1. Installation and Servic e Personnel: Installation and service must be carried out by authorized personnel who have the technical training and experience necessary to be aware of any hazardous operations during installation and service, and of measures to avoid any danger to themselves, to any other personnel, and to the equipment. 2. Access to the Equipment: Access to the equipment in use must be restricted to service personnel only. 3. Safety Norm Norms: s: Recommended safety norms are detailed in the Health and Safety sections of this manual. Local safety regulations must be used if mandatory. Safety instructions in this document should be used in addition to the local safety regulations. In the case of conflict between safety instructions stated in this manual and those indicated in local regulations, mandatory local norms will prevail. Should local regulations not be mandatory, then the safety norms in Volume 1 will prevail. 4. Service Personnel Skill: Service personnel must have received adequate technical training on telecommunications and in particular on the equipment this manual refers to. Trademarks All trademarks are the property of their respective owners. 614-330055-001 DECEMBER 2015 I PROVISION USER MANUAL II AVIAT NETWORKS PROVISION USER MANUAL Aviat Networks Technical & Sales Support Service and Technical Support: For customer service ser vice and technical technical support, support, contact one of the the regional regional Techni Technical cal Help Desks listed below. below. Americas Ameri cas Technica Technicall Help Desk EMEA Techni Technical cal Help Desk Asia Pacific Technic Technical al Help Desk Aviat Network Networks, s, Inc. Aviat Network Networkss Aviat Networks San Antonio, TX Blantyre, Glasgow G72 0FB Clark Freeport Zone U. S. A. United Kingdom Philippines Phil ippines 2023 Phone: +1 210 526 6345 Phone: +1 210 526 6345 Phone: +1 210 526 6345 Toll Toll Free (USA):1-800-227-8332 Fax: +44 16 9871 7204 (English) Fax:+1 210-526-6315 Fax: +33 1 5552 8012 (French) Email: Email: Email: CustomerCare.Asia@aviatnet.com CustomeCare.Americas@aviatnet.com CustomerCare.EMEA@aviatnet.com Fax: +63 45 599 5196 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 cal calll our Global S Support upport Hotline: •You will be greeted by an automated response that will ask you for your PIN#. Request a PIN# here on the Aviat Ne Network tworkss web site. •As soon as you enter your PIN#, you will be transferred to our Global Technical Helpdesk that will assist you with your technical issue. •If you do not have a PIN# your call will be answered by our Support Assurance Desk. Your call will be supported and prioritized accordingly. http://www.aviatnetworks.com/services/customer-support/technical-assistp://www.aviatnetworks.com/services/customer-support/technical-assistSee our web site at: htt ance/ Sales and Sales Support: For sales information, information, contact one of the th e Aviat Ne Network tworkss headquar headquarter ters, s, or find y our regional sales office at http://www.aviatnetworks.com/. http://www.aviatnetworks.com/. 614 330055 001 DECEMBER 2015 III PROVISION USER MANUAL Corporate Headquarters International Intern ational Headquarters California, USA Singapore Aviat Network Networks, s, Inc. Aviat Networks (S) Pte. Ltd. 5200 Great American Parkway 17, Changi Business Park Central 1 Santa Clara, California 95054 Honeywell Building, #04-01 U. S. A. Singapore 486073 Phone: + 1 408 567 7000 Phone: +65 +6 5 6496 0900 Fax: + 1 408 567 7001 Fax: + 656496 0999 Toll Free for Sales Inquiries: Sales Inqui Inquiries: ries: + 1 888-478-9669 +1-321-674-4252 IV AVIAT NETWORKS PROVISION USER MANUAL User Manual Table of Contents ProVision Copyright and Terms of Use Aviat Networks Technic al & Sales Support User Manual Table of Contents i iii v CHAPTER 1. WELCOME TO PRO VISION 1 The Goals of Pr oVision How ProVision Works Getting the Most Value fr om ProVision What You Need To Know To Use ProVision Doc umentation Or ganization Documentat Documen tation ion Conven Conventtions and Terminology Additional Addit ional Documentation 2 3 4 6 7 9 10 CHAPTER 2. DEVICE SUP UPPORT PORT IN P RO VISION 11 Li List st of Devi Devic es Supported in ProVision Eclipse Device Support Suppor t CTR Device Support CTR 83 8300 and ProVision CTR CTR 8440 and ProVision CTR 8540 and ProVision CTR CTR 8611 and ProVision ProVision WTM 3100 Device Suppo Support WTM 3200 Devic e Support 12 16 18 18 19 20 21 23 24 WTM 3300 Device Su Support WTM 6000 Device Su Support TRuepoint Ruepoint Device Su Support Constellation Devic e Suppor t Generic Device Device Support Additional Addit ional Dev D eviic e Suppor t Ci Cissco Devic e Support DART Devic e Support DXR Devic e Support MegaSta MegaSt ar Devic e Support Symmettricom Devic e Support Symme TNet TN et Device Support XP4 Device Sup Suppor t 25 27 29 31 32 33 33 33 33 34 34 34 34 614-330055-001 DECEMBER 2015 V PROVISION USER MANUAL CHAPTER 3. NAVIGATING PROVISION Starting a User Session Exiting a User Session Changing Your Password 35 35 37 37 Entering Your Contac t Details Viewing Your ProVision Lic ense Details Viewing Cu Customer Support Contac t Details Viewing ProVision’ s Version Number Using the Online Help The ProVision User Inter fac e Customizing the User Interface Menu Bar Main Mai n Tool Tool Bar Right-Click Menus Menus View Tabs: Physi Physic al, Logical, Circuits, VLAN, EOAM Physical Viewer Viewer and Ic ons Logical Tree Viewer 38 39 40 40 41 44 44 45 51 53 55 55 61 Circuits Viewer Tab Map Vi Viewer ewer Physical Map View Flat Map View View Map Ma p Tools Map Bac kgrounds Map Annotations Annotations Detailed Detai led Device Device View Views Submap Subma ps Equipment Views Int Interfa erfacce Views Even Eve nt Browser The Task Man Manager Sc reen 61 63 63 64 64 66 69 71 71 73 78 80 82 Using Searc Using Searc h to Sear ch All ProVision Data Search Searc hing the Tree Viewers Icons Informa Information and Usage Viewiing Radio Ic on Anatomy View Ab Abou outt User De Defined Ic ons Alarm Severity Sever ity Colo Color Coding Device St States Radio Tasks Integratin Inte grating g Windows Applications with ProVision Linkin Link ing g Documents to to Devic es and Maps 83 87 89 89 91 91 92 93 95 97 CHAPTER 4. DEPLOYI EPLOYING NG AND MANAGING DEVICES 101 About Deploying and Managing Devic es The The Process for Deployi Deploying ng and and Managing Devic es Device Deployme Deployment By Type 102 103 104 VI AVIAT NETWORKS PROVISION USER MANUAL Deploying Devic es Adding, Editing, and De Deleting De Devic e Containers Adding a Container User Defined Containers Renaming a Container 106 106 107 108 111 Deleting a Container Standard SNMP Devic e Deployment Ec lipse Devices and Nodes Deployment DXR 200 and DXR SMA Devic e Deployment CAU (Control Alarm Unit) Deployment Cisco Deployment Constellation Devic e Deployment CTR 8300 and 8540 Devic e Deployment Generic Device Deployment Deployment Proxy and and Network Element Deployment Symmetrico Symmetric om TP1x00 Deployment Symmetrico Symmetric om TP5000 Deployment TRuepoin TRuep ointt Device De Deployment 111 112 117 120 122 123 124 125 128 131 135 137 138 TRuepointt 6500 Device Deployment TRuepoin TNet Device Device Deploym Deploymen entt Networrk Auto-Discovery for Devic es Netwo Troubleshooting Devic e Deployment Changi Changing ng a Device’s Device’s Co Container Moving Movin g Contai Containers ners and Devic es in the Map Viewer Renaming Renamin g a Device Deletin Delet ing g a Device Device Managin Manag ing g Devices Managi Man aging ng a Device Verifyi Veri fying ng ProVisi ProVision on is Rec eiving Device Events Unmanagin Unman aging g a Device Vi Viewin ewing g Eclipse Eclipse RAC Low Late Latenc y Links 142 144 148 152 152 153 153 154 156 156 157 158 159 Manually Discovering W Manua WT TM 6000 Configur ation Manually Discovering T TR Ruepoint 65 6500 Configuration Manuallly Discovering DXR 700 Radios Manua Managing Managin g Proxy Confi Configurat guratiion Managi Man aging ng SMA and and DXR DXR Devices Linkin Link ing g Procedures Discoverin Discove ring g and Verifyi Verifying ng Lin Links Creating Creati ng an RF Link from the Tree Viewer Creatin reating g an RF Link from the Find Func tion Creatin reating g an Ecli Eclipse RF Link Creati Crea ting ng an Ethe Ethernet rnet Lin Link Creating Creati ng a Tributary Tributary Lin L ink k Deletin Delet ing g an RF Link 161 162 162 163 165 167 167 169 170 171 173 174 175 Deletin Delet ing g an Ethernet Link Circuit Managem Management 176 177 614-330055-001 DECEMBER 2015 VII PROVISION USER MANUAL About Circ uits and Circ uit Management Collec ting Circ uit Information Viewing and Managing Circuits Circ uits Tab Filter and Selec t Circ uits 177 178 179 179 181 View a Single Circ uit View Intersec ting Cir cuits View Ring Circ uits View Loop Switc h Circ uits Find and Resolve Conflic ting Circuits Event Br owser for a Circ uit Circ uit Provisioning Using Circ uit Provisioning Ci Circuit rcuit Diagnostics Diagnostics Delete a Circ Circ uit Configuring onfiguring and Synchronizing Devic es Clock Synchr Synchro onization View Viewing Viewi ng Config Configu uration for Devic es 182 183 183 184 185 186 186 186 190 190 192 192 194 Configuration Profiles for Bulk Configuration Configura Create and and Execute Execute a New Configuration Pr ofile Configuration Configuratio n Profile Referenc e Dele Del ete a Configuration Profile Qualityy of S Qualit Se ervic e - Classific ation Qua Quality of Servic e - Sc heduling Viewing/Changing Viewing/Changin g Network IP Addresses Viewing/Changing TNet Proxy Configurations Using th the e TNet TNet Proxy Viewe Viewer Loading/Activating New Software and Lic enses Ab About out Loading Loading De Devvic e Software Via Pr oVision Eclipse Software Loa Loading Examples Stage 1: Software Load Proc edure 201 202 206 211 212 214 217 218 220 221 221 222 224 Part A Register Register the Sof Software onto the server Pa Part rt B Load Load the Software onto the Devices Stage 2: Software Activa Activation Pr oc edure Recommended Activati Activation Proc ess Eclipse Softwar Software Ac tivation Pr oc edure TRuepoin TRuep ointt Software Activa Activation Proc edure Other Software Activati Ac tivatio on Proc edure Eclipse and and CTR CTR Node Node Lic enses Device Configu Configuration ration Bac Bac kup and Restore CHAPTER 5. CARRIER ETH THERNET ERNET MANAGEMENT VLAN Management Overview of VLANs Vi Vie ewing Disc overed VLANs 224 227 230 230 231 233 236 237 240 243 244 244 245 VIII AVIAT NETWORKS PROVISION USER MANUAL Viewing List of Discovered VLANS Viewing VLAN Configuration Details Viewing VLAN Topology Viewing VL VLANs in th the Physic al and Fl Flat Ma Maps Identifying and Resolving VLAN Faults 246 247 250 252 254 Configuring VLANs Pr ovisioning a New VLAN Modifying an Existing VLAN Deleting an Existing VLAN Ether net OAM Management Overview of Ethernet OAM Viewing Disc overed EOAM MAs Viewing List Of Discovered EOAM MAs Viewing Viewi ng EOAM MA MA Logic al Topology Vi Viewin ewing g EOAM MA Physic al Topology Identi Iden tifyi fying ng an and d Resolving Resolving EOA EOAM Configuration Faults Configurin Config uring g Ethernet Ethernet OAM Provisioning Provisionin g a New EOAM MA 257 257 261 262 263 264 265 266 267 269 270 275 275 Modifying Modifyin g an EOAM MA Deleti Dele ting ng an EOAM MA ERP Ring Ring Managem Manageme ent Overview of ERP ERP Vi Viewin ewing g Discovered Discovered ERP Rings and Ri Ring Co Configuration Vi Viewin ewing g ERP Rin Ring g Co Conf nfiiguration Details Co Conf nfig iguri uring ng an ERP Ring Ring Provisionin Provision ing g a New ERP Ring Provisioniing an ERP Subring Provision Modifying Modifyin g an ERP Ring Deleting an ERP Ring 280 280 282 282 283 285 286 286 290 292 292 CHAPTER 6. MANAGING EVENTS Event Manageme Managemen nt Proc esses Managing Managin g Event Proc esses in ProVision Suggestted Steps for Managing Events Sugges Event Management Interdependenc ies Setti Set ting ng Up Sc or eboar d Groups Customizing Event Br owsers Event vent Manageme Management nt Procedure Proceduress Network Events Network Event States Viewing Network Events Viewing an Event’ s Pr operties Acknowlledging a Networ k Event Acknow Unacknowledg Unacknowled ging a Networ k Event Managing Managi ng Event Notific ation Po Pop-Ups and Au Audio Alarms 295 296 296 296 297 297 297 299 299 299 300 301 303 305 306 614-330055-001 DECEMBER 2015 IX PROVISION USER MANUAL Manually Clear ing a Networ k Event Manually Resynchronize Alarms Configure TRuepoint 64 6400 Alarm Resync hronization Customizing Ev Event N Na ames or Severity Levels Sleep Status for a Devic e Event Br owsers Saving an Event Browser View Viewing a Saved Event Browser Customizing an Event Br owser Changing Event Browser Options Deleting an Event Browser Saving Event Browser Contents Printing Event Browser Contents Eventt Log Pre-Filte Even Pre-Filteri rin ng Vi Viewin ewing g Event Event Log Pre-Filte Pre-Filterin ring g Addi Adding ng An Event Event Log PrePre-Filter at the Root Level Addin dding g an Event Pre-filter at an Objec t Level Addi Adding ng an Even Event Pr Pre-Filter Via an Event Browser 307 308 308 310 311 314 315 316 317 321 323 324 325 326 328 329 332 333 Modifyin Modify ing g An Eve Event Log Pre-Filter Deletin Delet ing g An Event Event Log Pr e-Filter Event Analyzer Analyzer Security Log Eventt Noti Even Notification Set the the Server Notific ation Preferenc es Ad Add d or Edit Edit Event Event Notif Notificat icatio ion n Rules Delete an Event Notificati Notification on Rule Configuring Config uring the Notific ation Rule Se Sett Up an Emai Emaill Event Notific ation Set Up a Pop-Up Message Notification Set Set Up an Audio Alarm Notification Set Up Script Script Ex Execu ecuti tio on on Event Notification 334 335 338 340 341 342 343 347 348 351 353 355 357 Logical Containers Addin Add ing g a Device to a Logical Container Removing Removi ng a Devic Devic e from a Logic al Container Renaming Renamin g a Logic Logic al Container Deleting Deleti ng a Logical Contai Contain ner Logicall Links Logica Addin Add ing g a Logical Link Renamin Ren aming gaL Lo ogic al Link Deletin Delet ing g a Log Logical Link Scorebo Score board ard Group Group Sc enarios Ab About out Scorebo Scoreboard Group Sc enarios Viewing a Scoreboard Group Creati Crea ting ng a Score Scor eboar d Group 359 361 362 363 363 364 364 365 365 367 367 368 369 Editin Edit ing g a Scor Scoreboard Gr oup Deleting Deletin g a Sco Sc oreboard Group 370 370 X AVIAT NETWORKS PROVISION USER MANUAL Adding a Sc oreboard Editing a Sc oreboard Deleting a Scoreboard Opening an an Ev Event Br Browser from a Sc oreboard CHAPTER 7. SYSTEM DIAGNOSTICS AND REPORTS Using System Diagnostics About ProVision and Craft Tools Diagnostic and Pe Performance Tr ends Analysis Proc edures Circ uit Diagnostic s Feature Circ uit Diagnostic Window Setting Up a Circ uit Diagnostic Test Circuit Diagnostic Options Data Collec Collec tion Daily Performance Data Co Collec tion Enabling 15 1 5-minute Performanc e Data Collection Changi Changing ng Device Data Collecti Collection Status Etherne Ethern et Performance Data Collec tion Enabling Enablin g 15 15-Minute Ethernet Da Data Collec tion Vi Viewin ewing g Ethernet Performance Etherne Eth ernett Bandwidth Utilization Performance Featur Features Performanc e History Performance Tren Trends Performance Th Thresholds resholds Craft Tools and Diagnostic Diagnostic Controls List of Craft Craft Tools Tools Launchin Laun ching g a Craft Tool LE3000 an and LE3200 Craft Tool Installation WMT Craft Craft Tool TNet Web Web Craft Tool and Diagnostic s Launching the TNet Web Craft Tool TN TNe et Diagnostic s TNet Diagnostic s - Protection Tab TNet D Diiagnostic s - G. 821 Performanc e Tab TNet Diagnostics Diagnostics - CB 149 Performance Tab TNet Diagnostics Diagnostics - RSSI Tab XP4 Device Support: Craft Tool and Diagnostic s Launching the XP4 Craft Tool Launching the XP4 XP4 Diagno Diagnostic s Activatin Activat ing g and Deactivati Deactivating an an XP4 Tributary Loopbac k Activatin Activat ing g an and d De Deac tivating an an XP XP4 Loc al Loopback Viewing/Changiing XP4 Protection Settings Viewing/Chang Resetting Resetti ng an XP4 Radio Device Device Diagnostic Controls for Sel Selec ted Devic es 370 373 373 374 377 378 380 381 381 381 384 386 388 389 390 392 393 393 394 399 404 404 409 413 417 417 419 421 421 424 427 429 430 431 433 434 436 436 437 437 441 443 445 446 614-330055-001 DECEMBER 2015 XI PROVISION USER MANUAL Constellation Diagnostic Controls CAU Diagnostic Contr ols DART Diagnostics Contr ols DVA Diagnostic Controls Megastar Diagnostic Controls CHAPTER 8. DEVICE AND NETWORK REPORTS Inventory Reports View and S a avve the Inventory Report fo f or a Single Devic e View and S a avve Inventory Reports for Multiple Devices Ec lipse Fault Report Capac ity Report View / Save / Delete Ser ver Reports Vi View ew and and Save Save Capac ity Reports for Multiple Devic es RF Network Health Health Reports Run Run an and d View RF Network Health Reports Ethernet Network Health Report Clock Synchronizati Synchronization on Network Hea Health Report Eclipse Sec urity Status Report Clock Sync Report Link Repor Report Licenssing Report Licen Creating Creati ng Custom Custom Reports Scheduling Schedu ling Repo Reports Reports Available by Device Typ Type Glossary Index 447 451 452 453 455 457 458 459 462 465 467 469 471 474 475 480 485 488 490 492 496 498 507 510 513 dxli XII AVIAT NETWORKS Chapter 1. Welcome to ProVision Welcome to ProVision. ProVision is a management tool for monitoring the eleme elements nts in a wireless wirele ss radio network. ProVision h has as an easy to use interf interface ace and tools that enable you y ou to view events from network devices. This means that you can identify problem areas in your network, and determine how to solve these proble problems. ms. The purpose of the User Guide documentation is to provide you with the technical information you require to use ProVision. This includes: l Using ProVisio ProVision n to create create and maintain network network maps l Monitor Monitoring ing and managing device status, per perfor formance, mance, and event repo reporting rting l Configuring Aviat Aviat Networks Networks devices l Configuring Configuring and managing thir third d party devices devices l Generating Generating supporting supporting reports reports and graphs graphs This documentation is for all ProVision users, including: Ro le R ole Descriptio n NOC Operators Monitor the radio network for errors and performance. FolFollow predefined procedures when faults are detected. May have little or no radio expertise. NOC Engineers Config Configure ure the radio sett settings ings and perfor performs ms so softwar ftwaree and configuration changes. Radio domain experts. NOC Fault Finders Diagno Diagnose se and isol isolate ate faul faults ts in the netwo network rk down to the unit/event level. Issue tro trouble uble tickets to field engineers where necessary. If you are working with ProVision in a different role, for example, as a ProVision administrator, refer to the Additional Documentation on page 10 10.. This section includes the fo following llowing topics: l What You Need Need To Know To To Use ProVision on page 6 l The Goals Goals of ProVisio ProVision n on page 2 l How ProVisio ProVision n Works Works on page 3 l Getting the Most Most Value from from ProVision ProVision on page 4 l Additional Doc Documentation umentation on page 10 l Documentation Organization on page 7 l Documentation Convention Conventionss and Terminology on page 9 614-330055-001 DECEMBER 2015 CHAPTER 1. WELCOME TO PROVISION The Goals of ProVision ProVision is the best tool to help your business to manage its radio network in many ways:: ways l Achieving Achieving maximum system availability. availability. l Reducing network operating ccosts. osts. l Managing your network network pr proactive oactively ly rather than reactively. reactively. How does ProVision do this? ProVision informs the user of events and device failures in a managed wireless radio network. By identifying events and failures for users, this reduces the time between a fault occurring and the fault being repaired. It may even allow a repair to be done before a link fails completely. ProVision also obtains and stores data about the network devices, including: l l l Infor Information mation entere entered d when the device was installed and commissioned commissioned into service Perfor Performance mance data Events fro from m the device ProVision can be used to reconfigure the devices in the network. ProVision is used to assist in performing the following functions: l Network Network plann planning ing l Installation l Commissioning l Event monitoring l Device / network network per performance formance l Fault diagnostics l Device re reconfigurations configurations l Inventory management Next Topic: How ProVision Works on page 3 1 2 AVIAT NETWORKS PROVISION USER MANUAL How ProVision Works This figure shows how ProVision interfaces with the radio network: Figure 1-1. How ProVision ProVision Works The ProVision Server communicates with the network devices, and stores the events/respon s/r esponses ses in a database. The ProVision Client provides the user interface, and displays on screen the events and data the user has requested. The ProVision ProVision Ser Server ver and ProVision ProVision Client software software can be installed on a single computer,, or separately. puter separately. ProVision can have multiple Clients: up to 15 Clients for each Server. 614-330055-001 DECEMBER 2015 3 CHAPTER 1. WELCOME TO PROVISION Getting the Most Value from ProVision Using ProVision adds value proactively by finding problems before they affect traffic. ProVision has features that increase its value in several ways. Turning Data Into Informatio Information n ProVision Pro Vision enable enabless you to stre streamline amline the number number of a alarms larms by: 1. Re Reducing ducing the th e number of alarms entering entering the system using pre-filte pre-filters, rs, “filter “filtering ing a att input”. 2. Reducing the volume of alarms being displayed on screen using filters, “filtering at display”. In addition, you can create views and Scoreboard groups to meet your monitoring needs. Score Sco rebo boards ards allow you to group devices devices together together in views that provide the information information you require. require. This provides a convenient convenient way to revie review w the status stat us of t hese d devices. evices. At a glance, you can highlight the important areas of the business, for example; the network backbone, backbo ne, golden cells, and high capacity links, with: l Easy diffe d ifferentiation rentiation betwee between n real real radio problems problems vs. informational data l Alarm status for for the entir entiree link l l Re Reducing ducing the amount of of data that is not of value by putting the radio in sleep sleep mode Notes Notes and messaging which makes information information available to all who need it Fault reports scan the network elements and present the radios with the highest number of alarms, or the highest severity alarms. With ProVision's Mobile Mobile Client, you can stay posted about network st status atus and faults while you travel,us travel,using ing Apple iOS or Android And roid devices. Managing Data Over Time Equipment status values such as RSL, temperature and voltages, and G.826 are only meaningful if you can compare them to a previous, similar value. ProVision can track these values over time and set thresholds when the values move outside specified ranges. Having the history of an alarm can add great value. ProVision lets you view all the alarms from a single radio and sort the alarms by type, enabling you to determine what is really happening. This is more significant than viewing one alarm out of context. With ProVision, you can pre-deploy radios and store data d ata about them without Managing them. Radios start forwarding events to ProVision when their status is changed to Managed. 4 AVIAT NETWORKS PROVISION USER MANUAL Using Perf P erform ormance ance Analysis ProVision can collect and save huge amounts of performance data from the radios. This data is normally over-written in the radios. The data can be used to find patterns before traffic is affected, and to diagnose problems if a radio fails. ProVision can keep the daily data for all radios for a predefined time. This data can be used to spot long term trends in radio performance, identify problem sites or radios. Radios that are identified as critical or causing problems can also be monitored more intensely using 15-minute data collection, which can be used to find problems that are occurring now. This data can also be kept in the ProVision database indefinitely. Performance data can provide information in many ways. If a radio is having performance trouble, checking the performance data from nearby links or co-sited links can help to identify if the problem is due to non-equipment problems such as rain fade, local interference, site power problems, or other reasons. ProVision can be used to display performance data from a number of radios at the same time to assist with this, or for a single radio over over t ime. Real value can be gained from ProVision when a radio has failed. Looking at historical performance data and events from a failed radio can help determine; what end of the link has failed and what type of failure it may be. The data stored in ProVision for the failed radio is available even when communication to the link has been lost. 614-330055-001 DECEMBER 2015 5 CHAPTER 1. WELCOME TO PROVISION What You Need To Know To Use ProVision To use ProVision ProVision effe effective ctively, ly, we recommend recommend that you have th thee followin following g knowledge knowledge and skills: l General General familiar familiarity ity with Aviat Networks Networks devices devices and device conce concepts pts Experience working in a ProVision environment is also helpful. Working knowledge of ProVision is demonstrated by completing ProVision training t raining courses: l ProVision User Training l ProVision System Administrator Training 6 AVIAT NETWORKS PROVISION USER MANUAL Documentation Docu mentation Organization This manual is organized into the following chapters and appendices: Device Support in ProVision This section describes all devices supported by ProVision, and the specific ProVision functionality that supports the devices. It also includes lists of Generic Device supported third party devices. Navigating ProVision on page 35 This section describes how to navigate the ProVision software front end. It introduces the ProVision ProVision user interface interface and the main interface interface compon components. ents. It also d escrib escribes es the network search facility and navigating naviga ting context-sensitive pop-up menus and functions. Deploying and Managing Devices on page 101 This section describes how to deploy, link, and manage radios in ProVision. This includess cir include circuit cuit management management and cir circuit cuit provisioning. provisioning. Carrier Ethernet Management on page 243 This section describes how to view and configure Carrier Ethernet functionality, including: l VLAN l Ethernet OAM l ERP Managing Events on page 295 This section describes event management tools for events generated by the radios and by the system. This includes: l l l Individual event event history and probable probable cause identif identification ication.. Se Servic rvices es that enable enable you to group group together together network network de devices vices that share sh are a common purpose. Customizable Event Event Browsers Browsers with event event filtering filtering and browser browser options that you can save and re reuse. use. l Prefilte Prefiltering ring events events at input which re reduces duces the number number of events events in the system. l Scorebo Scoreboard ard groups, providing an at -a-glance over overview view of a network. System Diagnostics and Reports on page 377 This section describe describess system diagnostics, including: l Enabling performance performance data dat a co collection. llection. l Launching the individual radio craft craft tools. tools. l Using Diagnostic Diagnostics. s. Device and Network Reports on page 457 614-330055-001 DECEMBER 2015 CHAPTER 1. WELCOME TO PROVISION This section describe describess how to use all ProVision ProVision reports, reports, including custom reports reports and report scheduling. 7 8 AVIAT NETWORKS PROVISION USER MANUAL Documentation Conventions and Terminology Graphic Cues The following icons function as graphical cues used to characterize particular types of associated associate d supporting information. information. CAUTION: A caution caution item item identifi identifies es important information information pertainin pertaining g to actions actions that that may cause damage to equipmen equipment, t, loss of data, or corrupti c orruption on of files. W AR NI NG : A warning item identifies identifies a ser ious physical danger or major possible problem. NOTE: A note item identifies additional information about a procedure or function. 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 Cou rier font is used to indicate commands that the user needs to type in. Italic font is used to emphasize words and phrases, to introduce new terms, and for the titles of printed publications. Common Terminology Terminology l Clic Click k or Select: Point the mouse pointer at the item you want to select, then quickly quic kly press press and re release lease the left mouse button. l Right-Click: Point the mouse pointer at the item you want to select, then quickly press and release the right mouse button. 614-330055-001 DECEMBER 2015 9 CHAPTER 1. WELCOME TO PROVISION Additional Documentation The ProVision Installation and Administration Guide (P/N 614-330053-001) contains additional information to help users understand, install, and use ProVision. Its audience is advanced users, such as system administrators. It provides system administrators with the following instructions: l l l Task-ori Task-oriente ented d assistance a ssistance in planning for, installing, and configuri configuring ng ProVisi ProVision on hardware and softwar softwaree components. ProVision database data base backup backup and restore procedure proceduress How to provide Aviat Network Networkss with the information information rreq equire uired d to analyze and respond to ProVision software problems. It is included in the online help. The online help also includes information about equipment alarms that may be accessed for Aviat Networks radios. Furtherr additional documentation Furthe documentation includes: ProVision Pro Vision Mobile Client Manual ProVision Pro Vision Upgrade Guide ProVision Pro Vision Solaris Quick Start Guide ProVision Pro Vision Windows Quick Start Guide 10 AVIAT NETWORKS Chapter 2. Device Support in ProVision ProVision natively supports all Aviat Networks microwave radio and network support devices. ProVision also natively supports partner products. Additional third-party devices are supported through its Generic Device functions. This section provides a reference list of all the devices that ProVision supports. It also includess device function include function summaries for Aviat Ne Network tworkss devices, devices, and fo forr devices that have spec sp ecial ial functionality functionality in Pr ProVisio oVision. n. Content here includes: l List of Device Devicess Supported Supported in ProVision ProVision on page 12 l Eclipse Device Device Suppor Supportt on page 16 l CTR Device Device Support Support on page 18 l WTM 3100 Device Device Supp Support ort on page 23 l WTM 3200 3200 Device Device Support on page 24 24 l WTM 3300 3300 Device Device Support on page 25 25 l WTM 6000 6000 Device Device Support Support on page 27 l TRuepoint TRue point Device Support on page 29 l Constellation Constellatio n Device Device Suppor Supportt on page 31 l Generic Gener ic Device Support on page 32 l Additional Devic Devicee Support on page 33 614-330055-001 DECEMBER 2015 CHAPT CH APTER ER 2. DEVICE SUPPORT SUPPORT IN PROVISION List of Devices Supported in ProVision This section lists all the devices supported in ProVision. Each list is in alphabetical order. Aviat Networks Networks Microwave Microwave Network Devices l Altium 155, MX l Aurora l CAU l Constellation l Constellation Constellation via Farscan Farscan Proxy Proxy l CTR 8300 l CTR 8540 l CTR 8440 l CTR 8611 l DART l DVA l DVM 45, xT l DXR 100 l DXR 200 via SMA Proxy l DXR 700 / SMA l Eclipse IDU (all (all variants), INU, INUe, INUe, IDU IDU,, IRU600, IRU600, RAC LL, RAC LL DDR l LE3000, LE3200 l Megastar Megastar 1+, M: M:N N l Microstar Microstar type I, II, II, III l SPECTRUM II SNMP SNMP l l TNet TNet Pr Proxy oxy devices devices (all 13 device types) TRuepoi TRuepoint nt 4000, 4040, 4040, 5000 l TRuepoint TRuepoint 6400 l TRuepoint TRuepoint 6500 l Velox l WTM 3100 l WTM 3200 l WTM 3300 l WTM 6000 l XP4 16/E3/T3, 2/4/8X 11 12 AVIAT NETWORKS PROVISION USER MANUAL Partner Product Devices l l Accedian EtherNID, Metro Metro NID, NID, MetroNODE MetroNODE Cisco range: 3650, ME2400, ME3400E, ME3400E, MWR2941, ME3600, ME3800 ME3800,, ME 3600X, ME 3800X ME 3900, ASR 903, ASR 1000, SNS 3495, Catalyst 2950, l Catalyst 2960 E-Band E-Link 1000EX 1000EXR, R, LR LR,, Q, Eagle l EMS Proxy and N Network etwork Elements l Memotec Memotec CX-U l Radwin WinLink WinLink 1000, 1000, Radwin Radwin 2000 2000 l Sagem ADR 155C / 2500 eeXTR XTRA A l Sagem SAGEM-LIN SAGEM-LINK K l Symmetricom Timers Timers TP 100 1000+ 0+ TP 1100, TP 5000, 5000, TP 500 l Tellabs 7300 range: 7345 l Te Tellabs llabs 8600 range: range: 8605, 8609, 8611, 8630, 8660 l WiChorus SmartCore Devices Supported with GDS Packages l 4RF Aprisa XE XE Micr Microware oware Radio l Adtran MX280 MX2800 0 Mux l Adtran MX282 MX2820 0 Mux l Adtran Ne Netvanta tvanta 7100 Switch Switch l Adtran OPTI-6100 OPTI-6100 Mux l Adtran TA908e TA908e Mux l Adtran Tracer Tracer 6000 Microwave Microwave Radio l Alcatel MDR-8000 MDR-8000 Microwave Microwave Radio l Allgon Transcend Transcend Microwave Microwave Radio l APC UPS Ne Network twork Mgmt Card 2 Argus Cordex CXC l Asentria SiteBoss SiteBoss S500 Site Managers l Asentria SL81 Site Manager l Asentria SL10 SL10 Site Site Manager Manager l Bats AATS l Bayly OMNI OMNI Flex DACS l Bayly OMNI Linc Mux l Bayly OMNI OMNI Optix Mux Mux l Benning MCU MCU Power Power System l Benning Benning MCU v2 Powe Powerr System System l C&D Sageon Sageon Power Power System l l l CAC Axxius 800 Mux CAC Wide Bank 28 28 M Mux ux 614-330055-001 DECEMBER 2015 CHAPT CH APTER ER 2. DEVICE SUPPORT SUPPORT IN PROVISION l Cisco ASA 5500 l Cisco 1900 ISR Series Series Ro Router uter l Cisco 3750 Metro Metro Switch l Cisco 3824 3824 Router l Cisco 3825 3825 Router l l Cisco 7200 Series Series Router Router Cisco 7350 Switch l Cisco ASA 5500 5500 Series Series Firewall l Cisco ONS 15310-MA Mux l Delta CSU503 Power System l DPS NetGuardian NetGuardian G4 - G5 Site Manager Manager l Eaton SC200 Power System l Eltek BC2000 Power System l Eltek Smartpack, Smartpack, Flatpack Po Power wer Systems l Emerson LXP LXP Series Series Power Power System l Emerson Netsure Netsure 502 P Power ower System l ETI ADH ADH NETCOM NETCOM De Dehydrator hydrator l Exalt EXE X-5i 5i & EX-2.4i EX-2.4i Mi Micro crowave wave Radios Exalt EXE X-5i-16 5i-16 & EX-2.4i-16 EX-2.4i-16 Mi Micro crowave wave Radios l Fujitsu Flashwave Flashwave 4100 4100 Mux Mux l Fujitsu Flashwave Flashwave 9420 9420 Mux l GE MDS Intrepid Microwave Microwave Radio l Harris Intraplex l IPMobileN IPMobileNet et IP Network Network Controller l Keymile UMUX UMUX (via UNEM V8 EMS) EMS) l LaMarche LMHF l LightPointe Aire X-Stream X-Stream Microwave Microwave Radio Radio l Lineage Lineage Galaxy Pulsar NE843 P Powe owerr System System l Loop Telecom Telecom AM3440-A AM3440-A & C Mux l Loop Teleco Telecom m O9100 Mux Mux l Loop Telecom Telecom V4150 Mux l MDS Intrepid and Intrepid Ultra l MultiTel iS3, iS3, Fusion, Mirador Mirador Site Managers l NEC iPasolink Microwave Microwave Radio Radio l NEC NLite NLite E Micr Microwave owave Radio Radio l RFL IMUX IMUX 2 2000 000 M Multip ultiplexers lexers & MDACS l Siemens Siemens HiPath 4000 l Socomec Socomec Net Net Vision Po Power wer System l Sycamore DNX-1u and DNX-11 Mux l Tejas TJ100 Mux l l l Tejas TJ1270 Mux Tejas TJ1400 Mux 13 14 AVIAT NETWORKS PROVISION USER MANUAL l Tejas TJ1600 Mux l Telco Systems OTM1000 OTM1000 Mux Mux l Te Tellabs llabs 6300 6300 Mux (via (via ECT EMS) l Tellabs 8600 Switch l Terabeam Terabeam TeraBridge TeraBridge 5x45 and 5x45 11 Etherne Et hernett Micr Microwave owave RadioRadio l l TrangoLINK TrangoLINK Giga Microwave Microwave Radio TrangoLINK TrangoLINK GigaPlus Microwave Microwave Radio l TRAK TRAK 9100 Timing System l Zhone IMACS IMACS S Serie eriess Mux 614-330055-001 DECEMBER 2015 15 CHAPT CH APTER ER 2. DEVICE SUPPORT SUPPORT IN PROVISION Eclipse Device Support What Is Eclipse? Eclipse is one of the industry’s leading platforms for microwave access, transport and backhaul applications. app lications. Eclipse Eclips e p provides rovides the most comprehensive wireless solution availavail able for transport of all types of traffic, from low-capacity PDH to high-capacity SDH/SONET to Carrier Ethernet. Eclipse features features include Super-PDH™ Super-PDH™ capacity capa city migratio migration, n, advanced nodal networki networking ng and Liquid Bandwidth assignment of available radio capacity between TDM and Ethernet traffic, all to deliver high-end performance at lower overall cost of ownership. Eclipse radios are easy to upgrade with the addition of DAC and RAC cards and additional modules. Because of this, Eclipse networks have a long life. ProVision can manage all variants of Eclipse devices, including: l Eclipse 100 Eclipse 300 300 (IDU) l Eclipse 300 300 (INU) l Eclipse 300 300 (INUe (INUe)) l IRU 600 l l Eclipse incor incorporating porating the followin following g plug-ins: RAC LL DDR, DDR, DAC 1 55o, DAC 155eM, DAC GE3, NCC, NCM, Fan l Eclipse using using DPP port port Ethernet Ethernet l Eclipse Edge IDUspe How ProVision Supports Eclipse ProVision is the best element manager for Eclipse devices. All of ProVision's functions work for Eclipse. This table lists Eclipse management support supp ort functions. Functio n Area Information Deploy and Discover Eclipse Devic Devices es and Nodes Nodes Deplo Deployment yment on page 117 Network Auto-Discovery for Devices on page 148 Circuits and Links Viewing Viewin g and Managing Circuits on page 179 About Circuits and Circuit Management on page 177 Circuit Provisioning on page 186 Linking Procedures Procedures on page 167 Creating an Eclipse RF Link on page 171 Logical Links Links on page 364 16 AVIAT NETWORKS PROVISION USER MANUAL Functio n Area Information Configure Viewing Viewin g Config Configuration uration fo forr Devic Devices es on page 194 Configuration Profiles for Bulk Configuration on page 201 View Devices Submaps Sub maps on page 71 Collect Data Viewing Eclipse RAC Low Latency Links Performance Per formance Data Collection on page 1 Ethernet Performance Data Collection on page 393 Ethernet Bandwidth Utilization on page 399 Reports RF Ne Network twork Health Re Reports ports on page 474 Capacity Report on page 467 Eclipse Fault Report on page 465 Eclipse Security Status Status Report on page 488 Clock Sync Report on page pa ge 490 Clock Synchronization Network Health Report on page 485 Ethernet Network Health Report on page 480 Manage Device Software Link Report on page 492 4 92 Loading/Activat ing New New Software Software and Licenses Licenses on page 221 Eclipse Software Software Loading Examples on page 222 Eclipse and CTR Node Licenses on page 237 Backup and Restore Device Configuration Bac Backup kup and Restore on page 240 Configuration Backup and Restoration on page 1 Security and Alarms Eclipse Str Strong ong Se Securi curity ty on page 1 Event Analyzer on page 338 338 The ProVision online help includes a complete listing of the Eclipse Alarms as an appendix. appendix. Carrier Ethernet VLAN Manage Management ment on page 244 Ethernet OAM Management Manag ement on page 263 ERP Ring Management on page 282 Clock Synchronization View on page 192 614-330055-001 DECEMBER 2015 17 CHAPT CH APTER ER 2. DEVICE SUPPORT SUPPORT IN PROVISION CTR Device Support ProVision Pro Vision provides support for the entire suite of CTR devices devices provide provided d by Aviat Ne Nettworks. Note that t hat all these devices require require a specific feature license key. CTR 8300 and ProVision The CTR 8300 is a super-compact microwave router that can pack up to 1 Gbps of data throughput in a single radio channel. It is a smaller version of the CTR 8540 microwave router. How ProVision Supports CTR 8300 Devices Function Area Information Deploy and Discover Standard SN SNMP MP Devic Devicee Deplo Deployment yment on page 112 CTR 8300 and 8540 Device Deployment on page 125 Network Auto-Discovery for Devices on page 148 About Loading Device Software Via ProVision on page 221 Creating an RF Link from the Tree Viewer on page 169 Adding a Device to t o a Logical Container on page 361 Adding a Logical Link on page 364 Configure Viewing Configuration for Devices on page 194 Configuration Profiles for Bulk Configuration on page 201 Device Security Accounts Deploying a Configur Configuration ation NBI View Submaps Sub maps on page 71 Interface Interf ace Views Collect Data Perfor Per formance mance Data Collec Collection tion on page 1 Performancee History on page 404 Performanc Performanc ormancee Trends Trends on page pa ge 409 Performance Thresholds on page 413 Ethernet Performance Performance Data Collection on page 393 Ethernet Bandwidth Bandwidth Utilization on page 399 18 AVIAT NETWORKS PROVISION USER MANUAL Function Area Information Reports RF Network Health Repor Reports ts Inventor Inve ntory y Re Reports ports on page 4 58 Ethernet Network Health Report on page 480 Creating Custom Reports on page 498 Backup and Restore Link Report on page 492 Devicee Config Devic Configuration uration Backup and Restor Restoree on page 240 Configuration Backup and Restoration on page 1 Carrier Ethernet VLAN Manage Management ment on page 244 Ethernet Ether net OAM Management Management on page pa ge 263 ERP Ring Management on page 282 CTR 8440 and ProVision The Aviat Network Networkss Converged Transport Transport Router (CTR) 8440 is a next generation carrier class cell site router that combines high performance Carrier Ethernet & IP/MPLS switching and routing, along with TDM services aggregation, in a compact 1RU platform. How ProVision Supports C CTR TR 8440 Devices Function Area Information Deploy and Discover Standard SN SNMP MP Devic Devicee Deployme Deployment nt on page 112 Network Auto-Discovery for Devices on page 148 Linking Procedures on page 167 View Submaps Sub maps on page 71 Interface Interf ace Views Collect Data Perf Pe rfor ormance mance Data Collec Collection tion on page 1 Perfor Per formance mance Thre Thresholds sholds on page 413 Ethernet Performance Data Da ta Collection on page 393 Ethernet Bandwidth Utilization on page 399 Deploying Deplo ying a Per Perfor formance mance Data NBI Deploying a Configuration NBI Reports Ethernet Netwo Network rk Health Report on page 480 Creating Custom Reports Reports on page 498 Inventory Reports Reports on page 458 Link Report.htm Report.htm Backup and Restore Restore Device Configura Configuration tion Backup and Restore on page 240 Configuration Configurati on Backup and Restoration on page 1 614-330055-001 DECEMBER 2015 19 CHAPT CH APTER ER 2. DEVICE SUPPORT SUPPORT IN PROVISION CTR 8540 and ProVision The Aviat Networks Converged Transport Router (CTR) 8540 offers fully converged microwave indoor unit (IDU) and cell site router (CSR) functions in a new carrier class platform built both for intelligent microwave and IP/MPLS interwork- with split mount and all outdoor radios.networking with flexibility to It is designed to provide complete solutions with lowest cost of ownership by removing the need to consider which product to use for switching and routing, which for radio, and their integration for management, training and sparing. CTR is espe especially cially applicable in network networkss inco incorpor rporating ating radio backhaul where this unique versatility provides the most flexible, sscalable, calable, and cost-efficient cost-efficient plat form form of type. t ype. Its features include: l Media Media convergence and transport trans port over radio, radio, fiber or copper on one compact l 1U platfor platform m l Site aggregatio aggregation n and expansion through multiple IP, IP, Etherne Ethernet, t, and PDH interfaces l Up to eight directly-conne directly-connecte cted d IF or PoE radio links per chassis l Additional Addit ional radios can be co connected nnected on no non-PoE n-PoE Ethernet interfaces interfaces l Provision Provision for for all-indoor all-indoor operation operation to 11 GHz or split-mount split-mount to 80 GHz l l l L1LA support, including for for 2+0 L1LA, L1LA, 2+2 XPIC XPIC L1LA, and inter-RAC inter-RAC protection Adaptive or fixed fixed modulation to 1024 1024 QAM Co-channel operation with XPIC for for double density llinks inks in a single fre frequency quency channel l Comprehensive L2 traffic, service, service, and protection options; QoS, QoS, VLANs, LAG, l EOAM, QinQ, RSTP, RSTP, MSTP, MSTP, ERPS l PoE+ ports ports support 65W per inter interface face l T1/E1 transport via TDM pseudowires l Chassis based active/standby active/standby for prote protection ction and expansion l Plug-in module and software software options fo forr service service eexpansion xpansion l CLI, Web GUI, and SNMP SNMP manageme management nt access l Power efficient efficient de design sign 20 AVIAT NETWORKS PROVISION USER MANUAL How ProVision Supports CTR 8540 Devices Function Area Information Deploy and Discover Standard SN SNMP MP Devic Devicee Deployme Deployment nt on page 112 CTR 8300 and 8540 Device Deployment on page 125 Network Auto-Discovery for Devices on page 148 About Loading Device Software Via ProVision on page 221 Creating an RF Link from the Tree Viewer on page 169 Adding a Device to a Logical Container on page 361 Adding a Logical Link on page 364 Configure Viewing Viewi ng Confi Configuration guration for Devic Devices es on page 194 Configuration Profiles for Bulk Configuration on page 201 Device Security Accounts Deploying a Configuration NBI NBI View Submaps Sub maps on page 71 Interface Views Interface Clock Synchronization View on page 192 Collect Data Performan Perfor mance ce Data Collection on page 1 Performance History on page 404 Performance_Trends.htm Performance Perform ance Thresholds on page 413 Ethernet Performance Data Collection on page 393 Ethernet Bandwidth Utilization on page 399 Reports RF Network Health Reports Inventor Inve ntory y Re Reports ports on page 4 58 Ethernett Network Health Report on page 480 Etherne Creating Custom Custom Reports on page 498 Link Report on page 492 Clock Synchronization Synchronization Network Health Reports Backup and Restore Restore Device Configuration Backup and Restore on page 240 Configuration Backup and Restoration on page 1 Carrier Ethernet Ethernet VLAN Management on page 244 Ethernet OAM Management Management on page 263 ERP Ring Management on page 282 CTR 8611 and ProVision The CTR 8611 is s an integrated integrated microwave ro router uter purpose-built purpose-built for mission-critic mission-critical al applications where full redundancy and protection are paramount. It has a High Availability design to interoperate with any transport network, and delivers industry-leading 614-330055-001 DECEMBER 2015 21 CHAPT CH APTER ER 2. DEVICE SUPPORT SUPPORT IN PROVISION L2/L3 routing functionality L2/L3 functionality optimized optimized to impro imp rove ve the per perfor formance mance and manageability manageability of microwave-based transport networks. How ProVision Supports CTR 8611 Devices Function Area Information Deploy and Discover Standard SN SNMP MP Devic Devicee Deployme Deployment nt on on page 112 CTR 8300 and 8540 Device Deployment on page 125 Network Auto-Discovery for Devices on page 148 About Loading Device Software Via ProVision on page 221 Creating an RF Link from the Tree Viewer on page 169 Adding a Device to a Logical Container on page 361 Adding a Logical Link on page 364 Configure Viewing Viewi ng Configur Configuration ation for Devic Devices es on page 194 Configuration Profiles for Bulk Configuration on page 201 Device Security Accounts View Deploying a Configur Deploying Configuratio ation n NBI Submaps Sub maps on page 71 Interface Interf ace Views Collect Data Performan Perfor mance ce Data Collection on page 1 Performance History on page 404 Performance Trends on page 409 Performance Perform ance Thresholds on page 413 Ethernet Perf Perfor ormance mance Data Collec Collection tion on page 393 Ethernet Eth ernet Bandwidth Utilization on page 399 Reports RF Network Health Repor Reports ts Inventory Reports Reports on page 458 Ethernet Net work Health Healt h Repor Reportt on page 480 Creating Custom Reports on page 498 22 AVIAT NETWORKS PROVISION USER MANUAL WTM 3100 Device Support What Is WTM 3100? The Aviat Ne Network tworkss WTM 310 3100 0 is an all outdoor packet-micr packet-microwave owave radio operating operating in licensed frequency bands from 7 to 38 GHz with channel sizes from 7 to 56 MHz. Suitable for connecting locations up to ~50km apart, the WTM 3100 will deliver up to 360 Mbit/s of Ethernet capacity on a single port. It is designed to meet Carrier Ethernet transport requirements and provides operators with an economic solution for basic microwave micr owave networking networking applications ap plications at sites with severe severe space restrictio restrictions. ns. The WTM 3100 can be deployed in a variety of Ethernet or Carrier Ethernet applications to connect packet switches, routers or specialized IP enabled platforms such as 4G mobile RAN. It operates as a transparent Ethernet bridge and can be deployed in chain, ring,, star or mesh topologies. ring topologies. The WTM 3100 also provides operators with a clear demarcation between the Ethernet transport (microwave) and the switching layer of the network, enabling rapid fault isolation and optimizing the mean time to repair (MTTR). How ProVision Supports WTM 3100 Pr ProVisio oVision n is the best eleme element nt manager for WTM 3100 3100 d evices. evices. This table lists WTM 3100 3100 management support functions. management functions. Function Area Information Deploy and Discover Standard SN SNMP MP Devic Devicee Deployme Deployment nt on page 112 Network Auto-Discovery for Devices on page 148 Configure Viewing Viewi ng Confi Configuration guration for Devic Devices es on page 194 Configuration Profiles for Bulk Configuration on page 201 NBI Configuration Management Management View Devices Interface Interf ace Views on page 78 Collect Data Perf Pe rfor ormance mance Data Collec Collection tion on page 1 Performance Thresholds on page 413 Ethernet Performance Performance Data Collection on page 393 Ethernet Bandwidth Utilization on page 399 Reports RF Network He Health alth Reports on page 474 Capacity Report on page 467 4 67 Ethernet Network Health Report on page 480 Creating Custom C ustom Reports on page 498 614-330055-001 DECEMBER 2015 23 CHAPT CH APTER ER 2. DEVICE SUPPORT SUPPORT IN PROVISION WTM 3200 Device Support What Is WTM 3200? The Aviat WTM 3200 is an advanced all outdoor packet radio featuring an advanced Carrier Ethernet switch and highly scalable microwave transport platform. Its specialty is efficient microwave networking for space and power restricted locations. Equipped with QPSK to 1024 QAM modulation in frequency bands from 6 to 42 GHz, the WTM 3200 supports throughput rates up 1 Gbit/s. The WTM 3200’s 3200’s Carrier Carrier C Class lass Ethernet Ethernet switch supports a advanced dvanced traffic management, management, security and control features. It can be quickly integrated and harmonized with existing (deployed) Carrier Ethernet networks and devices such as the Aviat Eclipse GE3 switching platform. The WTM 3200 also provides the added security of AES encryption for management and payload traffic. Low power consumption (<35 Watts) and simplified cabling ensures the WTM 3200 maximizes installation, operations and maintenance efficiency at small sites. How ProVision Supports WTM 3200 ProVision is the best element manager for WTM 3200 devices. This table lists WTM 3200 management support functions. Function Area Information Deploy and Discover Standard SN SNMP MP Devic Devicee Deplo Deployment yment on page 112 Network Auto-Discovery for Devices on page 148 About Loading Device Software Via ProVision on page 221 Configure Viewing Viewin g Confi Configuration guration for Devic Devices es on page 194 Configuration Profiles for Bulk Configuration on page 201 NBI Configuration Management Managem ent Collect Data Perfor Per formance mance Data Collec Collection tion on page 1 Performance Thresholds on page 413 Ethernet Performance Data Collection on page 393 Ethernet Bandwidth Utilization on page 399 Reports RF Network He Health alth Reports on page 474 Ethernet Network Health Report on page 480 Backup and Restore Device Configurati Configuration on Backup and Restore on page 240 Configuration Backup and Restoration on page 1 24 AVIAT NETWORKS PROVISION USER MANUAL WTM 3300 Device Support The Aviat Ne Network tworkss WTM 33 3300 00 is an innovative microwave microwave networking networking plat for form m that introduced a new class of performance to the 80 GHz market. It delivers link capacities to urban network sites from 400 Mbps to 1 Gbps in the smallest, lightest and most aesthetically integrated package in the market. Applications include mobile backhaul (macro and small cell), fixed line access and enterprise LAN interconnect. The Aviat Networks WTM 3300 offers a unique combination of high system gain, adaptive modulation techniques and capacity scalability from 400 Mbit/s to 1 Gbit/s within a standard 250 MHz channel. Suitable for urban links from 0.5 to 3 km, the WTM 3300 is the first 80 GHz product to feature an ‘invisible antenna’ design which drives significant TCO gains for the operator. It also means operators can now access more rooftop, wall and street level sites compared to traditional parabolic antenna systems that are often not viable due d ue to techn technical, ical, environme environmental ntal or planning restrictio restrictions. ns. For locations locations where where higher gain is required, WTM 3300 can also be equipped with 1 ft or 2 ft parabolic antenna. How ProVision Supports WTM 3300 ProVision is the best element manager for WTM 3300 devices. This table lists WTM 3300 management support functions. Functio n Area Information Deploy and Discover Standard SN SNMP MP Devic Devicee Deplo Deployment yment on page 112 Network Auto-Discovery for Devices on page 148 Creating an RF Link from the Tree Viewer on page 169 Adding a Device to a Logical Container on page 361 Adding a Logical Link on page 364 About Loading Device Software Via ProVision on page 221 Configure Viewing Viewin g Config Configuration uration for Devic Devices es on page 194 Configuration Profiles for Bulk Configuration on page 201 View Devices Devices Interface Interf ace Views on page 78 Collect Data Performance Per formance Data Collection on page 1 Performance Per formance Thre Thresholds sholds on page 413 Ethernet Ethe rnet Performance Data Collection on page 393 Ethernet Ethern et Ban B andwidth dwidth Utilization on page 399 614-330055-001 DECEMBER 2015 25 CHAPT CH APTER ER 2. DEVICE SUPPORT SUPPORT IN PROVISION Functio n Area Information Reports RF Ne Network twork Health Re Reports ports on page 474 Capacity Report on page 467 Inventory Reports on page 458 Ethernet Network Health Report on page 480 Backup and Restore Creating Custom Reports on page 498 Devicee Configur Devic Configuration ation Backup and Re Restore store on page 240 Configuration Backup and Restoration on page 1 26 AVIAT NETWORKS PROVISION USER MANUAL WTM 6000 Device Support What Is WTM 6000? The Aviat Networks WTM 6000 is an all-IP trunking radio, capable of supporting up to 4 Gbit/s of aggregate data throughput. The WTM 6000 is a network operator’s first choice for high trunking capacity for regional and national backbone links in place of fiber. It includes advanced packet transport features that have only been available in lower capacity microwave systems. These include built-in Ethernet switching, link aggregation, traffic prioritization, Quality of Service controls and Synchronous Ethernet (SyncE) capabilities. Network operators that need ultra-dependable wireless connections can use WTM 6000 as a fiber alternative for all-IP network backbone links. The WTM 6000 is the highest density wireless trunking solution on the market, being the first system to accommodate up to 16 radio channels in a single sub-rack, and supporting 4 Gbit/s and more of aggregate Ethernet throughput . With integrated switching and native Ethernet/IP support, sup port, the WTM 6 6000 000 also a lso providess optional supp provide suppor ortt for STM-1 STM-1 traffic, traffic, enabling enabling operators operators to maintain m aintain legac l egacy y TDM services without having to use inefficient circuit emulation. The WTM 6000 is also the first trunking radio in its class to support 256QAM Adaptive Coding and Modulation (ACM) to enable enable operato operators rs to achieve higher higher link capacities capacities with smaller antennas. How ProVision Supports WTM 6000 Pr ProVisio oVision n is the best eleme element nt manager for WTM 6000 devices. devices. This table lists WTM 6000 management support sup port functions. Functio n Area Information Deploy and Discover Standard SN SNMP MP Devic Devicee Deplo Deployment yment on page 112 Network Auto-Discovery for Devices on page 148 Configure Viewing Viewin g Config Configuration uration fo forr Devic Devices es on page 194 Configuration Profiles for Bulk Configuration on page 201 Manually Discovering WTM 6000 Configuration on page 161 NBI Configuration Management Management View Devices Equipmentt Views on page 73 Equipmen Physical Viewer and Icons on page 55 614-330055-001 DECEMBER 2015 CHAPT CH APTER ER 2. DEVICE SUPPORT SUPPORT IN PROVISION Functio n Area Information Collect Data Performance Per formance Data Collection on page 1 Performance Thresholds on page 413 Ethernet Performance Data Collection on page 393 Ethernet Bandwidth Utilization on page 399 Reports RF Ne Network twork Health Re Reports ports on page 474 Ethernet Network Health Report on page 480 27 28 AVIAT NETWORKS PROVISION USER MANUAL TRuepoint Device Support The TRuepoint TRuepoint series series are robust, high-capacity digital microwave microwave radios for the North America wirele w ireless ss transmiss transmission ion market. They deliver bro broad ad network flexibility and path reliability. Supported TRuepoint devices include: l TRuepoint TRuepoint 4000 l TRuepoint TRuepoint 4040 l TRuepoint TRuepoint 5000 l TRuepoint TRuepoint 6400 l TRuepoint TRuepoint 6500 How ProVision Supports TRuepoint This table lists TRuepoi TRuepoint nt management management support functions. Function Area Deploy and Discover Information TRuepoint TRue point Device Deployment on page 138 TRuepoi TR uepoint nt 6500 Device Deployment Deployment on page pa ge 142 Network Auto-Discovery for Devices on page 148 Linking Procedures on page 167 Discovering and Verifying Links on page 167 Configure and Manage Viewing Viewi ng Configuratio Configuration n for for Devic Devices es on on page 194 Configuration Profiles for Bulk Configuration on page 201 Manually Discovering TRuepoint 6500 Configuration on page 162 Manually Resynchronize Resynchronize Alarms on page 308 Customizing Event Names Names or Severity Levels on page 310 View Devices Equipment Equipme nt Views on page 73 Collect Data Perf Pe rfor ormance mance Data Collec Collection tion on page 1 Reports RF Network Health Repor Reports ts on page 474 Inventor Inve ntory y Re Reports ports on page 4 58 Manage Device Software Loading/Activating ng New Software and Licenses on page Loading/Activati 221 Backup and Restore Restore Device Configuration Backup and Restore on page 240 614-330055-001 DECEMBER 2015 29 CHAPT CH APTER ER 2. DEVICE SUPPORT SUPPORT IN PROVISION NOTE: For TRuepoint 4040 v2 and 5000 devices with V2 V2 controllers , an additional ProVision function enables you to apply SNMPv3 privacy/ encryption. encryption. To do this this using the algorithm algorithm types of TDES, AES128, or, for US customers only, AES192 and AES256, your ProVision system requires: * A specific ProVision feature license. * A Java cryptography extension (JCE unlimited strength ju jurisdiction risdiction policy file/s) from Sun Microsystems. Contact Con tact your Aviat Networ ks r epresentative epresentative to o btai btain n this this l icense and this extension. 30 AVIAT NETWORKS PROVISION USER MANUAL Constellation Device Support What Is Constellation? Constellation is a digital microwave Constellation microwave radio for the North North Amer America ica wirele wireless ss transmission transmission market. It features an all-indoor architecture designed for mid- to high-capacity applications. Constellation enables Constellation enables simplified capacity upgrades—fr upgrades—from om 4 xDS1 to 4xDS3 or 1xOC-3— and easy maintenance without tower-mounted equipment. It offers a rich set of standard and optional features, features, including super sup erior ior transmission characteristics. characteristics. How ProVision Supports Constellation This table lists unique Constellation management support functions. Function Area Deploy and Discover Information Constellation Constellatio n Devic Devicee Deplo Deployment yment on page 124 Network Auto-Discovery for Devices on page 148 Configure and Manage Viewing Viewi ng Configuratio Configuration n for for Devic Devices es on on page 194 Configuration Profiles for Bulk Configuration on page 201 Constellation Diagnostic Controls on page 447 Manually Re Resynchro synchronize nize Alarms on page 308 Customizing Event Names Names or Severity Levels on page 310 View Devices Equipment Equipme nt Views on pa page ge 73 Reports RF Ne Network twork Health Re Reports ports on page 474 Inventory Reports on page page 458 Backup and Restore Restore Device Configuration Backu Backup p and Restore on page 240 Configuration Backup and Restoration on page 1 614-330055-001 DECEMBER 2015 31 CHAPT CH APTER ER 2. DEVICE SUPPORT SUPPORT IN PROVISION Generic Device Support What Are Generic Devices? Generic devices can be SNMP or IP based, non-Aviat Networks devices. This allows you to deploy required devices, either as SNMP or IP devices, provided they are SNMP/IP compliant. ProVision also presence polls them, using either an SNMP or an ICMP ping. The generic devices are categorized in ProVision as: l Symbol l Generic l Multiplexer l Router l Switch l l Microwave Microwave Radio Site Manager l Base Station l Timing System l Server l Firewall l Air Condit Conditioner ioner How ProVision Supports Generic Devices Most ProVision generic device support is for Administrator level users and is described in the ProVision Installation and Administration Manual. Standard-level users can : l Deploy Generic Generic Devices - Generic Device Deployment on page 128 l View Generic Generic Devices - Interface Views on page 78 l View and Manage Gener Generic ic Device Device Events Events -Event -Event Browser, Browser, Event Notification, Notification, About Scor Scorebo eboard ard Group Sce Scenarios narios,, NBI Event Management. Management. NOTE: Aviat Ne N e tworks provides consulting services for Generic Device int integration. egration. Please c ontact your Aviat Networks s ales and support support staff for more information. 32 AVIAT NETWORKS PROVISION USER MANUAL Additional Device Support This section is a re refe fere rence nce for othe otherr device types that have speci sp ecific fic support instructions instructions in ProVision: l Cisco l DART l DXR l MegaStar l Symmetricom l TNet l XP4 NOTE: All of these instructions instructions assume that you are experienced with the devices. devices. Refer to the the sourc e documentation documentation for the devices as required. NOTE: Each of these device types must be configured configured to send SNMP traps to the IP address of the ProVision server. Cisco Device Support ProVision installation of Cisco devices requires an extra step, documented here: l Cisco Deployment Deployment on on page 123 123 DART Device Support ProVision provides specific support for DART devices: l DART Diagno Diagnostics stics Controls on page 452 l Activating and Deactivating DART DART Tributar Tributary y Loopbacks Loopbacks DXR Device Device Support ProVision provides specific support for DXR devices: l DXR 200 and DXR SMA Device Deploym Deployment ent on page 120 l Manually Discover Discovering ing DXR DXR 700 Radios Radios on page 162 l Managing SMA SMA and DXR DXR Device Devicess on page 165 614-330055-001 DECEMBER 2015 33 CHAPT CH APTER ER 2. DEVICE SUPPORT SUPPORT IN PROVISION MegaStar Device Support For MegaStar, ProVision provides: l Megastar Me gastar Diagnostic Diagnostic Controls Controls on page 455 Symmetricom Device Support ProVision installation of Symmetricom devices requires an extra step, documented here: l Symmetricom Symmetr icom TP1x00 TP1x00 Deployment Deployment on page 135 l Symmetricom TP5000 TP5000 Deployment on page 137 TNet Device Support ProVision provides specific support su pport for TNET devices: l TNet TN et Device Device Deployme Deployment nt on page 144 l Using the TNet TNet Proxy Proxy Viewe Viewerr on page 220 220 l Viewing/Changing Viewi ng/Changing TNet TNet Proxy Proxy C onf onfiguratio igurations ns on page 218 l TNet TN et Web Web Craft Tool Tool and Diagnostics on page 424 XP4 Device Support ProVision provides specific specific support for XP4 devices: l Additional Devic Devicee Sup Support port on page 33 l Additional Device Device Suppor Supportt on on page 33 l Activating and Deactivating an XP4 XP4 Tributary Tributary Loopback Loopback on page 437 l Activating and Deactivating Deactivating an XP4 Local Local Loopback Loopback on on page 441 l l Viewing/Changing XP4 Viewing/Changing XP4 Protecti Protection on Settings Settings on page 443 Resetting Re setting an XP4 XP4 Radio Device Device on on page 445 34 AVIAT NETWORKS Chapter 3. Navigating ProVision This section describes the ProVision user interface and how to start using ProVision, including: l The ProVision ProVision User Interf Interface ace on page 44 l Right-Click Right-Clic k Menus Menus on on page 53 53 l View Tabs: Tabs: Physical, Physical, Logical, Circuits, Circuits, VLAN, EOAM on on page 55 l Map Viewer Viewer on page 63 l Detailed Detaile d Device Views on on page 71 l Event Browse Browserr on on page 80 80 l Using Search Search to Search Search All ProVisio ProVision n Data on page 83 l Searching Sear ching the Tree Tree Viewers Viewers on page 87 l l Icons Infor Icons Information mation and Usage on page 89 Integrating Windows Applications with ProVision on page 95 NOTE: This This s ection assumes that ProVision has has been installed, and the devices ar e deployed and being managed from ProVision. Starting a User Session The ProVision Client Software on your PC enables you to start and run a ProVision user session. ProVision allows multiple simultaneous user sessions. Changes made by one user are immediately reflected in the ProVision database. However, no two users can change the same data at the same time, because when changes are being made to an object, the system locks that object. After you enter your login details and these details are v erified, erified, your PC connects connects to the ProVision Pro Vision serve server. r. The ProVision ProVision User Inter Interface face displays, with the lat est details, alarms and events about the network and its performance. Your user name, and the name of the ProVision server to which you are connected, are displayed at the bottom of the User Interface window. NOTE: Set your display res olution olution to a minimum minimum of 1024 x 768. Thi Thiss ensures that all th the e c omponents omponents in the ProVision windows windows are visible on your display. 614-330055-001 DECEMBER 2015 35 CHAPT CH APTER ER 3. NAVIGATING PROVISION Procedure 1. From the desktop, double-click the ProVision Client shortcut. (In Windows 8 or 8.1, swipe in from the right edge of the screen, or, using a mouse, point to the upperright corner corner of the scree screen, n, move the mouse pointer down to open the function sidebar, and then tap Search. From here, locate and click on the ProVision Client icon.) 2. The ProVision Login window displays. 3. Type your user name and password in the fields provided. For example: l User: LeslieSmith l Password: passw or ord d 4. Enter the name of your Pr ProVisio oVision n Serve Serverr and sele select ct Login. The ProVision Loading window displays displ ays.. When ProVision is loaded, the ProVision Loading Load ing window closes, and the ProVision User Interface displays. Exceptions If you type in an unknown user name or password,or the sever is not available, the following error error message displays. disp lays. 36 AVIAT NETWORKS PROVISION USER MANUAL Select OK and retype your user name and password. CAUTION: Aft After er three three failed failed attempt attemptss with an incorrect incorrect login login na name me or password, th the e Login Login di dialog alog box closes and access to ProVi ProVision sion is deni denied. ed. At this this poin pointt you must contact your Network Administrator. Administrator. If the error error message displays again, contact your Ne Network twork Administrator. Administrator. Exiting a User Session ProVision user sessions continue to run until you exit the session or shut down your workstation. Procedure 1. Select the X in the upper right corner of the user interface window. A message displays prompting you to confirm your exit request. 2. To close your ProVision user session, select Yes. Changing Your Password Each user requires a user name and password to log into ProVision.The system administrator sets up your first user password. You can change your password at any time. ProVision passwords must have between 6 and 32 alphanumeric characters. Passwords are case sensitive. NOTE: If you type an invalid invalid passwor d in any any of the passwor d boxes, an error O K. message displays. To close the message box and try again, select 614-330055-001 DECEMBER 2015 37 CHAPT CH APTER ER 3. NAVIGATING PROVISION Procedure 1. Select Administration > Change User Details. The Change User Details window displays for your user name. 2. Select Change Password. The Change Password dialog box displays. 3. In the New Password field, type your new password. 4. Re-type your new password in the Confirm New Password field. Select OK O K. 5. To accept your password changes on the Change User Details window, select OK. 6. Use your new password the next time you log in to ProVision. Entering Your Contact Details ProVision provides a location to store your email and contact details. You can enter new contact details and change existing details, such as an address and phone number. Procedure 1. Select Administration > Change User Details. The Change User Details window, with your user name, displays disp lays.. 38 AVIAT NETWORKS PROVISION USER MANUAL 2. In the Email Address field, enter your email address. 3. Select in the Contact Details frame and type in your details. 4. To accept your changes and close the window, select OK O K. 5. Changing Your Password on page 37 Viewing Your ProVision License Details The ProVision license details can be viewed at any time. License details display in the status bar, for example: There are two types of license, an evaluation license that expires a specified number of days after installation and a permanent license that has no expiry date. Procedure 1. Select Help > License Details. The License Detail window displays, for example: 2. To close the window, select OK. 614-330055-001 DECEMBER 2015 39 CHAPT CH APTER ER 3. NAVIGATING PROVISION Viewing Customer Support Contact Details If you need to contact Aviat Networks Customer Support, the contact information is available from from the ProVision ProVision Help menu. Procedure 1. Select Help > Customer Support. The Customer Support Information window displays. 2. To view the contact details of your region’s Aviat Networks Customer Support center, select the Technical Assistance tab. 3. To close the window, select OK. Viewing ProVision’s Version Number In certain situations, you need need to know the version numbe numberr of y our Pro ProVision Vision software software;; for example, when deciding whether to upgrade or reporting a fault. Procedure 1. Select Help > About ProVision. The About ProVision window displays, including the version number. 40 AVIAT NETWORKS PROVISION USER MANUAL 2. To close the window, select OK. Using the Online Help The online help module you receive with ProVisionprovides complete documentation of ProVision, including: User Manual l l Installation and Administration Administration Manual Manual l Alarms l Technical Technical Support Information Information The online help displays using the default Web browser on the PC. The online help user interface is shown below: Figure 3-1. ProVision Online Online Help 614-330055-001 DECEMBER 2015 41 CHAPT CH APTER ER 3. NAVIGATING PROVISION Each topic in the online help has its location listed at the top of the page. This helps you to identify related topic areas. If you prefer to have printed versions of the documentation, print them from the PDF provided on the ProVision Installation CD (P/N 614-500502-002). You can also print individual help pages from the Web Browser view. Procedure NOTE: The ProVision online help displays in your default HTML browser . The ProVision help is included included with the the ProVision software. You do not need a link to the Internet to use the ProVision help and its features. 1. From the menu bar, select Help > Help Topics. The ProVision online help window displays. 2. To navigate the online help, use the tabs in the left navigation panel: l Contents - Enables you to view the information headings organized by subject. Expand the top-level headings to view the subtopics. l Index - The index is used to find important terms and display the related topic. l Search - Enables you to search for any character string in the help set. l Glossary - View definitions in the Glossary listing. l Favorites - Bookmark topics you refer to often in Favorites. 3. The search results list all the topics that contain the search string, with a % rank showing how well the topic matches the search. All occurrences of the search string are highlighted in the help topic. 42 AVIAT NETWORKS PROVISION USER MANUAL 614-330055-001 DECEMBER 2015 43 CHAPT CH APTER ER 3. NAVIGATING PROVISION The ProVision User Interface From the main ProVision interface, you can perform all the required functions to manage network responsibilities, quickly and effectively. Figure 3-2. Main User Interface Interface The functions of the main user interface are described in the following sections: l Customizing the User User Interf Interface ace on page 44 Menu Me nu Bar on page 45 l Main Too Tooll Bar on on page 51 51 l View Tabs: Tabs: Physical, Logical, Logical, Circuits, VLAN, VLAN, EOAM on on page 55 l Map Viewer Viewer on page 63 l Event Browser on page 80 l Using Sear Search ch to Search All ProVision Data on page 83 l Searching Sear ching the Tree Tree Viewers Viewers on page 87 l Customizing the User Interface This table lists the ways you can customize the user interface. Table 3-1. Cu Customizi stomizing ng th the e Main User Interface 44 AVIAT NETWORKS PROVISION USER MANUAL Required R esult Action Main User Interface To minimize, maximize, or close the interface window Selectt the req uired butto Selec button n from the butto buttons ns loc located ated in the upper right corner. To res resize ize the the interfa interface ce windo window w Clic Click ka and nd dra drag g an any y of of th thee outside outside ed edges ges of tthe he int intererface window. Physical Viewer To res resize ize the Phys Physica icall Viewer Clic Click k and drag the vertica verticall spl split it bar. To hi hide de th thee Physi hysiccal Viewe Viewerr Selec Selectt the the X the Physical Viewer toolbar. To sh sho ow the the Ph Phys ysic ical al Viewer Viewer In th thee Wind Windo ow men menu, u, sele selecct Physical. Map Viewer To res resize ize the the Map Map Viewer pa panel nel Clic Click ka and nd drag drag th thee vertica verticall sp split lit ba bar. r. To hi de de the Map Vi ew ewe r S eelle ct ct the X on the Map toolbar. To sho how w the Map Vi View ewer er In the the Wind Windo ow me menu nu,, sel elec ectt Map Map.. To add add a bac backgr gro oun und d Sel Selec ectt Map Map Prope ropert rties ies on the the Ma Map p too toolba barr to ad add da JPG background for the map. You can add different JPG backgrounds for Physical and Flat Map views of the network. Event Browser To res resize ize the Event Event Browse Browserr Clic Click k and drag the horiz horizon ontal tal spl split it bar. To hid idee the Event ent Bro rows wser er Sel Selec ectt Hide Hide.. To show how the the Even Eventt Bro Browser wser In the the Win Windo dow w men menu, u, se sellect ect Events Events.. To chang changee displayed Event va values lues In the Event Brows Browser er too toolbar, lbar, sselec electt Browser Options to edi t brows browser er opt options ions.. Menu Bar The menu bar contains menu items and pull-down options used to access common, non-device specific functions such as: l Event Browsers l Security Security Management l Re Reportin porting g and Data Collection Collection l Scheduling configuration operations l Help System NOTE: The menu bar items displayed on the the main user interface may vary depending on your user access profile. The figure below shows the ProVision menu bar with all the menu options displayed. The table below contains descriptions of the menu items and associated pull-down options available from the menu bar. 614-330055-001 DECEMBER 2015 CHAPT CH APTER ER 3. NAVIGATING PROVISION The ProVision ProVision menu system include includess context-sensi context-sensitive tive right-click menus. Access Access the right-click menus by right-clicking on an object within the Map Viewer or Physical Viewer.. The right-click Viewer right -click menus provide device specific functionality. functiona lity. For m more ore information, see Right-Click Menus on page 53 53.. Table 3-2. Menu Bar Items And And Pull-Down Pull-Down Option Optionss Menu Item Function File Topology Import - Enables you to import a network topology in XML file format. The Tree and Map Viewers are automatically populated with objects, that is, containers and devices. Typically used when migrating a previous version of ProVision to ProVision. For more information see the ProVision Installation and Administration Guide,, Migrating Topology. Guide Topology Export - Enables you to export network objects and hierarchy to an XML file. The network topology can be exported as a backup, for support diagnostic purposes, purposes, for 3rd party north bound integration and for future migrating to a la later ter versio version n of ProVis ProVision. ion. Task Manager - Enables you to review the status of a current task being run by ProVision. Exit - Enables you to close your ProVision user session. See Exiting a User Session on page 37 Search Search - Enables you to find specific objects. The search process is done on the data held in ProVision, not on the devices in the network. See Using Search to Search All ProVision Data on page 83 . You can also select the sear searcch ico icon on th thee too tooll bar bar.. 45 46 AVIAT NETWORKS PROVISION USER MANUAL Menu Item Function Fault Device Maintenance View the sleep status of all devi ces. Event Browser > Security Log View the ProVision S ecurity Log. Event Browser > New Events Brows Browser er Enables you to see saved Event Browser views, select the view you want to open, or create a new Events Browser. You can also use the add Event Browser View down arrow to display saved Event Browser views. icon, and the drop- Event Analyzer Enables you to view and run the Event Analyzer. Scoreboard Scoreboar d Groups New Scoreboa Scoreboard rd Groups Enables Enabl es you to view saved Scorebo Scoreboard ard gro groups, ups, and select select a Sco Scoreboard reboard group to open, or add a new Scoreboard group. You can also use the add Scoreboard group arrow to display saved Scoreboard groups. icon, and the drop-do drop-down wn For more information on Scoreboard Groups, see Scoreboard Group Scenarios on page 367 . Event Pre-Filter Enables you to view, add, and remove pre-filter events. Events that match the pre-filter pre-fil ter events are blo block cked ed before reaching the syst system. em. Filt Filtering ering events at input reduces the number of events being fully processed and increases performance. For For more i nfo nformatio rmation n on the Event Pre-fil Pre-filters, ters, see Event Notification on page 341. Event Notifications Enables you to set up ProVision to notify you via email, audio, or pop-ups whenever selected events occ occur ur within the network. You can also instruct ProVision to run a shell script for a batch file whenever selected events occur. For more information see Event Notification on page 341. Notifications Preferences Preferences Enables you to set up the IP address of your mail server and other required settings for E-mail notification. For more information see Set the Server Notification Preferences on page 342. Client Notification Dialogue View the Event Notificatio Notification n dialogue. 614-330055-001 DECEMBER 2015 CHAPT CH APTER ER 3. NAVIGATING PROVISION Menu Item Function Con Configu figur ration tion IP Addres ess s Enables you to view and change IP information assigned to devices on the network. License Licen se Loading Enabl Enables esthan you to load ad licenses to isetting ndividual Ecl Eclipse ipseorradios radios, , to provide a capa capacity city greater thelo default factory of 10xE1 16xDS1. For more information, see Eclipse and CTR Node Licenses on page 237 . Configuration Profiles Enables you to apply settings to multiple radios. For more information, see Configuration Profiles for Bulk Configuration on page 201. ProVisioning Enables you to run Provisioning functions. Select Circuit, VLAN, EOAM, or ERP. Software Loading Lists the container and current software version of each Eclipse radio in the network. For more information, see Loading/Activating New Software and Licenses Licenses on page 221 . Software Loading Preferences Enables you to update the software of the Eclipse radios. The functions include Software Software Register and Server. For mor moree information, see Loading/Activating New Software and Licenses on page 221. Network Auto-Discovery Set up specific devices to be auto-discovered. Circuit Collection Preferences Set up circuit collection collection time preferences. Global Circuit Trace Enables you to run a global circuit trace. Edit User Defined Icons Enables editing of user defined icons, see About User Defined Icons on page 91 47 48 AVIAT NETWORKS PROVISION USER MANUAL Menu Item Function R epo rts Help Desk Creates a report for you to send to the Help Desk when you need support. Inventory Enables you to run an Inventory report for a selected radio. Capacity Enables you to run a Capacity report for a selected radio. Network Health Enables you to run a Network Health Report. Select from the available NHR options. Security Status Collects security data for one or more Eclipse devices. Clock Sync Enables you to view clock synchronization status and values for clock sync supported devices. Custom Reports Enables users to create customizable reports for devices. Scheduled Reports Provides ability to schedule reports to run on a regular basis. Server Reports Enables you to view generated Server reports. Link Reports Enables you to run a Link Report. Perfor formance Data Co Colllection tionn n Enables you to view and change performance data collection criteria, daily and/or every 15 minutes, for each radio in the network. By default, when a radio is deplo deployed, yed, data coll collectio ection n is set to daily. Fo Forr more i nfo nformatio rmation, n, see Data Collection on page 388 . Thresholds Set data collection thresholds for devices in the network. Ethernet Bandwidth View Ethernet Bandwidth use for Eclipse devices. Clock Sync Performance Metrics Enables setting setti ng and viewing of Clock Quality threshold and Clock Stability threshold. 614-330055-001 DECEMBER 2015 CHAPT CH APTER ER 3. NAVIGATING PROVISION Menu Item Function Administrati Admin istration on User Accounts This is an administrative function. It enables you to create, delete, and view all user accounts. For more information see Access Control. Change User Details Enables you to change your contact details and password. For more information see Entering Your Contact Details on page 38. Session Manager Enables an administrator to manage user access to ProVision sessions. Database Purge Enables you to set the purge criteria and the time of day that the purge process occurs. See Access Control. Database Backup Manual Backup Database Backup Scheduled Backup Enables you to enter a backup description and to indicate what the system includes in the backup. backup. See Datab Database ase and Server Management . Backup Preferences Enables you to set and save back ba ckup up preferences. preferences. See Set Backup Preferences. Server Redundancy Enablee back Enabl backup up server redundancy redundancy.. See Standby Server Configuration Prerequisites. Device Security Accounts This is an administrative function. For radio types that have user name and password security such as the XP4 rad radio, io, this function enables you to enter these details into ProVision. See Access Control. Eclipse Portal Locking Locks write access to Portal from ProVision. See Locking Eclipse Portal Write Access fro from m ProVision. Generic Device Management This is an administrative function. For generic devices entered by the user, this function function enabl enables es you to enter the device config configuratio uration n detail detailss into Pro ProViVision. See Gen G eneric eric Device Management. Email Server Configuration Configuration In this screen, screen, you note the IP address of your email server, used when ProVision sends an email message about an event. See Set the Server Notification Preferences on page 342. RADIUS Server Configuration C onfiguration Allows admini Allows administrato stratorr to enable and con configure figure ProVision RADIUS server authentication. See Enabl Enabling ing a RADIUS Server. 49 50 AVIAT NETWORKS PROVISION USER MANUAL Menu Item Function Window Click on an item to view or hide that window in the Pro ProVision Vision screen screen displa display. y. - Physical - Logical - Circuits - VLAN - EOAM - Map - Events - Reset Layout = Resets the Window layout back to the Default layout. Help Help Topics Enables Enabl es you to acc access ess the Pro ProVision Vision User Guide online. online. License Lic ense Details Displays your ProVision license details. Customer Support This window has tabs for the three Customer Support centers and their contact details. About ProVis ProVision ion Displays the version of ProVision that is installed. Main Tool Bar The main Tool Bar and its buttons are a fast way to access frequently used ProVision functions. The main Tool Bar is shown below. The Physical Viewer, Viewer, Map Viewe Viewer, r, Ev ent Browser, Browser, and other scree screen n are areas as have their own tool bars. Table 3-3. Tool Bar Icons Icon Name Definition Search Enabl Enables es you to rapidly find spec specific ific object objects. s. See The ProVision User Interface on page 44. Task Manager Lists all tasks, completed or otherwise, that have been executed in ProVision. Pop-up windows provided additional information and functions when executing tasks. See Loading/Activating New Software and Licenses on page 221. Server Reports Saves and retrieves reports from a single radio or from multiple radios. For more information information see View / Save / Delete Server Reports on page 469 . 614-330055-001 DECEMBER 2015 51 CHAPT CH APTER ER 3. NAVIGATING PROVISION Icon Name Definition Global C ir ir-- Runs a global circuit trace on all circuits in the system. See See cuit Trace "Running the Circuit Trace". Event Enables you to open a new Event Browser and select saved Browser Scoreboard Groups Event Browser views. See Event Browser on page 80. Enables you to add a new Scoreboard group and view saved Scoreboard groups. See Scoreboard Group Scenarios on page 367. Event Ana- Opens the Event Analyzer. See Event Analyzer on page 338. lyzer 52 AVIAT NETWORKS PROVISION USER MANUAL Right-Click Menus Pr ProVisio oVision n right-click right-click menus provide access access to the options available for the sele selected cted object, for example a region, an Eclipse radio, or an event. You can access right-click menus from the objects displayed in the Tree Viewer, the Map Viewer, and from events listed in the Event Browser. The options presented in a given right-click menu depend on the context of the object selected. To display a right-click menu: 1. Place the cursor over the object or event entry. 2. Right-click using the right-click button on the mouse. In the ProVision screen, a right-click menu displays. The menu contains the function options that are available with the selected object or event. 3. Drag the cursor to the desired menu option and left-click to select. The window or dialog box displays. Right-click menus are available for all items in the Tree Viewer and Map Viewers, including: l Containers l Root levels l NBI options l Devices l Device components l Links l Logical links They are also available for all items in the Logical Container, including: l Logical containers Circuits l Events l Radio Right-Click Menus Different Differ ent radio types have d diff iffer erent ent right-click right-click menu options, based on the available functions for the radio. An example of an individual radio right-click menu is shown below. 614-330055-001 DECEMBER 2015 53 CHAPT CH APTER ER 3. NAVIGATING PROVISION Note that items that are active for a radio are checked. In the example above, the radio is Managed Managed and is having 15-minute Radio Perfor Performance mance Data recor recorded. ded. When a link is established between between two radios, the right-click menu includes two add addiitional options: l Remote([radio]] LINKn) - Displays the options for the remote radio that the Remote([radio selected radio is connected; where “radio” is the name of the remote radio and “n” is the remote radio radio’s ’s slot numbe numberr where the remote link hardware is installed. l Link - Displays the options for the link that connects the selected radio and the remote radio. NOTE: You can select multiple radios/devices and righ right-click, t-click, and you will view a generic r ight-click ight-click menu. This menu includes includes only the functionss that are s hared amongst all the devices. tion 54 AVIAT NETWORKS PROVISION USER MANUAL View Tabs: Physical, Logical, Circuits, VLAN, EOAM There are several tabs that provide tree views of ProVision devices: l Physical - Display s the complete complete “tree “tree view” of the entire entire ne network twork.. l Logical Logical - Displays logi logical cal container containers. s. l Circuits - Displays circuits. circuits. l VLAN - D Displays isplays VLANs. VLANs. l EOAM - Displays Ether Ethernet net OAM. OAM. The topics covered covered in this section section include: l Physical Viewer Viewer and Icons Icons on page 55 55 Logical Tree Tree Viewer on page 61 l Circuits Viewer Viewer Tab on on page 61 l l For infor information mation about the VLAN VLAN and EOAM tabs, see Viewing Discovered VLANs on page 245 and Viewing Discovere Discovered d EOAM MAs on page 265 Physical Physi cal Viewer and Icons In the Physical View option, the entire radio network is represented as a tree of containers and devi devices. ces. Each container (for example, a region) is represented as a parent, with all the devices positioned underneath, as its children. NOTE: A container container is a collec tion of related objects arr anged in a hierarchical r elationship. elationship. Objects c an have parents and children. 614-330055-001 DECEMBER 2015 55 CHAPT CH APTER ER 3. NAVIGATING PROVISION Figure 3-3. Tree Viewer - Physical Viewer Within the Physical pane, the regions, regions, sites, racks, and devices are llisted isted in alph alphabetical abetical order. Context-sensitive right-click Context-sensitive right-click menus are supported within this view. For more informinform53.. ation, see Right-Click Menus on page 53 Reparent Rep arent Obje Objects cts You can reparent reparent objects objects within the Tree Tree v iewer in the Physical pane. To do this, left-click on the mouse to select the objects and press the Ctrl key. Keeping the Ctrl key pressed, move the objects to the new parent container. Do not release the Ctrl key or the mouse at any point during this process. Navigating the Physical Viewer Select the + next to a parent object (container or Eclipse radio) to expand the tree for that object. Select the - next to a parent object to contract the tree for that object. Double-clicking an object with the left mouse button expands or contracts contracts the hierarchy hierarchy tree for that object. Single-clicking an object with the left mouse button: l Highlights the selected selected ob objec jectt in the Physical Viewer and l Displays the map for the ob objec jectt in the Map Viewer. Viewer. Single-clicking an object with the right mouse button: l Displays a right-click right-click menu menu listing the options for for that object object and l Opens the map for the objec objectt in the Map Viewer. Viewer. Service Ser vice and Status Statu s Icons When devices are in service service,, they display disp lay without any add additional itional icons. When devices are out of sservice ervice,, they display disp lay with this icon beside them: t hem: 56 AVIAT NETWORKS PROVISION USER MANUAL An example of t he Physical Frame with out of service s ervice devices is shown below: below: Items with Clock Synchronization display with the Clock Sync icon beside them in the map: - Device Device is cloc clock k sy nce nced d - Clock source is external Items with RAC LL and RAC LL DDR enabled display with an R or IF icon beside them in the Tree Viewer and on their links in the Map: Items that are Out of Service display with an icon beside them in the Tree Viewer or the Map: Physical Frame Object Icons Within the Physical frame, containers a and nd devices are represente represented d by icons. The t able below below lists the containers that can be used us ed in ProVision. Table 3-4. Con Contai tainers ners used in ProVision ProVision Co Con nta taiiner Icon Note otes ProVision Manager The ProVision Manager generates ProVision related events, for examplee trial licens exampl licensee expiry messag messages, es, and prov provides ides access access to the security log, license and customer support details. Ro Root ot The The Ro Root ot and ProV ProVisio ision n Manag Manager er icons icons are aut automa omatic tical ally ly displayed in the Physical Viewer. Region Reg ion A regio region n is a gro grouping uping of devic devices es and and/or /or sites sites tha thatt is typ typica icall lly y geo geo-graphically based. 614-330055-001 DECEMBER 2015 CHAPT CH APTER ER 3. NAVIGATING PROVISION Co Con nta taiiner Icon Note otes Site Site A site site is a locat atio ion n wher wheree a de devic vicee or de devic vices es are are sto stored. red. Rac ack k A rac rack rep repres resen ents ts a phy physic sical al sto storage rage uni unitt in wh whic ich h a num number ber of devices can be stored. At a large site, there may be several physical racks installed. The table below lists the SNMP devices that can be deployed in ProVision. Table 3-5. SNM SNMP P Devices Devices Device Icon Accedian EtherNID, Accedian EtherNODE ADR 155C: Aviat Network Networkss ADR, ADR 2500: SAGEM ADR, an add-on to the Altium. , , and Altium, Altium MX, and Altium MX 2+0 Aurora Constellation Control Alarm Unit Cisco Devices: Devices: 2400 2400,, 2 941, 3400, ASR 903 CTR 8500, CTR 8440 and and and and DART and DART (remote management) DVA and DVM, DVM-XT DXR 100 and DXR100 (protected) Symmetricom TP1x00+ TP1100 and TP500 and DXR 700 and DXR 700 (protected): DXR 700 radios are “discovered”/visible “disco vered”/visible i n the Pro ProVision Vision when the connec connected ted DXR SMA is deployed. 57 58 AVIAT NETWORKS PROVISION USER MANUAL Device Icon and Eclipse INU Node and Eclipse INUe Node (includes IDU 600) The INU has an NCC, 1 fan and 4 slots for plug-ins. The INUe has an NCC, 2 fans and 10 slots for plug-ins. An Eclipse Node can have the following following component components: s: NCC Fan RAC (standard and RAC 4X) ODU DAC NPC Links (standard, protected, and ring protected) These co These componen mponents ts are displa displayed yed in the Physica Physicall Vie wer using the following icons: Eclipse IDU Terminal: the Eclipse Terminal has a fixed layout; ancillary parts are displayed as plug-ins. E-Band E-Link 1000EXR, 1000LR 1000LR Memotec CX-U EMS Proxy and Network Elements LE3000, LE3200, WinLink 1000, Radwin 2000 MegaStar 1+ and M+N and MicroStar I, I (Protected), II, and II Tellabs 8605, 8609, 8611, 8630, 8668 TRuepoint 6400, TRuepoint 5000, TRuepoint 4040, and TRuepoint 4000 and TRuepoint 6500 and TRuepoint 6500 double terminal Velox WTM 3100, 32 00, and 3300 WTM 6000 and WTM 6000 Repeater and XP4 (remote (remote manag management) ement) 16xE 16xE1/E3/DS3 1/E3/DS3 and XP4 16xE1/E3/DS3 (remote management, protected) and XP4 16xE1/E3/DS3 16xE1/E3/DS3 and XP4 16xE1 16xE1/E3/DS3 /E3/DS3 (pro (protect tected) ed) 614-330055-001 DECEMBER 2015 CHAPT CH APTER ER 3. NAVIGATING PROVISION Device Icon XP4 2/4/8x (remote management) and XP4 2/4/8x (remote management, protected) and XP4 2/4/8x and XP4 2/4/8x (protected) and User Defined - based on user provided graphics - see About User Defined Icons Table 3-6. TNet Device Device Icons Device Icon Classic II and LC Series and LC Series (pro (protect tected) ed) M Fiber and and M Series and M Series (pro (protect tected) ed) QUANTUM and QUANTU QUANTUM M (protec (protected) ted) SPECTRUM SPECT RUM I and SPECTRUM II and SPECTRUM II (protected) (protected) TNet Proxy and W Series and W Series (pro (protect tected) ed) Table 3-7. Gen G eneric eric SNMP Device Device Icons Device Icons The Generic SNMP device icons represents SNMP enabled, non-Aviat Networks devices. You can manage these devices and ProVision also presence polls them. From left to right, these devices are: Symbol Generic Multiplexer Router Switch Microwave Radio Site Mana Manager ger Base Station Timing System Server Firewall Air Conditioner Instructions for adding containers and deploying devices are described in Deploying Devices on page 106. 106 . 59 60 AVIAT NETWORKS PROVISION USER MANUAL Related Topics: l View Tabs: Tabs: Physical, Logical, Logical, Circuits, VLAN, VLAN, EOAM on on page 55 l Searching Sear ching the Tree Tree Viewers Viewers on page 87 l Logical Tree Tree Viewer on page 61 Logical Tree Viewer The Logical tree viewer displays the logical containers created in ProVision, and the devicess and cir device circuits cuits grouped under each logical logical container. container. This tre treee view supports severity propagation, with the logical container taking on the highest severity of its devices. Configure your required logical containers. Then, add devices to them. You might, for example, create a logical container to include all backbone radios or all the radios within the C entr entral al Business District. For more info inform rmation ation see Logical Containers on page 359 359.. Figure 3-4. Physical Viewer - Logical Containers Tab NOTE: By default, the Logical Containers tab is not populated at installation. Circuits Viewer Tab The Circuits tab lists circuit bundles within the network that are made up of one or more Eclipse radios. Circuits with non-Eclipse radios do not appear in the Circuits tab. Like the Logical Container tab, this view supports severity propagation, with the circuit bundle taking on the highest severity of it s devices. After a Circuit Trace command is executed, ProVision lists l ists all Eclipse Eclips e radio rad io circuits. For more information, see Circuit Management on page 177 177.. 614-330055-001 DECEMBER 2015 CHAPT CH APTER ER 3. NAVIGATING PROVISION Figure 3-5. Physical Viewer - Circuits Tab NOTE: By default, the Circuits tab is not populated at installation. 61 62 AVIAT NETWORKS PROVISION USER MANUAL Map Viewer The Map Viewer provides two different views of the network: l Physical Map Map View on page 63 l Flat Map View View on page 64 The following following object object types are supporte supported d in t he Map Viewer; Viewer; l Region l Site l Rack l Device objects objects l RF links l Service Service links. Right-click an object in the Map Viewer to see the right-click menu, which lists the options available for that object. Additional Addit ional information on the Map Viewer is in the following sections: l Map Tools Tools on page 64 l Map Backgro Backgrounds unds on page 66 l Submaps Sub maps on page 71 Physical Map View The Physical Map View shows an overview of the network. This view displays only the first level of children children under the parent object selected. To open this view, click on the Physical Map icon on the Map Toolbar: 614-330055-001 DECEMBER 2015 63 CHAPT CH APTER ER 3. NAVIGATING PROVISION Figure 3-6. Map View View When an Eclips Eclipsee Node is selected selected in the Physical Viewer, Viewer, its chassis and components are displayed in the Map view. NOTE: The map help help,, map proper ties, zoom and padlock functions functions are described in Map Map T ools ools on pag e 6 4 . Flat Map View In the Flat Map view, only the network devices and links are displayed. This view enables you to change from a traditional hierarchal view showing regions, sites, and devices, to an all network object view. To open this view, click on the Flat Map icon in the Map Toolbar: This view is particularly helpful when managing events, because you can see the severity information for both ends of the links, for many radios. Flat map views can be displayed for any container (root, region, site, and service) within the Physical Viewer. For example, a flat map view selected at the root container displays all the network devices. A flat map view selected for a region or site displays all the network elements grouped under the container selec s elected. ted. This alternative view is very useful for a use who wants to maintain the logical structure of regions/sites and view the status of all network elements at a glance. Map Tools These are the functions in the ProVision Map toolbar. 64 AVIAT NETWORKS PROVISION USER MANUAL Map To ol Icon Use Physical Map Clic Click k this to view the Phy Physica sicall Map view. Flat Map Clic Click k this to view the Fl Flat at Map view. Navigate Up, Back, or Forwards Use these arrows to navigate to different maps in the network. Zoom to Fit Screen The Zoom Zoom to Fit Screen tool tool enabl enables es you to zo zoom om in and see all of your devices on the Map View at one time. This is particularly useful for large networks. To return to the standard view, click the Zoom to Fit tool again. Enable/Disable Map Zooming The map zoom tool enables you to zoom in/out of the Map Viewer. The map zoom tool functions are: - Single-click the zoom icon to enable the map zoom tool. - Left-click the zoom icon to zoom in on the map and objects displays in the Map Viewer. - Right-click the zoom icon to zoom out. - Single-click the zoom icon a second time to disable the map zoom tool. Locked and Unlocked By default the map padlock is locked. This means that objects cannot be moved in the Map Viewer. To move objects around in the Map Viewer, select the padlock icon. The icon changes to an unlocked padlock. Select the unlocked padlock, and the icon changes back to the locked state. The objects in the Map Viewer revert back to the default, locked locked state. For additional information see Moving Containers Flash for Unacknowledged Events and Devices in the Map Viewer on page 153 . The Flash tool can be set to flash/blink as a visual indicator that there are unacknowledged Events in this map. This flashes flashes for events of Minor, Warning, Major, and Critical severity. Map Mode Enables you to select the map view mode: Enables - Off - Displays standard Map View. - VLAN View - Displays VLAN data. - Clock Sync OAM View- Displays Clock Sync data. See Clock Synchronization View. Map Icon Size The Map Icon tool tool shrinks or enlarges device icons. This is useful when you are zooming. Auto-Arrange The Auto-Arrange tool tool automatical automatically ly orders the device icons in your map view. 614-330055-001 DECEMBER 2015 65 CHAPT CH APTER ER 3. NAVIGATING PROVISION Map To ol Icon Use Object Filter The map object filter tool tool enabl enables es you to searc search h for and select select specific map items. Properties The map propert properties ies tool tool enables you to add and cha change nge map backgrounds. For more information, see Map Backgrounds on page 66 . Print The map print tool tool enabl enables es you to print the content contentss of the map viewer. - Fit To Page prints the entire map view on a single page. - Visible Area prints only the area displayed on the map view. - Page Setup allows you to set up the print criteria for your printer. Help The map help, displa displayed yed at the top of the screen, screen, provides a desc provides description ription of the various links, device sta states tes and event management tasks that are displayed within the Map Viewer. Viewer. To display the map help, click the help button. The follo lowing wing poppop-up up window defines the various links and icons on the Map Viewer. Map Backgrounds You can add a backgro background und image for any obje object ct located in the Physica Physicall Map or Flat Fl at Map pane. When an object is selected, in the Physical pane, the imported image displays in the Map Viewer. Icons can then be placed on top of the background image. Typically, a background backgro und image is a geographical map, a floor pl plan, an, or some s ome form of schematic. s chematic. 66 AVIAT NETWORKS PROVISION USER MANUAL You can assign different different images to the Physical Physica l and Flat Map views. Use your favorite search search engi engine ne to find website websitess that provide maps fo forr countries, countries, regions, and cities that you can download and use in ProVision . Pr ProVisio oVision n supports t he following image formats for map backgro backgrounds: unds: l l jpg gif (GIF87 and GIF89a) GIF89a) NOTE: The map viewer viewer w indow indow size is 4096 X 3072 pixels. Use image editing edit ing software, such as PhotoShop, PhotoShop, to s ize the map image to this size. Procedure 1. Within the Physical Viewer, select the view type to which you want to add a map background, backgro und, the Physical or Flat Fl at map view. 2. Select the Map Properties ic icon on on the Map Viewe Viewerr. dow displays. The The Map Prope Properrtie tiess winwin- 3. Select the checkbox to enable Background Image selection. 4. Select the Map Object Filter button. The Map Selection window displays. 5. Browse to the location of the stored map files. 6. Select the required map file and select Open. 7. To apply the selected map, select OK. 614-330055-001 DECEMBER 2015 67 CHAPT CH APTER ER 3. NAVIGATING PROVISION To remove a map background image: 1. Within the Physical Viewer, select the view type from which you want to remove a map background. 2. Select the Map Properties ic icon on on the Map Map Vie Viewe wer. r. The The Map Prope Properrtie tiess winwin- dow displays. 3. To remove the background image, deselect the Background Image checkbox. 4. To accept the change, select OK O K. The Map Viewer displays with a blank background. Related Topics: l Physical Map Map View on page 63 l Submaps Sub maps on page 71 68 AVIAT NETWORKS PROVISION USER MANUAL Map Annotations In the ProVision Map View, you can label specific items in a map. You can also apply a label to the Container level of the devices, or to the map itself, using the Map Annotations function. The Map Annotation function is useful for: l Naming regions regions or groups l Providing notes l Adding corpor corporate ate identity identity Procedure 1. Open Open a Physical Physical Map in the Map View View o off ProVi ProVisio sion. n. 2. Ri Right-c ght-clic lick k on a blank blank space in the map. In the pop-up pop-up menu, sele select ct Add Annotation. 3. The Ann Annotati otation on scree screen n displays. displays. 4. Use this this scree screen n to set the annota annotation tion text, text, image, image, and style. 614-330055-001 DECEMBER 2015 CHAPT CH APTER ER 3. NAVIGATING PROVISION 5. Clic Click k OK. 6. The anno annotatio tation n displays in the Map Map View. View. When Wheneve everr you open open this Map View, the annotation will display disp lay in the upp upper er left corne corner. r. Table 3-8. Annot Annotati ation on Screen Values Values Item Value Text Text Type the text for the annotati on. Ico Ic on Optio ption nally, you can selec electt an ico icon from your PC. This can be a custo custom m image or a corpo corporate rate logo, logo, formatted as a .jpg, .png, or .bmp file. Icon Location Relative To Text Whether the icon will be in front of (leading) (leading),, below, above, or behind (trailing) the text Style Font Type, Font Size, Font Color, and Background Set the appearance of your font using these items. Note that for Font Size, you must use the up/down arrows to adjust the size. Opacity ity Set Set the opac pacity ity of the tex extt and ico icon im ima age. You ma may y want to use large text set at 50% opacity, to give it a trans- Pre revi view ew lucent overlay of the map. Wh Wha at yo your ur sel elec ecte ted d tex text, ico icon, and styl ylee wi willl look like. ike. 69 70 AVIAT NETWORKS PROVISION USER MANUAL Detailed Device Views In ProVision, you can view detailed information about each managed device. All device have at least one detailed view option: several have two or three. To identify the device views available for a device, right-click it. Device view options are listed in the right-click menu. The following are the detailed device view types. NOTE: Device view types not required for your l ocation may not b be e included in this documentation. l l l Submap View - A view displaying managed elements of a device. See 71.. Submaps on page 71 Equipmen Equipmentt View - A real-time view of a device, based on the physical configuration of the device. See Equipment Views on page 73. 73. Int Interface erface View - A view displaying a device’s IF interfaces. See Interface Views on page 78 78.. Submaps A submap is a separate floating window showing the eleme elements nts within the selected object or device. This figure shows an example of a submap window. Submaps are fully functional maps with their own menu and tool bar. A submap can be opened for a container, device, RF link, Eclipse element element (for example, examp le, DAC, LINK) or Memotec CX-U element in either the Physical Viewer or Map Viewer. Submaps display for Eclipse, CTR 8440, and CTR 8540. Figure 3-7. Eclipse Submap Submap View 614-330055-001 DECEMBER 2015 71 CHAPT CH APTER ER 3. NAVIGATING PROVISION Figure 3-8. CTR Submap Submap View Use submaps to: l l l Have several several submaps open at any one time; these these can be maximized or minimized as required. Pe Perf rfor orm m specific oper operations ations on a submap using its menu and tool bar. bar. Increase Increase the Physic Physical al Viewer size size by minimizing the Map Viewer Viewer and displaying submaps. Procedure 1. Right-click Right-click the container container or device (the Physical Viewer Viewer,, or Map Viewer, Viewer, or submap). 2. From the right-click menu displayed, select Open Device. 3. Or, in the Physical Viewer, open a device and select a sub-device from the Physical Viewer.. A separate submap window displays Viewer displ ays.. 4. If a plug-in is missing, its space includes a question mark icon, as shown below: NOTE: If the device’s r ight-click ight-click m enu says Open Submap, the view that that displays is s imilar to the Flat Map option. These devices usually have 73.. more detailed Equipment Views on page 73 72 AVIAT NETWORKS PROVISION USER MANUAL In and Out of Service View When devices are in service service,, they display disp lay without any add additional itional icons. When devices are out of sservice ervice,, they display disp lay with this icon beside them: t hem: An example of t he Submap with out of service s ervice devices is shown below: Equipment Views For certain types of radio, users can access both the standard submap view and an Equipment View. An Equipment View shows the layout and status of all radio components, exactly as they are installed. Equipment Views are available for the following radio types: l ADR 155c l ADR 2500 l Constellation l MegaStar MegaStar M:N and 1+1 l TRuepoi TRuepoint nt 4040 and 5000 l TRuepoint TRuepoint 6400 l TRuepoint TRuepoint 6500 l WTM 6000 Procedure To open an eq equipment uipment view: 1. Right-click the device within the Physical Viewer or Map Viewer. 2. From the right-click menu displayed, select Open Equipment View. 3. A separate Equipment View window displays. ProVision communicates with the device to get the most current data for the equipment view. This may take a moment. 614-330055-001 DECEMBER 2015 73 CHAPT CH APTER ER 3. NAVIGATING PROVISION 4. To rediscover plug-ins in the Equipment View, click the Refresh but ton . 5. To view the Event Browser for this item, click the Event Browser but t on . Equipment View Examples In the Equipment Views, the color of each plug-in device changes based on new events. ProVision updates the event status automatically. ADR 155c The ADR 155c displays with this equipment view. NOTE: ADR equi equipment pment views views ar e only available for ADR155c or 2500 if the ADR firmware is later than P2.6. ADR 2500 The ADR 2500 displays with this equipment view. 74 AVIAT NETWORKS PROVISION USER MANUAL Constellation The radio below is a Constellation terminal. The radio below is a Constellation repeater, set up for two links. 614-330055-001 DECEMBER 2015 75 CHAPT CH APTER ER 3. NAVIGATING PROVISION MegaStar M:N and 1+1 This radio displays at two levels in the equipment view; the shelf and the specific equipment layout. Double-click on a device on the shelf to drill down and view the specific equipment layout. In the example below, by drilling down into the SPU shelf, we see that the alarm is from the CTI. TRuepoint 4040 and 5000 TRuepoint 4040 and 5000 radios display with the same type of equipment view: 76 AVIAT NETWORKS PROVISION USER MANUAL TRuepoint 6400 614-330055-001 DECEMBER 2015 77 CHAPT CH APTER ER 3. NAVIGATING PROVISION TRuepoint 6500 Interface Views For certain certain types of radio, user userss can a acce ccess ss an Interf Interface ace View. An Interf Interface ace View shows the IF interfaces for the radio. Interf Inte rface ace Views are available for the following following radio types: ty pes: Accedian l l Cisco devices l CTR 8440, 8540 l CTR 8611 (cannot enable Ports Ports from from the Inter Interface face vie view w for CTR 8611) l Juniper M7i/10i l Generic Devices l Symmetricom l Tellabs 8600 (cannot enable Ports Ports from the Interface Interface view fo forr Te Tellabs llabs 8600) l WTM 3300 The color of the interface interface shows the interface interface status: l l Green Green = Connected Connected Red = Disconnected Disconnected l Gray = Disable Disabled d 78 AVIAT NETWORKS PROVISION USER MANUAL Procedure 1. Right-click the device within the Physical Viewer or Map Viewer. 2. From the right-click menu displayed, select Open Interface Viewer. 3. A separate Interface View window displays. ProVision communicates with the device to get the most current data for the equipment view. This may take a moment. 4. To rediscover plug-ins in the Interface View, click the Refresh but ton . 5. To enable ports for an interface, right-click on an interface and select Port Enable. 6. To view the Event Browser for this item, click the Event Browser butt on . 614-330055-001 DECEMBER 2015 79 CHAPT CH APTER ER 3. NAVIGATING PROVISION Event Browser The main Event Browser displays at the bottom of the main user interface, presents a scrolling list of events captured by ProVision. From the main Event Browser, you can perform many functions, such as acknowledge and clear events, view event history and probable cause, and add an event to pre-fil299.. ter tering. ing. For details see Event Management Procedures on page 299 By default, unacknowledged active events are listed in chronological order, with the most recent events displayed at the top of the list. A maximum of 1000 events can be displayed in the main Event Browser. Figure 3-9. Mai Main n Event Event Browser Browser # Value 1 Severity 2 Status 3 4 Acknowledged/Unacknowledged Note 5 Notification Notification Dialog boxes 6 Event Severity and Count Countss Status Bar The status bar provides provides the following information: information: l The user currently currently logged on. l The ProVision ProVision server server to which you are connected. connected. l l The number number of active notification dialog boxes. For mor moree information information Set the Server Notification Preferences on page 342. 342. The event event severity severity counts, counts , color-coded color-coded representations representations of the total number of events of each severity type. 80 AVIAT NETWORKS PROVISION USER MANUAL NOTE: To view only the the events of a particular severity, for example major events, in a separate Event Browser window, select the colorcoded event sever ity count. count. Event Browser Menu The right-click menu has additional functions for the main Event Browser. l Event Filters opens the Filters window and allows you to tell ProVision which event you want to filter. For more information see Event Log Pre-Filtering on page 326. 326 . l Browser Options opens the Browser Options window. From here, you can customize the details, fields, and sorting options in the Event Browser view. For more information see Changing Event Browser Options on page 321. 321. l Save Settings saves the curre current nt Event Browser settings. l Maximize/Hide allows you to display and hide the Event Browser view. l Certain events, particularly particula rly the WTM 3300 Perfor Performance mance Thre Threshold shold event, include pop-up notes with value details Customizing the Main Event Browser Browser In the main Event Browser, you can change how the information displays. 1. To move move a column, click and drag the column column title bar to the required position. 2. Se Selec lectt the require required d column title to change the orde orderr in which eve events nts are displayed. Select the same column title a second time reverses the sort order for the column. For more information, Customizing Event Browsers on page 297. 297. 614-330055-001 DECEMBER 2015 81 CHAPT CH APTER ER 3. NAVIGATING PROVISION The Task Manager Screen The Task Manager screen shows the status of tasks in progress, including the start and end time of the task. You are often prompted to open the Task Manager when you start a task or report that may take some time to run. ProVision can run multiple tasks simultaneously. If multiple tasks are running, the Task Manager will show these tasks. You can Filter the Task Manager sscre creen en t o view tasks for specific sp ecific devices, hop counts, containers, or dates/times. Click on the Filter button, then enter the value in the Filter field. NOTE: Whi While le ProVision can run multiple multiple tasks simultaneously, simultaneously, it will not run multiple multiple versions of the sam e task. For example, only one Inventory Report can be generated at a time. 82 AVIAT NETWORKS PROVISION USER MANUAL Using Search to Search All ProVision Data ProVision’s main search function enables you to find specific data in the ProVision system. The Search function searches all ProVision data to locate the data you specify, from an IP address for a specific radio to all radios in a particular state. NOTE: The search text field searches detailed device properties: Class Name, Name, IP Address, State, SNMP Version, Eclipse License Serial Number, Software Version, Device Sub-Type (e.g., RAC 6x), Device IDU Type (e.g., I NUe). NOTE: To search for device subtypes, such as RAC LL, specify the sub- typeThis usinis using g the wildcard aster ixfor in this the the Searc h field, for example, *RAC LL. currently required type of search. Procedure 1. Either: select Search > Search from the menu to open the Search window. Or, from the tool bar, select the Search icon. icon. The Se Searc arch h windo window w displays. For a fast search, enter a value in the Search: field and click Search Now. Click on More Criteria to view the full Search screen: 614-330055-001 DECEMBER 2015 83 CHAPT CH APTER ER 3. NAVIGATING PROVISION 2. The Search window lists the criteria that you can enter to narrow your search: Search - Enter any value or property that you want to search on. Physical Container - Enter a Physical Container name. IP Address - Enter a full or partial IP address. l Objec Objectt T Type ype - Select Object Types from the drop-down menu. Note that you can search for one object object type or multiple objec objectt types. Object State - Select Object States from the drop-down menu. Devices with Pre-Filter Enabled l l Devices with Performance thresholds Enabled Devices with Ethernet 15-min or standard data collection every 15 mi minutes, nutes, Daily l Devices with Customized events Enabled l Devices Devices that are are Out of Service Enabled After you have enter entered ed all your search criter criteria, ia, click Search Now. 3. The results display at the bottom of the Search window. You can select a column title, Object or Object Container, to sort the results in either ascending or descending order. 4. You can right-click an object or a container in the search results screen to view associated right-click menus. See the Search Result Examples below for a sample of this. 5. To clear the results, or to enter data for another search, click New Search. 6. To close the Search window, select Close. Search Result Examples The figure below shows a search result using text. The asterisks before and after the text enable wildcard searching, to find all device values that include that text. 84 AVIAT NETWORKS PROVISION USER MANUAL The figure below shows a search result for a specific IP Address. 10.16.10.199 is the IP address of an Eclipse INU. The Eclipse radio and its components are displayed as a result of the search. Note that an item has been right-clicked and displays a menu with available functions. functions. The next figure shows an example of a search result, for Eclipse radios with 15-minute radio data collection enabled. This search criteria is useful when the system is running slowly, and you suspect there might be too many radios with this mode of data collection enabled. 614-330055-001 DECEMBER 2015 CHAPT CH APTER ER 3. NAVIGATING PROVISION 85 86 AVIAT NETWORKS PROVISION USER MANUAL Searching the Tree Viewers ProVision’s Find search function enables you to find specific data in any of the ProVision tree views: Physical, Logical, or Circuits. This allows you to find and view an item quickly. Select Find fro from m the Tree Tree Viewer toolbar to open the Search Search Tr Tree ee window. This will appear at the bottom of the Tree Tree Viewer. Viewer. This Find function uses “wildcard” searches. With a wildcard search, you use an asterisk (*) or question mark (?) to tell the function how you want to search for your numbers or text. Using the up and down icons, you can then go through the Tree View and find the items that include part or all of the numbers or text. For example, if we want to find items with the word “North” in the item name, there are four ways to enter that for a wildcard search: l North* = An asterisk after the value; finds all items that begin with this value. l *North = An asterisk in front of the value; finds all items that end with this value. l *North* = An asterisk before and after the value; finds all items that contain this value. l N*th = An asterisk within a value; finds all items that begin and end with the noted note d values. l To search search for for device device subtypes, such as RAC LL, specify specify the subtype using the wildcard asterix in the Search Search field, for examp example, le, *RAC LL. This is curre currently ntly required for this type of search. 614-330055-001 DECEMBER 2015 87 CHAPT CH APTER ER 3. NAVIGATING PROVISION Procedure 1. Select Find from the Tr Tree ee Viewer toolbar, or highlight highligh t the Tree Tree Viewer and press Ctrl+F3 on the keyboard. The Tree Search field displays below the Viewer. 2. Type the search criteria. Use the Wildcard search convention. 3. To start the search, either press the Enter key, or click the Up and Down icons in the Tree Search. The Tree Search function will go up or down the Tree View and highlight each item that matches your search. Continue until you find the item you want. 4. To close the Tree Search, select the red X. The Tree Search closes and is not seen in the display. 88 AVIAT NETWORKS PROVISION USER MANUAL Icons Information and Usage Both the Physical Viewer and the Map Viewer show the current status of each network element, with icons representing the highest severity event that has been detected for the device. Color and other graphic cues show the status of the objects/network elements. This alerts you to changes in device status. To identify potential problems, ProVision propagates the alarm state of objects upwards through each object, and its parent objects change color as well. A parent object’s color reflects the most severe alarm on any of its children. This section covers the following topics: l Viewing Viewi ng Radio Icon Icon Anatomy Anatomy on page 89 l Alarm Seve Severity rity Color Coding on page 91 l Devicee States Devic States on page 92 l l Radio Tasks on page 93 See About User Defined Icons on page 91 l Also see Physical Viewer and Icons on page 55 for a list of all device icons Viewing Radio Icon Anatomy Physical Viewer Viewer Display Display of Radio Icon Anatomy The figure below shows an example of a Eclipse Terminal icon displayed in the Physical Viewer’s Viewer ’s phy physical sical pane. From the device icon, you can identify the name of t he device, the type of device, if the device is functioning normally by the color of the event severity icon, and if any tasks are being performed on the device, for example, pre-filtering. Figure 3-10. Physical Viewer Viewer - Labeled Radio Icon # Value 1 This item is Clo Closed sed in the tree struc structure; ture; subsub-radios radios and devices are not displaying. 614-330055-001 DECEMBER 2015 89 CHAPT CH APTER ER 3. NAVIGATING PROVISION # Value 2 If an event is present present,, the co colo lorr here indicat indicates es the event severity. Mouse over this to view the event type. 3 Radio icon. 4 5 Task. Radio name. Map Viewer for Radio Icon Anatomy The figure below shows an example of an XP4 radio icon displayed in the Map Viewer. Each radio icon shown in the Map Viewer, or a submap, displays information about the network element the icon represents. The information includes the radio’s name, state, and event information. Figure 3-11. Map Viewer Viewer - Labeled Labeled Radio Radio Icon # Value 1 If an event is present present,, the co colo lorr here indicat indicates es the event severity. Mouse over this to view the event type. 2 Radio icon. 3 Radio state and task task.. The current state of the radio. For more information, see Device States on page 92 4 Ra Radio dio name. Identifies the specific specific radio (net (network work element) represented by this icon. 5 Mouse over displaying event details. 90 AVIAT NETWORKS PROVISION USER MANUAL About User Defined Icons When deploying some device t ypes, such as a Generic Generic Device Symbol, users can enter customized icons. User defined icons: l Can be .jpg, .bmp, or .png graphics l Can be up to 2.4 2.4 MB in size size l Are automatically resi resized zed to match icon icon shape and format format To remove remove a user-def user-define ined d icon fro from m a device, device, right-click right-click the device in the Map v iew. Select Remove Customization. The device icon will change to a default. To manage user-def user-define ined d icon icons, s, go to the C Conf onfiguratio iguration n menu and select select Edit User Defined Icons. You can delete or edit selected icons from here. Alarm Severity Color Coding Each event has a severity level. The level indicates whether the event is a routine action, a warning of impending problems, or a signal of catastrophic events within a device. This table defines the six levels of event severity and the associated color code. Table 3-9. Event Color Codes Codes Severity Level Co lo lor C ode Critical Red Major Orange 614-330055-001 DECEMBER 2015 91 CHAPT CH APTER ER 3. NAVIGATING PROVISION Severity Level C olor C ode Minor Yellow Warning Warnin g Cyan Normal Green Informational White Device States A device state s tate defines defines the conditions in which a device exist s. State repre representation sentation is based on Telecom Telecom standards stand ards that include: l OSI state dictionar dictionary y (based on the OS OSII SM SMF F 10164-2 standard) l Event state dictionar dictionary y to display the th e set set of eevents vents A radio can only be in one state, s tate, but can have a number of tasks applied app lied to the events it is generating. When a radio has more than one task, a + sign displays on the state indicator. When the cursor is moved over a radio icon, pop-up text displays information about the radio, such as its state and tasks. Object Pop-up Details When you move the mouse over an obje object ct in the Physical Viewer, Viewer, pop-up details for th thee object are displayed. The INU radio shown below is in an active state, has 5-min data collection and pre-filtering enabled, is Managed, and has two warnings. When you mouse-over a container object the number of its children displ displays ays in the popup. Figure 3-12. Radio Wit With h Pop-up Pop-up Text This table lists the various states for devices, and how these states are indicated in the user interface. interface. Table 3-10. Device States 92 AVIAT NETWORKS PROVISION USER MANUAL Device Devi ce Sta State te Icon Icon Oth Other er Indi Indica cators tors Unmanaged - Ev Event ent sever severity ity is bl blue. ue. The The poppop-up up text text dis displ play ayss State: Unmanaged. Managed - Even Eventt sev severity erity can can be any of the the colo colors rs - gree green, n, cyan, cyan, yello yellow, w, orange, ora nge, or red. The pop-up text di splays splays State: Managed. For more information on managing a device, see Managing a Device on page 156 . Connecting ProVision is attempting to con connect nect to the device acro across ss the network using the device’s IP address. There has been no communication from the device since being managed. The pop-up text displays State: Connecting. Asleep The radio is asleep. asleep. The poppop-up up text displ displays ays State: Asleep. For more, see Sleep Status for a Device. Errored The manag managed ed radio is not respo responding nding to polling polling from Pro ProVision Vision.. The pop-up text displays State: Errored. “+” icon If a “+” ico icon n appears in the bott bottom om left corner corner of a tas task k icon, icon, this indicates that more than one radio task and/or device state is associated with that radio. radio. The pop-up pop-up text displays the additio additional nal tasks/states. Radio Tasks A task represents represents additional add itional ProVision activity a ctivity on events. This can be for one radio or a set of radios. For example, pre pre-fi -filter ltering ing events st ops the events that tha t meet meet the pre-filter pre-filter criteria before they can get into the system. Typically, a task is only active for a radio that is Managed. When a task is being performed on a radio or radios, the radio displays with the task icon, for example, pre-filtering. Table 3-11. Radio Tasks Radio Task Ico n Pre-filtered For more information about pre-filtering events, see Event Log Pre-Filtering on page 326 . 15-minute data collection ProVision uses the data from the radio to create performance forma nce trends graph graphs. s. See Data Collection on page 388 for more information. Performance Thresholds Performance thresholds feature allows you to associate an alarm or group of alarms with unexpected performance results resu lts.. See Performance Performance Thresholds on page 413 for more information. “+” icon If a “+” icon icon appears in the bott bottom om left corner corner of a tas task k icon, this indicates that that more than one radio task and/or device state is assoc associated iated wi th that radio. The pop-up text displays the additional tasks/states. 614-330055-001 DECEMBER 2015 CHAPT CH APTER ER 3. NAVIGATING PROVISION 93 94 AVIAT NETWORKS PROVISION USER MANUAL Integrating Windows Applications with ProVision You can integrate Windows app applications lications with ProVision, to conveniently launch these applications directly directly from from ProVision. ProVision. There There are two levels levels of application app lication integration: integration: At the device level, to display in a device’s right-click menu. menu. This links the application to that particular device type, and it displays in the right-click menu for all instances of that device type. Use this for applications that are very device-specific, such as a craft tool for a Generic Device. At the main Root level, to display in the main ProVision toolbar. toolbar. This does not link the application to any device type. Use this option for applications that are based on general general data, dat a, such as PCR (Paperless Chart Rec Recorder order). ). NOTE: For each application to to be used, the application files files need to be installed on each individual individual ProVision client. Note the system location where the installation files files are saved, for use in the the launch configurati configuration on procedure. Procedure 1. On the ProVision Client, install the Generic Device craft tool or tools. 614-330055-001 DECEMBER 2015 95 CHAPT CH APTER ER 3. NAVIGATING PROVISION 2. Log into ProVision at the NOC engineer or system administrator level, i.e., using the NOC engineer or administrator user name and password. 3. Open the Edit Applications screen, based on the type of application integration you need: l To set set up the application at the Root Root level, in the main ProVision ProVision too toolbar lbar,, click on the Applications icon iin n the the upper upper righ rightt of the mai main n scr scree een: n: l . To set set up a windows application a pplication at th thee Device Device le level, vel, in the Tre Treee Viewe Viewer, r, locate a device that you want to connect with craft tools. Right-click on its icon. In the right-click menu, Applications > Edit Applications displays. Click on Edit Applications. Applic ations. l The Edit Applications scre screen en display s. 4. To add a new Application, click Add. A new line appears in the screen. Doubleclick in the fields to enter the following values: l l l Name - Enter the name of the craft tool application. Executable Path Path - Navigate to the location of the device craft tool executable file (.exe). Select the .exe file. Parameters - Only use this value if you are linking the application with a specific device type, and only if you need to customize the .exe file with command line parameters. See the Installation and Administration Guide, Generic Devices, for more details. 5. To enter additional Applications, click Add again. You can save multiple Applications for each device, as shown. 6. When you are done, click OK. 7. The applications are now directly integrated with ProVision. l l Applications integrate integrated d at Ro Root ot level level now display in the upper right right of the main screen toolbar. Click on the application icons to open and use the applications. The right-clic right-click k menu for for the device device now displays Applications >(Application Names), and you can open the applications from there. 8. If you need to update the application, open Applications > Edit Applications again. This re-opens the Edit Applications scre screen. en. Make changes to the application ap plication link from this screen. 96 AVIAT NETWORKS PROVISION USER MANUAL Linking Documents to Devices and Maps You can link documents to devices and to the main Map display disp lay in ProVision, to conveniently launch refere reference nce documents d ocuments directly fro from m ProVision. This is done by setting up an integrated Windows application, then linking a document to run when that application is opened. There The re are two levels levels of this: At the device level, to display in a device’s right-click menu. menu. This links the document to that particular device type, and it displays in the right-click menu for all instances of that device type. At the main Root level, to display in the main ProVision toolbar. toolbar. This does not link the document to any device type, and it is available for all users. NOTE: For each document and application application tto o be used, the files need to be installed on eac h indi individu vidual al ProVision c lient lient.. Note the sys tem loc ation where the files ar e save d, for use in the the launch configuration configuration procedure. 614-330055-001 DECEMBER 2015 97 CHAPT CH APTER ER 3. NAVIGATING PROVISION Procedure 1. On the ProVision Client, install the Generic Device craft tool or tools. 2. Log into ProVision at the NOC engineer or system administrator level, i.e., using the NOC engineer or administrator user name and password. 3. Open the Edit Applications screen, based on the type of application integration you need: l To set set up the application at the Root Root level, in the main ProVision ProVision too toolbar lbar,, click on the Applications icon iin n the the upper upper righ rightt of the mai main n scr scree een: n: l . To set set up a windows application a pplication at th thee Device Device le level, vel, in the Tre Treee Viewe Viewer, r, locate a device that you want to connect with craft tools. Right-click on its icon. In the right-click menu, Applications > Edit Applications displays. Click on Edit Applications. Applic ations. l The Edit Applications scre screen en display s. 4. To add a new Application, click Add. A new line appears in the screen. Doubleclick in the fields to enter the following values: l l l Name - Enter the name of the application. Executable Path Path - Navigate to the location of the application executable file (.exe). Select the .exe file. Parameters - Navigate to the location of the document and enter the link to the document. document. 5. To enter enter additional ad ditional App Application lications/Do s/Documen cuments, ts, click Add again. You can save multiple documents for each device, as shown. 6. When you are done, click OK. 7. The applications and their linked documents are now directly integrated with ProVision. l l Linked Linked documents documents integrated integrated at Root leve levell now display in the upper right right of the main screen toolbar. Click on the application icons to open and use the applications. The right-clic right-click k menu for for the device device now displays Applications >(Application Names), and you can open the documents from there. 98 AVIAT NETWORKS PROVISION USER MANUAL 8. If you need to update the document, open Applications > Edit Applications again. This re-opens the Edit Applications screen. Make changes to the document link from this screen. 614-330055-001 DECEMBER 2015 99 Chapter 4. Deploying and Managing Devices You can deploy and manage devices in a network using usin g ProVision. Deploying a device provides ProVision with details about a real device in the network. Managing a device activates ProVision to communicate with the device and show the device status. A device is any SNM SNMP P enabled object that ProVision can ca n communicate with, for example, a Aviat Networks radio, a DXR SMA or a non-Aviat Networks radio. This section is written for the NOC operator. It is assumed that ProVision is already installed and managing the network. It describes the workflow and procedures to deploy, link, and manage devices in ProVision. This section covers the following topics: l About Abo ut Deploying and Managing Managing Devices Devices on page 102 l Deploying Deplo ying Devices Devices on on page 106 l Managing Devic Devices es on on page 156 156 l Configuring Configur ing and Synchronizing Synchronizing Device Devicess on page 192 l Circuit Manageme Management nt on page 177 l Configuring Configur ing and Synchronizing Synchronizing Device Devicess on page 192 l Loading/Activat ing New New Software Software and Licenses Licenses on page 221 221 For Carrier Ethernet functions, including VLAN, Ethernet OAM, and ERP ring, see Carrier Ethernet Management on page 243 243.. 614-330055-001 DECEMBER 2015 101 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES About Deploying and Managing Devices For a radio network, the majority of devices in the network are already physically installed, commissioned, deployed, and managed in ProVision. When new towers/sites are installed, the NOC operator/ operator/engi enginee neerr deploys and manages the new devices devices in ProVision. When a device is installed instal led and successfully commissioned, you can manage the device with ProVision. ProVision polls p olls the device and receives receives events from tthe he device. Deploying a device provides ProVision with data about that device in the network. The deployed device displays as a graphical icon on the ProVision user interface. Until a new device is deploye d eployed d and managed in ProVision, ProVision, ProVision ProVision does not recogni recognize ze the device device,, or receive traps generated by a device. To successfully successfully deploy d evices, evices, you y ou need t he following following information information:: installation locations, radio types, and IP addresses. To enable you to group devices by location, ProVision includes the following containers: Region Site Rack When setting up the network in ProVision y ou can choose to t o use any or none of the t he container objects. If the network is already set up and you are deploying new devices, then fo follow llow the existing pattern. NOTE: A high level container can have a ddition dditional al c ontainers ontainers a nd devices. For example, a region may consist of several sites and devices Deployment Guidelines When deploying Aviat Networks Network s devices, you must create createyou yourcan sitechange hierarchy bef before ore deploying any devices. Once you have deployed a device, the site hierarchy placement of the device at any time. Naming Standard St andardss You and your company choose the th e naming na ming standards stand ards to app apply ly to your ProVision network. Set the t he naming standards stand ards as early as possible to make the implementation implementat ion easier. Note, that with the proper authority, you can rename most ProVision objects at any time. As an example of how h ow your devices and links might be nam named: ed: l If you have three three sites (A, B, and C), t hat have two conne connecting cting links links (one between A and B, and one between B and C) you could have Eclipse device between names of: o Eclipse A-1 10.14.135.1 102 AVIAT NETWORKS PROVISION USER MANUAL o Eclipse B-1 10.14.135.3 o Eclipse C-1 10.14.135.5 Device Deploym Deployment ent and Manageme Management nt Workflow Workflow The process below shows how deploying and Managing devices fits into the total ProVision management process. 1. Install ProVision. ProVision. 2. Is this installation an upgrade? l If Yes, Yes, after after you install the upgrade upgrade,, import the saved topolo topology. gy. l If No, No, procee proceed d to the next step. step. 3. In ProVision, deploy and manage devices. 4. Use ProVision to manage events. 5. Use ProVision to run system diagnostics. 6. During deployment, management, and system diagnostics, ProVision uses performance trend analysis of G.826 and RSL/RSSI. Deployme Dep loyment nt and Manageme Management nt When you deploy a device, you are p providing roviding details about a real real device to ProVision. You can manage manag e t he device at the same time or leave l eave t he device to be man managed aged at a later date. When a device is deployed but not Managed in ProVision, the device does not generate generate alarm traps, is not polled for status, and the event state color is blue, which signifies an unmanaged status. The Process for Deploying and Managing Devices Prerequisites To deploy and manage devices, you must have all of the following information: l A comprehensive comprehensive network network element element inventor inventory y l List of all the site sites, s, each device device name and its type l Know Know any device specific specific details l Determine Determine IP addre add ress ss assignments l Determine Determine device specific specific configuration re require quirements ments Dependencies ProVision requires the correct IP address for the devices on the network. This is required so that ProVision can poll and receive events from the devices. 614-330055-001 DECEMBER 2015 103 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Deploying Devices This is the reco recommende mmended d process process for deploying Aviat Ne Network tworkss devices devices in a an n existing network. 1. Add a new Container, if required. 2. Deploy the new Radios. 3. If required (for example, for new TRuepoint devices) update their 4. configuration. 5. Manage the new devices. 6. Create links. 7. Verify the new links. 8. Verify that ProVision is receiving events from the devices. 9. Check that the devices, and their links, are all configured correctly. Pre-Deploying Devices When you are p prere-deploying deploying devices in ProVision, in advance adva nce of rolling out the network you can use the following process. The main m ain difference difference betwee between n this and the standard stand ard Deploying Radios process is that you create and verify links before you Manage the devices. 1. Add a new Container, if required. 2. Deploy the new devices. 3. Create links. 4. Verify the new links. 5. Manage the new devices. 6. Verify that ProVision is receiving events from the devices. 7. Check that the devices, and their links, are all configured correctly. CAUTION: This This process is not applicable applicable to the the DXR DXR 700 and Eclipse Node devices. devices. A DXR DXR 700 is auto-di auto-discovered scovered when th the e DXR SMA to which which it is conn connected ected is managed managed in ProVision, ProVision, and and th therefore erefore the the device device is managed managed before you can create the the link. link. Th The e Eclipse Node uses uses plug-ins, plug-ins, whi w hich ch means its its configu configuration ration is auto-discovered auto-discovered when th the e device device is managed managed in ProVision. ProVision. Only Only then then can you create a link link or links. links. Device Deployment By Type Table 4-1. Device Deployment Deployment Instruction Instructionss by Device Type 104 AVIAT NETWORKS PROVISION USER MANUAL Device Deplo yment Details CAU CAU (Contro (Controll Alarm Unit) Deplo Deployment yment on page 122 Cisco Cisco Deployme Deployment nt on page 123 Constellation Constellation Constellatio n Devic Devicee Deployme Deployment nt on page 124 DXR 200 DXR SMA DXR 200 and DXR DXR SM SMA A Device Device Deplo Deployment yment on page 120 DXR 200 and DX DXR R SMA SMA Devic Devicee Deployment Deployment on page 120 Eclipse Eclipse Devic Devices es and Node Nodess Deplo Deployment yment on page 117 Generic Generic Gener ic Device Deployment on page 128 Symmetricom Symmetrico Symmetr icom m TP1x0 TP1x00 0 Deplo Deployment yment on page 135 TNet TNett Devic TNe Devicee Deployme Deployment nt on page 144 TRuepoint 4000 TRuepoint TRue point Device Deployment on page 138 TRuepoint 4040 TRuepoint TRue point Device Deployment on page 138 TRuepoint TRuep oint 5000 TRuepoint TRue point Device Deployment on page 138 TRuepoint TRuep oint 6400 TRuepoint TRue point Device De Deployment ployment on page 138 TRuepoint TRuep oint 6500 TRuepoint TRue point 6500 Device Deployment on page 142 All Oth Other er Devices Standard SNMP Device Deployment on page 112 Includes ADR 155c, ADR 2500, Altium, Aurora, Cisco, CTR 8500, DART, DVA, DVM, DVM-XT, DXR 100, E-Link, LE 3000, LE 3200, all MegaStar, Memotec CX-U, all MicroStar, SAGEM-LINK, SPECTRUM II SNMP SNMP,, Symmetrico Symmetricom m Timers, Tell Tellabs, abs, Velo Velox, x, Radwin WinLink 1000, Radwin 2000, X XP4 P4 614-330055-001 DECEMBER 2015 105 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Deploying Deplo ying Devices This section covers the following deploying procedures: l Adding, Editing, and Deleting Device Device Container Containerss on page 106 l Standard SNMP SNMP Device Device Deployment Deployment on page 112 includes legacy, MicroStar, MegaStar, DVA l Eclipse Device Devicess and Nodes Deployment Deployment on page 117 l TRuepoint TRue point Device Deployment on page 138 l TRuepoi TR uepoint nt 6500 Device Device Deployment Deployment on page 142 l Constellation Constellatio n Device Device Deployment Deployment on page 124 124 l CAU (Control (Control Alarm Unit) Unit) Deployment Deployment on page 122 122 l Generic Gener ic Device Device Deploym Deployment ent on page 128 l l Cisco Deplo Deployment yment CTR 8300 8300 and 8540 Device Device Deployment on page 125 l Symmetricom TP1x00 Deployment l Symmetricom TP5000 Deployment l TNett Device TNe Device Deploymen Deploymentt on page 144 l DXR 200 200 and DXR SMA SMA Device Deployme Deployment nt on page 120 l Troubleshooting Tro ubleshooting Device Device Deployment on page 152 l Changing a Devic Device’ e’ss Container on page 152 l Moving Mo ving Containers Containers and Devices in the Map Map Viewer on page 153 l Renaming Re naming a Devi Device ce on page 153 l Deleting a Device on page 154 Adding, Addin g, Editing, and and Deleting Device Containers A container represents represents an object object that serves as a s a grouping entity for devices in ProVision. Other containers are added to a parent container, and devices are deployed from their container. This section describes the following Container functions: l Adding a Container Container on on page 107 107 l User Define Defined d Containers on page 108 l Renaming Re naming a Container Container on page 111 l Deleting Dele ting a Container Container on page 111 106 AVIAT NETWORKS PROVISION USER MANUAL Adding Ad ding a Container Container The following procedure describes how to add a standard container. There are three types of containe containerr available a vailable:: l Region Region - Use as a container for Sites. l Site - Use as a container container for for radios and/o and/orr Racks. Racks. l Rack - Use Use as a container for Radios. If you need to define your own container type, see User Defined Containers on page 108 108.. Procedure 1. In the Tree Viewer or the Map Viewer, right-click on a root icon or an existing container, for example, the network or a region icon. 2. In the right-click menu, select Deploy Object. The Deployment window displays. l Click on Containers. The Containers Family window displays. 3. Select the required Container icon, for example, Site. The Deploying <container < container> > window displays displ ays.. 614-330055-001 DECEMBER 2015 107 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES 4. In the Name field, type the name for the container. 5. Ensure that the Parent name displayed is correct; the container is placed under the parent listed. 6. Click Deploy. l l The Tree Tree Viewer Viewer and the Map Viewer’s Viewer’s Hierarchic Hierarchical al la layer yer are updated and display the new containment icon. The Deplo Deploying ying <container <container> > results window displays, confirming that the container has been deployed. 7. Select Close. NOTE: The contai container ner can be r eassigned to another another par ent. User Defined Containers You can create create user-defined user-defined containers. This enables y you ou to have container icons and types def defined ined by your organizatio organization. n. NOTE: You must provide your own contain container er icons, in .jpg format. The container icons are automatically shrunk to a small display size when they are deployed in ProVision. ProVision. A s ize of 45 pixels wide by 35 pixels pixels high high is recommended. 108 AVIAT NETWORKS PROVISION USER MANUAL Procedure 1. Obtain your Container icon graphics in .jpg format. Save them on the same PC as your installation. instal lation. 2. In the Tree Viewer or the Map Viewer, right-click on a root icon or an existing container, for example, the network or a region icon. 3. In the right-click menu, select Deploy Object. The Deployment window displays. l Click on Containers. The Containers Family window displays. 4. Click the User Defined Container icon. The User Defined Defined Container Container window displays. 614-330055-001 DECEMBER 2015 109 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES 5. In the Container Type field, enter the Type Typ e of container you are defining. defining. 6. To use a previously loaded icon, select it in the Existing User Defined Icons frame. Icon 7. To load a new icon, thethe in the field. Then, click the button. From your PC,enter choose thicon's e .jpg . jpg Type graphic for the container icon. It Select displays disp lays in the User Defined screen. 8. Click Next. l l The Deplo Deploying ying <container <container> > results window displays, confirming that the container has been deployed. The Tree Tree Viewer Viewer and the Map Viewer’s Viewer’s Hierarchic Hierarchical al la layer yer are updated and display the user-defined container icon. 110 AVIAT NETWORKS PROVISION USER MANUAL NOTE: The container container can be r eassigned to another another par ent. Renaming a Container By defaul default, t, the ne networ twork k roo roott contain container er is not not name named. d. You You can give it a name using the Rename function. You can also change the name of any container that is incorrect or misspelled. Procedure 1. Right-click Right-click the container container to be changed. changed. In the right-c right-click lick menu, select select Rename. The Rename Rename Object Object window displays. d isplays. 2. Make the required changes to the container’s name. 3. To save the changes, select OK. Deleting a Container You can delete a container from the Tree Tree Viewer V iewer or the Map Viewer’s Viewer’s Hierarc Hierarchical hical layer. When a container is deleted, the Tree Tree a and nd Map Viewers Viewers are refre refreshed shed and the container is no longer displayed. CAUTION: Before deleting deleting a container, container, ensure there there are no managed radios or lin links ks associated with th the e contain container. er. NOTE: If you delete a c ontainer ontainer that contains contains radios this has no effect on the the actual ra dios or the com munications munications traffic they are carr ying. Procedure 1. Right-click Right-click the container container icon. icon. In the right-c right-click lick menu, select select Delete. The Delete Objects window displays. 614-330055-001 DECEMBER 2015 111 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES 2. To delete the selected object(s), select Yes. Standard SNMP Device Deployment Aviat Networks Networks or third-party t hird-party SNMP SNMP devices have an IP address, add ress, can be accessed via IP network netwo rks, s, and use the Simple Network Network Management Management Protoc Protocol ol to communicate communicate with ProVision. When you deploy a device you are p providing roviding details about a real real device to ProVision. You can manage manag e t he device at the same time or leave l eave t he device t o be ma managed naged at a later date. NOTE: When a device is deployed but not managed in ProVision, the device does not generate alarm traps, and is not polled for status. The event state color displays as blue, which signifies signifies an unmanaged unmanaged status. This section describes how to deploy standard SNMP devices. To help you deploy specific device types, see also Device Deployment By Type on page 104 104.. Prerequisites l l Cisco - For each Cisco device, you must adjust the CLI settings with ProVision's IP address. See Cisco Deployment on page 123 CTR 8540 - For each CTR 8540 device, you must set up SNMP and trap commands, both in the device before ProVision deployment, and within commands, ProVision. See CTR 8300 and 8540 Device Deployment on page 125 125.. l l l MicroStar - For each MicroStar device you are deploying in ProVision, you must find that t hat device in WebCIT and and set up ProVision’s IP address as the manager of that device. This setting is found in WebCIT via the Provisioning screen, in Network Setting 2, as the value SNMP Manager #1. See the WebCIT Operator manual for further further details. details. MegaStar - For each MegaStar device you are deploying in ProVision, you must find that device in FarScan and set up ProVision’s IP address as the manager of that device. See the FarScan Operator O perator manual for further details. Symmetricom - For each Symmetricom TP5000 device, you must adjust the CLI settings with ProVision's IP address. See Symmetricom TP5000 Deployment on page 137. 137 . For each Symmetricom TP1x00 device, you must find it in the TimeCraft craft craft tool and set up ProVision's IP address. See Symmetricom TP1x00 Deployment on page 135 Symmetricom 112 AVIAT NETWORKS PROVISION USER MANUAL l Community Strings -Many devices require read and write community strings. The community string (which is a name or combination of characters) is part of the device device’s ’s conf configuratio iguration n information information.. When ProVision ProVision wants to communicate with the device, it authenticates using the community string. There are typically two community strings linked with a device, one for reading values and one for writing (setting) values. These are normally set to “public” or “private”, but can be set to other values as a form of security. Procedure 1. Within the Tree Tree Viewer, Viewer, right-click an existing container container and sele select ct Deploy Object. The Deployment window displays, showing all the container and device options. 2. Select the icon for the required device type. The Deployment screen for that device type displays, showing available devices. NOTE: If you c annot immediately immediately find find the icon for the device type, try Microwave Radio or Ethernet. Then, select the required device icon. 3. The Deploying <device < device name> name> window displays. Enter the values for the new device,, as descr device describe ibed d for specific specific device types listed in the table ta ble below. below. NOTE: For all new devices, check to see that the Parent is correct. T h e device is placed under the parent listed. 4. Select Deploy. The Deploying <device < device name> name> results window displays. 5. To close the Deploying <device < device name> name> window, select Close. 6. Select the required device icon. 7. The Deploying <device < device name> name> window displays. Enter the values for the new device,, as descr device describe ibed d for specific specific device types listed in the table ta ble below. below. 8. Select Deploy. The Deploying <device < device name> name> results window displays. 9. To close the Deploying <device < device name> name> window, select Close. Table 4-2. Devi Device ce Deployment Deployment Details Details for Stan Standard dard SNMP Devi Devices ces 614-330055-001 DECEMBER 2015 113 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Device Deplo yment W indow Steps Single Devices: Accedi Accedian an EtherNID EtherNID,, Accedian Accedi an EtherNODE, Aurora, C Cisco, isco, CTR 8440, DVA, DVM, DVM-XT, ADR, Altium, DART, Velox, XP4, Symmetricom, SPECTRUM II SNMP, DXR 100, ELink, Memotec CX-U, LE3000, LE 3200, Radwin WL1000 and RW2 000 000,, Tellabs. In the Name field, type a descriptive name for the radio.The radio is labeled with this name in the User Interface. Enter the radio’s IP address. If present, the Read Community and Write Community strings have the default values. Only change them if the radio setting has been changed. The Read and Write Community strings must match the strings entered into the radio. To have ProVision start managing the radio, select the Manage checkbox. Protected Radios: DXR 100, XP4, DVM (repeater) SAGEM-LINK In the Name field, type a descriptive name for the radio. The radio is labeled with this name in the User Interface. Enter the A radio’s IP address. Enter the B radio’s IP address. The Read Community and Write Community strings have the default values. Only change them if the radio setting has been changed. The Read and Write Community strings must match the strings entered into the radio. To have ProVision start managing the radio, select the Manage checkbox. Multiplexes: ADR 155C, ADR 2500 In the Name field, a descriptive name forinthe MicroStar device. Ittype is labeled with this name the User Interface. Enter the IP address. The Read Community string has the defaul defaultt value. Only change it if the radio setting has been changed. The Read and Write Community strings must match the strings entered into the radio. To have ProVision start managing this radio, select the Manage checkbox. 114 AVIAT NETWORKS PROVISION USER MANUAL Device Deplo yment W indow Steps MicroStar I, II, III In the Name field, type a descriptive name for the MicroStar device. It is labeled with this name in the User Interface. Enter the IP address. The Read Community string has the defaul defaultt value. Only change it if the radio setting has been changed. The Read and Write Community strings must match the strings entered into the radio. To have ProVision start managing this radio, select the Manage checkbox. MegaStar M:N In the Name field, type a descriptive name for the Megastar device. It is labeled with this name in the User Interface. The Read Community string has the default value. Only change it if the radio setting has been changed. The Read and Write Community strings must match the strings entered into the radio. To have ProVision start managing this radio, select the Manage checkbox. MegaStar 1+1 In the Name field, type a descriptive name for the device. It is labeled with this name in the User Interface. Enter the IP address. address. The Read Community string has the default value. Only change it if the radio setting has been changed. The Read and Write Community strings must match the strings entered into the radio. To have ProVision start managing this radio, select the Manage checkbox. 614-330055-001 DECEMBER 2015 115 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Device Deplo yment W indow Steps Symmetricom Timing SystemTP1x00+ TP5000 In the Name field, type a descriptive name for the device. It is labeled with this name in the User Interface. Enter the IP address. address. To have ProVision start managing this radio, select the Manage checkbox. Select the SNMP Version, Version, v2c or V3. The Read Community string has the default value. Only change it if the radio setting has been changed. The Read and Write Community strings must match the strings entered into the radio. CTR 8540, WTM 3100 In the Name field, type a descriptive name for the device. It is labeled with this name in the User Interface. Enter the IP address. address. To have ProVision start managing this radio, select the Manage checkbox. Select the checkbox for Perform Class Checking Checking on Deployment. This checks that the radio class matches the device deployment window data. If the device deployment data does not m atch atch the actual radio clas class, s, an error message displays: Click OK. Then, click Back and select the correct device type. Select the Set Device out of service check box if required. 116 AVIAT NETWORKS PROVISION USER MANUAL Device Deplo yment W indow Steps WTM 3200 3200,, WTM 3300 3300,, WTM 6000 6000.. In the Name field, type a descriptive name for the radio.The radio is labeled with this name in the User Interface. Enter the radio’s IP address. (For WTM 3200, both IPv4 and IPv6 addresses are valid.) If present, the Read Community and Write Community strings have the default values. Only change them if the radio setting has been changed. The Read and Write Community strings must match the strings entered into the radio. To have ProVision start managing the radio, select the Manage checkbox. Select the checkbox for Perform Class Checking Checking on Deployment. This checks that the radio class matches the device deployment window data. If the device deployment data does not m atch atch the actual radio clas class, s, an error message displays: Click OK. Then, click Back and select the correct device type. Select the Set Device out of service check box if required. Eclipse Eclips e Devices and Nodes Deployment Deployment Deploying Eclipse devices and nodes is similar to Standard SNMP Device Deployment on page 112. 112. When you are d deploying eploying Eclipse nodes, you must select the option to Perform Class Checking on Deployment. Deployment. If this is not selecte selected, d, the Eclipse obje object ct is deployed deployed without checking its radio class, and the object may be incorrect. If it is wrong, you will see an Invalid Deployment event in the Event Browser. This indicates that the device needs to be deleted and redeployed as the correct radio class. NOTE: To deploy an Eclipse Edge device, deploy it as an IDU; to deploy an Eclipse IRU 600, deploy it as an Eclipse INU. 614-330055-001 DECEMBER 2015 117 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES NOTE: In addi addition tion,, Administrator-l Administrator-l evel users can auto-discov auto-discov er and deploy Eclipse devices with Network Auto-Discovery. See Network Au t o- D i s co v ery fo r D ev ic es on p a g e 1 4 8 . Procedure 1. Identify the IP addresses for the Eclipse devices. Object. The 2. In the Tree Viewer, right-click an existing container and select Deploy Object. Deployment window displays. Select the Eclipse icon. The Eclipse device options are displayed. 3. Select the Eclipse device that you require. Enter the values for it as follows: Eclipse Node or Terminal (INU / INUe / IDU) Ensure the correct parent displays; the device is placed under the listed parent. In the Name field, type a descriptive name for the radio.The radio is labeled with this name in the User Interfa Interface. ce. Enter the radio’s IP address. Both IPv4 and IPv6 addresses are valid. To have ProVision start managing the radio, select the Manage checkbox. Select the checkbox for Perform Class Checking on Deployment. This checks that the radio class matches the device deployment window data. If the device deployment data does not match the actual radio class, an error message displays: Click OK. Then, click Back and select the correct device type. 118 AVIAT NETWORKS PROVISION USER MANUAL Protected Eclipse Node Ensure the correct parent displays; the device is placed under the listed parent. In the Name field, type a descriptive name for the radio.The radio is labeled with this name in the User Interfa Interface. ce. In the Name field, note whether the radio is an IDU ES or an IDU GE. Enter the A radio’s IP address. Enter the B radio’s IP address. Both IPv4 and IPv6 addresses are valid. To have ProVision start managing the radio, select the Manage checkbox. 4. When an Eclipse Node is deployed within ProVision, the Eclipse INU icon displays in the Tree Viewer, and the basic INU chassis displays in the Map Viewer. 5. When an Eclipse Node is managed, ProVision queries the radio to determine its component layout, and populates the chassis with the results. Figure 4-1. Eclip Eclipse se Node that that is deployed deployed but but not managed managed NOTE: When an Eclipse device is fully deployed, ProVision captures all of its plug-ins plug-ins and IP address es. This This pr ovides support for r edun edundant dant NMS connections. connections. 614-330055-001 DECEMBER 2015 119 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES DXR 200 and DXR SMA Device Deployment DXR 200 is a legacy device. To view information about DXR 200 in ProVision, they must be managed with an SMA. DXR 200 devices communicate through an SMA Proxy. When an event occurs on a DXR device: l The DXR DXR device communicates communicates with the SMA. l Then, the SMA SMA sends an SNMP event event to ProVision over etherne ethernet. t. DXR 200 devices must be communicating with their SMA to send data to ProVision. If the DXR cannot connect to an SMA, ProVision will not receive data from the DXR. Up to 4 DXR devices can be directly connected to one SMA. However, a DXR can be connected to a network of up to 255 other DXRs. You can view SMA device d evice configurations via the Configuration Manager and a nd the Management Viewer. Because DXR 200 is a legacy device, limited information is available through ProVision. The available ProVision functions for DXR 200 devices are: Presence Polling, Event Collection, and Configuration Viewer. Configuration Viewer is especially useful for the DXR slot configuration. The DXR SMA SMA provides provides the network communications communications for the DXR 700 radios. When you deploy a DXR SMA you also have the option to discover the connected DXR terminals. The figure below shows a DXR SMA deployed in ProVision. This example is not yet Managed, and its DXR 700 terminals are not discovered. A DXR SMA can ca n have a maximum maxim um of four DXR 700s connected. connected. Figure 4-2. DXR SMA rad radio io deployed in ProVision, ProVision, but but not Managed Managed Procedure CAUTION: You Y ou must deploy th the e SMA before before you deploy a DXR device, device, because p part art of the the device deployment deployment process involves selecting selecting an SMA. To deploy an SMA device, and link it to DXR 200 devices, do the following: 120 AVIAT NETWORKS PROVISION USER MANUAL 1. In the Tree Viewer, right-click an existing container and select Deploy Object. Object. The Deployment window displays. 2. Select the DXR icon. The DXR device options are displayed. 3. Select Select the DXR SMA device icon. icon. The Deploying DXR SMA SMA window displays. d isplays. Device Deployment Window Steps Check the Parent field. Ensure the correc correctt parent displays in this field. The device is placed under the parent listed. In the Name field, type a descriptive name for the radio.The radio displays with this name. Press the Tab key and type in the radio’s IP address. To have the SMA discover its DXR terminals, select Discover DXR Terminals. To have ProVision start managing the radio, select the Manage checkbox. Click Next. Then, on the window that displays, select Deploy. The Deploying SMA results window displays. Select Close. 4. After you have created the SMA, you are ready to set up the DXR 200 devices. 5. In the Tree Viewer, go to the container that includes the SMA. Right-click it and select Deploy Object. Object. 6. The Deployment window displays. Again, click on the DXR icon. In the DXR Family screen, and select DXR 200. The Deploying DXR 200 window displays. Device Deployment Window Steps Ensure the correct parent displays; the device is placed under the parent listed. In the Name field, type a descriptive name for the radio.The radio is labeled with this name in the User Interface. Press the Tab key and type in the radio’s Network Port, which will be one of the values A through D on the SMA. Enter the Terminal Number of the DXR terminal. To have ProVision start managing the radio, select the Manage checkbox. Click Next. Select Deploy. The Deploying DXR 200 results window displays. Select Close. The Proxy List displays. Select the DXR SMA that will be the proxy for this DXR 200. 7. Select Deploy. The Deploying DXR 200 results window displays. 8. Click Close. The DXR 200 is now deployed. 614-330055-001 DECEMBER 2015 121 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES CAU (Control Alarm Unit) Deployment A Control Alarm Unit (CAU) is a site management unit providing alarm/status alarm/sta tus inputs input s for monitoring devices. It can provide remote command outputs for controlling devices. The communication ports on the CAU carry controls and inputs to the connected devices. The CAU is normally used with TRuepoint and MicroStar radios, to connect them to transmission equipment that is not directly compatible with Aviat Networks standards. NOTE: The CAU is configured and installed using instructions in the CAU - Control Alarm Unit Instruction Manual, P/N IMN-099945-E06, provided with the CAU. Prerequisite For each CAU you are deploying in ProVision, you must find that device in FarScan and set up ProVision’s IP address as the manager of that device. This is required to manage a CAU from ProVision. See the FarScan Op erator manual for further further details. Procedure 1. Identify the IP addresses for connecting the CAUs. 2. In the Tree Viewer, right-click an existing container and select Deploy Object. Object. The Deployment window displays. Select the Other Microwave icon. The Other Microwave Mic rowave device options are displayed. 3. Select Select the CAU C AU device option. 4. The Deploying CAU screen displays. Enter the values for a CAU, as follows: Ensure the correct parent displays; the device is placed under the parent listed. In the Name field, type a descriptive name for the CAU device. It is labeled with this name in the User Interface. Enter the IP address. address. The Read Community string has the default value. Only change it if the radio setting has been changed. The Read and Write Community strings must match the strings entered into the radio. Select the Manage checkbox. 5. The CAU and its status can now be viewed from ProVision. 6. To set up the CAU further, Configuration Profiles for Bulk Configuration on page 201 122 AVIAT NETWORKS PROVISION USER MANUAL Cisco Deployment Before you deploy a Cisco device in ProVision, you must set up device trap hosting for the ProVision ProVision server server using the CLI C LI commands for the device. device. This enab enables les device comcommunication with ProVision. ProVision. This is re requir quired ed for all Cisco devices: l Cisco 2400/3400 2400/3400 l Cisco ASR 903 l Cisco ASR 1000 l Cisco Catalyst 2950/2 2950/2960 960 l Cisco ME ME 3600/3650/3 3600/3650/3800 800 l Cisco 3900 l Cisco ME 3600X/Cisco 3600X/Cisco ME 3800X 3800X l Cisco MWR 2941 l Cisco SNS SNS 3495 Follow these instructions for each Cisco device you need to manage with ProVision. NOTE: For more details details s ee individu individual al Cisco documentation. documentation. Procedure 1. Obtain Obtain the IP IP address address of the P Pro roVisi Vision on serve serverr you will use to manag managee the device. 2. Telne Telnett into into the Cisco device device.. 3. Add the Pr ProVisio oVision n server server IP address. address. Use the follo following wing commands to add and save the IP address of the ProVision server. enable config conf ig termi terminal nal snmp-serv snmp -server er commu community nity publi public c ro snmp-serv snmp -server er commu community nity priva private te rw snmp-serv snmp -server er queue queue-leng -length th 100 snmp-serv snmp -server er enabl enable e traps snmp-s snm p-serv erver er hos host t <Pr <ProVi oVisio sion n IP add addres ress> s> ver versio sion n 2c public public snmp-s snm p-serv erver er tra trap p lin link k iet ietf f 4. Exit the CLI comman command d windo window w for for the devi device ce.. 5. Lo Log g into Pr ProVi oVisio sion n and deploy deploy the device device.. 614-330055-001 DECEMBER 2015 123 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Constellation Device Deployment Introduction Constellation devices Constellation devices are deployed using the standard sta ndard Deployme Deployment nt procedure procedure in ProVision. After they are deployed, a Constellation discovery agent identifies the radios, and notes their type. There are two types of Constellation radio: Type Definition Terminals Terminals have o ne link. They can be protected or unprotected. Tree Viewer Display Protected link = Unprotected link = Repeaters Repeaters have two t wo links. They can have both links protected, both links unprotect unpr otected, ed, or they can have one link protected and one link unprotected. The procedure below is an overview of the Constellation deployment process. Read Standard SNM SNMP P Device Deployment Deployment on page pa ge 112 for full details. NOTE: Con Constellation stellation for Far Scan is deployed in ProVision with limited functionality. It does not have the following: * Performance data collection (resulting in no no perfor mance thresholds or trends recorded) * Network Health R eport * Full functionality functionality for the Inventory Inventory Report, Diagnostic Diagnostic Controls, and Configuration Viewer Performance data collection for Constellation is is only supported for the following variants: 3DS3, 4DS3, and 155mbit. Prerequisite For each Constellation device you are deploying in ProVision, you must find that device in FarScan and set up ProVision’s IP address as the manager of that device. This is required to manage a Constellation device from ProVision. See the FarScan User manual for further further details. 124 AVIAT NETWORKS PROVISION USER MANUAL Procedure 1. Identify the IP addresses for the Constellation radios. Object. The 2. In the Tree Viewer, right-click an existing container and select Deploy Object. Deployment window displays. Select the Other Microwave icon. The Constellation Constellation device option is displayed. Select the Constellation option. The Deploying Constellation screen displays. Enter the values for a Constellation Constella tion radio, as follows: Ensure the correct parent displays; the device is placed under the parent listed. In the Name field, type a descriptive name for the Constellation device. It is labeled with this name in the User Interface. Enter the IP address. address. The Read Community string ha hass the default value. Only change it if the radio setting has been changed. The Read and Write Community strings must match the strings entered into the radio. To have ProVision start managing this radio, select the Manage checkbox. 3. After you have deployed all the required Constellation devices, the Constellation discovery agent automatically identifies the devices. Click on the devices in the Tree Viewer.. The devices Viewer d evices sshould hould display disp lay with their links and their protected/unprotec protected/unprotected ted status. 4. The Constellation devices are now fully deployed and managed from ProVision. NOTE: When a Constellation Constellation device is fully deployed, ProVision captures all of its IP addresses. This provides support for redundant NMS connections. CTR 8300 and 8540 Device Deployment To deploy a CTR 8300 or CTR 8540 device in ProVision, you must do the following: Set up the device pre prere requisites, quisites, as listed list ed below. below. l l Manually deploy or auto-discover auto-discover the device in Pro ProVision. Vision. 614-330055-001 DECEMBER 2015 125 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES l Configure Configure the specifi specificc device logins logins and passwords in ProVision. ProVision. Follow these instructions for each device you need to manage with ProVision. For more details see the CTR documentation. Prerequisites Before deploying CTR 8540 or cTR 8300 devices in ProVision, you must do the following: l l l Use the CLI commands to enable enable SNM SNMP P and to create create a ProVision ProVision user acc account ount with root access a ccess for the device. This enables commu communication nication with ProVision. Se Sett up the device for for syslog forwarding. forwarding. To do this, either either run the command loggin log ging g <PV ser server ver IP> on the CTR device, or set this up via the CTR Configuration profile in ProVision. See the Configuration Profile Reference on page 206. 206 . Make sure that the system running Pro ProVision Vision (Solari (Solariss or any other other OS), has no process using port 514. See Changing Syslog Server Port in the Installation and Administration Manual. Procedure 1. Configure the following on each device, using the CLI. See the manual CTR CLI Reference Ref erence for details. a. Enable SNMP and co configure nfigure the SNMP read/write community strings. Use the following commands to enable SNMP for the device and note that: l l l We rec recomme ommend nd using the same values on each CTR 8540 8540 or CTR 8300, 830 0, simplifying the configuratio configuration n and maintenance maintenance of passwords on ProVision. This also provides the ability to use network auto discovery. For improved improved security, we also recommend recommend using a differ different ent valu e from the commonly used “public” / “private” values. value The followin following g example indicates the CLI commands requir required ed to enable enab le SNM SNMP P and configure configure read read community string value “public1” and write community string value “private1” on a CTR device: aos# confi configure gure termi terminal nal aos(config aos(c onfig)# )# snmpsnmp-serve server r view all 1 incl included uded aos(config)# aos(config )# snmpsnmp-serve server r commu community nity public1 public1 version version both read all notify notif y all aos(config)# aos(config )# snmpsnmp-serve server r commu community nity private1 private1 versi version on both read al all l wr writ ite e al all l no noti tify fy al all l aos(config aos(c onfig)# )# confi config g save aos(config aos(c onfig)# )# end b. Create a provisi provision on user ac account count wi with th root access. Use the following commands to create a ProVision user account with root (privilege level 15) access. ProVision needs this account to automatically log into the device to 126 AVIAT NETWORKS PROVISION USER MANUAL perform operations such as event collection, configuration backup and software download. Passwords must be between 8 and 32 characters long and contain at least one letter, one number, and alpha-numeric character, and at least one lower and one upper case character. A new password must have at least 4 characters different from the old password l l For ease ease of management access under Pro ProVision Vision we recommend recommend that a common user name, such as 'provision', and a shared password for the user name, is used on all CTR devices to be managed. The followin following g example indicates the CLI commands requir required ed to configure conf igure a user account account called ‘provision’ ‘provision’ w ith the appropr ap propriate iate level of access: aos# confi configure gure termi terminal nal aos(confi aos( config)# g)# user username name provi provision sion passw password ord <pass <password> word> privilege privilege 15 aos(confi aos( config)# g)# conf config ig save aos(confi aos( config)# g)# end 2. Ensure that all changes are backed up to secure storage. Exit the CLI command window for the device. 3. Deploy the de device vice in P ProVisi roVision. on. Perform the following in ProVision: a. Wher Wheree a common common “provisio “provision” n” user user account account password password has been been applied, configure the device login in ProVision at the root network container. See Setting Device Security Account Values. b. Log into ProVision a and nd deploy the CTR 8540 device, as described in Standard SNMP Device Deployment on page 112. 112. Devices can also be found via autodiscovery: see CTR Device Support on page 18. 18. c. Where Where unique unique “provision “provision”” user user account account passwords have been been applied, configure the device login in ProVision as each device is deployed. deployed. See Setting Device Security Security Account Values. Values . d. Pr ProVi oVisio sion n can now now communic communicate ate fully fully with the CT CTR R 85 8540 40 device. Auto-discovery of RF and Ethernet Links When upgrad upgrading ing software on CTR 8540 or CTR C TR 8300 from release 2.x to release 3.0 release, the LLDP protocol is erroneously disabled by the embedded sof s oftware. tware. This re results sults in ProVision ProVision being being unable t o au to-discover to-discover RF links and Ethernet links. To solve this problem, the user needs to enable LLDP on the CTR device through executing executing the following CLI commands: c t set lld lldp p ena enable ble 614-330055-001 DECEMBER 2015 127 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Auto-discovery of Linked WTM Devices If a CTR 8540 device is connected to a WTM device via the POE or an Ethrnet port, ProVision automatically discovers the ink and deploys the WTM radio as a child object of the parent CTR. The auto-discovered WTMs display as child devices in the Tree Viewer: And as links in the details of t he Map viewer: viewer: Genericc Device Deployment Generi Deployment Generic devices can be SNMP or IP based, non-Aviat Networks devices. This allows you to deploy required devices, either as SNMP or IP devices, provided they are SNMP/IP compliant. ProVision also presence polls them, using either an SNMP or an ICMP ping. The generic devices are categorized in ProVision as: l Generic Devices l Multiplexer l Router l Switch l Microwave Microwave Radio l Power Supply l Alarm Unit l Base Station 128 AVIAT NETWORKS PROVISION USER MANUAL l Timing System l Server l Firewall l Air Condit Conditioner ioner l Symbol Symbol = Device that has no managed status, can sele select ct custom icon icon To create a generic device, you enter both standard deployment details and a Support Package name. The Support Package name helps ProVision to manage types of devices. Similar or related related device devicess can be grouped grouped in the same Support Support Package Package.. NOTE: If a G eneric Device is an IP device, its support is limited at this this time to being being pres ence polled. W AR NI NG : When you deploy a generic device, you, or an advanced- level user, must also set up the generic device event collection. This function fun ction requires an addition additional al Pr oVision module license. This This is documented in the Installation and Administration Guide . If you are working with an advanced-level user to deploy generic devices, please provide them with all the device details: name, type, IP address, and Browser and Telnet port settings. Procedure Device Deployment Windows S t e ps Select the Generic Device Type that best describes the device. Then, click Next. 614-330055-001 DECEMBER 2015 129 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Device Deployment Windows S t e ps Enter the values for the device in this screen: Ensure the correct parent displays; the device is placed under the parent listed. Press the Tab key and type in the device’s IP address. address. The Browser and Telnet Port settings are the default, only change these if required. Some devices have an SSH Port setting. Select the Communications type for the device, SNMP or IP. To have ProVision start managing the device, select the Manage checkbox. Click Next Next.. For the steps below, the Generic Device module license is required. For For an S NMP Device only, ass assign ign the Read Community and Write Community strings, and the SNMP Version. Version. The Read Community string has the default value. Only change it if the radio setting has been changed. The Read Community strings must match the strings entered into the radio. Assign a Support Pack Package age name. Select a Support Package from the Package drop-down menu, or enter a Support Package name in the New Package Name field. If you enter a new Support Package name, it is available in the Package menu. If you select an existing Support Package, it needs to match the device Communication municat ion type, SNMP or IP. Click Deploy. The new device is deployed. If you are deploying a Symbol device, first, you are prompted to enter a Symbol name. Then you are asked to select a custom icon. This is not required. Icons can be .jpg, .bmp, or .png graphics up to 2.4 MB in size. ProVision will automatically resize the icon. Any icons you enter are saved for later re-use. See About User Defined Icons on page 91 130 AVIAT NETWORKS PROVISION USER MANUAL Proxy You and Network Element Deployment can connect ProVision to another Element Management System (EMS) to t o make this visible within ProVision. This typ typee of EMS is called a Proxy. After you have deployed a Proxy, you can assign Network Elements to the Proxy. This manages devices that ProVision cannot connect to because the Network Element devices do not have SNMP. Prerequisite For each EMS Proxy you are deploying in ProVision, you must obtain the IP address, port data (for browser, telnet, and SSH), and Communications type. Procedure 1. In the Tr Tree ee Viewer Viewer,, right-click right-click an existing containe containerr or t he Root and select select Deploy Object.. Object 1. The Deployment window displays. Select the EMS/Proxy device option. 2. Select whether you want to deploy an EMS or a Proxy. NOTE: You should deploy the the EMS fir st, and then deploy deploy its network el e- ments as Proxies. 3. The Deploying screen displays. 4. Enter the values for the EMS: 614-330055-001 DECEMBER 2015 131 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Ensure the correct parent displays; the device is placed under the parent listed. In the Name field, type a descriptive name for the EMS It is labeled with this name in the User Interface. Enter the IP address. address. Enter the Browser Port. Port. Enter the Telnet Port. Port. Enter the SSH Port. Port. Select the Communications type from the drop-down menu. Only select the Manage checkbox if this EMS is to be managed. If required, you can use a custom icon. To activate this, click the Use Custom Icon check box and select the icon. Select the Support Package for the EMS Proxy. If you have loaded loaded Generi Genericc Device Pack Packages ages previously, these will display in the Package dropdown menu as options. You can also type in the name in the New Package Name field. 132 AVIAT NETWORKS PROVISION USER MANUAL Select the SNMP option for the EMS.Options include v1, v2, and V3. The Read Community and Write Community must match the strings entered into the radio. 5. To deploy a Network Element: In field, type a It descriptive forthe the Name Network Element. is labeled name with this name in the User Interface. Enter the Network Element ID. ID. Only select the Manage checkbox if this EMS is to be managed. The Managed state is inherited from the EMS in the next step. 614-330055-001 DECEMBER 2015 133 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES If required, you can use a custom icon. To activate this, click the Use Custom Icon check box and select the icon. If this is not required, click Next. From the Proxy list, select the EMS Proxy that this will be linked to. 134 AVIAT NETWORKS PROVISION USER MANUAL Select the Type for the Network Device. If you have loaded a Type previously, these will display in the Type drop-do drop-down wn menu as options. You can also enter a new Type name in the Type Name field. 6. The EMS Proxy and its Network Element Devices can now be viewed from ProVision. W AR NI NG : Se e Managing Proxy Configuration on page 163 to reassign Network Element Devices if required. Symmetricom TP1x00 Deployment To fully deploy a Symmetricom TP1x00 (1000, 1100) device in ProVision, you must note a value from the Symmetricom craft tool for the specific Symmetricom device. You need to add a new Principal, and use the Principal user name to configure the device SNMP options when deploying it in ProVision. Procedure 1. Obtain the IP address of the ProVision server you will use to manage the device. 2. Open the Symmetricon craft tool, TimeCraft. 3. In the left frame, select SNMP Parameters. Then, in the main screen, go to the SNMP Pri Principa ncipals ls Configuration frame. 614-330055-001 DECEMBER 2015 135 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES 4. Click on the button New Principal and enter the values for a New Principal. Select the SNMP version from the Type and select the Access. Enter the principal Name a ass shown below. Then, click OK. 5. On the SNMP Trap Configuration panel click the Edit button; the Edit Trap Settings screen displays. Select the Principal Name from the drop down list. Assign the principal princ ipal name to the IP Addre Address ss of the Pro ProVision Vision serve server. r. Then, click OK. 6. The New Principal appears in the SNMP Principals Configuration and the SNMP Trap Configuration as shown below (highlighted in red). 136 AVIAT NETWORKS PROVISION USER MANUAL 7. Exit TimeCraft and log into ProVision. 8. Deploy the new Symmetricon device in ProVision using the Standard SNMP Device Deployment on page 112. 112. In the Deployment screen for SNMP options, add the user name from step 3 as the Read Community in ProVision. Then, click Deploy. 9. The Symmetricom TP1x00 device is deployed and fully managed by ProVision. Symmetricom TP5000 Deployment Before you deploy a Symmetricom TP5000 device, you must set up a read community string value using the C LI commands for the device. device. This enables enables device comcommunication with ProVision. ProVision. Follow Follo w these instruc instructions tions for each Symmetricom Symmetricom TP5000 TP5000 device you need need to manage with ProVision. 614-330055-001 DECEMBER 2015 137 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES NOTE: For more details see the Symmetricom TP5000 document, TimeProvider 5000 IEEE 1588 Grand Master Clock User’s Guide, Part Number 098-00028-000-rev-d . Procedure 1. Obtain Obtain the IP IP address address of the P Pro roVisi Vision on serve serverr you will use to manag managee the device. 2. Te Telnet lnet into into the Symmetricom Symmetricom TP5000 TP5000 device. device. 3. Add the Pr ProVisio oVision n server server IP address. address. Use the follo following wing commands commands to add and display the IP address of the ProVision server. set snm snmp p add man manage ager r <ip <ip-ad -addre dress> ss> show sho w snm snmp p man manage ager r 4. The SN SNMP MP Man Manage agerr displays. 5. Type th thee follow following ing commands commands to add the “r “rea ead d commun community” ity” string string (groupv2 in the example shown below; the community name is assigned to the manager ID with the same index ). set snmp add v2-c v2-commun ommunity ity grou groupv2 pv2 secur secureLv1 eLv1 read-writ read-write e show snmp v-2 commu community nity 6. This This confi confirms rms that you can read read and wr write ite to the co communi mmunity ty string. string. The Community Name (groupv2) is used as the read community string for deploying TP5000 in ProVision. 7. Exit the CLI comman command d windo window w for for the devi device ce.. 8. Lo Log g into Pr ProVi oVisio sion n and deploy deploy the device device.. TRuepoint Device Deployment To deploy a TRuepoint device in ProVision, it must be deployed, then configured using the Configuration Profiles function. TRuepoint devices must communicate with a ProVi- sion trap and a ProVision SNMP manager to send data to ProVision. The procedure below is an overview of the required process. It describes how to deploy the following TRuepoint devices: 6400, 5000, 2+0, 4040, 4040/2, and 4000. See also TRuepoi uepoint nt 6500 Device Deployment Deployment on page pa ge 142. 142. TR 138 AVIAT NETWORKS PROVISION USER MANUAL Read Standard SNMP Device Deployment on page 112 and Configuration Profile Reference on page 206 for full details. NOTE: For TRuepoint 4040 v2 and 5000 devices with V2 V2 controllers , an addition addi tional al ProVision function function enables you to apply SNMPv3 privacy/ encryption. encryption. To do this this using the algorithm algorithm types of TDES, AES128, or, for US customers only, AES192 and AES256, your ProVision system requires: * A specific ProVision feature license. * A Java cryptography extension (JCE unlimited strength ju jurisdiction risdiction policy file/s) from Sun Microsystems. Contact Con tact your Aviat Networ ks r epresentative epresentative to obtain this this l icense and this extension. Prerequisite To do this, you need access to both ProVision and WebCIT, the TRuepoint craft tool, for the TRuepoint devices. For each TRuepoint device you are deploying in ProVision, you must find that device in WebCIT Web CIT and set up ProVision’s IP address add ress as the manager of t hat device. This is required to manage a TRuepoint device from ProVision. See the Procedure below for specific instructions. Procedure 1. Identify and record the IP address of your installation of ProVision. See Determining the Server’s IP Address in the Installation and Administration Manual for complete instructions. 2. Identify all the TRuepoint devices you want to deploy in ProVision. 3. Log into WebCIT. For each TRuepoint device noted in step 2: l l l Go to the Provisioning screen, in Network Setting 2. Se Sett the value SNMP Manager to the ProVision IP address identified in step 1. See the WebCIT Operator manual for further details. Save the changes. changes. 4. Once steps 2 and 3 are completed for each TRuepoint device, log into ProVision. 5. Identify the IP addresses for connecting TRuepoint devices to ProVision via a ProVision trap and a ProVision SNMP manager. 6. In the Tr Tree ee Viewer, Viewer, right-click an existing container container and sele select ct Deploy Object. Object. The Deployment window displays. Select the TRuepoint icon. The TRuepoint device options are displayed. 7. Select the TRuepoint device that you require. Enter the values for it as follows: 614-330055-001 DECEMBER 2015 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES TRuepoint 4000, 4040, and 6400 Ensure the correct parent displays; the device is placed under the parent listed. In the Name field, type a descriptive name for the TRuepoint device. It is labeled with this name in the User Interface. Enter the IP address. address. The Read Community string has the default value. Only change it if the radio setting has been changed. The Read and Write Community strings must match the strings entered into the radio. To have ProVision start managing this radio, select the Manage checkbox. Select Deploy. The Deploying TRuepoint results window displays. Click Close Close.. The radio is now deployed. TRuepoint 4040 v2, 5000, and 5000 2+0 Ensure the correct parent displays; the device is placed under the parent listed. In the Name field, type a descriptive name for the TRuepoint device. It is labeled with this name in the User Interface. Enter the IP address. address. To have ProVision start managing this radio, select the Manage checkbox. Click Next Next.. Select the SNMP Version. Version. If you select Version v2c, the Read and Write Community options display. The Read and Write Community strings must match the strings entered into the radio. 139 140 AVIAT NETWORKS PROVISION USER MANUAL If you select Version v3 for the SNMP version, further options display. If required, check the box to Use Inherited Security Account from the parent container. Enter a Username. This is associated with the two passwords below. Authentication:: This selects the algorithm Authentication used for this device’s data. Select a Type Type,, and enter a Password and a Confirmation for the password. Privacy: This selects the encryption algorith algorithm m used for this device’s data data.. Selec Selectt a Type Type,, enter a Password and a Confirmation for the password. The Authentication and Privacy types are determined by your organ organizat ization’s ion’s network policy. policy. An Authen Authentica tication tion of MD5 and a Privacy of AES128 is a common “strong security” combination. To change or view SNMPv3 credentials on a TRuepoint radio, see the TRuepoint 5000/4040 500 0/4040 Operator’s Interface Interfa ce Manual, IMN-903003-E07 IMN-9030 03-E07. There are two ways to change cha nge these credent credentials ials.. One is using WebCIT, WebC IT, log logging ging in as the administrator user and setting the authentication and privacy passwords. The other way is using third-party SNMP tools, such as MGSoft and NetSNMP. Click Deploy. The TRuepoint radio is now deployed. 8. For 4040, 5000, and 6400 radios, there is an extra step. After you have deployed all the required radios, select them in the Tree Viewer. In the menu bar, go to the Configuration menu and select Configuration Profile. 9. In the Configuration Profiles screen, select the TRuepoint 6400/5000/4000/4040 Managers option for the TRuepoint radio type. Enable the option and enter the SNMP manager IP address; this is the ProVision IP address identified in Step 1. 10. Select the TRuepoint 6400/5000/4000/4040Trap Destination option for the TRuepoint radio type you have deployed. Enable the option and enter the trap destination IP address; this is the same as the SNMP manager IP address in step 9. 614-330055-001 DECEMBER 2015 141 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES 11. Save and apply the Configuration Profile settings, as documented in Configuration Profile Reference on page 206. 206 . 12. The TRuepoint devices are now fully deployed and managed from ProVision. NOTE: TRuepoint 6400 requires an additional procedure to enable its alarm resynchronization; see Configure TRuepoint 6400 Alarm Resynchronization on page 308. 308 . NOTE: When a TRuepoint TRuepoint device is fully deployed, ProVision captures captures all of its IP addresses. This provides support for redundant NMS connections, nection s, as s hown in this this diagram below: TRuepoint 6500 6500 Device Deploy Deployment ment You can deploy and manage TRuepoint 6500 devices in ProVision. In ProVision, TRueTRuepoint 6500 devices differ from other ot her TRuepoint devices. They have a unique Performance History display; display; their event collection is trap-based; trap-bas ed; and their alarms are synchronize synchronized d History display; their event collection is trap based; bas ed; and their alarms are synchronize synchronized d automatically after state changes. More information informat ion is included throughout this documentation, particularly particularly for Managing SMA and DXR Devices on page 165. 165. There are two types of TRuepoint 6500 devices: 142 AVIAT NETWORKS PROVISION USER MANUAL Type Definitio n Standard Standard TRuepoint 6500 radio. Tree Viewer Display Double Ter- This type includes 2 minal supervisory terminal units. The procedure below is an overview of the required process. It describes how to deploy TRuepoint 6500 and TRuepoint 6500 double terminal devices. For more information, read Standard SNMP Device Deployment on page 112. 112. Prerequisite For each TRuepoint device you are deploying in ProVision, you must find that device in WebCIT Web CIT and set up ProVision’s IP address add ress as the manager of t hat device. This is required to manage a TRuepoint device from ProVision. This setting is found in WebCIT via the Provisioning screen, in Network Setting 2, as the value SNMP Manager #1. See the WebCIT Operator manual for further further details. Procedure 1. Identify Identify the IP addresse addressess for connec connecting ting TRuepoi TRuepoint nt devices devices to ProVisio ProVision n via a ProVision trap and a ProVision SNMP manager. 2. In the Tree Viewer, right-click an existing container and select Deploy Object. Object. The Deployment window displays. Select the TRuepoint icon. The TRuepoint device options are displayed. 3. Select the TRuepoint 6500 device that you require, Standard or Double Terminal. Enter the values for it as follows: 614-330055-001 DECEMBER 2015 143 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES TRuepoint 6500 Ensure the correct parent displays; the device is placed under the parent listed. In the Name field, type a descriptive name for the TRuepoint device. It is labeled with this name in the User Interface. Enter the IP address. address. The Read Community string has the default value. Only change it if the radio setting has been changed. The Read and Write Community strings must match the strings entered into the radio. To have ProVision start managing this radio, select the Manage checkbox. Select Deploy. The Deploying TRuepoint results window displays. Click Close. The TRuepoint radio is now deployed. TRuepoint 6500 Double Terminal Ensure the correct parent displays; the device is placed under the parent listed. In the Name field, type a descriptive name for the TRuepoint device. It is labeled with this name in the User Interface. The Read Community string has the default value. Only change it if the radio setting has been changed. The Read and Write Community strings must match the strings entered into the radio. For each of the two terminals, enter the IP addresses. To have ProVision start managing this radio, select the Manage checkbox. Select Deploy. The Deploying TRuepoint results window displays. Click Close. The TRuepoint radio is now deployed. 4. After you have deployed the TRuepoint 6500 radio, ProVision immediately discovers cove rs the device co configur nfiguration ation and presents presents the discovere discovered d plug-ins. This is done automatically, as a background task. The terminals display in the Tree Viewer, with the discovered plug-ins displaying as child objects in the Tree Viewer. 5. The TRuepoint devices are now fully deployed and managed from ProVision. TNet Device Deployment TNet devices communicate with a TNet Proxy using TNet protocol over TNet cabling. The TNet Proxy communicates with ProVision using SNMP over ethernet. Due to 144 AVIAT NETWORKS PROVISION USER MANUAL performance issues it is recommended that no more than 500 TNet devices are allocated to a single TNet Proxy. ProVision supports up to 3000 TNet devices. When an event occurs on a TNet TNet device, an SNMP SNMP event is sent by the TNet TNet Proxy to ProVision. Within ProVision, TNet TNet devices are typica t ypically lly deployed under the location (region, (region, site or rack) at which they are physically deployed. This is not necessarily the same location at which the TNet TNet Proxy is deployed, as shown in the following screen. screen. You can view Proxy, subnets, and TNet TNet device configurations via the Proxy Configuration Manager. See Viewing/ Viewing/Changing Changing TN TNet et Proxy Configur Configurations ations on page 218. 218. NOTE: TNet Web requires Java 1.7. About TNet Proxies A TNet TNet Proxy is a dedicated Windows NT Server connected to the ProVision serve s erverr over a LAN. The TNet Proxies communicate with ProVision using SNMP. TNet Proxies communicate with managed TNet devices through a serial interface, either directly or through a terminal server. A TNet Proxy converts SNMP requests from ProVision to the TNet protocol to communicate with the TNet devices. This is an overview of how ProVision interacts with the TNet Proxies and the TNet devices. 614-330055-001 DECEMBER 2015 145 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Figure 4-3. ProV ProVisi ision on and a TNet TNet Network Network Procedure CAUTION: You must deploy deploy the the TNet Proxy Proxy before before you deploy deploy a TNet TNet device, device, because part of the the device deployment deployment process involves selecting selecting a TNet Proxy. 1. Within the Tr Tree ee Viewer, Viewer, right-click an existing container, container, for example, the network icon and select Deploy Object. The Deployment window displays. 2. Select the TNet icon. The TNet devices are displayed. 3. Select the required device icon. 4. The Deploying <device < device name> name> window displays. Enter the values for the new device,, as descr device describe ibed d for specific specific device types listed in the table ta ble below. below. 5. Select Deploy. The Deploying <device < device name> name> results window displays. 146 AVIAT NETWORKS PROVISION USER MANUAL 6. To close the Deploying <device < device name> name> window, select Close. Table 4-3. Device Deployment Deployment Details Details for TNet TNet Devices Device Deployment Window S t e ps TNet Proxy ProVision can manage up to ten TNet Proxies. Each proxy can support up to 16 radio subnets (0 to 15). Ensure the correct parent displays; the device is placed under the parent listed. In the Name field, type a descriptive name for the TNet Proxy. The TNet Proxy is labeled with this name in the User Interface. Press the Tab key and type in the TNet Proxy’s IP address. The Read Community string has the default value. Only change it if the radio setting has been changed. The Read and Write Community strings must match the strings entered into the radio. Enter the total number of Subnets for this proxy. To have ProVision start managing the TNet Proxy, select the Manage checkbox. All Other TNet Devices Ensure the correct parent displays; the device is placed under the parent listed. In the Name field, type a descriptive name for the radio. The device is labeled with this name in the User Interface. Press the Tab key and type in the subnet number (Subnet #). The valid range is 0 - 15. For all TNet radios other than SPECTRUM II the valid radio address range is 0 - 223. For SPECTRUM II radios the valid radio address range is 256 - 1279. Press the Tab key and type in the radio address. To have ProVision start managing the TNet device, select the Manage checkbox. Select Next. The Proxy List displays. Select a TNet Proxy from the list displayed. Select Deploy. The Deploying <device <device name> name> results window displays. To close the Deploying <device < device name> name> window, selec selectt Close. The table below below lists the TNet device deployment/manageme deployment/management nt problems problems that tha t can occur occur between between ProVision and a nd the TNet TNet Proxy, and the suggested solutions. Table 4-4. ProV ProVisi ision on an and d TNet Proxy Proxy - Device Device Deployment Deployment Discrepan Discrepancies cies 614-330055-001 DECEMBER 2015 147 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Depl eploy oym ment ent Discr screpa epancy Sol Soluti tion on Radio deployed in ProV ProVisi ision on but See below, Manually Deploying a TNet Device not deployed in the Proxy. into the Proxy . Wrong radio type in either ProVi- Delete the radio from ProVision. sion or the Proxy. This also deletes the radio from the Proxy. See Deleting a Device on page 154 Deploy and manage the radio in ProVision. The radio is automatically deployed into the Proxy. Radio deployed in the Proxy but Deploy and manage the radio in ProVision. not deployed in ProVision, and Delete the radio from ProVision. the radio is not required. This also also deletes the radio from the Proxy. Manually Deploying a TNet Device into the Proxy When a TNet TNet device is deployed and managed manag ed in ProVision, the radio data dat a including the radio subnet, address and type is written to the TNet Proxy. In certain circumstances data is not written to the Proxy, for example, when you are deploying a TNet device and communications communic ations are lost between ProVision and the Proxy. As a result, the TNet device displays in ProVision ProVision in the connec connecting ting state ten to the Proxy database. because because the device details we were re not wr writit- You can confirm confirm whether or not the TNet TNet device details have bee been n written to the Proxy, via the Proxy Viewer. Viewer. See Using t he TNet TNet Pro Proxy xy Viewe Viewerr on page 220 for more information. If the TNet device is not listed in the Proxy database, you can manually deploy the TNet TNet device into the Proxy. Proxy. To manually deploy a TNet device into the Proxy: 1. Right-click the TNet device. In the right-click menu, select Deploy into Proxy. 2. The TNet device details stored in ProVision, are written into the Proxy database. Network Auto-Discovery for Devices Network Auto-Discovery is a ProVision task that polls a range of IP addresses for the following device types: l Eclipse l CTR 830 8300, 0, 8440, 8540, 8611 l Constellation l Cisco ASR 903 l TRuepoint l WTM 3100, 3200, 3200, 3300 3300 l Loaded GDS packages/devices l Generic Generic Ethernet Ethernet devices (see note) 148 AVIAT NETWORKS PROVISION USER MANUAL When you run Network Auto-Discovery, you tell ProVision which w hich IP add address ress ranges to search. sear ch. ProVision ProVision polls the IP addresse addressess and captures captures discovere discovered d device devicess in container containerss in ProVision. This is a fast way to deploy devices when applying ProVision to an existing network. Note that: Discover Discovered ed devices devices are named named with the class name of the devic devicee and the device-specific IP address. l l l l Users Users can edit the devic devicee data of all discover discovered ed device devices. s. ProVision ProVision only deploys the discovere discovered d objects objects into the specified specified Container Container.. If a Container specified for auto-discovery does not exist, ProVision will create it. You can review review the auto-deployment auto-deployment re results sults and note any error errors. s. NOTE: Generic Ethernet devices devices that h have ave pre-r egistered packages are only available for autod autodiscover iscover y if customized with a <sysobjectid> in the package by an administrator, s ee the ProVision GDS Performance Management document. Otherwise Generic devices are auto-discovered based on ifTable or ifXTable support. support. Generic Ethernet devices ar e autodiscovered in this order: registered packages, ifXTable ifXTable supported (Eth(EthernetHC), ifTable supported (Ethernet). Procedure 1. Log into ProVisio ProVision. n. 2. In the Configuration menu, select Network Auto-Discovery. The Network AutoDiscovery screen displays. 3. To enable Network Auto-Discovery, you need to enter an IP address range. You must enter at least one IP address range; you can enter multiple ones. ProVision will search for all devices in the IP address ranges. To do this: l Click Add. The Add IP Range fields display. Enter values for: 614-330055-001 DECEMBER 2015 149 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES o IP Address Range - Enter the start and end of the IP address range. This accepts both IPv4 and IPv6 addresses. o Read Community - Enter public or private, based on the device password requirements. o Container Name - range Enter will a unique Container name. All the discovered for this IP address be deployed in this container, just below devices the level in the Physical Tre Treee view. PV/Root level o If re require quired, d, check the Manage on Deployment check box. The discovered devices will be deployed in a Managed state. o If re require quired, d, check the Discover Generic Ethernet Devices box. Any discovered Generic devices that have pre-registered packages or that support ifTable or ifXTable will be deployed. l Click Add IP Range. 4. The IP Address range is added to the Discovery Ranges list. 5. Repeat steps 3 and 4 as required for each IP address range. To remove an IP range, select it and click Remove. To change an entered IP address range, select it and click Edit. The IP range displays for editing: 6. To run t he network network Auto-Discovery, Auto-Discovery, click Start Task. 7. The Task Manager display displayss the network network Auto-Discovery Auto-Discovery in p rogre rogress. ss. 150 AVIAT NETWORKS PROVISION USER MANUAL NOTE: ProVision will run the the auto-discover auto-discover y on up to 5 IP address ranges at one time. All remaining ranges will be queued an and d run as tasks. 8. When the network Auto-Discovery is complete: The new new Container is cre created, ated, and holds any discovere discovered dd devic evices. es. l l l The results results and an d errors errors of the ne network twork Auto-Discovery process process can be viewed by right-clicking on each IP address range in the Task Manager. See below for more information. You can import the results results of the network network auto-discovery auto-discovery as a .CSV file by clicking click ing the Import button. The CSV file includes the following data, without a descriptive descr iptive header: Start IP Address, Address, End IP Address, C ontainer ontainer Name, Read Read Community. Network Networ k Auto-Discover Auto-Discoveryy Results an and d Error Error Messages You can view the re results sults and err errors ors of tthe he network au auto-discovery to-discovery process. There There are four main result result messages: messages: l Object at address < <## ####> ##> success successfully fully deployed - An object was found and deployed. l Object not detected at address <# <#### ###> >- Nothing at this IP address is responding to the SNMP request; no object was found or deployed. l Object detected at address <## <#### ##> > but unable to find matching matching class - An object was found: however, ProVision is unable to identify the object type. This means the identified object is not supported by auto-discovery at this time. l Any m message essage hi highlighted ghlighted in red - A red highlight in the auto-discovery results warns you that an obje object ct has been been deployed previously in ProVision as a s the wrong class type typ e (for example, examp le, deployed as IDU but auto-dis auto-discover covery y detects it as an INUe.) You must either delete or redeploy the device. l Example of Eclipse Eclipse auto-discove auto-discovery ry results: results: 614-330055-001 DECEMBER 2015 151 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Troubleshooting Device Deployment When you deploy a device, you may rec receive eive the t he following error error messages: messag es: Exception Co rrective Action IP Address Already Allocated If you attempt to assign an IP address that has already been allocated to a device the following message displays: Select OK. The Deploying <device name> window displays enabling you to re-enter the correct IP address. Invalid IP Address If you enter an invalid IP address the Select OK and re-enter a following message displays: valid IP address. Verifying ying ProVision is Rec Receiving eiving Device Events E vents on page 157 Verif Changing a Device’s Container If you have deployed a device under the wrong container and want to move it to a different container, you can reparent the device in the Tree Viewer. If you change the device’s container, you must reposition the object in the Map Viewer. For more information, see Moving Containers and Devices in the Map Viewer on page 153.. 153 NOTE: Con Contain tainer er and device objects ar e repar ented in in the the Tree Viewer physical pane. 152 AVIAT NETWORKS PROVISION USER MANUAL NOTE: Reparenting Reparenting a TNet device w ith ithin in the the Tree Viewer is exactly the same as for other objects. However, reparenting TNet devices to a difTNett ferent TNet Proxy is a different procedure. See Viewing/Changing TNe Proxy Configurations on page 218 . Procedure 1. To unlock the tree, select the locked icon, located on the physical pane’s title bar. 2. Select the device to be moved to a different container. 3. Drag and drop the device into the required container. The device has been reparented and displays under the new container in the Tree and Map Viewers. 4. To lock the tree, select the unlocked unlocked icon. Moving Containers and Devices in the Map Viewer You may want to reposition container objects and/or devices in the Map Viewer. Viewer. You can do this, if you have enough user access. NOTE: If you mov e a linked device to another another pos ition ition on th the e map, the link moves w ith the the radio. NOTE: Moving an object object on one map view, for example, the flat vi view, ew, does not effec t the positioning positioning of the object on the other l ayer. Procedure 1. To unlock the map, select the locked icon. 2. To move an object, in the Map Viewer, select the desired object and drag it to the new position. 3. To relock the map, select the unlocked icon. Renaming a Device You can change device names for devices in ProVision. 614-330055-001 DECEMBER 2015 153 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Procedure 1. Right-click the device to be changed. The device’s right-click menu displays. 2. Select Rename on the right-click menu. The Rename Object window with the selected device’s name displays. 3. Make the required changes to the device’s name. 4. To save the changes, select OK . Deleting a Device There are three reasons to delete a device from ProVision: l A device was accidentally deployed in the wrong wrong region region or site. l The radio radio has be been en decommissione decommissioned d or replaced replaced with a d diff iffer erent ent radio type. l The radio radio is no longer bein being g managed by ProVisio ProVision. n. You can delete a device fro from m the Tree Tree Viewer V iewer or the Map Viewer. Viewer. When the device is deleted the Tree and Map Viewers refresh and the device is no longer displayed. NOTE: Deletin Deleting g a device in ProVision has has no effect on the traffic carrying capability of the device, but event generation generation is disabled in the device. NOTE: You cannot directly delete a DXR 700 radio. You have to select the DXR SMA option to Discover Terminals. For more information see Manually Discovering DXR 700 Radios on page 162 . CAUTION: WARNING: Be careful when deletin deleting g a TNet Proxy, as this this also also deletes deletes all the the associated child TNet radios in in ProVision, ProVision, and and delet deletes es the the Proxy’s Proxy’s database. database. Procedure 1. Right-click the device’s icon. The right-click menu displays 2. Select Delete on the right-click menu. A Delete Objects window displays. 154 AVIAT NETWORKS PROVISION USER MANUAL 3. To delete the selected device, select Yes Y es. 614-330055-001 DECEMBER 2015 155 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Managing Man aging This section Devices covers the following device management procedures: l Managing a Device Device on on page 156 156 l Verifying Verif ying ProVision is Rece Receiving iving Device Events on page 157 l Unmanaging a Devic Devicee on on page 158 158 l Manually Discovering Discovering WTM WTM 6000 Configuratio Configuration n on page 161 l Viewing Viewi ng Eclipse RAC RAC Low Latency Latency Links on on page 159 l Manually Discovering Discovering TRuepoi TRuepoint nt 6500 Configuration Configuration on page 162 l Manually Discover Discovering ing DXR DXR 700 Radios Radios on page 162 l Managing SMA SMA and DXR DXR Device Devicess on page 165 l Managing Pro Proxy xy Configuration Configuration on page 163 l Linking Proce Procedures dures on on page 167 Managing Mana ging a Device When you activa activate te Managed status stat us for a device in ProVision, ProVision initiates presence polling of the device. Then, an info information rmational al event event is added to t he ProVision ProVision event log, noting the radio has been commissioned co mmissioned successfully. Typically, in ProVision ProVision you manage the radio, and then link it to another radio. For a pre-deployment radio, you create the links first, and then manage the radio. NOTE: Important: This process is not applicable for Eclipse Node and DXR 700 radios. NOTE: A ProVision managed device that has not yet been inst installed alled and commiss ioned at the site is shown in ProVision with the connecting connecting icon . Procedure To activate Managed status for a single device: 1. Right-click the device to be managed. The device’s right-click menu displays. 2. Select Manage. ProVision changes the device to a Managed state. A check displays beside Managed in the right-click menu, showing that the device is Managed. To set the Managed status of two or more devices: 1. Select the device icons for all the required radios. Then, right-click. 156 AVIAT NETWORKS PROVISION USER MANUAL 2. If all the devices have the same Managed status, Manage displays in the rightclick menu. 3. If some devices are set to Managed and some are not, the right-click menu displays as follows: 4. Set the status to Managed or Unmanaged for the devices. The status that you choose is applied to all the devices. Verifying ProVision is Receiving Device Events When a device is Managed, this enables event traffic between ProVision and the device. You can verify that ProVision is receiving receiving events fro from m the device by: l Adjusting Event filtering filtering to display all events rece received ived from from a d evice: evice: or l By causing an alarm to be be raised raised b by y the radio. If ProVision is not receiving events from a device, check that the device’s IP address is correct. The device’s IP address displays in pop-up text when you place the cursor over the device’s icon in the Tree or Map Viewer. If the IP address is incorrect, you can change it. See Viewing/Changing Network IP Addresses on page 217. 217. Procedure 1. Right-click the managed device. 2. From the right-click menu, select Event Browser.The Event Browser displays. 614-330055-001 DECEMBER 2015 157 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES 3. Select the View Filters ic icon on.. The Fi Filte lterrs windo window w displ displays ays.. 4. Enable both States, Active and Closed. Enable all the Severity types. OK 5. Select . If ProVision is receiving events from the radio, these events are displayed in the Event Browser Browser window. 6. To close the Event Browser window, select the X in the upper right corner. 7. To confirm you do not want to save the changes, select No. Unmanaging a Device When a device is Managed, ProVision p polls olls and monitors the device, and the device sends events to ProVision. In certain situations you may not want to monitor one or more devices on the network. For example, a device might be installed in a remote location where a concert is held on an annual basis. During the concert you would manage the device in ProVision, and for the remainder of the year you would leave the device in an un-managed state. When you un-mana un-manage ge a device in ProVision, the following occurs: l The device s event status statu s changes to blue in the Tree Tree Viewe Viewer. r. A blue ob object ject l balloon displays disp lays in the Map Viewer. For DXR DXR SMAs, SMAs, the conn connec ected ted DXR 700s are also un-managed. 158 AVIAT NETWORKS PROVISION USER MANUAL l The device device’s ’s event event history and perf performanc ormancee data are not displayed until the device is remanaged. l An unmanaged informational informational event event is added a dded to the ProVisio ProVision n event log. l ProVision stops presence polling the device. l Event gener generation ation is disabled in the device. device. CAUTION: Where Where a field techni technician cian is working working on a device device tha thatt may generate generate a large number number of faults faults you must “sleep th the e device” device” rather rather than than unmanagi unmanaging ng it. For more in information formation see Sleep Status for a Device . Procedure 1. Right-click the device to be un-managed. In the right-click menu, deselect the Managed checkbox. The device is changed to an unmanaged state, and is no longer polled by ProVision. Viewing Eclipse RAC Low Latency Links With ProVision, users can identify Eclipse Eclips e Low Latency links operating in either IF repeater or Regenerator mode. These links provide fast, ultra low latency transmission, with reduced reduced propagation propagat ion and equipment-related equipment-related latency. Eclipse INU and INUe devices that include RAC LL, RAC LL DDR or RAC3X configurations with low latency modem profiles, can be enabled for low latency operation through the LL software feature license. RAC LL and RAC LL DDR supports IF repeater and Regenerator functions, whereas RAC 3X only supports the Regenerator function. NOTE: RAC 3X supports supports r egeneration only. There are two low latency icon indicators, (IF) and (R), which can be viewed to indicate the low latency mode of a RAC interface: l l (IF) indicates indicates that a LL modem profile profile is active and IF repeater repeater mode has been been enabled on the RAC interface, resulting in the Eclipse node passing the IF signal from ODU to ODU. (R) indicates indicates that re regene generator rator mode mode is active, i.e. a LL modem profile profile is active however IF repeater mode is disabled. In the Map view, low latency paths through the network are identified: Note that where IF repeater mode reverts to Regenerator fallback mode, the RF link objec objectt conn connecti ecting ng the RAC interface interfacess will indicate the associate a ssociated d alarm condition. condition. 614-330055-001 DECEMBER 2015 159 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES In the the Tree view, RACs operating in low latency mode have a low latency indicator indicator beside the RAC interface object: In a Submap view, RACs operating in low latency mode have a low latency indicator on the RAC plugin: 160 AVIAT NETWORKS PROVISION USER MANUAL Users can search for RAC LL and RAC LL DDR devices using the Search function, entering Eclipse RAC LL in the text Search field: see Using Search to Search All ProVision Data on page 83. 83. In addition, RAC LL devices are included in the Inventory Report, with other licensed features, noted as LL Capability devices: see View and Save the Inventory Report for a Single Device on page 459. 459 . NOTE: For more information about about RAC LL, s ee the topic topic Eclipse Low Latency Operation in the Aviat Networks Eclips Eclipse e User Manua Manuall. Manually Discovering WTM 6000 Configuration In ProVision, when you manage a WTM 6000, you have the option of discovering the radio’s radio ’s configurations. When ProVision discovers d iscovers a WTM 6000, it communicates with the radio and identifies its plug-ins. The plug-ins are then noted and displayed in ProVision, as shown below in a sample Map View of a WTM 6000. If a WTM 6000 is changed in the Craft Tool, e.g., one of its plug-ins is removed, a warning Event E vent is raised raised for the radio in ProVision, ProVision, “Device “Device Configuration Configuration Changed”. You need need to compare this to related events. If it shows that this is due to a plug-in failure, take steps to fix this. If the event was raised when a device was configured to add or remove plug-ins, you need to rediscover the plug-ins, using the procedure below. Then the updated device configuration will display in the Map View and be used for event management. 614-330055-001 DECEMBER 2015 161 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Procedure 1. In the Tr Tree ee or Map Viewer, Viewer, right-click the require required d WTM 6000 radio. In the rightclick menu, select Discover Configuration. 2. The WTM 6000 is updated to reflect any new connections or any changes that were discovered. Any changes displ display ay in the Tree Tree V Viewer iewer.. Manually Discovering TRuepoint 6500 Configuration In ProVision, when you manage a TRuepoint 6500, you have the option of discovering the radio’s configurations. When ProVision discovers d iscovers a TRuepoint TRuepoint 6500, it communicates with the radio and identifies its plug-ins. The plug-ins are then noted and displayed in ProVision, as shown below belo w in a samp sample le Tree Tree View V iew of a TRue TRuepoint point 6500. If a TRuepoint 6500 is changed, e.g., one of its plug-ins is removed, a warning Event is raised raise d for the radio in ProVision, ProVision, “Device “Device Configuration Configuration Changed”. You need need to compar comparee this to related events. If it shows that this is due to a plug-in failure, take steps to fix this. If the event was raised when a device was configured to add or remove plug-ins, you need t o re rediscover discover the plug-ins, plug-ins , using the procedure below. Procedure 1. In the Tree or Map Viewer, right-click the required TRuepoint 6500 radio. In the right-click menu, select Discover Configuration. 2. The TRuepoint 6500 is updated to reflect any new connections or any changes that were discovered. Any changes display in the Tree Viewer. Manually Discovering DXR 700 Radios In ProVision, when you manage a DXR SMA, you have the option of discovering the connected DXR 700 radios. 162 AVIAT NETWORKS PROVISION USER MANUAL You can also manua manually lly discover DXR 700 radios in the following situations: situa tions: l l l Where Where the discover discover option was not enabled enabled when the DXR SM SMA A was managed in ProVision, because the radio had not been commissioned. Where Where you are getting getting unusual re responses, sponses, you may discove discoverr the radios to see iiff the radios have been changed, that is, swapped ports. To delete delete a DXR 700 rradio adio from from ProVisio ProVision n where a DXR 700 radio has been been physically removed from the network. Procedure 1. In the Tree or Map Viewer, right-click the required DXR SMA. In the right-click menu, select Discover Terminals. 2. The user interface is updated to reflect any new DXR 700 radios or any changes that were discovered. Managing Proxy Configuration Configuration For Proxy and Network Element devices, you can change which Network Elements are assigned to which Proxy. Procedure 1. In the Tre Treee View View or Map Map View, right clic click k on a Proxy. Proxy. From the right-clic right-click k menu, select Proxy Configuration Manager. 2. The Proxy Configuration Mana Manager ger displays. 614-330055-001 DECEMBER 2015 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES 3. Fro From m this scre screen, en, you can select select a Networ Network k Element Element and reassign reassign its Network Element ID number. 4. To move move a Ne Network twork Eleme Element nt from from one Pro Proxy xy to another another,, drag and drop it in the Tree View. You will be asked to confirm reparenting the Network Element. Click Yes and the Network Element will be reassigned. 3. Cl Cliick Close. Your changes are saved. 163 164 AVIAT NETWORKS PROVISION USER MANUAL Managing SMA and DXR Devices 120,, DXR 200 is a As described described in DXR 200 and DXR SMA Device Deployment on page 120 legacy legac y device. device. To communicate with Pro ProVision, Vision, DXR 200 devices devices must be connecte connected d to an SMA Proxy. It is the SMA proxy that communicates with ProVision via ethernet. To manage an SMA and its DXR 200 devices, you need to ensure that the ProVision configuration of the DXR radios matches the DXR 200 radios actually configured by an SMA. SM A. The DXR 200 200 radios must be identified identified and configure configured d cor corre rectly. ctly. To do this: 1. Check the status of the DXR 200 radios for an SMA using the Management Viewer screen. 2. Make any corrections to the configuration of the SMA or DXR 200 radios using the Management Configuration screen. NOTE: DXR 200 ra dios are s et up outside outside of ProVision. ProVision. When you create a new DXR 20 0 for an SMA, it should be based on the DXR radios that are physically connected to the SMA. Use the “Discover Terminals” function to identify these radios. Procedure 1. In the Tree or Map Viewer, right-click the required DXR SMA. In the right-click menu, select Discover Terminals. 2. Right-click the DXR SMA again and select Management Viewer. 3. The Management Viewer screen displays. 4. The Management Viewer displays data about all the DXR 200 radios contained by an SMA. This includes the network port, terminal number, status, and ProVision name. Note t he following: l l l 614-330055-001 Radios highlighted highlig hted in orange need need to be deployed or other otherwise wise cor correc rected ted in ProVision. Radios with a Status of “Not “Not Present” Present” are are not physically connected connected to the SMA. SMA. Radios with a Status of “Deployed” are physically connected to the SMA. Radios deployed deployed correc correctly tly in ProVision ProVision are displayed in white. DECEMBER 2015 165 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES 5. If you need to correct the configuration for an existing DXR 200 radio, right-click its DXR SMA and view the right-click menu. Select Management Configuration. 6. The Management Configuration scre screen en display s. 7. The Management Configuration screen displays all the SMAs. In a tree viewer, it shows which DXR 200 radios connect to which SMAs. 8. To check the configuration parameters for an SMA or a DXR 200, click on it in the tree viewer. The configuration values display. For an SMA, you can edit the Name. For a DXR 200, you can edit the Name, Network Port, and Terminal Number. Click on Commit Changes to save changes. 9. Select Close to close this screen. 10. If you make any changes, open the Management Viewer again to ensure that any changes to DXR 200s 200s have bee been n successful. successful. 166 AVIAT NETWORKS PROVISION USER MANUAL Linking Procedures ProVision can discover and create links between certain devices. A Radio Frequency (RF) link is added between devices in ProVision to show that the devices are carrying communications traffic. An Ethernet link shows that the devices are carrying Ethernetenabled traffic. You can only create a link between Aviat Networks devices of the same type, for example, one Eclipse radio to another Eclipse radio, or one CTR 8540 router to another CTR 8540 router. To create an RF or Ethernet link between two devices, the radios must be deployed in ProVision. By creating a link between two devices in ProVision, you are able to see the complete link, viewing both ends. In the Map Viewer or submap, the highest severity event from either radio is reflected in the color of the link. For more information see Alarm Severity Color Coding on page 91. 91 . This section covers the RF and Ethernet linking procedures: l Discover Disco vering ing and Verifying Verifying Links Links on page 167 l Creating Cre ating an RF Link from from the Tree Tree Viewe Viewerr on page 169 l Creating Cre ating an RF Link from from the Find Function Function on page 170 l Creating Cre ating an Eclipse RF RF Link on page 171 l Creating Cre ating an Ethernet Ethernet Link Link on on page 173 l Creating Cre ating a Tributar Tributary y Link on on page 174 l Deleting Dele ting an RF Link Link on on page 175 l Deleting an Ethernet Ethernet Link Link on page 176 NOTE: RF links are automatically automatic ally discovered for Eclipse radios. Discovering Disco vering and Verifying Verifying Links You can discover and verify the following link types, typ es, which then display displ ay in the Map View: Lin ink k Type Sa Samp mple le fro rom m Ma Map p Vie iew w RF Link Link is a pla plain in line: 614-330055-001 DECEMBER 2015 167 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Lin ink k Type Sa Samp mple le fro rom m Ma Map p Vie iew w Ethernet Link Link la labeled beled with squares squares:: Tributary Link Link labeled with diamonds: Logical Link Link Linkss are displayed displayed beside each other: other: Optical Link Link labeled with circles: Multiple Links Link is a thic thick k lline: ine: mouse over over it to view sepa separate rate llinks inks.. For the following device types: l Eclipse l CTR 8540 l TRuepoint l WTM 3300 This is done using Discover Links. NOTE: Thi Thiss function is available for TRuepoint 4000, 404 0, 5000, and 6400 ra dios. It is not available for TRuepoint TRuepoint 6500. TRuepoint 6400 radios can have two RF links. All other radios have one RF l ink. ink. Procedure 1. In the Search screen, locate the device. 2. The device displays in the Search results frame. Right-click on the device. 3. From the right-click menu displayed, move the cursor to the Create Link option and select Discover Links. 168 AVIAT NETWORKS PROVISION USER MANUAL 4. Two messages will display. The first is a progress report: the second is the link discovery results. 5. Select OK. 6. If you need to create additional links, see Linking Procedures on page 167 Creating an RF Link from from the Tree Viewer From the Tree Viewer, you can select and link two radios. To link two Eclipse radios, instead of sele selecting cting the specific specific radios, select select the link objec objects ts for those radios. NOTE: To create an RF link from the Find screen, see Creating an RF Link from the Find Function on page 170 . Procedure 1. In the Tree Viewer, locate the two radios to be linked. You may want to check to see if the radios already have a link to another radio: see Discovering and Verifying Links on page 167. 167 . 614-330055-001 DECEMBER 2015 169 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES 2. Select the first radio icon, hold the CTRL key and select the second radio icon. 3. Right-click the second radio icon, and from the right-click menu displayed, select Create Link - RFLink . 4. Select OK O K. Exceptions l l If you try try to create create a link using a radio that already already ha hass a link, an error error message displays. If you are are trying trying to cre create ate a link, and the Create Link menu option remains grayed out, you may not have selected both ends, or the radios selected are not compatible. l l To create create an RF link for WTM 6000, select select both Path Groups, then open the right-click menu and select C reate Link - RF Link . If you try to create a link for for two radios that are not not compatible, an error error message displays. Creating an RF Link from the Find Function From the Find screen, you can select and link two radios. To link two Eclipse radios, you must select t he link objects objects for those th ose radios. rad ios. NOTE: To create an RF link from the Tree Viewer, see Creating an RF Link from the Tree Viewer on page 169 . Procedure 1. To open the Search screen, go to the Edit menu and select Search. The Find screen displays. 170 AVIAT NETWORKS PROVISION USER MANUAL 2. In the Find screen, locate the two radios to be linked. You may want to check to see if the radios already have a link to another radio: see Discovering and Verifying Links on page 167. 167 . 3. Select the icons for the two radios that you want to link. 4. Right-c Right-click. lick. From the right-click right-click menu, select select Create Link - RF Link. A message will display disp lay.. 5. Select OK. The radios are now linked. linked. Exceptions l l l If you try try to create create a link using a radio that already already ha hass a link, an error error message displays. If you are are trying trying to cre create ate a link, and the Create Link menu option remains grayed out, you may not have selected both ends, or the radios selected are not compatible. If you try to create a link for for two radios that are not not compatible, compatible, an erro errorr message displays. Creating an Eclipse RF Link When creating creating an Eclipse RF link you must select compatible comp atible Eclipse Eclips e Nodes. The Eclipse radio linking linking conf configuratio iguration n options are shown below. Each end of the link must have the same ODU type, that is ODU 100 to ODU 100 or ODU 300 to ODU 300. 614-330055-001 DECEMBER 2015 171 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Figure Figu re 4- 4. Eclipse Radio L Lin inkin king g Configu Configuration ration Options Options The types of Eclipse radios and the maximum number of links per each radio type are as follows: Table Tabl e 4-5. Eclipse Radios - Number of Links Type ype of Ec Ecllips pse e Radi Radio o Maximum Numbe ber r of Links Eclipse Terminal one link Eclipse INU three links Eclipse INUe six links When creating creating an RF link between between Eclips Eclipsee Nodes you must select t he same type typ e of Link icons for both sides of the link. The Eclipse Node link icons are as follows: Table 4-6. Eclipse Radios - Type of Links Type of Eclipse Link Icon Link (non-protected) Protected link Ring-protected link Procedure 1. In the Tree Viewer, locate the two radios to be linked. You may want to check to see if the radios already have a link to another radio: see Discovering and Verifying Links on page 167. 167. 2. Expand both the Eclipse radios so the required link icons are displayed. 3. Left-click the link icon of the first firs t radio and CTRL lleft-click eft-click the link icon of the second secon d radio. 4. Right-click, and from the right-click menu displayed, select Create Link - R F Link . A message displays, confirming that the link is created. 172 AVIAT NETWORKS PROVISION USER MANUAL 5. Select OK. NOTE: RF links are automatically discovered for Eclipse radios. Exceptions l l l If you try try to create create a link using a radio that already already ha hass a link, an error error message displays. If you are are trying trying to cre create ate a link, and the Create Link menu option remains grayed out, you may not have selected both ends, or the radios selected are not compatible. If you try to create a link for for two radios that are not not compatible, compatible, an erro errorr message displays. Creating an Ethernet Link From ProVision, you can create Ethernet links for Ethernet-enabled devices. NOTE: For more details about Ethernet Ethernet management see VLAN Man- agement on page 244 , ERP Ring Management on page 282, and Et hernet OAM Management on page 263 . Procedure 1. In the Tr Tree ee Viewer Viewer,, locate the first devic d evicee to be linke linked. d. 2. Right-click, and from the the right-clic right-click k menu displayed, select select Create Link -Ethernet Link. The Create Ether Ethernet net Link screen screen displays. 3. For each side of the link,select the device by clicking Change and choosing the specific device from the drop-down menu. 614-330055-001 DECEMBER 2015 173 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES 4. Then, select the available Port for the device from the Port drop-down menu. 5. Select Create. The link is created. and nd 6. To view the links, see bothViewing EOAM MA Logical Topology on page 267 a Viewing VLANs in the Physical and Flat Maps on page 252 Ethernet links display in the Map View with a square labeling the link: 7. To delete a link, see Deleting an Ethernet Link on page 176 NOTE: Ethernet links are automatically discovered for Eclipse radios. Exceptions l l l Ports Ports that are n not ot available fo forr linking linking display in red red in the drop-down menu. If you are are trying trying to cre create ate a link, and the Ethernet Link menu option remains grayed out, the device cannot support an Ethernet link. If you try to create a link for for two devices devices that are not not compatible, an error error message displays. Creating a Tributary Link From ProVision, you can create Tributary links for Eclipse devices that have 3xE3/DSM3M 3xE3/DSM 3M cards. Procedure 1. In the Tree Viewer, locate the two plug-ins to be linked. Select both plug-ins. 2. Right-click, and from the right-click menu displayed, select Create Link - Tributary Link. 3. ProVision displays the Tributary Link configuration dialog: 4. Select which ports are physically connected together via cable and click OK. ProVision will create the tributary link. 174 AVIAT NETWORKS PROVISION USER MANUAL 5. To view the links, check the Map View and find the Tributary Links, labeled with a diamond. Hover over the link to view its details in a pop-up. Or, right-click on the link to view the menu and see options for managing the link. Clicking the Configure Link menu item, displays the same dialog as in Step 4 to change the port mapping: 6. To delete a link, use the same procedure as in Deleting an Ethernet Link on page 176 Exceptions l l l Ports Ports that are n not ot available fo forr linking linking display in red red in the drop-down menu. If you you are trying to ccre reate ate a link, and the Tributary Link menu option remains grayed out when you have selected both plug-ins, the plug-in cannot support a Tributary link. If you try to create a link for for two devices devices that are not not compatible, or where where a link already exists, an error message displays. Deleting Dele ting an RF Link You can delete an a n RF link. There There are two t wo reasons to delete a link fro from m ProVision; either the wrong radios were linked, or the link is no longer available due to a change in equipment installed at the site. 614-330055-001 DECEMBER 2015 175 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Procedure 1. In the Tree Viewer, for an Eclipse radio, right-click the Link icon. For all other radios, right-click the radio icon. 2. In the right-click menu, move the cursor to the Link option and select Delete. The Delete Link window displays. Y es. 3. To confirm deleting the link, select Yes Deleting an Ethernet Link You can delete an a n Ethernet link from the t he Tre Treee Viewer or the Map View. Procedure 1. To delete an Ethernet link from the Tree Viewer, right-click the device; at the bottom of tthe he right-click menu, Ethernet Links display. disp lay. Sele Select ct the link and choose Delete. 2. To delete an Ethernet link from the Map view, select the Ethernet link in the map. A pop-up menu names the link and provides a Delete option. Choose Delete. 3. The Ethernet link is deleted. 176 AVIAT NETWORKS PROVISION USER MANUAL Circuit Management Pr ProVisio oVision n provides provides complete complete Eclipse E clipse circui circuitt management. management. Eclipse Circ C ircuit uit information information is documented docume nted in the following sections: l About Abo ut Circuits and Circuit Manageme Management nt on page 177 l Collecting Collec ting Circuit Circuit Information Information on on page 178 l Viewing Viewi ng and Managing Managing Circuits Circuits on page 179 l Circuit Pro Provisionin visioning g on page 186 186 About Circuits and Circuit Management A circuit is a single tributary path pat h that travels through a sequence sequence of radios. For Eclipse E clipse radios, circuits are initiated and terminated term inated on a DAC (INU/INUe), or, for an IDU, within its ethernet/dat ethernet/data a modu module. le. A circuit group is a col collection lection of tributary paths that travel through the same sequence of radios from the same start point to the same end point. There are three steps to loading and managing Circuits: l Set up the Circuit Collection Prefer Preference encess - Collecting Circuit Information on page 178 l View and Manage Circuits - Viewing and Managing Circuits on page 179 l Provisioning Circuits - Circuit Provisioning on page 186 ProVision periodically captures the cross-connect configurations from the radios. If you make any circuit configuration changes to the radios within a circuit, the circuit must be re-traced to accurately identify the newly-configured circuit. ci rcuit. Circuit tracing tracing:: l l l Locates incorrec incorrectt circuit cross-connections cross-connections within tthe he network network Views and and manages changes to tthe he network circuit configuration (such as adding circuit capacity during network rollout). Views the circuits circuits to use us e the troublesho troubleshooting oting feature featuress of ProVision, ProVision, such as as loopback and PRBS (pseudo random binary sequence) testing. ProVision supports circuit tracing amongst the following Eclipse card types: l DAC GE3 l DAC GE l DAC ES l DAC 155eM/ 155eM/155oM 155oM l DAC 16xE1/DS1 l DAC 4xDS1 614-330055-001 DECEMBER 2015 177 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES l DAC 3xE3/DS3 3xE3/DS3M M l NCM Circuits can be traced through the DAC 155eM/155oM if NMS traffic is turned on. All other DAC types will be treated as endpoints of a circuit and cannot be traced through. Circuit tracing is supported through all RAC card types. NCM circuits are collected via circuit collection and can be viewed via the Circuits tab: see View Loop Switch Circuits on page 184 Collecting Circuit Information ProVision automatically downloads circuit information once a day, at a time that you specify. The circuit data is collected and then analyzed off line, to conserve processing time. You can also run a manual download of circuit information at any time. NOTE: Circuit information is only collec ted from normal, managed devices. Procedure 1. To set the time for daily collection of circuit information for all circuits, go to the Configuration menu and click Circuit Collection Preferences. 2. The Circuit Collection scre screen en display s. 3. To set the time each day when Circuit information is collected and loaded into ProVision, set the Perform daily at value. Then, click OK. The Circuit data will be collected and loaded at this time every day. 4. To collect and load circuit information immediately at the radio/container level, right-click right-c lick the device and select select Circuits - Circuit Collection. The information is immediately immediate ly downloaded. 5. Click OK to close the screen. 178 AVIAT NETWORKS PROVISION USER MANUAL Viewing and Managing Circuits The circuits are displayed in monitoring the Circuitsthe Tab, available to and be monitored The following features make network easy efficient: and managed. l Circuits Tab on page 179 l Filter and Select Select Circuits on page 181 l View a Single Single Circuit on on page 182 l View Inter Intersectin secting g Circuits on page 183 l View Ring Circuits on on page 183 183 l View Loop Loop Switch Switch Circuits Circuits on page 184 184 l Find and Resolve Resolve Conflicting Conflicting Circuits Circuits on page 185 l Circuit Diagnostic Diagnosticss on page 190 l Circuit Provisioning l Delete_a_Circuit.htm Circuits Circui ts Tab ProVision can support up to 50,000 circuits in a network. In the Circuits Tab, you can view, sort, analy ze, and and filter the available circuits. The Circuits Tab displays immediately be behin hind d the main Map Tab in the ProVision user interface. Click the Circuits Tab to view this screen. screen. To view details for a circuit, mouse over it in the map view to see a detailed pop-up. From here, you can access the following functions: l Filter and Select Select Circuits on page 181 l View a Single Single Circuit on on page 182 View Inter Intersectin secting g Circuits on page 183 l View Ring Circuits on on page 183 183 l View Loop Loop Switch Switch Circuits Circuits on page 184 184 l Find and Re Resolve solve Conflicting Circuits on page 185 l Circuit Diagnost Diagnostics ics on page 190 l Using Circuit Provisioning on page 186 l Commissioning Commissioni ng and Decommissioning on page 1 l 614-330055-001 DECEMBER 2015 179 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Figure 4-5. Circuits Tab Table 4-7. Circu Circuit it Tab Values Values Value Definiti Definition on Selected Object Name of the sel selected ected object object;; its circuits circuits are det detailed ailed in th this is ttab. ab. To view all circuits for the entire network, click the X beside this field. Bundle Circui Circuits ts Check this bo box x to bundle circ circuits. uits. This gro groups ups ccircuits ircuits based o on n sh shared ared st start art pointss and circuit path point paths, s, to make the circ circuit uit infor information mation easier to proces process. s. NOTE: Portal circuit bundles bundles only relate to internal cr oss- connection internal connectionss w hile ProVision bundles bun dles ar e of end-to-end circuits. circuits. Include Intersecting Circuits Check this box to view circuits that pass through the circuits for this object, in addition to circuits that start and end at this object. Filter Use the Filter Filter func function tion to filter and view spec specific ific circ circuits. uits. The entered text is comcompared against the data in a columns of the circuit table. Export Circuits Use the the Expo Export rt Circuit Circuitss fun functio ction n to expo export rt ccircuits ircuits as a semico semicolo lon n sepa separated rated ffile. ile. Map Tab Selec Selectt a circ circuit uit in the table, table, and a graph graphic ic represent representatio ation n displa displays ys in the Map Tab. Conflicts Tab See Find and Resolve Conflicting Circuits on page 185 for details. Circuitt Table Circui Shows infor information mation for the links links for the selected selected device. Severity The severity of any events for this link link.. 180 AVIAT NETWORKS PROVISION USER MANUAL Value Definition Status The sta status tus of this link link.. Status is indicat indicated ed by colo color: r: Green = OK. Red = Data incomplete, cannot completely trace this circuit. Blue = Circuit names inco inconsist nsistent. ent. Yellow = Circuit route changed. Orange = Circuit route removed, circuit has been deleted and recreated. Glowing Orange = Incorrect Ring configuration. Name The name of the circuit, circuit, which sho shows ws the connec connected ted devices. Start Eclipse radio and DAC plug-in/port for the circuit connec connection tion beginning. End Eclipse radio and DAC plug-in/port for the circuit connec connection tion end. Capacity Tot Total al capacity of the circuit. Type Circuit type: E1, E3, STM1 STM1,, Ethernet Ethernet,, Ring AM Pri Priority ority Related to Adaptive Modula Modulation, tion, assigned in Eclipse Portal Portal if applicable. Filter and Select Circuits ProVision can manage up to 50,000 circuits. To locate specific circuits, use the Filter function. Procedure: 1. Ensure that circuits are loaded into the Circuits tab. 2. If you want to search circuits for one device, select that device in the Tree viewer. The circuits for that device display in the Circuits tab. 3. If you want to search circuits for all devices, open the Circuits tab and click the X beside the th e Selected Object field. All circuits for the network display in the Circuits tab. 4. At the bottom of the Circuits tab, click the Filter button. 5. The Filter field displays. 6. Enter a value for the circuits. This can include its: l Name, Name, or part of the name l Type - E1, E3, E3, etc etc.. l IP address, address, or part of the IP address address l Severity Severity level 7. Then, press Enter. 8. ProVision filters all available circuits based on this value. For example, if you searched on an IP address, all circuits that include that IP address will be selected. The circuits that match this value display in the Circuits tab. 614-330055-001 DECEMBER 2015 181 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES View a Single Circuit In the Circuits Tab, select the table row of an individual circuit to display that circuit, and only that circuit, in the Map subtab of the Circuits. In the example below, Circuit 1 is selected, and displays in the Map subtab: If the Map and Conflicts subtabs are not displaying, select the circuit and click the Show Details button on the lower right of the Circuits tab. This opens the Map/Conflicts subtabs with the circuit displayed. To close these subtabs, click Hide Details. The Map details include the port numbers for the devices. To view additional information about a circuit, in the Map subtab, place the cursor over the circuit device. A popup displays with link information. You can right-click on a single circuit. The circuit right-click menu includes: Item Function Commission Tributaries Runs decommissioning on this circuit. See Commissioning and Decommission Dec ommissioning ing on page 1 . Decommission Trib- Runs decommissioning on this circuit. See Commissioning and utaries Decommission Dec ommissioning ing on page 1 . Circuit Provisioning Provisioning Show Conflicts Conflicts Opens the Circuit Provisio Provisioning ning screen. See Using Circuit Provisioning on pa page ge 186 . Opens the Conflict subtab and displays any circuit conflicts. See Fi Find nd and Resolve Conflicting Circuits on page 185. 182 AVIAT NETWORKS PROVISION USER MANUAL Item Function Clear Conflicts Reso Resolves lves any identifi ed circuit co conflicts. nflicts. See Find and Resolve Conflicting Circuits on page 185. Diagnostics Opens the Circuit Diagno Diagnostic sticss screen. screen. See C Circ ircuit uit Diagnostic Diagnosticss on page 190. Rename Opens a field enabl enabling ing you to Rena Rename me a circ circuit. uit. Delete Deletes the circuit. Event Browser Opens the circuit-s circuit-specific pecific Event Brows Browser. er. See Event Browser for a Circuit on page 186 . Network Health Report Opens a RF Network Health Reports on page 474 for this specific device. View Intersecting Circuits Intersecting circuits circuits for a device are circuits that do d o not start or terminate at a device, but instead pass through the device on their circuit pat pathway hway.. You can include intersecting circuits in your view of a device’s circuits. Procedure 1. Select the device in the Tree Viewer. 2. Open the Circuits Tab. The device circuits are displaying. 3. Click the Include Intersecting Circuits check box. 4. Any intersecting circuits are added to the Circuits Tab. View Ring Circuits ProVision clearly identifies circuits for Eclipse ring networks. When you select and view the Circuit in the Map subtab, it is identified as an Eclipse Ring. Hover over the circuit to view its ring pathways: 614-330055-001 DECEMBER 2015 183 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES The view clearly identifies Eclipse NCM loop switch card circuits in loop circuit networks. Double-click the circuit to expand and view all the aspects of the loop circuit. This includes all nodes in the ring including the NCM configuration of east, west, drop and passthrough cir circuits. cuits. Hover over the circuit to view any errored devices in the ring. View Loop Switch Circuits ProVision clearly identifies Eclipse NCM loop switch card circuits in loop circuit networks. When you select a and nd view the Loop Circuit in the Map subtab, it is identified as a Loop Circuit. Hover over the circuit to view its pathways: 184 AVIAT NETWORKS PROVISION USER MANUAL Double-click the circuit to expand and view all the aspects of the loop circuit. This includes all nodes in the ring including the NCM configuration of east, west, drop and passthrough cir circuits. cuits. Find and Resolve Conflicting Circuits A circuit conflict occurs when, w hen, due to a circuit reconfiguration, reconfiguration, a circuit pat pathway hway nee needs ds to be updated. Circuit conflicts do not occur when a circuit is first traced; they may be identified in subsequent traces. ProVision includes a Conflicts subtab, which enables you to view and resolve conflicting circuits. Procedure 1. Select the device in the Tree Viewer. 2. Open the Circuits Tab. The device circuits are displaying. 3. To view conflicts for a circuit, right-click the circuit and select Show Conflic Conflicts ts. Or, click the Show Details button, then click the Conflicts subtab. 4. To reso resolve lve conflicts conflicts for a cir circuit, cuit, right-click right-click the cir circuit cuit a and nd sele select ct Clear Conflicts. If required, use Portal to reconfigure the Eclipse radios. 614-330055-001 DECEMBER 2015 185 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Event Browser for a Circuit To view the events that apply to objects in a circuit or circuit bundle, select Event Browser. This opens a separate, floating window that displays a scrolling list of events for the circuit objects. For a complete complete description, description, see Event Browsers on page 314 314.. Circuit Circu it Provisioning Provisioning The Circuit Provisioning function allows you to select one or more Eclipse devices and create, edit or delete circuits between the devices. These are then written directly to the radios. Circuits can be written to a radio in Portal, but the ability to do this from ProVision makes ProVision a central circuit manager for the device network. W AR NI NG : Circuit provisioning provisioning is only supported for Ec lipse software 5.1 and later versions. versions . It is not supported for earlier versions of Portal. This means that only Eclipse devices with 5.1 or later embedded software installed can be managed using Ci Circuit rcuit Provisioning Provisioning fr om ProVision. To create a circuit a radio in ProVision, you must do the following: l Make sure that all links for the netwo network rk are are set up. l Discover Discover RF RF links for for the radio (see (see Linking Procedures on page 167). 167). l l Use the Circuit Provision Provisioning ing function function to cre create ate the circuit circuit or circuits circuits and a nd write it to the radio. Commission the cir circuits. cuits. This section describes how to use Circuit Provisioning Provisioning and how to commission and decommission created circuits. l Using Circuit Circuit Provisio Provisioning ning on page 186 l Commissioning Commissioni ng and Decommission Decommissioning ing on page 1 Using Circuit Provisioning The Circuit Provisioning function enables you to create circuits for radios. This process defines all possible paths between devices, and allows you to choose which paths you want to use for circuits. Note the following: 186 AVIAT NETWORKS PROVISION USER MANUAL l l l To cre create ate a circuit, circuit, a circ circuit uit path mu st begin begin and end with a DAC. RF links for the involved involved radios must be discover discovered ed be befor foree a new circuit circuit can be created. After After you cre create ate a circuit, you can edit it, incr increasing easing or decr decreasing easing its capacity. To change the termination points or routing, you must delete and recreate the circuits. Procedure 1. Check Check that the Eclipse Eclipse radio radioss you want to con conne nect ct with a circuit circuit have had RF links created. See RF Linking Procedures. Procedures. 2. In the T Tre reee Viewer Viewer or or the Cir Circuits cuits tab, select select the radio radio and right-clic right-click k Circuit screen en displays. d isplays. Provisioning. The Circuit Provisioning scre NOTE: If there are too many devices to display in the the available paths window, then a cloud is displayed with the number of devices in the path. 3. 4. 614-330055-001 The uppe upperr left left corner corner of of the scree screen n shows selected selected objec objects. ts. The item in the frame for Object A is the radio you selected to open this screen. If you selected two radios, the second one is in the frame for Object B. These fields allow users to select two objects to be linked via a circuit. If req require uired, d, select an objec objectt in the field field for Obje Object ct B. DECEMBER 2015 187 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES 5. After After you have selecte selected d Object Object A and Objec Objectt B, the Available Paths area area displays the link options. options . The Available Paths area shows all possible network paths linking the selected radio end points for this radio, with the following information: l Free =Shows the available capacity of the path. l Used = This shows the used/configured capacity of the path for a circuit. New circuits do not show a capacity value. l l 7. 8. l l l Paths = A graphic of the path of the circuit through the Eclipse network. The terminating Eclipse radios are indicated by paired DAC + RAC icons. Interme Inte rmediate diate Eclipse nodes are shown as single radio icons. Where Where there are more than 5 path hops, a cloud icon is shown, with a number indicating the number of intermediate Eclipse nodes. Pathway Tooltip Tooltip = Place the cursor over a circuit pathway to view its full information, displayed as a tooltip. Se Sele lect ct the networ network k path that you want to have for for a cir circui cuitt. The Cross Cross Conne C onnections ctions Table Table will be populated with the cross-con cross-connec nection tion information for the selected path. Cross Co Connect nnection ion T Table able = Shows objects, objects, ports, free free capacity, and priority priority level of the connection. Circuit Name = A name prefix for this circuit bundle. This will appear as part of all circuit names within this bundle. Note: ProVision circuit bundles are related to end-to-end circuits. Cont Contiguou iguous s Circuit = The capacity for this circuit. If you set the capacity at too high a value, value, a warning warning will display. 188 AVIAT NETWORKS PROVISION USER MANUAL 9. Using the Cross Connec Connectt data, review review and adjust the configur configured ed por portt connections. You can click on a Port to assign a different port value from a drop-down menu. Then, assign the Circuit Name and set the Contiguous Circuit value. NOTE: Only free ports can be used for a new circuit. If you select a port that is is not a fr ee port, a war ning ning will display. NOTE: For Eclipse links that have Adaptive Adaptive Modulation, Modulation, the Priority level indicates indicates the prior ity of the new circuits. Adapt Adaptive ive Modulation priority cannot be changed from ProVision. ProVision. l If a Loop Loop Switch path h has as been been sele selected, cted, you can edit the Loo Loop p Switch port connections and directions by clicking the Edit… button: 614-330055-001 DECEMBER 2015 189 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES l o A dialog appears with the cross-connection information for each side of the loop switch ring: o As in the previous step, you can click on a port to assign a different port valu e from a drop-down menu. To cha value change nge the east and west directions of the ring, click the Swap East/West button. Click the OK button to confirm confirm the configur configuration. ation. 10. After After the cir circuit cuit capacity and other values are corre correct, ct, click Commit Changes. 11. ProVision ProVision writes writes the changes changes to the nodes. nodes. This can can take sever several al minutes; progress progr ess indicators display displa y during the proc process. ess. First, ProVision ProVision check checkss with the radios. Then, it verifies that the circuit changes were made successfully. A message displays disp lays when the circuit change is written successfully, or if it is not successful. 12. In the Circuit Provisioning Provisioning screen, screen, click Close. The new circuit displays in the Circuits tab, in the list of circuits for the radio. 13. Afte Afterr you have co complete mpleted d Circuit Provision Provisioning ing for for a cir circuit, cuit, you can open it, edit the data port connections and capacity, and write it to the radios again. Circuit Diagnostics Select Circuit Diagnostics to open the circuit diagnostics window. This feature allows you to diagnose problems problems within a circuit and isolate faulty equipment. For a complete complete description description of this fe feature ature,, see Circuit Diagnostics Feature on page 381. 381. Circuits deleted because they no longer exist in the ratio network are shown via Delete a Circuit on page 190. 190. Delete a Circuit You can delete one or more m ore circuits from the t he Circuits Tab. Deleting a circuit will delete it fr from om both both the software and the radio network. network. 190 AVIAT NETWORKS PROVISION USER MANUAL Procedure 1. In the Circuit Tab, right-click the name of the circuit. 2. Select Delete on the right-click menu displayed. The Delete Circuits window displays. 3. To delete the selected circuit from both ProVision and the radio network, select OK. 4. To not delete the circuit at all, click Cancel. 5. If you chose step 3 the Circuits Tab is refreshed and the circuit is no longer displayed. 614-330055-001 DECEMBER 2015 191 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Configuring and Synchronizing Devices This section details device configuration and synchronization procedures: l Clock Synchro Synchronization nization View View on page 192 l Viewing Viewi ng Configuration Configuration for for Device Devicess on page 194 l Configuration Profiles Profiles for Bulk Configuration on page 201 201 l Eclipse and CTR Node Node Licenses Licenses on page 237 237 l Viewing/Changing Viewi ng/Changing Network Network IP IP Addresses Addresses on page 217 l Viewing/Changing Viewi ng/Changing TNet TNet Proxy Proxy C onf onfiguratio igurations ns on page 218 l Using the TNet TNet Proxy Proxy Viewe Viewerr on page 220 220 Clock Synchronization View Synchronous Ethernet Synchronous Ethernet allows various nodes in an Ethernet Ethernet network network t o sy nchr nchronize onize to the same clock frequency. NOTE: This function requires a feature license: see About Licenses. In ProVision, you can view the clock synchronization of devices in a network. Clock Sync Mode, opened in the Map Viewer, provides a visualization of the current network synchronization chro nization conf configuratio iguration, n, allowing an enginee engineerr to understand understand how clock signals are being distributed d istributed across the network, with: l l l l A color-coded color-coded clock icon for for eeach ach source of of timing synchronization. Note that the sources sources are normally normally external external to the network network.. Color-coded links between between devices devices receiving receiving their timing from from the matching source. Color-co Color-coded ded highlights for device devicess where clock clock quality and stability are below below set thresholds. Synchronization properties properties in tool tool tips NOTE: You can view cl ock synchronization performance data using using the the Clock Synchronization Network Health Report on page 485 . 192 AVIAT NETWORKS PROVISION USER MANUAL Procedure 1. Within the Tree Tree Viewer, Viewer, select a Container or device. device. The related related network network displays display s in the map Viewer. NOTE: Note: Use the Map or Lo gical Container Container view so that all nodes relating to the synchronized network network ar e visible. 2. In the Map toolbar, select the Clock Sync icon. 3. The Clock Sync Mode view displays. 4. Review the clock synchronization. The Clock Sync view provides a visualization of the current network synchronization configuration. The view shows: l l l External External clock sour sources ces as inputs (e (each ach external external clock sour source ce is given a unique color). Distribution Distribution of the clock from from node to node acr across oss radio links, with direction direction of clock cloc k pro p ropagation pagation shown by colore colored d arrows arrows along a long links. Degraded configuration, where a node has fall fallen en back to holdover or fr free ee-running mode. 5. To set the Quality and Stability thresholds for the view, right click on the map view and select Performance - Clock Sync Performance Metrics. In the screen, set the quality threshold from the drop-down menu and set the number of switches for the stability threshold. Click OK and these values are saved and applied to all Clock Sync Views. Devices that do not meet the quality and stability thresholds will be highlighted in the view. 614-330055-001 DECEMBER 2015 193 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES 6. Right click on any map icon and select Clock Sync Properties from the menu. A clock sync properties view is shown for each clocked device in the map item, including: l The clock clock synchronization synchronization device device (in the title of the view view window) l Clock sources, sources, listed in priority order. order. l l The curre current nt locked locked clock source source is highlighted (color of the highlight matches the arrow color on the map). The status of the SSM feature, feature, either enabled/disabled. (SSM, (SSM, Syncronization Status Messaging, is an extension of the Synchronous Ethernet feature. It enables monitoring of the Quality Level, QL, of configured clock sources, and for the automated switching of the device's clock source to the "best available" source). Viewing Configuration for Devices Configuration data is entered via a craft tool and stored in the radio. Use the Configuration Viewer to review the configuration for a device: ProVision retrieves and displays the device values from the craft tool. You can also save the configuration data for a device as a text .CSV file. Procedure 1. Within the Tree or Map Viewer, right-click the device icon. Select Configuration Viewer from the right-click menu. 2. The Configuration window displays. 194 AVIAT NETWORKS PROVISION USER MANUAL 3. Select the required tab to view the device data in which you are interested. 4. The data may have changed since you selected to view it. To refresh the data, select the Refresh from Radio button. 5. To save the configuration data as a .CSV file, click Save. 6. To close the Configuration window, select Close. The table below lists the data that displays in the Configuration Viewer for different radio and device types. Note that the most frequently used tabs are listed first, and specialized tabs are listed later. Tab Descriptio n Information tab The infor information mation ta tab b lists general inf informat ormation ion about th thee device, such as name, site name, IP address, and type. Radio Frequency/ Link tabs For Eclipse radios, the Configuration Viewer window has separate tabs that list the radio frequency configuration for each link. The drawing below shows the Configuration Viewer window for an Eclipse Node with one link in slot 1 (LINK1) and one link in slot 4 (LINK4). NOTE: If DAC GE3s are included for an Eclipse radio, they are listed in the Software tabs. Note: Remote link information is not supported for IDU prot protected ected devices For protected XP4 X P4 radios the Configuration Viewer window has two radio frequency tabs: RF 1 and RF 2. 614-330055-001 DECEMBER 2015 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Tab Descriptio n For Altium, DART, TRuepoint, MegaStar, and Velox radios the Configuration Viewer window has a single link tab. For MegaStar, this includes Radio PA status. For DXR radios, there is no RF tab; instead, see the Slot Configuration tab. For Constellation radios, Constellation Terminal radios display one link tab. Constellation Repeater radios display two link tabs. Each link tab has data for modem settings, protection settings, and link settings. Non-Farscan Constellation radios display one Link tab and the IP Routing tab: Constellation via Farscan Proxy radios do not display the IP Routing tab. 195 196 AVIAT NETWORKS PROVISION USER MANUAL Tab Descriptio n The radio frequency tab list listss infor information mation about the radio type (capac (capacity, ity, bandwidth and modulation) and the link settings. For Eclipse, XP4 and DART radios, if a radio frequency link has been established, both the local and the remote data displays. Ethernet (CTR 8540) Ethernet port values for a device. Hardware tab Hardware (Velox only) The Hardware tab lists the version of the supported platform and IDU serial number and barcode. 614-330055-001 DECEMBER 2015 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Tab Descriptio n Interfaces The device interfaces for a device. (ADR*, Memotec CX-U) * With firmware firmware later than P2.6. This tab provides the IP routing settings for a device. IP Routing Tab (TRuepoint 5000, Constellation without FarSca FarScan n Proxy only) MC Alarm Inputs Alarm inputs and relay outputs for the DVM’s conn connections. ections. and MC Relay Outputs (DVA, CAU) 197 198 AVIAT NETWORKS PROVISION USER MANUAL Tab Descriptio n Mux Modem Tab Mux modem settings for TRuepoint 4040/5000 or Constellation radios. (TRuepoint 4040 and 5000, and Constellation) PAI (DVA Only) Programmable Alarm Indicators (PAIs) for a DVM. 614-330055-001 DECEMBER 2015 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Tab Descriptio n POE (CTR 8540 only) POE plugins and related settings. Includes PSE Settings table which contains power of ethernet port specific informatio information n RSC and RPS (GP) Data about the Rad Radio io Service C hann hannel el and Rad Radio io Pro Protect tection ion Swi tching tching for the TRuepoint 6500 radio. (TRuepoint 6500, WTM 6000 6000)) NOTE: For more on the RSPI, RSC/RPS, and Service tab values for TRuepoint 6500, see the TRuepoint 6500 documentation. RSPI (TRuepoint 6500, WTM 6000 6000)) Radio Section Physical Interface values for the TRuepoint 6500. 199 200 AVIAT NETWORKS PROVISION USER MANUAL Tab Descriptio n Service data for the TRuepoint 6500 radio. Service (TRuepoint 6500, WTM 6000) Slot Configuration Tab (DXR Only) Details about each slot for the DXR radio, and the hardware and software installed at each slot. Software tab The Software Software tab lists the version of the software software fo forr the compo components nents o off the radio. Configuration Profiles for Bulk Configuration This section describes the pre-set profile options for using the Configuration Profiles. 614-330055-001 DECEMBER 2015 201 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES The Configuration Configuration Profiles Profiles function enables enables you to a apply pply configuratio configuration n settings to multiple devices, including to their alarms. Configuring multiple radios at the same time is called bulk configuration. Users must have administration or NOC Engineer access to set up Configuration Profiles and enable bulk configuration. Bulk configuratio configuration n options are available a vailable for the following following devices: devices: l Altium l CTR 8540 l CX/Megastar l Constellation l l DART Eclipse, including including options options for: for: Ethernet l l IDU ES l DAC ES l l DAC GE DAC GE3 l Portal Portal ACL and SNMP ACL configuratio configuration n l Radio account security l RADIUS l LE3000/LE3200 l Radwin 2000 l Radwin WL 1000 l TRuepoint l WTM 3100, 3200, 3200, 3300 3300 l WTM 6000 l XP4 To set up bulk configuration, see the following topics: l Create Cre ate and Execute E xecute a New New Configuration Configuration Profile Profile on page 202 202 l Configuration Profile Ref Refere erence nce on page 206 206 l Delete a Configuration Profile Profile on page 211 Create and Execute a New Configuration Profile From the Configur From Configuration ation Profile Profile screen, screen, you can select and update a Configuration Profile, apply it to one or more devices, and save it to apply it to additional devices. 202 AVIAT NETWORKS PROVISION USER MANUAL Procedure 1. Open the Configuration Profile window: l l From the me menu nu bar, select Configuration > Configuration Profiles. Or, right-click right-click a container container or a device and select select Configuration > Profiles from the right-click menu. 2. The Configuration Profile window displays the available profile options for the device in the left frame. In the right frame, it displays the selected profile option for viewing and editing. NOTE: Use the drop-down menu at the the upper left to view Supported, Al l , or Saved Confi Configuration guration Profiles Profiles for this this device type. You can als o Filt e r for configuration configuration profiles that contain a keyword. 3. In the right frame, select the profile option. Click the Read button to view the current settings for the device. NOTE: Th The e Read bu butt tton on is activated activated if you opened opened the the Con Config figurat uration ion Profile window by right-clicking an individual radio. Clicking this button reads the radio’s configuration configuration and automatically automatically enters the the information to the Configuration Profile window. 4. In the right frame, enter any changes to the configuration settings. See Configuration Profile Reference on page 206 for information on the different profiles. Then, click Next. 5. Select the devices where you will execute these thes e n new ew profile settings. The left frame displays the profile settings. settings. The right frame displays the devices available to receive this profile setting. Note that you can Filter the devices, or use a check box to select All Devices or Unmanaged devices. When you have selected the devices, click Execute. A message will ask you to confirm Executing the profile. 614-330055-001 DECEMBER 2015 203 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES 6. The new profile is executed and applied to the devices. A Task Manager screen displays the process. The Task Manager tracks the status by displaying the date and time that the bulk configuration command was issued, with the configuration name. Select the + to display the devices that had the bulk configuration command applied. NOTE: If you are writing changes changes to a TRuepoint TRuepoint device, a w arning mesExecuting g these changes will ov erwrite erwrite any previous sage displays: Executin settings. Click OK to finish finish saving the changes. NOTE: If you ar e wr iting iting Advanced Advanced or Ethernet Ethernet changes that iimpact mpact a Configuration tion Profil Profile(s) e(s) DAC GE, a warning message displays: These Configura may affect traffic. Are you sure you want to execute them? Click OK to finish saving the changes. 7. You can save a configuration profile by clicking the Save button in the Configur igurati ation on Pro Profi file less scr screen. the configuration profile: The Save screen displays, prompting you to name 204 AVIAT NETWORKS PROVISION USER MANUAL 8. The newly saved profiles appear when you select Saved in the drop-down menu. Each item includes a list of the scripts that are assigned to it. Select a script and click Next. 9. Select the Execute button to execute the saved profile. The Selected Object List window opens. 10. The Object List window lists only those radios that support the profile. 11. Select the Close button to close the Task Manager. 12. Select the Close button to close the Configur Configuration ation Profile Profile window. NOTE: Saved configurations configurations als o appear in the right-click right-click menu for the device. See the example below. 614-330055-001 DECEMBER 2015 205 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Delete a Configuration Profile on page 211 Configuration Profile Reference This section includes two tables with bulk configuration setting details: l Eclipse Configuration Prof Profiles iles l Profiles Profiles for All Other De Devices vices Configuration profiles apply apply configuration settings to multiple devices in a single transaction. This includes the ability to predefine the settings for one of more devices and then later writing to the devices, or copying the settings from one device, optionally editing, and then writing to the same or other devices. This section provides a list of the profiles available for each device type. For each profile, a description of the parameters that can be configured is provided. NOTE: Alarm Configu Configuration ration tabs tabs are s imilar for all device types. They list the alarms for the device or plug-in, plug-in, w ith a drop-down menu for severity levels, including Critical, Major, Minor, Warning, or Informational. You ca n reset the alarm s everity levels or use the Skip option option to skip them. Table 4-8. Eclipse Confi Configurat guration ion Profiles Con Configu figur ration tion Profi ofile Se Sett ttiings Eclipse AUX Module:Alarm Input Configuration Entry of descriptions and severity levels for additional alarms. Eclipse Alarm Configuration Defaultt Reset Defaul Check the box to reset all alarm values for an Eclipse device or plug-in to the factory defaults. Enter the Alarm Description and select the Severity level. 206 AVIAT NETWORKS PROVISION USER MANUAL Co Con nfigu figur ration tion Profi ofile Se Sett ttiings Enables Enabl es spec specific ific DAC G E3/IDU GE3 configurat configurations ions.. Eclipse DAC GE 3 Plugin: setting ing may affec affectt netwo network rk traffic. For more Eclipse Advanced Settings for NOTE: Changing this sett data on these values see the Eclipse Portal documentation. DAC GE3 Eclipse GE 3 Ethernet Module: Eclipse Advanced Settings for IDU GE3 - Flow Control - Check box to enable. - MAC Address Learning - Check this box to enable MAC Address Learning. - Max Frame Size - Set the maximum frame size. - Storm Control - Click to enable storm control. - Broadcast - Check this box to enable b roa roadcas dcast. t. - Multicast - Check this box to enable multicast. - Unknown Unicast - Check this box to enable unknown unicast. - Storm Traffic Rate % - Specify the % of storm rate (received broadcast and multicast traffi traffic) c) enabled from this port. A value of 0 filters all storm traffic: a value of 100 disables storm control. Enables spec Enables specific ific DAC GE/IDU GE configurat configurations ions.. Eclipse DAC GE PluNOTE: Changing this sett setting ing may affec affect t netwo network rk traffic. For more gin/Eclipse GE Ethernet data on these values see the Eclipse Portal documentation. Module: Eclipse Advanced - Flow Control - Check box to enable. Settings for DAC GE/IDU GE - Disable Address Learning - Check this box to disable MAC Address Learning: this is for devices used in ring/me ring/mesh sh networks networks.. - Link Status Propagation - Check to enable link status propagation. - Storm Traffic Rate % - Specify the % of storm rate (received broadcast and multicast traffi traffic) c) enabled from this port. A value of 0 filters all storm traffic: a value of 100 disables storm control. - Max Frame Size - Set the maximum frame size. - Restore Timer(s) - Set the restore timers value. Eclipse GE 3 Ethernet ModNOTE: Changing this sett setting ing may affec affectt netwo network rk traffic. ule: Eclipse Ethernet Port Set- Ethernet port settings for the selec selected ted Eclipse Eclipse device. tings for IDU GE3 Use the drop-down menus to select the required values for the usage, the speed, the duplex, and Master/Slave settings. Eclipse DAC GE3 Plugin: Eclipse Ethernet Port Settings for DAC GE3 Eclipse DAC ES Plugin: NOTE: Changing this sett setting ing may affec affectt netwo network rk traffic. Eclipse Ethernet Priority Map- Ethernet Priority Mode settings for the selected Eclipse devices. ping for DAC ES - Priority Mode - Select a Priority Mode to receive the priority values. Choose a value from: Port Default, Default, 802.1p, 802.1p th then en Diffserv, Diffserv, or Diffserv then 802.1p, Diffserv. Eclipse DAC GE Plugin: - In Internal ternal Prio Priority rity -Assigns a priority level to a device in this set of Eclipse Ethernet Priority MapPriority Mode priorities. Choose a value from Low, Mediu Medium m Low, ping for DAC GE Medium High, or High. Eclipse ES Ethernet Eclipse Ethernet Modul Module: e: Eclipse Ethernet Priority Map- ping for IDU ES Eclipse Ecli pse GE Ethern Ethernet et Modul Module: e: Eclipse Ethernet Priority Mapping for IDU GE 614-330055-001 DECEMBER 2015 207 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Con Configu figur ration tion Profi ofile Se Sett ttiings Eclipse DAC GE3 Plugin: NOTE: Changing this sett setting ing may affec affectt netwo network rk traffic. Eclipse Ethernet Priority Map- Ethernet Priority Mode settings for the selected Eclipse devices. ping for DAC GE3 - In Internal ternal Prio Priority rity - Assigns a Priority level to a device in the set of 802.1p,, Diffserv, Diffserv, and/or MPLS EXP.Choose Priority Modes: 802.1p EXP.Choose a value from Q0 (Low) to Q7 Q7 (H (High igh). ). Eclipse GE 3 Ethernet Module: Eclipse Ethernet Priority Mapping for IDU GE3 Eclipse DAC ES Plugin: NOTE: Changing this sett setting ing may affec affectt netwo network rk traffic. Eclipse Ethernet Port Settings Ethernet port settings for the selected selected Eclips Eclipsee device. Use the drop-do drop-down wn for DAC ES menus to select the required values for the speed, the duplex,the MDIX, and Priority settings. Eclipse DAC GE Plugin: Eclipse Ethernet Port Settings for DAC GE Eclipse Ecli pse ES Ethernet Ethernet Modul Module: e: Eclipse Ethernet Port Settings for IDU ES Eclipse Ecli pse GE Ethern Ethernet et Modul Module: e: Ethernet Priority Mapping for IDU GE Eclipse DAC GE3 Plugin: Eclipse Link Status Propagation for DAC GE3 NOTE: Changing this sett setting ing may affec affectt netwo network rk traffic. Link status propagation settings for the sele selected cted Eclipse devices, including: - Local Peer - local port peer. Remote Peer - remote port peer. Mode - Normal or Degraded. Restore and Hold timer values Eclipse Login Banner Con- Enter text to display before and after a user logs into Eclipse Portal from figuration Eclipse NMS Traps Destination a device. This is useful for warnings and administration requirements. NMS trap destination information for the selected radios. - Enable - Select the checkbox to enable the trap destination. - Destination - The IP address of the trap destination. - Destination - IP address of the destination. - Port - The UDP port at the trap destination. - Rate - The maximum number of traps that can be set per minute. - Operation Mode - From the drop-down menu, select whether the trap destination is powered by ProVision or a Third Party application. Eclipse OSPF Settings IP address of a server to use for OSPF sett settings, ings, and to enabl enablee OSPF OSPF use for the IP’s ports, AUX drives, and slots. CAUTION: OSPF sys system tem settings are complex. complex. An IP m ust be set up in Portal as enabled for OSPF for these settings to work correctly. This setting sett ing should should only be used by experienc experienced ed administra administrato tors rs with access to Portal. Eclipse Portal Lockout Reboot Time Set the time in seconds that the Portal Access will not be allowed (i.e., users will be locked out of Portal) after a reboot. 208 AVIAT NETWORKS PROVISION USER MANUAL Co Con nfigu figur ration tion Profi ofile Se Sett ttiings Eclipse Radio Account Configuration Set the user permissions for ProVision users for this specific Eclipse radio. See Setting Eclipse Device Security Values for more details. - User Name - Between 4 and 32 characters - Password - Between 8 and 32 characters - Confirmation - Retype the Password. - Enter this information for each user. - Permissions - Check the boxes for the user's permission levels for Eclipse radios: Read Only, Engineer, Admin, Crypto. At least one Permission must be selected for a user. Eclipse RADIUS Configuration NOTE: The RADIUS server must be enabled to use this. See Enabling a RADIUS Server. Set the RADIUS authentication "shared secret" in bulk for multiple Eclipse IP addresses. - Enable - Check to enable for noted radio - IP address - for Eclipse radio (valid for both IP4 and IP6) - Port - Authentication port - Shared Secret - Shared Secret value - Confirmation - Confirmation value NOTE: The Eclipse radios will try to authenticate any login request against each RADIUS server in the order they are listed until one of the RADIUS servers responds. Eclipse Security Portal ACL Configuration IP addresses in this list are able to connect to Portal. If Enable Portal ACL is i s checked and the IP address is not in this list, the IP addresses are denied access to Portal. - Enable Portal ACLACL- Check to enable Portal ACL for all Eclipse radios in ProVision. - IP Address - For Eclipse radio - Mask - Mask to apply to Eclipse radio range Eclipse Security SNMP ACL Configuration IP addresses in this list are able to send messages/commands to radios. If Enable Enabl e SNMP ACL is checked and the IP address is not in this list, the SNMP messages are denied. - Enable SNMP ACL - Check to enable SNMP ACL for all devices in ProVision. - IP Address - For SNMP server - Mask - Mask to apply to SNMP range Eclipse SNMPv3 User Account Sets up the users able to access Eclipse SNMPv3 devices with: - Name Configuration - Account Level - Crypto, Control, Admin, User - Authentication Password (twice to confirm) - Privacy Password (twice to confim) Click Remove to remove one user. Click Remove All to remove all users. Eclipse Time Server Settings IP address of of a time server that sync synchro hronizes nizes the interna internall cloc clocks ks o off the network components. Eclipse Time Server Select the checkbox to activate the Eclipse time server setting. - IP Address - IP address of the Eclipse time server. Eclipse Time Zone Settings 614-330055-001 Time zo zone ne to appl apply y to one one or more sel selected ected rad radios. ios. U Use se the dro drop-do p-down wn menu to select the required time zone. DECEMBER 2015 209 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Con Configu figur ration tion Profi ofile Se Sett ttiings Eclipse SNMPv3 User Accounts Create or remove SNMPv3 security users, i ncl ncluding: uding: - Name - User name - Access Level - Security access level - Authentication Password - Privacy Password Table 4-9. Profiles for All Other Devices Con Co nfigur igurat atio ion n Pro roffile ile Set Settings ings Altium/XP4: XP4 16xE1 Trib Altium/XP4: Controls When you configure the trib cont controls rols for each of the 16 tribs, you cho choose ose whether the trib is Normal (commissioned) or Inverted (not commissioned.) Note that Normal tribs will report errors if they have no traffic. Constellation Trap Destinations Trap destination information for the Constellation radios. - Destination - The IP address of the trap destination. NOTE: This data is not active for Constellation for FarScan devices. DART NMS Trap Destin- Select up to three trap destinations for the following components of the DART radios: ation -- Ethernet Radio - Serial Port 1 - Serial Port 2 Select the check box to activate the trap destination for the selected component. In the Destination field, enter the IP address for the specified trap destination. LE3000/LE3200 Trap Destinations Trap destination information for the LE3000 or LE3200 radios. - Destination - The IP address of the trap destination. - Port - Enter the port required for the trap destination. Radwin 2000 Trap Destinations Trap destination information for the selected Radwin 2000 devices. - Destination - The IP address of the trap destination. - Port - Enter the port required for the trap destination. WinLink WinLin k 1000 Trap Destinations Trap destination information for the selected WinLink 1000 devices. - Destination - The IP address of the trap destination. TRuepoint SNMP Managers: 5000, 4040, 4000 TRuepoint Trap Destinations: ation s: 6400, 5000, 5000, 4040, 4000 - Port - Enter the port required for the trap destination. Trap destination information for the selected type of TRuepoint radios. - Enable - Select the checkbox to enable the trap destination. - Destination - The IP address of the SNMP manager. NOTE: Executing these changes overwrites any previous settings, and disabling SNMP managers also disables ProVision’s SNMP connection to the device. Trap destination information for the selected type of TRuepoint radios. - Enable - Select the checkbox to enable the trap destination. - Destination - The IP address of the trap destination. WTM 310 3100 0 Time Time Mana Manager ger Time zzone one information information for the WTM 3100 devices. - Enable - Check to enable time management. - Destination - IP address of the WTM 3100 device. - Time Zone - Select time zone of device. WTM 310 3100 0 Trap Destinations Trap destination info information rmation for the sselected elected WTM 3100 devices. - Enable - Check this box to enable trap destination management. - Destination - The IP address of the trap destination. 210 AVIAT NETWORKS PROVISION USER MANUAL Con Co nfigur igurat atio ion n Pro roffile ile Set Settings ings WTM 3200 SNMP Mana Managers gers SNMP ttrap rap destina destination tion info informatio rmation n for th thee WTM 3200 devic devices. es. - Enable SNMP - Check to enable S NMP manag management. ement. - IP Address - The IP address of the trap destination. WTM 33 3300 00 NMS Trap Destinations - Port - Enter the port required for the trap destination. NMS Trap destina destination tion informat information ion for the selected WTM 3300 devices. - Domain - The specified domain. - Destination - The IP address of the trap destination. WTM 33 3300 00 Time Zone Time zo zone ne to apply apply tto o one or more devices devices.. Use the dropdrop-down down menu tto o select the required time zone for the radio. WTM 6000 Trap Destina Destinations tions Trap destination information for the select selected ed WTM 3100 or WTM 6000 6000 devices. Destination - The IP address of the trap destination. Delete a Configuration Profile on page 211 Table 4-10. CTR CTR 8540 / 8300 Configu Configuration ration Profiles Con Co nfigur igurat atio ion n Pro roffile ile Set Settings ings CTR - Qos - Classification CTR - QoS - Scheduling For more information, go to Quality of Service Service - Classific C lassification ation. For more information, go to Quality of Service - Scheduling. CTR Syslog Forwarding Syslog trap forwarding destination for the selected devices. - Address Type - Select the checkbox to enable the trap destination. - Address - The IP address of the destination ProVision server. - Port - The port number of the destination ProVision server. - Protocol – The protocol used to send syslog events. This can be UDP, TCP or TLS. CTR Time Server IP address of a time server that sync synchro hronizes nizes the interna internall cloc clocks ks of the network devices. d evices. - Tim Time e Server - Select the checkbox checkbox to activate the time server setting. - IP Address - IP address of the time server. CTR Time Zone Settings Time zo zone ne to be appl applied ied to the selected selected devices devices.. Use the drop-down menu to select the required time zone. Delete a Configuration Profile You can delete a saved configuration profile. Note that you cannot delete one of the default configuration profiles provided by Aviat Ne Network tworks. s. You can only dele delete te configuration configuration pro p rofile filess that you or your users ha have ve create created. d. Procedure 1. From the menu bar, select Configuration > Configuration Profiles. The Configuration Profiles window opens. 2. From the left side of the screen, select the saved profile to delete. 3. Select the Delete bu butto tton. n. Pr ProV oVisi ision on asks asks if you rea eally lly want want to dele delete te the selected profile. Select Yes to continue. 614-330055-001 DECEMBER 2015 211 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES 4. The selected profile is deleted. It will not be available in this screen or in the rightclick menus. 5. Select the Close button to close the th e Configuration Configuration Profiles Profiles window. Quality of Service - Classification This screen displays QoS - Classification. Users can configure priority mapping and classification for VLANs and interfaces. Supported classification includes priority types for 802.1p, DSCP and IP ToS. VLANs and interfaces interfaces with identical classification configurations are grouped together. Procedure 1. Go t o Qos - Classification. 2. To re read ad the cur curre rent nt device device's 's Classif Classificati ication on cli click ck the Ic Iconon-Re Read. ad. See See Create and Execute a New Configuration Profile for details on reading configuration profiles. n The Policy map is also read and will replace the policy map of the selected CTRs when the configuration is executed. 3. Pri Prior ority ity mapping and classific classification ation settings settings display by classification classification type (Interface , VLAN). Types that have identical configurations are grouped together. 4. To add a ne new Classi Classifi fication, cation, select the type (Interface , VLAN) and click on the Priority type to Add (Vlan 802.1p, IP Tos, IP DSCP, MPLS EXP). 5. Clicking on the Classificatio Classification n will either either collapse or expand it. 6. To rem remove ove a classifi classificatio cation, n, expand expand it and clic click k the Remove button. 7. The value valuess for the cl classif assificati ication on display. display. You can change change:: n Enabled status of a Priority mapping n Ingress priority to Internal Priority mapping n Pre-Color n Drop Precedence n Policy Map - Note you will need to read a radio to get all the policies. 8. Yo You u can can add an Interface or VLAN, depending on the Type of the classification, classific ation, by selecting selecting the Applies To button. n n You can only add a VLAN that ProVision knows about but only the VLANs that the radio knows about will be ap applied. plied. ProVision shows all possible Interfaces that a CTR can have but only the Interfaces that the radio knows about will be applied. 212 AVIAT NETWORKS PROVISION USER MANUAL o A port-channel can have any number assigned to it, so port-channels are shown by their If Index. For example, po (If Index=27). Figure Figu re 4- 6. Qos - Classification Figure Figu re 4- 7. Figure 4-8. QoS Policing Policing Values Values Fi e l d De scription QoS Group Click on a classification classification to display the values for a QoS group. Internal Priority Displ Displays ays the internal priority assigned assigned to ingress ingressing ing traff traffic ic for the interface/ VLAN. Default is 0, lowest priority. Enable Check the box to enable enable this priority level level.. Eac Each h priority mapping crea creates tes a rule on the switch. As there are limited rules, it is recommended that for IP DSCP only the priorities in use should be enabled. Set the pre-col pre-color or policing value from the drop-do drop-down wn menu. Set the pre color color policing value from the drop do down wn menu. - None - Red - Yellow Pre Color - Green 614-330055-001 DECEMBER 2015 213 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Fi e l d De scription Policy map/policin map/policing g Set policing policing values values for policy policy map ID and policing policing mode. Optio Options ns displayed are policies configured via E-Portal Quality of Service - Policing. NOTE : A policy must be configured for traffic to flow. Default configuration contains Policy 1 with no metering. Quality of Service - Scheduling This screen screen displays scheduling scheduling action by enabled enabled interf interface. ace. Users can set QoS Scheduling algorithms and congestion control for each enabled QoS interface. There are eight queues for each interface. Procedure 1. Go t o Qos - Scheduling. 2. To re read ad the current current device's device's Scheduling Scheduling click the Ico Icon-R n-Read. ead. See See Create and Execute a New Configuration Profile for details on reading configuration profiles. n 3. The Congestion Control map is also read and will replace the Congestion Control map of the selected CTRs when the configuration is executed. Any Por Ports ts that have a def default ault configuratio configuration n are shown b beside eside the Default Ports button. n n The default configuration is Strict Priority Priority an and d Congestion None.. Control of None The ports are shown in compressed format. For example, 0/1, 0/2, 0/3, 0/5 will be shown as 0/1-3,5. 4. To change change a ports de defaul faultt configur configuration ation cclick lick the Default Ports button and untick that port. 5. Yo You u can can vi vieew Internal Priority and Weight values. You can change: n Scheduler - Select the Scheduler algorithm. Options are listed in the table below. n Congestion Control - Select either None or one of the configured queue templates. 214 AVIAT NETWORKS PROVISION USER MANUAL Figure Figu re 4- 9. Qos - Scheduling 614-330055-001 DECEMBER 2015 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Figure 4-10. 215 216 AVIAT NETWORKS PROVISION USER MANUAL Figure 4-11. QoS Policing Policing Values Values Fi e l d De scription Scheduler Select the QoS Scheduling algo algorithm: rithm: -- S trict Priority Round Robin - Wei ghted Roun Round d Robin Robin - Weighted Fair Queuing - Strict Round Robin - Strict Weighted Round Robin - Strict Weighted Fair Queuing - CIR EIR - Committed and excess rate algorithm - Strict CIR EIR - Strict committed and excess rate algorithm CAUTION : CIR EIR options are not supported on radio, L1LA or protection interfaces Internal Priority Displ Displays ays the Internal Internal Prio Priority rity sett setting ing for each queue. Weight Displ Displays ays the weighting appl applied ied to weighted scheduler scheduler action actionss by queue. A color square displays the apportionment of weighting by weighted queue. NOTE: Configurable only for scheduling algorithms that use weights. For Weighted Fair Queuing and Strict Weighted Fair Queuing - the weight must be larger than the interface's MTU. Congestion Control Enable con congestion gestion control control by selecting an option, from the list of configured queue templates. Configure these from E-Portal's Quality of Service - Congestion Control. Viewing/Changing Network IP Addresses The network network configuratio configuration n gives you a list of the device IP addresse addressess ente entere red d via Pro ProViVision. From here you can view and change the ProVision device IP addresses. This function enables you to view a list of the network devices’ IP address and where required, change an IP address. NOTE: Changin Changing g a device’ s I P address within within ProVision d does oes not change the IP address s tored in th the e device itself. Procedure: 1. From the menu bar, select Configuration > IP Address. The IP Address window displays. To display all the devices and associated IP addresses at once, select Expand All Levels. 614-330055-001 DECEMBER 2015 217 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES 2. Double-click the IP addresses to be changed, and type the new IP addresses. 3. To apply the new IP addresses, select Apply. O K. 4. To accept the changes, select OK Viewing/Changing TNet Proxy Configurations The information in this section is only relevant if your network has TNet devices deployed deploye d and commissione commissioned. d. The Proxy Proxy Configuration Configuration Manager displays a subnet subnet view of t he networ network’s k’s TNe TNett Proxies. Proxies. From the Configuration Manager, you can identify how many subnets have been set up for each Proxy, and which devices are grouped under each subnet. Use this function when setting up the network to ensure the TNet radio details in ProVision match those stored in the TNet Proxy. When you select a TNet TNet device it s configuration parameters stored in ProVision are a re disdi splayed. You can change the device name, and the subnet in tandem with the necessary cabling changes between the Proxy and its devices. 218 AVIAT NETWORKS PROVISION USER MANUAL CAUTION: If I f you change change a subnet subnet without without moving moving the the device’s device’s cabling to the the new new sub- ne net, t, when ProVisi ProVision on next next polls polls the Proxy, Proxy, the device device display displayss in an errored state. state. NOTE: The TNet device device icons ar e detailed in in TNet Devices on page 2-34. Procedure 1. In the Tr Tree ee Viewer Viewer or Map Viewe Viewer, r, rightright-cli click ck a TNe TNett Proxy Proxy ic icon. on. right-click menu displays: The Proxy Proxy 2. Select Proxy Configuration Manager. The Pro Proxy xy Configur Configuration ation Manager window displays. Activity Activi ty How to... Select the required Proxy icon. To change a Proxy’s name or increase its number of subnets within withi n ProVis ProVision: ion: Make the required changes to the Subnets field. There is a maximum of 16 subnets per Proxy. To save the changes within ProVision, select Commit Changes. Changes. To change a Proxy’s IP address: Viewing/Changing Changing Ne Network twork IP Addresses Addresses on page pa ge 217. See Viewing/ To move a TNet device from one subnet to another subnet Expand the Proxy and the subnet to display the TNet devices. Select the required TNet device. and/or change the TNet’s address on the subn subnet: et: The device’s name, the subnet it is connected on, and its address on the subnet are displayed. Enter the new subnet number and/or the new address. Select Commit Changes. Changes. To close the Proxy Configuration Manager window, select Close. 614-330055-001 DECEMBER 2015 219 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Using the TNet Proxy Viewer The TNet Proxy Viewer enables you to identify where there are problems with TNet devices, and if the problems are in ProVision or the TNet Proxy. In the Proxy Viewer, the Subnet to Radio Status columns contain TNet device data read from the Proxy. The ProVision name, type and status columns contain the device data stored in ProVision. NOTE: You must have a Con Configu figuration ration security profile as a user to access the Proxy Viewer. Procedure 1. In the Tree Viewer or Map Viewer, right-click the required TNet Proxy icon. Or, locate and right-c right-click lick the TNet TNet Proxy icon in the Proxy Configur Configuration ation Manager scre screen. en. 2. From the right-click menu, select Proxy Viewer. 3. The Proxy Viewer < proxy name> name> window window displays. 4. Check for any discrepancies between the Proxy and ProVision radio data. 5. To close the Proxy Viewe Viewerr window, select select Close. 220 AVIAT NETWORKS PROVISION USER MANUAL Loading/Activating New Software and Licenses This section describes how to load and activate new Eclipse, CTR 8540, and TRuepoint software, and new Eclipse node lice nses. l About Loading Device Software Via ProVision on page 221 221 l Eclipse Softwar Softwaree Loading Loading Examples on page 222 222 l Stage 1: Software Software Load Load Procedure on page 224 224 l Stage 2: Sof Software tware Activation Procedure Procedure on page 230 230 l Eclipse and CTR Node Node Licenses Licenses on page 237 237 l Devicee Configuration Devic Configuration Backup and Restore Restore on page 240 Aboutt Loading Device Software Abou Software Via ProVision CAUTION: Before loading and activatin activating g new software, it is importan importantt to review the the release notes and th the e ReadMe file that that accompany the the new software version to be aware of any caution cautionss and advice notes. notes. Using ProVision, ProVision, you can re remote motely ly upgrade software for the follo following wing devices: devices: l All Eclipse Radios l All TRuepoint TRuepoint Radios l l CTR 8540 WTM 3300 You can do this for multiple mul tiple devices simultaneously, simult aneously, using the Loading/Activat Loading/Activating ing New Software feature. You select a number of devices to be loaded, in a single task. Then, ProVision transfers the software from the software register to the devices. This feature also p rovides rovides the fle flexibility xibility to sequentially sequentially run a number number of separate sof softwaretware-loading loading tasks to different devices and device types. Once the transfer is completed, you can activate the software in the radio in one of two ways:: ways l Manu Manual al Activati Activation on - ProVision lets you activate each radio manually. This is available for Eclipse, TRuepoint, TRuepoint, CTR, and WTM devices. devices. l Scheduled Activati Activation on - For Eclipse devices only, ProVision also lets you select a date and time to automatically activateinone or sections more radios. This is useful automatically activate the new software large of a network at a to time when there there is minimal traffic, traffic, minimizing network network disruptions. 614-330055-001 DECEMBER 2015 221 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES An entire network of devices can have new software ins installed. talled. And by being being able to select an activation time to coincide with low circuit usage, you can ensure minimum disruption to network traffic. NOTE: When loading software using this this feature, feature, the same vers ion of the software is loaded onto all parts of a device. W AR NI NG : Do not initiate software loading during the period when daily performance collection is performed (default 1 am); this can result in a failed data collec tion poll. poll. The Software Upgrade Upgrade P Proces rocesss The software upgrade is split into two separate stages: loading and activation. l l Stage 1: Software Software Load Load Procedure on page 224 - The loading stage is slow, especially for Eclipse devices, and can take up to 30 minutes or longer. Because the loading proc process ess does not affec affectt the network traffic, traffic, this slower slower stage of the software upgrade can be initiated at any time. Stage 2: Sof Software tware Activation Procedure Procedure on page 230 230 - The activation stage, although it occurs almost instantly, may affect network traffic. Because of this, the activation stage is under separate control to allow you to select a time when network traffic is least affec affected. ted. The following is an overview of the individual steps that make up the software download procedure. 1. Bring the new version of device software into the ProVision Server software register. 2. Identify the number of download tasks needed in order to upgrade the network. A software download task refers to the number of devices to be grouped together for a download. 3. Create and initiate a software download task, by selecting the device type, the software version, and the radios to be loaded. load ed. Monitor progress using the ProVision Task Manager. 4. On download completion, activate the software in the devices from the ProVision Task Manager and monitor activation p pro rogre gress. ss. 5. Repeat steps 3 and 4 for other software download tasks. Subsequent tasks begin as soon as the previous task completes loading. The ProVision Task Manager can be used to simultaneously activate software across tasks. Two software loading examples are shown, for Eclipse radios. Eclipse Software Loading Examples This first example divides the network into levels and loads the Eclipse software to each level as a single task. The first such task would be to load the software to the radios at 222 AVIAT NETWORKS PROVISION USER MANUAL the farthest points from the operation center. This group is called “Level 1” in the example below. The remaining levels can be loaded in subsequent tasks as shown. Figure Figu re 4- 12. Example 1: An Eclipse Radio Radio Network Divided Divided into into Levels The second method is to divide the network into regions and load the Eclipse software to each region as a single task as shown. 614-330055-001 DECEMBER 2015 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Figure 4-13. Example 2: An Eclipse Radio Network Network Divided into into Region Regionss Stage 1: Software Load Procedure The software load procedure is further divided into two parts: Part A: Register Register the Software Software onto the ProVision Serve Serverr l l Part B: Load the Software Software onto the Device Devicess Part A Register the Software onto the server Prerequisites 223 l l Ensure that the current current software software (the ve versio rsion n that is about to be replaced) replaced) is listed in the Software Register. In the event of a problem while loading the new software, the current version can be re-installed if needed. For Eclipse devices with Strong Security enabled, to enable ProVision to load software updates, you need an active SNMPv3 user account for the devices, set up with the Crypto access level. An Eclipse SNMPv3 user account can be set up from the Portal craft tool, or set up from ProVision via the Configuration 224 AVIAT NETWORKS PROVISION USER MANUAL Profile Settings. See Setting SNMPv3 Security Access on page 1 for more details. CAUTION: Before loading loading software onto a network network of devices, always complete th the e load and activat activation ion one one radio radio a test and and check for for normal op operati eration on in the the lab before download downloadin ing gtosoftware toin the live lab, network. Procedure 1. From the menu bar, select Configuration > Software Loading Preferences. The Software Software Loading Pre Prefe fere rence ncess window d displays. isplays. It lists all software software versio versions ns that were were previously registered. NOTE: If the required required softwar e is already listed on the the register, proceed to Part B Load the Software onto the Devices on page 227 . 2. Click on the Register menu and select the type of software pack that you want to load. 3. A directory window displays. 4. You need to select the software that you will load. Either: Select Select the directory directory that tha t contains the th e software. software. Select Select the desired desired software pack and select Open. l 614-330055-001 DECEMBER 2015 225 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES l Place the CD with the software software update (the file file type is *.swpack) *.swpack) in the CD ROM drive. Select the CD ROM drive from the drop-down menu. Select the desired software pack and select Open. 5. The new software pack now appears on the software register register.. 6. To set the server value for the software type, select the software type, then go to the Servertab. Two features are displayed: Server IP Address and Concurrent Loads. Ensure the Server IP Address is set to the IP address of the network interface card facing the radio network. This is particularly important for servers that use multiple network interface cards 226 AVIAT NETWORKS PROVISION USER MANUAL ProVision writes this IP address to the radios of this type. When the software download is started, the radios use this IP address as the one it looks for to find the new software. 7. Select the number of concurrent loads using the Concurrent Loads slide bar. The Concurrent Loads slide bar contr controls ols t he number of softwar softwaree transfe transfers rs that tha t can be performed performed at the same time. The number nu mber of which (1 - 15) is dependent on the network’s bandwidth band width.. The Concurrent Loads slide bar allows you to tell ProVision how many radios it can simultaneously load software to. If a network has 2000 radios, the ProVision application can take quite a long time to load the software if it does so one radio at a time. But if the Concurrent Loads is set to 10 (and if the network has the available bandwidth)) the time to load the software t o all 2000 radios would be much width mu ch faster. 8. Select OK to close the Software Loading Preferences window. Part B Load Load thefrom Software ontoscreen. theYou Devices software the Software Loading can open this screen from the right-click menu in the Tree Viewer for a site or for a device, container or service. You can also open it from the main menu. 614-330055-001 DECEMBER 2015 227 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Heading Description Status If this item is blan blank k for a device, the device is live and avail available able to have new software loaded. Problem icons are: = fata fatall conditio condition n exists for the device, and software software canno cannott be loaded. Note that items with this status are grayed out. = Incompatible objects. = warning icon noting that there are problems with this device, which may impact on software loading. loading. Object The type and name of the device. Container The IP name of the co container. ntainer. Software Version(s) The version number of the currently installed software. The Software Loading screen identifies the following for each unit in ProVision: You can select the type of software that you are loading, and you can filter the Software Loading screen to view only devices that match a specified software type. NOTE: The software download process may take up to 30 minutes or longer, depending on the network bandwidth, the num ber of concurrent loa loads, ds, the number of d evices evices being l oaded within the task, and the size of the software file being load d. Eclipse software normally takes 30 minutes or longer to load; TRuepoint software may load more quickly. Procedure: 1. From the menu bar, select Configuration > Software Loading. The Software Loading window displays. 2. In the Type menu, select the device type. The Software Loading scree screen n displays each device of that type in the network, the container where it is located, and its current software version. 3. In the Operation menu, select the software type to load. The devices of that type display. In the sample below, for the TRuepoint software loading, there are Operation menu options for standard TRuepoint or RFU upgrade. 4. Select the devices that are to have the software loaded. To organize or filter the devices, you can: l l Select Select the column he heading ading Object Container to sort the devices by their location in the network. To load load a group of device devicess that are a re listed se seque quentially, ntially, hold down d own the shift key and select the first and last device in the list. 228 AVIAT NETWORKS PROVISION USER MANUAL l l To load load a group of device devicess that are a re not liste listed d sequentially, sequentially, hold down the ctrl key and select each device. To identify identify devices devices that are not not compatible with the software software type, click filter Incompatible Objects. An exclamation mark displays beside any incompatible objects. 5. For Eclipse, CTR8540, CTR8300 and WTM3300 devices, you can Select the Scheduled Activation check box to activate the software at a specific time. To set the day and time for scheduled activation, highlight an item (for example, the hour) in the text box and adjust it using the up or down arrows. NOTE: If you do not select Scheduled Activation Activation,, the software activates immediately after you click Load Selected Software . 6. Select the software pack version to be loaded from the Operation drop-down box. (The version that was loaded in steps 2 and 3 appear in the list.) 7. Select the Apply Selected Objectsbutton to begin the t he download download.. 8. A ProVision message box appears. Select Yes Y esto close the So Software ftware Table Table window and open the Task Manager window. Alternatively, select No to leave the Software Table Table window open. open. The Task Manger window can be opened at anytime by selecting the Task Manager icon . 9. The Task Manager window appears. Select the + to view the objects that are being updated. A bar chart indicates the progress of the download. 10. The download is complete when the bar chart indicates 100%. At that time the Activatebuttons appear. app ear. See Stage 2: Software Activation Procedure on page 230 for the next steps to take. NOTE: If you selected sc heduled heduled activation activation for an Eclipse device, instead of Activatebuttons appearing, a timer displays which counts down the amount amount of time before the scheduled activation activation occurs . 11. If the sof softwar twaree load load fails, fails, or is inc incomple omplete te,, an alarm iico con n displays: rightright-cli click ck on the icon to view information about the software loading problem. 614-330055-001 DECEMBER 2015 229 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES If the software loading fails for a WTM 3200 device, the following message may display: To resolve this, reconfigure the WTM 3200 to support https mode: Unmanage it, then Manage it again and retry the software loading. See Managing a Device on page 156 12. Stage 2: Software Activation Procedure on page 230 Stage 2: Software Activation Procedure The activation procedure procedure is when software, installed in Stage 1: Software Load Procedure on page 224 is switched on. There are separate procedures for: l Eclipse Software Activation Procedure Procedure on page 231 l TRuepoint TRuepoint Software Activat Activat ion Procedure Procedure on page 233 233 TRuepoint TRue point Software Activat Activat ion Procedure Procedure on page 233 233 l Other Software Software Activation Procedure Procedure on page 236 236 Recommended Activation Process The activation process, specifically the reboot (software reset), may or may not affect traffic. It depends on the software release, the update destination within a node/ter- 230 AVIAT NETWORKS PROVISION USER MANUAL minal, and the hardware versions. Always assume that traffic may be affected when scheduling an activation. To minimize the possible disruption of the network, it is recommended to begin by activating at the farthest pointssite from One reason is toaffectavoid the the devices loss of visibility of a remote in the the operations event therecenter. is a software problem ing the normal link operations to or from the newly-loaded site. Also, if there is a trafficaffecting problem, then by going first to a remote site, the least amount of traffic is affected. Eclipse Software Activation Procedure To activate the Eclipse software after it has been loaded onto the devices, follow steps 1 through 6. NOTE: For Eclipse devices, when the software is loaded it resides in both the IDU and the ODU. For an Eclipse Node, the software resides in the NCC and in each ODU plug-in. For an Eclipse Terminal, the software resides in the IDU and ODU. 1. Select the Activate button to activate the software inside the Eclipse device. The Activate button changes to a Running button utton and an in info form rmati ation on icon icon appe appear ars. s. If the Activation fails, a message displays, with a recommended action forpreparing the device. 2. Sele Select ct the the icon icon to ope open n a pop-up pop-up wi window ndow that track trackss the activatio activation n proc proces ess, s, which is divided divid ed into three steps: steps : activation, activa tion, reboot, reboot, and verify. l Activation (<10 sec.): The Eclipse device switches IDU (indoor unit) and ODU (out switch thenew newsoftware software.inThe messages OK” and “NCCdoor OK”unit) indicate thattothe both the ODU“ODU1 and the NCC, respectively, is now activated. l 614-330055-001 Reboot (90 sec. to 2 min.): The Eclipse device reboots reboots (resets (resets the software). software). DECEMBER 2015 231 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES l When the message “Wait “Wait for re reboo boott OK” appear app ears, s, it indicates that the reboo reboott is complete. When the message “Wait for plug-ins OK” appears, it indicates that the plug-ins (such as the RAC and DAC) are communicating with the NCC. NOTE: It is only during tthe he reboot step (which typically typically las ts less than 30 sec onds) that traffic traffic c an be affected. During the the re boot, NMS vis ibility ibility of the rebooted device and any downstream devices are lost. l Verify (2 to 5 min.): ProVision checks the to make sure the software version in the IDU and ODU is the same as the version in the Software Table (Stage (Stage 1: Software Load Procedure on page 224). 224 ). The message “versions OK” indicates the two versions are the same. 3. The process is complete when each of the activation steps indicates OK. 4. Right-click the task bar to open a pop-up window with additional functions. Tooltips over the task provide details such as description, status, start, and end time for the task. It also keeps a count of the goals within the task that are errored and completed. l Abort - Ends the task. This option is only available during the loading and activation steps. If the task is aborted, both the task and its list of devices remain in the Task Manger. The status for the task and each device within the task is listed as “Aborted.” Note that you cannot abort Activation. 232 AVIAT NETWORKS PROVISION USER MANUAL l Delete - Deletes the task from the Task Manager. This option is available after the task is complete and the task cannot be deleted while it is running. The task remains in the Task Manager until you delete it or until you log out of the ProVision Pro Vision Client C lient application. ap plication. 5. Right-click the individual device within the task to open a right-click window with additional functions. functions. l Results - Displays the results of the software loading and activation process for the particular device and lists the description, status, start, and end time for the process. 6. Select the Close button to close the Task Manager window. TRuepoint Software Activation Procedure To activate the TRuepoint software after it has been loaded onto the devices, follow steps 1 through 7: NOTE: Before you begin, begin, ensure that the the TRuepoint TRuepoint devices devices have been set up with the the corr ect FTP cr edentials; edentials; s ee the Device Security Accounts scr een een.. NOTE: Standard Standard TRuepoint TRuepoint software and RFU upgrades ar e separate software load procedures. See Step 4 of Stage 1: Software Load Procedure on page 224 for the software loading prerequisite for an RFU upgrade. 1. Beside the TRuepoint device, a drop-down menu button displays with options: l Alterna Alternate te System l l l The following process is executed: Switch the software software banks banks and activate the new new Controller Controller software, through the Alternate Software process (see below). Then Then load t he new interf interface ace card card firmware and activate, through the Firmware Upgrade process (see below). Alterna Alternate te Sof Softwar tware e – Activates the new Controller software through the following process. Note that this process does not affect traffic: 614-330055-001 DECEMBER 2015 233 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES l l l Switch the software software banks, banks, with the Altern Alternate ate now becoming bec oming the Primary bank. Re Reboo boott of the Controller, Controller, resulting resulting in activation of the new Controller software. Firmware Upgrade – Activates the new interface card firmware through the following process: l l l The Controller loads the th e new new interface card firmware into the cards. Activate the new firmwar firmwaree in the cards. cards. RFU Upgrade – Activates the new RFU firmware directly. NOTE: The Firmware Upgrade process affects traffic. For TRuepoint 5000 and 4040v2, only the SPU cards (MUXes and modems) are loaded, but not the RFU(s). The RFU(s) c an be loaded with the the new firmwar e in the the active bank through throug h Web CIT (see the final step of these instructions instructions for details). details). For TRuepoint 6400, all cards (LIU, DPU, OPT, RCVR and XMTR) are loaded. 2. Select the activation option you require for the TRuepoint device. The button changes to a Running bu butto tton n and an in info form rmati ation on icon icon appe appear ars. s. 3. Se Sele lect ct the the icon icon to ope open n a pop-up pop-up window window that track trackss the activatio activation n proc proces ess, s, which is divided divid ed into three steps: st eps: activa activation, tion, reboot, reboot, and verify. l Activation (<10 sec sec.): .): The TRuepoi TRuepoint nt device switches switches to t he new softwar software. e. l Reboot (90 sec. to 2 min.): The TRuepoint device reboots (resets the software). The “Wait for reboot OK” message indicates that the reboot is complete. 234 AVIAT NETWORKS PROVISION USER MANUAL NOTE: TRuepoint traffic is affected during both Activation and Reboot stages. During the the r eboot, NMS visibility visibility of the r ebooted device and any downstream devices are lost. l Verify (2 to 5 min.): ProVision checks to make sure the software version in the device is the same as the version in the Software Table (Stage (Stage 1: Software Load Procedure on page 224). 224 ). The message “versions “versions OK” indicates t he two ver versions sions are the same. 4. The process is complete when each of the activation steps indicates OK . 5. If a TRuepoint software load has failed, it displays in red. Right-click on the device to view the reason for the software load failure. Possible reasons include: l l Upgrade Agent Agent Not Not Acce Accessible ssible - The radio has failed to reboot after the upgrade. Repeat the Activation from step 1. Failed To To Send - Radio is having problems receiving the upgrade: could be a configuration problem with the radio. 6. Right-click the software type-level task bar to open a pop-up window with additional functions. functions. l Abort - Ends the task. This option is only available during the loading and activation steps. If the task is aborted, both the task and its list of devices remain in the Task Manger. The status for the task and each device within the 614-330055-001 DECEMBER 2015 235 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES task is listed as “Aborted.” Note that you cannot abort Activation. l Delete - Deletes the task from the Task Manager. This option is available after the task is complete and the task cannot be deleted while it is running. The task remains in the Task Manager until you delete it or until you log out of the ProVision Pro Vision Client C lient application. ap plication. 7. To verify verify that the software version version has loaded corr correctly ectly for the TR TRuepoi uepoint nt devices, devices, open the Configuration Viewer for each device and check the Inventory tab. This tab should show that the correct firmware version is now loaded to the device. See Viewing Configuration for Devices on page 194 194.. 8. Select the Close button to close the Task Manager window. Other Software Activation Procedure To activate the software after it has been loaded onto the CTR8540, CTR8300, WTM3200 WTM3 200 and a nd WTM3 WTM3300 300 devices, d evices, follow steps 1 through 6. 1. Select the Activate button to activate the software inside the device. The Activate button changes to a Running b butto utton n and and an in info form rmati ation on icon icon appe appear ars. s. If If the Activation fails, a message displays, with a recommended action for preparing the device. 2. Se Sele lect ct the the icon icon to ope open n a pop-up pop-up window window that track trackss the activatio activation n proc proces ess. s. Usually, once the activation is triggered, the device will be restart with new firmware. l Reboot: The device re reboo boots ts (re (resets sets the software) software) which may take few minutes. l When the message Wait for re reboo boott OK appear app ears, s, it indicates that the reboo reboott is complete. NOTE: During reboot traffic can be affected. The NMS visibilit visibilityy of the rebooted device and any downstream devices are lost. 3. Right-click the task bar to open a pop-up window with additional functions. Tooltips over the task provide description, status, start, and end time for the task. It also keeps a count of the goals within the task that are errored and completed. 236 AVIAT NETWORKS PROVISION USER MANUAL l Abort - Ends the task. This option is only available during the loading and activation steps. If the task isThe aborted, thetask taskand andeach its list of devices remain in the Task Manger. statusboth for the device within the task is listed as “Aborted.” Note that you cannot abort Activation. l Delete - Deletes the task from the Task Manager. This option is available after the task is complete and the task cannot be deleted while it is running. The task remains in the Task Manager until you delete it or until you log out of the ProVision Pro Vision Client C lient application. ap plication. 4. Right-click the individual device within the task to open a right-click window with additional add itional functions. l Results - Displays the results of the software loading and activation process for the particular device and lists the description, status, start, and end time for the process. 5. Select the Close button to close the Task Manager window. Eclipse and CTR Node Licenses Eclipse and CTR 8540 Node licenses can be downloaded to individual Eclipse radios or CTR 8540 devices, one at a time or in bulk. For Eclipse, the factory default Eclipse Node license permits installation of up to six RACs, each with a maximum capacity of 10xE1, or 16xDS1. Beyond this level, licenses must be purchased, which provide an up to capacity on a per RAC basis. When you register new licenses, a copy of each license is stored in the folder: \ProVisionServer\repository\licenses . A copy of each license is retained in this folder after the license is applied to the radio. 614-330055-001 DECEMBER 2015 237 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES NOTE: When you upgrade to a higher higher ve rsion of ProVision, the licenses that were applied to the the ra dios are unaffected. unaffected. It is recom mended to save a backup copy of the repository folder with the license files, then migrate the folder to the server once the new vers ion of ProVision has has been installed. Contact one of the regional Aviat Networks sales offices to purchase an upgraded Eclipse or CTR 8540 Node license. Procedure To install Node licenses: 1. When you receive the new Node licenses, place them in a temporary folder on the computerr that ser compute serves ves as the ProVisio ProVision n client. client. NOTE: If you are loading 100+ licenses into into the folder, this will take some time. 2. From the ProVision menu bar, select Configuration > License Loading. The License Loading window opens. If you have not previously browsed for or applied any new Node licenses, the window is blank. 3. Select the Register Licenses button. The Location For License File(s) window opens. From this window, browse to the folder that contains the new licenses. You can either select select one or more individual license license files to register register,, or you can select the folder to register all licenses in the folder. 4. Select the Open button. The licenses licenses selected selected are a re listed in the Eclipse License License Table window. The license files are uploaded to the ProVision server repository and are stored in the folder: <pvroot>\ProVisionServer\repository\licenses <pvroot>\ProVisionServer\repository\licenses.. l Each license file file has a serial serial number that corre corresponds sponds to a particular radio. radio. ProVision automatically matches the license to its radio and displays the re result sult in the E Eclipse clipse Licen License se Table. l l l So Sort rt the table by clicking clicking on selecte selected d table ta ble headings. headings. Only the most recent recent license ffor or a particular objec objectt displays displa ys in the License License Table. A message displays, Found ne new w licenses licenses and uploaded to repositor repository. y. Click OK to proceed to the next step. 238 AVIAT NETWORKS PROVISION USER MANUAL 5. Select one or more objects and select the Load License to Selected Objects button. NOTE: If you are loading a batch batch of radios, only se lect 10 - 20 r adios at a time. It takes approximately approximately 5 minutes minutes for ProVision to to apply licenses to 10 Eclipse radios on a remote network. A Task Manager displays and shows the the status of the batch as the licenses are applied. 6. The lice licenses nses for the sele selected cted objects objects are applied to t hose objects. objects. Note that the Date Applied column is now populated. The table below details the License Table values. To register additional licenses, repeat steps 3 to 4. To load licenses to objects, repeat steps 5 to 6. 7. To export the data from the License Information table as a .CSV file, click Export. You are prompted p rompted to select the name and location of the t he . CSV file. ProVision notifies you when the Export is complete. Table 4-11. License Table Headings 614-330055-001 DECEMBER 2015 239 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES Heading Descriptio n Object The name of the Node. Node. Container The cont container ainer of the Node. Serial Number The seria seriall number of the No Node. de. Files The names of the License License files files.. Date Applied The mo most st recen recentt date fo forr this license license being appl applied ied to the No Node. de. Related Topics: V ia ProVision on page 221 About Loading Device Software Via Device Configuration Backup and Restore ProVision automatically saves a configuratio ProVision configuration n backup backup file every every 12 hours for the following device types deployed in ProVision. ProVision. l Eclipse l CTR 8300, 8300, 8540, and 8440 (see (see note) note) l TRuepoint TRuepoint 5000 l WTM 3200 3200 and 330 3300 0 (export (export only, re restore store iiss av ailable fr from om the craft tool) l Symmetricom l Accedian NOTE: Other devices can be backed up and restored from their craft tools. To do this, ProVision does the following: l l l l Detects Detects whether conf configuratio iguration n has changed changed by reading reading the last change time from the devices. If change is is detected, detected, FTPs FTPs the configur configuration ation file to the backup backup location on the ProVision server. Re Returns turns the last 5 copies of the configur configuration ation file filess onto the server. server. Saves Saves this backup and uses it (for Eclipse, Eclipse, with Portal) Portal) to load onto new installations. This process is run as a background process on a regular basis. You can export the backup if it is required. required. W AR NI NG : Fo r TRuepoint 5000 devices, to enable the Configurati Configuration on Backup for eac h device, you must s et up the the device s ecurity acc ount ount in the craft tool, then in ProVision using Device Secur Security ity Accounts. Once the back up is collected you can restore the devices. 240 AVIAT NETWORKS PROVISION USER MANUAL W AR NI NG : CTR 8440 devices c an have their configuration configuration backup saved, but not not res tored. The c onfiguration onfiguration backup is done via the TFTP serv er which comes bundled bundled with the the ProVision Server installation. installation. The TFTP server runs on port 69. Note that any external TFTP servers should be stopped for the TFTP server on ProVision tto o wor k. Procedure 1. Select a node or device in the Tree Viewer. 2. Right-click the node or device. device. In the right-c right-click lick menu, select select Configuration, then select Export Configuration Backup. 3. The Export Configuration Backup scre screen en display s. 4. This screen lists the available backup files for the node or device. You can do the following with backups from this screen: l Preview - Displays a preview of the backup. l Restore - Restore a selected backup file. l Export - Export and save the backup file. 5. To export the backup, select the most recent backup and click Export. 6. The Select Export Location screen displays. Navigate to the file folder where you want to save the backup, and click Save. 614-330055-001 DECEMBER 2015 CHAPT CH APTER ER 4. DEPLOYING AND MANAGING DEVICES DEVICES 7. The backup file is saved to this location. 8. The backup file can be used to load the devices again, if required. Select the backup file a and nd click Restore. 241 242 AVIAT NETWORKS PROVISION USER MANUAL Chapter 5. Carrier Ethernet Management Using ProVision, ProVision, y ou can manage Ca Carr rrier ier Ethernet Ethernet devices. devices. This includes v iewi iewing, ng, provisioning, and fault manag management. ement. ProVision provides Carrier Ethernet management for the following device types: l l l Eclipse family devices devices with DAC GE3 or IDU GE3 (for (for VLAN VLAN and EOAM, 7.2.32 or later Eclipse firmware: firmware: for ERP provisioning, provisioning, 7.3.32 7. 3.32 or later Eclipse firmware) CTR 8540 devices (require (requiress 2.4 or later CTR 8540 firmware) firmware) VLAN and EOAM E OAM for CTR 8300 devices (requir (requires es 2.3 or later CTR 83 8300 00 firmware) This section covers the following topics: l VLAN Manage Management ment on on page 244 244 l Ethernet Ether net OAM Manage Management ment on page 263 263 l ERP Ring Ring Management Management on page 282 282 NOTE: Carrier Ethernet function functionss require feature licenses - s ee About Licenses . 614-330055-001 DECEMBER 2015 CHAPT CH APTER ER 5. CARRIER ETHERNET MANAGEMENT VLAN Management This section describes how to use ProVision to perform VLAN management: l Viewing discovered VLANs Viewing VLAN VLAN configuration details l l Identifying Identifying and resolving resolving VLAN VLAN faults faults l Configuring VLANs l Creating Creating a VLAN VLAN l Modifying Modifying a VL VLAN AN l Validating VLAN conf configuratio iguration n l Deleting Deleting a VLAN ProVision Pro Vision provides VLAN management management fo forr t he following device typ es: l Eclipse family devices devices with DAC GE3 or IDU GE3 (requir (requires es 7.2.32 o orr later Eclipse firmware) l CTR 8540 devices (require (requiress 2.4 or later CTR 8540 firmware) firmware) l CTR 8300 devices (requir (requires es 2.3 or later CTR 8300 8300 firmware) This VLAN documentation documentation include includess the following sections: l l Overview Over view of VLAN VLANss on page 244 Viewing Discover Discovered ed VLANs on page 245 245 Viewing Viewin g List of Discovere Discovered d VLANS on page 246 l l Viewing Viewin g VLAN Configuratio Configuration n Details on page 247 l Viewing Viewin g VLAN Topolo Topology gy on page 250 l l l Viewing VLANs Viewing VLANs in the Physical Physical and Flat Maps on page 252 Identifying and Reso Resolving lving VLAN Faults on page 254 Configuring Config uring VL VLANs ANs on on page 257 257 Provisionin Pro visioning g a New VLAN on on page 257 l l Modifying Mo difying an Existing VLA VLAN on page 261 l Deleting Dele ting an Existing VLAN on page 262 262 243 Overview of VLANs VLANs (Virtual LANs) are u used sed to segregate segregate users and/or services services on a LAN (Local Area Network) from other users/services on the same LAN. VLANs behave as if they were on a separate LAN, even though they all share the same physical network and network address. What are tthe he network benef benefits its of VLANs? 244 AVIAT NETWORKS PROVISION USER MANUAL l VLANs segment networks to pro provide vide improved security, workgroup management and traffic control. l VLANs VLANs also enable traffic prioritization to support Quality of Service (QoS) needs. Where Ethernet Ethernet bandwidth is restricte restricted, d, traff traffic ic tagged ta gged as high prior priority ity will transit a switched network ahead ah ead of lower l ower priority or un untagged tagged traffic. This is particularly relevant where VLANs are transported over a service-provider network. l VLANs VLANs can also be stacke stacked d to provide a demarcation between customer and service provider networks. Multiple customer VLANs can be stacked on a service ser vice-pro -provider vider VLAN, with the service provider provider able to provide each with a unique priority to support service level agreements (SLAs). The VLAN traffic data is identified and separated by Ethernet frame tagging. Ethernet frames ingressing a VLAN port have a VLAN tag inserted that includes the VLAN ID and a priority/class setting. Switches within the network use the VLAN ID tag to maintain VLAN membership/segregation over common trunk links. VLANs are software-configured; they are not constrained by the physical topology of a network. For Eclipse, VLAN is enabled theunder DAC aGE3 card.n In Eclipse Portal, VLANs arer established estab lished by gro grouping uping switchwith ports common commo VLAN membership membe rship identifier identifie (VLAN ID). Each VLAN uses a different VLAN ID. VLAN configuration sets VLAN tagging and filtering, and selects and customizes cross-connections between user and network ports. p orts. VLANs provide a means to manage all traffic within w ithin a DAC GE3 switch, from switch port ingress to egress, and to establish VLANs for use beyond the switch. NOTE: ProVision does not provide VLAN provisioning provisioning of NCM ports. W AR NI NG : To enable VLAN viewing and management, management, ProVision must be configured as the SNMP manager trap des tin tination ation for the VLAN Eclipse devices . With With this this c onfiguration onfiguration,, ProVision receives faults and configuration configu ration change events from the VLANs with minimal delay. For more about VLANs, chapter VLAN tagging, and VLAN typesDescription. in Aviat Networks products, see the Ethernet Operation of the Eclipse Produc Productt Descri ption. Viewing Discovered VLANs Using ProVision, it is fast and easy to view your network VLANs. ProVision automatically discovers and displays all VLANs in the network in the VLAN Tab, including the end-to-end topology for each VLAN. The VLAN Table provides a list of the discovered VLANs. From the VLAN Tab, you can also view an end-to-end topology map or the configuration configuration details of a sele selected cted VLAN. ProVision continually checks for new VLANS and VLAN configuration changes. VLAN information is persisted in the database to retain VLAN view access during loss of communication with managed devices. To support VLAN end-to-end discovery, ProVision must identify the underlying Layer 1 network netwo rk topolo topology. gy. This is enable enabled d by Pro ProVision’ Vision’ss aut omated discovery, discovery, coupled with the 614-330055-001 DECEMBER 2015 245 CHAPT CH APTER ER 5. CARRIER ETHERNET MANAGEMENT ability to manually deploy links (RF or Ethernet) where the network devices cannot provide the management information. To view VLANs, see these procedures: l Viewing List of Discovere Viewing Discovered d VLANS on page 246 Viewing Viewi ng VLAN Configuratio Configuration n Details on page 247 l Viewing Viewi ng VLAN Topolo Topology gy on page 250 l Viewing Viewi ng VLANs VLANs in the Physical and Flat Maps on page 252 252 l Viewing List of Discovered VLANS This section describe describess how to v iew the list of discovered discovered VLANs, including filtering filtering for specific speci fic list items. Procedure 1. To view view all VLANs, VLANs, sele select ct the network object object in the Tree Tree Viewer Viewer.. To view the VLANs associated with a specific object (e.g. a region or a device), select the specific object in the Tree Viewer. 2. Ope Open the the VLAN Tab. The automatically discovered VLANs display in the VLAN table. NOTE: Transparent member devices of a VLAN are included included in the the VLAN as par t of the path between the the main VLAN devices. 3. By default, the VLAN tab table le is filter filtered ed to list only the membe memberr ports ports (for each VLAN) on the devices within the selected container conta iner object in i n the Tre Treee V View. iew. To extend the VLAN table to include all member ports for each VLAN, select the Show All Member Ports checkbox. 4. To fi filte lterr the list o off VLAN VLANs, s, you can: can: l l Sort Sort the VLAN table by by clicking on table header headers. s. Click on the Filter button to filter filter for specifi specificc text or number numbers. s. You can filter for for VID and severity values: valu es: for example, entering entering "vid=200" will search for results with a VID value of 200. l 5. Se Selec lectt an a n object object in th thee Tr Tree ee Viewer Viewer to view its VLAN items in t he VLAN tab. To export export the list of of VLAN VLANs, s, click click the Export button at the bottom of the VLAN table. You will be prompted prompt ed to save the VLAN Table data d ata as a .txt .tx t file. VLAN Tab – VLAN Table View In the VLAN table view, a single row of data displays for each VLAN. 246 AVIAT NETWORKS PROVISION USER MANUAL NOTE: Discovered VLANs with the same VID are assumed to be separated segments of the same VLAN due to either either a configuration configuration error or a fault condition. condition. Therefore, they are pres ented as a single entry in the VLAN table. table. Because a customer may intentionally intentionally reuse VIDs in p physhysically s eparated parts of the network, in a future relea se the option will be provided to select w hether hether a VLAN in this this state is a ctually separate VLANs. Table 5-1. VLAN Tab – VLAN Mode Table Definitions Definitions Tabl ble e Item Def efiinition tion Alarm Status Displ Displays ays th thee highest ac active tive ala alarm rm severity for al alll al alarms arms tha thatt are auto auto-matically correlated to this VLAN. To see alarm levels, see Alarm Severity Color Coding on page 91. VID VID identifier for the VLAN. VLAN. Name Name of the VLAN. VLAN. Members List of devices incl included uded in the VLAN VLAN.. Show All member Ports Option to extend the VLAN Table to include all member ports for each VLAN (i.e., the Members field is no longer longer filtered by the Tree View con con-tainer selection). This also results in the VLAN Map displaying all devices in the network with VLAN port membership. EOAM This icon indicat indicates es that EOAM monito monitoring ring is enabled for this VLAN (i.e., an EOAM MA is configured.) ERP ring. = This VLAN contains member ports that form a physical layer = This is an ERP control VLAN, with an ERP ring applied. Viewing VLAN Config Configuration uration Det Details ails You can view the configuration details for a specific VLAN using the view Details option. Procedure 1. Sele lect ct the VLAN Tab. Select the VLAN in the VLAN table. 2. Clic Click k the the Details button. The Details display below the table, with a tab of details for VLAN, and for implemented EOAM and ERP applied to the VLAN. Note: EOAM and ERP tabs only display if these are implemented. If 614-330055-001 DECEMBER 2015 CHAPT CH APTER ER 5. CARRIER ETHERNET MANAGEMENT EOAM or ERP are not present on the VLAN, EOAM or ERP tabs will not display. 3. Click on eeach ach tab to view the Details. Se Seee the values values descr describe ibed d belo below. w. 4. In the VLA VLAN tab tab,, to view viewclick Switche Switches, click click the Switches Edge Ports viewing theNEdge Ports, the s, button. button. To return to VLAN Information This tab presents the details of the selected VLAN. Edge Ports v iew: Switches view: 247 Deta De taiils Ite tem m De Defi fin niti tion on Port Types There are two tables tables here: - Edge Ports - Devices on the "edge" of a network that do not connect to other radios - Network Ports - ports that link radios. Device Device name. Read onl only. y. Enabled Port state is enabled (checked) (checked) or disabled (blank (blank). ). 248 AVIAT NETWORKS PROVISION USER MANUAL Port Specified port port.. Rea Read d onl only. y. Device For Network Ports onl only: y: the device that supports this VLAN. Second Enabled and Port values are related to this device. VLAN Members- All VLANs that include this specified port. hip Advanced Advanc ed Bridge Port Mode For For Edge ports. For CTR devices only only.. Only Customer Bridge is supported, but at this time Provider Bridge modes will display if they have been co configured nfigured via CLI. Filtering For For Edge port ports. s. Enabl Enablee or disabl disablee Filt Filtering ering for inco incoming ming frames. Trunk For Tagged ports. Enable or disable Trunking. Where available, Trunk ports are tagged by default. NOTE: Either Filtering or Trunking can be enabled: they cannot both be enabled. Forbidden VIDs For all T Tagged agged ports. Trunk Trunkss are automaticall automatically y included i n any VLAN. You can bloc block k or "forbid" them from being included in a specific VLAN by entering the VID number numberss here. Priority For untagged Edge Port Ports. s. EOAM Information This tab presents the details for the EOAM MA associated with the selected VLAN. It lists all EOAM MA/MEGs configured for the selected VLAN. Deta Detail ils s Item De Defi fini niti tion on MA ID/ME ID Unique MA ID/M ID/ME E ID defined o on n the VL VLAN. AN. Y1731 Type of service, noted as True (Y.1731) (Y.1731) or Fals Falsee (80 (802.1ag) 2.1ag) Level MD/MEG level, representing hierarchical levels of management. VID VLAN ID for the service service being monito monitored. red. MEPs/Devices MEPs MEPs and devices with MIPs fo forr this EOAM MA. Note that EOAM EOAMss can have more than 2 MEPs. Diagnostics - Links to the EOAM Diagnostics view for this EOAM MA/ME 614-330055-001 DECEMBER 2015 249 CHAPT CH APTER ER 5. CARRIER ETHERNET MANAGEMENT ERP Information This tab presents the details for the ERP rings associated with the selected VLAN. It presents details for both the main ERP ring and for any ERP subrings. Deta etails Item tem Defi efiniti tion on Name Name of the ERP ring. Members Devices and port portss on the devices used for the ERP ERP.. Fo Forr exampl example, e, INUe153 is the device name, and 7/2 indicates the slot and port (respectively). RPL Owner Ring Protection Link Owner – device/port with this icon. Subring ERPS Subring - device/port with this icon. RPL Owner on a Subring RPL RPL Owner on the Subring (inva (invalid!) lid!) - The RP RPL L own owner er is not allowed on the subring component of an ERP ring. Viewing VLAN Topology With ProVision, you can view the end-to-end topology of a VLAN (Layer 2) correlated with the physical phy sical (Layer 1) network top topology. ology. This is disp displayed layed as a filtered filtered view of t he Flat Map, using the Flat Map coordinates for positioning each object. 250 AVIAT NETWORKS PROVISION USER MANUAL Procedure 1. Ope Open the the VLAN Tab. Select the VLAN in the VLAN table. 2. Clic Click k the the Map button. The topology displays in the map. See the map values described below. Table 5-2. VLAN Map Att Attribu ributes tes Map Item tem Defi efiniti tion on Show All Member Ports Option(i.e. to extend the VLAN Table tolong include all member each VLAN the Members field is no longer er filtered by theports Tree for View container selection). This also results in the VLAN Map displaying all devices in the network with VLAN port membership. Alarm Status Displays the alarm levels ac active tive for devi ces. To see alarm levels, see Alarm Severity Color Coding on page 91 . Port Status tool tip Po Port rt status status is displa displayed yed in the the boxes on the link lines. Hover over these for a tool tip that displays: - Plug-Ins – Device and plug-in Ids for this port. - Type – Network Network Port or User Por Port. t. - Status – Enabled or Disabled status for linked ports. - Alarm Status for the ports. Edge Ports Port names highlighted in purple are Edge Ports. Network Ports 614-330055-001 Port names highlighted in orange on links are Network Ports. Ports. DECEMBER 2015 251 CHAPT CH APTER ER 5. CARRIER ETHERNET MANAGEMENT Link or Connector Status - Black solid line – RF link. Mouse over for RF link details. - Square on line– Ethernet link. Mouse over for DAC port link data for this link branch. - Looped dash line - Cable connect between two Ethernet plugins (DAC Filter GE3s). Displays Displays a field for Filtering Filtering the VLAN tabl tablee based on an alph alphanumeric anumeric value: onl only y items that include this value will display. Export Click Click this to expo export rt and save the data as a .txt .txt file. Create Clic Click k this to crea create te a new VLAN VLAN.. Viewing VLANs in the Physical and Flat Maps You can view the configuration details for a specific VLAN in the main Physical Map or Flat Map view, using the Map Mode – VLAN Mode. This is useful for viewing a selected VLAN in the context of the t he larger network. Procedure 1. Se Sele lect ct the Physica Physicall or Flat M Map. ap. In the map functio functions, ns, selec selectt Map Mode and choose VLAN Mode. 2. The map display change changess to include include VLAN VLAN items items in the uppe upperr and lower lower right corners. To view the port information on the map, click the arrow beside VLAN Mode in the map; a drop-down menu displays disp lays.. You can select port configuration configurationss to v iew, including: l Active Ports = Admin enabled ports l Edge Ports = VLAN terminating ports 252 AVIAT NETWORKS PROVISION USER MANUAL l Network Ports = Network ports delivering the VLAN 3. To view view a specif specific ic map, sele select ct the VLAN Mode Ports item. Then, select the VLAN to be displa d isplayed yed from the t he list of discovere d iscovered d VLANs. 4. For the se sele lecte cted d VLAN, VLAN, the por portt VLAN map attrib attribute utess display in the Physical/Flat map view. Table 5-3. VLAN Map Map Att Attribu ributes tes for Physical/Flat Physical/Flat Map Map Item Definitio n Alarm Status Displays Displays the ala alarm rm page llevels evels91 active act forr this this device. See Alarm Severity Color Coding on . ive fo 614-330055-001 DECEMBER 2015 253 CHAPT CH APTER ER 5. CARRIER ETHERNET MANAGEMENT Port Status Po Port rt status status is dis display played ed in the boxes on the llink ink lines lines.. Ho Hover ver o over ver these for a tool tip that displays: - Plug-Ins – Device and plug-in Ids for this port. - Type – Network Port or Edge Port. - Status – Enabled or Disabled status for linked ports. - Alarm Status for the ports. Edge Ports Po Port rt names highl highlighted ighted in purple are Edge Ports. Ports. Network Ports Port names highlighted in orange on links are Network Ports Ports.. Link Status - Blac Black k sol solid id lline ine – RF link. Mouse over for RF link details. - Square on line – Ethernet link. Mouse over for DAC port link data for this link branch. Identifying and Resolving VLAN Faults This section describe describess how to use Pro ProVision Vision to identify, identify, verify, verify, isolate and resolve resolve VLAN faults. ProVision Pro Vision detects faults in VLANS by automatically perfor performing: ming: l VLAN configuration validation valid ation checks checks l Ethernet OAM configuration validation valid ation checks checks l Ethernet OAM continuity testing l Correlatio Correlation n of reporte reported d events to the VLANs (e.g. (e.g. a port down alarm is associated with all VLANs on that specific port). W AR NI NG : To r esolve VLAN configuration configuration faults, you may need to be able to make changes to devices using the device craft tools, such as Eclipse Portal. Procedure 1. Ope Open the the VLAN Tab. The VLAN Tab displays VLAN connections with faults. To view these quickly, either: l So Sort rt the VLAN table table by alarm status in descending orde order. r. l View the VLAN VLAN map: device alarm status is shown on each device device.. 254 AVIAT NETWORKS PROVISION USER MANUAL 2. Re Review view the faults faults for a spec specific ific VLAN VLAN by by right-clic right-clicking king it in the VL VLAN AN Table Table and selecting Event Browser. The Event Browser displays all the faults for the VLAN. 3. You You can also view view the faults faults fo forr an EOAM MA b by y viewi viewing ng it in the EOA EOAM M tab. Hovering over the errored EOAM MA opens a pop-up with the fault details. 614-330055-001 DECEMBER 2015 255 CHAPT CH APTER ER 5. CARRIER ETHERNET MANAGEMENT 4. l To isolat isolatee this fault fault and identif identify y its cause, cause, use the VLAN VLAN manage manageme ment nt features in ProVision: Check that there are are no physical connection connection (RF or Etherne Ethernet) t) faults by inspecting the connections between the nodes using either the VLAN Map or EOAM Map (where EOAM monitoring has been enabled). l l l 4. Where Where EAOM monitoring monitoring has been been enabled enabled on the VLAN, use the EOAM diagnostics identified in section Identifying and Resolving EOAM Configuration Faults on page 270 to help with diagnosing EOAM MA continuity faults. Inspect Inspect the configuration configuration of the VLAN using the VLAN Table, Table, VLAN Details and VLAN Map identified in this section. See Viewing Discovered VLANs on page 245. 245. Check whether there there are packet loss or er error ror proble problems ms on the associated ass ociated ports or queues that deliver the VLAN using the Ethernet performance feature. See Ethernet Bandwidth Utilization on page 399. 399 . The VLAN VLAN Fault Fault Table Table belo below w lists the most common common VLAN VLAN faults faults and provides resolution actions. For other alarms, see the Alarms Appendix. Table Tabl e 5-4. Co Common mmon VLAN Faults Alarm Names Cause Channel X MEP defect or Port X MEP defect An OAM link or configur configuratio ation n error has occurred due to one or more of the following defects: - RDI - Remote interface down - No CCM - Invalid CCM - Xcon CCM - Unexpected period - Y1731 mode only - Unexpected MEP - Y1731 mode only - Mismerge - Y1731 mode only Resolution Action - Resolve the link error, or correct the configuration. con figuration. Use ProVision ProVision EOA EOAM M diagnostics and validation to resolve this. - Note that the link error, or configuration error could be in the local node, the remote node that has the peer MEP defined, or any node in between. - Unexpected MEG level - Y1731 mode only - Local link failure - Y1731 mode only - Internal HW failure - Y1731 mode only - Internal SW failure - Y1731 mode only - AIS condition - Y1731 mode only - LCK condition -Y1731 mode only Ethernet Down Th Thee Et Ether hernet net port port or TC link link is down. down. - Che Check ck VLAN VLAN conn connec ectio tion n port port cabl ables es.. - Check for related alarms on the connected equipment. - Check the circuit configuration (Circuits screen). - Withdraw the DAC GE3 card, pause, then reinsert. If the alarm persists, replace the card. Plug-in initializing The pl plug ug--in is still ill init initia iallizin izing g. 256 - Chec Check k pl plug ug--in pres presen encce and connections.. Review the device for nections alarms. AVIAT NETWORKS PROVISION USER MANUAL Alarm Names Cause Port X DPP link down The end-end Ethernet link is down due to a problem with the DPP cable. - Check local and remote DPP cable connections. Port Xframe excessive out of drop One or more of thecongestion VLAN links resulting in traffic onare thedown, remaining link(s). -link If the port/channel is included in aif aggregation group, check to see it is as a consequence of the failure of a partner link. - Check port/channel traffic loading using the Performance screen. - Determine if the dropping is an isolated instance or becoming more frequent. If the later, review the connection design parameters. Port X SFP missing The SFP is missing fro from m an enabled SFP port (P4, P5). The SFP module has not been install insta lled ed or has been withdrawn withdrawn.. Unable to read port information ProVision cannot read the port information over SNMP. Resolution Action - Insert the relevant SFP module. - Check the NMS connectivity to the device, including the MTU MTU (max (maximum imum transmission unit) size. - Exclude virus scanner from ProVisionServer\mysql\data\tmp directory Configuring VLANs This section describes how to configure VLANs. It also describes how to validate that configuration changes have been applied correctly to VLANs. See these procedures: l Provisioning Pro visioning a New New VLAN on page 257 257 l Modifying Mo difying an Existing VLAN VLAN on on page 261 261 l Deleting Dele ting an Existing VLAN on page 262 262 Note the following: l When provisioning a new VLAN, VLAN, consider whether Ethernet OAM monitoring of the VLAN service service is req required. uired. This provides a higher level of service service assurance,, re assurance resulting sulting in a higher qualit quality y VLAN service. service. See Ethernet OAM Management on page 263 263.. Provisioning a New VLAN In ProVision, users can create and launch new VLAN provisioning from within the ProVision software. This is available for for Eclipse, CTR 8540, and CTR 8300. Procedure 1. 614-330055-001 To open open the VLAN Pro Provisionin visioning g screen, screen, you have four options: DECEMBER 2015 CHAPT CH APTER ER 5. CARRIER ETHERNET MANAGEMENT l In the VLAN tab, clic click k the Create button. l In the main me menu, nu, open open Configuration - Provisioning - VLAN. l Se Selec lectt devices devices in the Map view, right-click right-click them, and choose Configuration Add to VLAN. l 2. In the Tree Tree View View or Map Map v iew, sele select ct the items or ports and right-click, right-click, and select Configuration - VLAN Provisioning. Select one or more ports from the display. Then, click Provision. The VLAN Provisioning scre screen en display s. 257 258 AVIAT NETWORKS PROVISION USER MANUAL 3. You can re review view or enable enable specif specific ic VLAN configur configuration ation values. These ar are: e: For the overall VLAN: l VLAN type- Either VID, with VID value, Name, and Transparent, or Trunk. For Edge Ports and Network Ports: l Device - Device name. Read only. l Enabled - Port state is enabled (checked) or disabled (blank). l Port - Specified port. Read only. l VLAN Membershi Membership p - All VLANs that include this specified port. NOTE: Edge Ports are devices on th the e "edge" of a network that do not connect to other radios. Network Ports are ports linking radios. 5. Cl Cliick Advanced to set up the following VLAN configuration values for Edge Ports and Network Ports. First, select whether the ports are Tagged or Untagged, using the check box to enable Tagged status. Then, set the values: Priority - For untagged Edge ports. The priority value (0 - 7) assigned to untagged frames. l Bridge Port Mode - For Edge ports. For CTR devices only. Only Customer Bridge is supported, but at this time Provider Bridge modes will display if they have been configured via CLI. l Filtering - For Edge ports. p orts. Enable or disable Filtering Filtering for incoming frames. frames. Display only, not supported for this release. l Trunk - For Tagge Tagged d ports. Enable or disable Trunking. Trunking. Where available available,, Tr Trunk unk ports are tagged by default. NOTE: a) Filtering or Trunking can be enabled: they cannot both be enabled. b) You cannot unset a trunk from here. If you no longer want a port to be a Trunk, select the trunk VLAN and remove the port from that VLAN. 614-330055-001 DECEMBER 2015 259 CHAPT CH APTER ER 5. CARRIER ETHERNET MANAGEMENT l Forbidden VIDs - Trunks are automatically included in all VLANs. One example of the use of forbidden VIDs is blocking or "forbidding" them from being included inclu ded in a specific VLAN V LAN by entering entering the VID numbers h here ere.. Note tthat hat for forbidden bidden VIDs are a re also applicable a pplicable to non-trunk non-trunk ports. 6. To re revie view w available available switc switches hes,, clic click k the Switches button. VLAN modification, whether adding a dding a new VLAN or m modifying odifying a VLAN or deletion d eletion of a VLAN, applies to only the switches listed here. Users can add additional switches or remove the displayed ones. A switch is automatically added when any port for that switch is added. NOTE: All ports und under er a s witch are visible to each otehr. otehr. Eclipse is not considered a switch because ports on one DAC GE3 are not visible to another DAC GE3. For Eclipse devices, Switches are DAC GE3 modules. 6. The Switch Switches es view view displays, with a read-0n read-0nly ly display of the Switche Switchess linked linked to this VLAN provisioning. 7. You You can also add additional additional ports ports by by dragging dragging and dropping dropping them them from from the Tree viewer. Note that a message displays if a selected port cannot be dropped: see the highlight in this screen sample, where Port 1 is being dragged and dropped and a message is displaying. 260 AVIAT NETWORKS PROVISION USER MANUAL W AR NI NG : If a setting is incorrect or causes a VLAN problem, this error iicon con displays displays next next to th the e settin setting: g: VLAN after resolving all errors. You can only commit a 8. When you have enter entered ed all your re requir quired ed se settings, ttings, click Commit Changes. A progress window displays and confirms when the provisioning is complete. For CTR devices, see Saving Carrier Ethernet Configuration for CTR Devices on page 1. 1. 9. Use Pro ProVision Vision to validate the new VLA VLAN N has be been en corr correc ectly tly provisione provisioned: d: l l l Check that the new new VLAN displays in the VLAN table. table. Click the Details Details button to verify verify the VLAN details details.. See section Viewing VLAN Configuration Details on page 247 . Click the Map Map button to verify verify the VLAN VLAN topology. topology. See See se section ction Viewing VLAN Topology on page 250. 250. Check that the alarm alarm status field in the VLA VLAN N table indicates indicates that no alarms are active. active . Where Wher alarms are a re active follow folloto w tresolve he procedure proce dure in Viewing VLANs in the Physical and eFlat Maps onactive, page, 252 the fault(s). 10. Use ProVision ProVision to configure Ethernet OAM monitor monitoring ing of the new VLAN service ser vice by applying EOAM Provisioni Provisioning, ng, see Provisioning a New EOAM MA on page page 275 Modifying an Existing VLAN The procedure for modifying an existing VLAN is the same as the provisioning pro257.. cedure in the section Provisioning a New VLAN on page 257 614-330055-001 DECEMBER 2015 261 CHAPT CH APTER ER 5. CARRIER ETHERNET MANAGEMENT Select the VLAN, right-click it, and select Edit. NOTE: ProVision will not allow you to make changes to a Management Management VLAN. Deleting an Existing VLAN ProVision can be used to ensure that a VLAN is correctly deleted from the configuration of all device devices. s. NOTE: You cannot d delete elete a Management VLAN VLAN or a VLAN with EOAM or ERP enabled. Delete the EOAM and ERP before you delete the VLAN. Procedure 1. In ProVisio ProVision, n, select select the network network or containe containerr objec objectt that contain containss the VLANs. Then, open the VLAN tab. In the VLAN table, right-click on the VLAN and select Delete. 2. Check Check that the VLAN VLAN is no longe longerr displayed displayed in the VLAN VLAN tabl table. e. NOTE: See the CTR Portal ProVision manual and the CTR 8540 CLI Refer- ence Manual for CTR 8540 instructions. instructions. 262 AVIAT NETWORKS PROVISION USER MANUAL Ethernet OAM Management ProVision provides Ethernet OAM (EOAM) management. This section describes how to use ProVision’s EOAM functions for: l Viewing discovered discovered EOAM Maintenance Maintenance Associations (MAs) (MAs) l Viewing MA configuration details l Configuring Configuring EOAM to provide provide fault monitoring monitoring of VLANs VLANs (Eclipse only) l Validating EOAM configuratio configuration n Pr ProVisio oVision n provides provides EOAM management for the following following device types: l l l Eclipse family devices devices with DAC GE3 or IDU GE3 (requir (requires es 7.2.32 o orr later Eclipse firmware) CTR 8540 devices (require (requiress 2.4 or later CTR 8540 firmware) firmware) CTR 8300 devices devices (requires (requires 2.3 or later CTR 83 8300 00 firmware) Limitations: l l EOAM Up/In Up/In MEP conf configuratio iguration n is not supported by CTR 2.3 2.3 and 2.4 software. EOAM Y.1731 Y.1731 MA in Eclipse 8.0 is not compatible compatible with CTR. An Eclipse fix fix is planned for a later 8.0 software software rele release. ase. The following sections are provided: l l Overview Over view of Etherne Ethernett OAM on page 264 Viewing Viewi ng Discovere Discovered d EOAM MAs on page 265 265 Viewing Viewin g List Of Discovere Discovered d EOAM MAs on page 266 266 l l l l Viewing Viewin g EOAM MA Logical Logical Topology Topology on page 267 l Viewing Viewin g EOAM MA MA Physical Topology Topology on page 269 269 Identifying Iden tifying and Resolving Resolving EOAM Configuratio Configuration n Faults on page pa ge 270 270 Configuring Ethernet OAM on page 275 Provisioning a New EOAM MA on page 275 Provisioning l l Modifying Mo difying an EOAM MA on page 280 l Deleting Dele ting an EOAM MA on page 280 See also the section Identifying and Resolving VLAN Faults on page 254 for troubleshooting VLANs with EOAM. NO T E: Impor Important: tant: To enable enable EOAM management, management, ProVision must be c onfigured onfigured as the SNMP manager tr ap destination. With this configuration, figu ration, ProVision r eceives faults and c onfiguration onfiguration change events from the EOAM entities entities w ith minimal minimal delay. 614-330055-001 DECEMBER 2015 263 CHAPT CH APTER ER 5. CARRIER ETHERNET MANAGEMENT Overview of Ethernet OAM Ethernet OAM (Operation, Administration, and Maintenance) is a set of Ethernet support functions enabling: l Detection and resolution of VLAN service service faults l Measurement Measurement of VLAN service service perfor performance mance NOTE: Thi Thiss function function is enabled enabled from Eclipse ver sion 7.2.32 onwar ds, and CTR 8540 version 2.4. Unlike TDM circuits, Unlike circuits, Ethernet Ethernet services services are virtual in nature and can be dynamic. Ethernet er net OAM is needed needed to ensure Ethern Ethernet et service quality and availability are predictable predictable and in line with what was provisioned / subscribed. When data is being transmitted with Ethernet packet-switched network OAM protocols active, designated OAM PDUs (frames) are sent alongside user traffic. Sever Several al standards have been been developed developed that support Et hernet hernet OAM at differe different nt layers. Service OAM addresses end-to-end Ethernet connectivity fault management (CFM) and in future performanc performancee monitoring monitoring (PM), (PM), as def defined ined within IEEE 802.1ag, 802.1ag, and ITU-T ITU-T Y.1731. Note that: th at: l l l 802.1ag and Y.1731 specifications overlap/conver overlap/converge ge on CFM. PM is only defined defined in Y.1731. (Note: (Note: PM is not supported in the curr current ent ProVision product) Connectivity Connectivity & Fault M Manageme anagement nt (CFM): Provides proactive continuity continuity monitoring to identify problems. l l l Provides Provides rapid fault verific verification ation and isolation. l Refers Refers problems problems to the responsible responsible maintenance eentity ntity.. Perfor Performance mance Monitoring Monitoring (PM): (PM): Supports service level agreements agreements (S (SLA) LA) through meaningful reporting of: l l Frame loss l Frame delay l Frame delay var variation iation l Provides proactive perfo performance rmance monitor monitoring ing for maximum maxim um service reliability For Eclipse, CFM is enabled with the DAC GE3 card. Local and remote maintenance end points (MEP) must be configured, and, optionally, the maintenance intermediate points (MIP). In ProVision, the EOAM Provisioning feature configures CFM maintenance associations. See Provisioning a New EOAM MA on page 275 275.. NOTE: EOAM perfor mance monitoring monitoring is not available in this this release of ProVision. 264 AVIAT NETWORKS PROVISION USER MANUAL Ethernet OAM Acronyms Base acronym definitions for EOAM are: l EOAM = Ether Ethernet net Operations, Operations, Administratio Administration n and Maintenance Maintenance.. l MA (MEG) = One or more MEs on the same service level, belonging to the same service VLAN. Sometimes simplified to MA, as in this section. l MEP = Maintenance Entity End Point, the end points of a ME. The connection points (ports) that initiate EOAM messages. l MIP = Mainte Maintenance nance Entity Interme Intermediate diate Point, a connection connection point (port) (port) between two MEPs in a ME that relays and responds to some EOAM between messages. MIPs are not explicitly configured as part of a MA. Pr ProVisio oVision n presents presents both IEEE 802 802.1ag .1ag and ITU-T ITU-T Y.1731 EOAM termino terminology. logy. The following table presents the equivalent terms: IEE E 802.1 ag ITU-T Y.1 731 No equi valent Mai ntenance Enti ty (ME) Main inttena enance Ass Associat iation ion (MA) Maint inten ena ance nce En Enttity ity Gro Group (MEG) EG) MA I denti fi er (MAID) MEG I denti fi er (MEG ID) Mai ntenance Dom ai n (MD) No equi valent MD Level MEG Level MA End Poi nt (MEP) MEG End Poi nt (MEP) MA Int Interme ermedi dia ate Point int (MIP IP)) MEG Int Interme ermedi dia ate Point int (MIP) IP) Viewing Discovered EOAM MAs ProVision makes it simple to visualize your network services and the route / path they are currently taking across the network. ProVision automatically discovers and displays all EOAM monitored VLAN services in the network in the EOAM Tab, including automatically and proactively tracing the end-to-end route of dynamic services. The EOAM Table provides a list of the discovered Maintenance Associations (MA), either 802.1ag MA or Y.1731 MEG / ME. From the EOAM Tab you can also view logical representation of the ports in the end-to-end topology of each MA, or view the same MA overlaid on your physical phy sical network flat-map. flat -map. For each MA you can choose to launch diagnostics diagnost ics to perform manual link-trace or loop-back tests. ProVision continually checks for new EOAM MAs and topology changes that affect the routing of existing MAs, and automatically performs end-to-end link trace tests (in both directions) to validate connectivity and (in the case of a fault) to isolate faults to a port. EOAM information is persisted in the database to retain EOAM view access during loss of communication communication with managed devic d evices. es. To support VLAN end-to-end discovery, ProVision must identify the underlying Layer 1 network netwo rk topolo topology. gy. This is enable enabled d by Pro ProVision’ Vision’ss aut omated discovery, discovery, coupled with the ability to manually deploy links (RF or Ethernet) where the network devices cannot provide the management information. See these topics: 614-330055-001 DECEMBER 2015 265 CHAPT CH APTER ER 5. CARRIER ETHERNET MANAGEMENT l Viewing Viewi ng List Of Discover Discovered ed EOAM MAs MAs on page 266 l Viewing Viewi ng EOAM MA Logic Logical al Topology on page 267 267 l Viewing Viewi ng EOAM MA MA Physical Topology Topology on page 269 269 Viewing List Of Discovered EOAM MAs It is easy to view and filter EOAM MAs in ProVision. The EOAM tab displays the MA Table, which is the list of MAs/MEGs that originate/terminate on the devices/objects selected sele cted through the tree view or match the selecte selected d filter filter on the EOAM table table.. For a multipoint VLAN service, an associated multipoint MA/MEG is displayed as a set of entries, one entry for each point-to-point point-to-point MA/ME. The set will have common MA/MEG MA/MEG ID name, MD / MEG Level and VID values. Problem Problem services services can be iden id entified tified quickly through sorting the Alarm status column. Procedure 1. In the main Pr ProVisio oVision n interf interface, ace, click on the EOAM Tab. 2. The EOAM Tab di displays, splays, with the EOA EOAM M Ser Service vicess table. table. 3. To fi filte lterr the list o off EOAMs EOAMs,, you can can:: l l Sort Sort the table by by clicking on table headers. Click on the Filter button to filter for specific text or numbers. l Enter a text filter filter into the Selected Object field. Table 5-5. EOAM Services Table Function or Acronym Definition MA/MEG Attributes Alarm Status Displays the highest active alarm severity for all alarms that are automatically correlated to this VLAN. To see alarm levels, see Alarm Severity Color Coding on page 91. Validation Status Configuration validation status: - Present, passed validation - Linktrace continuity failure - Faulty 266 AVIAT NETWORKS PROVISION USER MANUAL Type ype Indi Indiccates wh whet eth her the EOA EOAM servi ervicce is an 802. 2.11ag MA or Y.1731 MEG. EG. MA ID ID/M /ME E ID MA ID or ME ID. ID. Le Leve vell MD MD/M /MEG EG level evel,, repr repres esen enti ting ng hier hierar arcchic hical lev evel elss of mana manage gemen ment. t. VID Sta Start MEP VLAN ID for the service being monitored. Sta Start MEP for the MA/M /ME EG. End MEP End MEP for the MA/ M ME E G. S iz ize Total num b beer of MEPs plus MIPs i n the MA/ M ME EG . Filter Filt Filter er the EOAM devices based on a spec specific ific value. value. Export Expo Export rt the displayed displayed EOAM data as a .txt .txt file. You You can use Filt Filter er to select specific data before you do this. Map Opens the Map View. Details Displays or clo closes ses the topolo topology gy inspection view. Viewing EOAM MA Logical Topology With ProVision, you can view the end-to-end logical topology of a MA/M MA/MEG, EG, including ports on managed equipment and ports on unmanaged or third-party equipment. Procedure 1. In the main Pr ProVisio oVision n interf interface, ace, click on the EOAM Tab. 2. The EOAM Tab displays, wi with th the EOAM EOAM Table. Table. 3. Se Selec lectt an EOAM row row in the table. To To view view its logical to topology, pology, click Details. 4. l The Details view displays. See the table below for Details view values. On mousing over over a Details item, item, a pop-up p op-up note indicates indicates the path, t ype, IP address, state, and event count. On mousing over over the port port for the item, item, a pop-up node indicates indicates the port, port, MEP, MAC address, path, type, and event count. l 614-330055-001 DECEMBER 2015 267 CHAPT CH APTER ER 5. CARRIER ETHERNET MANAGEMENT An example of a continuity failure is shown above. See Identifying and Resolving EOAM Configuration Faults on page 270 for recommended actions to resolve identified problems. Third party devices are also displayed in the EOAM Details view. Where a 3rd party device is not managed in ProVision, a linktrace operation initiated from a managed device can reveal the MAC address and status of unmanaged devices that have been configured with either a MEP or MIP on the MA/MEG being traced. Table Tabl e 5-6. EOAM Details View Detail Item Defi Definition nition Connection topology Connection in view MEP end points and intermediate MIPs. Device Name Device name link linked ed to each MEP MEP/MIP, /MIP, sho shown wn in lower lower left of each Details item. Type Device type, sho shown wn in al alll mous mouseovers eovers.. Path Device location location path, shown in all mouseovers. State Managed or Unmanaged, shown in device mouseovers. Active Event Count Act Active ive event count count for ea each ch sseverity everity llevel, evel, sho shown wn in al alll mouseovers. Port Asso Associated ciated device plug-in for each MEP/MIP, shown on port mouseover. MEP Down (out (out)) or Up (inwards), shown on port mouseover. MAC Address Port MAC address for each MEP/MIP, shown on port mouseover. NOTE: If the EOAM includes a trunked link link,, the link displays as shown: 268 AVIAT NETWORKS PROVISION USER MANUAL Viewing EOAM MA Physical Topology With ProVision, you can view the end-to-end topology of a MA/M MA/MEG EG (Layer 2) correlated related with the Ethernet Ethernet and RF (L (Layer ayer 1) ne network twork topology. topology. This is displayed as a filtered view of the Flat Map, using the Flat Map coordinates for positioning each linked Eclipse device. Procedure 1. In the main Pr ProVisio oVision n interf interface, ace, click on the EOAM Tab. 2. The EOAM Tab displays, with the EOAM Servic Services es T Table able.. 3. Se Sele lect ct an EOAM row row in the tab table. le. To view view its physic physical al topology, topology, click Map. 4. The EOAM EOAM Map Map view displays for the se selec lected ted MA/MEG. MA/MEG. Se Seee the table table belo below w for map attributes. attributes. 5. You can can right-click right-click on on devices devices to open open the full full right-c right-click lick menu, menu, including access to the craft tool for the device. Table 5-7. EOAM Map Att Attribu ributes tes 614-330055-001 DECEMBER 2015 269 CHAPT CH APTER ER 5. CARRIER ETHERNET MANAGEMENT Map Item Definition Device Icons Mouse over for device status, including assigned EOAM path, type, state, and alarms. To see alarm levels, see Alarm Severity Solid Line – Physical RF/Ethernet Link Color Coding on page 91 This line is coloured to indicated the highest active severity of the RF link related related alarm conditions. A too tooltip ltip is provided to indicate the RF link endpoints and status. Dotted Line – Physical Ethernet Connection Physical Ethernet Ethernet connection ((e.g. e.g. cable) cable).. This line is co coloured loured to indicate the highest active severity of the Ethernet port alarm conditions.. A tooltip conditions tooltip is provided to indicate path details. Dotted Line – EOAM MA end-to-end Connection nec tion Topology This can can span either a single hop or multipl multiplee hops. Bla Black ck indicates there there is layer 2 connec connectivity tivity between the devices. Red with an “X” indicates ind icates a la layer yer 2 connectivity (c (continuity) ontinuity) fault fault.. A too tooltip ltip is provided to indicate path details. Identifying and Resolving EOAM Configuration Faults In the Ether Ethernet net OAM Diagnostics scre screen, en, users can apply Loopback Loopback and Link Trace Trace operations to the selected Maintenance Association (MA). If the MA has continuity problems, select the device/object adjacent to the point of failure. Then, use the right-click menu to launch the craft tool to resolve the configuration problem. See the EOAM Fault Table in this section for probable cause and recommended actions to resolve identified problems. Procedure 1. 2. In the main Pr ProVisio oVision n interf interface, ace, click on the EOAM Tab. In the EOAM Se Service rvicess table, selec selectt the EOAM link to analyze. RightRight-click click on the link and select Diagnostics. 3. The EOAM Diagn Diagnosti ostics cs scre screen en displays. displays. 270 AVIAT NETWORKS PROVISION USER MANUAL 4. Se Selec lectt whether you are going going to analyze the Loopb Loopback ack or the Link Tr Trace. ace. Go to the Operation item and choose either Loopback or Link Trace. 5. To analy analyze ze Loopback: l l l Select Select the Initiator and Target: MEP or MIP. For a trunk, trunk, you can select the specific specific MAC MAC add addre ress ss fro from m the Target dropdown menu: Set the Number of Mess Messages ages. For a MA configured using 802.1, the maximum message count is 1024. For a MA configured using Y.1731, the maximum message count is 8192. l Set the VLAN Priority. l Click Apply. 6. The Diagno Diagnostic stic is run. run. The Results Results tab displays whethe whetherr the Loopb Loopback ack is a l SUCCESS or a FAILURE, as shown below. Possible problems may include: Radio not responding responding or loopback loopback not supported supported for thi thiss radio l Device deleted (may display if a device is deleted immediately before 614-330055-001 DECEMBER 2015 271 CHAPT CH APTER ER 5. CARRIER ETHERNET MANAGEMENT diagnostics) A loopback loopback is currently currently running running for this this MEP l 7. l l l l To anal analyz yzee Link Trace: Select Select the Initiator and Target MEP or MIP. Set the Time to Live (hops) or the maximum number of maintenance points (EOAM ports) to transverse. For a Y.1731-based Y.1731-based Maintenance Maintenance Association Association there are are two add additional itional options that can be set: Timeout (seconds) and VLAN Priority. For a trunk, trunk, you can select the specific specific MAC MAC add addre ress ss fro from m the Target dropdown menu: Click Apply. l 8. The Diagnostic is run. The The Results Results tab displays whether whether the Link T Trace race is a SUCCESS or a FAILURE, as shown below. Possible problems may include: l Another Link Trace is currently running running on this DAC l Acquiring lock (Another linktrace is running, will try again) 272 AVIAT NETWORKS PROVISION USER MANUAL l l l l Device deleted (may display if a device is deleted immediately before diagnostics) Link Trace Trace has has time out. Radio not not responding responding Target not found (linktrace runs but Target does not respond) EOAM linkT linkTrace race disabled (server_configuration.xml has eoa eoam m linkTrace linkTrace value set to false) 9. Re Resolve solve the fault with the rec recommen ommended ded resolution resolution ac actions, tions, listed listed in the EOAM Fault table below. below. EOAM Fault Table Alarm or Problem Probable Cause and Recommended Action Linktrace failure using manual diagnostics Manual Manual llinkt inktrac racee opera operation tion resul results ts in a failur failure, e, due to a network problem or configuration issue. Actions:: Actions - Run the linktrace again in the opposite direction to confirm where the falure is occurring. Check for invalid configuration changes or physical network i ssues. Loopback failure using manual diagnostics Manual Manual lloo oopback pback opera operation tion res result ultss in a fail failure, ure, due to a network problem or configuration issue. Actions:: Actions - Run the loopback again in the opposite direction to confirm where the failure is occurring. -network Check for invalid configuration changes or physical issues. 614-330055-001 DECEMBER 2015 273 CHAPT CH APTER ER 5. CARRIER ETHERNET MANAGEMENT No Results returned for EOAM Link Trace alarm Automatic linktrace can not b e performed, due to MEP defects on a related port. Actions:: Actions - Fix the MEP defect (see above). - May be due to radio timeout, so run again. MA name (primary VID) does not match the primary VLAN ID Actions: Actions: - Change the MA name(Primary VID) to match the Primary VLAN ID. ME of MEP CCI is not enabled Actions: - Go to Portal for this device and select "CCM Enabled" on the MEP. MEP CCI is not enabled Actions: - Go to Portal for this device and select "CCM Enabled" on the MEP. ME "ME name" CCI is not enabled Actions: - Go to Portal for this device and select "CCM Enabled" on the ME. MEP directions are different Actions: - Change all the MEPs in this MA to be either Down/out Dow n/out or Up/in. MEP ID of MEP appears more than once for this MA/ME You are not allowed to have MEPs i n an MA/ME with the same ID. Actions: Actions: - Ensure that all the MEP IDs in this MA/ME are unique. MEP VID does not match the MA/ME VID Actions: - Either make the MEP VID the same as the MA / ME VID or change the MEP VIDto 0. Port is not a member of VLAN VID Actions: - Add the port to the VLAN. Port X MEP defect alarm A MEP defect has been detect detected ed on the spec specified ified port port,, due to a netwo network rk problem or conf configuratio iguration n issue. Actions: Actions: - Perform a manual link trace and/or loopback to confirm the issue. - Check for configuration changes. Red arrows shown in EOAM inspection or dia- Automatic linktrace has failed to trace in one or both gnostic view directions end-to-end from MEP to MEP. The red arrow indicates the part of the maintenance association that has failed to return a linktrace response, due to a network problem or configuration issue. Actions:: Actions - Perform a manual link trace and/or loopback to confirm the issue. - Check for invalid configuration changes or physical VLAN VID does not exist network issues. Actions: - Either create The "VID" VLAN on all devices or change the VID on the MA/ME to one that exists on all radios. 274 AVIAT NETWORKS PROVISION USER MANUAL Configuring Ethernet OAM This section describes how to configure Ethernet EOAM monitoring of VLANs from ProVision. It also describes how to validate that configuration changes have been applied corre correctly ctly to EOAMs. These functions are supported for: l Eclipse family devices devices with DAC GE3 or IDU GE3 (requir (requires es 7.2.32 o orr later Eclipse firmware) l CTR 8540 devices (require (requiress 2.4 or later CTR 8540 firmware) firmware) l CTR 8300 devices devices (requires (requires 2.3 or later CTR 83 8300 00 firmware) l Provisioning Pro visioning a New New EOAM MA on on page 275 l Modifying Mo difying an EOAM MA MA on page 280 280 l Deleting Dele ting an EOAM MA MA on page 280 280 NOTE: Provisioning Provisioning of EOAM MAs s panning panning C CTR TR and Eclipse devices is not yet supported from ProVision due due to a limitation in the the Eclipse software. This This al so impacts the ability ability to pr ovision ERP rings s pann panning ing CT CTR R and Eclipse. The limitation limitation will be address ed in later Eclipse and ProVision software releases. Interop requires the Legacy Mode tickbox on the Eclipse Portal OAM s creen to be unticked, unticked, and the ass ociated configuration object is not yet ac cess ible to ProVision through through the Eclipse SNMP management interface. Provisioning a New EOAM MA ProVision includes fast Ethernet OAM provisioning for Eclipse, CTR 8540, and CTR 8300. 830 0. Configuring Configuring d devic evices es in isolation can lead t o error errorss and poor configuratio configurations. ns. The Pr ProVisio oVision n EOAM provisioning provisioning simplifie simp lifiess this complex complex task with one screen, screen, accesse accessed d from the VLAN tab. You can use this screen to configure or provision new MAs, or to edit existing MAs. To provision an MA/MEG for a multipoint service VLAN, point-to-point MA/ME needs to be deployed individually using the same VID, MA/MEG ID name and MD / MEG Level. EOAM Provis Provisioning ioning Prerequisites Prerequisites l The VLANs VLANs to be monitored monitored through EOAM must already already be co configur nfigured ed on the Eclipse DAC GE 3 cards. For more information, see Provisioning a New VLAN on page 257 614-330055-001 DECEMBER 2015 275 CHAPT CH APTER ER 5. CARRIER ETHERNET MANAGEMENT l You will need need your y our configur configuration ation info information: rmation: which which devices devices and which specific specif ic ports will be connecte connected. d. You will also need need conf configuratio iguration n details including type (Y.1731 or 802.1ag), names, directions, etc. Procedure 1. Sele lect ct the VLAN tab. VLAN items with EOAM already provisioned show this icon; 2. . To ccre reate ate a new new EOAM, right-clic right-click k on any VLAN VLAN and selec selectt EOAM Provisioning. Select the device/object. Or, to edit an existing EOAM, select it from the drop down menu, or go to the EOAM tab, right-click on the EOAM, and select Edit. 3. The EOAM Provisioning screen displays. Note that it shows the VID from the VLAN's details in the VLAN tab. 4. If the re remote mote end end point MEP is not not on a device being being managed by Pr ProVisio oVision n (e.g., an unsupported third party device type), select Unmanaged Remote End Point, requiring the user to only enter the remote end MEP number. 5. Se Selec lectt the device/o device/obje bject ct and interface/ interface/port port for for Ob Objec jectt B. This will be the second half of the provisioned MA. NOTE: When changing a MA (edit) the Object A and Object B fields cannot be edited. If you need to change the end points, delete this MA and add a new one. 276 AVIAT NETWORKS PROVISION USER MANUAL 6. l You can set set up specific MA/ME MA/ME configur configuration ation option options. s. For Y.1731, Y.1731, these are: are: Mode - Y.1731 MD/MEG MD/ MEG Level Direction l ME ID: ICC - The ITU Carrier Code (ICC) is a unique code assigned to a network operator or service provider by the ITU. It is 1-6 characters, alphabetic, or leading alphabetic with trailing numeric. l ME ID: UMC - The Unique MEG ID Code (UMC) is assigned by the network operator oper ator or service provider provider,, and needs needs to be unique within that organisation’s organisation’s domain. It is 6 characters. The user enters up to the first 4 characters. 7. l l For 802 802.1, .1, the options options are: are: Mode - 802.1 MD Name - Options include String, Primary VID, Unsigned Unsigned Integer Integer,, RFC 2865 VPN ID MD/MEG MD/ MEG Level Direction l MA Name - Options include String, Primary VID, Unsigned Integer, RFC 2865 VPN ID 614-330055-001 DECEMBER 2015 CHAPT CH APTER ER 5. CARRIER ETHERNET MANAGEMENT 8. If re requir quired, ed, you can set up Advanced Advanced configuratio configuration n options. options. Click Advanced to view these. The options include: l MIPs – Add devices that should be configured to act as Maintenance Intermediate Points. l MIP Creation - Select the MIP creation type: None = No MIP will be created for the end points at a l higher MD / MEG level. l Default = MIPs can be created in selected intermediate nodes, regardless of whether a MEP exists at those nodes for a lower MD / MEG level. Requires one or more nodes to be selected for MIPs. l Explicit = MIPs can be created in selected intermediate nodes if a MEP exists at those nodes with a lower MD / MEG level. Requires one or more nodes to be selected for MIPs. l l CCM Interva Intervall – Select an interval from 100ms to 10 minutes. CCM Priority - Select number value between 0 and 7, where 7 is the highest priority prio rity (Y.1731 mode only). 277 278 AVIAT NETWORKS PROVISION USER MANUAL 9. When you have enter entered ed all your re requir quired ed se settings, ttings, click Commit Changes. A progress window displays and confirms when the provisioning is complete. 10. You can now now provision provision further further EOAM EOAM maintenance maintenance association associationss for VLAN items. 11. To validate that the EOAM MA is succe successfully ssfully pr provisio ovisioned: ned: l Check the alarm status of the devices devices in the EOAM. l Run Diagnostics Diagnostics on the EOAM MA/M MA/ME. E. See Identifying and Resolving EOAM Configuration Faults on page 270. 270. NOTE: For CTR devices devices provisioned via the the ProVision softare, the process is c omplete. omplete. Note Not e that if EOAM is provisioned provi sioned for a CT CTR R device via CLI commands, commands , the EOAM notification notification must be set via CLI as w ell: the command is: snmp-serve snmpserver r enab enable le notif notificati ications ons ether ethernet net cfm all 614-330055-001 DECEMBER 2015 279 CHAPT CH APTER ER 5. CARRIER ETHERNET MANAGEMENT Modifying an EOAM MA The procedure for modifying an existing EOAM is the same as the provisioning procedure in the section Provisioning a New EOAM MA on page 275. 275. For an existing MA/MEG, the following settings can be edited. The MA/MEG must be deleted and recreated in order to change other settings. l Mode Mode (802.1ag (802.1ag or or Y Y.1731) .1731) l ICC and UMC (Y.1731) l Addition Addit ion of new MIPs l CCM Interval Interval l CCM Prio Priority rity (Y.1731) (Y.1731) Deleting an EOAM From ProVision, you MA can delete an EOAM MA that is in the EOAM Services Table. W AR NI NG : You c annot annot delete EOAMs included included in an ERP ring fro m ProVision.. D elete the ERP ring first if this ProVision this is required: see Deleting an ERP Ring on page 292 . W AR NI NG : You cannot delete individual MEP-to-MEP point-to-point segments of an MA/MEG assoc iated with with a multipoint multipoint service VLAN. When Wh en selec tin ting g to delete one of the the MA/MEG entries in the EOAM Table, you are prompted whether to delete all MA/MEG segments (i.e. the complete multipoint multipoint MA/MEG). On confirmation, all the MA/MEG segments are deleted in a single single tra nsaction. Procedure 1. In the main Pr ProVisio oVision n interf interface, ace, click on the EOAM Tab. 2. The EOAM Tab displays, with the EOAM Servic Services es T Table able.. 3. Se Selec lectt an EOAM row row in the table. table. To delete delete it, rightright-click click it it and select Delete. 4. A message displays, asking you to conf confirm irm the dele deletion. tion. If you are certain, certain, click Yes. 5. The EOAM EOAM is deleted deleted from from the de device vicess and the network. network. (For CTR de device vices, s, .) see Saving Carrier Ethernet Configuration for CTR Devices on page 11.) 6. To co conf nfir irm m that the MA is dele deleted: ted: 280 AVIAT NETWORKS PROVISION USER MANUAL l l Check the VLAN VLAN Details Details view to ensure ensure that the EOAM no longer longer displays in association with a VLAN. Check the EOAM Tab Tab to ensure that t he EOAM MA/M MA/ME E no longer displays. 614-330055-001 DECEMBER 2015 281 CHAPT CH APTER ER 5. CARRIER ETHERNET MANAGEMENT ERP Ring Management This section describes how to use ProVision to perform the following ERP operations: l Viewing discovered discovered network rings (Layer 1 and ERP rings) l Viewing ring configuration details l Configuring ERP rings l Creating Creating an ERP ring l Modifying Modifying an ERP ring l Deleting Deleting an ERP ring l Validating ERP ring conf configuratio iguration n ProVision Pro Vision provides ERP ring management for the follo following wing device types: l Eclipse family devices devices with DAC GE3 or IDU GE3 (for (for ERP ERP provisio provisioning, ning, this requires 7.3.32 or later Eclipse firmware). l CTR 8300 devices (requir (requires es 2.3 or later CTR 8300 8300 firmware) l CTR 8540 devices (require (requiress 2.4 or later CTR 8540 firmware) firmware) Limitations: l l EOAM Up/In Up/In MEP conf configuratio iguration n is not supported by CTR 2.3 and 2.4 software, preventing ERP subrings from being configured. EOAM 802.1ag 802.1ag based ERP rings rings are not not suppor supp orted ted by CTR 2.3 and 2.4 software. The following sections are provided: l l l l Overview Over view of ERP on on page 282 Viewing Discovere Viewing Discovered d ERP Rings and Ring Configuratio Configuration n on page 283 Viewing Viewi ng ERP Ring Ring Configuration Configuration Details on page 285 285 Configuring Config uring an ERP Ring on on page 286 Provisionin Pro visioning g a New ERP Ring Ring on page 286 l l Provisionin Pro visioning g an ERP Subring Subring on page 290 l Modifying Mo difying an ERP Ring on page 292 l Deleting an ERP Ring on page 292 Overview of ERP Ethernet Ring Protection (ERP), also known as Ethernet Ring Protection Switching (ERPS) ITU-T G.8032 / Y.1344, is a form of network protection that enables CarrierGrade Ethernet services and performance by providing fast recovery from failure (sub 50ms) and removing loops in layer 2 networks. 282 AVIAT NETWORKS PROVISION USER MANUAL Pr ProVisio oVision n provides provides ERP management for t he following device typ types: es: l l l Eclipse family devices devices with DAC GE3 or IDU GE3 (requir (requires es 7.2.32 o orr later Eclipse firmware) CTR 8540 devices (require (requiress 2.4 or later CTR 8540 firmware) firmware) CTR 8300 devices devices (requires (requires 2.3 or later CTR 83 8300 00 firmware) What is Network Protection? Ne Network twork protection protection uses the topology of the netwo network rk to provide alter alternate nate pat hs to reach a final destination. Normally, only one path is used at a time and the other paths are either blocked or kept in a standby mode. In the event of failure or congestion the network protection p rotection protoco p rotocoll re-routes re-routes the affected affected traffic tthrough hrough the next best best alternate path. The most common network topology to provide protection is ring topology but in the data world mesh topology is also very popular. ERP The main purpose of ERP is to provide fast recovery from failure (sub 50ms) and remove loops in layer-2 networks. ERP eliminates the loops in the network by selecting a Ring Protection Link (RPL), a Ring Protection Link Owner (RPL), and a protocol that allows it to indicate and react to failures on the other nodes or links in the ring. With ERP configured, under normal conditions the RPL is blocked. When a link failure is detected the RPL is unblocked, healing the ring. ERP rings can be revertive or non-revertive. l G.8032 uses standard Ca Carrie rrierr Ethernet technology: technology: 802.1 802.1 MAC address learning, learning, forwar forwarding ding and FDB flushing functions l l l l l 802.1q 802.1q VLAN VLAN tagging l Y.1731 EOAM MA/M MA/MEGs EGs using CCMs to detect failure failure Depending Depending on the CCM C CM interval interval the topology reconve reconverge rgence nce can be achie achieved ved in less than 50 ms Other failure failure de detectio tection n mechanisms (normally (normally at t he physical layer) can be used to expedite the failure recovery. Two versio versions ns of the pro protoco tocoll are supported supported at this time G.8031v1 and G.8032v2. Both use Ring Automatic Protection Switching PDUs (R-APS) to communicate among the nodes; SF, NR, RB. Viewing Discovered ERP Rings and Ring Configuration From the VLAN Tab, you can view devices configured into ERP rings, and the details of the ring configuration. 614-330055-001 DECEMBER 2015 283 CHAPT CH APTER ER 5. CARRIER ETHERNET MANAGEMENT NOTE: The top topology ology map view of ERP co nfiguration nfiguration is is par t of the EOAM topology map view. See Viewing EOAM MA Physical Topology on page 26 9 . Procedure 1. Sele lect ct the VLAN Tab. The automatically discovered VLANs display in the VLAN table. VLANs with an active ERP ring disp display lay this icon: . VLANs on a phy physical sical ring that can support supp ort ERP disp display lay this icon: . You can sort the table for ERPs to display disp lay active ERPs and VLANs with ERP support by clicking on the ERP header. 2. To view view the ERP ring ring for for a VLAN VLAN,, select select a VLAN that has the ERP ic icon on.. Then, click Map. The Map view displays the VLAN with the ERP ring. 3. By default, the VLAN VLAN table and VLAN Map Map is filte filtere red d to list only the member ports (for each VLAN) on the devices within the selected container object in the Tree View. Where Ring nodes are deployed in separate Tree view containers (e.g. regions), select the Show All Member Ports check box to see all the ring nodes on the VLAN Map. 4. To filte filterr the list of VLA VLANs Ns ffor or ER ERP P data, you can: 284 AVIAT NETWORKS PROVISION USER MANUAL l So Sort rt the table by clicking clicking on table headers, headers, espe especially cially the ERP column. l Click on the Filter button to filter filter for specifi specificc text or number numbers. s. l Enter a text filter into the Selected Selected Object Object field. For more information, see Viewing Discovered ERP Rings and Ring Configuration on page 283 and Viewing VLANs in the Physical and Flat Maps on page 252 252.. Viewing ERP Ring Configuration Details You can view ERP member and RPL owner details for an ERP control V VLAN. LAN. Procedure 1. To view view the ERP details details for an ERP contro controll VLAN, in the VLAN VLAN tab, tab, select select a VLAN that has the ERP icon. 2. To view view the co confi nfigur guratio ation n details, details, clic click k Details. Click the ERP tab. This tab presents the details for the ERP associated with the selected VLAN, including the presence of any subrings. The ERP Details tab values are described in the table below. Details Tab - ERP Ring Deta etails Item tem Defi efiniti tion on Name Name of the ERP ring. 614-330055-001 DECEMBER 2015 285 CHAPT CH APTER ER 5. CARRIER ETHERNET MANAGEMENT Members Devices and port portss on the devices used for the ERP ERP.. Fo Forr exampl example, e, INUe153 is the device name, and 7/2 indicates the slot and port (respectively). RPL Owner Ring Protection Link Owner – device/port with this icon. Subring ERP Subring - The Subring component of this ERP ring, i.e., the Up/In EOAM. RPL Owner on a Subring RPL RPL Owner on the Subring (inva (invalid!) lid!) - The RP RPL L Owner is not not allowed on the Subring component of an ERP ring. Configuring an ERP Ring This section describes how to configure ERP rings from ProVision. l Provisioning Pro visioning a New New ERP Ring on on page 286 l Provisioning Pro visioning an ERP Subr Subring ing on page 290 l Modifying Mo difying an ERP Ring on on page 292 292 l Deleting Dele ting an ERP Ring on on page 292 292 NOTE: Provisionin Provisioning g of EOAM MAs s panning panning C CTR TR and Eclipse devices is not yet supported from ProVision due due to a limitation in the the Eclipse software. This This a lso impacts the ability ability to pr ovision ERP rings s pann panning ing CT CTR R and Eclipse. The limitati limi tation on will be address ed in later Eclipse and ProVision software releas es. Interop requires the Legacy Mode tickbox on the the Eclipse Portal O AM scr een to be unticked, unticked, and the associated configuration figu ration object is not yet acces sible to ProVision through through the Eclipse SNMP management interface interface . Provisio Pro visioning ning a Ne New w ERP Ring ProVision includes fast ERP ring provisioning for Eclipse, CTR 8540, and CTR 8300.

pdf-aviat-pv-user-manual compress

Related documents

Products

Support

pdf-aviat-pv-user-manual compress

Related documents

Add this document to collection(s)

Add this document to saved

Suggest us how to improve StudyLib