VoIP and Network Quality Manager Administrator Guide

Copyright © 2015 SolarWinds Worldwide, LLC. All rights reserved worldwide.No part of this document may be reproduced by any means nor modified,decompiled, disassembled, published or distributed, in whole or in part, ortranslated to any electronic medium or other means without the written consentof SolarWinds. All right, title, and interest in and to the software anddocumentation are and shall remain the exclusive property of SolarWinds andits respective licensors.SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHERTERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ONSOFTWARE AND DOCUMENTATION FURNISHED HEREUNDERINCLUDINGWITHOUT LIMITATION THE WARRANTIES OF DESIGN,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, ANDNONINFRINGEMENT. IN NO EVENT SHALL SOLARWINDS, ITSSUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES,WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGALTHEORY EVEN IF SOLARWINDS HAS BEEN ADVISED OF THEPOSSIBILITY OF SUCH DAMAGES.The SOLARWINDS and SOLARWINDS & Design marks are the exclusiveproperty of SolarWinds Worldwide, LLC and its affiliates, are registered withthe U.S. Patent and Trademark Office, and may be registered or pendingregistration in other countries. All other SolarWinds trademarks, service marks,and logos may be common law marks, registered or pending registration in theUnited States or in other countries. All other trademarks mentioned herein areused for identification purposes only and may be or are trademarks orregistered trademarks of their respective companies.

VoIP and Network Quality Manager Version 4.2.2, revised 11/16/2015

About SolarWindsSolarWinds, Inc develops and markets an array of IT management, monitoring,and discovery tools to meet the diverse requirements of today’s ITmanagement and consulting professionals. SolarWinds products continue toset benchmarks for quality and performance and have positioned the companyas the leader in IT management and discovery technology. The SolarWindscustomer base includes over 85 percent of the Fortune 500 and customersfrom over 170 countries. Our global business partner distributor networkexceeds 100 distributors and resellers.

Contacting SolarWindsYou can contact SolarWinds in a number of ways, including the following:

Team Contact information

Sales 1.866.530.8100www.solarwinds.com

Technical Support www.solarwinds.com/support

User Forums www.thwack.com

ConventionsThe documentation uses consistent conventions to help you identify itemsthroughout the printed and online library.

Convention Specifying

Bold Window items, including buttons and fields.

Italics Book and CD titles, variable names, new terms

Fixed font File and directory names, commands and codeexamples, text typed by you

http://www.solarwinds.net/

http://www.solarwinds.net/support

http://www.thwack.com/

Convention Specifying

Straight brackets, asin [value]

Optional command parameters

Curly braces, as in{value}

Required command parameters

Logical OR, as invalue1|value2

Exclusive command parameters where only one ofthe options can be specified

SolarWinds VoIP and Network Quality ManagerDocumentation LibraryThe following documents are included in the SolarWinds VoIP and NetworkQuality Manager documentation library:

Document Purpose

SolarWinds VoIP andNetwork QualityManager AdministratorGuide

Provides detailed setup, configuration, andconceptual information.

Page Help Provides help for every window in theSolarWinds VoIP and Network Quality Manageruser interface.

Release Notes Provides late-breaking information, knownissues, and updates. The latest Release Notescan be found at www.solarwinds.com

http://www.solarwinds.com/

The following documents supplement the SolarWinds VoIP and NetworkQuality Manager documentation library with information about NetworkPerformance Monitor:

Document Purpose

NetworkPerformanceMonitorAdministrator Guide

Provides detailed setup, configuration, andconceptual information.

Page Help Provides help for every window in the NetworkPerformance Monitor user interface.

Release Notes Provides late-breaking information, known issues,and updates. The latest Release Notes can be foundat www.solarwinds.com.

http://www.solarwinds.net/

Table of ContentsTips and Tricks 18Introduction 19Why Install SolarWinds VoIP and Network Quality Manager 19What SolarWinds VoIP and Network Quality Manager Does 19How SolarWinds VoIP and Network Quality Manager Works 22

Installing SolarWinds VoIP and Network Quality Manager 24SolarWinds VNQM Licensing 24IP SLA Sites 25IP Phones 25Nodes 25Licensing example 25

Installation Requirements 26SolarWinds VoIP and Network Quality Manager Requirements 26SQL Server Requirements 27

Installing SolarWinds VNQM 29Additional Polling Engine and Web Console 33Installing an Additional Polling Engine 33Installing an Additional Web Console 35Upgrading VNQM 37Uninstalling VNQM 38

Configuring VoIP and Network Quality Manager 39IP SLA Management 40

7

Understanding Quality of Service and IP SLAs 40IP SLA Operations in VNQM 41

Quality of Service Metrics 42Latency 42Jitter 44Packet Loss 46Mean Opinion Score (MOS) 48

Understanding Polling Intervals for IP SLA Operations 49Designating Paths 51Understanding the Impact IP SLA Operations Have on Your Network 51Dangers of Overusing IP SLA Operations 52Strategies for the Proper Use of IP SLA Operations 53

Configuring Devices for IP SLA Operations 54Configuring devices for ICMP echo path operations 54

Adding IP SLA Nodes to VoIP and Network Quality Manager 56Discovering IP SLA-Capable Nodes Automatically 56Adding IP SLA-Capable Nodes Manually 57Configuring CLI Credentials 57

Adding IP SLA Operations 58Adding DNS IP SLA Operations to Your Devices 59Adding FTP IP SLA Operations to Your Devices 60Adding HTTP IP SLA Operations to Your Devices 62Adding DHCP IP SLA Operations to Your Devices 63Adding TCP Connect IP SLA Operations to Your Devices 65Adding UDP Jitter IP SLA Operations to Your Devices 67Adding VoIP UDP Jitter IP SLA Operations to Your Devices 69Adding ICMP Echo IP SLA Operations to Your Devices 71Adding UDP Echo IP SLA Operations to Your Devices 74Adding ICMP Path Echo Operations to Your Devices 76Adding ICMP Path Jitter Operations to Your Devices 78

8

VoIP and Network Quality Manager Administrator Guide

9

Adding Existing Operations to VoIP and Network Quality Manager 81Editing IP SLA Operations 82Modifying the SLA Location 82Renaming Operations in VoIP and Network Quality Manager 83

Deleting IP SLA Operations from VoIP and Network Quality Manager 83VoIP Management 84Managing Call Managers 85

CLI Credentials 85Credentials Used for Cisco CallManager 86

Monitoring Call Manager Health 86Adding Cisco CallManager Devices to VoIP and Network Quality Manager 87Adding CallManager Express Devices to VoIP and Network Quality Manager 90Managing Avaya Call Managers 90Setting up an Avaya Call Manager to emit quality data 95

Avaya CDR parameters 97Adding Avaya Call Manager Devices 98Adding an Avaya Communication and Media Server to VNQM 98Requirements for Handling RTCP Data 100

Bandwidth Requirements for Avaya Communication and Media Servers 101Adding Call Manager Devices from Other Manufacturers 101Defining FTP Servers 102Configuring Cisco CallManagers for FTP 102Editing Call Managers 103Call Manager CDR/CMR Polling 104AXL Credentials 104FTP Server Settings 105Call Manager CDR/CQR Polling 106Call Manager CLI Credentials 106Deleting Call Manager Devices from VoIP and Network Quality Manager 106

Managing Gateways 107

Table of Contents

Adding Gateways 107Editing VoIP Gateways 108Editing CLI Credentials for Gateway Nodes 109Removing Gateways 110

Selecting VoIP and Network Quality Manager Infrastructure 111Call Precedence Levels 112

VoIP and Network Quality Manager Settings 112VNQM Settings Overview 112IP SLA Management 113Manage IP SLA Operations 113Manage IP SLA Nodes 113

VoIP Management 113Manage CallManager Nodes 113Manage VoIP Gateways 114Select VoIP Infrastructure 114

Details 114Edit VoIP and Network Quality Manager Settings 114Database Details 115

Configuring VoIP and Network Quality Manager Settings 115Setting Traffic Precedence 118

Using VoIP and Network Quality Manager 120Starting VNQM 120Exploring VNQM Views 121VoIP CallManager View 122

Customizing Charts in VNQM 124Chart Titles 124Calculated Series 125Time Period 125Sample Interval 126Chart Size 126

10


11

Data Tables 126Font Size 126Printing Options 126Data Export Options 127Advanced 127

Using Custom Properties for VNQM 127Using Alerts and Alert Actions in VNQM 128Creating and Managing Alerts 128Alert Preconfiguration Tasks 129Sending an Email/Page 129Dialing a Paging or SMS Service 130Playing a Sound 130Sending an SMNP Trap 131Creating Text to Speech Output 131

Configuring the Default Email Action 131Navigating to the Alert Manager 132Settings Page (Recommended) 132All Active Alerts Resource 133Active Alerts Details 133Node Details 133

Best Practices and Tips for Alerting 133Use the Out of the Box Alerts as Templates 133Restrict Who Receives Alerts 133Plan which Devices to Monitor 133Establish Dependencies 134

Creating New Alerts 134Setting Alert Properties 135Setting Trigger Conditions 137Setting Reset Conditions 139Setting the Time of Day or Schedule 141

Table of Contents

Setting Trigger Actions & Escalation Levels 143Trigger Actions 144Escalation Levels 145

Setting Reset Actions 145Reviewing the Alert Summary 146

Commonly Created Alerts 147Alert Me When a Server is Down 147Use a Custom Property in Alerts 149

Viewing Triggered Alerts 151Acknowledging Alerts 151Testing Alerts 152Testing Trigger Conditions 152Testing Trigger or Reset Actions within the Alert 152Testing Actions in the Action Manager 153

Managing Alerts 153Adding and Editing Alerts 153Enabling and Disabling Alerts 154Exporting or Importing Alerts 154Deleting Alerts 154

Building Complex Conditions 154Waiting for Multiple Objects to Meet the Trigger Condition 155Evaluating Multiple Condition Blocks 155How Condition Blocks Are Evaluated 156

Evaluating Multiple Object Types 156Available Alert Actions 157Changing Custom Property 158Dialing Paging or SMS Service 159Emailing a Web Page 160Executing an External Program 161Executing a Visual Basic Script 163

12


13

Logging an Alert to a File 164Logging an Alert to the NPM Event Log 165Managing the resource allocation of a virtual machine 166Deleting a snapshot of a virtual machine 168Moving a virtual machine to a different host 169Moving a virtual machine to a different storage 171Pausing a virtual machine 172Powering off a virtual machine 173Powering on a virtual machine 174Restarting a virtual machine 175Suspending a virtual machine 176Taking a snapshot of a virtual machine 177Playing a Sound 179Restarting IIS Site or Application Pools 180Sending a Windows Net Message 181Sending an SNMP Trap 182Using Get or Post URL Functions 184Sending a Syslog Message 185Sending an Email/Page 186Setting Custom Status 188Using Text to Speech Output 189Logging an Alert to the Windows Event Log 190

Changes in the Alerting Engine 192Changed or removed functionality 192Database changes 192Macro or variable changes 193

Alert Migration to the Web 193Migration Issues 193Limitations to Migrated Alerts 193

Integrating Alerts with Other Products 194

Table of Contents

VNQM Reports 194Using Predefined VNQM Reports 195Historical IP SLA Reports 195Historical VoIP Reports 199

VNQMMaps 200VoIP and Network Quality Manager Map Variables 200

Appendix A: References 203Troubleshooting 203Back Up Your Data 203Verify Program Operation 203Stop and Restart 204Run the Configuration Wizard 204Working with Temporary Directories 205Moving the SQL Server Temporary Directory 205Redefining Windows System Temporary Directories 205

Slow Performance on Windows Server 2008 206Adjusting Interface Transfer Rates 207Error When Creating New Group 207

Orion Variables and Examples 207Variable Construction 208Variable Modifiers 208General Alert Variables 209Date Time 211Group Variables 213SQL Query 215Status Values 215Node Variables 217Defunct Alert Variables 228

Example Messages Using Variables 228Using Macro Formatters 230

14


15

Syslog Alert Variables 230Syslog Date/Time Variables 230Other Syslog Variables 232

Trap Alert Variables 233Trap Date/Time Variables 233Other Trap Variables 235

Status Icons and Identifiers 23595th Percentile Calculations 236Regular Expression Pattern Matching 237Characters 237Character Classes or Character Sets [abc] 238Anchors 239Quantifiers 240Dot 242Word Boundaries 243Alternation 243

Required SolarWinds Account Permissions 244Appendix B: Software License Key 246Maintaining Licenses with License Manager 247Installing License Manager 247Using License Manager 248

Appendix C: MIBs Maintained by VoIP and Network Quality Manager 250General 250All Operations 250DHCP Operations 251DNS Operations 251HTTP and FTP Operations 251ICMP Echo Operations 251TCP Connect Operations 251UDP Jitter Operations 252

Table of Contents

VoIP UDP Jitter Operations 252VoIP Specific MIBs 253

Appendix D: Supported Versions of Cisco Unified Call Manager 254OIDs from the ccmTable 254OIDs from the ccmRegionTable 255OIDs from the ccmGatewayTable 255OIDs from the ccmProductTypeTable 255OIDs from the ccmPhoneTable 256OIDs from the ccmPhoneExtnTable 256OIDs from the ccmH323DeviceTable 256

Appendix E: How VoIP and Network Quality Manager Creates Operations 258Owner Field Value 258SNMP-Based Operations 258DHCP Operations 259DNS Operations 260FTP Operations 261HTTP Operations 262ICMP Echo Operations 263TCP Connect Operations 265UDP Echo Operations 266UDP Jitter Operations 267VoIP UDP Jitter Operations 269

CLI-Based Operations 271ICMP Path Echo Operations 271IP SLA Syntax 271IP SLA Monitor Syntax 272RTR Syntax 272

ICMP Path Jitter Operations 273IP SLA Syntax 273IP SLA Monitor Syntax 273

16


17

RTR Syntax 274Appendix F: Database Maintenance 275Running Database Maintenance 275

Table of Contents

Tips and Tricksl Network Performance Monitor provides default chart titles and subtitles.To restore the default values, clear the respective fields when editingchart titles, and then click Submit.

l To display gauges and charts for the opposite direction call path betweenthe same two endpoints, click View reverse call path.

l The time interval for collecting CDR and CMR data can be modifiedduring the configuration of Cisco call managers. For more information,see Configuring Cisco CallManagers for FTP.

l To find the necessary balance between server load and data granularity,try using different polling intervals. For more information, see ConfiguringVoIP and Network Quality Manager Settings.

l Configure the length of time performance data is retained to balancedatabase maintenance with IP SLA requirements. For more information,see Configuring VoIP and Network Quality Manager Settings.

18

Tips and Tricks

IntroductionSolarWinds VoIP and Network Quality Manager offers an easy-to-use,scalable IP SLA network monitoring solution that can integrate seamlessly withother SolarWinds products on the Orion platform.

Why Install SolarWinds VoIP and NetworkQuality ManagerInternet Protocol Service Level Agreement (IP SLA) technology offers acost-effective and efficient response to the needs of enterprises of all sizes. Asa network manager, you face more than the simple question of whether yournetwork is up or down. You need to know specific quality of servicemeasurements for your network. VoIP and Network Quality Manager gives youthe tools to quickly test the fitness of your current network, and then determineand track quality of service on your network over time.SolarWinds VoIP and Network Quality Manager collects IP SLA-specific dataand provides presentation tools that enable IP SLA network monitoring andreal-time status reporting. VoIP and Network Quality Manager can also beused in integration with SolarWinds Network Performance Monitor, leveragingthe NPMmonitoring options to provide a better overview of your network.

What SolarWinds VoIP and Network QualityManager DoesWith VoIP and Network Quality Manager you can monitor and report both real-time and historical performance statistics for your IP SLA-capable network.

19

Introduction

VoIP and Network Quality Manager offers the following features to help youmanage your entire network.Quality of Service (QoS) Monitoring with Cisco IP SLA Operations

VoIP and Network Quality Manager uses Cisco IP SLA operations tomeasure network performance. Specifically, IP SLA operations provideimmediate insight into network Quality of Service (QoS), including packetloss, latency, jitter, and mean opinion score (MOS) metrics. VoIP andNetwork Quality Manager collects IP SLA data and then presents it in theeasy-to-use Web Console environment. With VoIP and Network QualityManager and IP SLA operations, you know at a glance exactly how wellyour network is and has been performing. For more information aboutCisco IP SLA operations, see www.cisco.com/go/ipsla.

VoIP Phone TroubleshootingVoIP and Network Quality Manager uses Call Detail Records (CDR) andCall Management Records (CMR) data from your call managers to helpyou identify possible affected calls and patterns of affected calls.CDR/CMR data provides region information per call record in addition tothe call source and destination, MOS, latency, packet loss, terminationcall code, and more. With VoIP and Network Quality Manager, you candrill in to problem areas to start identifying the underlying problems.

Custom Charts and GaugesVoIP and Network Quality Manager provides easy-to-read charts andgauges that you can customize to suit your monitoring requirements. Youcan quickly determine the current status and performance of your networkusing custom VoIP and Network Quality Manager gauges of key IP SLAmetrics such as jitter, latency, packet loss, and MOS. With custom VoIPand Network Quality Manager charts, you can easily track the historicalperformance of all the paths on your network.

20

http://www.cisco.com/go/ipsla

Custom Alerts and ActionsVoIP and Network Quality Manager enables you to create custom alertsfor your network in the same way you create advanced alerts and actionsin Network Performance Monitor. Specifically, VoIP and Network QualityManager enables you to configure IP SLA-related alerts with a variety ofcorresponding actions to notify you of events on your network. These IPSLA alerts are filtered from existing alerts and presented separatelywithin VoIP and Network Quality Manager. For more information aboutusing Advanced Alerts in VoIP and Network Quality Manager, see UsingAdvanced Alerts and Actions in the VoIP and Network Quality ManagerAdministrator Guide.

Custom ReportingWith Orion Report Writer, VoIP and Network Quality Manager providesreal-time and historical statistics reporting for the IP SLA-specific networkstatistics. When you install VoIP and Network Quality Manager, severalpredefined reports become available within Report Writer. By usingcustom properties, you can also generate custom reports to specificallycommunicate the historical condition of your network. For moreinformation about data reporting in VoIP and Network Quality Manager,see Creating VoIP and Network Quality Manager Reports in the VoIPand Network Quality Manager Administrator Guide.

Gateway MonitoringVoIP and Network Quality Manager provides comprehensive resourcesthat enable you to monitor your VoIP gateways, giving you an overviewof individual PRI trunks of your gateways.

Call Manager MonitoringCall manager devices are scalable call processing solutions formanaging IP-based telecommunications networks. These devicesprovide VoIP networks with the features and functions of more traditionaltelephony. VoIP and Network Quality Manager uses the SNMP andICMP monitoring technology and the AXL API of Cisco to interact withcall managers and to persistently track call manager performance. Withthe addition of VoIP and Network Quality Manager, you immediatelyknow the status of your VoIP network and all of its components at anytime.

21

What SolarWinds VoIP and Network Quality Manager Does

Introduction

VoIP and Network Quality Manager comes with presets that allow you tomonitor Cisco CallManager and CallManager Express, and Avaya CallManager devices. You can also define custom Management Information Base(MIB) pollers to monitor call managers from other manufacturers. Callmanagers by other manufacturers are monitored like other nodes and cannotbe added as call managers. For more information, consult the following table:

Topic Reference

Custom MIB Pollers See Monitoring MIBs with Universal DevicePollers in the SolarWinds Network PerformanceMonitor Administrator Guide.

Cisco CallManagerSupported Devices

Search for "CallManager" at www.cisco.com.

Adding CiscoCallManager Devices

See Managing Cisco CallManager Devices in theVoIP and Network Quality Manager AdministratorGuide.

Adding Avaya CallManager Devices

See Adding Avaya Call Manager Devices.

MonitoringCallManager Devicesfrom OtherManufacturers

See Adding Call Manager Devices from OtherManufacturers in the VoIP and Network QualityManager Administrator Guide.

How SolarWinds VoIP and Network QualityManager WorksSolarWinds VoIP and Network Quality Manager builds upon the proventechnology of the SolarWinds Orion platform to give you monitoring, alerting,and reporting abilities for your network.

22

http://www.solarwinds.com/documentation/helploader.aspx?topic=OrionAGMonitoringCustomMIBs.htm

http://www.solarwinds.com/documentation/helploader.aspx?topic=OrionAGMonitoringCustomMIBs.htm

http://www.cisco.com/

http://www.solarwinds.com/documentation/helploader.aspx?topic=OrionIPSLAManagerAdministratorGuide-AddingAvayaCallManagersToVNQM.htm

After installation and initial configuration, VoIP and Network Quality Managerdeploys Cisco IP SLA operations to generate various types of network trafficincluding DNS requests, DHCP IP allocation, FTP and HTTP requests, TCPconnect, ICMP and UDP Echo, and simulated VoIP traffic between devices onyour network using the jitter codec you specify. Cisco IP SLAs provide real-time and historical performance statistics that VoIP and Network QualityManager presents in the readily customizable Web Console. VoIP andNetwork Quality Manager downloads CDR/CMR data from your Cisco callmanager and uses your AXL credentials to pull region information to providedetailed call record information about every call in your network.You can also monitor Avaya Communication and Media Server devices withVoIP and Network Quality Manager. VNQM intercepts the CDR packets sentby the TCP protocol, as well as the RTCP data sent through UDP, and basedon these data, it provides information about the call details and the call quality.IP SLA operations VoIP and Network Quality Manager only work with CiscoIOS devices that support the RTT MIB. For more information about the MIBsVoIP and Network Quality Manager uses, see MIBs Maintained by VoIP andNetwork Quality Manager in the VoIP and Network Quality ManagerAdministrator Guide.Note: For VoIP statistics, VoIP and Network Quality Manager uses simulatedVoIP traffic, instead of real VoIP traffic. This ensures the continuous collectionof performance statistics so you can know the state of your network at any time,regardless of whether the network is actually being used to complete a call.

23

How SolarWinds VoIP and Network Quality Manager Works

Installing SolarWinds VoIP andNetwork Quality ManagerSolarWinds VoIP and Network Quality Manager provides a simple, wizard-driven installation process.The installation is powered by the following tools:

1. VNQM Installation Wizard installs VNQM and launches the installationof the corresponding .NET framework requirements.

2. VNQM Licence Activation Wizard deals with the activation of yourlicense, you can temporarily skip this step.

3. SolarWinds Configuration Wizard takes care of the basic configurationof VNQM.

You can find more installation related details in the following sections:

l VNQM Licensingl Installation Requirementsl Installing SolarWinds VNQMl Additional Polling Engine and Web Consolel Upgrading VNQMl Uninstalling VNQM

SolarWinds VNQM LicensingSolarWinds VoIP and Network Quality Manager uses four different licensetypes and is licensed on the IP SLA site level, the IP Phone level, and thenode level.The following license types are available:

l SLA 5 – 5 IP SLA sites, 300 IP Phones, and 40 nodesl SLA 25 – 25 IP SLA sites, 1500 IP Phones, and 200 nodes

24

Installing SolarWinds VoIP and Network Quality Manager

l SLA 50 – 50 IP SLA sites, 3000 IP Phones, and 400 nodesl SLA X – Unlimited IP SLA sites, unlimited IP Phones, and 1000 nodes

IP SLA SitesAny device that has at least one monitored operation counts toward your IPSLA site count.

IP PhonesAny IP phone connected to your network when the network is polled countstoward your IP Phone count. Phones can be registered or unregistered.Registered phones are connected, take precedence over unregistered phones,and count toward your license. Unregistered phones are disconnected and donot count toward your license. If you have more registered IP phones than thenumber granted to you by your license, only the latest registered phones willbe monitored, up to the number of phones granted by your license. Registeredand unregistered phones after that number will not be monitored.

NodesAny SNMP-enabled device that you monitor counts toward your node count.Each monitored call manager typically consumes a node license.Each source node counts towards your node count. In a bidirectional setup,each node is both a source and target node, and they both count towards yourlicense.

Licensing exampleIf your network uses four IP SLA sites, 45 nodes, and 700 IP Phones, you maydecide to purchase the smallest license.The number of IP SLA sites fall within your license count, but the number ofnodes and IP Phones do not. When you configure VoIP and Network QualityManager, you must choose 40 out of your 45 nodes to monitor, including thecall managers you want to monitor. VoIP and Network Quality Managerautomatically monitors only 300 registered IP Phones at a time of the 700 onyour network. Each time your network is polled, a different 300 registered IPPhones may be monitored.

25

Installation RequirementsThe following requirements are based on a minimum installation of VoIP andNetwork Quality Manager with SQL Server on a separate database server.If you are installing VoIP and Network Quality Manager with SolarWindsNetwork Performance Monitor, the server that you use to host VoIP andNetwork Quality Manager must also support an installation of NPM.Note: To optimize database scalability, we recommend that you maintain yourSQL Server installation on its own server, separate from the server on whichyou are hosting SolarWinds Network Performance Monitor and VoIP andNetwork Quality Manager. If you must host your SQL server on the sameserver, we recommend a quad-processor, 2.67 GHz, 64-bit CPU and at least16 GB of RAM.

SolarWinds VoIP and Network Quality Manager Requirements

Hardwareor software Requirements

Environment VoIP and Network Quality Manager supports IP SLA forCisco IP SLA capable devices. It is possible to monitor CiscoCallManager, CallManager Express, and AvayaCommunication and Media Server devices with VoIP andNetwork Quality Manager.

CPU Dual processor, 3GHz

RAM 8 GB

Hard drivespace

20 GB

Operatingsystem

Windows Server 2003 SP2 (32-bit), Enterprise edition orhigher, including R2, with IIS installedWindows Server 2003 SP2 (64-bit), including R2, with IISinstalled, running in 32-bit modeWindows Server 2008 (32-bit), Enterprise Edition or higher,with IIS installed

26

Installation Requirements


Hardwareor software Requirements

Windows Server 2008 (64-bit), with IIS installed, running in32-bit modeWindows Server 2012

.NETFramework

Version 4.0

Webbrowser

Internet Explorer version 8 or laterMozilla Firefox - two most recent versionsGoogle Chrome - two most recent versions

SQL Server Requirements

Hardware orsoftware Requirements

CPU Dual processor, 3 GHzQuad-processor, 2.67 GHz, 64-bit (for largenetworks)

RAM 8 GB16 GB (for large networks)

Hard drive space 20 GB

Database SQL Server 2008 Express, Standard, or EnterpriseSQL Server 2012 Express, Standard, or EnterpriseSQL Server 2012 SP1SQL Server 2014

Notes:

l If you anticipate six million standard, device to device calls per monthwith a peak hour of 20,000 calls, we recommend using a dedicated SQL

27

server with a 64-bit, 2.67 GHz quad-processor CPU and 16 GB of RAM.We do not support more than six million calls per month.

l If you are installing VoIP and Network Quality Manager with SolarWindsNPM, see Orion NPM Requirements in the SolarWinds NetworkPerformance Monitor Administrator Guide.

28

SQL Server Requirements

http://www.solarwinds.com/documentation/helploader.aspx?topic=OrionAGRequirements.htm


Installing SolarWinds VNQMSolarWinds VoIP and Network Quality Manager employs an intuitive wizard toguide your installation.To install VNQM:

1. Log on as an administrator to the server you will use to monitor your IPSLA network.

2. Launch the executable file.l If you downloaded the product from the SolarWinds website,navigate to your download location, and then launch theexecutable file. You may need to run the executable file as anadministrator.

l If you received physical media, browse to the executable file, andthen launch the executable file. You may need to run theexecutable file as an administrator.

3. If you are prompted to install requirements, click Install, and thencomplete the installation, including a reboot, if required.Notes:

l Downloading and installing the Microsoft .NET Framework 4.0 maytake more than 20 minutes, depending on your existing systemconfiguration.

l If a reboot is required, after restart, click Install to resume theinstallation, and then click Next on the Welcome window.

4. To use the Orion Improvement Program to send anonymous data aboutyour product usage to SolarWinds, click Yes, send data.

5. Review the Welcome text, and then click Next.6. Select your preferred language, and then click Next.

Note: This selection cannot be changed later.

29

7. If the Setup Wizard detects that Microsoft Internet Information Services(IIS) is not installed, select Suspend installation to manually install IIS,click Finish, quit setup, and then install IIS.Note: The Web Console requires that Microsoft IIS is installed on theVoIP and Network Quality Manager server. If you do not install IIS at thispoint, you must install IIS later, and then configure a website for the WebConsole to use. For more information about IIS, see Enabling IIS.

8. Accept the license agreement, and then click Next.9. Click Next to confirm the default Destination Location.

To install to a destination folder other than the default given, clickBrowse, select an installation folder, and then click OK.

10. Read the Start Copying Files information, and if you are satisfied withyour settings, click Next to continue.

11. Click Finish to close the Installation Wizard.12. Select one of the available licensing options.

l To buy a license, click Buy Now.If this is a new installation ofSolarWinds VoIP and Network Quality Manager, click EnterLicensing Information, and then complete the license registrationprocess. For more information about software license keys, seeSoftware License Key in the VoIP and Network Quality ManagerAdministrator Guide.Click Continue when the license is successfully installed.

l If you want to evaluate VNQM, click Continue Evaluation.13. The Orion Configuration Wizard launches automatically. Click Next on

the Welcome screen to continue the basic configuration.Note: If the Configuration Wizard does not start automatically, starttheConfiguration Wizard in the SolarWinds Orion folder.

30

Installing SolarWinds VNQM

http://www.solarwinds.com/documentation/kbloader.aspx?kb=1309


14. Define your SQL server settings, and then click Next.

a. Select or fill in your SQL Server instance.b. Define the authentication used on the server:

l If you want to use your Windows credentials, select UseWindows Authentication.

l If you want to use your SQL server credentials, select UseSQL Server Authentication.

Note: The selected instance must support mixed mode or SQLauthentication with strong passwords. For more information, seethe page on the Microsoft Developer Network about authenticationmodes.

15. Specify your SQL database settings:l If you are creating a new database, select Create a new database,provide a name for the new database, and then click Next.

l If you are using an existing database, select Use an existingdatabase, type or select the database name, and then click Next.Note: If you are using an existing database or SQL account, theuser account must be a member of the db_owner database role.

16. Specify the SQL server account for Orion:

a. If you want the polling engine and web console to use a new SQLaccount for accessing the database, select Create a new account,provide a new account name and confirmed password, and thenclick Next.Note: If you are creating a new SQL account for use with VoIP andNetwork Quality Manager, the account must be a member of thedb_securityadmin database role.

b. If you want the polling engine and web console to use an existingSQL account for accessing the database, select the existingaccount, provide the appropriate password, and then click Next.

31

http://msdn.microsoft.com/ms143705.aspx

http://msdn.microsoft.com/ms143705.aspx

17. Specify the website settings:

a. Provide the IP address of the server used for the web console.Note: Consider retaining the default IP address setting of AllUnassigned, unless your environment requires the designation ofa specific IP address for your Web Console.

b. Specify both the port through which you want to access the webconsole, and the volume and folder in which you want to install theweb console files, and then click Next.Note: If you specify any port other than 8787, the default port forevaluations, you must include that port in the URL used to accessthe web console. For example, if you specify an IP address of192.0.2.1 and port 8080, the URL used to access the web consoleis http://192.0.2.1:8080.

c. If you are prompted to create a new directory, click Yes.

d. If you are prompted to create a new website, click Yes.Note: Choosing to overwrite an existing website does not result inthe deletion of any previously applied custom NPM websitesettings.

18. Confirm that the services you want to install are selected on the ServiceSettings window, and then click Next.

19. If you are prompted to disable the SNMP Trap Service, click Yes.20. Review the final configuration items, and then click Next.21. Click Finish on the Completing the Orion Configuration Wizard dialog.

The Orion Web Console is launched automatically.

32

Installing SolarWinds VNQM


Additional Polling Engine and Web ConsoleInstalling additional pollers and Web Consoles helps you extend yourSolarWinds VoIP and Network Quality Manager implementation. You caninstall additional polling engines to aid you in load balancing and configureadditional websites to ensure redundant access through more than one webserver. By sharing the same database, you can also share a unified userinterface, making the addition of polling engines transparent to your staff.The additional polling engines and Web Consoles are available as separateinstallers from your main installation.These components are licensed and purchased separately from your mainVoIP and Network Quality Manager. For more information about purchasinglicenses, contact your sales representative ([email protected]) orcustomer service.

Installing an Additional Polling EngineDownload the special installation package for the VoIP and Network QualityManager additional polling engines to the server where you want to install theadditional polling engine:SolarWinds-Orion-VNQM-vx.y.z-Poller.exe

where x is the major release number, y is the minor release number, and z isthe point release number.Note: After completing the following procedure, VoIP and Network QualityManager polling engines emulate the same behavior as NPM additionalpolling engines. They monitor only applications on nodes associated with theVoIP and Network Quality Manager additional polling engine.To install the additional polling engine:

1. Log on with a Windows administrator account to the server where youwant to install the additional polling engine.

2. Run the installer for the VoIP and Network Quality Manager Poller.

33

mailto:[email protected]

3. If you are prompted to install requirements, click Install, and thencomplete the installation, including a reboot, if required.Notes:


l If a reboot is required, click Install after the restart to resume theinstallation, and then click Next on the Welcome window.

4. If you want to use the Orion Improvement Program to send anonymousdata about your product usage to SolarWinds, click Yes, send data.

5. Type your VoIP and Network Quality Manager server host name or IPaddress, the administrator user name, and the administrator password.Click Next to verify that you are installing the correct version of thepolling engine for your server.

6. Review the Welcome page, and then click Next.7. Accept the license agreement, and then click Next.8. Choose a destination location, or accept the default location, and then

click Next.9. Click Next to start copying files.10. Click Finish to complete the Installation Wizard.11. Click Enter Licensing Information to enter your license, or click

Continue Evaluation.12. Review the Configuration Wizard Welcome page, and then click Next.13. Configure the database for your environment by selecting the appropriate

SQL Server database and Authentication information, and then clickNext.

14. Configure the database by selecting Use an existing database, andthen selecting the name of the SQL Server database for the VoIP andNetwork Quality Manager server, and then click Next.

15. Select whether to Create a new account, or Use an existing account,enter the account information, and then click Next.

34

Installing an Additional Polling Engine


16. If the Website Settings page is displayed, configure the IP Address,Port, andWebsite Root Directory as appropriate, select whether youwant to enable automatic login, and then click Next.

17. Ensure that all the services displayed in the Service Settings page areselected, including the Job Engine Plugin, and then click Next.

18. Review the Configuration Wizard Summary page, and then click Next.19. Click Finish to complete the Configuration Wizard.

You can assign nodes to the polling engines by selecting the polling engineyou want in the Add Node wizard.You can also perform poller load balancing using Node Management to assignnodes to polling engines.To assign nodes to polling engines:

1. Log on to the web console as a user with node management rights.2. Click Home.3. In the All Nodes resource on the Orion Summary Home view, click

Manage Nodes.4. Select the nodes you want to change, and then click More Actions >

Change Polling Engine.5. Select the new polling engine, and then click Submit.

Installing an Additional Web ConsoleDownload the special installation package for VoIP and Network QualityManager additional web consoles to the server where you want to install theadditional web console:SolarWinds-Orion-VNQM-vx.y.z-WebOnly.exe

where x is the major release number, y is the minor release number, and z isthe point release number.TCP port 17777 must be open on both the VoIP and Network Quality Managerserver and the website.Ensure you schedule an appropriate maintenance window in which to installthe additional Web Console.

35

To install the additional Web Console:

1. Log on to your current VoIP and Network Quality Manager additionalWeb Console server with a Windows administrator account.

2. Run the VoIP and Network Quality Manager installer.3. If you are prompted to install requirements, click Install, and then

complete the installation, including a reboot, if required.Notes:


l If a reboot is required, click Install after the restart to resume theinstallation, and then click Next on the Welcome window.

4. If you want to use the Orion Improvement Program to send anonymousdata about your product usage to SolarWinds, click Yes, send data.

5. Type your VoIP and Network Quality Manager server host name or IPaddress, the administrator user name, and the administrator password.Click Next to verify that you are installing the correct version of thepolling engine for your server.

6. Review the Welcome page, and then click Next.7. Accept the license agreement, and then click Next.8. Choose a destination location, or accept the default location, and then

click Next.9. Click Next to start copying files.10. Click Finish to complete the Installation Wizard.11. Review the Configuration Wizard Welcome window, and then click Next.12. Specify the appropriate information on the Database Settings window,

and then click Next.13. Specify the appropriate database to use, and then click Next. Ensure you

have stopped your polling engines before continuing.14. Specify the appropriate database account on the Database Account

window, and then click Next.

36

Installing an Additional Web Console


15. Select the IP address, port, and website root directory on the WebsiteSettings window, and then click Next.

16. Review the configuration summary, and then click Next.17. Click Finish to complete the Configuration Wizard.

Upgrading VNQMUpgrading VNQM does not require you to uninstall your current installation.However, you must follow certain upgrade paths according to the version youare upgrading VNQM from.Until VoIP and Network Quality Manager 4.0, the application required theinstallation of SolarWinds Network Performance Monitor. Since version 4.0,VNQM has been a stand-alone application which can but does not have to beinstalled together with NPM.For more details about upgrading VNQM, see the KB article "Compatibility ofSolarWinds Orion Products for Installation and Upgrade."Notes:

l Back up your database before you start the upgrade to ensure none ofyour data is lost during the upgrade.

l None of your historical data or customized settings will be lost in theprocess.

l If you have a large amount of VoIP and CallManager data, the upgrademay take 30 minutes to an hour to complete.

To upgrade VoIP and Network Quality Manager:

1. Follow the appropriate upgrade path.2. Install VoIP and Network Quality Manager normally. For more information

about installing VNQM, see Installing VoIP and Network Quality Managerin the VoIP and Network Quality Manager Administrator Guide.

If you use IP SLA Manager 3.5.1:

1. Upgrade NPM to version 10.5.2. Upgrade to VoIP and Network Quality Manager 4.1 and then upgrade to

VNQM 4.2.2.

37

http://knowledgebase.solarwinds.com/kb/questions/1888/Compatibility+of+SolarWinds+Orion+Products+for+Installation+and+Upgrade#ipslam

http://knowledgebase.solarwinds.com/kb/questions/1888/Compatibility+of+SolarWinds+Orion+Products+for+Installation+and+Upgrade#ipslam

If you use VNQM 4.1 or above:

1. Upgrade to VoIP and Network Quality Manager 4.2.2.

Uninstalling VNQMThe uninstallation procedure for VNQM consists of removing the SolarWindsVoIP and Network Quality Manager application in the Control Panel. However,configuration files, database entries and registry keys are not removed by thisprocedure.To completely uninstall VNQM, contact SolarWinds Technical Support forassistance.

38

Uninstalling VNQM

Configuring VoIP and NetworkQuality ManagerVNQMmonitors your IP SLA operations and VoIP infrastructure. ConfiguringVNQMmeans adding your devices to VNQM, defining what you are going tomonitor, and how often you want to poll data from your devices.You can configure VNQM in the Orion Web Console.To start VNQM:

1. Log on to your VoIP and Network Quality Manager server.2. Start the Orion Web Console in the Orion program folder.3. Click the VoIP and Network Quality tab.

After establishing your basic VoIP infrastructure and adding IP SLA operations,you can change your settings at any time to further customize VoIP andNetwork Quality Manager for your network. For example, you can add IP SLAdevices, designate paths, and configure polling options. VoIP and NetworkQuality Manager uses a wizard-based application to guide you through theprocess of configuring VoIP and Network Quality Manager for your network.The following sections provide detailed instructions for configuring the variousaspects of VoIP and Network Quality Manager for your network.

l IP SLA Management - configuring your IP SLA devices and IP SLAoperations

l VoIP Management - configuring your CallManagers, gateways, anddefining VoIP infrastructure

l VNQM Details - configuring database, polling and monitoring settings

39

Configuring VoIP and Network Quality Manager

IP SLA ManagementBy using VNQM you can monitor IP SLA operations that are set on yourdevices. Designing a tailored set of IP SLA operations for monitoring yourdevices is a complex task.For more information about IP SLA operations and quality of service metrics inVNQM, see Understanding Quality of Service and IP SLAs in the VoIP andNetwork Quality Manager Administrator Guide.After you have designed a set of IP SLA operations to be used for monitoringyour devices, complete the following steps:

1. Configure your devices for IP SLA operations. For more information, seeConfiguring Devices for IP SLA Operations in the VoIP and NetworkQuality Manager Administrator Guide.

2. Add devices that you want to monitor to your database. For moreinformation, see Adding Devices for Monitoring in the Web Console.

3. Add your devices as IP SLA nodes into VNQM. For more information,see Adding IP SLA nodes to VoIP and Network Quality Manager in theVoIP and Network Quality Manager Administrator Guide.

4. Define IP SLA operations to be monitored by VNQM. For moreinformation, see Adding IP SLA Operations in the VoIP and NetworkQuality Manager Administrator Guide.

Related tasks:

l Editing IP SLA operationsl Deleting IP SLA operations

Understanding Quality of Service and IP SLAsIP Service Level Agreements (IP SLAs) are a diagnostic method developed byCisco that generates and analyzes traffic between Cisco IOS devices on yournetwork. By using VoIP and Network Quality Manager to implement IP SLAoperations between your network devices, you can acquire real-time andhistorical statistics that give you accurate Quality of Service (QoS)measurements over designated network paths between a source device and atarget device.

40

http://www.solarwinds.com/documentation/helploader.aspx?topic=OrionCoreAGAddingDevicesWebConsole.htm

For a better understanding of individual quality of service and IP SLAs, it isnecessary to understand the following concepts:Source

A device that creates and inserts IP SLA packets into the network. Thesource is where all IP SLA operation tests are initiated.

TargetThe ultimate destination of the packets created and sent by the source.

OperationThe type of test being performed on the network.

IP SLA Operations in VNQM

The following operations are supported by VoIP and Network Quality Manager.DHCP

Dynamic Host Configuration Protocol (DHCP) IP SLA operationsmeasure the response time taken to discover a DHCP server, and thenobtain a leased IP address from it.

DNSDomain Name Server (DNS) IP SLA operations measure the differencein time from when a DNS request is sent and when the reply is received.

FTPFile Transfer Protocol (FTP) IP SLA operations measure the responsetime between a Cisco device and an FTP server to retrieve a file.

HTTPHypertext Transfer Protocol (HTTP) IP SLA operations measuredistributed web services response times.

ICMP EchoInternet Control Message Protocol (ICMP) Echo IP SLA operationsmeasure round trip time between nodes on the network.

ICMP Path EchoICMP Echo IP SLA operations measure round trip time hop-by-hopbetween nodes on the network.

41

IP SLA Operations in VNQM


ICMP Path JitterICMP Path Jitter IP SLA operations measure WAN quality by testingconnection times hop-by-hop between two devices.

TCP ConnectTransmission Control Protocol (TCP) Connect IP SLA operationsmeasure WAN quality by testing connection times between two devicesusing a specific port.

UDP EchoUser Datagram Protocol (UDP) Echo IP SLA operations measure roundtrip time between nodes on the network.

UDP JitterUDP Jitter IP SLA operations measure WAN quality by testingconnection times between two devices using a specific port number.

VoIP UDP JitterVoice over Internet Protocol (VoIP) UDP Jitter IP SLA operationsmeasure call path metrics on the VoIP network.

Quality of Service MetricsThe quality of service in VNQM is measured by using the following metrics:

l Latencyl Jitterl Packet Lossl Mean Opinion Score

Latency

With respect to VoIP, latency is a measure of the difference in time betweenwhen one caller speaks and when the other caller hears what the first has said.Excessive network latency can cause noticeable gaps and synchronizationloss in transmitted conversations, particularly when VoIP is used with othertypes of data, as in a video conference. If these gaps become large enough,callers may find that they will inadvertently interrupt each other whileconversing.

42

IP SLA operations measure latency by sequentially applying four different timestamps to a single test packet in the following way:

1. Time stamp T1 is applied to a test packet as it leaves the source router.2. Time stamp T2 is applied as the test packet arrives at the target router.3. Time stamp T3 is applied as the test packet leaves the target router to

return to the source.4. Time stamp T4 is applied when the test packet returns to the source.

IP SLA operations provide four separate measures of latency by computingdifferences among the four time stamps in the following way.

Latency measure Calculation

Round trip time T4 – T1

Source-to-target latency T2 – T1

Target processing latency T3 – T2

Target-to-source latency T4 – T3

Note: Latency is computed for both source-to-target and target-to-sourcedirections to account for asynchronous network behavior, providing a moredetailed picture of the overall network latency.VoIP and Network Quality Manager calculates latency in the following way:if (rttMonLatestJitterOperNumOfRTT <> 0)delay = (convert rttMonLatestJitterOperRTTSum tomilli/microseconds depending on rttMonEchoAdminPrecision) /rttMonLatestJitterOperNumOfRTTelsedelay = 0if (micro/milli second convert value ofrttMonLatestJitterOperOWSumSD andrttMonLatestJitterOperNumOfOW has value andrttMonLatestJitterOperNumOfOW <> 0)delaySD = micro/milli second convert value ofrttMonLatestJitterOperOWSumSD / rttMonLatestJitterOperNumOfOWelse

43

Latency


if (micro/milli second convert value ofrttMonLatestJitterOperOWSumDS andrttMonLatestJitterOperNumOfOW has value andrttMonLatestJitterOperNumOfOW <> 0)delayDS = micro/milli second convert value ofrttMonLatestJitterOperOWSumDS / rttMonLatestJitterOperNumOfOWelsedelaySD & delayDS = null

rttMonLatestJitterOperNumOfRTT 1.3.6.1.4.1.9.9.42.1.5.2.1.1

rttMonLatestJitterOperRTTSum 1.3.6.1.4.1.9.9.42.1.5.2.1.2

rttMonEchoAdminPrecision 1.3.6.1.4.1.9.9.42.1.2.2.1.37

rttMonLatestJitterOperOWSumSD 1.3.6.1.4.1.9.9.42.1.5.2.1.33

rttMonLatestJitterOperNumOfOW 1.3.6.1.4.1.9.9.42.1.5.2.1.41

rttMonLatestJitterOperOWSumDS 1.3.6.1.4.1.9.9.42.1.5.2.1.37

Jitter

Jitter is a measure of the variation in network latency that results in a loss ofsynchronization over time. In VoIP phone calls, users experience jitter asdistracting noise, clicks, and pops. To ensure acceptable quality of service,network jitter should be located, isolated, and addressed. By using VoIP andNetwork Quality Manager you can identify areas of your network that may beexperiencing synchronization difficulties, and then you can take the necessaryaction to ensure maximum quality of service on your VoIP network.VoIP and Network Quality Manager requires you to select a jitter codec toproperly configure IP SLAs for your VoIP network. Codecs compute jitter byspecifying that IP SLA operations send a number of packets (n), each with aspecific size (s), at a set interval (i) between packets, at a determinedfrequency (f), as shown in the following table.

44

CodecIP SLA operationfrequency (f)

Defaultnumber ofpackets (n)

Defaultpacketsize (s)

Defaultintervalbetweenpackets (i)

G.711a Set on eachoperation as thenetwork test interval

1000 160 + 12RTP bytes

20 ms

G.711u 1000 160 + 12RTP bytes

20 ms

G.729a 1000 20 + 12RTP bytes

20 ms

For more information about configurable settings within VoIP and NetworkQuality Manager, see Configuring VoIP and Network Quality Manager Settingsin the VoIP and Network Quality Manager Administrator Guide.Note: Based on the Cisco IP SLA operations used by VoIP and NetworkQuality Manager, jitter codecs G.711a and G.711u can achieve a peak MOS of4.34. On the same basis, jitter codec G.729a can achieve a peak MOS of 4.06.VoIP and Network Quality Manager calculates jitter in the following way:jitterSD = (rttMonLatestJitterOperSumOfPositivesSD +rttMonLatestJitterOperSumOfNegativesSD ) /(rttMonLatestJitterOperNumOfPositivesSD +rttMonLatestJitterOperNumOfNegativesSD)

jitterDS = (rttMonLatestJitterOperSumOfPositivesDS +rttMonLatestJitterOperSumOfNegativesDS) /(rttMonLatestJitterOperNumOfPositivesDS +rttMonLatestJitterOperNumOfNegativesDS)

Jitter = (rttMonLatestJitterOperSumOfPositivesSD +rttMonLatestJitterOperSumOfNegativesSD +rttMonLatestJitterOperSumOfPositivesDS +rttMonLatestJitterOperSumOfNegativesDS) /(rttMonLatestJitterOperNumOfPositivesSD +rttMonLatestJitterOperNumOfNegativesSD +rttMonLatestJitterOperNumOfPositivesDS +rttMonLatestJitterOperNumOfNegativesDS)

45

Jitter


rttMonLatestJitterOperSumOfPositivesSD 1.3.6.1.4.1.9.9.42.1.5.2.1.9

rttMonLatestJitterOperSumOfNegativesSD 1.3.6.1.4.1.9.9.42.1.5.2.1.14

rttMonLatestJitterOperNumOfPositivesSD 1.3.6.1.4.1.9.9.42.1.5.2.1.8

rttMonLatestJitterOperNumOfNegativesSD 1.3.6.1.4.1.9.9.42.1.5.2.1.13

rttMonLatestJitterOperSumOfPositivesDS 1.3.6.1.4.1.9.9.42.1.5.2.1.19

rttMonLatestJitterOperSumOfNegativesDS 1.3.6.1.4.1.9.9.42.1.5.2.1.24

rttMonLatestJitterOperNumOfPositivesDS 1.3.6.1.4.1.9.9.42.1.5.2.1.18

rttMonLatestJitterOperNumOfNegativesDS 1.3.6.1.4.1.9.9.42.1.5.2.1.23

Note: VoIP and Network Quality Manager reads one jitter value at a giventime, which is calculated based on the SNMP poll. This is an average value.The CLI command is not necessarily executed at the same moment. For thisreason, the output of the current CLI commands is not the same as the valuesdisplayed in the VNQM charts or in the historical data.

Packet Loss

Packet loss is a quantitative measure of information loss over a given networkconnection. Though packet loss is inevitable in any network environment, thegoal is always to identify where packets are lost in transmission so you can actto minimize information loss and maintain high QoS for your services.VoIP and Network Quality Manager calculates packet loss in the followingway:if (rttMonLatestJitterOperPacketLossSD +rttMonLatestJitterOperPacketLossDS +rttMonLatestJitterOperPacketMIA <> 0)packetLoss =

46

((rttMonLatestJitterOperPacketLossSD +rttMonLatestJitterOperPacketLossDS +rttMonLatestJitterOperPacketMIA) * 100) /(rttMonLatestJitterOperPacketLossSD +rttMonLatestJitterOperPacketLossDS +rttMonLatestJitterOperPacketMIA +rttMonLatestJitterOperPacketLateArrival +rttMonLatestJitterOperPacketOutOfSequence +rttMonLatestJitterOperNumOfRTT)elsepacketLoss = 0if (rttMonLatestJitterOperPacketLossSD +(rttMonLatestJitterOperPacketMIA/2) +((rttMonLatestJitterOperPacketLateArrival +rttMonLatestJitterOperPacketOutOfSequence +rttMonLatestJitterOperNumOfRTT)/2) <> 0)packetLossSD = (rttMonLatestJitterOperPacketLossSD +(rttMonLatestJitterOperPacketMIA/2) +((rttMonLatestJitterOperPacketLateArrival +rttMonLatestJitterOperPacketOutOfSequence +rttMonLatestJitterOperNumOfRTT)/2)) * 100 /(rttMonLatestJitterOperPacketLossSD +(rttMonLatestJitterOperPacketMIA/2))elsepacketLossSD = 0if (rttMonLatestJitterOperPacketLossDS +(rttMonLatestJitterOperPacketMIA/2) +((rttMonLatestJitterOperPacketLateArrival +rttMonLatestJitterOperPacketOutOfSequence +rttMonLatestJitterOperNumOfRTT)/2) <> 0)packetLossDS = (rttMonLatestJitterOperPacketLossDS +(rttMonLatestJitterOperPacketMIA/2) +((rttMonLatestJitterOperPacketLateArrival +rttMonLatestJitterOperPacketOutOfSequence +rttMonLatestJitterOperNumOfRTT)/2)) * 100 /(rttMonLatestJitterOperPacketLossDS +(rttMonLatestJitterOperPacketMIA/2))elsepacketLossDS = 0

rttMonLatestJitterOperPacketLossSD 1.3.6.1.4.1.9.9.42.1.5.2.1.26

47

Packet Loss


rttMonLatestJitterOperPacketLossDS 1.3.6.1.4.1.9.9.42.1.5.2.1.27

rttMonLatestJitterOperPacketMIA 1.3.6.1.4.1.9.9.42.1.5.2.1.29

rttMonLatestJitterOperPacketLateArrival 1.3.6.1.4.1.9.9.42.1.5.2.1.30

rttMonLatestJitterOperPacketOutOfSequence 1.3.6.1.4.1.9.9.42.1.5.2.1.28

rttMonLatestJitterOperNumOfRTT 1.3.6.1.4.1.9.9.42.1.5.2.1.1

Mean Opinion Score (MOS)

MOS is an industry standard measure of call quality expressed on a scale ofincreasing perceived quality, from one to five. VoIP and Network QualityManager reports MOS as computed by a standard InternationalTelecommunications Union (ITU) algorithm involving the codec for your VoIPnetwork and values of latency, jitter, packet loss, and MOS advantage factor.Jitter, latency, and packet loss are variable quantities that are measured byVoIP and Network Quality Manager in real time. Generally, MOS reflects callquality as shown in the following table.

Call quality MOS

Very satisfied 4.3-5.0

Satisfied 4.0-4.3

Some users satisfied 3.6-4.0

Many users dissatisfied 3.1-3.6

Nearly all users dissatisfied 2.6-3.1

Not recommended 1.0-2.6

Both the MOS advantage factor and the codec algorithm are selected for yourspecific network on the VoIP and Network Quality Manager Settings page. Thefollowing table provides guidance for how the advantage factor is determinedfor your application.

48

Communication system typeexamples

Maximum advantage factorvalue

Conventional wired network 0

Wireless network within a building 5

Outdoor wireless network (cellularphones)

10

Remote communications by satellite 20

For more information about MOS calculations, see the ITU-T RecommendationG.107.For more information about codec algorithms, see Jitter in the VoIP andNetwork Quality Manager Administrator Guide.For more information about VoIP and Network Quality Manager settings, seeConfiguring VoIP and Network Quality Manager Settings in the VoIP andNetwork Quality Manager Administrator Guide.

Understanding Polling Intervals for IP SLA OperationsVNQM polls IP SLA operations at a certain frequency. This frequency isdefined by polling intervals set in your database.VoIP and Network Quality Managerdivides all monitored operations on a nodeinto groups based on their polling frequency. The polling frequency is dividedby two for the polling interval, which occurs twice as fast as the pollingfrequency.The polling interval groups are the following:

l Polling interval <= 1minl 1min < Polling interval <= 3minl 3min < Polling interval <= 6minl 6min < Polling interval

For any given group of operations, VoIP and Network Quality Manager findsthe operation with the most frequent polling interval in the group and uses thatinterval to poll the entire group. Consider the following example:

49

Understanding Polling Intervals for IP SLA Operations


Five operations are being monitored on a single node. These operations havethe following polling frequencies:

l Operation A: 1 minutel Operation B: 2 minutesl Operation C: 4 minutesl Operation D: 5 minutesl Operation E: 14 minutes

Operations A and B would be put in the same group because their pollingintervals are both <= 1 minute. The polling interval of Operation A is 30seconds, and the polling interval of operation B is 1 minute. VoIP and NetworkQuality Manager will poll both of these operations simultaneously every 30seconds because the more frequent of the two operations is 1 minute, andVNQM polls twice that frequency.Operations C and D are in a different group because their polling intervals are2 minutes and 2.5 minutes, which are <= 3 minutes and greater than 1 minute.VNQM will poll both of these operations simultaneously every 2 minutesbecause the more frequent of the two operations is 4 minutes, and VNQM pollstwice that frequency.Operation E is in a different group because its polling interval is 7 minutes.Notes:

l If you want to change a polling interval for an operation, you have to do itin your database.

l VNQM does not support the polling of several hundred operations at 5second polling interval.

To check the currently set polling interval in VNQM:

1. Go to VoIP & Network Quality settings.2. Click Edit or delete operations.3. On the Manage IP SLA Operations page, select the appropriate

operation, and then click Edit. You can check the polling interval in theread-only Frequency field.

50

Designating PathsFor some of the SLA operations used by VoIP and Network Quality Manager,performance statistics are collected by sending traffic over paths between sitesthat you define. These network paths are defined by your IP routing protocol.Because large networks can quickly become complicated, VoIP and NetworkQuality Manager provides an easy-to-use interface for selecting paths formonitoring. When configuring IP SLA operations, VoIP and Network QualityManager offers the following options for establishing monitoring:Simple

A simple path contains one source node and only one destination node.The path can be tested bidirectionally.

Fully MeshedA Fully Meshed path configuration connects every node you define overdistinct call paths to every other node selected.

Hub and SpokeA Hub and Spoke call path configuration allows you to designate specificnodes as hubs. Each hub is then connected to all other nodes, with pathsrepresenting spokes.

CustomThe Custom call path configuration option allows you to define your ownpaths. All defined nodes are listed under this option, and expanding eachnode displays a list of all other nodes. You can use the check boxes todefine paths to best suit your monitoring requirements.

Understanding the Impact IP SLA Operations Have on YourNetworkWhen configured properly, IP SLA operations have a minimal impact on youroverall network health. However, problems can arise when configurationsforce operations to be tested too frequently, or when too many overlappingoperations are being performed across similar paths.Most problems occur when using IP SLA operations on a fully meshednetwork. For example, in a fully meshed network with seven devices, a simpleICMP Echo operation would require 42 operations to test each link in eachdirection. The number of links is calculated in the following way:Hub-and-Spoke Links = N - 1

51

Designating Paths


Full Mesh Links = N(N - 1)/2N is the number of devices on the network. Therefore, the number of links in aseven device fully meshed network would be 7(7 - 1)/2, or 7(6)/2, or 21.To test each link bi-directionally, twice as many operations are needed. Thenumber of bi-directional links is found using the following calculation:Hub-and-Spoke Links = (N - 1)2Full Mesh Links = N(N - 1)Therefore the total number of operations for the seven site hub-and-spoke andseven site full mesh are as follows:Hub-and-Spoke Operations = (7 - 1)2 = 12Full Mesh Operations = 7(7 - 1) = 42Adding three more operations to that network would increase the operationsfrom 36 to 144 (36 x 4). 144 operations will not have a significant impact on thissmall network.When looking at a typical mid-sized network with 30 devices, the number ofoperations begins to quickly increase, according to the following calculation:Links = 30 x 29/2 = 435Total Operations = 435 x 2 x 4 = 3480The number of operations grows at an exponential rate. Here is the samearithmetic for a 180 device network:Links = 180 x 179/2 = 16,110Total Operations = 16,110 x 2 x 4 = 128,800

Dangers of Overusing IP SLA Operations

By continuing to add operations and devices to any network, especially in afully meshed environment, overall network performance will start to degrade. Inaddition to burdening the network with test packets, a large number of IP SLAoperations can cause the following effects:

l Several thousand test results stored every five minutes can create a largedatabase affecting other services on the database.

l Chances are that most of the historical results will never be examineddue to the large number of results to filter.

52

l Adding thousands of IP SLA operations could add a significant burden tothe SNMP poller.

Strategies for the Proper Use of IP SLA Operations

IP SLA operations can negatively affect network performance when they areimplemented improperly. To avoid affecting the performance of your network,use the following strategies:Keep Local Tests Local

Not all test types are used to test WAN services (DHCP is one example).A large network may have several distributed DHCP servers. If each sitehas a local DHCP server, users at that site would receive IP addressesfrom the local server if it is available. For 40 sites you could accomplishDHCP testing by deploying an operation from the local switch or router ofeach site to the local DHCP server of the site. This creates only 40 testswith 40 results to poll and store every five minutes. You might also addtests for some secondary DHCP servers and have around 50 tests intotal. If you added all DHCP testing to all sites to all servers you wouldhave approximately 402, or 1600 tests. Most of these tests are for DHCPrequests to remote sites, which will never actually be what the usersrequest when obtaining an IP address.

Test Paths Only for Supported TrafficFor this example, UDP jitter, a common IP SLA test, will be used. On anMPLS 40-site network, the UDP jitter operation is implemented betweenfive sites that use UDP to deliver video conferencing. Because videoconferencing is sensitive to network jitter and delay, implementing jitteroperations between these sites is recommended. Using the formula for afull mesh network such as an MPLS network, we need to set up tenoperations. However, if full mesh is deployed to test the links between allsites, there would be 40 x 39/2=780 tests, and only 1.3% of the testswould be for valid video paths. Therefore, a custom deployment of theoperations is the recommended option in this scenario.

Consider Decreasing the Test Frequency When PossibleDecreasing or increasing the test frequency has a significant impact onthe network load. For example, decreasing the test frequency from 300seconds to 360 seconds will lessen the test impact on the source deviceand network by ten percent. Increasing the frequency to 150 seconds willincrease the load by one hundred percent.

53

Strategies for the Proper Use of IP SLA Operations


Avoid Overlapping TestsIt is possible to deploy a DNS test to an internal DNS server, an HTTPtest to an intranet page, a ping test to the HTTP server, and a TCPconnect to the HTTP server from a local switch. While there are fourindividual operations testing four services, there are now three redundanttests overlapping each other. The HTTP operation performs thefollowing:

1. Resolves the URL to an IP address using the DNS server.2. Performs a TCP port 80 request to the HTTP server.3. Requests the HTTP and detects a successful page load.4. Records the DNS resolve time, TCP open time, and page

load time.Using the HTTP test, the other three tests can be eliminatedbecause they yield the same results.

To prevent overloading the network with IP SLA operations, VoIP and NetworkQuality Manager limits the number of operations that can be created at onetime to 306, or 18 nodes in a fully meshed environment.For more detailed information about IP SLA operation configurations anddeployment strategies, see the New to Networking Volume 2: The Basics ofCisco IP SLA technical reference.

Configuring Devices for IP SLA OperationsCisco IP Service Level Agreements (IP SLAs) are the primary means by whichVoIP and Network Quality Manager acquires information about theperformance of your network. The process of configuring a device for IP SLAcan involve numerous command line operations on each router. To help youeasily configure your devices, VoIP and Network Quality Manager canautomatically add IP SLA operations to your network devices and startmonitoring those operations immediately.

Configuring devices for ICMP echo path operations

Devices where you want to monitor ICMP echo path operations must bemanually configured. VNQM reads hop results from history data. Therefore, theoperation needs to be configured to save data to the history table. To enable history data support, configure the following items:

54

http://www.solarwinds.com/documentation/ref/New to Networking vol2.pdf

http://www.solarwinds.com/documentation/ref/New to Networking vol2.pdf

l History filter (all)l Number of buckets kept (min value: 1)l Number of samples kept (max value: 30)l Lives of history kept (min value: 1)

To configure history data support, follow the directions based on your IOSversion on the following Cisco links:

l Configuring an ICMP Path Echo Operation with Optional Parameters onthe Source Device

l Configuring and Scheduling an ICMP Path Echo Operation with OptionalParameters on the Source Device

l Setting History Characteristics

To check history configuration, use one of the following commands (dependingon your IOS version):sh ip sla history fullsh ip sla monitor history fullsh rtr history full

When history is properly configured, the output resembles the following:Entry number: 55Life index: 1Bucket index: 4Sample index: 1Sample time: *08:08:19.278 UTC Tue Aug 24 1993RTT (milliseconds): 5Response return code: OKTarget address: 10.199.254.5

Life index: 1Bucket index: 4Sample index: 2Sample time: *08:08:19.286 UTC Tue Aug 24 1993RTT (milliseconds): 1Response return code: OKTarget address: 10.199.254.2

55

Configuring devices for ICMP echo path operations

http://www.cisco.com/en/US/docs/ios-xml/ios/ipsla/configuration/12-4t/Configuring_Cisco_IOS_IP_SLAs_ICMP_Path_Echo_Operations.html#GUID-C1F2537E-603A-4FD9-ADE6-2229E14A5758

http://www.cisco.com/en/US/docs/ios-xml/ios/ipsla/configuration/12-4t/Configuring_Cisco_IOS_IP_SLAs_ICMP_Path_Echo_Operations.html#GUID-C1F2537E-603A-4FD9-ADE6-2229E14A5758

http://www.cisco.com/en/US/docs/ios/12_4/ip_sla/configuration/guide/hspaecho.html#wp1056201

http://www.cisco.com/en/US/docs/ios/12_4/ip_sla/configuration/guide/hspaecho.html#wp1056201

http://www.cisco.com/en/US/docs/ios/12_2/configfun/configuration/guide/fcf017.html#wp1001189


Life index: 1Bucket index: 4Sample index: 3Sample time: *08:08:19.286 UTC Tue Aug 24 1993RTT (milliseconds): 1Response return code: OKTarget address: 10.199.2.3

Adding IP SLA Nodes to VoIP and Network Quality ManagerBefore you can start creating and monitoring IP SLA operations, you must addyour IP SLA-capable routers to VoIP and Network Quality Manager.For more information about the management information bases (MIBs)referenced by VNQM, see Appendix C: MIBs Maintained by VoIP and NetworkQuality Manager.Requirements

l Source devices must first be added to the database before you can addthem to VoIP and Network Quality Manager. For more information aboutadding nodes, see Adding Devices for Monitoring in the Web Console inthe SolarWinds Orion Core Administrator Guide.

l The devices must be Cisco devices and must support SNMP v2 or v3. Toconfirm that the Cisco IOS release for your device supports IP SLAoperations, visit the Cisco Feature Navigator, click Research Features,select Search by Feature, and then select IP SLAs - DHCP Operation.

Discovering IP SLA-Capable Nodes Automatically

If you want to add more nodes at once, complete the following procedure toautomatically discover and add nodes to VoIP and Network Quality Manager.To automatically discover and add nodes to VoIP and Network QualityManager:

1. Log on to your SolarWinds VoIP and Network Quality Manager serverusing an account with administrator privileges.

2. Click VoIP & Network Quality in the Modules menu bar, and then clickVoIP & Quality Settings at the top right of the view.

3. Click Automatically discover IP SLA capable nodes.4. Click Start IP SLA Discovery.

56


http://tools.cisco.com/ITDIT/CFN/jsp/index.jsp

5. After the discovery has finished, click No, I want to exit this wizard, andthen click Next.

Adding IP SLA-Capable Nodes Manually

If you want to add individual nodes, complete the following procedure.To manually add nodes to VoIP and Network Quality Manager:



3. Click Manually Add Nodes to VoIP and Network Quality Manager.4. Select the nodes you want to add to VoIP and Network Quality Manager,

and then click Add Nodes.5. If you are prompted to enter credentials that include write privileges,

complete the following procedure:

a. Click Edit Node Details.

b. Click Edit Credentials.

6. If SNMP v2 is used, set the SNMP version and port number in theassociated fields, type the read/write community string, and then clickTest.

7. If SNMP v3 is used, select a saved credential set from the list, or type thecredentials in the provided fields, and then click Test.

8. Click Add Selected Nodes.

Configuring CLI Credentials

Some IP SLA operations require command line interface (CLI) logincredentials in order to configure the operations on your routers. Complete thefollowing procedure to add CLI credentials to your VoIP and Network QualityManager nodes.

57

Adding IP SLA-Capable Nodes Manually


To add CLI credentials to your VoIP and Network Quality Manager nodes:



3. Click Manage IP SLA Nodes.4. Select the node you want to edit, and then click Edit Node.5. Type the name of the credential set in the Credentials Name field to

create a new set.6. Type the user name and password in the associated fields.7. Type the enable level to use when logging in.

Note: The enable level must have privileges to execute configureterminal commands as well as be able to configure IP SLA operations.For information about configuring network devices, see yourmanufacturer’s documentation.

8. Type the password associated with the enable level to use when loggingin.

9. Expand Advanced, and then select the protocol, port number, andconnection timeout you want to use when connecting to your networkdevices.

10. Test the credentials, and then click Save when you have finished.

Adding IP SLA OperationsThe following sections detail how to add each type of operation SolarWindsVoIP and Network Quality Manager supports. Complete the associatedprocedures to start monitoring your IP SLA operations.You can either create new IP SLA operations and add them to your devices, oryou can add operations existing on your devices to VNQM.Notes:

l When SolarWinds VoIP and Network Quality Manager creates IP SLAoperations on your network devices, the numbers used to identify theoperations start at 40000. This way you can easily identify the operationscreated by VoIP and Network Quality Manager.

58

l If there are operations defined on your devices, it is stronglyrecommended that you to back up your device settings before you startadding new operations.

Adding DNS IP SLA Operations to Your Devices

Domain Name Server (DNS) IP SLA operations measure the difference in timefrom when a DNS request is sent and when the reply is received. Theseoperations ensure that your DNS servers are operational and are performingas expected.Note: You cannot add operations that have been previously created with VoIPand Network Quality Manager. If you have already created an operation withthe same operation number, you must manually remove the operation from thedevice.To add DNS IP SLA operations to your network devices:


2. Click the VoIP & Network Quality tab in the Modules menu bar, and thenclick VoIP & Quality Settings at the top right of the view.

3. Click Add new operations in the Manage IP SLA Operations section.4. Select Create new operations, and then click Next.5. Select DNS, and then click Next.6. Select the nodes you want to add to your new DNS operations, and then

click Next.Note: If you do not see your IP SLA routers in the list, you must add thedevices before you can continue. For more information, see AddingDevices for Monitoring in the Web Console in the SolarWinds NetworkPerformance Monitor Administrator Guide.

7. Type the IP Address of the DNS server and the hostname or IP addressto resolve, and then click Next.

8. Type the frequency for the operation to be performed.9. Define your warning, critical, and maximum threshold values in the

associated fields.

59

Adding DNS IP SLA Operations to Your Devices




10. If you want to assign a Virtual Routing and Forwarding (VRF) name forthis path, expand Advanced, and then type the VRF name.Note: VRFs only exist on provider edge routers (PE). A VRF is a routingand forwarding table instance, and you can have more than one VRF perPE. The VRF includes routes that are available to a certain set of sites. AVRF is named based on the VPNs it services and on the role of thecustomer edge (CE) router in the topology.

11. Click Next.12. If you want to rename operations or edit any other operation properties,

select the operations you want to modify, and then click Edit.13. Review the operations you want to create, and then click Create

Operations.Note: Depending on the number of operations that are being created,this process can take several minutes to complete.

14. Click Go to VNQM Home to finish the procedure and return to the VoIPand Network Quality Manager home page.

Adding FTP IP SLA Operations to Your Devices

File Transfer Protocol (FTP) IP SLA operations measure the response timebetween a device and an FTP server to retrieve a file. These operations run onCisco IP SLA capable devices, and they ensure that your FTP servers areoperational and performing as expected.Note: You cannot add operations that have been previously created with VoIPand Network Quality Manager. If you have already created an operation withthe same operation number, you must manually remove the operation from thedevice.To add FTP IP SLA operations to your network devices:



3. Click Add new operations in the Manage IP SLA Operations section.4. Select Create new operations, and then click Next.

60

5. Select FTP, and then click Next.6. Select the nodes you want to add to your new FTP operations, and then

click Next.Note: If you do not see your IP SLA routers in the list, you must add thedevices before you can continue. For more information, see AddingDevices for Monitoring in the Web Console in the SolarWinds NetworkPerformance Monitor Administrator Guide.

7. Type the URL of the FTP server, and then click Next.8. Type the frequency for the operation to be performed.9. Define your warning, critical, and maximum threshold values in the

associated fields.10. If you want to assign a type of service (ToS) or Virtual Routing and

Forwarding (VRF) name for this path, expand Advanced, and then typethe type of service number and VRF name in the appropriate fields.Notes:

l The ToS octet is a decimal value (0-255) that sets the precedencefor VoIP traffic monitored with Cisco IP SLA operations. The defaultToS value used by VoIP and Network Quality Manager is 184,corresponding to Expedited Forwarding (EF) per hop behavior(PHB) and a Differentiated Service Code Point (DSCP) value of 46.For more information about the ToS octet, see Setting TrafficPrecedence in the VoIP and Network Quality ManagerAdministrator Guide.

l VRFs only exist on provider edge routers (PE). A VRF is a routingand forwarding table instance, and you can have more than oneVRF per PE. The VRF includes routes that are available to acertain set of sites. A VRF is named based on the VPNs it servicesand on the role of the CE in the topology.


select the operations you want to modify, and then click Edit.

61

Adding FTP IP SLA Operations to Your Devices




13. Review the operations you want to create, and then click CreateOperations.Note: Depending on the number of operations that are being created,this process can take several minutes to complete.


Adding HTTP IP SLA Operations to Your Devices

Hypertext Transfer Protocol (HTTP) IP SLA operations measure distributedweb services response times. These operations ensure that your HTTPservers are operational and performing as expected.Note: You cannot add operations that have been previously created with VoIPand Network Quality Manager. If you have already created an operation withthe same operation number, you must manually remove the operation from thedevice.To add HTTP IP SLA operations to your network devices:


2. Click VoIP and Network Quality in the Modules menu bar, and thenclick VoIP & Quality Settings at the top right of the view.

3. Click Add new operations in the Manage IP SLA Operations section.4. Select Create new operations, and then click Next.5. Select HTTP, and then click Next.6. Select the nodes you want to add to your new HTTP operations, and

then click Next.Note: If you do not see your IP SLA routers in the list, you must add thedevices before you can continue. For more information, see AddingDevices for Monitoring in the Web Console in the SolarWinds NetworkPerformance Monitor Administrator Guide.

7. Type the URL of the HTTP server, and then click Next.8. Type the frequency for the operation to be performed.

62



9. Define your warning, critical, and maximum threshold values in theassociated fields.

10. If you want to assign a type of service (ToS) or Virtual Routing andForwarding (VRF) name for this path, expand Advanced, and then typethe type of service number and VRF name in the appropriate fields.

Notes:







Adding DHCP IP SLA Operations to Your Devices

Dynamic Host Configuration Protocol (DHCP) IP SLA operations measure thetime taken to discover a DHCP server and then obtain a leased IP addressfrom it. These operations ensure that your DHCP servers are operational andperforming as expected.

63

Adding DHCP IP SLA Operations to Your Devices


Note: You cannot add operations that have been previously created with VoIPand Network Quality Manager. If you have already created an operation withthe same operation number, you must manually remove the operation from thedevice.To add DHCP IP SLA operations to your network devices:



3. Click Add new operations in the Manage IP SLA Operations section.4. Select Create new operations, and then click Next.5. Select DHCP, and then click Next.6. Select the nodes you want to add to your new DHCP operations, and

then click Next.Note: If you do not see your IP SLA routers in the list, you must add thedevices before you can continue. For more information, see AddingDevices for Monitoring in the Web Console in the SolarWinds NetworkPerformance Monitor Administrator Guide.

7. Type the IP address of the DHCP server to be tested, and then clickNext.

8. Type the frequency for the operation to be performed.9. Define your warning, critical, and maximum threshold values in the

associated fields.10. Click Next.11. If you want to rename operations or edit any other operation properties,




64



Adding TCP Connect IP SLA Operations to Your Devices

Transmission Control Protocol (TCP) Connect IP SLA operations measureWAN quality by testing connection times between two devices using a specificport. These operations ensure that your WAN is operational and performing asexpected.Note: You cannot add operations that have been previously created with VoIPand Network Quality Manager. If you have already created an operation withthe same operation number, you must manually remove the operation from thedevice.To add TCP Connect IP SLA operations to your network devices:



3. Click Add new operations in the Manage IP SLA Operations section.4. Select Create new operations, and then click Next.5. Select TCP Connect, and then click Next.6. Select the type of path your network is configured to use. For more

information, see Designating Paths in the VoIP and Network QualityManager Administrator Guide.

7. Select the source nodes you want to add to your new TCP Connectoperation, and then click Next.Note: If you do not see your IP SLA routers in the list, you must add thedevices before you can continue. For more information, see AddingDevices for Monitoring in the Web Console in the SolarWinds NetworkPerformance Monitor Administrator Guide.

8. Select the target nodes you want to add to your new TCP Connectoperation.

9. If you want to create the path in only one direction, select No, create thepath in just one direction.

65

Adding TCP Connect IP SLA Operations to Your Devices




10. If you want to specify an external node as a target, complete the followingprocedure.

a. Click Yes, use external node as a target.b. Type the IP address or host name of the external node you want to

add.Note: If you use a host name, the source node of the operationmust be able to successfully resolve the host name.

11. Click Next.12. Type the frequency for the operation to be performed.13. Type the port number to be used in the test in the Port Number field.14. Define your warning, critical, and maximum threshold values in the

associated fields.15. If you want to assign a type of service (ToS), Virtual Routing and

Forwarding (VRF) name for this path, or enable the target node to act asa controller, expand Advanced, and then type the type of service numberor VRF name in the appropriate fields, or select Control enable.Notes:





66



Adding UDP Jitter IP SLA Operations to Your Devices

User Datagram Protocol (UDP) Jitter IP SLA operations measure WAN qualityby testing connection times between two devices using a specific port number.These operations ensure that your WAN is operational and performing asexpected.Note: You cannot add operations that have been previously created with VoIPand Network Quality Manager. If you have already created an operation withthe same operation number, you must manually remove the operation from thedevice.To add UDP Jitter IP SLA operations to your network devices:



3. Click Add new operations in the Manage IP SLA Operations section.4. Select Create new operations, and then click Next.5. Select UDP Jitter, and then click Next.6. Select the type of path your network is configured to use. For more


7. Select the source nodes you want to add to your new UDP Jitteroperations, and then click Next.Note: If you do not see your IP SLA routers in the list, you must add thedevices before you can continue. For more information, see AddingDevices for Monitoring in the Web Console in the SolarWinds NetworkPerformance Monitor Administrator Guide.

67

Adding UDP Jitter IP SLA Operations to Your Devices




8. Select the target nodes you want to add to your new UDP Jitteroperation.




add.Note: If you are using a host name, the source node of theoperation must be able to successfully resolve the host name.

11. Type the frequency for the operation to be performed.12. Type the port number to be used in the test in the Port Number field.13. Define your warning, critical, and maximum threshold values in the





15. Click Next.

68

16. If you want to rename operations or edit any other operation properties,select the operations you want to modify, and then click Edit.


18. Click Go VNQM Home to finish the procedure and return to the VoIP andNetwork Quality Manager home page.

Adding VoIP UDP Jitter IP SLA Operations to Your Devices

VoIP UDP Jitter IP SLA operations measure call path metrics on your VoIPnetwork. These operations ensure that your VoIP network is operational andperforming as expected.Note: You cannot add operations that have been previously created with VoIPand Network Quality Manager. If you have already created an operation withthe same operation number, you must manually remove the operation from thedevice.To add VoIP UDP Jitter IP SLA operations to your network devices:



3. Click Add new operations in the Manage IP SLA Operations section.4. Select Create new operations, and then click Next.5. Select VoIP UDP Jitter, and then click Next.6. Select the type of path your network is configured to use. For more


69

Adding VoIP UDP Jitter IP SLA Operations to Your Devices


7. Select the source nodes you want to add to your new VoIP UDP Jitteroperation, and then click Next.Note: If you do not see your IP SLA routers in the list, you must add thedevices before you can continue. For more information, see AddingDevices for Monitoring in the Web Console in the SolarWinds NetworkPerformance Monitor Administrator Guide.

8. Select the target nodes you want to add to your new VoIP UDP Jitteroperation.





11. Type the frequency for the operation to be performed.12. Type the port number to be used in the test in the Port Number field.13. Define your warning, critical, and maximum threshold values in the

associated fields.

70



14. If you want to assign a codec, type of service (ToS), or Virtual Routingand Forwarding (VRF) name for this path, expand Advanced, select thecodec, and then type the type of service number and VRF name in theappropriate fields. For more information about codec algorithms, seeJitter in the VoIP and Network Quality Manager Administrator Guide.Notes:







Adding ICMP Echo IP SLA Operations to Your Devices

Internet Control Message Protocol (ICMP) Echo IP SLA operations measureround trip time between nodes on your network. These operations ensure thatyour network devices are operational and performing as expected.

71



Notes:

l You may need to configure your device to successfully use ICMP Echooperations. For more information, see Configuring CLI Credentials in theVoIP and Network Quality Manager Administrator Guide.

l You cannot add operations that have been previously created with VoIPand Network Quality Manager. If you have already created an operationwith the same operation number, you must manually remove theoperation from the device.

To add ICMP Echo IP SLA operations to your network devices:



3. Click Add new operations in the Manage IP SLA Operations section.4. Select Create new operations, and then click Next.5. Select ICMP Echo, and then click Next.6. Select the type of path your network is configured to use. For more


7. Select the source nodes you want to add to your new ICMP Echooperation, and then click Next.Note: If you do not see your IP SLA routers in the list, you must add thedevices before you can continue. For more information, see AddingDevices for Monitoring in the Web Console in the SolarWinds NetworkPerformance Monitor Administrator Guide.

8. Select the target nodes you want to add to your new ICMP Echooperation.


72



10. If you want to specify an external node as target, complete the followingprocedure.



11. Click Next.12. Type the frequency for the operation to be performed.13. Define your warning, critical, and maximum threshold values in the







73





Adding UDP Echo IP SLA Operations to Your Devices

UDP Echo IP SLA operations measure round trip time between nodes on yournetwork. These operations ensure that your network devices are operationaland performing as expected.Note: You cannot add operations that have been previously created with VoIPand Network Quality Manager. If you have already created an operation withthe same operation number, you must manually remove the operation from thedevice.To add UDP Echo IP SLA operations to your network devices:



3. Click Add new operations in the Manage IP SLA Operations section.4. Select Create new operations, and then click Next.5. Select UDP Echo, and then click Next.6. Select the type of path your network is configured to use. For more


7. Select the source nodes you want to add to your new UDP Echooperation.Note: If you do not see your IP SLA routers in the list, you must add thedevices before you can continue. For more information, see AddingDevices for Monitoring in the Web Console in the SolarWinds NetworkPerformance Monitor Administrator Guide.

74



8. Select the target nodes you want to add to your new UDP Echooperation.



a. Click Yes, use external node as a target.

b. Type the IP address or host name of the external node you want toadd.Note: If you use a host name, the source node of the operationmust be able to successfully resolve the host name.

11. Click Next.12. Type the frequency for the operation to be performed.13. Type the port number to be used in the test.14. Define your warning and critical threshold values in the associated fields.15. If you want to assign a type of service (ToS) or Virtual Routing and

Forwarding (VRF) name for this path or enable the target node to act as acontroller, expand Advanced, and then type the type of service numberor VRF name in the appropriate fields or select Control enable.Notes:



75

Adding UDP Echo IP SLA Operations to Your Devices






Adding ICMP Path Echo Operations to Your Devices

ICMP Path Echo IP SLA operations measure round trip time between eachnode on a designated path on your network. Round trip time is measured hop-by-hop. These operations ensure that your network devices are operationaland performing as expected.Notes:

l To add ICMP Path Echo operations, you must add CLI login credentialsto your source node. For more information, see Configuring CLICredentials in the VoIP and Network Quality Manager AdministratorGuide.


To add ICMP Path Echo IP SLA operations to your network devices:



3. Click Add new operations in the Manage IP SLA Operations section.4. Select Create new operations, and then click Next.5. Select ICMP Path Echo, and then click Next.

76

6. Select the type of path your network is configured to use. For moreinformation, see Designating Paths in the VoIP and Network QualityManager Administrator Guide.

7. Select the source node you want to use for your ICMP Path Echooperation.Note: If you do not see your IP SLA routers in the list, you must add thedevices before you can continue. For more information, see AddingDevices for Monitoring in the Web Console in the SolarWinds NetworkPerformance Monitor Administrator Guide.

8. If the target node is being monitored, select it from the list.9. If you want to create the path in only one direction, select No, create the

path in just one direction.10. If you want to specify an external node as a target, complete the following

procedure.

a. Click Yes, use external node as a target.

b. Type the IP address or host name of the external node you want toadd.Note: If you use a host name, the source node of the operationmust be able to successfully resolve the host name.

11. Click Next.12. Type the frequency for the operation to be performed.13. Define your warning and critical threshold values in the associated fields.

77

Adding ICMP Path Echo Operations to Your Devices




14. If you want to assign a type of service (ToS) or Virtual Routing andForwarding (VRF) name for this path, expand Advanced, and then typethe type of service number and VRF name in the appropriate fields.Notes:







Adding ICMP Path Jitter Operations to Your Devices

ICMP Path Jitter IP SLA operations take call path measurements betweeneach node on a designated path on your VoIP network. Round trip time ismeasured hop-by-hop. These operations ensure that your VoIP network isoperational and performing as expected.

78

Notes:

l To add ICMP Path Jitter operations, you must add CLI login credentialsto your source node. For more information, see Configuring CLICredentials in the VoIP and Network Quality Manager AdministratorGuide.


To add ICMP Path Jitter IP SLA operations to your network devices:



3. Click Add new operations in the Manage IP SLA Operations section.4. Select Create new operations, and then click Next.5. Select ICMP Path Jitter, and then click Next.6. Select the type of path your network is configured to use. For more


7. Select the source node you want to use for your ICMP Path Jitteroperation, and then click Next.Note: If you do not see your IP SLA routers in the list, you must add thedevices before you can continue. For more information, see AddingDevices for Monitoring in the Web Console in the SolarWinds NetworkPerformance Monitor Administrator Guide.

8. If the target node is being monitored, select it from the list.9. If you want to create the path in only one direction, select No, create the

path in just one direction.

79

Adding ICMP Path Jitter Operations to Your Devices







11. Click Next.12. Type the frequency for the operation to be performed.13. Define your warning, critical, and maximum threshold values in the







80



Adding Existing Operations to VoIP and Network Quality Manager

With VoIP and Network Quality Manager you can monitor operations that arealready configured on a device. To do so, add these operations to VNQM.To add an operation configured on your device to VNQM:



3. Click Add new operations in the Manage IP SLA Operations section.4. SelectMonitor existing operations, and then click Next.5. If you want to automatically discover operations on your nodes, complete

the following procedure.

a. Select Automatically discover existing operations, and thenclick Next.

b. Select the node where the operation you want to monitor resides,and then click Next.Note: If you have not entered valid CLI credentials for the selectednode, you may be prompted to enter credentials. You do not haveto provide credentials to the node.

c. Select the operation you want to monitor, and then click MonitorOperations.

81

Adding Existing Operations to VoIP and Network Quality Manager


6. If you want to manually enter the operation numbers, expand Advanced,and then complete the following procedure.

a. SelectManually enter operation numbers, and then click Next.b. Select the node where the operation you want to monitor resides,

and then click Next.Note: If you have not entered valid CLI credentials for the selectednode, you may be prompted to enter credentials. You do not haveto provide credentials to the node.

c. Enter the operation number, and then click Next.d. Select the operation you want to monitor, and then click Monitor

Operations.


Editing IP SLA OperationsThe following sections provide more details about editing IP SLA operationsmonitored by VoIP and Network Quality Manager:

l Modifying the SLA Locationl Renaming Operations in VNQM

Note:Modifying operations created with VNQM is possible only by usingVNQM. If you modify an operation created by VNQM directly on the device, thechanges will be overwritten by the IP SLA operation settings from VNQM.

Modifying the SLA Location

You can add or modify location information for any IP SLA operation bycompleting the following procedure.To edit the SLA location:


2. Click Edit or delete operations in the Manage IP SLA Operationssection.

82

3. Select the operation you want to modify, and then click Add/Edit SLALocation.

4. Select the Origin Location or Cisco CallManager ID.5. Select the Target Location or Cisco CallManager ID.6. Click Save.

Renaming Operations in VoIP and Network Quality Manager

Any operation that VoIP and Network Quality Manager monitors is given adefault name using the following pattern: SourceNodeName ->TargetNodeName, where SourceNodeName is the name of the source nodeand TargetNodeName is the name of the target node. To change the name ofan operation, complete the following procedure.To rename an operation:



3. Select the operation you want to modify, and then click Edit.4. Type the new name for the operation in the Operation Name field, and

then click Save.

Notes:

l Leaving the Operation Name field blank results in the operation beingnamed using the default naming pattern.

l If you change the name of a node in NPM, the change will be reflected inthe operation name unless the default naming pattern is not being used.

Deleting IP SLA Operations from VoIP and Network QualityManagerIf you decide to stop monitoring specific IP SLA operations in VoIP andNetwork Quality Manager, complete the following procedure.

83

Renaming Operations in VoIP and Network Quality Manager


Note: Deleting manually added IP SLA operations from VoIP and NetworkQuality Manager only removes the operations from the list of monitoredoperations. The operations will still exist on your network devices. You mustmanually remove operations from your devices to completely remove theoperations. If you do not remove the operations, you will not be able to addother operations with the same number.To delete IP SLA Operations from VoIP and Network Quality Manager:




4. Select the operations you want to delete, and then click Delete.5. When prompted to confirm, click Delete to stop monitoring the selected

operations.

VoIP ManagementIn VoIP and Network Quality Manager you can monitor your call managers,VoIP gateways and define your VoIP infrastructure for a quick overview in theVoIP Infrastructure resource.To configure your devices for monitoring in VNQM, complete the followingsteps:

1. Add the devices to your database. For more information, see AddingDevices for Monitoring in the Web Console in the SolarWinds Orion CoreAdministrator Guide.

2. Add the devices to VNQM for monitoring.

l If you want to monitor VoIP calls on your devices, add themas call managers. For more information, see Managing CallManagers in the VoIP and Network Quality ManagerAdministrator Guide.

84



l If you want to monitor the PRI trunk utilization of your devices,add them as gateways. For more information, see ManagingGateways in the VoIP and Network Quality ManagerAdministrator Guide.

VNQM also provides an overview of your VoIP infrastructure monitored byVNQM. For more information about configuring this resource, see SelectingVoIP Infrastructure in the VoIP and Network Quality Manager AdministratorGuide.

Managing Call ManagersCall Manager devices are managed on the Manage Call Manager Nodespage.The Manage Call Manager Nodes page provides a list of Cisco CallManager,CallManager Express, and Avaya Communication and Media Server devicesthat are currently monitored by VNQM.Note: Call managers from manufacturers other than Cisco and Avaya can bemonitored with VoIP and Network Quality Manager if you use a custommanagement information base (MIB) poller specifically configured for your callmanager from other manufacturers. You cannot monitor call manager specificdata, such as VoIP phones, region information, or call data. For moreinformation, see Adding Call Manager Devices from Other Manufacturers.To access the Manage Call Manager Nodes page:

1. Log in to the Orion Web Console as an administrator.2. Select the VoIP and Network Quality tab, and then click VoIP & Quality

Settings in the top right of the page.3. Click Manage CallManager Nodes.

CLI Credentials

Command line interface (CLI) credentials are used to log in to any device, suchas a call manager, a gateway, a router, and so on, that accepts commandsthrough a command line interface. You can provide text input through thecommand line, and receive text output after the execution of the command. Formore information about CLI credentials and their usage, see Configuring CLICredentials.

85

Managing Call Managers


The CLI credentials are also used for logging in to Avaya Call Managers. Formore information, see Adding Avaya Call Manager Devices.Credentials Used for Cisco CallManager

To exercise the full benefits of monitoring Cisco CallManager devices, you canprovide AXL credentials and FTP credentials to the CDR/CMR data. Bydownloading CDR/CMR data from CallManager devices, VoIP and NetworkQuality Manager can track the region information of each call made throughyour monitored Cisco CallManager device.AXL refers to the Administration XML API of Cisco, which provides amechanism to receive and modify data in the database of the call manager.VoIP and Network Quality Manager queries the database for regioninformation. No information is modified in the database. You can create a readonly AXL account specifically for VoIP and Network Quality Manager.Note: To monitor CDR/CMR data, perform the following tasks to both publisherand subscriber Cisco CallManager Devices.

1. Configure the Cisco CallManager to monitor calls. For more information,see Configuring Cisco CallManagers for FTP.

2. Enable the AXL API. For more information, see your manufacturer'sdocumentation.

3. Create an AXL account. For more information, see your manufacturer'sdocumentation.

Monitoring Call Manager Health

VoIP and Network Quality Manager references the Cisco ManagementInformation Base (MIB) CISCO-CCM-MIB to provide out-of-the-box monitoringcapability for Cisco CallManager and CallManager Express devices.You can also monitor Avaya Communication and Media Server devices withVoIP and Network Quality Manager. VNQM intercepts the CDR packets sentby the TCP protocol, as well as the RTCP data sent through UDP, and basedon these data, it provides information about the call details and the call quality.Note: If you want to track the performance of call managers from othermanufacturers, you can use universal device pollers in connection withSolarWinds Network Performance Monitor. For more information, seeMonitoring MIBs with Universal Device Pollers in the SolarWinds NetworkPerformance Monitor Administrator Guide.

86

http://www.solarwinds.com/documentation/helploader.aspx?topic=orionagmonitoringcustommibs.htm

After a call manager device has been added to the database for management,you can use the intuitive interface of VoIP and Network Quality Manager totrack and report call-processing performance statistics for your VoIP network.Only Cisco CallManager, CallManager Express, and Avaya Communicationand Media Server devices can be added to VoIP and Network QualityManager as CallManager nodes. Call management devices from othermanufacturers can only be monitored as a part of your VoIP infrastructure. Formore information about adding call management devices from othermanufacturers than Cisco and Avaya, see Adding Call Manager Devices fromOther Manufacturers in the VoIP and Network Quality Manager AdministratorGuide.Note: Cisco CallManager, CallManager Express, and Avaya Communicationand Media Server devices provide a different level of details:

l For Cisco CallManagers, you can see all information from the device CallDetail Records, such as the call source, destination, duration, or the callquality indicators.

l For Cisco CallManager Express devices, the information about CDR isnot available, thus giving you only the details about the device status andits phone devices count.

l For Avaya Communication and Media Server devices, you can seeinformation such as the call source, destination, duration, and certain callquality indicators.

Adding Cisco CallManager Devices to VoIP and Network Quality Manager

The following procedure adds a Cisco CallManager device to VoIP andNetwork Quality Manager.Note: Avaya Call Managers can also be monitored with VoIP and NetworkQuality Manager. For more information about monitoring Avaya Call Managers,see Managing Avaya Call Managers. Call managers from manufacturers otherthan Cisco and Avaya can be monitored with VoIP and Network QualityManager if you use a custom management information base (MIB) pollerspecifically configured for your call manager from other manufacturers. Youcannot monitor call manager specific data, such as VoIP phones, regioninformation, or call data. For more information, see Adding Call ManagerDevices from Other Manufacturers in the VoIP and Network Quality ManagerAdministrator Guide.

87



To add a Cisco CallManager device to VoIP and Network QualityManager:


Settings in the top right of the page.3. Click Add CallManager nodes.4. Select an available CallManager-hosting device, and then click Next.

Note: If you do not see an expected CallManager device, use the WebConsole to add it. You may need to enable SNMP on the CallManagerdevice.

5. Decide whether you want to collect information about calls on this callmanager.

l If you want to collect information about calls on this call manager,select Enable CDR/CMR polling for this Call Manager, and thenclick Next.

l If you do not want to collect call information from this call manager,select Add Call Manager without CDR/CMR monitoring, clickNext, and then click Add Call Manager.

6. Define your AXL credentials by either selecting an existing credentialset from the Select AXL credentials list or by creating a new set.

To create a new set, complete the following procedure:

a. Type a name in Select AXL credentials.b. Type the user name in AXL Username.c. Type the password in AXL Password.

Notes:

l Enter AXL credentials for both publisher and subscriber call managers.

l AXL credentials must be accurate. VoIP and Network Quality Managertests the credentials before continuing to the next step.

88

7. Click Next.8. Define the FTP server details.

a. Type the FTP server IP address or host name where yourCDR/CMR data is stored. For more information about FTPconfiguration, see Configuring Cisco CallManagers for FTP.

b. Enter the FTP port number.c. Select Passive mode to connect to the FTP server in passive

mode.d. If you connect to an SFTP site, select Secure connection.e. Enter the CDR/CMR file path if applicable.f. Enter your FTP credentials by either selecting an existingcredential set from the Select FTP credentials list or by creating anew set.To create a new set, complete the following procedure.

l Type a name in Select FTP credentials.l Type the user name in FTP Username.l Type the password in FTP Password.l Click Test FTP server connection to test thecredentials.

g. Type a number in Polling Frequency between 1 and 60 toconfigure how frequently you want to poll the FTP server inminutes.

h. Select Delete CDR/CMR files from FTP server after download ifyou want to remove the files from the FTP server.Warning: Deleting CDR/CMR files from the FTP server may causeserious data loss. Ensure that your backups are runningsuccessfully before selecting this option.Note: Removing the files from the FTP server is advisable toprevent the device from filling up on logs, or in the case when youwant to speed up data collection from the FTP server.

i. Click Next.

89



9. Review the information, and then click Add Call Manager, or click Backto make changes.

Adding CallManager Express Devices to VoIP and Network Quality Man-ager

The following procedure adds a Cisco CallManager Express device to VoIPand Network Quality Manager.Note: VoIP and Network Quality Manager does not collect call datainformation or region information from CallManager Express devices and doesnot support phone polling on the devices.To add a CallManager Express device to VoIP and Network QualityManager:


Settings in the top right of the page.3. Click Add new CallManager nodes.4. If you have not already added your CallManager devices to the database,

use the Web Console to add your CallManager devices beforecontinuing.

5. Select an available CallManager Express device, and then click Next.Note: If you do not see an expected CallManager Express device, usethe Web Console to add it.

6. Click Next.7. Review the information, and then click Add Call Manager, or click Back

to make changes.

Managing Avaya Call Managers

To exercise the full benefits of monitoring an Avaya Call Manager, the devicemust be configured to emit CDRs and quality data.

90

In order to collect Avaya data in VNQM, the Avaya user must have sufficientpermissions to execute the following commands:

l display system-parameters cdr: to set up an Avaya call manager toemit CDR and quality data.

l list station: to display a list of phone devices.l list media-gateway: to display a list of gateways.l list ip-network-region monitor: to display a list of regions.l status station: to display the details of phones, including statusinformation.

l display station [x], where [x] is the extension number of the phone:to display the details of phones. The extension number of the phone canbe obtained by using the list station command.

l display media-gateway [y], where [y] is the gateway number: todisplay the details of gateways. The gateway number can be obtained byusing the list media-gateway command.

To set up an Avaya Call Manager to emit CDRs:

1. Log on to the Avaya Call Manager using PuTTY, TuTTY, or AvayaManager.

2. Type change system-parameters cdr, and then press F3.3. Set the Primary Output Format to customized.

91



4. Set the Primary Output Endpoint to CDR1, and then press F7 tonavigate to the next page.Note: If the Primary Output is already in use, you can use the SecondaryOutput for these settings.

5. Define the customized CDR format according to the details in thefollowing illustration, and then press F3 to save your changes.Note: Instead of the calling-num parameter, you can also use the clg-num/in-tac parameter.

92

6. Type change node-names ip, and then press F3.

7. Type a name for VNQM. The name can be any name you choose.

8. Type the IP address of the VNQMmain or additional poller in the IPAddress column, and then press F3 to save your changes.

93



9. Type change ip-services, press F3, and then define the followingsettings:

l Service Type: CDR1l Local Node: procrl Remote Node: [vnqm] where [vnqm] is the name you specified inStep 7.

l Remote Port: 50000

10. Press F7 to navigate to the next page.

94

11. Set the Reliable Protocol to n, and then press F3.

Note: After changing a setting, press F3 to save it, or press F1 to discard yourchanges.

Setting up an Avaya Call Manager to emit quality data

To set up an Avaya Call Manager to emit quality data, complete the followingprocedure.

1. Log on to the Avaya Call Manager using PuTTY, TuTTY, or AvayaManager.

95

Setting up an Avaya Call Manager to emit quality data


2. Type change system-parameters ip-options, press F3, and thendefine the following settings:

l Server IPV4 Address: The IP address of the VNQMmain oradditional poller

l RTCP Report Period in secondsl IPV4 Server Port: 5005

3. Press F3 to save your changes.4. Type change ip-network-region [x] where [x] is the region number,

and then press F3 .5. Use F7 to navigate to the IP Network Region page.

96

6. Define the following settings:l RTCP Reporting Enabled: yl Use Default Server Parameters: y

7. Press F3 to save your changes.

Avaya CDR parameters

To take advantage of CDR polling in VoIP and Network Quality Manager, atleast the following Avaya CDR parameters must be configured:

l dialed-num

l calling-num, or clg-num/in-tacl start-date(4d) or start-datel start-time

l end-date(4d), end-date, or datel end-time, or timel cond-code

If your Avaya setup makes it necessary, you can substitute certain parameterswith different ones, and use them in the following way:

97

Avaya CDR parameters


l Instead of the start-time parameter, you can use the time and sec-dur parameters.

l Instead of the start-time parameter, you can use the end-time andsec-dur parameters.

l Instead of the end-time parameter, you can use the start-time andsec-dur parameters.

l Instead of the time parameter, you can use the start-time and sec-dur parameters.

The order in which you configure CDR parameters is not relevant.Notes:

l To be able to use the start-date, start-date(4d), end-date(4d), start-time,and end-time CDR custom fields, you must enable the SA8201-StartTime and the 4-Digit Year CDR Custom fields special application.

l You must also enable the SA8202-Intra-switch CDR by COS specialapplication.

Adding Avaya Call Manager Devices

Before adding Avaya Communication and Avaya Media Server devices toVNQM, make sure that you configure the device for VNQM. For detailedinformation, see Managing Avaya Call Managers.When you add an Avaya call manager device, VoIP and Network QualityManager uses the value of the OID 1.3.6.1.2.1.1.1 (sysDescr) to identify anAvaya Communication and Media Server.

Adding an Avaya Communication and Media Server to VNQM

The following procedure adds an Avaya Communication and Media Serverdevice to VoIP and Network Quality Manager.Note: Call managers from manufacturers other than Cisco and Avaya can bemonitored with VoIP and Network Quality Manager if you have SolarWindsNetwork Performance Monitor installed, and use a custom managementinformation base (MIB) poller specifically configured for your call manager fromother manufacturers. You cannot monitor call manager specific data, such asVoIP phones, region information, or call data. For more information, seeAdding Call Manager Devices from Other Manufacturers in the VoIP andNetwork Quality Manager Administrator Guide.

98

To add an Avaya Call Manager device to VoIP and Network QualityManager:


Settings in the top right of the page.3. Click Add CallManager nodes in the VoIP Management > Manage

CallManager Nodes section.4. Select an available CallManager-hosting device, and then click Next.

Note: If you do not see an expected call manager device, use the WebConsole to add it. Make sure that you enable SNMP on the call managerdevice.

5. Decide whether you want to collect information about calls on this callmanager.

l If you want to collect information about calls on this call manager,select Enable CDR/CQR polling for this Call Manager, and thenclick Next.

l If you do not want to collect information about calls on this callmanager, select Add Call Manager without CDR/CQRmonitoring, and then click Next.For information about the configuration of the necessary CDRparameters, see Avaya CDR parameters.

6. Define the CLI credentials that let you log in to the SAT console of theAvaya Call Manager by either selecting an existing credentials set fromthe Select Credentials list, or by creating a new set.

To create a new set, complete the following procedure:

a. Type the user name and password in the appropriate fields.b. Select the enable level from the list.c. Type the enable password.d. In the Advanced section, select either the Telnet or the SSH

protocol from the list.e. Specify the Connection Timeout.

99

Adding an Avaya Communication and Media Server to VNQM


7. Click Test to test the credentials.Note: If the SAT account has a PIN code defined for additionalauthentication, the CLI credential test will fail. PINs are not supported byVoIP and Network Quality Manager. Disable the PIN in the Avaya CallManager, or use a credential set for which a PIN code is not defined.

8. Click Next.9. Review the information, and then click Add Call Manager, or click Back

to make changes.

Notes:

l The Avaya CDR/CQR Polling configuration grouping describes theconfiguration settings that are applicable to the Avaya Call Manager. Toemit CDR or CQR (RTCP) data, use the listening ports that aredisplayed. The port numbers cannot be further configured through theuser interface of VoIP and Network Quality Manager.

l VoIP and Network Quality Manager does not support the usage ofsurvivable processors on Avaya. If you have set up survivableprocessors on your Avaya Communication and Media Server, VNQMdoes not accept CDR data.

l Use an NTP server to synchronize the time settings of the AvayaCommunication and Media Server and the VNQM pollers. Thesynchronization is necessary to make sure that the CDR data and thecall quality data match each other. If the time settings of the call managerand the VNQM pollers are not synchronized, the call quality data may notbe displayed.

Requirements for Handling RTCP Data

If VNQM does not handle RTCP data correctly, the following causes arepossible. Make sure that you fix these issues in order for VNQM to be able toprocess RTCP data.

l RTCP is already pointing to a different target than your VNQM instance.l Both channels for CDR data are already occupied.l You are using a customized data format for the CDR channel, whichdoes not comply with the requirements of VNQM.

100

Bandwidth Requirements for Avaya Communication and Media Servers

This topic provides information about the average bandwidth requirements ofAvaya Communication and Media Servers with different traffic levels.This section assumes that the default polling interval of five seconds is used.If an Avaya Communication and Media Server handles 20 000 callssimultaneously, the bandwidth necessary for polling RTCP data can be up to18 Mbps.If an Avaya Communication and Media Server handles one-sixth of thisamount, that is, around 3 000 calls simultaneously, the bandwidth necessaryfor polling RTCP data is up to 3 Mbps.Based on the previous calculations, a bandwidth of 5 Mbps suits most needs.

Adding Call Manager Devices from Other Manufacturers

VNQMalso allows limited monitoring of other call manager devices. You canadd them as VoIP network nodes and monitor their status in the VoIPInfrastructure resource. To do so, use a universal device poller configured foryour call manager from other manufacturers. To take advantage of this option,SolarWinds Network Performance Monitor must also be installed.Notes:

l Call managers from manufacturers other than Cisco and Avaya areadded as VoIP network nodes, and thus are not displayed in theCallManagers resource.

l No CDR/CMR data are collected.

For more information about setting up universal device pollers for callmanagers from other manufacturers, see Monitoring MIBs with UniversalDevice Pollers in the SolarWinds Network Performance Monitor AdministratorGuide.For more information about adding call managers from other manufacturers toVoIP and Network Quality Manager, see Adding VoIP Infrastructure in the VoIPand Network Quality Manager Administrator Guide.

101

Bandwidth Requirements for Avaya Communication and Media Servers




Defining FTP Servers

When you set up your Cisco CallManager device to collect CDR/CMR data,you can also designate an FTP server where the data is stored so that otherapplications, such as VoIP and Network Quality Manager, can download andprocess the data. For more information about FTP configuration, seeConfiguring Cisco CallManagers for FTP.If you are unsure of your FTP server settings, check your Cisco BillingApplication Server parameters.The Polling Frequency refers to how frequently VoIP and Network QualityManager tries to download CDR/CMR data. If you have a large amount of dataor if VoIP and Network Quality Manager experiences frequent timeouts, youshould extend the amount of time between polls.Deleting CDR/CMR data can cause serious data loss, but can be useful incertain circumstances. Do not select this option unless you successfully runverified backups of your data.

Configuring Cisco CallManagers for FTP

Complete the following procedure to configure your Cisco CallManager deviceto save CDR/CMR data to an FTP server.You will need administrator access to your Cisco Unified CommunicationsManager and Cisco Unified Serviceability pages.

1. Log on to your Cisco Unified Communications Manager Administrationpage with an account that has administrative privileges.

2. Click System > Service Parameters.3. On the Service Parameter page, set the CDR Enabled Flag to True.4. Click OK.

To change the time interval for collecting CDR/CMR data, clickSystem > Enterprise Parameters, modify the CDR File TimeInterval, and then click OK.

5. Log on to the Cisco Unified Serviceability page with an account that hasadministrative privileges.

6. Click Tools > CDR Management.

102

7. Click the plus sign to add a new application billing server.8. Enter the following information:

l Host or IP address - the application billing server to which you wantto send CDRs

l User Name - the user name of the application billing server whohas write permissions to the directory to which you send the CDRdata

l Password - the FTP passwordl Protocol - the protocol used to send CDR data to the applicationbilling server

l Directory Path - the path to which you want to send CDR data

9. Click Add.Note: This information is used when configuring your CCM when youwant to monitor CDR/CMR data in VoIP and Network Quality Manager.

Editing Call Managers

In VoIP and Network Quality Manager you can edit the properties of your callmanager nodes.You can edit the following properties:

l Node name and polling addressl Polling Details (polling method, polling intervals and engines, CDR/CMRpolling settings)

l Dependenciesl Custom propertiesl Call Manager specific details (AXL credentials, FTP server settings,polling frequency)

l Alerting thresholds

For more information about editing node properties, see Edit Properties in theSolarWinds Network Performance Monitor Administrator Guide.

103

Editing Call Managers

http://www.solarwinds.com/documentation/helploader.aspx?topic=OrionCoreAGEditingDeviceProperties.htm


To edit call manager specific settings:

1. Log in to the Orion Web Console as an administrator.2. Click VoIP & Network Quality in the Modules menu bar, and then click

VoIP & Quality Settings at the top right of the view.3. Click Manage CallManager Nodes in the VoIP Management section.4. Select the call manager node you want to modify, and then click Edit

CallManagers. This opens the Edit Properties page where you can editthe following call manager specific details, depending on the type of callmanager.

l For Cisco Call Managers:

Call Manager CDR/CMR Polling

Select Enable CDR/CMR polling for this CallManager to collect information about calls on thisCallManager.

AXL Credentials

Select the appropriate settings from the SelectAXL Credentials list or define new credentials.To define a new set of AXL Credentials:

l Type a name in Select AXL Credentials.l Type the user name in AXL Username.l Type the password in AXL Password.Notes:

l Enter AXL credentials for bothpublisher and subscriber callmanagers.

l AXL credentials must be accurate.VoIP and Network Quality Managertests the credentials before continuingto the next step.

104

FTP Server Settings

Fill in or edit details about the FTP server whereyour CDR/CMR data is stored. For moreinformation about FTP configuration, seeConfiguring Cisco CallManagers for FTP.FTP Server: Fill in or edit the FTP server IPaddress.Port: Fill in or edit the FTP port number.Passive mode: Select this option to connect tothe FTP server in passive mode.Secure Connection: Select this option if youconnect to an SFTP site.CDR/CMR file path: Fill in or edit these details ifappropriate.FTP Credentials: Add or edit your FTPcredentials.

To define a new set of FTP Credentials:

l Type a name in Select FTP Credentials.l Type the user name in FTP Username.l Type the password in FTP Password.

Polling Frequency: Type a number between 1and 60 to configure how frequently you want topoll the FTP server in minutes.Delete CDR/CMR files from FTP server afterdownload: Select this option to delete CDR/CMRfiles from the FTP server if the hard drive isbecoming full or if you need to speed up datacollection from the FTP server.Warning: Deleting CDR/CMR files from the FTPserver may cause serious data loss. Ensure thatyour backups are running successfully beforeselecting this option,

105

FTP Server Settings


l For Avaya Communication and Media Servers:

Call Manager CDR/CQR Polling

Select Enable CDR/CQR polling for this CallManager to collect information about calls on this CallManager.

Call Manager CLI Credentials

Select the appropriate settings from the SelectCredentials list, or define new credentials.To define a new set of CLI Credentials:

l Type the user name and password in theassociated fields.

l In the Advanced section, you can define theprotocol, the port number, and the connectiontimeout.

5. Edit the appropriate details, and then click Submit.

Deleting Call Manager Devices from VoIP and Network Quality Manager

The following procedure provides the steps required to delete a Call Managerdevice from VoIP and Network Quality Manager.To delete a Call Manager device from VoIP and Network Quality Manager:


Settings in the top right of the page.3. Click Manage CallManager nodes.4. Select the CallManager-hosting devices you want to delete, and then

click Remove CallManagers.5. Click OK to confirm.

106

Managing GatewaysManaging gateways in VoIP and Network Quality Manager is done on theManage Gateways page. This page provides a list of all gateway nodesmonitored by VNQM.To access the Manage Gateway Nodes page:


Settings in the top right of the page.3. Click Manage gateways in the VoIP Management grouping.

Notes:

l For polling gateway details, VNQM requires valid CLI credentials.l For adding gateway nodes to VNQM, the nodes already have to be inyour database.

Adding Gateways

If you want to monitor your gateways with VoIP and Network Quality Manager,you have to add them to VNQM as gateway nodes first.The Add VoIP Gateway page provides a wizard which helps you to add agateway node to VoIP and Network Quality Manager as a gateway. Gatewaynodes require CLI credentials.To add a gateway device to VoIP and Network Quality Manager:


Settings in the top right of the page.3. Click Add gateways in the VoIP Management grouping.

107

Managing Gateways


4. Select VoIP Gateways to Add: Select one or more available nodeswhich you want to add to VNQM as gateways.Note: If you do not see an expected device, click add your nodes to addit to the Orion database, and then repeat Steps 1 - 3. For moreinformation about adding nodes to the Orion database, see AddingDevices for Monitoring in the Web Console in the SolarWinds NetworkPerformance Monitor Administrator Guide.

5. Click Next.6. The CLI Credentials Issues dialog pops up with details about CLI

credential issues on the nodes you are adding. Modify CLI credentials tosolve the issues:

a. Select the node or nodes whose CLI credentials you want to edit.Note: If you want to use the same CLI credentials for all nodeswith issues, click Select Errors. All nodes will be selected.

b. Click Edit Credentials.

l Select valid credentials in the Select Credentials list or define anew set of credentials in the Username and Password fields.

l Click Save to apply your CLI credential settings on the selectednodes.

c. Click Select Successful to select nodes whose CLI credentialshave been updated successfully.

d. Click Continue to add the selected nodes to VNQM as gatewaynodes.

7. Review the information, and then click Finish to add the selectedgateways, or click Back to make changes.

Editing VoIP Gateways

You can edit the gateway node details, such as the node name, polling details,dependencies or custom properties.

108



To edit gateway node properties:

1. Log in to the Orion Web Console as an administrator.2. Click VoIP & Quality Settings in the top right of the VoIP and Network

Quality tab.3. Click Manage gateways.4. Select one or more available gateways that you want to edit.

Note: If you do not see an expected device, click add your nodes to addit to the Orion database, and then repeat Steps 1 - 3. For moreinformation about adding nodes to the Orion database, see AddingDevices for Monitoring in the Web Console in the SolarWinds NetworkPerformance Monitor Administrator Guide.

5. Edit the appropriate properties of the selected gateway node. For moreinformation about editing nodes, see Editing Object Properties in theSolarWinds Network Performance Monitor Administrator Guide.

6. Click Submit to apply your changes.

Editing CLI Credentials for Gateway Nodes

For monitoring gateway nodes, VNQM uses CLI credentials.To edit CLI credentials, complete the following steps:

1. Log on to your VoIP and Network Quality Manager server using anaccount with administrator privileges.

2. Click VoIP & Quality Settings in the top right of the VoIP and NetworkQuality tab.

3. Click Manage Gateways.4. Select the node you want to edit, and then click Edit CLI Credentials.

109

Editing CLI Credentials for Gateway Nodes



http://www.solarwinds.com/documentation/helploader.aspx?topic=OrionCoreAGEditingDeviceProperties.htm


5. Select the appropriate settings from the Select Credentials list or definenew credentials.To define a new set of CLI credentials:

l Select Credentials: Type the name of the new credential set.l Username: Type the user name.l Password: Type the password.l Enable Level: Select the enable level to use when logging in.Note: The enable level must have privileges to execute terminalcommands. VoIP and Network Quality Manager uses Showcommands to fetch and display data from the gateway. Forinformation about configuring network devices, see yourmanufacturer’s documentation.

l Enable Password: Type the password associated with the enablelevel to use when logging in.

6. Expand Advanced, and then select the Protocol, Port Number, andConnection Timeout you want to use when connecting to your networkdevices.

7. Click Test to test the credentials.8. Click Save to apply your changes.

Removing Gateways

If you want to stop monitoring the PRI trunk utilization of a gateway, remove thegateway from VNQM.To remove gateway nodes from VNQM:


Quality tab.3. Click Manage gateways.4. Select one or more gateways that you want to remove.5. Click Remove Gateways, and then click OK to confirm.

110

Selecting VoIP and Network Quality Manager InfrastructureIn VoIP and Network Quality Manager you can monitor the health and status ofyour IP SLA and VoIP devices in the VoIP Infrastructure resource on the VoIPSummary View page. To use this resource, select VoIP nodes which form theVoIP infrastructure.To specify VoIP infrastructure for VNQM:


Quality tab.

3. Click Select VoIP nodes.

4. Click the + in front of the name of manufacturers to see the availabledevices.

5. Make sure you only select the nodes that you want to see in the VoIPInfrastructure resource.Notes:

l If you do not see an expected VoIP-related device or interface inthe list, use the Web Console to add the device to the database.For more information, see Adding Devices for Monitoring in theWeb Console in the SolarWinds Network Performance MonitorAdministrator Guide.

l If you are adding a VoIP simulation node and you want VNQM toautomatically discover its IP SLA operation configuration, you mustprovide an SNMP read/write community string when you add thedevice.

6. When you have selected all nodes that are a part of your VoIPinfrastructure, click OK to confirm your settings.

111

Selecting VoIP and Network Quality Manager Infrastructure




Call Precedence LevelsThe priority of a call is indicated by the call precedence level. The followingtable contains the list of possible call precedence levels.

Call precedence level Call priority

0 Flash override

1 Flash

2 Immediate

3 Priority

4 Routine

VoIP and Network Quality Manager SettingsThe following sections provide information about the settings you can define inVoIP and Network Quality Manager.

l VNQM Settings Overviewl Configuring VNQM (Example Workflow)l Setting Traffic Precedence

VNQM Settings OverviewThe VoIP and Network Quality Manager Settings page gives an overview ofthe configuration pages within VoIP and Network Quality Manager.To access this page:


Quality tab.

The following settings of VoIP and Network Quality Manager can beconfigured from this page.

112

IP SLA Management

This section provides links for managing IP SLA nodes and operations. Formore information, see IP SLA Management in the VoIP and Network QualityManager Administrator Guide.

Manage IP SLA Operations

By using the links in this section you can add, edit or delete IP SLA operationson your network. Each IP SLA operation on your network is associated with adesignated simulation node.Notes:

l IP SLA operations are limited to locations where there is an existing,Cisco IP SLA-compatible router or switch to serve as a simulation node.For more information about Cisco IP SLA-capable routers and switches,go to www.cisco.com/go/fn, click Research Features, select Search byfeature, and then select IP SLAs – UDP Based VoIP Operation.

l Only nodes added to the database are available for IP SLA Managermonitoring.

Manage IP SLA Nodes

By using the links in this section you can add, edit and remove IP SLA devicesfrom VoIP and Network Quality Manager. For more information, see AddingNodes to VoIP and Network Quality Manager in the VoIP and Network QualityManager Administrator Guide.

VoIP Management

By using the links in this section you can manage your VoIP network: callmanagers, gateways, and VoIP infrastructure.For more information, see VoIP Management in the VoIP and Network QualityManager Administrator Guide.

Manage CallManager Nodes

By using the links in this section you can specify and manage the devices onyour VoIP network that are Cisco CallManager, CallManager Express, andAvaya Communication and Media Server devices.

113

IP SLA Management

http://www.cisco.com/go/fn


Note:Only nodes added to the database are available for VoIP and NetworkQuality Managermonitoring.

Manage VoIP Gateways

By using the links in this section you can specify and manage devices on yourVoIP network that are gateways.

Select VoIP Infrastructure

By using the Select VoIP nodes link you can select VoIP-related nodes andinterfaces from your database and then display them in the VoIP Infrastructureresource.VoIP and Network Quality Manager can monitor any node that is relevant toyour VoIP network, provided you have first added the node. By expanding thegiven node trees, you can choose to monitor VoIP traffic down to the interfacelevel. VoIP and Network Quality Manager provides a number of default alerts,reports, and resources with which you can constantly monitor all of your VoIPdevices.For more information about adding devices and interfaces, see Adding Nodesto VoIP and Network Quality Manager in the VoIP and Network QualityManager Administrator Guide.For more information about alerts and reports in VoIP and Network QualityManager, see Using VoIP and Network Quality Manager in the VoIP andNetwork Quality Manager Administrator Guide.

Details

By using the options in this section you can configure general VNQM options,and view database details.

Edit VoIP and Network Quality Manager Settings

Links in this section present general options regarding your configuration ofVoIP and Network Quality Manager. From the VoIP and Network QualityManager Settings page, you can configure the following:

l The port through which VoIP and Network Quality Manager sendssimulated traffic.

l The jitter codec that VoIP and Network Quality Manager simulates onyour network.

114

l The interval at which VoIP and Network Quality Manager collects dataabout your network.

l The length of time that the collected data is retained in the database.l The MOS advantage factor that appropriately characterizes your VoIPnetwork for the purpose of determining the Mean Opinion Score (MOS).

l The Type of Service (ToS) octet allows you to set precedence levels forVoIP traffic and IP SLA operations.

l Whether you can view operations created by VoIP and Network QualityManagerin the running configurations on your Cisco devices.

l Which calls are successfully completed.l The timeout period of CDR/CMR data collection.l Whether you want to enable automatic Avaya Call Manager detection.

For more information, see Configuring VoIP and Network Quality ManagerSettings in the VoIP and Network Quality Manager Administrator Guide.

Database Details

The VoIP and Network Quality Manager Database Details page providesinstallation and memory sizing information for your database. From this viewyou can read statistics concerning individual tables within your database.Select a table from the list to see a count of rows and memory usage by dataand indexes, respectively.

Configuring VoIP and Network Quality Manager SettingsThe following steps guide you through the process of configuring VNQM on theVoIP and Network Quality Manager Settings page.Note: VoIP and Network Quality Manager maintains default values for thesesettings. If you want to use the default settings, click Restore Defaults.To edit VoIP & Quality Settings:


Quality tab.3. Click Edit VoIP & Network Quality Manager settings in the Details

section.

115

Database Details


4. If you want to use a port other than the default for simulated VoIP traffic,type your preferred port in the VoIP UDP Port field.

5. Select the VoIP Jitter Codec you are using for your VoIP network. Formore information about jitter codecs, see Jitter in the VoIP and NetworkQuality Manager Administrator Guide.

6. Type a CallManager Polling Interval in minutes to specify how often youwant to collect your call manager data.

VoIP and Network Quality Manager measures the performanceof your network by periodically sending test packets overdefined paths. The period between measurements is referredto as the polling interval. As network sizes and VoIP serverperformance vary, you may have to try a number of differentintervals to achieve the necessary balance between serverprocessing load and data resolution.

7. Type the period of time, in days, to retain IP SLA operation statistics inthe IP SLA Data Retention field.

VoIP and Network Quality Manager stores statistics regardingthe performance of your VoIP network in your database. Thelength of time this data is retained is configurable, allowing youto balance database maintenance with IP SLA requirements.As network sizes and VoIP server performance vary, you mayhave to try different retention periods to achieve the necessarybalance between database memory allocation and dataretention.

116

8. Type a value for the MOS Advantage Factor.Note: The advantage factor measures on a scale of 0 to 20 thewillingness of VoIP network users to trade call quality for convenience.For example, a cellular telephone is more convenient than a wiredtelephone, so some loss of call quality due to compression over a cellularphone network, as compared to call quality over a wired phone network,is acceptable to most users. This distinction is reflected in a higheradvantage factor for a cellular phone network than for a wired phonenetwork. For more information, see Mean Opinion Score (MOS) in theVoIP and Network Quality Manager Administrator Guide.

9. Provide a value for the Type of Service (ToS) octet to set theprecedence of VoIP traffic on your network.Note: The ToS octet is a decimal value (0-255) that sets the precedencefor VoIP traffic monitored with Cisco IP SLA operations. The default ToSvalue used by VoIP and Network Quality Manager is 184, correspondingto Expedited Forwarding (EF) per hop behavior (PHB) and aDifferentiated Service Code Point (DSCP) value of 46. For moreinformation about the ToS octet, see Setting Traffic Precedence in theVoIP and Network Quality Manager Administrator Guide.

10. SelectOperations in running configurations to view all newoperations created by VoIP and Network Quality Manager in the runningconfigurations on Cisco devices. You cannot view VoIP and NetworkQuality Manager operations created with CLI credentials.

11. Type in the call termination codes that you want to represent successfullycompleted calls in Successful call termination codes.

12. Enter the time period that you want to wait before ending the CDR/CMRjob in hh:mm:ss format in the CDR/CMR job timeout field.

13. Select whether you want to enable the detection of Avaya CallManagers. If the Avaya Call Manager Detection option is enabled,VNQM automatically detects Avaya Call Managers when you add callmanagers through the Add Call Manager wizard. For more informationabout adding Avaya Call Managers, see Adding Avaya Call ManagerDevices. If you use a load balancer, it is recommended that you disablethis option, and add the load balancer directly to VNQM.

117

Configuring VoIP and Network Quality Manager Settings


14. Type in the VoIP Gateway Polling Interval in minutes to specify howoften the status of your VoIP gateways and their calls should be checked.

15. Type in a value for the VoIP Gateway Critical Threshold in percent tospecify when you want to be warned that the channel utilization of yourgateways is critical.

16. Type in a value for the VoIP Gateway Warning Threshold in percent tospecify when you want to be warned that the channel utilization of yourgateways is high.

17. Specify how long your VoIP gateway statistics should be retained in theVoIP Gateway Retention Period field.

18. Click OK after you have finished configuring your VoIP and NetworkQuality Manager settings.

Setting Traffic PrecedenceIn VoIP and Network Quality Manager you can set the precedence, or packetpriority, of your network traffic. Setting precedence levels for your trafficenables you to better ensure high quality of service on your network. VoIP andNetwork Quality Manager employs a decimal Type of Service value specifiedon the VoIP and Network Quality Manager Settings page. For moreinformation, see Configuring VoIP&Network Quality Settings in the VoIP andNetwork Quality Manager Administrator Guide. The Type of Service valueused by VoIP and Network Quality Manager corresponds to the per hopbehavior (PHB) and the Differentiated Service Code Point (DSCP) values asshown in the following table.

118

119

Setting Traffic Precedence

Using VoIP and Network QualityManagerVoIP and Network Quality Managerfocuses on the IP SLA operations and VoIPinfrastructure of your network.The following sections introduce basic tasks you can accomplish with VNQM:

l Starting VNQMl Exploring VNQM Viewsl Customizing Charts in VNQMl Using Custom Propertiesl Using VNQM Alertsl Using VNQM Reportsl Using VNQMMaps

Starting VNQMVoIP and Network Quality Manager opens in a web browser. The defaultHome tab provides a selection of the most relevant resources for monitoringyour network.To start VoIP and Network Quality Manager:

1. Log on to your VoIP and Network Quality Manager server.2. Start the Orion Web Console in the Orion program folder.3. Click the VoIP and Network Quality tab.

Note: You can also open VoIP and Network Quality Manager in a webbrowser by filling in the name or IP address of the server with your VNQMinstallation, such as http://oriondemo.solarwinds.com/Orion/.

120

Using VoIP and Network Quality Manager

If you use another port than the default 80, you need to add it to the address. Ifport 8080 is used, the address opening your VNQM in a web browser lookslike the following: http://oriondemo.solarwinds.com:8080/Orion/.

Exploring VNQM ViewsVoIP and Network Quality Manager presents current network performancemetrics in easy-to-review tables, graphs, and charts.VNQM data is provided in resources that are displayed on views.A View is a web page providing a framework for displaying information aboutyour VoIP calls and IP SLA operations in relation to individual nodes. Viewscontain resources. You can customize which resources you want to have on aview.Selected views offer optional, fully customizable subviews that allow you tomore extensively organize the resources that are available in your webconsole. For more information about subviews, see Using and ConfiguringSubviews in the SolarWinds Network Performance Monitor AdministratorGuide.The following two basic types of views are available:

l Summary views show VoIP or IP SLA details on all nodes andoperations managed by VNQM. You can access your summary views inthe VoIP and Network Quality menu bar. For more information aboutcustomizing the menu bar, see Customizing Web Console Menu Bars inthe SolarWinds Network Performance Monitor Administrator Guide.

l Detail views show traffic information about individual objects in your IPSLA and VoIP infrastructure. You can access your detail views byopening a summary view and clicking the object whose details you wantto see.

Resources are displayed on your views as a box and provide informationabout different aspects of your VoIP infrastructure or IP SLA operations usuallyin a chart and a table.Some resources are meant to be used on summary views, some are suitablefor detail views, and some can be useful on both view types. The informationshown pertains to either all devices VoIP and Network Quality Managermonitors (if used on a summary view) or to the selected object (if used on adetail view for a node, interface, gateway or call manager, or other object).

121

http://www.solarwinds.com/documentation/helploader.aspx?topic=OrionCoreAGUsingConfiguringSubviews.htm

http://www.solarwinds.com/documentation/helploader.aspx?topic=OrionCoreAGUsingConfiguringSubviews.htm

http://www.solarwinds.com/documentation/helploader.aspx?topic=OrionCoreAGCustomizingWebConsoleMenuBars.htm

For more information about customizing VoIP and Network Quality Managerviews, see Customizing Views in the SolarWinds Network PerformanceMonitor Administrator Guide.The following views are provided with VoIP and Network Quality Manager:IP SLA Operation Details View

Provides information about a single IP SLA operation instance. This viewprovides troubleshooting information for that instance.

IP SLA Summary ViewProvides an overview of the entire network, including resources thatpresent information about IP SLA operations, IP SLA network maps,events and alerts, and overall performance metrics.

IP SLA Top 10 ViewProvides several resources containing lists of the top ten operations bycategory. These lists provide a quick overview of potential problem areason your network.

IP SLA Web Summary ViewProvides an overview of your web-based operations, including resourcesthat present information about web operations, events and alerts, andoverall performance metrics.

VoIP Call Details ViewDisplays detailed information about a single call.

VoIP Call Path ViewDisplays information about a single VoIP call path. This providesinformation about the originating VoIP site of the call path.

VoIP Call Manager Gateway ViewDisplays information about a gateway which has been registered with acall manager.

VoIP CallManager ViewProvides information about a single call manager instance, includinginformation about the server or router that hosts the call managerinstance.

VoIP Gateway ViewProvides detailed information about a single VoIP gateway or endpoint.

122

VoIP CallManager View

http://www.solarwinds.com/documentation/helploader.aspx?topic=OrionCoreAGCustomizingViews.htm


Location ViewDisplays information about a single VoIP location.

VoIP Phone Details ViewDisplays information about a single VoIP CCM Phone.

VoIP Site ViewDisplays information about a single VoIP Site. A VoIP Site is an IP SLAnode with an operation.

VoIP Summary ViewProvides an overview of your entire VoIP network, including resourcesthat present information about VoIP devices, VoIP-related events andalerts, call paths, and overall performance metrics.

VoIP and Quality SubviewThis subview is shown as the left navigation tab VoIP and Quality fornode detail views which are provided by SolarWinds NetworkPerformance Monitor.

It provides VNQM-relevant information pertaining to a selectednode directly from the node view. The displayed informationdepends on how the node was added to VNQM:

l GatewayThe subview provides information about the node from the gateway pointof view. Resources shown here include Data Distribution, Failed Calls,Top 10 Quality and Trunk Utilization.

l Call ManagerThe subview provides information relevant for the node as a CallManager. Here you can find resources such as Call Manager Stats,Failed Calls, Registered and Unregistered Phones chart, DisconnectCauses, and Connected Phones.

l IP SLA nodeThe subview displays the IP SLA Operations resource which providesinformation about IP SLA operations created on the selected node.

123

l Gateway and IP SLAIf a node has been added to VNQM as both a gateway node and anIP SLA node, the VoIP and Quality subview displays both gateway andIP SLA operations relevant for the selected node, that is, DataDistribution, Failed Calls, Top 10 Quality Issues, Trunk Utilization, and IPSLA Operations.

Customizing Charts in VNQMCharts produced within the Orion Web Console are customizable.To customize a chart, click Edit in the top right corner of the appropriateresource and use the customization options available on the correspondingEdit Resource page.The following sections describe options that are available on the CustomizeChart page to modify the presentation of a selected chart:

l Chart Titlesl Calculated Seriesl Time Periodl Sample Intervall Chart Sizel Data Tablesl Font Sizel Printing Optionsl Data Export Optionsl Advanced

Note: Click Refresh at any time while customizing a chart to review thechanges you have made.

Chart TitlesChart Titles are displayed at the top center of a generated chart. In the ChartTitles area you can modify the title and subtitles of your generated chart.

124

Customizing Charts in VNQM


Network Performance Monitor provides default chart titles andsubtitles. To restore the default values, clear the respective fieldswhen editing chart titles, and then click Submit.

Calculated SeriesIn your graphs, you can display markers calculated from historical data. Byusing these markers, you can compare the current situation with the calculatedseries.To display markers in the graph, select the appropriate options:

l Show a trend line displays the trend line, allowing you to see potentialfuture results as they are extrapolated from collected historical data.

l Show the sum of all data series displays a line showing the total of allobjects graphed.

l Show the 95th percentile line displays the 95th percentile marker. Formore information, see 95th Percentile Calculations in the SolarWindsOrion Core Administrator Guide.

Note:Only the options applicable for the particular resource are available.

Time PeriodYou can designate a predefined or custom time period for your chart by usingany of the available methods:

l Select a predefined time period from the time period list.l Select the Select custom period option, and then provide custom Startand Ending Dates/Times in the appropriate fields.

Some charts define the time period they show using the following options:

l Default zoom range: Select the time period to be displayed in the graphor chart per default. You can see this information by default below thechart title.

l Amount of historical data to load: Select the time period for which thedata should be loaded. You can display this data dynamically using theslider below the chart.

125

http://www.solarwinds.com/documentation/helploader.aspx?topic=OrionAG95thPercentileCalculations.htm

l Sample interval: Select the time interval which you want to see in thegraph as a single point or bar.Note: Data within the defined sample is summarized automatically.

Sample IntervalThe sample interval dictates the precision of your generated chart. A singlepoint or bar is plotted for each sample interval. If a sample interval spansmultiple polls, polled data is automatically summarized and plotted as a singlepoint or bar on the chart.Note: Due to limits of memory allocation, some combinations of time periodsand sample intervals may require too much system resources to display, due tothe large number of polled data points. As a result, charts may not be displayedif the time period is too long or if the sample interval is too small.

Chart SizeChart size options configure the width and height, in pixels, of the chart. Youcan maintain the same aspect ratio, or scale the chart in size, by entering awidth, and then entering 0 for the height.

Data TablesThe Data Table Below Chart option displays a table of the charted data pointsbelow the chart.Note: You may not be able to read individual data points if you select a smallsample interval. Select a larger sample interval to more easily read data points.

Font SizeGenerated charts have variable font sizes. By using the Font Size option youcan select a small, medium, or large size font for your chart labels and text.Note: Font size selections are maintained in the printable version of your chart.

Printing OptionsTo print your customized chart, click Printable Version. A printable version ofyour customized chart is displayed in the browser.

126

Sample Interval


Data Export OptionsExportable chart data is also available from selected charts in the DisplayData from Chart area. Data can be exported as Microsoft Excel-compatibleRaw Data or as HTML-formatted Chart Data.To export chart data, click Raw Data, and then follow the prompts to open orsave the resulting raw data file.

AdvancedBy using this option you can modify the title and subtitle of your generatedchart. Chart titles are displayed at the top center of a generated chart.To modify the chart title and subtitle:

1. Click + next to Advanced.2. Fill in the appropriate Chart title or Chart subtitle.

Note: SolarWinds Orion may provide default chart titles and subtitles. If youedit any of them, you can restore the default titles and subtitles by clearing therespective fields, and then clicking Submit.

Using Custom Properties for VNQMBy using the Orion Custom Property Editor, you can simplify the task ofmonitoring your network. By using the Custom Property Editor you can definecustom properties, such as country, building, asset tag, and serial number.These properties may apply to any device or operation that you have stored inthe SolarWinds VoIP and Network Quality Manager database. After propertiesare added, they are available for display and filtering within any Orionapplication. A few examples of how custom properties can be used are asfollows:

l Add a custom property and display it as an annotation on a chart.l Add a custom property to interfaces to display a custom description.l Add a custom property that is used as an account limitation on sites.l Add additional information to sites, such as contact, owner, or supportcontract number.

l Add a notification property to sites that can configure the alerts feature tosend an email to a computer named within the custom property.

127

l Add a custom property to routers and interfaces for grouping them on theweb or in a report.

l Add a custom property of billing codes or customer IDs.

In the Custom Property Editor you can choose from a collection of commonlyused properties, or you can build your own custom properties. After yourcustom property is defined, you can use the Custom Property Editor topopulate your custom property with appropriate values or you can use theImport Wizard to populate the new property from either a text file or acomma-delimited file. For more information about creating custom propertiesfor VoIP and Network Quality Manager, see Creating a Custom Property in theSolarWinds Network Performance Monitor Administrator Guide.

Using Alerts and Alert Actions in VNQMAs of Core version 2015.1 (VNQM version 4.2.2), alerts are no longer createdwith the desktop-based, Advanced Alerts Manager or Basic Alerts Manager.Alerts are instead created and managed in the SolarWinds Orion WebConsole. See Creating and Managing Alerts for more information.

Creating and Managing AlertsAn alert is an automated notification that a network event has occurred, suchas a server becoming unresponsive. The network event that triggers an alert isdetermined by conditions you set up when you configure your alert. You canschedule alerts to monitor your network during a specific time period, andcreate alerts that notify different people based on how long the alert has beentriggered.The types of events for which you can create alerts vary, depending on theOrion platform products you have installed. For example, you can create analert to notify you if a node in a specific location goes down or if the networkresponse time is too slow when you have NPM. If you have installed SAM, youcan receive alerts about application response times or when your Exchangemailbox database is almost full.You can create alerts for any monitored object. Most Orion platform productsallow you to alert against at least Interfaces, Volumes, and Nodes.Use the following topics to get started if you have never used Orion platformproducts:

128

Using Alerts and Alert Actions in VNQM

http://www.solarwinds.com/documentation/helploader.aspx?topic=OrionCoreAGCreatingCustomProperties.htm


l Alert Preconfiguration Tasksl Best Practices and Tips for Alertingl Navigating to the Alert Managerl Creating New Alertsl Alert Me When a Server is Down

Use the following topics to get started with web-based alerts if you haveupgraded to Core version 2015.1.2:

l Changes in the Alerting Enginel Setting Custom Statusl Building Complex Conditions

You can also view our Alert Lab on thwack for community-based alertinformation.

Alert Preconfiguration Tasks

Some alerts require extra configuration, separate software installations, orspecific information input.Alert actions that must be set up before creating or configuring alerts include:

l Sending an Email/Pagel Dialing a Paging or SMS Servicel Playing a Soundl Sending an SNMP Trapl Creating Text to Speech Output

Note:Make sure there are monitored objects in the SolarWinds Oriondatabase before creating or configuring alerts. Monitored objects can includeitems such as nodes, databases, and applications.

Sending an Email/Page

This action sends an email from the product to a selected recipient. First,configure the default SMTP server the product uses to send email. You canchange the default SMTP server later or use different SMTP servers forspecific alerts.

129

http://thwack.solarwinds.com/community/labs_tht/alert-lab

http://thwack.solarwinds.com/

Configure the SMTP server in the alert action or from the Settings page. Youneed the following information:

l The SMTP host name or IP addressl The SMTP port numberl Whether the SMTP server uses SSLl The SMTP credentials, if necessaryl Default sender email address

For instructions on creating an action to send an email/page, see Sending anEmail/Page.

Dialing a Paging or SMS Service

This action forwards alerts to a paging or SMS service. Enable this capabilityby downloading and installing NotePager Pro from Notepage.net to yourSolarWinds Orion server.For instructions on configuring this action, see the NotePage TechnicalSupport page, at http://www.notepage.net/solar-winds/technicalsupport.htm.

Playing a Sound

The Play a Sound action uses the SolarWinds desktop notification client toplay the sound on your computer when an alert arrives.You must download and install the client on every computer that you want toplay a sound when an alert arrives. After installing the desktop notificationclient, configure which sound you want to play when an alert is received.Computers that do not have the desktop notification client installed on them donot play a sound when an alert arrives. If you want an alert notification sound toplay on your desktop or laptop, you must install and configure the desktopnotification client on that computer.Download the desktop notification client from <Your SolarWinds Orionserver>/DesktopNotificationTool/SolarWinds.DesktopNotificationTool.msi.Run the installer and follow the on-screen instructions to install the client.The desktop notification client requires the following information to connect toyour SolarWinds Orion server and receive alerts:

130

Dialing a Paging or SMS Service

http://www.notepage.net/solar-winds/orion.htm

http://www.notepage.net/solar-winds/technicalsupport.htm


l Orion Server Name or IP Addressl Orion User Namel Password

You can use the server name and credentials that you use to logon to yourSolarWinds product.For instructions on creating an action to play a sound, see Playing a Sound.

Sending an SMNP Trap

Configure this action to enable SolarWinds Orion to send an SNMPnotification. Creating this action requires the following information:

l UDP port numberl SNMP version numberl SNMP credentials

For instructions on creating an action to send an SNMP trap, see Sending anSNMP Trap.

Creating Text to Speech Output

The Text to Speech Output action uses the SolarWinds desktop notificationclient and your computer's speech synthesizer to convert text messages-to-speech messages. The action notifies users of new alerts by reading the alertout loud. This capability is especially helpful for users who are visuallyimpaired or who are not always at their desks to read alerts onscreen.Download and install the client on each computer that you want to play asound. Then configure which synthesizer you want to play.For instructions on set up an action to create text-to-speech output, see UsingText to Speech Output.

Configuring the Default Email Action

Email alert actions require a designated SMTP server. The Settings pageenables you to configure a default SMTP server and any default sender orrecipient details.Note: Separate email addresses with a semicolon.

131

To configure default email alert action settings:

1. Click Settings > Configure Default Send Email Action.2. Under the Default Recipients heading, provide the email addresses of

all default recipients for any email alert action, like the following:[email protected]; [email protected];[email protected]

3. Under the Default Sender Details heading, provide the default Name ofSender and the default Reply Address.

4. Under the Default SMTP Server heading complete the following steps:

a. Provide the Hostname or IP Address of your SMTP Server andthe designated SMTP Port Number, such as 192.168.10.124, port25. This is a required field.

b. If you want to use SSL encryption for your alert emails, select UseSSL.Note:Opting to use SSL automatically changes the SMTP portnumber to 465.

c. If your SMTP server requires authentication, select This SMTPServer requires Authentication, and then provide requestedcredentials.

Navigating to the Alert Manager

Use the Alert Manager to create, edit, delete, enable, or disable alerts. You canaccess the Alert Manager in one of four ways:

l Settings Page (Recommended)l Active Alerts Detailsl All Active Alerts Resourcel Node Details

Settings Page (Recommended)

SolarWinds recommends using the Settings page to navigate to the AlertManager.

132

Navigating to the Alert Manager


1. Click Settings.2. Under Alerts & Reports, click Manage Alerts.

All Active Alerts Resource

From the All Active Alerts resource, click Manage Alerts in the right side.

Active Alerts Details

From the Active Alerts Details page, click Manage Alerts in the Managementresource.

Node Details

On the Node Details page, navigate to the All Alerts this Object can triggerresource.Click Manage Alerts.

Best Practices and Tips for Alerting

Use the following best practices and tips to help you configure and test youralerts.

Use the Out of the Box Alerts as Templates

SolarWinds recommends using the alerts that are included when you installthe product as templates for your new alerts.Find an alert that is similar to one you want to create and click the Duplicate& Edit button. Not only does this pre-populate fields for you, but it also allowsyou to skip to specify parts of the Alert Wizard that have data you want tochange.

Restrict Who Receives Alerts

During your initial evaluation and testing, send alerts to a few people instead ofsending alerts to a large distribution list. This can prevent overloading youremail server while you fine-tune your alerts.

Plan which Devices to Monitor

133

To reduce the number of alerts sent out, consider which devices are mostimportant. For example, you may want to receive alerts only for mission criticalinterfaces instead of every interface on a device.

Establish Dependencies

Establishing dependencies prevents you from receiving duplicate alerts thatstem from a single network event. For example, you may want to be emailed ifservers in your server farm go down, but if the router goes down and theservers can no longer be polled, you do not want to receive notifications for allof your servers.

Creating New Alerts

SolarWinds provides an Alert Wizard to guide you through creating or editingalerts.To create a new alert definition, navigate to the Alert Manager, and click AddNew Alert.You can also select an alert that is similar to the alert you want to create andclick Duplicate & Edit.

Note: You can skip to different steps after you have saved an alert or if youclicked Duplicate & Edit.Properties

Provide information about the alert, including its name, severity, howfrequently you want to evaluate the conditions, and if you want to restrictaccess to the alert using account limitations.

See Setting Alert Properties for more information.Trigger Condition

Use the trigger condition to define what event must occur to activate youralert. Trigger conditions can be as simple as a node going down or ascomplex as multiple SQL statements.Note: While SolarWinds provides a method to create SQL conditionsmanually, SolarWinds support is not provided. Visit thwack, SolarWinds'community website, for support from other users.

See Setting Trigger Conditions and Building Complex Conditions for moreinformation.

134

Establish Dependencies

https://thwack.solarwinds.com/


Reset ConditionUse the reset condition to define what must occur to remove an alertinstance from the active alerts list. For example, the "Email me when aNode goes down" alert automatically resets when the node comes backup. You can use the built-in reset conditions or create your own.

See Setting Reset Conditions for more information.Time of Day

Schedule when you want to monitor your network for the triggerconditions you created for the alert. You can create multiple schedulesthat control when an alert is enabled or disabled. For example, you candisable an alert during maintenance windows.

See Setting the Time of Day or Schedule for more information.Trigger Actions

Use trigger actions to define what happens when the trigger conditionsare met. By default, a triggered alert creates an entry in the Active Alertsresource with a configurable message.All other trigger actions, such as Send an Email/Page or Write to a Log,must be configured.

See the following for more information:

l Setting Trigger Actionsl Available Alert Trigger Actions

Reset ActionsUse reset actions to perform specific tasks when an alert is no longeractive, such as writing to the log that the issue has been acknowledged.Reset actions are usually used to notify others that the situation has beenresolved or to write the resolution to a log file.

See Setting Reset Actions for more informationSummarySee Reviewing the Alert Summary for more information.

Setting Alert Properties

After creating a new alert, use the Alert Properties to describe the alert,including which users can view the alert.

135

Enter the following information as necessary:Name of alert definition

This is a required field. SolarWinds recommends a name that describesthe condition and most visible alert action. For example, you can use"Email NetAdmins when router goes down" as the name of an alert. Thename is displayed in the Alert Manager and can be used to sort youralerts. If you intend to create a large number of alerts, you may want toconsider a naming convention that allows you to quickly scan through theAlert Manager.

Description of alert definitionDescribe the alert. This is displayed on the Manage Alerts page, soimportant information should be near the front.

Enabled (On/Off)Choose to evaluate the alert immediately after it is created and saved.The alert is enabled. If you are in the process of refining your alert, youmay want to disable this alert until it is ready for use.

Evaluation FrequencySolarWinds recommends using intervals longer than 1 minute toevaluate alert conditions. Shorter frequencies may put an undue burdenon your network performance or computing resources.If you elect to alert on an event, such as a changed IP address, thecondition is not evaluated by frequency, but by when the change isreported based on the polling interval.

Reduce the evaluation frequency to decrease your poller anddatabase loads.

Severity of AlertThis controls the appearance of the alert in the Active Alerts resourceand allows you to group or filter alerts more easily.

136

Setting Alert Properties


Alert Custom PropertiesThese help organize your alerts. For example, you can create a"Responsible Team" custom property and use it to help audit whoreceives specific alerts. You must create a custom property for alertsbefore you can assign a custom property to an alert.

Use custom properties to group your alerts in the Alert Manager or tocreate reports about alerts.

Alert Limitation CategoryUse this to restrict who can view the alerts. For example, managedservice providers can restrict alerts to their specific customers. If youcreate a new limitation, go to Settings > Users and add the newlimitation to the appropriate user accounts.

Setting Trigger Conditions

The trigger condition is the most complex step in creating an alert. Before youbegin, you may want to revisit the Best Practices and Tips for Alerting topic. Tosee an example of completed trigger conditions, see the Alerting When aServer is Down topic.Trigger conditions are built using child conditions that are evaluated in order.Child conditions are represented as a line item under the Actual TriggerCondition. You can have multiple trigger condition blocks with multiple childconditions.

Filter your environment to just the objects you want to monitor in Thescope of alert. Use the Show List link to view all of the objects thatthe alert monitors.

137

To set trigger conditions:

1. Choose what objects you want to monitor in the I want to alert on field.2. Establish how much of your environment you want to monitor in The

scope of alert.

You can monitor all objects in your environment or filter your environmentto a specific set of objects.

3. Create your trigger condition.

a. Choose if the child conditions must be true or false to trigger thealert.

l All child conditions must be satisfied (AND) - Every childcondition must be met

l At least one child condition must be satisfied (OR) - Atleast one child condition must be true

l All child conditions must NOT be satisfied - Every childcondition must be false

l At least one child condition must NOT be satisfied - Atleast one child condition must be false

b. Click the + sign to add child conditions.

l Add Single Value Comparison (Recommended) - Thechild condition evaluates a single field, like Status

l Add Double Value Comparison - The child condition

138

Setting Trigger Conditions


evaluates two conditions, such as Status and OSl Add And/Or block - Adds a sub condition block

Tip: Use the X at the end of each child condition to delete it, or usethe drop-down at the top of the block to delete the entire condition.

c. Select the object you want the child condition to evaluate, and thenselect which field you want to evaluate. In the example screenshot,the object is "Node" and the field is "Status".Tip: You can evaluate objects based on variables or macros.

d. Select how you want to compare the polled value of the field to thevalue entered here, and then enter the value. In the examplescreenshot, the comparison is "is equal to" and the value is"Down".

e. To use more complex conditions, such as evaluating when anapplication on a specific server is down and different application onanother server is down, enable complex conditions underAdvanced options. See Building Complex Conditions for moreinformation, or visit thwack, SolarWinds' community website, forsupport from other users.

f. Choose how long the condition must exist before an alert istriggered. This prevents receiving alerts when the alert condition,such as high CPU utilization, occurs briefly or only once during acertain time period.

l To immediately send an alert when the condition is met, clearany selection for Condition must exist for more than.

l To wait before sending an alert, select Condition must existfor more than, and enter how long the condition must exist.This option prevents multiple alerts firing if the condition istemporary.

Setting Reset Conditions

Reset conditions remove alerts from Active Alerts. You can also create resetactions that occur when the reset conditions are met.

139


For example, you can create an alert that triggers when nodes in your lab godown. If node 192.168.4.32 goes down, the alert fires for that specific instanceof the trigger condition and any escalation levels you create will continue untilyou reset the alert. Once the alert is reset, all trigger actions stop and a newalert fires the next time node 192.168.4.32 goes down. If you have createdreset actions, the reset actions fire.Note: When the alert is reset, escalation actions are halted.Select one of the following reset conditions:

l Reset this alert when trigger condition is no longer true(Recommended)SolarWinds recommends using this reset condition. If the triggercondition is no longer true when the objects are next polled, thisselection will automatically reset the alert.You may want to use the Condition must exist for more than option inthe trigger conditions in conjunction with this reset condition. Triggerconditions that involve volatile components, such as high CPUutilization, can trigger excessively with this reset condition.

l Reset this alert automatically afterSelect this to reset an alert after a set amount of time has passed. If thisinterval is less than the amount of time you wait for different escalationlevels, the escalation levels that occur after this interval do not fire. Thisreset condition is especially useful to remove event-based alerts fromActive Alerts.For example, if the trigger conditions still exists after 48 hours, you canuse this to trigger your alert actions again. The alert is reset and triggersas soon as the trigger condition is detected, which is as soon as theobjects are polled for this example.

l No reset condition - Trigger this alert each time the trigger conditionis metThe alert fires each time the trigger conditions are met.For example, when the alert for node 192.168.4.32 going down fires, anew alert for 192.168.4.32 fires every time the node is down when it ispolled.

140

Setting Reset Conditions


l No reset conditionThe alert is active and is never reset. To re-trigger the alert, the alert mustbe manually cleared from the Active Alerts view.

l Create a special reset condition for this alertSelect this to build a specific reset condition.For example, you can choose to reset the condition when the node hasbeen up for more than 10 minutes.See Setting Trigger Conditions or Building Complex Conditions for moreinformation on creating conditions.

Setting the Time of Day or Schedule

You can configure when an alert monitors your network. By default, alertsmonitor your network for changes all the time.Note: Alerts must be enabled to allow schedules to run.To schedule your alert:

1. Select Specify time of day schedule for this alert2. Click Add Schedule.

You can have multiple schedules for a single alert. For example, you canschedule the alert to monitor your network during off hours, and disable thealert during your maintenance windows.Enter the following information to schedule a monitoring period:

l Schedule NameThis is not required, but may help you organize or troubleshoot yourschedules. If you do not enter a name, a name is automatically generatedfrom the time period.

l Enable or Disable alert during following time periodIf you choose to disable the alert, it is enabled all other times unlessotherwise scheduled.

141

l FrequencyChoose when to monitor on a high level, such as daily, weekly, ormonthly.

l Enable everyThese options change based on the frequency.

l If you selected Daily...

You can choose to enable or disable the alert every few days, up toevery 31 days. You can also select specific business days. Forexample, you may want to disable network or disk activity alerts ifyou run daily, off-site backups of your critical data.

l Enter a time period

l To monitor or not for the entire 24 hour period, select All Day.

l To monitor or not during a specific time period during the day,enter a time and click Add Time Period.

l To monitor or not for a time period that spans midnight enter atime in the From field that is later in the day than the time inthe To field. For example, to schedule an alert between 11PMto 3AM, enter 11PM (or 23:00) in the From field and 3AM (or3:00) in the To field.

l If you selected Weekly...

Choose which days the alert is enabled or disabled. You may wantto disable alerts during a weekly maintenance window.




142

Setting the Time of Day or Schedule



l If you selected Monthly...

Choose which months the alert is enabled or disabled. This optionis useful when you have quarterly or monthly maintenancewindows.Choose either a specific date or a day.





l Starting onChoose a date to being the schedule.

l Right now - Start the schedule immediately.

l Specific Date - Select a time and day to begin the schedule.

l Ending onChoose and end date for the schedule, if necessary.

3. Click Add Schedule to create the schedule.

Setting Trigger Actions & Escalation Levels

143

Choose actions that occur whenever the trigger conditions are met. You canalso set up escalations levels so the alert triggers different actions if it has notbeen acknowledged quickly enough.Trigger Actions

By default, what you enter into the Message displayed when this alert istriggered field is displayed in the All Active Alerts resource.To add a trigger action:

1. Click Add Action.

2. Select an action from the list.See Alert Trigger Actions for a complete list of available actions.

3. Click Configure Action.

4. Enter the necessary information for the action.

Each action requires different information. Select from the list of AlertTrigger Actions for more information per action.Some actions require extra configuration steps, specific information, orspecial software. See Preconfiguration Tasks.Each action has the following sections:

l Name of action - This is not required, but can make it easier toorganize your Trigger actions.

l Time of Day... - You can choose different actions to occur atdifferent times of the day or month. For example, if you want to senda page, you might send it to a different person on weekends orholidays than during the week.

l Execution settings - You can select both options, neither option,or a single option.

l Do not execute this action if the alert has been acknowledgedalready (Recommended)

l Repeat this action every X minutes until the alert isacknowledged


144

Trigger Actions


Escalation Levels

Escalation levels in Orion platform products refer to user-defined time intervalsbetween when an alert is activated and when a user acknowledges that alert.You can configure the alert to perform different actions per escalation level.Escalation Level 1 contains all initial actions that you want to occur when thetrigger conditions are met and the alert activates.Escalation Levels 2 and above include all actions you want to occur if no oneacknowledged the alert during the previous escalation levels.For example, if an alert for a critical server activates and all of the recipient orfirst-level responders are out for training and do not acknowledge the alert,then the actions fire in the second escalation level. These actions may includeemailing managers or other backup staff.To escalate alerts:

1. In an existing alert, click Trigger Actions.2. Below the action, click Add Escalation Level.3. Choose how long you want to wait after the previous escalation level

before performing the actions in the new escalation level.4. Enter new actions in this escalation level.

You can copy all of the actions as Reset Actions to record that the issue hasbeen acknowledged or resolved. Click Copy Actions to Reset Actions Tab.

Setting Reset Actions

Choose actions that occur when the reset conditions are met and the alert is nolonger active.To add a reset action:

1. Click Add Action.2. Select an action from the list.

See Alert Actions for a complete list of available actions.

3. Click Configure Action.

145

4. Enter the necessary information for the action.

Each action requires different information. Select from the list of AlertActions for more information per action.Some actions require extra configuration steps, specific information, orspecial software. See Preconfiguration Tasks.Each action has the following sections:

l Name of action - This is not required, but can make it easier toorganize your Trigger actions.

l Time of Day... - You can choose different actions to occur atdifferent times of the day or month. For example, if you want to senda page, you might send it to a different person on weekends orholidays than during the week.

l Execution settings - You can select both options, neither option,or a single option.

l Do not execute this action if the alert has been acknowledgedalready (Recommended)

l Repeat this action every X minutes until the alert isacknowledged


To perform the same actions as when the alert was triggered, click CopyActions From Trigger Actions Tab. Use the copied trigger actions as a baseand modify them to reflect that the alert is no longer active.

Reviewing the Alert Summary

The Summary tab allows you to check your alert definition before you save anychanges.To modify any section, click Edit next to that section.To integrate your alerts with other SolarWinds products, such as AlertCentralor Web Help Desk, expand Alert Integration. Select as many variables as youneed to ensure that the variables are correctly translated for the other productsto use.

146

Reviewing the Alert Summary


Before you click Submit, review the information box above it. This box lists thenumber of objects that will trigger the alert immediately based on your currenttrigger condition.

Commonly Created Alerts

The following is a list of frequently created alerts. The topics walk you throughthe easiest method to create the alert and include tips on how to build morecomplex alerts.

l Alerting When a Server is Downl Creating an Alert to Discover Network Device Failures

Alert Me When a Server is Down

Use the following procedure to create an alert that writes to a log and emails amessage to you when a Windows server goes down.To create a new alert:

1. Click Settings > Manager Alerts.2. Search for "Email me when a Node goes down".3. Select the check box next to the alert, and click Duplicate & Edit.4. Enter a name for the alert, such as "Notify me when a Node goes down".5. Enable the alert.6. Click Trigger Condition or Next.7. In The scope of alert, selectOnly following set of objects.8. Select Node Machine Type is equal to Windows 2008 Server as the child

condition.>Tip: You can further refine your scope by entering another ANDcondition. For example, you can enter Node IP Address starts with10.10.45 to restrict the scope of the alert to a specific subnet.

147

9. The actual trigger condition should be Node Status is equal to Down.Tip: Select and enter a value for Condition must exist for more than toprevent being alerted when a node enters the down state frequentlywithin a set amount of time. This will prevent you from receiving alertsuntil the node has been in the down state for longer than the time youhave selected.Ninja Tip: You can further suppress alerts by enabling complexconditions in the Advanced options. This allows you to choose to waituntil multiple nodes are down before triggering a single alert.

10. Click Reset Condition. The default action should be to reset the alertwhen the node is up.

11. Click Trigger Actions.12. Under Trigger Actions, click Add Action.13. Select Log the Alert to a file, and then click Configure Action.

a. Click Browse (…) to open the default directory.b. Browse to an appropriate folder, and then type ExampleAlertLog

as the alert log file name.c. Click Save.d. In the Message text box, type Node ${N=SwisEntity;M=Caption} is

currently down.e. Click Add Action.

14. Click Add Escalation Level, and enter 5 minutes to wait for 5 minutesbefore escalating to the next level.

148

Alert Me When a Server is Down


15. Click Add Action in Escalation Level 2, and select Send anEmail/Page. Click Configure Action.

a. Enter your email as the recipient.b. Add a message.

Tip: You can use variables to customize your message. You canalso use a variable that allows you to acknowledge an alert fromemail (${N=Alerting;M=AcknowledgeUrl}).

c. Enter your SMTP server information if you have not already doneso.Tip: You can enter a default SMTP server that is used for all youremail in Settings > Configure Default Send Email Action.

d. Go to Execution settings to click Add Action.e. Click Add Action.

16. Click Copy Actions to Reset Actions Tab, and then click Next.17. Click Edit next to your logging action, and modify your message to Node

${N=SwisEntity;M=Caption} is back up.18. Click Edit next to your email action, and modify your message. You can

also delete the email if you do not want to know if the situation has beenresolved.

19. Click Summary, and review your alert definition.20. Click Submit.

Use a Custom Property in Alerts

The following example creates multiple alerts using the NodeLocation customproperty defined in Creating a Custom Property. An alert triggers when a nodegoes down. Upon triggering, the alert will write to a local log file, send a syslogmessage, and send an SNMP trap.Note: The ${variable} syntax is required for variables. For more information onthe use of variables, see Orion Variables and Examples.

149

To create a new alert:

1. Click Settings > Manage Alerts.2. Select the check box next to Node is down, and then click the Duplicate

& Edit button.3. Click Trigger Condition, and add a child condition. A child condition

should already exist for a node being down.4. Select the node object, and choose NodeLocation in the field drop-

down. Enter a comparison and value.5. Click the Trigger Actions, and then click Add Action.6. Select Log the Alert to a file, and then click Configure Action.

a. Enter the log filename in the Alert Log Filename field.b. In the Message text box, type the following:

Node ${N=SwisEntity;M=Caption} is currently down.c. Click Add Action.

7. Click Add Action, and select Send a Syslog Message. ClickConfigure Action.

a. Type 127.0.0.1 as the Hostname or IP Address of the SyslogServer, and then type the following in the Message field:Node ${N=SwisEntity;M=Caption} is currently down.

b. Click Add Action.

8. Click Add Action, and select Send SNMP Trap. Click ConfigureAction.

a. Type 127.0.0.1 as the SNMP Trap Destination, and then type thefollowing in the Alert Message field:Node ${N=SwisEntity;M=Caption} is currently down.

b. Click Next.c. Click Add Action.

9. Click Summary, and click Submit.

150

Use a Custom Property in Alerts


You can test your alert, and view the results of each of your alert actions asfollows. See Testing Alerts for more information.

l You can view results of your Syslog message action in the Web Consoleor through the Syslog Viewer on your SolarWinds Orion server.

l To view the results of your SNMP Trap action, click Start > AllPrograms > SolarWinds Orion > Syslog and SNMP Traps > TrapViewer.

Viewing Triggered Alerts

To view active triggered alerts, click Alerts in the Home view.You can also add the All Active Alerts resource to any view.

Acknowledging Alerts

When an alert has triggered and becomes active, you can then acknowledge it.After an alert is acknowledged, alert actions in higher escalation levels arehalted and the time it was acknowledged and the account that acknowledged itis recorded. You can also add notes that other users can read.Depending on your organization, acknowledging an alert can have differentpurposes outside of halting further notifications. The most common purposesare to provide an audit trail or to prevent multiple people from working on thesame issue.To acknowledge an alert:

1. Log in to the Orion Web Console using an account that has been grantedalert acknowledgment privileges.

2. Click Alerts on the Views toolbar.3. Click Acknowledge next to the alerts you want to acknowledge.

Tip: Depending on how you configure the email, you can acknowledge an alertdirectly from an email notification.To group active alerts:

1. Use the Group by drop-down to select how you want your alerts grouped.2. Use the double-arrows on the left to expand or contract the Group by

control.

151

To filter active alerts:

1. Click the filter icon on the column by which you want to filter alerts.2. Enter your filter term. The filter appears above the grid.3. Click the X next to the filter term to remove the filter.

To hide acknowledged alerts:

1. Click More on the right of the grid.2. Select Hide Acknowledged Alerts.

Testing Alerts

You do not have to actually experience a device failure to confirm that youralerts are working. The trigger condition is automatically evaluated and triggerand reset actions can be tested individually.

Testing Trigger Conditions

Alert conditions are automatically evaluated on the Summary tab. Scroll to thebottom of the page and view the information box above the Submit button.

Testing Trigger or Reset Actions within the Alert

When you simulate actions, the action will be performed once regardless ofwhether the trigger condition is true. If the action sends a message to arecipient, you should reduce the recipient list to yourself and a small number ofteam members until you are confident the alert is ready to be enabled in yourproduction environment.Note: The Send Email/Page action does not have to fire. You can view whatthe message will look like when the trigger or reset action fires without sendinga message.

1. Open an alert you want to test.2. Click Trigger Actions or Reset Actions.3. Click Simulate next to the alert action you want to test.4. Select an object to resolve any variables you have used in your alert

action.

152

Testing Alerts


5. Click Execute. To test email actions without sending an email, clickSimulate.

Testing Actions in the Action Manager

You can also test actions in the Action Manager. This is part of the AlertManager.Note: The Send Email/Page action does not have to fire. You can view whatthe message will look like when the trigger or reset action fires without sendinga message.

1. Select the action you want to test.2. Click Test.3. Select an object to resolve any variables you have used in your alert

action.4. Click Execute. To test email actions without sending an email, click

Simulate.

After the alert test completes, you can view the results of your alert actions.

l To view the results of your email alert action, open EvaluationAlertLogin your Orion folder, typically <Volume:>\ProgramFiles\SolarWinds\Orion.

l To view results of your Syslog message action, click Start > AllPrograms > SolarWinds Orion > Syslog and SNMP Traps > SyslogViewer.

l To view the results of your Syslog message action, click Start > AllPrograms > SolarWinds Orion > Syslog and SNMP Traps > TrapViewer.

Managing Alerts

You can add, edit, enable, disable, import, export, and delete alerts from theAlert Manager.

Adding and Editing Alerts

Use the Add New Alert or the Duplicate & Edit buttons to create new alerts.Select an alert and use the Edit Alert button to edit it.

153

Use the following topics to learn more about creating and editing alerts.

l Creating New Alertsl Commonly Created Alerts

Enabling and Disabling Alerts

Use the On/Off toggle or select an alert and click Enable/Disable to enable ordisable alerts.Alerts must be enabled to be evaluated. For example, if an alert is scheduledto run for a short period of time each year, it must be enabled so the scheduleruns. A disabled alert will not be evaluated, even if it is scheduled to run.

Exporting or Importing Alerts

You can use the Export/Import button to export or import alert definition files.Alerts are exported to XML and can only be imported from XML.Important: Confidential information, such as SMTP server credentials, may beincluded with the exported XML file. Please check the exported file for suchinformation or delete the information from the alert before you export it.

SolarWinds customers share their customized alerts in theSolarWinds thwack community. Visit thwack.solarwinds.com,download and import alerts by your peers. For example, to import analert that notifies you if Cisco ASA fails over, see the followingarticle: https://thwack.solarwinds.com/docs/DOC-170819.

Deleting Alerts

Use the Delete button to remove an alert.

Building Complex Conditions

Complex conditions are generally enabled by users who are comfortable withbuilding normal trigger conditions or who have trialed alerts using the normaltrigger conditions and require more control over the trigger conditions to betterrefine the environmental conditions that trigger an alert.Important: Do not use complex conditions until you have tested the triggerconditions individually. Creating an alert with complex conditions withouttesting it may prevent you from receiving important alerts.

154

Enabling and Disabling Alerts


https://thwack.solarwinds.com/docs/DOC-170819


To enable complex conditions:

1. Navigate to the Trigger Condition page.2. Expand Advanced options.3. Select Enable complex conditions.

You can use complex conditions to do the following:

l Wait for multiple objects to meet the trigger condition before alertingl Evaluate multiple condition blocksl Evaluate multiple object types

Waiting for Multiple Objects to Meet the Trigger Condition

Once you have enabled complex conditions, you can choose to trigger alertsonly when multiple objects meet the trigger condition.After you have enabled complex conditions, the following option is available inyour trigger condition:

This setting then combines all alerts that would be sent for each object into asingle alert.Important: Do not use this setting until you are confident that the triggercondition is correct. This setting can prevent important alerts from triggering.To trigger an alert only when multiple objects meet the trigger condition:

1. Enable complex conditions.2. In the trigger condition, select Alert can be triggered if.3. Enter how many objects must meet the trigger condition before sending

an alert.

Evaluating Multiple Condition Blocks

155

You can use complex conditions to evaluate multiple condition blocks, orsections, independently. For example, you may want to create an alert whenan application is down and when your fail-over server is active for more thanan hour.How Condition Blocks Are Evaluated

Condition blocks are evaluated in the order they are created. Take thefollowing example:(Condition A) & (Condition B) & (Condition C)

The primary condition block (Condition A), is evaluated first. If the condition ismet, the first secondary condition is evaluated (Condition B). If that condition ismet, the next condition block is evaluated in the same manner until there areno more condition blocks.All condition blocks must be met to trigger the alert.Condition blocks are evaluated using variations of AND, so the triggercondition in each section must be met.A condition block can be evaluated at a different time than other conditionblocks. In the example where you want to be alerted if the backup system isactive for more than an hour, you can choose to wait an hour after the primarycondition block, where the application going down is the trigger condition,before evaluating whether the backup system is still active.To choose to wait before evaluating a secondary condition block:

1. Enable complex conditions.2. Click Add Section.3. Select And then after from the drop-down menu between the two

condition sections.

4. Choose how long to wait before evaluating the next section.5. Create the next condition block.

Evaluating Multiple Object Types

156

How Condition Blocks Are Evaluated


To evaluate multiple object types, you should use complex conditions.Complex conditions can be used to alert on different object types within thesame alert. For example, you can create an alert to notify you when IIS is downand the free space on the volume is less than 30 GB.To choose different object types:

1. Enable complex conditions.2. Click Add Section.3. Choose a different value in I want to alert on.

Available Alert Actions

Orion platform products provide a variety of actions to signal an alert conditionon your network. For information on configuring each action, refer to thefollowing list.The following actions are available:

l Changing Custom Propertyl Dialing Paging or SMS Servicel Emailing a Web Pagel Executing an External Programl Executing a Visual Basic Scriptl Logging an Alert to a Filel Logging an Alert to the NPM Event Logl Managing the resource allocation of a virtual machinel Deleting a snapshot of a virtual machinel Moving a virtual machine to a different hostl Moving a virtual machine to a different storagel Pausing a virtual machinel Powering off a virtual machinel Powering on a virtual machinel Restarting a virtual machinel Suspending a virtual machine

157

l Taking a snapshot of a virtual machinel Playing a Soundl Restarting IIS Site or Application Poolsl Sending a Windows Net Messagel Sending an SNMP Trapl Using Get or Post URL Functionsl Sending a Syslog Messagel Sending an Email/Pagel Setting Custom Statusl Using Text to Speech Outputl Logging an Alert to the Windows Event Log

Changing Custom Property

Use the following procedure to modify a custom property through an alertaction.To configure a custom property action for an alert:

1. When editing or adding an alert, click Add Action.2. Select the Change Custom Property option, then click Configure

Action.3. Enter a name for the action in the Name of Action field.

158

Changing Custom Property


4. Under Custom Property Settings:

a. Select the Custom Property Name from the drop down list.b. Enter a Custom Property Value in the field provided.c. Optionally click Insert Variable to add variables using the following

procedure:

i. Select a Variable Category, and then select the variable toadd.

ii. To define a SQL variable, check Define SQL Variable.iii. Click [+] next to the name of a variable to add one or more

variables to the Custom SQL Variable window.iv. When done, click Insert Variable.

6. Expand Time of Day. Use this setting if you want to schedule thisaction. This schedule does not affect the overall alert schedule.

a. Select either Schedule is controlled on the alert level, noadditional schedule for this action needed or Use specialTime of Day schedule for this action. If you choose the latter,Click Add Schedule and then enter the time period over whichyou want to activate your alert action, and then select the days onwhich you want to activate your alert action.

7. Expand Execution Settings.

a. Check either Do not execute this action if the alert has beenacknowledged already (Recommended) or Repeat this actionevery X minutes until the alert is acknowledged. If you choosethe latter, specify the frequency to have this action repeated.

8. When done, click Add Action.

Dialing Paging or SMS Service

If NotePager Pro is installed, SolarWinds can be configured to communicatealerts using paging and SMS services. For more information about installationand configuration, see "SolarWinds Network Performance Monitor Integration"at www.notepage.net.

159

http://www.notepage.net/solar-winds/orion.htm

http://www.notepage.net/

Emailing a Web Page

The Edit E-mail Web Page Action window includes several sections forconfiguration. The following procedure configures an e-mail URL action for analert.To configure an email web page action for an alert:

1. When editing or adding an alert, click Add Action in an Action section ofthe Alert Wizard.

2. Select the Email a Web Page option, then click Configure Action.3. Enter a name for the action in the Name of Action field.4. Under Recipients:

a. Complete the To, CC, and BCC fields.b. You can optionally edit sender details by expanding [+] Sender

Details and editing the Name of Sender and the Reply Address.Note: You must provide at least one email address in the To field,and multiple addresses must be separated with commas. Somepager systems require a valid reply address to complete the page.

5. Expand Message.

a. Enter the Subject and Message of your alert trigger email/page. Note:Messaging is disabled if both the Subject and Messagefields are empty.

b. Optionally click Insert Variable to add variables using the followingprocedure:




c. For the Optional Web Server Authentication section, select Usercurrently logged in, Another user, or No user defined.

160

Emailing a Web Page


6. Expand SMTP Server.

a. Enter the Name of the SMTP Server.b. Enter the Hostname or IP Address of your SMTP Server and the

designated SMTP Port Number.Note: The SMTP server hostname or IP address field is required.You cannot send an email/page alert without identifying the SMTPserver.

c. To use SSL/TLS encryption for your alert email, check Use SSL.d. If your SMTP server requires authentication, check This SMTP

Server requires Authentication.e. Choose a Secondary SMTP Server from the list, if desired.

7. Expand Time of Day. Use this setting if you want to schedule this action.This schedule does not affect the overall alert schedule.

a. Select either Schedule is controlled on the alert level, noadditional schedule for this action needed or Use special Timeof Day schedule for this action. If you choose the latter, ClickAdd Schedule and then enter the time period over which you wantto activate your alert action, and then select the days on which youwant to activate your alert action.




Executing an External Program

There are several circumstances where you may want to execute a programwhen a specific network event occurs. Use the Edit Execute Program Actionwindow to specify the executable that should be started when the specifiedalert is triggered or reset, as shown in the following procedure.

161

External programs selected for this action must be executable using a batchfile called from the command line. Programs executed this way run in thebackground. However, you can set the MadCap Software Alerting EngineService to Interact with Desktop. SolarWinds recommends that scripts andbatch files be placed on the root of c:\ to simplify the path for the batch file.To configure an alert to execute an external program:


2. Select the Execute an External Program option, then click ConfigureAction.

3. Enter a name for the action in the Name of Action field.4. Under Execute an External Program settings:

a. Enter the Network path to external program in the field provided.For example: Use c:\test.bat, where c:\ is the disk on yourmain Orion poller and test.bat is your external program to beexecuted.

b. Select either Define User or No User Defined forOptionalWindows Authentication

5. Expand Time of Day. Use this setting if you want to schedule thisaction. This schedule does not the overall alert schedule.





162

Executing an External Program


Executing a Visual Basic Script

In some situations, you may want to execute a Visual Basic (VB) script when anetwork event occurs. The Edit Execute VB Script Action window is used tospecify the name and complete path of the file that shall be executed when thespecified alert is triggered or reset.To configure alerts to execute a Visual Basic (VB) script:


2. Select the Execute an External VB Script option, then click ConfigureAction.

3. Enter a name for the action in the Name of Action field.4. Under Execute an External VB Script settings:

a. Select a VB Script Interpreter from the drop down list.b. Enter the Network path to the external VB Script in the field

provided.For example: Use c:\test.vbs, where c:\ is the disk on yourmain Orion poller and test.vbs is your external VB Script to beexecuted.

c. Select either Define User or No User Defined forOptionalWindows Authentication

5. Expand Time of Day. Use this setting if you want to schedule thisaction. This schedule does not affect the overall alert schedule.




163


Logging an Alert to a File

SolarWinds can be configured to log alerts to a designated file. The followingprocedure logs an alert to a designated file.To configure an alert log file action for an alert:


2. Select the Log the Alert to a File option, then click Configure Action.3. Enter a name for the action in the Name of Action field.4. Under Log to File Settings:

a. Enter the log filename in the Alert Log Filename field.b. Optionally click Insert Variable to add variables using the following

procedure:




c. Enter a maximum log file size in MB (0 = unlimited).d. Enter the Message of your alert trigger in the field provided. e. Optionally click Insert Variable to add variables using the following

procedure:




164

Logging an Alert to a File


5. Expand Time of Day. Use this setting if you want to schedule this action.This schedule does not the overall alert schedule.





Logging an Alert to the NPM Event Log

You can specify that an alert should be logged to the NetPerfMon (NPM) EventLog either on the SolarWinds Orion server or on a remote server. The followingprocedure logs an alert to the NPM Event Log on a designated server.To configure alert logging to the NetPerfMon Event Log:


2. Select the Log the Alert to the NetPerfMon Event Log option, thenclick Configure Action.

3. Enter a name for the action in the Name of Action field.

165

4. Under Log the Alert to the NetPerfMon Event Log settings:

a. Enter the Message of your alert trigger in the field provided. b. Optionally click Insert Variable to add variables using the following

procedure:


ii. To define a SQL variable, check Define SQL Variable.iii. Click [+] next to the name of the variable to add one or more







Managing the resource allocation of a virtual machine

This alert management action is available if the integration with VirtualizationManager is enabled.To configure an alert to change the allocated resources on a virtual machine,perform the following procedure:

1. When you are editing or adding an alert, click Add Action in an Actionsection of the Alert Wizard.

166

Managing the resource allocation of a virtual machine


2. SelectManage VM - Change CPU/Memory Resources, and then clickConfigure Action.

3. Enter a name for the action in the Name of Action field.4. Under Select Virtual Machine to Manage Resource Allocation, specify

the virtual machine on which you want to adjust the number of CPUs, thememory capacity, or both.

a. To change the resource allocation of the virtual machine thattriggered the alert, click Execute this action on the VM thattriggered this alert.Note: This option is only available if the alert is built to trigger forvirtual machines.

b. To change the resource allocation of a different virtual machine,click Select specific VM frommy environment, and then searchfor the virtual machine on which you want to execute the action.

5. To power off the virtual machine before changing the resource allocation,and then power it on again after the resource allocation has beenchanged, select the relevant option. If the option is not selected, theaction will be performed live on the virtual machine.

6. Under Specify New Resources, specify whether you want to add moreresources to the virtual machine, or replace the existing resources withnew resources, and then specify the parameters of the new resource orresources.

a. Select Number of processors, and then specify the number ofprocessors to allocate to the virtual machine.

b. SelectMemory, and then specify the memory capacity to allocateto the virtual machine.


a. Select either Schedule is controlled on the alert level, noadditional schedule for this action needed or Use special Timeof Day schedule for this action. If you choose the latter, click AddSchedule, enter the time period over which you want to activateyour alert action, and then select the days on which you want toactivate your alert action.

167


a. Select either Do not execute this action if the alert has beenacknowledged already (Recommended) or Repeat this actionevery X minutes until the alert is acknowledged. If you choosethe latter, specify the frequency to have this action repeated.


The alert action is now configured in a way that the specified CPU andmemory resources will be allocated to the virtual machine when the alert istriggered.

Deleting a snapshot of a virtual machine

This alert management action is only available if the integration withVirtualization Manager is enabled.To configure an alert to delete a snapshot of a virtual machine, perform thefollowing procedure:


2. SelectManage VM - Delete Snapshot, and then click ConfigureAction.

3. Enter a name for the action in the Name of Action field.4. Under Select Virtual Machine to Delete Snapshot, specify the virtual

machine from which you want to delete a snapshot.

a. To delete a snapshot of the virtual machine that triggered the alert,click Execute this action on the VM that triggered this alert.Note: This option is only available if the alert is built to trigger forvirtual machines.

b. To delete a snapshot of a different virtual machine, click Selectspecific VM frommy environment, and then search for the virtualmachine on which you want to execute the action.

168

Deleting a snapshot of a virtual machine







The alert action is now configured in a way that the snapshot of the specifiedvirtual machine will be deleted when the alert is triggered.

Moving a virtual machine to a different host

This alert management action is only available if the integration withVirtualization Manager is enabled.To configure an alert to move a virtual machine to a different host, perform thefollowing steps:


2. SelectManage VM - Move to a Different Host, and then clickConfigure Action.

3. Enter a name for the action in the Name of Action field.

169

4. Under Select Virtual Machine to Move to a Different Host, specify thevirtual machine that you want to move.

a. To move the virtual machine that triggered the alert, click Executethis action on the VM that triggered this alert.Note: This option is only available if the alert is built to trigger forvirtual machines.

l To apply the action only to virtual machines of a specificvendor, select the relevant option, and then specify whetheryou want to perform to action on Hyper-V or VMware virtualmachines.

b. To move a different virtual machine, click Select specific VM frommy environment, and then search for the virtual machine on whichyou want to execute the action.

5. To power off the virtual machine before moving it to a different host, andthen power it on again after the action has been completed, select therelevant option. If the option is not selected, the action will be performedlive on the virtual machine.

6. Under Select Target Host, search for the host where you want to movethe selected virtual machine.






170

Moving a virtual machine to a different host


The alert action is now configured in a way that the specified virtual machinewill be moved to a different host when the alert is triggered.

Moving a virtual machine to a different storage

This alert management action is only available if the integration withVirtualization Manager is enabled.To configure an alert to move virtual machine data to a different storage,perform the following steps:


2. SelectManage VM - Move to a Different Storage, and then clickConfigure Action.

3. Enter a name for the action in the Name of Action field.4. Under Select Virtual Machine to Move to a Different Storage, specify

the virtual machine that you want to move.

a. To move the virtual machine that triggered the alert, click Executethis action on the VM that triggered this alert.Note: This option is only available if the alert is built to trigger forvirtual machines.

l To apply the action only to virtual machines of a specificvendor, select the relevant option, and then specify whetheryou want to perform to action on Hyper-V or VMware virtualmachines.

b. To move a different virtual machine, click Select specific VM frommy environment, and then search for the virtual machine on whichyou want to execute the action.

5. To power off the virtual machine before moving it to a different storage,and then power it on again after the action has been completed, selectthe relevant option. If the option is not selected, the action will beperformed live on the virtual machine.

171

6. Under Select Target Datastore, search for the datastore where you wantto move the selected virtual machine.

a. In a VMware environment, select one of the available datastores.b. In a Hyper-V environment, select one of the available datastores,

and then click either Use the default location to move the virtualmachine to the default location of the datastore, or click Specifycustom path, and then enter a custom location.






The alert action is now configured in a way that the specified virtual machinewill be moved to a different datastore when the alert is triggered.

Pausing a virtual machine

This alert management action is only available if the integration withVirtualization Manager is enabled.This action can only be configured for Hyper-V virtual machines.To configure an alert to pause a virtual machine, perform the following steps:


2. SelectManage VM - Pause, and then click Configure Action.

172

Pausing a virtual machine


3. Enter a name for the action in the Name of Action field.4. Under Select Virtual Machine to Pause, specify the virtual machine that

you want to pause.

a. To pause the virtual machine that triggered the alert, click Executethis action on the VM that triggered this alert.Note: This option is only available if the alert is built to trigger forvirtual machines.

b. To pause a different virtual machine, click Select specific VM frommy environment, and then search for the virtual machine on whichyou want to execute the action.






The alert action is now configured in a way that the specified virtual machinewill be paused when the alert is triggered.

Powering off a virtual machine

This alert management action is only available if the integration withVirtualization Manager is enabled.To configure an alert to power off a virtual machine, perform the followingsteps:

173


2. SelectManage VM - Power Off, and then click Configure Action.3. Enter a name for the action in the Name of Action field.4. Under Select Virtual Machine to Power Off, specify the virtual machine

that you want to power off.

a. To power off the virtual machine that triggered the alert, clickExecute this action on the VM that triggered this alert.Note: This option is only available if the alert is built to trigger forvirtual machines.

b. To power off a different virtual machine, click Select specific VMfrommy environment, and then search for the virtual machine onwhich you want to execute the action.






The alert action is now configured in a way that the specified virtual machinewill be powered off when the alert is triggered.

Powering on a virtual machine

This alert management action is only available if the integration withVirtualization Manager is enabled.

174

Powering on a virtual machine


To configure an alert to power on a virtual machine, perform the followingsteps:


2. SelectManage VM - Power On, and then click Configure Action.3. Enter a name for the action in the Name of Action field.4. Under Select Virtual Machine to Power On, specify the virtual machine

that you want to power on.

a. To power on the virtual machine that triggered the alert, clickExecute this action on the VM that triggered this alert.Note: This option is only available if the alert is built to trigger forvirtual machines.

b. To power on a different virtual machine, click Select specific VMfrommy environment, and then search for the virtual machine onwhich you want to execute the action.






The alert action is now configured in a way that the specified virtual machinewill be powered on when the alert is triggered.

Restarting a virtual machine

175

This alert management action is only available if the integration withVirtualization Manager is enabled.To configure an alert to restart a virtual machine, perform the following steps:


2. SelectManage VM - Reboot, and then click Configure Action.3. Enter a name for the action in the Name of Action field.4. Under Select Virtual Machine to Reboot, specify the virtual machine

that you want to reboot.

a. To reboot the virtual machine that triggered the alert, click Executethis action on the VM that triggered this alert.Note: This option is only available if the alert is built to trigger forvirtual machines.

b. To reboot a different virtual machine, click Select specific VM frommy environment, and then search for the virtual machine on whichyou want to execute the action.






The alert action is now configured in a way that the specified virtual machinewill be restarted when the alert is triggered.

Suspending a virtual machine

176

Suspending a virtual machine


This alert management action is only available if the integration withVirtualization Manager is enabled.To configure an alert to suspend a virtual machine, perform the following steps:


2. SelectManage VM - Suspend, and then click Configure Action.3. Enter a name for the action in the Name of Action field.4. Under Select Virtual Machine to Suspend, specify the virtual machine

that you want to suspend.

a. To suspend the virtual machine that triggered the alert, clickExecute this action on the VM that triggered this alert.Note: This option is only available if the alert is built to trigger forvirtual machines.

b. To suspend a different virtual machine, click Select specific VMfrommy environment, and then search for the virtual machine onwhich you want to execute the action.






The alert action is now configured in a way that the specified virtual machinewill be suspended when the alert is triggered.

Taking a snapshot of a virtual machine

177

This alert management action is only available if the integration withVirtualization Manager is enabled.To configure an alert to take a snapshot of a virtual machine, perform thefollowing steps:


2. SelectManage VM - Take Snapshot, and then click Configure Action.3. Enter a name for the action in the Name of Action field.4. Under Select Virtual Machine to Take Snapshot, specify the virtual

machine of which you want to take a snapshot.

a. To take a snapshot of the virtual machine that triggered the alert,click Execute this action on the VM that triggered this alert.Note: This option is only available if the alert is built to trigger forvirtual machines.

b. To take a snapshot a different virtual machine, click Select specificVM frommy environment, and then search for the virtual machineon which you want to execute the action.






The alert action is now configured in a way that a snapshot will be taken of thespecified virtual machine when the alert is triggered.

178

Taking a snapshot of a virtual machine


Playing a Sound

SolarWinds can be configured to play a sound upon alert trigger or reset. Thisalert action is frequently used in NOC environments. The SolarWinds DesktopNotification client must be installed on each computer that you want to play asound. The following procedure configures a sound to play for an alert.To configure a play sound action for an alert:


2. Select the Play a Sound option, and then click Configure Action.3. Enter a name for the action in the Name of Action field.4. Under Play a sound settings:

a. If not installed, click Download our desktop notification client todownload and install the notification client.

i. From the notification client, select an alert sound.

b. Optionally click Insert Variable to insert variables into the messagebody:






179




Restarting IIS Site or Application Pools

The following steps configure an alert to Restart an IIS Site/Application Poolon the trigger or reset action.To configure SolarWinds to Restart an IIS Site/Application Pool uponalert:


2. Select the Restart IIS Site/Application Pool option, then clickConfigure Action.

3. Enter a name for the action in the Name of Action field.4. Expand Restart IIS Site/Application PoolSettings.

a. Select the IIS Action to Perform from the drop down list.b. Specify the Site/Application Pool to Use, either Taken from alert

trigger or Use a different IIS Server.Note: If selecting Use a different IIS Server, enter the IIS Serverand the Site/Application Pool from the drop down lists.

5. Expand Time of Day.


180

Restarting IIS Site or Application Pools





Sending a Windows Net Message

Alerts can be configured to display a pop-up Windows Net Message either ona specific computer or on all computers in a selected domain or workgroup.The following steps configure Windows Net messaging for triggered or resetalerts.Note: The only operating systems supporting Windows Net Messaging onwhich SolarWinds supports SolarWinds installations are Windows Server2003 and Windows XP. SolarWinds only supports evaluation installations ofSolarWinds on Windows XP.To send a Windows Net message upon alert:


2. Select the Send Net Message option, then click Configure Action.3. Enter a name for the action in the Name of Action field.4. Under Send a Net Message settings:

a. Optionally check Send to all Computers in the Domain orWorkgroup.

b. Enter Computer Name or IP address in the field provided.Note: You can enter multiple computers or IP addresses byseparating them with commas.

c. Enter the Message of your alert trigger in the field provided.

181

d. Optionally click Insert Variable to add variables using the followingprocedure:









Sending an SNMP Trap

The following steps configure an alert to send an SNMP trap on the trigger orreset action.To send an SNMP trap:


2. Select the Send SNMP Trap option, then click Configure Action.3. Enter a name for the action in the Name of Action field.

182

Sending an SNMP Trap


4. Under Send SNMP Trap Message:

a. Enter SNMP Trap Destinations in the field provided.Note:Multiple IP Addresses should be separated by commas orsemicolons.

b. Select a Trap Template from the drop down lists.

5. Enter the Message of your alert trigger in the field provided.

a. Optionally click Insert Variable to add variables using the followingprocedure:


ii. To define a SQL variable, check Define SQL Variable.iii. Click [+] to add one or more variables to the Custom

SQL Variable window.iv. When done, click Insert Variable.

6. Expand SNMP Properties.

a. Enter a UDP Port number in the field provided.b. Select an SNMP Version from the drop down list.c. Enter the SNMP Community String in the field provided.





183


Using Get or Post URL Functions

SolarWinds can be configured to communicate alerts using HTTP GET orPOST functions. As an example, a URL may be used as an interface into atrouble ticket system, and, by correctly formatting the GET function, new troubletickets may be created automatically. The following procedure configuresSolarWinds to use GET or POST HTTP functions to communicate alertinformation.To configure SolarWinds to use GET or POST URL functions with alerts:


2. Select the Send a GET or POST Request to a Web Server option, thenclick Configure Action.

3. Enter a name for the action in the Name of Action field.4. Under HTTP request settings:

a. Enter a URL in the field provided.b. Select either Use HTTP GET or Use HTTP POST.






184

Using Get or Post URL Functions


Sending a Syslog Message

SolarWinds can log received alerts to the Syslog of a designated machine.The following procedure configures an alert to send a message to adesignated Syslog server.To configure an alert to send a Syslog message:


2. Select the Send a SysLog Message option, then click ConfigureAction.

3. Enter a name for the action in the Name of Action field.4. Under Send a SysLog message settings:

a. Enter the Hostname or IP Address of the Syslog Server in thefield provided.Note:Multiple Syslog servers should be separated by commas.

b. Select a Severity and a Facility from the drop down lists.

5. Enter the Message of your alert trigger in the field provided.

a. Optionally click Insert Variable to add variables using the followingprocedure:


ii. To define a SQL variable, check Define SQL Variable.iii. Click [+] to add one or more variables to the Custom

SQL Variable window.iv. When done, click Insert Variable.

185







The following procedure configures an email/page action for an alert.To configure an email/page action for an alert:


2. Select the Send an Email/Page option, then click Configure Action.3. Enter a name for the action in the Name of Action field.4. Under Recipients:

a. Complete the To, CC, and BCC fields.b. You can optionally edit sender details by expanding [+] Sender

Details and editing the Name of Sender and the Reply Address.Note: You must provide at least one email address in the To field,and multiple addresses must be separated with commas. Somepager systems require a valid reply address to complete the page.

186



5. Expand Message.

a. Select the format (Plain text or HTML) for your alert email.b. Enter the Subject and Message of your alert trigger email/page.

Note:Messaging is disabled if both the Subject and Messagefields are empty.

c. Optionally click Insert Variable to add variables using the followingprocedure:




6. Expand SMTP Server.

a. Enter the Name of the SMTP Server.b. Enter the Hostname or IP Address of your SMTP Server and the

designated SMTP Port Number.Note: The SMTP server hostname or IP address field is required.You cannot send an email/page alert without identifying the SMTPserver.

c. To use SSL/TLS encryption for your alert email, check Use SSL.d. If your SMTP server requires authentication, check This SMTP

Server requires Authentication.e. Choose a Secondary SMTP Server from the list, if desired.



187




Setting Custom Status

The following procedure configures a Set Custom Status action for an alert.The custom status does not affect the actual, polled values. For example, if thecustom status is set to UP, but the server is down or unresponsive, packet losscontinues to be 100%. Alerts based on the status do not trigger in this instance,but alerts based on a polled value, such as packet loss, do trigger.Important: When the status is set with an alert, the status does not update tothe actual, polled status. The status must be switched manually to a differentstatus or configured to use the polled status. Change the status to use thepolled status from the node details page or create a reset action to set thestatus to use the polled status.To configure a custom status action for an alert:


2. Select the Set Custom Status option, then click Configure Action.3. Enter a name for the action in the Name of Action field.4. Under Change Object Status Manually:

a. Select Change to a specific status if you are creating a triggeraction.

i. If you select, Change to a specific status, select the statusfrom the drop down list.

b. Select Use polled status if you are creating a reset action.

188

Setting Custom Status







Using Text to Speech Output

You may specify a phrase that will be spoken upon alert trigger and a separatephrase for the alert reset. SolarWinds uses Microsoft® Speech SynthesisEngine version 5.0. If you are under active SolarWinds maintenance, you mayalso install and use other text-to-speech engines by visiting the SolarWindswebsite. The following procedure configures text-to-speech output for an alerttrigger or reset.Note: Due to restrictions on Windows service applications, the Text to Speechaction is not available to SolarWinds installations on Windows 7 or WindowsServer 2008 and higher.To configure a text-to-speech output action for an advanced alert:


2. Select the Text to Speech Output option, then click Configure Action.3. Enter a name for the action in the Name of Action field.4. Under Text to Speech Output settings:

a. If not installed, click Download our desktop notification client todownload and install the notification client.

189

i. From the notification client, configure text to speech output.

b. Optionally click Insert Variable to insert variables into the Textfield:









Logging an Alert to the Windows Event Log

You may specify that an alert be logged to the Windows Event Log either onthe SolarWinds server or on a remote server. The following procedure logs analert to the Windows Event Log on a designated server.To configure alert logging to the Windows Event Log:


190

Logging an Alert to the Windows Event Log


2. Select theWindows Event Log option, then click Configure Action.3. Enter a name for the action in the Name of Action field.4. Under Event Log Settings:

a. Select either Use Event Log Message on Network PerformanceMonitor Server or Use Event Log Message on a Remote Server.Note: If the latter option is selected, enter the Remote ServerName or IP Address in the field provided.

b. Enter the Message of your alert trigger. c. Optionally click Insert Variable to add variables using the following

procedure:









191

Changes in the Alerting Engine

As of Orion platform version 2015.1, alerts are no longer created with thedesktop-based, Advanced Alerts Manager or Basic Alerts Manager. Alerts areinstead created and managed in the SolarWinds Orion Web Console.Alerts that you created in the desktop-based Alert Manager are migrated to theweb-based alerting engine when upgrading to Core version 2015.1. Somealerts may not be successfully migrated and include information about whythey were not migrated in the migration log. You can view the alert migrationlogs in the informational banners displayed after you update your installation.

Changed or removed functionality

The suppression section has not been carried over to web-based alerting. Useoptions, such as Condition must exist for more than, in the trigger conditionsto accomplish similar tasks.

Database changes

The following are a list of tables that have been changed that you may beusing in any custom SQL query:

l Engines has been renamed to AllEnginesl Nodes has been split into NodesCustomProperties, NodesData, andNodesStatistics

l History has been split into table-specific history tables, such as theAlertHistory table.

The new alerting engine also includes the following new alerting tables:

l AlertActivel AlertActiveObjectsl AlertConditionStatel AlertHistoryl AlertMigrationLogl AlertObjectsl AlertSchedules

192

Changes in the Alerting Engine


For a list of database changes from Orion platform version 2014.2 to version2015.1, including new tables, column changes, or data constraint or data typechanges, see the online Database Changes spreadsheet.

Macro or variable changes

Some alert variables are also not available. See the Defunct Alert Macros topicfor variables that cannot be used with the new alerting engine.

Alert Migration to the Web

The Advanced Alert Manager and the Basic Alert Manager are deprecated inSolarWinds Orion Core 2015.1 and later. A web-based alerting enginereplaces the previous alerting engine and includes new alerting variables. SeeGeneral Alert Variables for more information.To facilitate using the web-based alerting engine, part of the upgrade processmigrates alerts created with the desktop-based alerting engine to the web-based alerting engine. All alerts are migrated, including alerts that aredisabled.

Migration Issues

Some alerts may not be successfully migrated. The migration log records allalerts that are migrated and includes error messages for alerts that eithercannot be migrated or that are not migrated successfully.Common reasons that migration may not be successful include:

l Invalid alert variables or macros - See Defunct Alert Variables for a list ofvariables that are not supported.

l Invalid conditions - Some conditions are no longer supported.l Large alert scope - The number of objects that are relevant to an alertmay be too large to migrate.

Limitations to Migrated Alerts

Once an alert has been migrated, you can only view the alert definition throughthe web-based Alert Manager. You can no longer click on the alert in theviews.

193

Integrating Alerts with Other Products

Alerts may be shared with selected other SolarWinds products that are not partof the SolarWinds Orion Platform, such as AlertCentral and WebHelpDesk.To integrate alerts with other SolarWinds products:

1. On the Alert Summary page, expand Alert Integration.2. Check Integrate alert with other SolarWinds products and

subscribers (Recommended).3. Provide an appropriate Alert Subject. You can choose to use this name

as the subject field for the alert.4. Choose the alert Severity.

Note: This information may be used to determine how a shared alert ishandled by the product to which you are sharing the alert.

5. To include additional alert properties in the alert, click Insert Variableand choose which properties you want to include.

6. Click Submit.

VNQM ReportsSolarWinds provides Report Writer as a quick and easy way for you to extractdata from your database. Because VoIP and Network Quality Manager is anintegrated module of the Orion platform, information that you collect about yourIP SLA-capable network is easily presented in a variety of formats usingReport Writer.A number of predefined IP SLA-specific reports is available with yourinstallation of VoIP and Network Quality Manager. Report Writer also enablescustom IP SLA report creation, as necessary, using criteria and conditions youchoose. When you have finished editing your reports, you can view themthrough the VoIP and Network Quality Manager web interface and print themwith the click of a button.Note: VNQM 4.2.2 does not support managing reports directly within the OrionWeb Console.For more information about predefined IP SLA Reports, see Using PredefinedIP SLA Reports in the VoIP and Network Quality Manager Administrator Guide.

194

Integrating Alerts with Other Products


For more information about using Report Writer, see Creating and ModifyingReports in the SolarWinds Orion Core Administrator Guide.A report scheduling application is available to all customers with a currentmaintenance agreement. This tool schedules automatic email reports that canbe sent to individual users or groups of users. Log in to the customer portal ofwww.solarwinds.com and download the Report Scheduler from the AdditionalComponents for Orion area.Report Writer capabilities are further enhanced when they are used with theCustom Property Editor. Custom properties are available for report sorting andfiltering. For more information, see Creating Custom Properties for VoIP andNetwork Quality Manager in the VoIP and Network Quality ManagerAdministrator Guide.

Using Predefined VNQM ReportsThe following VNQM reports are provided with a VoIP and Network QualityManager installation.To access predefined reports:

1. Start the Orion Web Console in your SolarWinds Orion program folder.2. Go to the Home tab, and then select the Reports tab.3. Double-click the report you want to display.

To edit a report, open it in the Report Writer:

1. Start the Report Writer in your SolarWinds Orion program folder (forexample through Start > SolarWinds Orion > Alerting, Reporting, andMapping > Report Writer).For more information about customizing reports to suit your reportingneeds, see Creating and Modifying Reports in the SolarWinds OrionCore Administrator Guide.

Historical IP SLA Reports

VoIP and Network Quality Manager includes predefined reports for IP SLAoperations on your network.

195

http://www.solarwinds.com/documentation/helploader.aspx?topic=OrionCoreAGCreatingModifyingReports.htm


http://www.solarwinds.com/


DHCP – Last 7 DaysDisplays the average round trip time, maximum round trip time, and totalfailed requests over the last 7 days.

DHCP – Last MonthDisplays the average round trip time, maximum round trip time, and totalfailed requests that occurred last month.

DHCP – This MonthDisplays the average round trip time, maximum round trip time, and totalfailed requests that occurred this month.

DNS – Last 7 DaysDisplays the average round trip time and maximum round trip time forDNS requests over the last 7 days.

DNS – Last MonthDisplays the average round trip time and maximum round trip time forDNS requests that occurred last month.

DNS – This MonthDisplays the average round trip time and maximum round trip time forDNS requests that occurred this month.

FTP – Last 7 DaysDisplays the average round trip time and maximum round trip time forFTP requests over the last 7 days.

FTP – Last MonthDisplays the average round trip time and maximum round trip time forFTP requests that occurred last month.

FTP – This MonthDisplays the average round trip time and maximum round trip time forFTP requests that occurred this month.

HTTP – Last 7 DaysDisplays the minimum and average round trip time for HTTP, DNS, andTCP Connect requests as well as the total failed requests over the last 7days.

196



HTTP – Last MonthDisplays the minimum and average round trip time for HTTP, DNS, andTCP Connect requests as well as the total failed requests that occurredlast month.

HTTP – This MonthDisplays the minimum and average round trip time for HTTP, DNS, andTCP Connect requests as well as the total failed requests that occurredthis month.

ICMP Echo – Last 7 DaysDisplays the average round trip time and maximum round trip time forICMP Echo requests over the last 7 days.

ICMP Echo – Last MonthDisplays the average round trip time and maximum round trip time forICMP Echo requests that occurred last month.

ICMP Echo – This MonthDisplays the average round trip time and maximum round trip time forICMP Echo requests that occurred this month.

ICMP Path Echo – Last 7 DaysDisplays the average round trip time and maximum round trip time hop-by-hop over the last 7 days.

ICMP Path Echo – Last MonthDisplays the average round trip time and maximum round trip time hop-by-hop that occurred last month.

ICMP Path Echo – This MonthDisplays the average round trip time and maximum round trip time hop-by-hop that occurred this month.

ICMP Path Jitter – Last 7 DaysDisplays the average MOS for operations defined on your networkbetween listed source and destination sites hop-by-hop over the last 7days.

197

ICMP Path Jitter – Last MonthDisplays the average MOS for operations defined on your networkbetween listed source and destination sites hop-by-hop that occurred lastmonth.

ICMP Path Jitter – This MonthDisplays the average MOS for operations defined on your networkbetween listed source and destination sites hop-by-hop this month.

TCP Connect – Last 7 DaysDisplays the average round trip time and maximum round trip time forTCP Connect requests over the last 7 days.

TCP Connect – Last MonthDisplays the average round trip time and maximum round trip time forTCP Connect requests that occurred last month.

TCP Connect – This MonthDisplays the average round trip time and maximum round trip time forTCP Connect requests that occurred this month.

UDP Echo – Last 7 DaysDisplays the average round trip time and maximum round trip time forUDP Echo requests over the last 7 days.

UDP Echo – Last MonthDisplays the average round trip time and maximum round trip time forUDP Echo requests that occurred last month.

UDP Echo – This MonthDisplays the average round trip time and maximum round trip time forUDP Echo requests that occurred this month.

UDP Jitter – Last 7 DaysDisplays the average MOS for operations defined on your networkbetween listed source and destination sites over the last 7 days.

UDP Jitter – Last MonthDisplays the average MOS for operations defined on your networkbetween listed source and destination sites that occurred last month.

198



UDP Jitter – This MonthDisplays the average MOS for operations defined on your networkbetween listed source and destination sites that occurred this month.

VoIP UDP Jitter – Last 7 DaysDisplays minimum, maximum, and average VoIP metrics for thesimulated VoIP traffic between listed source and destination sites overthe last 7 days.

VoIP UDP Jitter – Last MonthDisplays minimum, maximum, and average VoIP metrics for thesimulated VoIP traffic between listed source and destination sites thatoccurred last month.

VoIP UDP Jitter – This MonthDisplays minimum, maximum, and average VoIP metrics for thesimulated VoIP traffic between listed source and destination sites thatoccurred this month.

Historical VoIP Reports

VoIP and Network Quality Manager includes predefined reports forVoIP-enabled devices on your network.Calls in Last 24 Hours

Displays the call details of all calls on your network between listedsource and destination sites over the last 24 hours.

Jitter – Last 30 DaysDisplays the average jitter for call paths defined on your networkbetween listed source and destination sites over the last 30 days.

Latency – Last 30 DaysDisplays the average latency for call paths defined on your networkbetween listed source and destination sites over the last 30 days.

MOS Score – Last 30 DaysDisplays the average MOS for call paths defined on your networkbetween listed source and destination sites over the last 30 days.

199

Packet Loss – Last 30 DaysDisplays the average packet loss for call paths between listed sourceand destination sites, as defined on your network, over the last 30 days.

VoIP Nodes Availability – Last 30 DaysDisplays the average availability for all VoIP-enabled nodes designatedon your network over the last 30 days.

VNQM MapsVoIP and Network Quality Manager allows you to display your IP SLAoperations on customizable maps produced within the Orion Web Console.You can create new maps or modify any existing map to include IP SLAoperations. The operation status is displayed on the map in the same fashionas nodes, interfaces, or volumes.For more information about using maps, see the SolarWinds Network AtlasAdministrator Guide.To add SolarWinds VoIP and Network Quality Manager operations to yourmap:

1. Start the Network Atlas in your SolarWinds program folder.2. Locate the source node in the left pane containing the IP SLA operations

you want to add.3. Click [+] next to the node name.4. Click [+] next to IP SLA Operations.5. Drag the operation you want to the drawing area.

VoIP and Network Quality Manager Map VariablesThe following list of variables can be used when creating labels for your mapobjects.

Variable Description

DateChangedUtc The last time the operation information wasupdated

200

VNQMMaps

http://www.solarwinds.com/documentation/orion/docs/OrionNetworkAtlasAdminGuide.pdf




Deleted Indicates if the operation has been deletedfrom VoIP and Network Quality Manager

Description A user defined explanation of the operation

DetailsUrl Link to the detail page

DisplaySource The source node

DisplayTarget The target node

Frequency How often the operation is performed

IpSlaOperationNumber The internal number of the operation

IsAutoConfigured This value is True if it was created by VoIPand Network Quality Manager, False if it wascreated by the user

LifetimeUtc The timeframe of when the operation isexecuted

NodeID The ID of the node

OperationInstanceID The internal ID of the operation

OperationName The name of the operation as it appears inthe database

OperationResultID The ID of the results of the operation

OperationResultRecordTime The timestamp of when the operation wasperformed

OperationStateID The ID of the operation state

OperationStatusID The ID of the operation status

OperationType The value of the operation type

201


OperationTypeID The ID of the operation type

SourceNodeID The node ID of the source node

StatusMessage A message that describes the status value

TargetNodeID The node ID the operation is targeting

For more information about creating maps, see the SolarWinds Network AtlasAdministrator Guide.

202

VoIP and Network Quality Manager Map Variables



Appendix A: ReferencesThis appendix provides troubleshooting information and reference material.Use the following to navigate directly to the information you want:

l Troubleshootingl Orion Variables and Examplesl Status Icons and Identifiersl 95th Percentile Calculationsl Regular Expression Pattern Matchingl Required SolarWinds Account Permissions

TroubleshootingIf you have problems with an Orion product, the causes are usually related toan incorrect configuration or corrupted files. The following suggestions canoften clear up these problems.

Back Up Your DataAs a first step in any troubleshooting procedure, you should back up your Oriondatabase.For more information about creating database backups, see the section,"Creating Orion Database Backup Files" in the SolarWinds NPM onlinedocumentation.

Verify Program OperationSolarWinds Orion runs many components at the same time to deliver a view ofyour network status.

203

http://www.solarwinds.com/documentation/helploader.aspx?topic=orionNPMmigration-createdbbackupdatabasemanager.htm

Appendix A: References

Confirm that the following components are running:

l Services:o Message Queuingo Net.Tcp Port Sharing Serviceo SolarWinds Alerting Engine serviceo SolarWinds Collector Data Processor, Management Agent, andPolling Controller services

o SolarWinds Information Serviceo SolarWinds Job Engine and Job Engine v2o SolarWinds Job Schedulero SolarWinds Orion Product serviceso SolarWinds Orion Information Serviceo SolarWinds Orion Module Engineo SolarWinds Syslog and Trap Services

l SQL Serverl Internet Information Service (IIS)l SolarWinds Web Console

Stop and RestartMany problems disappear when programs are restarted. Stopping andrestarting Internet Information Service (IIS) may eliminate web page problems.Problems with polling or data gathering may be eliminated by stopping andrestarting Job Engine or Collector services using the available shutdown toolthat you can locate as follows:Click Start > All Programs > SolarWinds Orion > Advanced Features >Orion Service Manager.For a complete refresh of the system, reboot the computer.

Run the Configuration WizardRunning the Configuration Wizard, which refreshes files on the web server andperforms checks on the structure of your database, may solve many problems.

204

Note: Before you run the Configuration Wizard, you should close all openapplications.

Working with Temporary DirectoriesThe following sections provide procedures for moving Windows and SQLServer temporary directories to optimize Orion server performance andresources.

l Moving the SQL Server Temporary Directoryl Redefining Windows System Temporary Directories

Moving the SQL Server Temporary Directory

The SQL Server temporary directory, tempdb, where temporary databaseobjects generated during table creation and sorting are stored, is typicallycreated in the same location on your Orion database server as themaster,model, andmsdb databases. Moving the tempdb database to a physicaldrive separate from your Orion database can significantly improve overallsystem performance.For more information about moving the SQL Server 2008 temporary directory,tempdb, see "Moving System Databases – Example A: Moving the tempdbDatabase".

Redefining Windows System Temporary Directories

Following established Windows standards, the SolarWinds Orion installer mayuse Windows User and System TEMP and TMP variable directories astemporary scratch spaces for file expansion and execution. If you do not havethe required scratch space available in the default User or System TEMP andTMP directories, use the following procedure to redefine your default locations.Note: Regardless of where you actually install SolarWinds Orion, somecommon files may be installed where the operating system of your Orion serverare located.To redefine default system temporary directories:

1. Log on to your Orion server as a user with administrative rights.2. Right-click My Computer, and then click Properties.3. Click Advanced, and then click Environment Variables.

205

Working with Temporary Directories

http://msdn.microsoft.com/en-us/library/ms345408.aspx

http://msdn.microsoft.com/en-us/library/ms345408.aspx


4. Select the variable name representing the directory you want to redefine,click Edit, and then provide a new path as the Variable value for theselected temporary directory variable.

Slow Performance on Windows Server 2008If Orion is installed on Windows Server 2008 and there are any devices onyour network, between your Orion server and your database server, that do notsupport RFC 1323, the TCP window size auto-tuning feature of WindowsServer 2008 may prevent your Orion server from successfully connecting withyour Orion database.This TCP auto-tuning feature is intended as a network-sensitive restriction,applied by the receiver—your SolarWinds Orion server—on the amount of datait is allowed or able to receive. If any devices along the network path betweenyour Orion server and your Orion database do not support the TCP windowscaling detailed in RFC 1323, the allowed size of the TCP window in packetssent to your Orion server may not match the TCP window size reported bypackets sent from your Orion server. This mismatch may lead to failedconnections between your Orion server and your Orion database. Thefollowing procedure disables this TCP auto-tuning feature, resetting the TCPreceive window to 64kB.To disable tcp auto-tuning:

1. Click Start > All Programs > Accessories.2. Right-click Command Prompt, and then click Run as administrator.3. If you are prompted by User Account Control, click Continue to open

the elevated command prompt.

Note: In some cases, having User Account Control (UAC) enabled onWindows Server 2008 can lead to installation errors. For moreinformation about disabling UAC, see the article "Disabling User AccountControl (UAC)" in the SolarWinds Knowledge Base.

4. At the prompt, enter the following:netsh interface tcp set global autotuninglevel=disabled

5. Close the command prompt window, and then restart your Orion server.

206

http://www.ietf.org/rfc/rfc1323.txt



Adjusting Interface Transfer RatesSolarWinds NPMmonitors the actual transfer rates on the interfaces andcalculates the percent utilization in real time, as it is requested in reports orwithin the user interface. Usually when you see interface utilization over 100%it is because the Transmit and Receive bandwidth values for this interface inSolarWinds NPM are incorrect.To update interface transfer rates:

1. Click Start > All Programs > SolarWinds Orion > Orion Web Console.2. In the web console, click the node that contains the interface you want to

update. This opens the Node Details view for the parent node of theinterface you want to edit.

3. In the Current Percent Utilization of Each Interface, or any other interface-related resource on the Node Details view, click the interface you want toedit. This opens the Interface Details view for the interface you want toedit.

4. In the Interface Details resource, click Edit Interface.5. Check Custom Bandwidth.6. Enter desired values in the Transmit Bandwidth and Receive

Bandwidth fields, and then click Submit.

Error When Creating New GroupIf you try to create a new group and you receive an error message aboutMSDTC, you should enable the MSDTC service on your SolarWinds Orionserver and your SQL server.This is an intermittent issue that is resolved by enabling MSDTC.For information, see this Microsoftarticle: https://code.msdn.microsoft.com/MSDTC-Service-enable-3e159891.

Orion Variables and ExamplesOrion platform products, including the Alert Manager, the Traps Viewer, theSyslog Viewer, and Network Atlas can employ Orion variables. Thesevariables are dynamic and, in the case of alerts, parse when the alert istriggered or reset.

207

Adjusting Interface Transfer Rates

https://code.msdn.microsoft.com/MSDTC-Service-enable-3e159891


As of Orion Platform version 2015.1, variables have changed to a more flexibleformat. The previous implementation was SQL based, and the new version isbased on SolarWinds Information Service (SWIS). For example, the variable${ResponseTime} is now ${N=SwisEntity;M=ResponseTime}.Tip: Check your version number by scrolling to the bottom of the page in theOrion Web Console.

Variable ConstructionVariables are designated by a $ and enclosed in {brackets}. There are threeattributes per variable, but only two are necessary.Note: All variables are available in the variable picker in the Orion WebConsole. You do not need to create or enter variables manually.${N=context;M=macroName;F=format}N

This is the context of the variable and required. You can use thefollowing contexts:

l Alerting - uses variables specific to alertingl OrionGroup - uses variables specific to groupsl SwisEntity - uses variables specific to the objects you monitor in thecontext of the alert

l Generic - uses variables specific to general environmental propertiesM

This is the variable or macro name and required. You can use entitynames from the SWIS.

FThis converts the data to a user-friendly format. Use formats that correlateto the data. For example, use DateTime with AcknowledgedTime, notwith ObjectType. You can convert data to specific formats using thevariable picker.

Variable ModifiersVariables can be modified by using any of the variable modifiers in thefollowing table.

208

VariableModifier Description

-Raw Displays the raw value for the statistic. For example, ifTransmit Bandwidth is set to 10 Mbps, then the raw valuewould be“10000000”. The cooked value would be “10Mbps”.

-Previous Displays the previous value for the statistic before theAlert was triggered

-Cooked Displays the cooked value for the statistic. For example,if Transmit Bandwidth is set to 10 Mbps, then the rawvalue would be “10000000” and cooked value would be“10 Mbps”.

-PreviousCooked

Displays the previous cooked value for the statisticbefore the Alert was triggered

Add modifiers to variables by the following examples below:${N=context;M=Modifier(macroName)}${N=Alerting;M=Previous(AcknowledgedBy)}

General Alert Variables

The following are valid, general alert variables.

General Variable Description

${N=Alerting; M=AlertID} The ID of the alert

${N=Alerting;M=AlertName}

The name of the alert from the alert fieldName of alert definition in Alert Properties

${N=Alerting;M=AlertDescription}

The description of the alert from the alert fieldDescription of alert definition in AlertProperties

${N=Alerting;M=AlertDetailsURL}

The URL used to get more information aboutthe triggered alert

209

General Alert Variables



${N=Alerting;M=AlertMessage}

The alert message from the alert fieldMessage displayed when this alert istriggered in Trigger Actions

${N=Alerting;M=DownTime} The amount of time the alert has been active

${N=Alerting;M=ObjectType}

The object type that the alert is monitoring

${N=Alerting; M=Severity} The severity of the alert from the alert fieldSeverity of Alert in Alert Properties

${N=Alerting; M=LastEdit} The last time the alert definition has beenedited

${N=Alerting;M=Acknowledged}

Acknowledged status

${N=Alerting;M=AcknowledgedBy}

Who the alert was acknowledged by

${N=Alerting;M=AcknowledgedTime}

Time the alert was acknowledged

${N=Alerting; M=Notes} Information from the Notes field when youacknowledge alerts through the Web Console

${N=Alerting;M=AlertTriggerCount}

Count of triggers

${N=Alerting;M=AlertTriggerTime}

Date and time of the last event for this alert.(Windows control panel defined “Short Date”and “Short Time”)

${N=Generic;M=Application}

SolarWinds application information

${N=Generic; M=Copyright} Copyright information

210


${N=Generic; M=Release} Release information

${N=Generic; M=Version} Version of the SolarWinds software package

It is possible to use previous generation variables, for example ${NodeName}.However, when using the variable picker, the new format is displayed bydefault. Previous generation variables can only be entered manually.Note: Some variables are no longer valid. See Defunct Alert Variables.

Date Time

The following are valid date and time variables.

Date/Time Variable Description

${N=Generic;M=AMPM}

AM/PM indicator

${N=Generic;M=AbreviatedDOW}

Current day of the week. Three characterabbreviation.

${N=Generic; M=Day} Current day of the month

${N=Generic; M=Date;F=Date}

Current date. (Short Date format)

${N=Generic;M=DateTime;F=DateTime}

Current date and time. (Windows control paneldefined “Long Date” and “Long Time” format)

${N=Generic;M=DayOfWeek}

Current day of the week.

${N=Generic;M=DayOfYear}

Numeric day of the year

${N=Generic;M=Hour}

Current hour

211

Date Time



${N=Generic; M=HH} Current hour. Two digit format, zero padded.

${N=Generic;M=Past2Hours}

Last two hours

${N=Generic;M=Past24Hours}

Last 24 hours

${N=Generic;M=Last7Days;F=Date}

Last seven days (Short Date format)

${N=Generic;M=PastHour}

Last hour

${N=Generic;M=LocalDOW}

Current day of the week. Localized languageformat.

${N=Generic;M=LocalMonthName}

Current month name in the local language.

${N=Generic;M=LongDate}

Current date. (Long Date format)

${N=Generic;M=Month}

Current numeric month

${N=Generic; M=MM} Current month. Two digit number, zero padded.

${N=Generic;M=AbbreviatedMonth}

Current month. Three character abbreviation.

${N=Generic;M=MonthName}

Full name of the current month

${N=Generic;M=MediumDate}

Current date. (Medium Date format)

${N=Generic;M=Minute}

Current minute. Two digit format, zero padded.

212


${N=Generic;M=Second}

Current second. Two digit format, zero padded.

${N=Generic;M=Time}

Current Time. (Short Time format)

${N=Generic;M=Today; F=Date}

Today (Short Date format)

${N=Generic; M=Year} Four digit year

${N=Generic;M=Year2}

Two digit year

${N=Generic;M=Yesterday; F=Date}

Yesterday (Short Date format)

Group Variables

The following are valid group variables.

Group Variable Description

${N=OrionGroup;M=GroupDetailsURL}

URL of the Group Details view for aselected group

${N=OrionGroup;M=GroupFrequency}

Interval on which groupmembership is evaluated and groupsnapshots are taken.

${N=OrionGroup; M=GroupID} Designated identifier for a definedgroup

${N=OrionGroup;M=GroupMemberDisplayName}

Display name of group membertype: Node, Volume, Component,Application, etc.

213

Group Variables



${N=OrionGroup;M=GroupMemberDisplayNamePlural}

Display name of multiple groupmembers of a type: Nodes,Components, Applications, etc.

${N=OrionGroup;M=GroupMemberFullName}

Full name of a group member,including location

${N=OrionGroup;M=GroupMemberName}

Name of a group member

${N=OrionGroup;M=GroupMemberPercentAvailability}

Percent availability of a groupmember when group member statusis Up, Warning, or Critical and 0% ifstatus is anything else.

${N=OrionGroup;M=GroupMemberSnapshotID}

Unique identifier of group membersnapshot.

${N=OrionGroup;M=GroupMemberStatusID}

Identifier assigned to a groupmember indicating its status. Formore information see StatusValues.

${N=OrionGroup;M=GroupMemberStatusName}

Name of group member status. Formore information see StatusValues.

${N=OrionGroup;M=GroupMemberUri}

Uri used by SolarWinds InformationService (SWIS) to refer to theselected group member within theweb console.

${N=OrionGroup; M=GroupName} Name of the group.

${N=OrionGroup; M=GroupOwner} Orion product appropriate to thegroup type

214


${N=OrionGroup;M=GroupPercentAvailability}

100% when group status is Up,Warning, Critical and 0% if status isanything else.

${N=OrionGroup;M=GroupStatusCalculatorID}

Name of roll-up logic calculator thatevaluates status of group based onmember statuses. (0 = Mixed, 1 =Worst, 2 = Best)

${N=OrionGroup;M=GroupStatusCalculatorName}

Name of roll-up logic calculator thatevaluates status of group based onmember statuses. (Mixed,Worst,Best)

${N=OrionGroup; M=GroupStatusID} Identifier assigned to a groupindicating its status. For moreinformation see Status Values.

${N=OrionGroup; M=GroupStatus} Name of group status. For moreinformation see Status Values.

${N=OrionGroup;M=GroupStatusRootCause}

A list of all group members that arenot Up

SQL Query

Any value you can collect from the database can be generated, formatted, orcalculated using a SQL query as a variable. To use a SQL query as a variablein Orion platform products, use ${SQL:{query}} as shown in the followingexample that returns the results of the SQL query:Select Count(*) From Nodes:Note: SolarWinds does not support SQL queries directly. Visit our user forumson thwack for help from our community.

Status Values

When using the ${N=SwisEntity; M=Status} variable with a monitored object,status values are returned, as appropriate. The following table provides adescription for each status value.

215

SQL Query



Status Value Description

0 Unknown

1 Up

2 Down

3 Warning

4 Shutdown

5 Testing

6 Dormant

7 Not Present

8 Lower Layer Down

9 Unmanaged

10 Unplugged

11 External

12 Unreachable

14 Critical

15 Partly Available

16 Misconfigured

17 Could Not Poll

19 Unconfirmed

22 Active

24 Inactive

25 Expired

216

Status Value Description

26 Monitoring Disabled

27 Disabled

28 Not Licensed

29 Other

30 Not Running

Node Variables

The following are valid node variables.

Node Variable Description

${N=SwisEntity;M=AgentPort} Node SNMP portnumber

${N=SwisEntity;M=Node.Allow64BitCounters} Node allows 64-bit counters (1), ornot (0)

${N=SwisEntity;M=AvgResponseTime} Average noderesponse time, inmsec, to ICMPrequests

${N=SwisEntity;M=BlockUntil} Day, date, andtime until whichnode polling isblocked

${N=SwisEntity;M=BufferBgMissThisHour} Device-dependent count of bigbuffer misses onnode in currenthour, queried withMIB1.3.6.1.4.9.2.1.30

217

Node Variables



${N=SwisEntity;M=BufferBgMissToday} Device-dependent count of bigbuffer misses onnode in currentday, queried withMIB1.3.6.1.4.9.2.1.30

${N=SwisEntity;M=BufferHgMissThisHour} Device-dependent count of hugebuffer misses onnode in currenthour, queried withMIB1.3.6.1.4.9.2.1.62

${N=SwisEntity;M=BufferHgMissToday} Device-dependent count of hugebuffer misses onnode in currentday, queried withMIB1.3.6.1.4.9.2.1.62

${N=SwisEntity;M=BufferLgMissThisHour} Device-dependent count of largebuffer misses onnode in currenthour, queried withMIB1.3.6.1.4.9.2.1.38

218


${N=SwisEntity;M=BufferLgMissToday} Device-dependent count of largebuffer misses onnode in currentday, queried withMIB1.3.6.1.4.9.2.1.38

${N=SwisEntity;M=BufferMdMissThisHour} Device-dependent count of mediumbuffer misses onnode in currenthour, queried withMIB1.3.6.1.4.9.2.1.22

${N=SwisEntity;M=BufferMdMissToday} Device-dependent count of mediumbuffer misses onnode in currentday, queried withMIB1.3.6.1.4.9.2.1.22

${N=SwisEntity;M=BufferNoMemThisHour} Count of buffererrors due to lowmemory on nodein current hour

${N=SwisEntity;M=BufferNoMemToday} Count of buffererrors due to lowmemory on nodein current day

219

Node Variables



${N=SwisEntity;M=BufferSmMissThisHour} Device-dependent count of smallbuffer misses onnode in currenthour, queried withMIB1.3.6.1.4.9.2.1.14

${N=SwisEntity;M=BufferSmMissToday} Device-dependent count of smallbuffer misses onnode in currentday, queried withMIB1.3.6.1.4.9.2.1.14

${N=SwisEntity;M=Caption} User friendlynode name

${N=SwisEntity;M=Community} Node communitystring

${N=SwisEntity;M=Contact} Contactinformation forperson or groupresponsible fornode

${N=SwisEntity;M=CPULoad} Node CPUutilization rate atlast poll

${N=SwisEntity;M=CustomPollerLastStatisticsPoll} Day, date, andtime of last pollattempt on node

220


${N=SwisEntity;M=CustomPollerLastStatisticsPollSuccess}

Day, date, andtime that nodewas lastsuccessfullypolled

${N=SwisEntity;M=NodeDescription} Node hardwareand software

${N=SwisEntity;M=DNS} Fully qualifiednode name

${N=SwisEntity;M=DynamicIP} If node supportsdynamic IPaddressassignment viaBOOTP or DHCP(1); static IPaddress return (0)

${N=SwisEntity;M=EngineID} Internal uniqueidentifier of thepolling engine towhich node isassigned

${N=SwisEntity;M=GroupStatus} Filename ofstatus icon fornode and, inOrion NPM, itsinterfaces

${N=SwisEntity;M=IOSImage} Family name ofCisco IOS onnode

${N=SwisEntity;M=IOSVersion} Cisco IOS versionon node

${N=SwisEntity;M=IP_Address} Node IP address

221

Node Variables



${N=SwisEntity;M=IPAddressType} Node IP addressversion (IPv4 orIPv6)

${N=SwisEntity;M=LastBoot} Day, date andtime of last nodeboot

${N=SwisEntity;M=LastSync} Time and date oflast nodedatabase andmemorysynchronization

${N=SwisEntity;M=Location} Physical locationof node

${N=SwisEntity;M=MachineType} Nodemanufacturer ordistributor andfamily or versioninformation

${N=SwisEntity;M=MaxResponseTime} Maximum noderesponse time , inmsec, to ICMPrequests

${N=SwisEntity;M=MemoryUsed} Total nodememory usedover pollinginterval

${N=SwisEntity;M=Stats.MinResponseTime} Minimum noderesponse time , inmsec, to ICMPrequests

222


${N=SwisEntity;M=NextPoll} Day, date andtime of nextscheduled nodepolling

${N=SwisEntity;M=NextRediscovery} Time of next noderediscovery

${N=SwisEntity;M=NodeID} Internal uniqueidentifier of node

${N=SwisEntity;M=PercentLoss} ICMP packet losspercentage whennode last polled

${N=SwisEntity;M=PercentMemoryUsed} Percentage oftotal nodememory usedover pollinginterval

${N=SwisEntity;M=PollInterval} Node pollinginterval, inseconds

${N=SwisEntity;M=RediscoveryInterval} Node rediscoveryinterval, inminutes

${N=SwisEntity;M=ResponseTime} Node responsetime, inmilliseconds, tolast ICMP request

${N=SwisEntity;M=SNMPv3Credentials.RWAuthenticationKey}

SNMPv3read/writecredentialauthenticationkey

223

Node Variables



${N=SwisEntity;M=SNMPv3Credentials.RWAuthenticationKeyIsPassword}

States if theSNMPv3read/writecredentialauthenticationkey is thepassword

${N=SwisEntity;M=SNMPv3Credentials.RWAuthenticationMethod}

SNMPv3read/writecredentialauthenticationmethod

${N=SwisEntity;M=SNMPv3Credentials.RWContext}

SNMPv3read/writesecurity contextinformation

${N=SwisEntity;M=SNMPv3Credentials.RWPrivacyKey}

SNMPv3read/writecredential key

${N=SwisEntity;M=SNMPv3Credentials.RWPrivacyKeyIsPassword}

States if theSNMPv3read/writecredential privacykey is thepassword

${N=SwisEntity;M=SNMPv3Credentials.RWPrivacyMethod}

SNMPv3read/writecredential privacyencryptionmethod

224


${N=SwisEntity;M=SNMPv3Credentials.RWUsername}

User friendlyname forSNMPv3read/writecredential

${N=SwisEntity;M=Severity} A network healthscore determinedadditively byscoring the statusof monitoredobjects. In OrionNPM 1 point isprovided for aninterface in awarning state,1000 points for adown interface,and 1 millionpoints for a downnode. In SAM,100 points isprovided for anapplication in awarning state,200 points for anapplication incritical state, 500is status isunknown, and1000 for a downapplication.

${N=SwisEntity;M=SNMPv3Credentials.AuthenticationKey}

SNMPv3authenticationkey

225

Node Variables



${N=SwisEntity;M=SNMPv3Credentials.AuthenticationKeyIsPassword}

States if nodeSNMPv3authenticationkey is password

${N=SwisEntity;M=SNMPv3Credentials.AuthenticationMethod}

SNMPv3authenticationtype

${N=SwisEntity;M=SNMPv3Credentials.Context}

Group or domainof user withSNMPv3 accessto node

${N=SwisEntity;M=SNMPv3Credentials.PrivacyKey}

SNMPv3credential key

${N=SwisEntity;M=SNMPv3Credentials.PrivacyKeyIsPassword}

States if nodeSNMPv3credential key isthe password

${N=SwisEntity;M=SNMPv3Credentials.PrivacyMethod}

SNMPv3credential keytype

${N=SwisEntity;M=SNMPv3Credentials.Username}

User friendlyname forSNMPv3credential

${N=SwisEntity;M=SNMPVersion} States the versionof SNMP used bythe node

${N=SwisEntity;M=StatCollection} Statisticscollectionfrequency, inminutes

226


${N=SwisEntity;M=Status;F=Status} Numerical nodestatus. For moreinformation, seeStatus Values.

${N=SwisEntity;M=StatusDescription} User friendlynode status

${N=SwisEntity;M=StatusLED} Filename of nodestatus icon

${N=SwisEntity;M=SysName} String reply toSNMP SYS_NAME OIDrequest

${N=SwisEntity;M=SysObjectID} Vendor ID of thenetworkmanagementsubsystem in OIDform. Clearlydetermines thetype of node.

${N=SwisEntity;M=SystemUpTime} Time, inhundredths of asecond, eithersince networkmonitoring started(WMI) or since themonitored devicerebooted (SNMP).

${N=SwisEntity;M=TotalMemory} Total nodememory available

${N=SwisEntity;M=UnManaged} States if node iscurrentlyunmanaged

227

Node Variables



${N=SwisEntity;M=UnManageFrom} Day, date, andtime when nodeis set to“Unmanaged”

${N=SwisEntity;M=UnManageUntil} Day, date, andtime when nodeis scheduled tobe managed

${N=SwisEntity;M=Vendor} Nodemanufacturer ordistributor

${N=SwisEntity;M=VendorIcon} Filename of nodevendor logo

Defunct Alert Variables

The following variables are no longer valid:

l ${Property} - The property the alert is monitoring. You can select a newvariable with the specific property you want to view.

l ${TriggeredValue} - The value that triggered the alert. You can select anew variable with the specific property you want to view.

l ${AlertStartTime} - When the alert active. You can use the Time of Dayscheduler to control when the alert is active.

l ${AlertEndTime} - When the alert is no longer active. You can usethe Time of Day scheduler to control when the alert is not active.

l ${ObjectSubType} - Determines if the node supports SNMP or is ICMP-only. You can use Node.ObjectSubType as the macro name.

Example Messages Using VariablesThe following examples illustrate messages that you can create usingvariables. You can use variables in the message body or the subject. You canalso use variables in alert conditions.SolarWinds recommends using the variable picker by clicking Insert Variable.

228

Message with variablesMessage withresolved variables

Previous reboot was at${N=SwisEntity;M=Previous(LastBoot)}.

Previous reboot was at10/29/2014 12:02:00PM.

Alert: The SNMP Community string used to query${N=SwisEntity;M=Caption} has been changedfrom ${N=SwisEntity;M=Previous(Community)}to ${N=SwisEntity;M=Community}.

Alert: TheSNMP Communitystring used to queryHouston_backup hasbeen changed from1234 to 5678.

Alert: ${N=SwisEntity;M=Caption} hasexceptionally high response time. AverageResponse Time is${N=SwisEntity;M=AvgResponseTime} and isvarying from${N=SwisEntity;M=MinResponseTime} to${N=SwisEntity;M=MaxResponseTime}.

Alert: DevOP_VMs hasexceptionally highresponse time. AverageResponse Time is 1200ms and is varying from500 ms to 1700 ms.

Current packet loss for${N=SwisEntity;M=Caption} is${N=SwisEntity;M=PercentLoss}. AverageResponse time is${N=SwisEntity;M=AvgResponseTime} and isvarying from${N=SwisEntity;M=MinResponseTime} to${N=SwisEntity;M=MaxResponseTime}.

Current packet loss forMainWebServer is43%. AverageResponse time is 500ms and is varying from200 ms to 800 ms.

You can also manually add a repeater when you expect multiple objects to beincluded in an alert. For example, if you have an alert set up to notify you when5 nodes go down, you can use <<< >>> to repeat both text and variables. Seethe examples below.This message with no repeater displays every node that is down in a separatesentence: ${N=SwisEntity;M=Caption} is${N=SwisEntity;M=Status;F=Status}.

229

Example Messages Using Variables


This message displays only the text included in the repeater, in this case eachnode that is down: <<< ${N=SwisEntity;M=Caption}>>> is${N=SwisEntity;M=Status;F=Status}.This message displays each node that is down and the status of each node:<<< ${N=SwisEntity;M=Caption} is${N=SwisEntity;M=Status;F=Status}.>>>Note:When using a repeater, you cannot use the PREVIOUS variable.

Using Macro Formatters

Be aware that using macro formatters can significantly change the macroresult. For example:${N=Generic;M=Date;F=Date} - Tuesday, December 2, 2014${N=Generic;M=Date;F=OriginalValue} - 12/2/2014These formatters are available in the UI from the macro variable picker, and adifferent set of formatters is available depending on the variable value type.

Syslog Alert VariablesThe following variables can be used in Syslog alert messages. Each variablemust begin with a dollar sign and be enclosed in curly braces as, for example,${VariableName}. Syslog alerts also support the use of Node alert variables.For more information on the use of variables, see Orion Variables andExamples.

Syslog Date/Time Variables

Syslog Date/TimeVariable Description

${AbbreviatedDOW} Current day of the week. Three characterabbreviation.

${AMPM} AM or PM corresponding to current time (before orafter noon)

${D} Current day of the month

230


${DD} Current day of the month (two digit number, zeropadded)

${Date} Current date. (Short Date format)

${DateTime} Current date and time. (Windows control paneldefined "Short Date" and "Short Time" format)

${DayOfWeek} Current day of the week.

${DayOfYear} Numeric day of the year

${H} Current hour

${HH} Current hour. Two digit format, zero padded.

${Hour} Current hour. 24-hour format

${LocalDOW} Current day of the week. Localized language format.

${LongDate} Current date. (Long Date format)

${LocalMonthName} Current month name in the local language.

${LongTime} Current Time. (Long Time format)

${M} Current numeric month

${MM} Current month. Two digit number, zero padded.

${MMM} Current month. Three character abbreviation.

${MediumDate} Current date. (Medium Date format)

${Minute} Current minute. Two digit format, zero padded.

${Month} Full name of the current month

${N} Current month and day

231

Syslog Date/Time Variables



${S} Current second.

${Second} Current second. Two digit format, zero padded.

${Time} Current Time. (Short Time format)

${Year2} Two digit year

${Year} Four digit year

Other Syslog Variables

Syslog Variable Description

${Application} SolarWinds application information

${Copyright} Copyright information

${DNS} Fully qualified node name

${Hostname} Host name of the device triggering the alert

${IP_Address} IP address of device triggering alert

${Message} Status of device triggering alert

${MessageType} The name of the triggered alert

${Severity} A network health score indicating node states as follows:INTERFACE_UNKNOWN = 1INTERFACE_WARNING = 1INTERFACE_DOWN = 1000NODE_UNKNOWN = 1000000NODE_WARNING = 1000000NODE_DOWN = 100000000

The Up score for Nodes and Interfaces is zero.

232

Syslog Variable Description

${Version} Version of the SolarWinds software package

Trap Alert VariablesThe following variables can be used in trap alert messages with the Orion TrapServer. Each variable must begin with a dollar sign and be enclosed in curlybraces as, for example, ${VariableName}.Note: Trap alerts may also use any valid node variables. For more informationabout node alert variables, see Orion Variables and Examples.

Trap Date/Time Variables

Trap Date/TimeVariable Description

${AbbreviatedDOW} Current day of the week. Three characterabbreviation.

${AbbreviatedMonth} Current month of the year. Three characterabbreviation.

${AMPM} AM or PM corresponding to current time (before orafter noon)

${D} Current day of the month

${DD} Current day of the month (two digit number, zeropadded)

${Date} Current date. (MM/DD/YYYY format)

${DateTime} Current date and time. (MM/DD/YYYY HH:MMformat)

${Day} Current day of the month

${DayOfWeek} Current day of the week.

${DayOfYear} Numeric day of the year

233

Trap Alert Variables


Trap Date/TimeVariable Description

${H} Current hour

${HH} Current hour. Two digit format, zero padded.

${Hour} Current hour. 24-hour format

${LocalDOW} Current day of the week. Localized language format.

${LongDate} Current date. (DAY NAME, MONTH DAY, YEARformat)

${LongTime} Current Time. (HH:MM:SS AM/PM format)

${M} Current numeric month

${MM} Current month. Two digit number, zero padded.

${MMM} Current month. Three character abbreviation.

${MMMM} Full name of the current month

${MediumDate} Current date. (DD-MMM-YY format)

${MediumTime} Current time. (HH:MM AM/PM format)

${Minute} Current minute. Two digit format, zero padded.

${MonthName} Full name of the current month

${S} Current second.

${Second} Current second. Two digit format, zero padded.

${Time} Current Time. (HH:MM format)

${Year} Four digit year

${Year2} Two digit year

234

Other Trap Variables

Trap Variable Description

${Application} SolarWinds application information

${Community} Node community string

${Copyright} Copyright information

${DNS} Fully qualified node name

${Hostname} Host name of the device triggering the trap

${IP_Address} IP address of device triggering alert

${Message} Message sent with triggered trap and displayed in TrapDetails field of Trap Viewer

${MessageType} Name or type of trap triggered

${Raw} Raw numerical values for properties sent in thecorresponding incoming trap.

${RawValue} Raw numerical values for properties sent in thecorresponding incoming trap. The same as ${Raw}.

${vbData1} Trap variable binding value

${vbName1} Trap variable binding name

Status Icons and IdentifiersOrion platform products use icons as a visual language to describe the statusof items that your product tracks, such as nodes, interfaces, events, or alerts. Inthe case of alerts and events, further information is provided with the icon in theresource.Status icons are used with individual items and collections of items (such as acollection of nodes). You can also control how the status for collections aredisplayed.

235

Other Trap Variables


95th Percentile CalculationsCalculation of the 95th percentile, a well-known statistical standard used todiscard maximum spikes, is based on 5 minute data samples. The calculationgathers these values every 5 minutes for however long you select, throwsaway the top 5%, yielding the 95th percentile value at the beginning of the list.Consider the following example of how the 95th percentile is calculated for a10 hour work day from 8am to 6pm (600 minutes):

1. Over the 10 hours, the following 120 values were collected for inboundtraffic (Mb/s):

0.149 0.623 0.281 0.136 0.024 0.042 0.097 0.185 0.198 0.243 0.2740.390 0.971 0.633 0.238 0.142 0.119 0.176 0.131 0.127 0.169 0.2230.291 0.236 0.124 0.072 0.197 0.105 0.138 0.233 0.374 0.290 0.8710.433 0.248 0.242 0.169 0.116 0.121 0.427 0.249 0.223 0.231 0.3360.014 0.442 0.197 0.125 0.108 0.244 0.264 0.190 0.471 0.033 0.2280.942 0.219 0.076 0.331 0.227 0.849 0.323 0.221 0.196 0.223 0.6420.197 0.385 0.098 0.263 0.174 0.690 0.571 0.233 0.208 0.242 0.1390.186 0.331 0.124 0.249 0.643 0.481 0.936 0.124 0.742 0.497 0.0850.398 0.643 0.074 0.590 0.771 0.833 0.438 0.242 0.092 0.376 0.2310.627 0.249 0.663 0.181 0.636 0.224 0.342 0.697 0.285 0.108 0.2110.074 0.490 0.271 0.133 0.338 0.242 0.519 0.376 0.331 0.227

2. When reordered from high to low:

0.971 0.942 0.936 0.871 0.849 0.833 0.771 0.742 0.697 0.690 0.6630.643 0.643 0.642 0.636 0.633 0.627 0.623 0.590 0.571 0.519 0.4970.490 0.481 0.471 0.442 0.438 0.433 0.427 0.398 0.390 0.385 0.3760.376 0.374 0.342 0.338 0.336 0.331 0.331 0.331 0.323 0.291 0.2900.285 0.281 0.274 0.271 0.264 0.263 0.249 0.249 0.249 0.248 0.2440.243 0.242 0.242 0.242 0.242 0.238 0.236 0.233 0.233 0.231 0.2310.228 0.227 0.227 0.224 0.223 0.223 0.223 0.221 0.219 0.211 0.2080.198 0.197 0.197 0.197 0.196 0.190 0.186 0.185 0.181 0.176 0.1740.169 0.169 0.149 0.142 0.139 0.138 0.136 0.133 0.131 0.127 0.1250.124 0.124 0.124 0.121 0.119 0.116 0.108 0.108 0.105 0.098 0.0970.092 0.085 0.076 0.074 0.074 0.072 0.042 0.033 0.024 0.014

236

3. Drop the first 6, as these equal the top 5% of the values:

0.771 0.742 0.697 0.690 0.663 0.643 0.643 0.642 0.636 0.633 0.6270.623 0.590 0.571 0.519 0.497 0.490 0.481 0.471 0.442 0.438 0.4330.427 0.398 0.390 0.385 0.376 0.376 0.374 0.342 0.338 0.336 0.3310.331 0.331 0.323 0.291 0.290 0.285 0.281 0.274 0.271 0.264 0.2630.249 0.249 0.249 0.248 0.244 0.243 0.242 0.242 0.242 0.242 0.2380.236 0.233 0.233 0.231 0.231 0.228 0.227 0.227 0.224 0.223 0.2230.223 0.221 0.219 0.211 0.208 0.198 0.197 0.197 0.197 0.196 0.1900.186 0.185 0.181 0.176 0.174 0.169 0.169 0.149 0.142 0.139 0.1380.136 0.133 0.131 0.127 0.125 0.124 0.124 0.124 0.121 0.119 0.1160.108 0.108 0.105 0.098 0.097 0.092 0.085 0.076 0.074 0.074 0.0720.042 0.033 0.024 0.014

4. The 95th percentile is 0.771.

Regular Expression Pattern MatchingWhen editing comparison criteria, the following regular expressions can beused for pattern matching. Examples are provided at the end of this section.

Characters

Character Description Example

Any characterexcept[,\,^,$,.,|,?,*,+,(,),

All characters except the listed specialcharacters match a single instance ofthemselves.

a matches a

\ (backslash)followed byany of[,\,^,$,.,|,?,*,+,(,),

A backslash escapes special charactersto suppress their special meaning.

\+ matches +

\xFF whereFF are 2hexadecimaldigits

Matches the character with the specifiedASCII/ANSI value, which depends on thecode page used. Can be used incharacter classes.

\xA9 matches© when usingthe Latin-1code page.

237

Regular Expression Pattern Matching


Character Description Example

\n, \r and \t Match an LF character, CR character anda tab character respectively. Can be usedin character classes.

\r\n matches aDOS/WindowsCRLF linebreak.

Character Classes or Character Sets [abc]

CharacterClasses orSets Description Example

[ (openingsquarebracket)

Starts a character class. A character classmatches a single character out of all of thepossibilities offered by the character class.Inside a character class, different rules apply.The rules in this section are only valid insidecharacter classes. The rules outside thissection are not valid in character classes,except \n, \r, \t and \xFF

Anycharacterexcept ^,-,],\add thatcharacter tothe possiblematches forthe characterclass.

All characters except the listed specialcharacters.

[abc]matches a,b or c

\ (backslash)followed byany of ^,-,],\

A backslash escapes special characters tosuppress their special meaning.

[\^\]]matches ^or ]

238

CharacterClasses orSets Description Example

- (hyphen)exceptimmediatelyafter theopening [

Specifies a range of characters. (Specifies ahyphen if placed immediately after the opening[)

[a-zA-Z0-9]matchesany letteror digit

^ (caret)immediatelyafter theopening [

Negates the character class, causing it tomatch a single character not listed in thecharacter class. (Specifies a caret if placedanywhere except after the opening [)

[^a-d]matches x(anycharacterexcept a, b,c or d)

\d, \w and \s Shorthand character classes matching digits 0-9, word characters (letters and digits) andwhitespace respectively. Can be used insideand outside character classes

[\d\s]matches acharacterthat is adigit orwhitespace

Anchors

Anchors Description Example

^ (caret) Matches at the start of the string to which the regularexpression pattern is applied. Matches a positionrather than a character. Most regular expressionflavors have an option to make the caret match afterline breaks (i.e. at the start of a line in a file) as well.

^.matchesa inabc\ndef.Alsomatchesd in"multi-line"mode.

239

Anchors


Anchors Description Example

$ (dollar) Matches at the end of the string to which the regularexpression pattern is applied. Matches a positionrather than a character. Most regular expressionflavors have an option to make the dollar matchbefore line breaks (i.e. at the end of a line in a file) aswell. Also matches before the very last line break ifthe string ends with a line break.

.$ matchesf inabc\ndef.Alsomatchesc in"multi-line"mode.

\A Matches at the start of the string to which the regularexpression pattern is applied to. Matches a positionrather than a character. Never matches after linebreaks.

\A.matchesa in abc

\Z Matches at the end of the string to which the regularexpression pattern is applied. Matches a positionrather than a character. Never matches before linebreaks, except for the very last line break if the stringends with a line break.

.\Zmatchesf inabc\ndef

\z Matches at the end of the string to which the regularexpression pattern is applied. Matches a positionrather than a character. Never matches before linebreaks.

.\zmatchesf inabc\ndef

Quantifiers

Quantifiers Description Example

? (questionmark)

Makes the preceding item optional. The optionalitem is included in the match, if possible.

abc?matchesab or abc

240


?? Makes the preceding item optional. The optionalitem is excluded in the match, if possible. Thisconstruct is often excluded from documentationdue to its limited use.

abc??matchesab or abc

* (star) Repeats the previous item zero or more times. Asmany items as possible will be matched beforetrying permutations with fewer matches of thepreceding item, up to the point where thepreceding item is not matched at all.

.*matches"def""ghi" inabc "def""ghi" jkl

*? (lazystar)

Repeats the previous item zero or more times. Theengine first attempts to skip the previous itembefore trying permutations with ever increasingmatches of the preceding item.

.*?matches"def" inabc "def""ghi" jkl

+ (plus) Repeats the previous item once or more. As manyitems as possible will be matched before tryingpermutations with fewer matches of the precedingitem, up to the point where the preceding item ismatched only once.

.+matches"def""ghi" inabc "def""ghi" jkl

+? (lazyplus)

Repeats the previous item once or more. Theengine first matches the previous item only once,before trying permutations with ever increasingmatches of the preceding item.

.+?matches"def" inabc "def""ghi" jkl

{n} where nis aninteger >=1

Repeats the previous item exactly n times. a{3}matchesaaa

241

Quantifiers



{n,m}where n >=1 and m >=n

Repeats the previous item between n and m times.Will try to repeat m times before reducing therepetition to n times.

a{2,4}matchesaa, aaaor aaaa

{n,m}?where n >=1 and m >=n

Repeats the previous item between n and m times.Will try to repeat n times before increasing therepetition to m times.

a{2,4}?matchesaaaa,aaa oraa

{n,} wheren >= 1

Repeats the previous item at least n times. Will tryto match as many items as possible before tryingpermutations with fewer matches of the precedingitem, up to the point where the preceding item ismatched only m times.

a{2,}matchesaaaaa inaaaaa

{n,}? wheren >= 1

Repeats the previous item between n and m times.The engine first matches the previous item n timesbefore trying permutations with ever increasingmatches of the preceding item.

a{2,}?matchesaa inaaaaa

Dot

DotCharacter Description Example

. (dot) Matches any single character exceptline break characters \r and \n.

. matches x or mostany other character

242

Word Boundaries

WordBoundary Description Example

\b Matches at the position between a word character(anything matched by \w) and a non-word character(anything matched by [^\w] or \W) as well as at thestart and/or end of the string if the first and/or lastcharacters in the string are word characters.

.\bmatchesc in abc

\B Matches at the position between two wordcharacters (i.e., the position between \w\w) as wellas at the position between two non-word characters(i.e., \W\W).

\B.\Bmatchesb in abc

Alternation

AlternationCharacter Description Example

|(vertical baror “pipe”)

Causes the regular expression engine to matcheither the part on the left side or the part on theright side. Can be strung together into a series ofoptions.

abc|def|xyzmatchesabc, def orxyz

|(vertical baror “pipe”)

The vertical bar has the lowest precedence of alloperators. Use grouping to alternate only part ofthe regular expression.

abc(def|xyz)matchesabcdef orabcxyz

243

Word Boundaries


Required SolarWinds Account PermissionsThe following table lists account permissions SolarWinds requires to specificfolders on your server.

AccessLevel Account Folder the account needs to access

read NETWORKSERVICE

C:\Program Files (x86)\SolarWinds\Orion\

read IUSR C:\Program Files (x86)\SolarWinds\Orion\

readAdministrator

C:\Program Files (x86)\SolarWinds\Orion\

read NETWORKSERVICE C:\Windows\Microsoft.NET\Framework\v4.0.30319\T

emporary ASP.NET Files

read IUSRC:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files

write NETWORKSERVICE

C:\ProgramData\Application Data\SolarWinds


C:\InetPub\SolarWinds\web.config


C:\Windows\TEMP

read NETWORKSERVICE

C:\Windows\TEMP

write Authenticated Users

C:\ProgramData\Application Data\SolarWinds\Logs

read NETWORK C:\

244

AccessLevel Account Folder the account needs to access

SERVICE

The following table lists account permissions SolarWinds requires to specificcertificates on your server.

AccessLevel Account

Certificate the account needs toaccess

read NETWORKSERVICE

SolarWinds-Orion

read NETWORKSERVICE

SolarWinds-Orion

read Administrator SolarWinds-Orion

read SYSTEM SolarWinds-Orion

read NETWORKSERVICE

SolarWinds Job Scheduler

read NETWORKSERVICE

SolarWinds Job Scheduler

read Administrator SolarWinds Job Scheduler

read SYSTEM SolarWinds Job Scheduler

245

Required SolarWinds Account Permissions

Appendix B: Software License KeyAfter installing the application, the setup program displays the licensingwindow. Complete the following procedure to enable your software licensekey.To enable a software license key:

1. Click Enter Licensing Information.2. If the computer on which you installed VoIP and Network Quality

Manager is connected to the Internet, complete the following procedure.

a. Click I want to activate my license over the Internet.b. Browse to https://customerportal.solarwinds.com/.c. Log in to the customer portal using your CustomerID and password.d. Click License Management.e. Browse to SolarWinds VoIP and Network Quality Manager, and

then locate the unregistered licenses list.f. Copy your unregistered VoIP and Network Quality Manageractivation key to the clipboard, and then paste it into the ActivationKey field on the Activate Toolset window.

g. If you use a proxy server to access the Internet, select the ProxyServer option, and then type the proxy address and port number.

h. Click Next.

3. If the computer on which you are installing VoIP and Network QualityManager is not connected to the Internet, complete the followingprocedure.

a. Click I want to activate my license through the Customer Portal.b. Complete the procedure described on the Activate Toolset window

to complete the registration.

246

https://customerportal.solarwinds.com/

Appendix B: Software License Key

Maintaining Licenses with License ManagerSolarWinds License Manager is an easy-to-install, free utility with which youcan migrate VoIP and Network Quality Manager licenses from one computer toanother without contacting SolarWinds Customer Service. The followingsections provide procedures for installing and using License Manager:

l Installing License Managerl Using License Manager

Installing License ManagerInstall License Manager on the computer on which you want to activate,upgrade or synchronize your license or on which you want to deactivatecurrently licensed products.Warning: You must install License Manager on a computer with the correcttime. If the time on the computer is even slightly off, in either direction, fromGreenwich Mean Time (GMT), you cannot reset licenses without contactingSolarWinds Customer Service. Time zone settings neither affect nor cause thisissue.To install License Manager via SolarWinds UI:

1. Click Start > All Programs > SolarWinds > SolarWinds LicenseManager Setup.Note: If problems with License Manager occur, download and install thelatest version of License Manager.

2. Click Next to accept the SolarWinds EULA.3. If you are prompted to install the SolarWinds License Manager

application, click Install.

Downloading the License Manager from the Internet

1. Navigate tohttp://solarwinds.s3.amazonaws.com/solarwinds/Release/LicenseManager/LicenseManager.zip.

2. Unzip the downloaded file, and then run LicenseManager.exe.

247

http://solarwinds.s3.amazonaws.com/solarwinds/Release/LicenseManager/LicenseManager.zip

http://solarwinds.s3.amazonaws.com/solarwinds/Release/LicenseManager/LicenseManager.zip

Using License ManagerYou must run License Manager on the computer where the currently licensedSolarWinds product is installed before you can migrate licenses to a newinstallation. The following procedure deactivates currently installed licensesthat can then be transferred to a new installation.To deactivate currently installed licenses online:

1. Start the License Manager from the SolarWinds Program group.2. Select your product in License Manager, and then click Deactivate.

Notes:l You can deactivate more than one product at the same time. In thiscase, the deactivation file will contain information about eachproduct.

l In certain products, you can deactivate licenses by using theinternal licensing tool of the product.

3. Complete the deactivation wizard, and save the deactivation file.

To deactivate currently installed licenses offline:

1. Start the License Manager from the SolarWinds Program group.2. Select your product in License Manager, and then click Deactivate.

Notes:l You can deactivate more than one product at the same time. In thiscase, the deactivation file will contain information about eachproduct.

l In certain products, you can deactivate licenses by using theinternal licensing tool of the product.

3. Complete the deactivation wizard, and save the deactivation file.4. Log in to the SolarWinds Customer Portal, and then navigate to the

License Management page.5. Select your product instance, and then click Deactivate license manually.

248

Using License Manager

Appendix B: Software License Key

6. In the Manage License Deactivation page, browse for the deactivationfile you created in License Manager, and click Upload.Deactivated licenses are now available to activate on a new computer.If you have deactivated a license on an offline computer, or if you do nothave active maintenance, contact Customer Support [email protected] to be able to reuse the availablelicense.

Log on to the computer where you want to install your new implementation andinstall the product. When asked to specify your license, provide the appropriateinformation from the Customer Portal. The license you deactivated earlier isassigned to the new implementation.

249

mailto:[email protected]

Appendix C: MIBs Maintained byVoIP and Network Quality ManagerVoIP and Network Quality Manager continually updates CISCO-RTTMON-MIBin order to maintain IP SLA operations between devices. The following OIDnames are maintained by VoIP and Network Quality Manager, according to thesettings of your VoIP and Network Quality Manager implementation, as itconducts IP SLA operations:

Generall SysContactOIDl RttMonApplVersionl RttMonApplResponder (Read/Write)l RttMonCtrlAdminStatus (Read/Write)l RttMonCtrlAdminRttType (Read/Write)l RttMonCtrlAdminOwner (Read/Write)l RttMonCtrlAdminNvgen (Read/Write)l RttMonEchoAdminProtocol (Read/Write)l RttMonEchoAdminTOS

All Operationsl rttMonCtrlAdminRttTypel rttMonEchoAdminProtocoll rttMonLatestRttOperSensel rttMonLatestRttOperSensel rttMonLatestRttOperApplSpecificSense

250

Appendix C: MIBs Maintained by VoIP and Network Quality Manager

l rttMonLatestRttOperSenseDescriptionl rttMonLatestRttOperTime

DHCP Operationsl rttMonEchoAdminTargetAddress (Read/Write)

DNS Operationsl rttMonEchoAdminTargetAddressString (Read/Write)l rttMonEchoAdminNameServer (Read/Write)

HTTP and FTP Operationsl rttMonLatestHTTPOperRTTl rttMonLatestHTTPOperDNSRTTl rttMonLatestHTTPOperTCPConnectRTTl rttMonLatestHTTPOperTransactionRTTl rttMonEchoAdminURL (Read/Write)l rttMonEchoAdminOperation (Read/Write)

ICMP Echo Operationsl rttMonEchoAdminTargetAddress (Read/Write)

TCP Connect Operationsl rttMonCtrlAdminTimeout (Read/Write)l rttMonEchoAdminControlEnable (Read/Write)l rttMonEchoAdminTargetAddress (Read/Write)l rttMonEchoAdminTargetPort (Read/Write)

251

UDP Jitter Operationsl rttMonLatestJitterOperSumOfPositivesSDl rttMonLatestJitterOperSumOfPositivesDSl rttMonLatestJitterOperSumOfNegativesSDl rttMonLatestJitterOperSumOfNegativesDSl rttMonLatestJitterOperNumOfPositivesSDl rttMonLatestJitterOperNumOfPositivesDSl rttMonLatestJitterOperNumOfNegativesSDl rttMonLatestJitterOperNumOfNegativesDSl rttMonLatestJitterOperPacketLossSDl rttMonLatestJitterOperPacketLossDSl rttMonLatestJitterOperPacketMIAl rttMonLatestJitterOperPacketLateArrivall rttMonLatestJitterOperPacketOutOfSequencel rttMonLatestJitterOperRTTSuml rttMonLatestJitterOperNumOfRTTl rttMonLatestJitterOperOWSumSDl rttMonLatestJitterOperOWSumDSl rttMonLatestJitterOperNumOfOW

VoIP UDP Jitter Operationsl rttMonLatestJitterOperMOSl rttMonEchoAdminSourceAddressl RttMonEchoAdminSourcePortl RttMonEchoAdminTargetAddressl RttMonEchoAdminTargetPortl RttMonEchoAdminVrfNamel RttMonEchoAdminTOS

252

UDP Jitter Operations

Appendix C: MIBs Maintained by VoIP and Network Quality Manager

l RttMonEchoAdminTOSl RttMonEchoAdminInterval

VoIP Specific MIBsl rttMonEchoAdminSourceAddressl rttMonCtrlAdminFrequencyl rttMonEchoAdminCodecTypel rttMonEchoAdminCodecPayloadl rttMonEchoAdminCodecNumPacketsl rttMonEchoAdminCodecIntervall rttMonEchoAdminICPIFAdvFactorl rttMonScheduleAdminRttLifel rttMonScheduleAdminRttStartTime

253

Appendix D: Supported Versions ofCisco Unified Call ManagerVoIP and Network Quality Manager uses the CISCO-CCM-MIB and supportsCisco Unified Call Manager versions 6, 7, 8, 9 and 10.Note: If you have multiple polling engines, you must install the same version ofIP SLA Manager on all polling engines before you will be able to add a CallManager server.The following table lists the OIDs used for Call Manager.

Name OID

ccmRegisteredPhones 1.3.6.1.4.1.9.9.156.1.5.5.0

ccmUnregisteredPhones 1.3.6.1.4.1.9.9.156.1.5.6.0

ccmRejectedPhones 1.3.6.1.4.1.9.9.156.1.5.7.0

ccmRegisteredGateways 1.3.6.1.4.1.9.9.156.1.5.8.0

ccmUnregisteredGateways 1.3.6.1.4.1.9.9.156.1.5.9.0

ccmUnregisteredGateways 1.3.6.1.4.1.9.9.156.1.5.10.0

OIDs from the ccmTableName OID

ccmVersion 1.3.6.1.4.1.9.9.156.1.1.2.1.4

ccmInetAddressType 1.3.6.1.4.1.9.9.156.1.1.2.1.6

ccmInetAddress 1.3.6.1.4.1.9.9.156.1.1.2.1.7

ccmClusterId 1.3.6.1.4.1.9.9.156.1.1.2.1.8

254

Appendix D: Supported Versions of Cisco Unified Call Manager

OIDs from the ccmRegionTableName OID

ccmRegionIndex 1.3.6.1.4.1.9.9.156.1.1.4.1.1

ccmRegionName 1.3.6.1.4.1.9.9.156.1.1.4.1.2

OIDs from the ccmGatewayTableName OID

ccmGatewayName 1.3.6.1.4.1.9.9.156.1.3.1.1.2

ccmGatewayDescription 1.3.6.1.4.1.9.9.156.1.3.1.1.4

ccmGatewayStatus 1.3.6.1.4.1.9.9.156.1.3.1.1.5

ccmGatewayInetAddressType 1.3.6.1.4.1.9.9.156.1.3.1.1.7

ccmGatewayInetAddress 1.3.6.1.4.1.9.9.156.1.3.1.1.8

ccmGatewayTimeLastStatusUpdt 1.3.6.1.4.1.9.9.156.1.3.1.1.11

ccmGatewayTimeLastRegistered 1.3.6.1.4.1.9.9.156.1.3.1.1.12

ccmGatewayProductTypeIndex 1.3.6.1.4.1.9.9.156.1.3.1.1.15

OIDs from the ccmProductTypeTableName OID

ccmProductType 1.3.6.1.4.1.9.9.156.1.1.8.1.2

ccmProductName 1.3.6.1.4.1.9.9.156.1.1.8.1.3

ccmProductCategory 1.3.6.1.4.1.9.9.156.1.1.8.1.4

255

OIDs from the ccmPhoneTableName OID

ccmPhoneIndex 1.3.6.1.4.1.9.9.156.1.2.1.1.1

ccmPhonePhysicalAddress 1.3.6.1.4.1.9.9.156.1.2.1.1.2

ccmPhoneDescription 1.3.6.1.4.1.9.9.156.1.2.1.1.4

ccmPhoneIpAddress 1.3.6.1.4.1.9.9.156.1.2.1.1.6

ccmPhoneStatus 1.3.6.1.4.1.9.9.156.1.2.1.1.7

ccmPhoneTimeLastRegistered 1.3.6.1.4.1.9.9.156.1.2.1.1.8

ccmPhoneE911Location 1.3.6.1.4.1.9.9.156.1.2.1.1.9

ccmPhoneProductTypeIndex 1.3.6.1.4.1.9.9.156.1.2.1.1.18

ccmPhoneName 1.3.6.1.4.1.9.9.156.1.2.1.1.20

OIDs from the ccmPhoneExtnTableName OID

ccmPhoneExtnIndex 1.3.6.1.4.1.9.9.156.1.2.5.1.1

ccmPhoneExtn 1.3.6.1.4.1.9.9.156.1.2.5.1.2

OIDs from the ccmH323DeviceTableName OID

ccmH323DevName 1.3.6.1.4.1.9.9.156.1.11.1.1.2

ccmH323DevDescription 1.3.6.1.4.1.9.9.156.1.11.1.1.4

ccmH323DevInetAddressType 1.3.6.1.4.1.9.9.156.1.11.1.1.5

256

OIDs from the ccmPhoneTable

Appendix D: Supported Versions of Cisco Unified Call Manager

Name OID

ccmH323DevInetAddress 1.3.6.1.4.1.9.9.156.1.11.1.1.6

ccmH323DevStatus 1.3.6.1.4.1.9.9.156.1.11.1.1.21

ccmH323DevStatusReason 1.3.6.1.4.1.9.9.156.1.11.1.1.22

ccmH323DevTimeLastStatusUpdt 1.3.6.1.4.1.9.9.156.1.11.1.1.23

ccmH323DevTimeLastRegistered 1.3.6.1.4.1.9.9.156.1.11.1.1.24

ccmH323DevProductTypeIndex 1.3.6.1.4.1.9.9.156.1.11.1.1.31

257

Appendix E: How VoIP and NetworkQuality Manager CreatesOperationsThe following sections detail how VoIP and Network Quality Manager createsnew operations on your network devices:

l Owner Field Valuel SNMP-Based Operationsl CLI-Based Operations

Owner Field ValueVoIP and Network Quality Manager sets the Owner field value using thefollowing naming scheme:SW.IpSla.<pollerMachineName>.<dbCatalogName>

Where:

l <pollerMachineName> is the name of the server that is running theprimary or additional poller assigned to a node that is a source node foran IP SLA operation.

l <dbCatalogName> is the name of the database on the database server.

SNMP-Based OperationsThe following tables list the OIDs and values that are used to create newSNMP-based operations:

l DHCP Operationsl DNS Operationsl FTP Operationsl HTTP Operations

258

Appendix E: How VoIP and Network Quality Manager Creates Operations

l ICMP Echo Operationsl TCP Connect Operationsl UDP Echo Operationsl UDP Jitter Operationsl VoIP UDP Jitter Operations

DHCP Operations

MIB name OID number Value

rttMonCtrlAdminRttType

1.3.6.1.4.1.9.9.42.1.2.1.1.4.<opNumber>

11 (Dhcp)

rttMonEchoAdminProtocol

1.3.6.1.4.1.9.9.42.1.2.2.1.1.<opNumber>

29 (DhcpAppl)

rttMonCtrlAdminOwner

1.3.6.1.4.1.9.9.42.1.2.1.1.2.<opNumber>

See “OWNER FieldValue”

rttMonCtrlAdminNvgen

1.3.6.1.4.1.9.9.42.1.2.1.1.10.<opNumber>

1

rttMonEchoAdminSourceAddress

1.3.6.1.4.1.9.9.42.1.2.2.1.6.<opNumber>

Source IP (only ifspecified)

rttMonEchoAdminTargetAddress

1.3.6.1.4.1.9.9.42.1.2.2.1.2.<opNumber>

DHCP IP

rttMonCtrlAdminThreshold

1.3.6.1.4.1.9.9.42.1.2.1.1.5.<opNumber>

MAX(WarningRttThreshold,CriticalRttThreshold)

rttMonCtrlAdminFrequency

1.3.6.1.4.1.9.9.42.1.2.1.1.6.<opNumber>

Frequency (s)

rttMonCtrlAdminTimeout

1.3.6.1.4.1.9.9.42.1.2.1.1.7.<opNumber>

Frequency * 0.6 (ms)

259


rttMonScheduleAdminRttLife

1.3.6.1.4.1.9.9.42.1.2.5.1.1.<opNumber>

Forever

rttMonScheduleAdminRttStartTime

1.3.6.1.4.1.9.9.42.1.2.5.1.2.<opNumber>

Now

rttMonCtrlAdminStatus

1.3.6.1.4.1.9.9.42.1.2.1.1.9.<opNumber>

Create & Go (activation)

DNS Operations



1.3.6.1.4.1.9.9.42.1.2.1.1.4.<opNumber>

8 (Dns)


1.3.6.1.4.1.9.9.42.1.2.2.1.1.<opNumber>

26 (DnsAppl)


1.3.6.1.4.1.9.9.42.1.2.1.1.2.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.1.1.10.<opNumber>

1

rttMonEchoAdminTargetAddressString

1.3.6.1.4.1.9.9.42.1.2.2.1.11.<opNumber>

Host name to resolve

rttMonEchoAdminNameServer

1.3.6.1.4.1.9.9.42.1.2.2.1.12.<opNumber>

DNS server IP

rttMonEchoAdminVrfName

1.3.6.1.4.1.9.9.42.1.2.2.1.26.<opNumber>

VRF name (only ifspecified)


1.3.6.1.4.1.9.9.42.1.2.1.1.5.<opNumber>


260

DNS Operations




1.3.6.1.4.1.9.9.42.1.2.1.1.6.<opNumber>

Frequency (s)


1.3.6.1.4.1.9.9.42.1.2.1.1.7.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.5.1.1.<opNumber>

Forever


1.3.6.1.4.1.9.9.42.1.2.5.1.2.<opNumber>

Now


1.3.6.1.4.1.9.9.42.1.2.1.1.9.<opNumber>


FTP Operations



1.3.6.1.4.1.9.9.42.1.2.1.1.4.<opNumber>

12 (Ftp)


1.3.6.1.4.1.9.9.42.1.2.2.1.1.<opNumber>

30 (FtpAppl)


1.3.6.1.4.1.9.9.42.1.2.1.1.2.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.1.1.10.<opNumber>

1


1.3.6.1.4.1.9.9.42.1.2.2.1.26.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.2.1.6.<opNumber>


rttMonEchoAdminOperation

1.3.6.1.4.1.9.9.42.1.2.2.1.13.<opNumber>

3 (FtpGet)

261


rttMonEchoAdminURL

1.3.6.1.4.1.9.9.42.1.2.2.1.15.<opNumber>

Target URL


1.3.6.1.4.1.9.9.42.1.2.1.1.5.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.1.1.6.<opNumber>

Frequency (s)


1.3.6.1.4.1.9.9.42.1.2.1.1.7.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.5.1.1.<opNumber>

Forever


1.3.6.1.4.1.9.9.42.1.2.5.1.2.<opNumber>

Now


1.3.6.1.4.1.9.9.42.1.2.1.1.9.<opNumber>

Create & Go (activation infact)

HTTP Operations



1.3.6.1.4.1.9.9.42.1.2.1.1.4.<opNumber>

7 (Http)


1.3.6.1.4.1.9.9.42.1.2.2.1.1.<opNumber>

25 (HttpAppl)


1.3.6.1.4.1.9.9.42.1.2.1.1.2.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.1.1.10.<opNumber>

1

262

HTTP Operations




1.3.6.1.4.1.9.9.42.1.2.2.1.26.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.2.1.6.<opNumber>


rttMonEchoAdminOperation

1.3.6.1.4.1.9.9.42.1.2.2.1.13.<opNumber>

1 (HttpGet)

rttMonEchoAdminURL

1.3.6.1.4.1.9.9.42.1.2.2.1.15.<opNumber>

Target URL


1.3.6.1.4.1.9.9.42.1.2.1.1.5.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.1.1.6.<opNumber>

Frequency (s)


1.3.6.1.4.1.9.9.42.1.2.1.1.7.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.5.1.1.<opNumber>

Forever


1.3.6.1.4.1.9.9.42.1.2.5.1.2.<opNumber>

Now


1.3.6.1.4.1.9.9.42.1.2.1.1.9.<opNumber>


ICMP Echo Operations



1.3.6.1.4.1.9.9.42.1.2.1.1.4.<opNumber>

1 (Echo)

263



1.3.6.1.4.1.9.9.42.1.2.2.1.1.<opNumber>

2 (IpIcmpEcho)


1.3.6.1.4.1.9.9.42.1.2.1.1.2.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.1.1.10.<opNumber>

1


1.3.6.1.4.1.9.9.42.1.2.2.1.26.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.2.1.6.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.2.1.2.<opNumber>

Target IP


1.3.6.1.4.1.9.9.42.1.2.1.1.5.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.1.1.6.<opNumber>

Frequency (s)


1.3.6.1.4.1.9.9.42.1.2.1.1.7.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.5.1.1.<opNumber>

Forever


1.3.6.1.4.1.9.9.42.1.2.5.1.2.<opNumber>

Now


1.3.6.1.4.1.9.9.42.1.2.1.1.9.<opNumber>


264

ICMP Echo Operations


TCP Connect Operations



1.3.6.1.4.1.9.9.42.1.2.1.1.4.<opNumber>

6 (TcpConnect)


1.3.6.1.4.1.9.9.42.1.2.2.1.1.<opNumber>

24 (IpTcpConn)


1.3.6.1.4.1.9.9.42.1.2.1.1.2.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.1.1.10.<opNumber>

1


1.3.6.1.4.1.9.9.42.1.2.2.1.26.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.2.1.6.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.2.1.2.<opNumber>

Target IP

rttMonEchoAdminTargetPort

1.3.6.1.4.1.9.9.42.1.2.2.1.5.<opNumber>

Target port


1.3.6.1.4.1.9.9.42.1.2.1.1.5.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.1.1.6.<opNumber>

Frequency (s)


1.3.6.1.4.1.9.9.42.1.2.1.1.7.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.5.1.1.<opNumber>

Forever

265



1.3.6.1.4.1.9.9.42.1.2.5.1.2.<opNumber>

Now


1.3.6.1.4.1.9.9.42.1.2.1.1.9.<opNumber>


UDP Echo Operations



1.3.6.1.4.1.9.9.42.1.2.1.1.4.<opNumber>

5 (UdpEcho)


1.3.6.1.4.1.9.9.42.1.2.2.1.1.<opNumber>

3 (IpUdpEchoAppl)


1.3.6.1.4.1.9.9.42.1.2.1.1.2.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.1.1.10.<opNumber>

1


1.3.6.1.4.1.9.9.42.1.2.2.1.26.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.2.1.6.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.2.1.2.<opNumber>

Target IP


1.3.6.1.4.1.9.9.42.1.2.2.1.5.<opNumber>

Target port


1.3.6.1.4.1.9.9.42.1.2.1.1.5.<opNumber>


266

UDP Echo Operations




1.3.6.1.4.1.9.9.42.1.2.1.1.6.<opNumber>

Frequency (s)


1.3.6.1.4.1.9.9.42.1.2.1.1.7.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.5.1.1.<opNumber>

Forever


1.3.6.1.4.1.9.9.42.1.2.5.1.2.<opNumber>

Now


1.3.6.1.4.1.9.9.42.1.2.1.1.9.<opNumber>





1.3.6.1.4.1.9.9.42.1.2.1.1.4.<opNumber>

9 (Jitter)


1.3.6.1.4.1.9.9.42.1.2.2.1.1.<opNumber>

27 (JitterAppl)


1.3.6.1.4.1.9.9.42.1.2.1.1.2.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.1.1.10.<opNumber>

1


1.3.6.1.4.1.9.9.42.1.2.2.1.26.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.2.1.6.<opNumber>


rttMonEchoAdminSourcePort

1.3.6.1.4.1.9.9.42.1.2.2.1.7.<opNumber>

Source port

267



1.3.6.1.4.1.9.9.42.1.2.2.1.2.<opNumber>

Target IP


1.3.6.1.4.1.9.9.42.1.2.2.1.5.<opNumber>

Target port

rttMonEchoAdminTOS

1.3.6.1.4.1.9.9.42.1.2.2.1.9.<opNumber>

Type Of Service (ifspecified)

rttMonEchoAdminPktDataRequestSize

1.3.6.1.4.1.9.9.42.1.2.2.1.3.<opNumber>

100

rttMonEchoAdminNumPackets

1.3.6.1.4.1.9.9.42.1.2.2.1.18.<opNumber>

100

rttMonEchoAdminInterval

1.3.6.1.4.1.9.9.42.1.2.2.1.17.<opNumber>

20


1.3.6.1.4.1.9.9.42.1.2.1.1.5.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.1.1.6.<opNumber>

Frequency (s)


1.3.6.1.4.1.9.9.42.1.2.1.1.7.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.5.1.1.<opNumber>

Forever


1.3.6.1.4.1.9.9.42.1.2.5.1.2.<opNumber>

Now


1.3.6.1.4.1.9.9.42.1.2.1.1.9.<opNumber>


268



VoIP UDP Jitter Operations



1.3.6.1.4.1.9.9.42.1.2.1.1.4.<opNumber>

9 (Jitter)


1.3.6.1.4.1.9.9.42.1.2.2.1.1.<opNumber>

27 (JitterAppl)


1.3.6.1.4.1.9.9.42.1.2.1.1.2.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.1.1.10.<opNumber>

1


1.3.6.1.4.1.9.9.42.1.2.2.1.26.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.2.1.6.<opNumber>


rttMonEchoAdminSourcePort

1.3.6.1.4.1.9.9.42.1.2.2.1.7.<opNumber>

Source port


1.3.6.1.4.1.9.9.42.1.2.2.1.2.<opNumber>

Target IP


1.3.6.1.4.1.9.9.42.1.2.2.1.5.<opNumber>

Target port

rttMonEchoAdminTOS

1.3.6.1.4.1.9.9.42.1.2.2.1.9.<opNumber>

Type Of Service (ifspecified)

rttMonEchoAdminCodecType

1.3.6.1.4.1.9.9.42.1.2.2.1.27.<opNumber>

Codec type:0 = NA1 = G711ULAW2 = G711ALAW3 = G729A

269


rttMonEchoAdminCodecPayload

1.3.6.1.4.1.9.9.42.1.2.2.1.29.<opNumber>

100 (if codec specified)

rttMonEchoAdminPktDataRequestSize

1.3.6.1.4.1.9.9.42.1.2.2.1.3.<opNumber>

100 (if no codecspecified)

rttMonEchoAdminCodecNumPackets

1.3.6.1.4.1.9.9.42.1.2.2.1.30.<opNumber>


rttMonEchoAdminNumPackets

1.3.6.1.4.1.9.9.42.1.2.2.1.18.<opNumber>

100 (if no codecspecified)

rttMonEchoAdminCodecInterval

1.3.6.1.4.1.9.9.42.1.2.2.1.28.<opNumber>


rttMonEchoAdminInterval

1.3.6.1.4.1.9.9.42.1.2.2.1.17.<opNumber>

20 (if no codec specified)

rttMonEchoAdminICPIFAdvFactor

1.3.6.1.4.1.9.9.42.1.2.2.1.31.<opNumber>

0 by default, configurableinternally


1.3.6.1.4.1.9.9.42.1.2.1.1.5.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.1.1.6.<opNumber>

Frequency (s)


1.3.6.1.4.1.9.9.42.1.2.1.1.7.<opNumber>



1.3.6.1.4.1.9.9.42.1.2.5.1.1.<opNumber>

Forever


1.3.6.1.4.1.9.9.42.1.2.5.1.2.<opNumber>

Now


1.3.6.1.4.1.9.9.42.1.2.1.1.9.<opNumber>

Create & Go (activationin fact)

270

VoIP UDP Jitter Operations


CLI-Based OperationsThe following examples list the commands that are used to create new CLI-based operations:

l ICMP Path Echo Operationsl ICMP Path Jitter Operations

ICMP Path Echo OperationsIP SLA Syntax

configure terminalip sla <opNumber>path-echo <dest_IP> [source-ip <source_IP>]owner <swIdentifier>threshold <threshold># MAX(WarningRttThreshold,

CriticalRttThreshold)frequency <frequencyMs>vrf <vrfName># VRF name (only if specified)tos <typeOfService># Type Of Service (only if specified)history filter allhistory buckets-kept 1history lives-kept 1samples-of-history-kept 30exitip sla schedule <opNumber> life forever start-time nowexit

271

IP SLA Monitor Syntax

configure terminalip sla monitor <opNumber>type pathEcho protocol ipIcmpecho <dest_IP> [source-ipaddr

<source_IP>]owner <swIdentifier>threshold <threshold># MAX(WarningRttThreshold,

CriticalRttThreshold)frequency <frequencyMs>vrf <vrfName># VRF name (only if specified)tos <typeOfService># Type Of Service (only if specified)filter-for-history allbuckets-of-history-kept 1lives-of-history-kept 1samples-of-history-kept 30exitip sla monitor schedule <opNumber> life forever start-timenowexit

RTR Syntax

configure terminalrtr <opNumber>type pathEcho protocol ipIcmpecho <dest_IP> [source-ipaddr


CriticalRttThreshold)frequency <frequencyMs>vrf <vrfName># VRF name (only if specified)tos <typeOfService># Type Of Service (only if specified)filter-for-history allbuckets-of-history-kept 1lives-of-history-kept 1samples-of-history-kept 30exitrtr schedule <opNumber> life forever start-time nowexit

272



ICMP Path Jitter OperationsIP SLA Syntax

configure terminalip sla <opNumber>path-jitter <dest_IP> [source-ip <source_IP>]owner <swIdentifier>threshold <threshold># MAX(WarningRttThreshold,

CriticalRttThreshold)frequency <frequencyMs>vrf <vrfName># VRF name (only if specified)tos <typeOfService># Type Of Service (only if specified)history filter allhistory buckets-kept 1history lives-kept 1samples-of-history-kept 30exitip sla schedule <opNumber> life forever start-time nowexit


configure terminalip sla monitor <opNumber>type pathJitter dest-ipaddr <dest_IP> [source-ipaddr


CriticalRttThreshold)frequency <frequencyMs>vrf <vrfName># VRF name (only if specified)tos <typeOfService># Type Of Service (only if specified)filter-for-history allbuckets-of-history-kept 1lives-of-history-kept 1samples-of-history-kept 30exitip sla monitor schedule <opNumber> life forever start-timenowexit

273

RTR Syntax

configure terminalrtr <opNumber>type pathJitter dest-ipaddr <dest_IP> [source-ipaddr


CriticalRttThreshold)frequency <frequencyMs>vrf <vrfName># VRF name (only if specified)tos <typeOfService># Type Of Service (only if specified)filter-for-history allbuckets-of-history-kept 1lives-of-history-kept 1samples-of-history-kept 30exitrtr schedule <opNumber> life forever start-time nowexit

274

RTR Syntax

Appendix F: Database MaintenanceThe primary tasks that are available for maintaining an SQL database are datasummarization and database compaction. Data summarization occursautomatically as part of the nightly maintenance program. You can also rundatabase maintenance on demand from the Windows Start menu.

Running Database MaintenanceDatabase maintenance performs a series of data summarizations that help youoptimize the size of your database. Data summarization consists of gatheringall the collected network data for a defined period of time, calculating statisticsfrom the data, and then discarding the data itself while retaining the statistics.By regularly running database maintenance, you can realize significant spacesavings and performance improvements.Database maintenance can either be run directly from the Start menu, orscheduled for a set Archive Time and initiated from the Poller Settings view inthe Web Console. In either case, after it is started, database maintenancenormally proceeds without further attention. The following procedure providesthe steps to perform Database Maintenance.Note: Administrative privileges are required to run Database Maintenance.To run the Database Maintenance utility:

1. If you want to run database Maintenance from the Web Console,complete the following steps:

a. Click Settings in the top right of the web console, and then clickPoller Settings in the Settings group.

b. Click Perform Maintenance Now in the Database Settings area.

2. If you want to run database Maintenance from the Start menu, clickStart > All Programs > SolarWinds Orion > Advanced Features >Database Maintenance, and then click Start.

275

Documents

VoIP and Network Quality Manager Administrator Guide