You are on page 1of 453

For the latest SAM documentation, see the SolarWinds Support Center.

SolarWinds
Server & Application Monitor
Version 6.3

Administrator Guide

Last Updated: November 7, 2016
Retrieve the latest version from: https://support.solarwinds.com/Success_Center/Server_Application_Monitor_(SAM)/Documentation

© 2016 SolarWinds Worldwide, LLC. All rights reserved.

This document may not be reproduced by any means nor modified, decompiled, disassembled, published
or distributed, in whole or in part, or translated to any electronic medium or other means without the prior
written consent of SolarWinds. All right, title, and interest in and to the software and documentation are
and shall remain the exclusive property of SolarWinds and its respective licensors.

SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED,
STATUTORY OR OTHERWISE, ON SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER INCLUDING
WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE, AND NONINFRINGEMENT. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORS
BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY EVEN
IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The SolarWinds and other SolarWinds marks, identified on the SolarWinds website, as updated from
SolarWinds from time to time and incorporated herein, are registered with the U.S. Patent and Trademark
Office and may be registered or pending registration in other countries. All other SolarWinds trademarks
may be common law marks or registered or pending registration in the United States or in other countries.
All other trademarks or registered trademarks contained and/or mentioned herein are used for
identification purposes only and may be trademarks or registered trademarks of their respective
companies.

Server & Application Monitor Administrator Guide, Version 6.3, 10/19/2016

2

Table of Contents
Information for SAM Installations 24

Monitor your environment with SAM 25

Applications defined and monitored in SAM 25

How SAM works 28

Prepare and install SAM 31

Requirements for SolarWinds SAM 33

SAM hardware requirements 33

SAM software requirements 35

SolarWinds SAM database server (SQL server) requirements 36

SAM requirements for virtual machines and servers 39

Requirements for monitoring Microsoft Hyper-V, VMware ESXi, and ESX Servers 40

Agent requirements 41

Agent resource consumption 42

Agent port requirements 43

SolarWinds High Availability requirements 44

Networking requirements 45

Additional SAM technology requirements 45

SAM technology requirements 45

SNMP requirements for monitored devices 46

Additional SolarWinds SAM requirements 46

Asset inventory and hardware health monitoring requirements 46

AppInsight for SQL requirements and permissions 47

AppInsight for Exchange requirements and permissions 49

AppInsight for IIS requirements and permissions 50

Requirements for the Windows Scheduled Task Monitor 51

SNMP requirements for monitored devices 52

3

Scale SAM for larger environments 52

SAM licensing model detailed 53

See the available component monitors remaining in your license 55

Configure the SolarWinds Orion server to use the correct syslog port 56

Multi-module system guidelines 56

Small deployment guidelines 56

Medium deployment guidelines 57

Large deployment guidelines 58

Security enhancements and exceptions for SolarWinds SAM 60

Enable secure channels with SSL 60

Configure the Orion Web Console for SSL 61

Configure the Orion Web Console to require SSL 61

Enable FIPS 62

Antivirus exclusions and service accounts 63

Directories 63

Ports 64

Service Accounts 64

Run SolarWinds SAM 64

Get Started with SAM 65

License Orion Platform products 65

What does the web-based License Manager show? 66

What can I do in the web-based License Manger? 66

Activate licenses with Internet access 67

Activate licenses offline 68

Assign licenses 68

Stack licenses 68

Assign licenses to a polling engine 68

Move licenses: deactivate and re-activate 69

Synchronize licenses 69

4

Add or upgrade licenses 69

Update a license 70

Upgrade and migrate SAM 71

Upgrading SAM 71

Migrating SAM and the SQL Database 71

Troubleshooting 71

Remove your SAM installation 71

Discover and manage devices 73

Discover and add network devices 73

Discover your network with the Discovery Wizard 73

Add nodes using Active Directory 77

Credentials for Active Directory discovery 78

Automatically add discovered nodes 78

Add discovered devices to SolarWinds 80

Add a single node for monitoring 83

Import nodes from a list of IP addresses 84

Manage scheduled discovery results 85

Minimize SNMP processing load during discoveries using the Discovery Ignore List 85

Add ignored devices back to discovery 85

Choose the polling method to use 86

External Node (No Status) 86

Status Only: ICMP 86

Most Devices: SNMP & ICMP 86

Windows Servers: WMI and ICMP 86

Windows and Linux Servers: Agent 87

View monitored objects on maps 87

Display nodes in the Worldwide Map of Orion nodes resource 87

Add nodes manually 88

Edit the position of locations 88

5

Add or remove nodes in locations, or rename locations 88

Delete locations 89

Place nodes automatically on the Worldwide Map 89

Place objects into the map using custom properties 90

Network Atlas 91

What can you see on maps? 91

What customization options are there? 91

Installing and using Network Atlas 92

Install Network Atlas 92

Start Network Atlas 93

Create network maps 93

Advanced mapping techniques 100

Delete a custom icon 103

Add custom icons from graphics files 104

Assign a custom icon to an object 104

Environment requirements 106

User requirements 106

Configure environment for the map import 107

Advanced map layouts 108

Display Network Atlas maps in the Orion Web Console 110

Display maps in the Orion EOC Web Console 111

Manage devices in the Orion Web Console 111

Stop monitoring devices 111

View node data in tooltips 112

Edit node properties 112

Edit the node name, web address, and which view opens when you double-click the node 113

Edit polling settings 113

Edit dependencies or custom properties 114

Add what additional data you want to poll on the node 114

6

Customize alerting thresholds 114

Promote a node from ICMP to SNMP monitoring 114

View the resources and statistics monitored on a node 115

Scheduling a Node Maintenance Mode Time Period 115

Suspend collecting data for monitored nodes 115

Resume data collection for nodes 116

Poll and rediscover devices immediately 116

Troubleshoot Windows Server memory over 100% 116

Promoting a Node to WMI Monitoring 117

Group objects and mirror network dependencies in the Orion Web Console 117

Group monitored objects 117

Create groups 118

Edit group properties or change the group members 119

Delete groups 119

Set the group status based on the status of the group members 119

Mirror network object dependencies in the Orion Web Console 120

Create a dependency between network objects 120

Edit a dependency between network objects 121

Delete a dependency between network objects 122

View active alerts on child objects when the parent object is down 122

Discover applications in your environment 123

Application Discovery 123

Add application monitors to nodes 125

Customize the application details view 126

Custom application details view 126

Select a view for a template 126

Select a view for an application 127

Customize SAM Application Summary views 128

Viewing node and application data in tooltips 130

7

Node tooltips 130

Application tooltips 130

Add SolarWinds SAM data to the Node Details view 132

Monitor your network in the Orion Web Console 134

View events, alerts, traps, and syslogs in the Orion Web Console Message Center 134

View the resources and statistics monitored on a node 135

View network events in the Web Console 135

Filter the displayed logged events in the Web Console 135

Remove events from the Web Console 135

View notifications 136

Monitor hardware health 136

Monitored Hardware Sensors 137

Enable hardware health monitoring 137

Enable monitoring from the Add Node wizard 137

Enable hardware health monitoring on a node 137

Enable, disable, or adjust hardware health sensors 138

Update hardware health statistics 138

Enable hardware sensors 138

Disable hardware sensors 138

Edit hardware health thresholds 139

Change hardware health temperature units 139

Hardware Details 140

Current hardware health status 140

Hardware Health Overview chart 141

Change hardware health threshold values 142

Monitor virtual infrastructure in the Orion Web Console 143

Prerequisites to monitoring virtual infrastructure 143

Add virtual servers for monitoring 144

Assess the status of the virtual environment 144

8

View ESX host details 145

Assign credentials to virtual servers 145

Assign credentials to Hyper-V servers 145

Assign credentials to VMware servers 145

Change VMware credentials in the Orion Web Console 146

Poll ESX hosts controlled by vCenter servers directly 146

Monitor with Orion agents in SAM 147

Overriding agent and agentless monitoring 147

Communication type 147

Templates and component monitors 148

Reports 149

Monitor devices with SolarWinds Orion agents 150

Agent settings 150

Navigate to the Agent Settings page 150

Adjust the Global Agent Settings 150

Agent communication modes 151

Server-initiated communication 151

Agent-initiated communication 151

Configure SNMP for agents 152

Configure SNMP 152

Configure SNMP v3 153

Credentials and privileges used on Linux-based computers 154

SSH credentials 155

Credentials with elevated privileges 155

SNMP credentials 155

Service account privileges 155

Certificates and the agent 156

Agent deployment 156

Deploy an agent with the Add Node wizard 157

9

Deploy an agent to a monitored node 158 Deploy the agent manually to a Windows computer 158 Deploy an agent manually to a Linux-based computer 159 Mass deploy an agent on Windows 160 Deploy agents on Linux-based computers through a repository 161 Deploy with a Gold Master Image 162 Deploy an agent with Patch Manager 163 Deploy on Windows Core Servers 167 Agent management 169 Manage Agents toolbar options 169 Manage Agents table columns 170 Edit agent settings 172 Track your polling method 172 View the status of agent plug-ins 173 Edit agent settings once deployed 174 Connect to or register a previously installed agent 175 Change the agent communication mode 176 Change the agent port 176 Upgrade agents manually 177 Agent migrations 177 Migrate agents from one Orion instance to another 177 Migrate certificates to a new server 178 Deploy an agent to a monitored node 178 Edit agent settings once deployed 180 Use a group policy to migrate agents 181 Troubleshooting agent deployment 181 Monitor Syslog messages 182 Before you begin 182 Configure the SolarWinds Orion server to use the correct syslog port 183 10 .

SPAN. and the information displayed in the Trap Viewer 191 Configure Trap Viewer filters and alerts 191 What is a Trap Template? 193 Monitor Quality of Experience metrics 194 How SolarWinds Packet Analysis Sensors work 195 Network Packet Analysis Sensor (NPAS) 195 Server Packet Analysis Sensor (SPAS) 195 Limitations to Packet Analysis Sensors 195 Common Packet Analysis Sensor deployment scenarios 196 Aggregation per application 197 Aggregation per site 198 Aggregation per computer 200 Monitor traffic to and from a port mirror. or network tap 202 11 . and the displayed columns in the Syslog Viewer 187 Trigger alerts when receiving specific Syslog messages 187 Forward syslog messages 189 Monitor SNMP traps 189 Before you begin 190 View SNMP traps in the Orion Web Console 190 View current traps in the Trap Viewer 190 Search for traps in the Trap Viewer 190 Define how many traps to display. Syslog message priorities 183 Syslog facilities 183 Syslog severities 184 View Syslog messages in the Orion Web Console 185 Clear Syslog messages in the Orion Web Console 186 View and clear Syslog messages in the Syslog Viewer 186 Search for Syslog messages in the Syslog Viewer 186 Define the number of messages displayed. if you want to refresh the traps view. trap retention. message retention.

Monitor traffic to and from a specific node 204 Remove a sensor 205 Monitor QoE applications and nodes 205 Manage global QoE settings 205 Monitor applications for QoE 207 Monitor nodes with a network sensor 208 Ignore traffic from applications or nodes 209 Define custom HTTP applications 210 Advanced sensor configuration 211 Configure which interface to monitor for traffic 211 Set the number of CPU cores and the amount of memory QoE can use 212 Configure QoE thresholds 212 Packet Analysis Sensor agents 213 Set up and monitor Cisco Unified Computing Systems (UCS) 213 Monitor your environment using AppStack 215 Troubleshooting with AppStack 216 AppStack categories and data 217 Supported categories and data 218 Customize the AppStack view 221 Filtering the AppStack 222 Filter options 223 Creating filters 223 Create an AppStack layout 224 Understanding the AppStack data 225 Object status and colors 226 Using quick links 227 Using the overview bar 228 Manage Asset Inventory 229 Enable and disable the Asset Inventory dashboard 230 12 .

Enable Asset Inventory data collection via the Management Resource 230 Asset Inventory data collection 231 Change the Default Asset Inventory Collection Period 231 Add server hardware monitoring 231 Add Node Wizard 231 Manually add hardware monitoring 232 Manage processes. services. and events in real time 233 The Real Time Process Explorer 234 Access the Real Time Process Explorer from the application details page 235 Monitor unmonitored processes 236 Use the Real Time Process Explorer 237 Real Time Process Explorer alerts 239 Real Time Process information in top 10 alerts 240 The Service Control Manager 242 Access the Service Control Manager (SCM) from the Node Details page 243 Use the Service Control Manager 244 Start and stop a service 244 Monitor a service with SAM 244 The Windows Scheduled Task Monitor 245 Requirements for the Windows Scheduled Task Monitor 246 Enable the Windows Scheduled Task Monitor 247 Access the Windows Scheduled Task Monitor 248 Understand the Windows Scheduled Task Monitor 249 Alert me when task last run result is non successful 249 Windows Scheduled Task Monitor returned status codes 250 WTSM status 253 The Real Time Event Log Viewer 255 Access the Real Time Event Viewer from the Node Details page 256 Filter events in the Real Time Events Viewer 257 13 . tasks.

0 273 Create a firewall rule 274 Configure IIS 275 Test the application 277 Set PowerShell permissions for Exchange 278 Resolving errors after a reinstall 278 Find Exchange URL settings 279 Attachment extensions acknowledged by AppInsight for Exchange 282 AppInsight for IIS 283 Navigate the AppInsight for IIS details view 283 Configure AppInsight for IIS on nodes 285 14 .0 272 Set PSLanguageMode to FullLanguage for the PowerShell website 272 Create a self-signed certificate 272 Configure WinRM 2. Filter collected events 257 Reading events in the Real Time Events Viewer 259 Monitor events in the Real Time Events Viewer 260 AppInsight for Exchange 261 Navigating AppInsight for Exchange 261 Recommendations for AppInsight for Exchange 263 Configure AppInsight for Exchange on nodes 264 Edit the AppInsight for Exchange template 267 Advanced Manual Configuration of AppInsight for Exchange 268 Configuration changes to enable AppInsight for Exchange 268 Find Exchange credentials 269 Manually configure the Exchange server 270 Define Exchange credentials 270 Grant Exchange Access 271 Set Mailbox Search Access 272 Install PowerShell 2.

0 on Windows Server 2008 and 2008 R2 290 Set execution policy on the target computer 292 Create a self-signed certificate 293 Create a firewall rule 294 Update WsMan limits 295 Create a WinRM listener 296 Find IIS URL settings 297 Verify a server's WinRM PowerShell instance 297 AppInsight for SQL 299 Navigate the different AppInsight for SQL views 299 Add AppInsight for SQL to a node via discovery 300 Monitor an SQL named instance 301 Monitor with AppInsight for SQL 301 Monitor with application templates 302 Edit the AppInsight for SQL template 303 Monitor clusters with AppInsight for SQL 304 Manage application monitor templates and component monitors 305 Create and manage templates 308 Create a template 308 Create a custom template (Example) 309 Create a SolarWinds Windows service application template 309 Assign a template to a node 310 Edit a template 310 Copy a template 311 15 . Edit the AppInsight for IIS template 288 Edit the AppInsight for IIS Template 288 Manually configure AppInsight for IIS 289 Install PowerShell 2.0 and the WebAdministration snapin 290 Download PowerShell 2.0 290 Install PowerShell 2.

Export and import templates 311 Delete templates 311 Tag a template 312 Change between 32-bit and 64-bit polling 312 Modify and customize monitors 314 Multi-edit components 314 Delete or Disable a monitor 315 Linux system configurations for component monitors 315 Apache configurations 315 Tomcat configurations 316 ODBC 317 General ODBC setup 317 Postgre SQL 317 MySQL 319 JMX 319 Squid 320 Nagios 320 IBM DB2 (with ODBC) 320 Monitors and templates using WMI 323 Component monitors using WMI 323 Templates using WMI 323 Assign and edit application monitors to nodes 327 Create component monitors from the Component Monitor Wizard 328 Scan nodes for applications 330 Manage templates and groups 332 Assign an application template to a group 334 Unassign application monitors from a group 336 Unmanage and manage assigned application monitors 337 Script custom component monitors 338 16 .

Linux/Unix Script monitor 339 Field Descriptions 339 Create a Linux or Unix script monitor 341 Nagios scripting 344 Windows Script monitor 345 Field Descriptions 345 Create a Windows Script Monitor 347 Nagios Script monitor 351 Field Descriptions 351 Scripts must report status through return codes 353 Test script output 354 Windows PowerShell monitor 355 Field Descriptions 355 Create a Windows PowerShell monitor 357 Application Monitor Thresholds 360 Inheriting Thresholds 361 Threshold Adjustments at the Template Level 361 Threshold Adjustments at the Component Monitor Level 361 Multi-Value scripts and thresholds 362 Apply baseline thresholds at the template level 363 Apply baseline thresholds at the application level 365 Adjust threshold settings and apply baseline data 367 Change the amount of data used in baseline calculations 367 Apply baseline thresholds at the template level 367 Apply baseline thresholds at the application level 368 Use latest baseline details 369 Edit capacity planning thresholds 370 View latest baseline details 371 View the Latest Baseline Details Page 371 17 .

Example tasks for application monitors 372 Create your first application and alert 373 Create a WMI monitor 373 Apply the WMI monitor template 373 Alert on the WMI application via email 373 Scan for applications to monitor 375 Monitor a specific URL 376 Monitor VMware performance counters using an application monitor 377 Add components to the application monitor 377 Monitor and restart stopped Windows services 379 Create the monitor 379 Create an alert that restarts any stopped Windows services and sends an email 379 Monitor large directories 380 Monitor IIS application pools 382 Use the JMX component monitor wizard 383 Add a JMX component monitor 383 Configure the SOAP monitor 384 Load WSDL Files 384 Manually Enter XML 385 High Availability in SolarWinds products 387 How does it work? 387 What is a Virtual IP address? 388 How do I choose a VIP address? 388 Which IP address is used as the source? 388 Examples of matching the binary bits 389 High Availability deployment walk-through 389 Optional deployment steps 390 Set up the standby server 390 Set up an HA pool 391 18 .

Configure High Availability settings 392 Set up the default High Availability email 392 Activate High Availability pool licenses 393 How failovers work 393 Upgrade High Availability pool members 394 Use alerts to monitor your environment 395 Alert preconfiguration tasks 395 Configure the default information in the email action 395 Best practices and tips for alerting 396 Navigate to the Alert Manager 397 Create new alerts to monitor your environment 397 Set alert properties 397 Define the conditions that must exist to trigger an alert 398 Define the conditions that must exist to reset an alert 400 Schedule when an alert monitors your environment 401 Define what happens when an alert is triggered 402 Add actions to alerts 402 Add what happens when an alert is not acknowledged 403 Define what happens when the alert is reset 404 Review the alert's configuration 405 Commonly created alerts 405 Alert me when a server goes down 405 Alert on custom properties 406 View triggered alerts in the Orion Web Console 407 Remove alerts from the Active Alerts list 408 Test alert triggers and actions 408 Test trigger conditions 408 Test alert actions while creating or editing an alert 408 Test alert actions in the Action Manager 409 19 .

Modify multiple alerts or share alerts 409 Add actions to alerts without opening the Alert Wizard 409 Share alerts with others 409 Build complex conditions 410 Wait for multiple objects to meet the trigger condition 410 Evaluate multiple condition blocks 411 How condition blocks are evaluated 411 Evaluate multiple object types 411 Manage alert actions 411 Assign an action to an alert 412 Enable and Disable Alerts 412 Available alert actions 412 Change a custom property 412 Create a ServiceNow incident 412 Use reference fields 413 Filter expression examples 413 Configure a ServiceNow incident 413 Dial a paging or SMS service 414 Email a web page to users 414 Create a dynamic URL 415 Execute an external batch file 415 Execute an external Visual Basic script 416 Log the alert message to a file 417 Log the alert to the NPM event log 417 Change the resource allocation of a virtual machine 418 Delete a snapshot of a virtual machine 418 Move a virtual machine to a different host 419 Move a virtual machine to a different storage 420 Pause a virtual machine 420 20 .

Power off a virtual machine 421 Power on a virtual machine 422 Restart a virtual machine 422 Suspend a virtual machine 423 Take a snapshot of a virtual machine 423 Play a sound when an alert is triggered 424 Send a Windows Net message 425 Restart IIS sites or application pools 426 Send an SNMP trap 426 Send a GET or POST request 427 Send a syslog message 427 Send an email or page 428 Manually set a custom status 429 Use the speech synthesizer to read alerts 430 Log an alert to the Windows Event Log on a specific server 430 Changes in the alerting engine 431 Changed or removed functionality 431 Database changes 431 Macro or variable changes 432 Alert migration to the web 432 Migration issues 432 Limitations to migrated alerts 432 Share alerts with other SolarWinds products 433 Integrate an Orion Platform product with ServiceNow 433 Before you begin 433 Install and configure the SolarWinds Alert Integration application in ServiceNow 434 Create a ServiceNow integration user with Web service access only 434 Configure an Orion Platform product with ServiceNow 434 Access remote nodes 435 21 .

SSH. schedule. and import reports in the Orion Web Console 436 Create reports in the Orion Web Console 436 Modify an existing web-based report 436 Create a new web-based report 437 Customize a web-based report layout 440 Add content to a web-based report 441 Add a custom chart or table to a web-based report 441 Add a data series and customize a chart 442 Add a data series and customize a table 443 Build conditions 444 Restrict who can access reports 444 Create or add a report limitation category 445 Restrict user access to the report 445 Generate reports on a schedule 445 Schedule a report to run automatically while creating or editing a report 445 Create and assign report schedules in Report Manager 446 Schedule reports from the Schedule Manager 447 Export reports 447 Export reports as XML 448 Import XML reports 448 Export Excel and PDF reports from the Orion Web Console 448 Modify legacy reports in Report Writer 448 Report Writer Preview Mode 449 Report Writer Design Mode 449 22 . Use Integrated Remote Desktop 435 Access nodes using HTTP. export. and Telnet 435 Web-based SSH 435 Create and view reports 436 Predefined reports 436 Create.

Customize report headers and footers with Report Writer 449 Create and modify reports in Report Writer 450 Report Writer General Options tab 450 Report Writer Select Fields Options tab 450 Report Writer Filter Results Options tab 451 Report Writer Top XX Records Options tab 451 Report Writer Time Frame Options tab 452 Report Writer Summarization Options tab 452 Report Writer Report Grouping Options tab 452 Report Writer Field Formatting Options tab 452 Allow access to restricted Report Writer reports 453 Export reports from Report Writer 453 23 .

Information for SAM Installations Before you install SAM. 24 . see the SAM Troubleshooting Guide. explore the following sections for information on different technology and licensing requirements:  n SAM hardware requirements  n Requirements for virtual machines and servers  n Additional monitoring requirements  n Security enhancements and exceptions for SolarWinds SAM  n Additional SAM technology requirements For instructions and guides for SAM setup. see Upgrade and migrate SAM. For troubleshooting issues and error messages.

an application is a collection of component monitors inherited from a template. For example. or script. counter.Monitor your environment with SAM SolarWinds Server & Application Monitor (SolarWinds SAM) gives you the tools to monitor your applications and environment through a single web console. For example. authentication servers. operating systems. web-based license management and much more. any application. leverage SAM monitored data and nodes with Orion features including automated application discovery.  n AppInsight: monitors every aspect for Microsoft Exchange. SAM monitors applications in public. private. is unique. and hybrid environments using:  n AppStack: provides an interactive visual mapping within Orion with an in-depth perspective through the entire environment to help identify the root cause of performance and availability issues. along with its parameters and returned values and/or states. SolarWinds SAM uses the data received to display vital statistics concerning the health of the system. It is a collection of component monitors designed to monitor a server or application. SolarWinds SAM provides the following types of templates: 25 . Node A node is considered to be any endpoint of a given network. SAM includes custom collections of templates. Monitor over 200 application types including application servers. database servers. displaying metrics. IIS. port availability. and alerts to intelligently monitor application status and issues. agent monitoring. and actions. another monitor can return the percentage of free space of a volume. server. and SQL servers in your environment. and performance counters to assess the status of every aspect of your application and the health of the application as a whole. Each monitor type.  n Alerts: identify issues using customizable triggers. static or baseline thresholds. and more. or computer on a network is considered a node. application monitors. status. Another type of component monitor can return up to ten values. Applications defined and monitored in SAM In SolarWinds SAM.  n Application Monitor templates: combine process monitors. status. device. Template A template is the blueprint for an application. and issues to manage and maintain these applications and servers. The type of information returned by the component monitor is based upon the type of monitor being utilized. High Availability. You can customize numerous templates using only the component monitors you need for a specific environment. A component monitor queries for values returned by a process. one type of monitor can report the up or down status of a service or process. Integrated with the Orion Platform.

Every application template includes a number of component monitors per application or service to monitor. SolarWinds recommends deploying a single template. homegrown application that you need to monitor. use the AppInsight templates to monitor these applications.  n If you have other business-critical applications. For a full list of component monitors. You can also obtain a template from the thwack community for an application not shipped with SAM.  n If you have a custom. see SAM Component Monitor Types. you can build a custom template. If you have business-critical Exchange. For a list of out-of-the-box templates. Application An application or application monitor in SAM monitors a specific application or server using a collection of component monitors. apply one of the many preconfigured application templates that ship with SolarWinds SAM. All component monitors return at least one value or one status condition. making necessary edits to customize it to your environment.  n AppInsight application templates are preconfigured templates that provide detailed information. Microsoft IIS. 26 . You can include multiple versions of component monitors for specific system monitoring or for customized scripts. These templates have their own mechanism of discovering elements of an application dynamically. and then deploying the edited template on all similar applications. Each node. or Microsoft SQL instances. along with its applications and component monitors. Component monitors return the current status or value of a monitored service or process. see the SAM Template Reference. can be viewed through the Orion Web Console as shown in the diagram below. Component Monitor A component monitor is the fundamental element of an application. They also have special licensing.

the applications based on that template are affected. The following illustration explains the template and application relationship. 27 . This inheritance relationship is beneficial if you need to make a lot of changes. only the individual application is affected. Conversely. rather than making one change to 100 applications (and therefore 100 changes). if you make a change at the application level.If you make a change at the template level. you can change one item that affects all 100 applications based on that template. For example.

All calls are made in real time and displayed on a Web Console accessible from any supported browser. SAM operations can be visualized with the following flowchart: 28 . there are no agents installed on your servers and no remote software to maintain. SAM provides real time feedback on your applications and trending through statistics stored in the Orion database.How SAM works Using UDP. SNMP. As a standalone product. Keeping with the SolarWinds common components infrastructure. and WMI calls to your environment and application servers. TCP.

Installed as a module in your family of SolarWinds products. SAM can be visualized with the following flowchart: 29 .

30 .

Prepare the Orion SQL Server database  3. and configure your SAM product and environment. refer to the SAM Getting Started Guide. Install a licensed copy of SolarWinds SAM  4. and Syslog communication and data collection. Plan for a production deployment  2. WMI. install. SNMP. the following topics can prepare and walk you through the process:  1.Orion Platform products monitor the health and performance of your network through ICMP. Prepare and install SAM To plan. Configure the Orion server and database 31 .

If you are upgrading one or more modules. Copy the installer to your APE or AWS. The order for your product installation is first the main polling engine. For SAM 6.  5. Install your modules on the Main Poller.3. use our Success Center to search for errors and troubleshoot the issues. Orion multi-module system guidelines These guidelines help you plan and build a multi-module environment for SAM and other Orion and SolarWinds products. click Settings > All Settings > Web Console Settings. you may have a bundle installer or Orion Scalability Engine Installer to download and run. This single installer will upgrade all Orion modules on each of these servers.  3. next all additional polling engines. click Settings > All Settings > Polling Engines. When complete. such as the Flow Storage Database for NTA. you will use the Orion Scalability Engine Installer for APE and AWS servers:  1. all modules are upgraded! If you encounter issues.  n For the APE installer. and finally the additional web server. Depending on the version of SAM. 32 .  n For the AWS installer.  2. These may include additional databases. Download this installer through the Orion Web Console.  4. you will need to upgrade your additional polling engines and additional web servers. Run the appropriate installer on your APE and AWS.

Requirements for SolarWinds SAM SolarWinds recommends installing your SolarWinds product on one server.AL1100 AL1500-ALX CPU speed Quad core. Solarwinds does not support installing SAM on domain controllers.solarwinds. 2. view the Scalability Engine Guidelines (PDF). 33 . Installations of multiple SolarWinds SAM servers using the same database are not supported. Use the minimum hardware configuration if you are evaluating the product or do not anticipate heavy usage. contact the SolarWinds sales team. see the following sections:  n SAM hardware requirements  n SAM software requirements  n SolarWinds SAM database server (SQL server) requirements  n Agent requirements  n Additional SAM technology requirements The Configuration Wizard installs the following required x86 components if they are not found on your Orion database server:  n Microsoft SQL Server Native Client  n Microsoft SQL Server Management Objects SAM hardware requirements The following table lists minimum hardware requirements and recommendations for your SolarWinds SAM server. For details on multi-module environments. and installing the Orion database on its own SQL Server. For more information about sizing SolarWinds Orion to your network.AL300 AL700 . 3. Installing multiple SolarWindsOrion Platform products on the same computer may change the requirements.0 GHz or better better better Do not enable Physical Address Extension (PAE). or visit www. Hardware requirements are listed by SolarWinds SAM license level.5 GHz or Quad core.com. HARDWARE AL150 . 2. For detailed requirements information. see the Multi-Module Requirements Guidelines for SAM.5 GHz or Quad core. SolarWinds strongly suggests using the recommended hardware configuration to avoid potential performance issues caused by a heavy load or custom configurations such as increased data retentions or more frequent polling intervals.

AL300 AL700 . no ports need to be open on the host where Port the agent is installed.  n 25 (TCP) SMTP port for non-encrypted messages  n 161 (UDP) for statistics collection  n 162 (UDP) for Trap Server listening for incoming messages  n 443 (TCP) default port for https binding and bi-directional ESX/ESXi server polling and for Cisco UCS monitoring  n 465 (TCP) for SSL-enabled email alert actions  n 587 ( TCP) for TLS-enabled email alert actions  n 1801 (TCP) for MSMQ WCF binding  n 4369 (TCP) required for RabbitMQ messaging (epmd)  n 5671 (TCP) for SSL encrypted RabbitMQ messaging from the additional polling engines to the main polling engine. Memory 4 GB minimum 8 GB minimum 16 GB minimum 8 GB recommended 16 GB recommended 32 GB recommended Server port Ports 4369. TCP port 17778 must be open on the Orion server Requirements: or the additional poller with which the agent is associated.AL1100 AL1500-ALX Hard drive 10 GB minimum 15 GB minimum 30 GB minimum space 20 GB recommended 40 GB recommended 100 GB recommended Some common files may need to be installed on the same drive as your server operating system. HARDWARE AL150 . This is a backup communication port that is not used by default. 34 . and 5672 are opened by default.  n 25672 (TCP) required for RabbitMQ messaging (Erlang distribution)  n 17777 (TCP) open for Orion module traffic  n 17778 (HTTPS and TCP) open to access the SolarWinds Information Service API and agent communication  n 17779 (HTTP and HTTPS) for the SolarWinds Toolset Integration  n 17791 (TCP) open for agent communication on any SolarWinds Orion server running Windows Server 2008 R2 SP1 Agent Open  n 17778 (Active mode): In Active mode. However. 25672. It is used on a continual basis once the agent has been deployed. These ports can be blocked requirements by the firewall.  n 5672 (TCP) for non-encrypted RabbitMQ messaging between the primary and additional polling engines. This port must be opened on the Orion server (inbound) and allowed by the firewall. Communication is initiated outbound from the agent to the Orion server.

SAM software requirements The following table lists software requirements and recommendations for a SAM installation. 2012 Datacenter Edition) edition. no ports need to be opened on the firewall for the Orion server.  n SolarWinds neither recommends nor supports the installation of any Orion product on the same server or using the same database server as a Research in Motion (RIM) Blackberry server.Basic Transition Mechanisms for IPv6 Hosts and Routers.  n 17790 (Passive mode): In Passive mode.1 (except for Standard installed.2. Edition)  n Windows Server 2016  n Windows 10 Installing SAM on Windows Server 2012 R2 Essentials is not supported. If Passive agents are used.4. CIDR notation is not supported for IPv6 addresses. and 2012 R2.  n Beginning with SAM 6. port 17790 must be opened on the host where the agent is installed and allowed by the firewall. SOFTWARE REQUIREMENTS Production Evaluation Only Operating  n Windows Server 2008 R2 SP1 with IIS in  n Windows 7 SP1 system 32-bit mode. HARDWARE AL150 . see RFC 4213 .AL300 AL700 . 35 . you can only install on Windows Server 2008 R2 SP1. 2012 R2. Operating  n English system  n German languages  n Japanese  n Simplified Chinese IP address IPv4 version IPv6 implemented as a dual stack. see Changing the Agent Port. For more information. 2012. and 2016.AL1100 AL1500-ALX Important: This requirement is for Active agents only. IIS must be  n Windows 8.  n Windows 8 (except for Standard  n Windows Server 2012. For more information.  n SolarWinds does not support installing SolarWinds Orion on domain controllers.

 n IIS is installed by the SolarWinds installer.5 Framework Compatible with 4. PowerShell SAM PowerShell Script Monitor works with PowerShell 1. For more information. SOFTWARE REQUIREMENTS Web Microsoft Internet Information Services (IIS).5 or later server  n DNS specifications require that host names be composed of alphanumeric characters (A-Z.0 or higher is required for remote execution. see RFC 952 . 36 . SolarWinds SAM database server (SQL server) requirements Your Orion Platform product and your SolarWinds Orion database should use separate servers. Accounts limited to the Orion Web Console do not require administrator privileges.2.0 installations that use web gardens.0 and higher for local execution. Be sure that you are running the same version of . 0-9). the minus sign (-). Multiple Orion server installations using the same database are not supported. RabbitMQ The following services must be running after installation is complete to collect syslog Services messages and traps:  n SolarWinds Syslog Service  n SolarWinds Trap Service User SolarWinds recommends that administrators have local administrator privileges to ensure privileges full functionality of local SolarWinds tools.).NET 4.NET on your primary server and any additional polling engines or web servers in the environment.0 or later (Toolset Integration is not supported on Firefox)  n Chrome 49.  n SolarWinds products are not compatible with IIS version 6.6. . You can install this software manually to reduce your installation time or network bandwidth.5. and periods (.DOD Internet Host Table Specification.NET . Underscore characters (_) are not allowed. version 7.NET 4.1 SolarWinds recommends using . PowerShell 2. Web  n Microsoft Internet Explorer version 11 or later with Active scripting console  n Microsoft Edge browser  n Firefox 45.0 or later  n Safari for iPhone Other MSMQ.

or 2008 R2 SP3  n SQL Server 2012. 2008 R2 SP1. 2008 SP2.5 GHz or better 2. CPU speed Quad core processor. 2. Standard. For more information. or 2008 SP4  n SQL Server 2008 R2. or Enterprise versions of the following:  n SQL Server 2008.  n Due to latency effects. This is recommended for evaluations.  n The FullWithSQL installer package automatically installs SQL Server 2014 Express. REQUIREMENTS AL150 .  n If you are managing your Orion database.AL1100 AL1500-ALX SQL Server SolarWinds supports Express. Quad core processor. 2008 SP1. SolarWinds recommends you install the SQL Server Management Studio component. We strongly recommend Simple recovery mode due to ensure best performance. 2008 R2 SP2.  n Either mixed-mode or SQL authentication must be supported. Dual quad core processor. 2012 SP2. 2008 SP3. SolarWinds does not recommend installing your SQL Server and your SolarWinds server or additional polling engine in different locations across a WAN.The following table lists software and hardware requirements for your SolarWinds Orion database server using SolarWinds SAM license levels as a reference. or 2012 SP3 (also with AlwaysOn Availability Groups)  n SQL Server 2014 (also with AlwaysOn Availability Groups) or 2014 SP1  n SQL Server 2016  n SolarWinds strongly recommends using 64-bit version of SQL Server. see this SolarWinds Knowledge Base article.0 GHz or better Hard drive 20 GB minimum 50 GB minimum 100 GB minimum space 40 GB recommended 100 400 GB recommended GB recommended SolarWinds recommends the following configuration:  n A hardware RAID Controller with a battery backed-up write back cache  n Disk Subsystem 1 Array : 2x 146 GB 115K disks RAID 1 (mirroring) for the OS 37 .AL300 AL700 .  n You can set the database recovery model to Full recovery mode only if you use Always On Availability. 2012 SP1.5 GHz or better 3.

 n Solid state drives are recommended for all components except the OS drive. some common files may need to be installed on the same drive as your server operating system.REQUIREMENTS AL150 . Memory 4 GB minimum 8 GB minimum 16 GB minimum 38 . data.AL300 AL700 .  n Mirrored drives for the OS and RAID 1+0 for database data files are recommended. a RAID 1+0 drive is strongly recommended for the SolarWinds database. Per Windows standards.AL1100 AL1500-ALX  n Disk Subsystem 2 Array 2: 1x 146 GB 15K disks RAID 1 (Pagefile + Extra Storage)  n Disk Subsystem 3 Array 3: with 6 x 15K 146 GB or 300 GB disks configured in a RAID 1+0 array to allow for maximum write performance for your SQL MDF and FILEGROUPS  n Disk Subsystem 4 Array 4: with 4x 15K 146 GB or 300 GB disks configured in a RAID 1+0 array to allow for maximum write performance for your SQL LDF Transaction LOG file  n Disk Subsystem 5 Array 5: with 4x 15k 146 GB or 300 GB disks configured in a RAID 1+0 array to allow for maximum write performance for your tempDB data file  n Disk Subsystem 6 Array 6: with 4x 15k 146 GB or 300 GB disks configured in a RAID 0 array to allow for maximum write performance for your tempDB LOG file  n Due to intense I/O requirements. and log files with a dedicated drive for the server operating system and tempdb files.  n Other RAID configurations can negatively affect your SQL Server's performance.

AL300 AL700 . 2. Authentication Either mixed-mode or SQL authentication Other If you are managing your SolarWinds Orion database.5 GHz or Quad core.REQUIREMENTS AL150 . non-business data operations to improve overall performance. You must maintain your SQL Server database on a separate. SAM requirements for virtual machines and servers SAM installations on VMware Virtual Machines and Microsoft Virtual Servers are fully supported if the following minimum configuration requirements are met for each virtual machine.AL300 AL700 . For example. The Installation Wizard installs the following required x86 components if they are not found on your Orion database server:  l SQL Server System Common Language Runtime (CLR) Types.0 GHz or better better better Allocated 10 GB minimum 15 GB minimum 30 GB minimum hard drive 20 GB recommended 40 GB recommended 100 GB recommended space 39 .AL1100 AL1500 . SAM plus 2 Additional additional pollers would require 32GB of RAM.ALX CPU speed Quad core.5 GHz or Quad core.0 or higher is required for remote execution. 3. 3 additional pollers would require 48GB Pollers of RAM.  l Microsoft SQL Server Native Client  l Microsoft SQL Server Management Objects SAM's PowerShell Script Monitor works with PowerShell 1. and so on. physical server. Orion products use secure SQL CLR stored procedures for selected. 2. Memory and Each additional poller requires 16 GB of additional RAM.AL1100 AL1500-ALX 8 GB recommended 16 GB recommended 32 GB recommended Additional memory improves both performance and reliability.0 and higher for local execution. PowerShell 2. SolarWinds recommends you software install the SQL Server Management Studio component. VM REQUIREMENTS BY SAM LICENSE LEVEL FOR REFERENCE CONFIGURATION AL150 .

ALX Due to intense I/O requirements. You must maintain your SQL Server database on a separate. VMware ESXi. FEATURES 4 4i 5i 6.1 or later Microsoft Hyper-V Server versions 2008 R2. The following methods are used by NPM to monitor VMware ESX Servers and their component features. REQUIREMENT DESCRIPTION SNMP SNMP must be enabled on all ESXi and ESX servers. 2012. VMware Tools are not a requirement but provide access to additional information. For more information about requirements. Memory 4 GB minimum 8 GB minimum 16 GB minimum 8 GB recommended 16 GB recommended 32 GB recommended Requirements for monitoring Microsoft Hyper-V. VM REQUIREMENTS BY SAM LICENSE LEVEL FOR REFERENCE CONFIGURATION AL150 . RAID 5 is not recommended for the SQL Server hard drive.AL1100 AL1500 . consult your ESX or ESXi server vendor documentation. For more information. such as IP addresses. 2012 R2 VMware VMware Tools must be installed on all virtual machines you want to monitor.AL300 AL700 .1 or later software VMware vSphere version 4. SQL Server should be hosted on a separate physical server configured as RAID 1+0. Virtualization ESXi and ESX Server version 4. physical drive. and ESX Servers Installations on VMware Virtual Machines and Microsoft Virtual Servers follow the minimum configuration requirements are met for each virtual machine. see VIM Minimum Requirements in the SolarWinds Virtual Manager documentation.0 Datacenter VMware API ESX cluster VMware API Virtual Center VMware API Detection as ESX server VMware API Volumes SNMP N/A SNMP 40 . tools If your virtual machines are on monitored ESXi and ESX servers.

1  n SUSE Linux Enterprise  n Windows 10 Server 10  n SUSE Linux Enterprise Only Pro. Before you deploy agents to a target computer. Enterprise. and Ultimate workstation Server 11 operating systems editions are supported. Windows 8. review the following system requirements. 64-bit only 41 . Licensing occurs through your product and is usually based on the number of monitored elements. 64-bit only  n Amazon AMI.0 Interfaces SNMP SNMP (partial) SNMP CPU VMware API Memory VMware API Total CPU VMware API (ESX details view) Total memory VMware API (ESX details view) Network traffic utilization VMware API (ESX details view) Guest VM list VMware API (ESX details view) Agent requirements Agent software is free.  n Linux agents run as a service daemon.  n SUSE Linux Enterprise Server 12  n Ubuntu 14. FEATURES 4 4i 5i 6. TYPE WINDOWS REQUIREMENTS LINUX Operating  n Windows Server 2008  n Red Hat Enterprise Linux 5 System  n Windows Server 2008 R2  n Red Hat Enterprise Linux 6  n Windows Server 2008 R2 SP1  n Red Hat Enterprise Linux 7  n Windows Server 2012  n CentOS 5  n Windows Server 2012 R2  n CentOS 6  n Windows 7. Windows 7 SP1  n CentOS 7  n Windows 8.  n Windows agents run as a service.

it runs as a Local System account and does not require administrative permissions to function.24% on average) Memory 10 .  n The account used for remote deployment must have access to the administrative share on the  n An account that can install target computer: \\<hostname_or_ software and create a user ip>\admin$\temp. To install a certificate. HDD Approximately 100 MB of hard drive space on the target computer. or the built-in Administrator account must be used. for installation only Agent resource consumption RESOURCE CONSUMPTION CPU Less than 1% on average under normal operating conditions (0. versions 2. see Certificates and the agent.5 (Required for Windows Server 2008 R2 SP1 and later) Security The VeriSign Root Certificate Authority (CA) must be current.100 MB. This is required because the agent software is signed using a VeriSign certificate.  n You may need to disable UAC remote restrictions. After the agent is installed.3 and Package for 32-bit or 64-bit later  n .  n User Account Control (UAC) must either be disabled on the target computer.4. depending on the number and types of jobs 42 . and group.0 (You must install this Python 3 is not supported manually if you are installing an agent on Windows Server 2008 R2 or earlier or Windows Core)  n .NET Framework 4. TYPE WINDOWS REQUIREMENTS LINUX Other The following software packages are installed by the You may need to install the Windows agent installer if necessary: following manually: software  n Microsoft Visual C++ 2013 Redistributable  n Python 2.NET Framework 4. the  n An account that can permissions following requirements must be met: connect remotely through SSH.  n Other remote or mass deployment methods do not have the same requirements. Account If you want to deploy agents from the Orion server.

Agent port requirements COMMUNICATION PORT OS DESCRIPTION METHOD 17778 Agent-initiated Windows Used continuously by the agent to communicate back to the Orion server. including jobs that ensure the agent service is still up and responding. This port (inbound) must be open on the client computer for remote deployment. TCP port 22 (outbound) must be open on the Orion server or additional polling engine and open (inbound) on the computer you want to monitor. 445 Either Windows Microsoft-DS SMB file sharing.3 kB/s versus WMI at 5. 22 Either Linux (TCP) Used to install the agent on Linux computers through SSH and SFTP or SCP. log all cron jobs. The log file can become large quickly. 43 . This must (inbound) be open on the remote computer. Also used to deploy the agent.000 agents. 135 Either Windows (DCE/RPC Locator service) Microsoft EPMAP.3 kB/s Storage 100 MB when installed A single polling engine can support up to 1. This must be opened if the remote computers you monitor run Windows 2008 R2. This port must be open on (inbound) the client computer (inbound) for remote deployment. Also used to deploy the agent. Agent: 1. If your distribution logs all cron jobs. Some Linux distributions. 17790 Server-initiated All Used to communicate with the Orion server. such as CentOS. ensure that you use a tool such as logrotate to keep your log files to a manageable size. RESOURCE CONSUMPTION Bandwidth Roughly 20% (on average) of the bandwidth consumed by the WMI protocol for transmission of the same information For example. Linux 17791 Agent-initiated Windows Used continuously by the agent to communicate back to 2008 R2 the Orion server.

 n If protecting an NTA environment.2 and later  n User Device Tracker 3. 44 .3 and later  n Database Performance Analyzer on Orion 10.  n SolarWinds does not provide failover support for any database.0.1 and later The following products can be integrated with your Orion Platform-based product.0.2 and later.8  n Engineers Toolset 11.5. but the stand-alone product is not supported.2.3 and later  n NetFlow Traffic Analyzer 4.3 and later SolarWinds strongly recommends that the hardware and software of the standby server matches the primary server.2 and later  n Patch Manager 2.SolarWinds High Availability requirements High Availability is provided for SolarWinds products released on Orion Platform products version 2016.3. The integration module between products is supported under SolarWinds High Availability.3  n Virtualization Manager 6. Supported products include:  n Network Performance Monitor 12.1 and later  n IP Address Manager 4.2.2 and later  n Firewall Security Manager 6.  n Storage Manager 6.6.4 and later  n Storage Resource Monitor 6. both servers must be able to connect to the separate NTA Flow Storage database.2.  n Both servers must be installed on Windows Server 2008 R2 or later.3 and later  n Web Performance Monitor 2.1 and later  n Server & Application Monitor 6.  n Both servers must be able to connect to your SolarWinds Orion database. Visit SolarWinds KB MT6886 to build an upgrade path.3. Using matching system specifications and installed software ensures the same performance in the event of a failover.1.  n Both servers must also meet or closely match the minimum hardware and software requirements for the products you have installed on the primary server.4 and later  n VoIP & Network Quality Manager 4.2. You cannot enable an HA pool for a server that includes non-supported products.2.1 and later  n Network Configuration Manager 7.

They do not need to be open in additional polling engine pools.  n A virtual IP address must be available on the same subnet as the primary and secondary servers. you may have additional requirements.  n All pool members must be able to resolve the host names of all additional pollers.  n Both your primary and secondary servers must be on the same subnet.  n Some SNMP trap.  n Port 5671 must be open into the HA pool with the main Orion server from all Orion servers. and secondary servers because of how Windows calculates the source IP address from the HA pool. and flow data is lost while waiting for the secondary server to become active.  n Devices sending syslogs. syslog message. SolarWinds does not support installing SAM on domain controllers. You can modify your devices to receive requests from all IP addresses or determine which IP address is used as the source IP address. and the main Orion server. For example. SAM technology requirements  n Requirements for monitoring virtual servers  n Requirements for virtual machines and servers  n Asset inventory and hardware health monitoring requirements 45 . Depending on your network. Networking requirements SolarWinds High Availability does not support IPv6 addresses.  n TCP ports 4369 and 25672 must be open between the main and secondary servers to allow RabbitMQ clustering between the two servers. primary. You may need to modify firewall rules to allow traffic from pool members and to the VIP address. and installing the Orion database on its own SQL Server. Pool members must also be able to resolve the host names of members in the same pool. additional websites.  n Devices must be able to accept inbound connections from the source IP and VIP addresses. These ports exchange EPMD and Erlang distribution protocol messages for RabbbitMQ. and NetFlow information to your Orion server must be configured to send the information to the VIP address and receive requests from the pool. Installations of multiple SolarWinds SAM servers using the same database are not supported. You do not need dedicated NICs.  n Both pool members must have static IPv4 addresses set on the network adapter. you may need to modify the NetFlow firewall rules to allow incoming TCP traffic on port 2055 to go to the VIP address. Up to three IP addresses per pool may be in use among the VIP. Additional SAM technology requirements SolarWinds recommends installing your SolarWinds product on one server. SNMP traps.

2 or higher  n IBM server with IBM Director (Common Agent. Additionally. Additional SolarWinds SAM requirements Enterprise-level SolarWinds SAM deployments with the potential for more than 1.x  n CIM  n VMware API 46 .000 monitors may need additional computing resources above the standards required for SolarWinds common components. these nodes must be managed by SAM to enable collection of Asset Inventory data: Operating System Protocol Windows SNMP. SNMPv2c. The following hardware supports Asset Inventory data collection:  n Dell servers with OpenManage Server Administrator Managed Node v7.x and v5.2 or later  n HP servers with HP System Insight Manager v6. WMI Linux SNMP AIX (v7 and higher) SNMP VMware ESX/ESXi v4.3 or higher)  n Additional hardware not listed here may be supported with a limited amount of information returned from the polling process. This means you do not need to have hardware health monitoring enabled to have inventory data collected and displayed.   Asset inventory and hardware health monitoring requirements Asset inventory data collection can be enabled for both physical and virtual assets and functions independently of hardware health monitoring. Consult your device documentation or a technical representative of your device manufacturer to acquire specific instructions for configuring SNMP on your device. The Asset Inventory feature supports the following operating systems and protocols and does not count against your SAM component monitor license. or SNMPv3 enabled device on your network. v6.  n AppInsight for SQL requirements and permissions  n AppInsight for Exchange requirements and permissions  n AppInsight for IIS requirements and permissions  n Requirements for the Windows Scheduled Task Monitor  n SNMP requirements for monitored devices SNMP requirements for monitored devices SolarWinds SAM can monitor the performance of any SNMPv1.

SP1.x AppInsight for SQL requirements and permissions AppInsight for SQL supports the following versions of Microsoft SQL Server: MICROSOFT SQL SERVER VERSION V ERSIONS SUPPORTED Microsoft SQL Server 2008 Without SP. SP2.  n SNMP for VMware nodes not polled via CIM or the VMware API VMware API for ESX/ESXi hosts polled via HTTPS vCenter.0  n Dell OpenManage Support for VMware ESXi 5. SP2 SP3 Microsoft SQL Server 2012 Without SP.2x VMware  n HP Management Agents for VMware ESX 4. Third-party software required for Asset Inventory information HP  n HP ESXi Offline Bundle  n HP Management Agents for VMware ESX 4. SP1 Microsoft SQL Server 2014   Microsoft SQL Server 2016   47 . SP3 Microsoft SQL Server 2008 R2 Without SP.x Only (Not for ESXi 4.0 Dell/VMWare  n OpenManage Support for VMware ESXi 5.0  n HP ESXi Offline Bundle for VMware ESXi 5.x)   n HP Insight Management WBEM Providers for ESXi 5. SP1.x)   n HP ESXi Offline Bundle for VMware ESXi 5.x  IBM  n IBM Director v6.0  HP/VMware  n HP Management Agents for VMware ESX 4.x Only (Not for ESXi 4.0  n HP ESXi Offline Bundle for VMware ESXi 5.x)   n HP Insight Management WBEM Providers for ESXi 5.x Only (Not for ESXi 4.

 n Connect permission to all databases. AppInsight for SQL permissions The minimum SQL permissions required to use AppInsight for SQL are as follows:  n Must be a member of the db_datareader role on the msdb system database. Following are the requirements and permissions needed for AppInsight for SQL.  n View any definition. SAM uses TCP detection during discovery. N'AppInsightUser' The following script configures permissions for a SQL account with Windows Authentication: 48 .@name_in_db = 'AppInsightUser' EXEC sp_addrolemember N'db_datareader'.  n Connect permission to Master database.  n SQL clusters cannot be polled with domain credentials via the Orion Agent because Agents do not work with AppInsight for SQL when the SQL server being monitored is in a cluster. However. Additional information is available for nodes managed via WMI. For example.@name_in_db = 'AppInsightUser' GRANT EXECUTE ON xp_readerrorlog TO AppInsightUser USE msdb EXEC sp_adduser @loginame = 'AppInsightUser' . it does require TCP. Important: This following scripts make changes directly to the database.  n Connect permission to the Msdb database.  n Must have VIEW SERVER STATE permissions. Notes about AppInsight for SQL:  n AppInsight for SQL supports both the SNMP and WMI protocols and uses SQL to gather information about the application." This is the result of the last client protocol that is tried during connection to the SQL server.  n Must be member of db_datareader role in the MSDB database.  n Agents do not work with AppInsight for SQL when the SQL server being monitored is in a cluster. The following script configures permissions for a SQL account: USE master GRANT VIEW SERVER STATE TO AppInsightUser GRANT VIEW ANY DEFINITION TO AppInsightUser GRANT VIEW ANY DATABASE TO AppInsightUser EXEC sp_adduser @loginame = 'AppInsightUser' .  n Execute permission on the Xp_readerrorlog stored procedure. Important: AppInsight for SQL does not require named-pipes.AppInsight for SQL data is collected at the same default five minute polling interval as traditional application templates. You should create a database backup before running either of these scripts. You may receive an error message pertaining to "named-pipes.

this additional level of permission is required.  n To provide organization-wide capability. and so on. Membership to this group gives the user object read-only access to the entire Exchange environment. but in order to modify Exchange and WinRM settings on the server. Note: For Exchange access. Hub Transport Servers need to be accessed via RPC. N'Domain\AppInsightUser' EXECUTE sp_MSforeachdb 'USE [?]. this is not required. the account must be a member of the Local Administrators group. the service account (Domain User) needs to be a member of the View-Only Organization Management group. Data is collected at the same default five minute polling interval as traditional application templates. as well as to poll performance counters.0 installed  n Exchange 2013 must have PowerShell 3. @name_in_db = ''Domain\AppInsightUser''' AppInsight for Exchange requirements and permissions AppInsight for Exchange works only with the Mailbox Role. In order for the account to be configured correctly. but they are not needed for monitoring once configuration is complete. USE master GRANT VIEW SERVER STATE TO "Domain\AppInsightUser" GRANT VIEW ANY DEFINITION TO "Domain\AppInsightUser" EXEC sp_adduser @loginame = 'Domain\AppInsightUser' . which is used for data storage.@name_in_db = 'Domain\AppInsightUser' EXEC sp_addrolemember N'db_datareader'.g.@name_in_db = 'Domain\AppInsightUser' GRANT EXECUTE ON xp_readerrorlog TO "Domain\AppInsightUser" USE msdb EXEC sp_adduser @loginame = 'Domain\AppInsightUser' .)  n In order to gather information. All other Exchange servers running different roles should use the Exchange application templates included with SAM if you intend to monitor them. the user object must be assigned the Mailbox Search management role within Exchange.0 installed 49 . Microsoft Exchange Versions Supported  n Microsoft Exchange Server 2010  n Microsoft Exchange Server 2013  n Microsoft Exchange Server 2016 AppInsight for Exchange Requirements and Permissions  n Local administrator permissions are needed for automatic configuration. EXEC sp_adduser @loginame = ''Domain\AppInsightUser''.  n For Mailbox statistics. without providing any domain or local access on the Exchange server. creating or deleting users. PowerShell Requirements  n Exchange 2010 must have PowerShell 2. It also prevents possible abuse by an unauthorized user accessing the account (e. modifying Exchange environment configuration.

see Manually configure the Exchange server.5 Microsoft Windows 2012 IIS 8.  n To install PowerShell on the Exchange server. AppInsight for IIS requirements and permissions Review the requirements and permissions for configuring AppInsight for IIS nodes in your environment. Non-administrative permissions for polling and monitoring is only achievable using the optional Orion Agent. see Set PowerShell permissions for Exchange.0 is required for Windows 2012 (regardless of Exchange version) For information on configuring PowerShell permissions.  n Administrator rights or equivalent credentials to the IIS server bring monitored is needed for configuration. AppInsight for IIS data is collected at the same default 5 minute polling interval as other application templates. AppInsight for IIS requirements and permissions  n PowerShell 2.  n Permissions must be granted for PowerShell to be accessed  n PowerShell 2.  n AppInsight for IIS supports the following versions of Microsoft operating systems and their respective IIS versions: MICROSOFT OS V ERSION >IIS V ERSION SUPPORTED Microsoft Windows 2008 IIS 7. see Find Exchange URL settings.  n To find Exchange URL settings.0 or higher must be installed on the IIS server. Consider upgrading Internet Explorer or using an alternate web browser such as Firefox or Chrome.0 Microsoft Windows 2008 R2 IIS 7.5 If any prerequisite is missing. see Manually configure the Exchange server. AppInsight for IIS technologies and ports The following table outlines the technologies and ports used by AppInsight for IIS: The IIS server must have the ports open on the managed nodes. the application goes into an Unknown state.  n IIS 7.0 Microsoft Windows 2012 R2 IIS 8. Common Configuration Issues  n To add local administrative privileges to an Active Directory account. Some resources may not function properly in Internet Explorer 8 or earlier. 50 .0 or higher must be installed.

port mentioned in the secure bindings of a site. You must create a firewall exception on the remote computer. HTTP TCP. PowerShell TCP port 5986 This is a secure listener hosted in the WinRM service. Shares) Requirements for the Windows Scheduled Task Monitor The WSTM supports monitoring tasks on the following operating systems:  n Windows 2003 R2 SP2  n Windows 2008  n Windows 2008 R2  n Windows 2012  n Windows 2012 R2 When SAM is installed on Windows 2003 R2 SP2. SMB (Windows TCP port 445 Used for Site Directory Information and Log Directory Information.65535 the operating system. The WSTM will not work for tasks from every level of the Task Scheduler Library. the HTTP Monitor is hidden. TECHNOLOGY PORT NOTES RPC Endpoint TCP port 135 SAM uses this port to establish WMI/RPC connections to the Mapper remote computer. WMI TCP ports 1025 . the secure bindings of a site. the SSL Certificate Expiration Date port mentioned in Monitor will be hidden. HTTPS TCP. At least one If the connection is not allowed. the HTTPS Monitor will be hidden. Only tasks from root directory can be monitored. At least one If the connection is not allowed. RPC is required for getting performance counters information via the ASP. scheduled tasks on Windows 2008 or later cannot be polled by the Windows Scheduled Task Monitor (WSTM). At least one If the connection is not allowed. port mentioned in the bindings of a site. Microsoft Windows uses a random port from this range 5000 or TCP ports for WMI communications. By default. SSL TCP. 51 . The default port range differs based on 49152 .NET resource.

SNMP requirements for monitored devices SolarWinds SAM can monitor the performance of any SNMPv1-. of up to ~1 GB of polled data per poller in the event that the connection between the polling engine and the database is temporarily lost. Scalability One APE for every 8-10k component monitors. Pollers Available? Poller Yes.  n SolarWinds SAM is capable of monitoring VMware ESX and ESXi Servers versions 3. SNMPv2c-. using MSMQ.5 and higher Remotability Available? Poller remotability is a feature that enables the local storage. Primary Poller ~8-10k component monitors per polling engine. 1 SAM server + 14 APEs). If you only want SolarWinds SAM to poll using SNMPv1. For more information about licensing. by default. Scale SAM for larger environments Stackable Yes. SolarWinds SAM attempts to use SNMPv2c to poll the device for performance information. consult your VMware documentation or technical representative. Options Maximum of 150k component monitors per primary SolarWinds SAM installation (i. or SNMPv3-enabled device on your network. Limits 25-50 concurrent Orion Web Console users.  n Unix based devices should use the configuration of Net-SNMP version 5.5 or higher that is specific to the type of Unix-based operating system in use. you must enable SNMP on all devices that are capable of SNMP communications.2 and higher. see Why are you licensing by monitors instead of by servers? 52 . for SAM versions 5. For SAM 6.  n If SNMPv2c is enabled on a device you want to monitor. Consult your device documentation or a technical representative of your device manufacturer to acquire specific instructions for configuring SNMP on your device. Two polling engines can be installed on a single server. you must disable SNMPv2c on the device to be polled. Notes:  n To properly monitor devices on your network. For more information about enabling SNMP and VMware Tools on your VMware device.e.5 and higher with VMware Tools installed on virtual machines.

5 kB / WMI poll and a 5 minute polling frequency. Most traffic related to monitoring is between an APE and Considerations the SolarWinds database. For more information. 53 . and their component statuses are changed to "Not Licensed." You can either disable some assigned component monitors to reduce your total assigned monitor count. It can be a process. the monitors that exceed your license limit are not activated. SAM licensing model detailed The SolarWinds SAM license you purchase is based on the number of allowed assigned component monitors. as long as the number of assigned component monitors does not exceed the license count. An application typically consumes 15-25 AL300 component monitors. with standard AppInsight for IIS consumes 30 component monitors per polling monitored IIS server. component AppInsight for Exchange consumes 50 component monitors monitors per mailbox role server. a service. AL700 The Windows Scheduled Task Monitor consumes five (5) AL1100 component monitors per Windows server. You can have as many application templates and assigned monitors as you need. a Nagios script. Based on 67. Bandwidth requirements depend on the size of the relevant component monitor. a performance Monitors Monitors) counter. the estimate is 1. throughput). or contact SolarWinds about upgrading your SolarWinds SAM license. WAN and/or Minimal monitoring traffic is sent between the primary SAM server and any APEs that Bandwidth are connected over a WAN. a port. see How do SNMP and WMI polling compare? WMI is best suited for environments where latency is < 100ms. ALX AppInsight for SQL consumes 50 component monitors per (Unlimited database instance. and so on. HOW IS AVAILABLE SAM QUESTIONS ANSWERS LICENSE TIERS LICENSED? By the AL150 (Up to What is a The value returned by a component monitor is a number of 150 Component measurement of application health and availability that needs Component Component Monitor? to be monitored. A component monitor provides a statistic that you want to monitor in SolarWinds SAM. If you have more assigned component monitors than allowed by your license. an URL. a User Experience Monitor.2 Mbps for 700 component monitors.

Agents Agent software is free. 50 component monitors count against your licensed number of component monitors. per Exchange Server. There may be some instances where Volumes or Nodes would be the highest factor. on and Component Monitors (refer to NPM licensing for Node & component Volume definition). HOW IS AVAILABLE SAM QUESTIONS ANSWERS LICENSE TIERS LICENSED? Why Monitor-based pricing is flexible. you have surpassed your allowed number of 300 monitors by 60. AppInsight for IIS When using AppInsight for IIS. per monitored IIS server The example below illustrates a situation where you would have 40 available component monitors available. Monitors. 30 component monitors count against your licensed number of component monitors. AppInsight for SQL When using AppInsight for SQL. Monitor-based pricing Component provides a good correlation of price to value. You remain bound by the limits of the license you own regardless of how you poll information. and not devices? Is it always Technically. AppInsight applications are licensed as 50 monitors per application and cannot be partially licensed. either via an agent or another protocol. it is based on highest number of Nodes. 54 . Volumes. per SQL instance. Component monitors? Monitors is the highest factor. but in almost every case. Windows Scheduled Task Monitor The WSTM consumes five (5) license units per node. AppInsight for Exchange When using AppInsight for Exchange. 50 component monitors count against your licensed number of component monitors. as is the case with typical applications. Due to adding AppInsight application implementations. Asset Inventory data collection Asset Inventory data collection does not count against your SAM component monitor license.

solarwinds.  3. Click Applications.com/support/ticket/serviceticket. as well as see all products you have installed on that computer. navigate to http://www. Click SAM Settings.solarwinds.solarwinds.  n To get your activation key. 55 . SolarWinds SAM licenses do not have to mirror the license count of any other installed SolarWinds product. you should step through the deactivation process a second time. You can activate or deactivate your products using the License Manager. See the available component monitors remaining in your license  1. navigate to the Customer Portal and click License Management. You no longer need your Customer ID and password. you can install SolarWinds SAM with a 150 component license on a SolarWinds NPM server with an unlimited node license. For example.com  n If you do not know your CustomerID and/or password.com/ instead of support. Licensing Information  n When using your Customer ID and password. License Paths The License Manager only works for people under active maintenance and can be downloaded from the customer portal. you can use your individual profile information. Log on to the SolarWinds Web Console with an administrator account.  2. Click SAM License Summary.aspx and request the desired information.  4. you can also click License Details in the Settings page to view the used and available component monitors.  n You can get your license information from the customer portal using the customer portal link: https://customerportal. Note: As an alternative to the previous procedure. You will prompted multiple times to confirm that you are sure you want to deactivate your product. then click the plus sign [+]. Deactivation If you have deactivation information.

aspx. 15.IPSLA 25 (up to 5.AL300  n WPM 5 .  5.5000 Orion Physical server or virtual machine Application  n Quad core processor or better Server Specifications  n 8-16 GB RAM  n 150 GB. SolarWinds Syslog Service listens for syslog messages on port 514 (UDP). If your devices use a different port for sending syslog messages.Configure the SolarWinds Orion server to use the correct syslog port By default. refer to the system requirements listed in the administrator’s guide for that module.WPM 20  n VNQM IPSLA 5 . Use the Medium Deployment guidelines for NTA.000 RPM  n 1 x 1 Gb dedicated NIC 56 . If you have only one Orion module.IP4000  n UDT UT2500 . The address in the address bar should look as follows: <your product server>/Orion/Admin/AdvancedConfiguration/Global.  1. after /Orion. On the Global tab. or change the port on which the service listens. The information here should be considered guidelines only. Copy /Admin/AdvancedConfiguration/Global.  4.SL500 (including up to 10 remote agents for DPI)  n SAM AL150 . and enter the UDP port number in the UDPListenPort entry. Small deployment guidelines Modules You can install NTA as part of a small deployment. Restart the syslog service from the notification bar or the Orion Service Manager. Click Save. scroll down to SyslogService. but it is not included in this configuration. consider reconfiguring the port on devices.aspx  3. Choose up to 3 modules:  n NPM SL100 .SyslogSettings. use these recommended guidelines for hardware and software deployment.DL200  n IPAM IP1000 . Log in to the Orion Web Console as an administrator. You can choose to use more or less hardware but your performance may vary depending on your deployment scenario. Multi-module system guidelines If you have more than one Orion Platform product.  2.000 operations)  n NCM DL50 . and paste it into your browser address bar. Go to Advanced Configuration settings.

and polling frequency. 2012. 2012.000 FPS received sustained on the main poller 2 .NET 4. 2012 R2. number of elements measured.WPM 200  n VNQM IPSLA 25 .IPSLA 50 (up to 10. 2012 R2.DL1000  n IPAM IP16. Medium deployment guidelines Modules NPM SL500 .SL2000 NTA for NPM SL2000  n 50.5 if they are not already on your server. 2012. or 2008 R2 SP1  n Microsoft SQL Server 2016. SQL Database Physical server recommended Server  n Quad core processor or better Specifications  n 16 GB RAM  n 100 GB1 (or more) storage in RAID 1+0 configuration (RAID 5 not supported)  n Windows Server 2016.000  n UDT UT10.000 RPM  n 1 x 1 Gb dedicated NIC  n Windows Server 2016. 2012 R2. 15.25. or 2008 R2 SP1 The Orion installer installs IIS (32-bit mode) and .4 additional modules:  n SAM AL700 . or 2008 R2 Standard Edition 1More or less space may be needed depending on your data retention policies.000 Orion Application Physical server or virtual machine Server Specifications  n Quad core processor or better  n 16 GB RAM  n 150 GB.  n Windows Server 2016. SQL Database Physical server recommended Server Specifications  n Dual quad core processor or better  n 64 GB RAM 57 .000 . 2014. 2012.AL1100  n WPM 50 .5 if they are not already on your server.000 operations)  n NCM DL500 .NET 4. or 2008 R2 SP1 The Orion installer installs IIS (32-bit mode) and .

see Requirements for the Orion Database Server and NTA 4. 2012. 2More or less space may be needed depending on your data retention policies. SolarWinds recommends a separate NTA Flow Storage Database.  n NTA 4.1 . 4More or less space may be needed depending on your data retention policies and the number of flows stored. You need approximately 8 GB of additional storage for every 1000 flows that are retained for 30 days. or 2008 R2 SP1 NTA-specific information  n NTA 4. Large deployment guidelines Modules NPM SLX (with multiple pollers) NTA for NPM SLX  n 50. 2014.000 flows stored for 30 days. number of elements measured.  n 250 GB2 (or more) storage in RAID 1+0 configuration (RAID 5 not supported)  n Hardware RAID Controller (software RAID not supported)  n Windows Server 2016.0 stores flow data in the SQL Database (NTA Flow Storage Database is not installed).000 component monitors  n Maximum of 50. 2012.1 only works with a 64-bit operating system.000 FPS received sustained on the main poller  n Up to 6 pollers (5 in addition to the main poller) for 300. you need a base of 100 GB plus an additional 400 GB of storage. NTA 4.000 FPS received sustained Any combination of these modules:  n SAM ALX  n 1 APE for every 10.NTA 4. For more information.0 . 2012 R2.0 Installation: Frequently Asked Questions.If the server is running a 32-bit operating system. and polling frequency. if you want 50.1 TB4 of storage capacity on local NTFS disk  n 1 x 1 Gb dedicated NIC  n Windows Server 2012 R2. 2012.000 component monitors per primary Orion SAM server + 4 APEs 58 . or 2008 R2 SP1  n Microsoft SQL Server 2016. For example. 3RAM for the NTA Flow Storage Database should be increased as the database size increases. or 2008 R2 Standard Edition NTA Flow Storage Physical server or virtual machine Database  n Quad core processor or better Server Specifications  n 16 GB3 RAM  n 100 GB .

1 and later  n Maximum of 30.000 devices per NCM instance (that is. for NCM 7. This is for your SQL MDF AND FILEGROUPS  n Disk Subsystem 4 Array 4: with 4x 15. 15.000 IP  n UDT UTX  n 150. 2012.000 ports per polling engine Orion Physical server or virtual machine Application  n Quad core processor or better Server Specifications  n 32 GB RAM  n 150 GB.000 146 GB or 300 GB disks configured in a RAID 1+0 arrays to allow for maximum write performance. 2012 R2.000 IP SLA operations per polling engine  n NCM DLX  n 1 APE for every 10.000 146 GB or 300 GB disks configured in a RAID 1+0 arrays to allow for maximum write performance. This is for your SQL LDF Transaction LOG file  n Disk Subsystem 5 Array 5: with 4x 15k 146 GB or 300 GB disks configured in a RAID 1+0 array for your tempdb data file  n Disk Subsystem 6 Array 6: with 4x 15k 146 GB or 300 GB disks configured in a RAID 0 array for your tempdb log file  n 1 Gb LAN port  n Windows Server 2016.5 if they are not already on your server. SQL Database Physical server recommended Server  n Dual quad core processor or better Specifications  n 128 GB RAM  n Hardware RAID Controller (software RAID not supported)  n Disk Subsystem 1 Array 1: 2 x 146 GB 15.000 disks RAID 1 (mirroring) operating system  n Disk Subsystem 2 Array 2: 2 x 146 GB 15. 2012 R2. or 2008 R2 SP1 59 .000 devices. NCM server + 2 NCM APEs)  n IPAM IPX  n 750.NET 4.  n VNQM IPX  n ~5. 2012.000 disks RAID 1 (Pagefile + extra storage)  n Disk Subsystem 3 Array 3: with 6x 15. or 2008 R2 SP1 The Orion installer installs IIS (32-bit mode) and .000 RPM  n 1 x 1 Gb dedicated NIC  n Windows Server 2016.

or 2008 R2 Additional Virtual machine recommended Polling  n Quad core processor or better Engine Server  n 32 GB RAM Specifications  n 150 GB.  n NTA 4. or 2008 R2 The Orion installer installs IIS (32-bit mode) and .  n Microsoft SQL Server 2016. 2012.5 if they are not already on your server. You can increase the security of your data by using SSL or FIPS.1 . SolarWinds recommends a separate NTA Flow Storage Database.0 Installation: Frequently Asked Questions.1 only works with a 64-bit operating system. 2012 R2. 2014. 2012. SolarWinds SAM uses the http protocol instead of https. 60 . Security enhancements and exceptions for SolarWinds SAM By default. see Requirements for the Orion Database Server and NTA 4.NET 4.  n Enable secure channels with SSL  n Enable FIPS For best performance. NTA 4. For more information.1 TB4 of storage capacity on local NTFS disk  n 1 x 1 Gb dedicated NIC  n Windows Server 2012 R2. SolarWinds also recommends creating an antivirus directory exclusion for the SolarWinds install folder.If the server is running a 32-bit operating system. or 2008 R2 Standard Edition NTA Flow Physical server or virtual machine Storage  n Quad core processor or better Database Server  n 16 GB3 RAM Specifications  n 100 GB . Enable secure channels with SSL SolarWinds products support the use of Secure Sockets Layer certificates to enable secure communications with the Orion Web Console. 15. NTA-specific information  n NTA 4. 2012.000 RPM  n 1 x 1 Gb dedicated NIC  n Windows Server 2016.0 .NTA 4.0 stores flow data in the SQL Database (NTA Flow Storage Database is not installed).

and click Refresh. providing credentials as required.  b.  n If your Orion database is not listed in the left pane.  d.0 and earlier. Review the configuration summary. Enter the SSL port number. click Add Default Server.Requirements  l Your server must have the required SSL certificate installed.  4.  8. Start the Database Manager from the SolarWinds Orion > Advanced Features program folder. Replace the default query with the following query. Shut down all SolarWinds services. and click Start Everything. Expand the SQL servers. In a text editor. Select Website. SolarWinds recommends that you disable SSL v3. and click Next. and click Query Table.  b.  n If your SQL Server is not listed in the left pane. Switch to the Orion Service Manager. Add a binding to https port 443 for the SolarWinds NetPerfMon site. Enable the Orion Web Console for SSL. Start the Configuration Wizard in the SolarWinds Orion > Configuration and Auto-Discovery program folder. and complete the Configuration Wizard. Change the Orion Web Console port. and navigate to SQL Servers > your SolarWinds Orion database server > SolarWindsOrion > Websites in the left pane.  a.  1. Log in to your Orion server using an account with administrative rights. select or provide the SQL Server instance you are using as your SolarWinds Orion database. open the web console configuration file. Select the login method. For more information. Click Connect to Database Server.config.  3.  5. You can also configure the Orion Web Console to require SSL. web. 61 .  2. consult the Microsoft online documentation on setting up SSL. on your primary SolarWinds server. UPDATE dbo. Due to security concerns. Click Add SQL Server.  6. and click Shutdown Everything.  d.  c.  2. Right-click the Websites table. Start the Orion Service Manager in the SolarWinds Orion > Advanced Features program folder.Websites SET SSLEnabled=1 WHERE WebsiteID=1  7. add it:  a. Configure the Orion Web Console to require SSL  1.  3. Using the format Server\Instance. Configure the Orion Web Console for SSL  1.  l Conduct secure SSL/TLS communications over port 443.  c. Port 443 is typically reserved for SSL traffic. and click Next on the Welcome window.

exe is located in the Install_Volume:\Program Files (x86)\SolarWinds\Orion folder. add the line: <httpCookies requireSSL="true" />  3.  1. In the <system. federal government.exe).  2. To enable the HTTPOnly flag for added security. Configure the Orion server for FIPS compliance. Edit it to <forms loginUrl="~/Orion/Login.FipsManager.config is C:\Inetpub\SolarWinds\.FipsManager. AES256 SolarWinds recommends that you install all FIPS-compliant SolarWinds software on FIPS-compliant servers and maintain all non-compliant SolarWinds software on non-compliant servers. Start the SolarWinds FIPS 140-2 Manager (SolarWinds. Enable FIPS FIPS (Federal Information Processing Standard) defines security and interoperability standards for computers used by the U. Save and close web.aspx" requireSSL=”true” />.S. Monitored nodes and network discoveries must use FIPS-compliant authentication and privacy or encryption methods. The default location of web.  2. FIPS-COMPLIANT METHODS Authentication SHA1 Privacy or encryption AES128. By default. Locate the line: <forms loginUrl="~/Orion/Login. SolarWinds.  5.web> section. See the Microsoft Support knowledge base for more information. locate the <httpCookies> tag. 62 .aspx" />  4. AES192. and edit it to the following: <httpCookies httpOnlyCookies="true" requireSSL="true" />  6.config.

 a. Antivirus exclusions and service accounts To run SolarWinds products you may need to exclude certain directories and ports from your antivirus software and add service accounts. Orion server  n C:\Inetpub\SolarWinds\  n C:\ProgramData\SolarWinds\  n C:\Program Files (x86)\Common Files\SolarWinds\  n C:\Program Files (x86)\Microsoft SQL Server\ 63 .  n Click the non-compliant monitored node.  3. Click Submit.  n If an installed product is not FIPS-compliant.  c. Complete the Network Sonar Wizard using the updated credentials.  b.  n Click the non-compliant network discovery. select Enable FIPS 140-2. and provide the passwords.  n If FIPS 140-2 is disabled. Select FIPS-compliant Authentication and Privacy/Encryption methods. and click Next. Click Restart now to restart all relevant SolarWinds services. and edit SNMP credentials to be FIPS- compliant. The SolarWinds FIPS 140-2 Manager will confirm that the current configuration of your SolarWinds products is FIPS-compliant. To refresh the list of non-compliant objects after editing the credentials.  b. Confirm that all SNMP credentials use FIPS-compliant Authentication and Privacy/Encryption methods. Directories Ensure that SAM has access to all required files by excluding the following directories from antivirus protection. and provide the passwords. You can also review antivirus exclusions for all Orion products in this article. click Close. and click Next.  4.  n SolarWinds assumes that C:\ is the default install volume. Confirm that all SNMP credentials are SNMPv3. restart the FIPS 140-2 Manager. Read the welcome text. and run the FIPS 140-2 Manager again. Delete or edit any credentials that are not FIPS-compliant SNMPv3.  n Do not exclude executable files. and edit its Polling Method to be FIPS- compliant. complete the following steps.  c. remove any non-compliant Orion Platform products from the FIPS-compliant server.  n If the FIPS Manager provides a list of objects or saved network discovery definitions that are not FIPS-enabled. Select SNMPv3 as the SNMP Version.  a.

After logging in.SNMP  n 1433/TCP .MS SQL  n 17777/TCP. Verify that the Location is changed to ServerName (not your domain) in the AD box. Click Login. SAM and all Orion products support different permissions for users. also exclude also the NTA Flow Storage Database directory and the appropriate backup directory from the antivirus protection.50727\Temporary ASP.50727\Temporary ASP.MS SQL  n 1434/TCP .30319\Temporary ASP.  2. 64 . Click Start > All Programs > SolarWinds Orion > Orion Web Console.SNMP  n 162/UDP .  1.0.NET\Framework64\v4.0.  n C:\Program Files (x86)\SolarWinds\  n C:\Windows\Temp\SolarWinds\  n C:\Windows\Microsoft.  n NETWORK SERVICE  n IUSR  n Authenticated Users Run SolarWinds SAM SAM is part of the Orion Web Console.NET Files  n C:\Windows\Microsoft.NET\Framework64\v2. SQL Server  n C:\Program Files\Microsoft SQL Server\  n C:\Program Files (x86)\Microsoft SQL Server\ Ports  n 80/TCP .NET\Framework\v4. we highly recommend setting up users to ensure your data and network remain in your control.NET Files  n C:\Windows\Microsoft. including administrator level for access to all key features and configurations.NET\Framework\v2. accessed through a web browser.NET Files If you are using NetFlow Traffic Analyzer. bookmark the page for ease of returning.0.IIS web  n 161/UDP . You can log in by default by entering the name Admin and no password.SolarWinds Information Service Service Accounts The following are LOCAL accounts and not domain.NET Files  n C:\Windows\Microsoft. When opened.0. The SolarWinds Web Console is displayed. You can access the page through a shortcut added to your programs.30319\Temporary ASP.

0. and general account management. Additional Polling Engines (APE). The web-based License Manager requires the main Orion server to be up. The SAM Getting Started guide is hosted in our Success Center to browse. Week 2: Customize SAM. Week 1: Get Started! Learn about SAM requirements. and click License Manager in the Details grouping. you can manage licenses for Orion Platform products. Additional Web Servers (AWS).1 or SAM 6. and discovering your network. scroll down. create custom properties and groups.2. configurations. You will learn about monitoring servers and applications. deploy Agents for polling. your licenses may be invalidated. search. exploring the environment. and refine your alerts. the web-based License Manager replaces the previous stand-alone Windows License Manager. maintain your environment. With SAM prepped. License Orion Platform products Beginning with SolarWinds Orion Platform products version 2016. how to use AppStack. We also provide downloadable PDFs per week. tweak thresholds based on incoming data and monitoring. engage the Quality of Experience. Get Started with SAM We include a series of guides set with common tasks from day 1 through week 4 of your journey learning SAM. such as NPM 12. Create custom views for your staff.  n Click Settings > All Settings. you can plan and scale your monitoring. and learn. and High Availability pools on a single Orion Web Console.3. and customize alerting for pinpointed monitoring results. Weeks 3 & 4: Scale and Manage. alerts and reporting. With the web-based License Manager. 65 . If the Orion server is down for more than 14 days. Some features available in SAM and multi-module Orion products will require administrator access.

license type and status. or Expiration Date. Product Version. and server that is using the license.  n Sort licenses by Product Name.  n Assign licenses to a server.  n Add or upgrade licenses. License Type. What can I do in the web-based License Manger?  n Activate or deactivate licenses. If you have upgraded from a previous version of your Orion Platform product. New installs use the web-based License Manager only. you can still use the stand-alone Windows version. Activated licenses display the activation key. The web-based License Manager replaces the stand-alone Windows License Manager in Orion Platform products. Orion Platform product version installed. What does the web-based License Manager show? The License Manager reviews and displays any of the following licenses it finds:  n Full and evaluation licenses for installed Orion Platform products  n Licenses for Additional Polling Engines and Additional Web Servers  n Added licenses that have not been assigned yet  n Orion Scalability Engine Evaluation license for evaluating APE and AWS  n Orion High Availability licenses All licenses include information about their duration and expiration dates. 66 .

 5. Click License Manager in the Details section. the expiration date. or your individual user account information.  a.  3. the assigned server. and complete the activation to see the license in the License Manager. Enter registration details. enter the details. license type.  1. On the top menu bar. Click Customer Portal. click Add/Upgrade License.Activate licenses with Internet access The License Manager automatically detects whether your Orion server has access to the Internet. contact Customer Support and submit a ticket. and log in using your Customer ID and password. 67 .  4. Sort the licenses by product name. The license type. product version. Click Settings > All Settings. or whether it is offline. If you license your product before you install it. and the license key are displayed in the License Manager. If you do not know your SolarWinds Customer ID and password or individual profile details.  2.  b.  d. and paste it into the Activation Key field in the License Manager Activate window. or expiration date to quickly find a license. and click Activate.  c. Enter the activation key. Click Activate. Copy the unregistered activation key. click License Management > License Management. Click the plus sign next to the SolarWinds product to display your activation key.

and the license details are displayed in the License Manager. choose the . Click Settings > All Settings. Click Copy to Clipboard to copy the unique machine key. and click Assign.  4.  1. When do I need to assign a license?  n To use the license by a different polling engine  n To improve polling capacity (stacking licenses)  n To change the default polling engine or web server assignment Stack licenses Stacking licenses can improve the polling capacity of your polling engines. After reaching the maximum number. and click License Management > License Management.  5. Click License Manager in the Details section.  4.  6. The polling engine is now using the license. In the offline activation mode. and click Activate. and click Activate. Assign licenses to a polling engine  1. assign an additional license to the same polling engine. Each polling engine can poll a specified number of elements at the default polling interval. Save the .  2. Select a product.lic file locally and transfer it to the offline computer. the polling interval is prolonged.Activate licenses offline If you have installed an Orion Platform product on a computer without Internet access.lic file.  7. Paste the unique machine id from clipboard. Assign licenses The License Manager automatically assigns an activated license to a server that needs a license.  2. Your license is now activated. you cannot activate a license for a product that is not installed. and click Activate License Manually. Select a polling engine and click Assign.  3. and click Generate License File. Select the license to reassign.  3. You can assign up to four polling engine licenses to one server. In the License Manager on the offline computer. Log in to the Customer Portal. the web-based License Manager guides you through offline activation. In the Customer Portal License Management. 68 . To maintain the default polling interval. Click Settings > All Settings > License Manager to open the web-based License Manager. See Scalability Engine Guidelines for your product in the SolarWinds Success Center for more information about extending the monitoring capacity. expand the product license to activate.

Activate the key to upgrade your license. install the polling engine or web server. you need to transfer the licenses to the new server. Uninstall the old main polling engine.  1.  2. open the Orion Web Console. and click Settings > All Settings > License Manager. To move an Additional Polling Engine. When the license is synchronized. You can only move licenses for product versions that were released during your maintenance period.  3.Move licenses: deactivate and re-activate To move your main polling engine for an Orion Platform product to another server. you can also add and activate a license for an Orion Platform product before installing it. Additional Web Server. you can upgrade immediately. See the SolarWinds Migration Guide for more information about moving Orion Platform products. Select the licenses.  a. and then synchronize your license with the Customer Portal. When you want to upgrade your Orion Platform product and your maintenance is expired. for example when you increase the number of licensed objects. See Uninstall NPM for more information. renew your maintenance or re-license your product. Click Synchronize. Prepare licenses to be moved. extend the maintenance. If your Orion Web Console is connected to the Internet.  2.  c. and click Deactivate. or stackable polling engine license. Synchronize licenses When your Orion server has access to the Internet. Copy and paste your activation keys to a text file. you receive a new activation key. 69 . Install the new main polling engine on the new server.  1.  b. To get a newer product version. Add and activate the license keys. Click Settings > All Settings > License Manager to start the License Manager. and then assign the license to it. without having to wait for the next daily synchronization or without having to update the license key manually. the maintenance status of your licenses is synchronized with the Customer portal daily. On the Orion server.  b. Add or upgrade licenses When you change how your product is licensed. The License Manager synchronizes with the Customer Portal and any updates in the Customer Portal are reflected in the web-based License Manager. Prepare the new main polling engine.  a.

If no server needs the license. select the license. Enter the Activation Key and registration details.  1. Go to the web-based License Manager. and click Update. 70 .  1. Update a license When you receive a new activation key for a license. Not sure how to get your Activation key? See Activate licenses for more details.  2.  3. and you can monitor the number of elements covered by the license. Enter the Activation Key and Registration Information. The license is now added to the License Manager and assigned to a server that needs it. and click Activate. the license remains unassigned.  2. and then click License Manager. The license key will be used for the license. and click Activate. click Add/Upgrade License. Click Settings > All Settings. In the License Manager. activate it.

and troubleshooting. Click Start > Control Panel > Add or Remove Programs. We recommend gathering diagnostics. Click Remove. If an issue occurs you need additional help with. checklists. and the general issue you found. Complete the SAM uninstall wizard. and any error codes you receive. use the SAM upgrade guide. and click SolarWinds Orion Server and Application Monitor.  n Check our Success Center for troubleshooting. and troubleshooting for migrations. a screenshot of the issue. You may also want to gather additional diagnostics on your additional pollers and web servers. Remove your SAM installation You may need to uninstall SAM to reinstall fully or when moving to another server. If you need to reinstall to a new server during a migration to new hardware. Learn how to upgrade like the geeks with preparation lists.  1. Attach and add this information to your ticket. Use the Product Upgrade Advisor to create the upgrade path. contact Support. use the Multiple Product Upgrade Guide.  2. Many of these updates solve issues you may experience part way through your upgrade. trying the following:  n If you experience issues and are not on the latest product versions. These instructions walk through the uninstall process. any error codes or messages displayed. we recommend completing a full upgrade. For environments with multiple SolarWinds modules. instructions. make sure to review the release notes for your SAM install version.Upgrade and migrate SAM Upgrading SAM For upgrade information. the version number. Migrating SAM and the SQL Database The SolarWinds Migration Guide includes preparation. and download a clean version from your Customer Portal.  n Migrating products to a new server with the same IP and hostname  n Migrating products to a new server with a new IP and hostname  n Migrating the Orion SQL database Troubleshooting If you encounter errors. instruction checklists. changed requirements. We recommend searching the name of the product. 71 . gotchas and need to know information.

and any error codes you receive. Many of these updates solve issues you may experience part way through your upgrade. and then click OK. We recommend gathering diagnostics. Expand HKEY_LOCAL_MACHINE > Software then delete both the SolarWinds and the SolarWinds.. We recommend searching the name of the product. Typically.. Typically. the version number.  4. and then delete both the SolarWinds and the SolarWinds. Attach and add this information to your ticket.  5.  7.. Click Start > Run and then enter regedit. and it can be found in the Databases folder of your SQL Server management application. Note: If you are uninstalling Orion SAM from a 64-bit computer. You may also want to gather additional diagnostics on your additional pollers and web servers. we recommend completing a full upgrade. trying the following:  n If you experience issues and are not on the latest product versions. Delete the following:  n The SolarWinds folder from the Program Files folder on your main volume. The Orion database is typically named NetPerfMon. contact Support.  n Check our Success Center for troubleshooting.net folders.  3. click SolarWinds Job Engine. Typically. any error codes or messages displayed. the SolarWinds website directory is located in C:\Inetpub\.  n Using your SQL Server tools.  n The SolarWinds website directory. The Orion database user can be found by expanding Security > Logins in your SQL Server management application.  n Using your SQL Server tools. and the general issue you found.  n The SolarWinds folder from the Program Files\Common Files folder on your main volume. a screenshot of the issue. Use the Product Upgrade Advisor to create the upgrade path. the Common Files folder is located at C:\Program Files\Common Files\. this SolarWinds folder is located in C:\Documents and Settings\All Users\Application Data\. delete your Orion database user.  6. If an issue occurs you need additional help with. delete your Orion database.net folders. the Program Files folder is located at C:\Program Files\. In the Add or Remove Programs window. expand HKEY_LOCAL_MACHINE > Software > Wow6432Node. then complete the uninstallation of the SolarWinds Job Engine. click Remove. Typically. 72 . If you encounter errors. Complete the uninstallation of the SolarWinds Orion Information Service.  n The SolarWinds folder from the All Users\Application Data\ directory.

and then click Start.Discover and manage devices Discover and add network devices When you install your Orion Platform product. click Settings > Network Discovery. firewalls and load balancers (if you have them).  l To automatically discover and add a larger number of devices across your enterprise. you must identify the devices you want to monitor. If the Discovery Wizard does not start automatically after configuration. 73 . The first time you discover your network.  l To add individual objects for monitoring. use the Network Sonar Discovery and Network Sonar Results Wizards. SolarWinds recommends adding a limited number of edge routers or switches. Discover your network with the Discovery Wizard Before you begin:  n Enable the networking devices you want to monitor for SNMP.  n Enable Windows devices for WMI. and add them to the SolarWinds Orion database. Add nodes with high latency one at a time.  2. and critical physical or virtual servers and hosts. Click Add New Discovery. add single nodes using Node Management in the Orion Web Console.  1.

This setting ensures that any agents you deploy. If there are no nodes using agents. including the one on your Orion server. SolarWinds recommends using this option when you are first starting out. you can use the following scanning options. As you scale your implementation. you enabled the Quality of Experience (QoE) agent during installation. The QoE agent monitors packet-level traffic. add a limited number of IP addresses. SolarWinds recommends scanning at most a /23 subnet (512 addresses max). If the Agents panel appears. If you have many IP ranges to scan. Directory Using Active Directory for discovery is particularly useful for adding large subnets because Orion can use the devices specified in Active Directory instead of scanning every IP address. so we recommend only scanning subnets where the majority of devices are objects you want to monitor. 74 . IP Use this option for a limited number of IP addresses that do not fall in a range. Option Description IP Ranges Use this option when you want Orion to scan one or more IP ranges. On the Network panel. consider adding multiple discovery jobs rather than including all ranges in a single job. Addresses Since a network discovery job can take a long time to complete. are up-to- date. Scanning a subnet returns everything that responds to ping. Subnets Use this option to scan every IP address in a subnet. Active Use this option to scan an Active Directory Domain Controller. you can leave this option unchecked. if this is your first discovery. select the Check all existing nodes check box. If there are any nodes using agents. 3.  4.

75 . and click Add vCenter or ESX Credential. On the Virtualization panel.  b. to discover VMware vCenter or ESX hosts on your network:  a. If all devices on your network require only the default SNMPv1 and SNMPv2 public and private community stings.  6. click Next. Check Poll for VMware.  b. or if you want to use an SNMPv3 credential. If any device on your network uses a community string other than public or private. If you do not add the host credentials. Orion still discovers the virtual machines (VMs) on the host. 5. Select <New credential> and provide required information. click Add Credential and provide the required information. However. On the SNMP panel:  a. you will not be able to see the relationships mapped between the VMs and hosts.

On the Windows panel. 7. 76 . SolarWinds recommends that you monitor Windows devices with WMI instead of SNMP. click Add New Credential and provide the required information. When you scale monitoring. to discover WMI or RPC-enabled Windows devices. This allows you to review the list of discovered objects and select the ones you want to monitor. SolarWinds recommends manually setting up monitoring the first time you run discovery. you can configure discovery to automatically start monitoring objects it finds. On the Monitoring Settings panel.  8.

and click Add New Discovery. Your Orion server can use the devices specified in AD instead of scanning every IP address in the subnet. On the Add Active Directory DC pop-up. enter your domain controller’s IP address/hostname and credentials. Click Settings > Network Discovery. and click Next. depending on the number of network elements the system discovers. click Add Active Directory Controller to query. On the Discovery Settings panel.  9.  3. Discovery can take anywhere from a few minutes to a few hours.  10. Add nodes using Active Directory Query your Active Directory Domain Controller to add nodes quickly and efficiently. click Next.  1. Create scheduled discoveries to discover and import any new servers and workstations that have been added to AD automatically. 77 . On Network Selection. Accept the default frequency and run the discovery immediately.  2.

 1. Choose to include devices that only respond to ICMP (ping). Complete the Network Discovery. On the Network Selection page. You can add additional AD controllers. you must provide the credentials of a Domain Administrator user. The credentials you provide are added to the discovery wizard as Windows credentials automatically. your discovery list may be smaller than you expect and you must add those devices manually. you will see the OUs you have added. or any other IP addresses that you need before continuing with discovery. all OUs are selected.  4. Select the organizational units (OUs) you want to scan for nodes. and add a discovery.  5. Click Settings > Network Discovery. Add workstations by clearing the Import servers only check box below the OUs.  2. but only servers will be added. It is useful when you have configured your discovery to find similar nodes or network devices. If the Active Directory credentials are not same as the Windows credentials for monitoring the node. By default. and click Finish. or select an existing one and click Edit. Click through the Discovery Wizard to the Monitoring Settings page. Credentials for Active Directory discovery When you use Active Directory discovery to add nodes. If you decide to exclude devices that only respond to ICMP. Automatically add discovered nodes Automatic monitoring means you do not have to go through the Discovery Import wizard every time you run a discovery. add credentials for WMI monitoring in the Windows Credentials step.  3. 78 .

 n Use Advanced Filtering Options for existing interface descriptions to choose your most interesting ports. Do NOT monitor desktop access ports because these ports will show an error state when everyone goes home for the day (for example). On Monitor Settings. select Up interfaces. You can also create advanced filters for interfaces under Advanced selection options. 79 . and click Define Monitoring Settings. etc. select Automatically monitor based on my. 4. 'WAN'.  5. This option is available for NPM.  n For switches. such as 'uplink'. select Up trunk ports and wireless access ports. Select the interfaces properties you want to apply to any discovered nodes and click Next.  n For servers. routers & firewalls. Tips for choosing interfaces  n Only monitor access ports that should always be up.

 8.  7.  n For servers. so you may need to take additional actions to identify them. When the discovery is run. the system automatically selects all network elements to be monitored. Fixed Disk. and anything that matches will be imported and monitored automatically.  6. Nodes that are discovered do not count against your license count. select Flash memory. select RAM. Continue configuring your discovery.  9. removable disks. Virtual Memory. You must clear the check boxes for elements you do not want monitored.' and removable disks disappear and display as unknown). This option is available for SAM. You can monitor other applications by using applications templates. Click Finish. or floppy disks (CDs always show '100% full.  n Other and Unknown volumes cannot be identified on import. Add discovered devices to SolarWinds After the Network Sonar Wizard discovers your network. your monitoring settings will be applied to any discovered devices. 80 . or Network Disk (Windows).  n We do not recommend monitoring CDs. Only nodes that you have added to the SolarWinds Orion database count against your license. Choose the applications you want to monitor. Only the most commonly monitored applications are available in this screen. routers. allowing you to import network elements into. and RAM. When you manually run discovery. Mount Points (*nix systems). Tips for choosing volumes  n For switches. by default. Choose the types of volumes you want to monitor. the Network Sonar Results Wizard opens. and firewalls.

you can also select Operationally Down or Administratively Shutdown states for import. select nodes you want to monitor. 81 . the product can only detect if the device is up or down.  2. contact technical support. it means that the credentials could not be validated. By default. and click Next. Ensure the interfaces you want monitor are selected. SolarWinds NPM imports interfaces that are discovered in an Operationally Up state. If the credentials still cannot be validated. and then click Import Nodes. To resolve this issue. If the Network Sonar Results Wizard does not open automatically. and cannot collect any other data.  1. and you have an active SolarWinds contract. As a result. click the Scheduled Discovery Results tab. verify the SNMP configuration on the device. Ensure the device types you want to monitor are selected. If you are discovering your network for the first time. because interfaces may cycle off and on. If a device appears as unknown vendor.  3. SolarWinds recommends that you monitor a small number of devices. and click Next. SolarWinds recommends that you do not monitor VoIP interfaces or NULL interfaces. However.

82 . Click the My Dashboards > Summary to begin exploring your network.  7. and click Import. When the import completes. and click Next. click Finish. Ensure the volume types you want to monitor are selected. 4.  5.  6. Review the list of elements to be imported. SolarWinds recommends that you do not monitor compact disks or removable disks.

Specify the node.  n Identify how often the node status. Log in to the Orion Web Console as an administrator. or topology details are updated. Adding a single node offers more detail in monitoring and is the recommended approach when you have a node with high latency. and then click Add a Node. and click Next. As you add a single node for monitoring. you can add individual nodes for monitoring.  b. Select the polling method. Click Settings > Manage Nodes.  n Add custom properties. Do not include nodes with high latency in a discovery job.  n Edit alert thresholds. Provide the host name or IP address.  a.  3.  2. monitored statistics. and provide credentials. To add a single node for monitoring:  1. 83 . you can:  n Select the statistics and resources to monitor.Add a single node for monitoring As an alternative to using the Network Sonar Discovery wizard.

Customize. Select the Override box and set thresholds specific for the node. and click Next.  6. Add Node.  d. To edit how often the node status.  a. Select the statistics and resources to monitor on the node. you may need to poll status information or collect statistics more frequently than the default polling intervals. The node will be monitored according to the options you set. edit alerting thresholds for the metric. 84 . monitored statistics. Click OK.  5. change the values in the Polling area. Review and adjust the device properties. Change the polling intervals if polling the nodes takes too long. To edit the SNMP settings. or topology details are updated. Import nodes from a list of IP addresses Import devices from a seed file in the Network Sonar Discovery wizard.  c. For critical nodes.  b. The Custom Properties area will be empty if you have not defined any custom properties for the monitored nodes.  4. Enter values for custom properties for the node. change the values. To adjust when the status of the node changes to Warning or Critical. and click Test. See "Add custom properties to nodes" in the SolarWinds Getting Started Guide .

Click Validate to confirm that the provided IP addresses and host names are assigned to SNMP- enabled devices. Click Add New Discovery to create a new discovery.  6. and clicking Add to Ignore List.  2. and click Settings > Network Discovery. and click Add to Ignore List. Click Scheduled Discovery Results.  5. Manage scheduled discovery results The Scheduled Discovery Results tab of Network Discovery provides a list of all recently discovered. Enter one IP address or host name per line. Click Scheduled Discovery Results. Ignore devices in future discoveries by selecting the nodes to ignore. Filter the results the left pane. The selected devices will not be discovered by the discovery. Update your SolarWinds Orion database to include changed or discovered nodes by selecting all nodes to update or to add. The Network Sonar Results Wizard opens with the results of your discovery.  2.  1. Use items in the Status and Group by lists to help you find devices. and navigate to Settings > Network Discovery. and click Edit. and navigate to Settings > Network Discovery.  5.  4.  3. and listed on this tab.  3. Click the Discovery Ignore List.  4. changed. Log in to the Orion Web Console. Minimize SNMP processing load during discoveries using the Discovery Ignore List Network discoveries often find devices you do not intend to monitor. Log in to the Orion Web Console. 85 . Open the seed file. and select the objects you want to monitor.  2. Click IP Addresses. or select a discovery. Results are compared between discoveries.  1. Add the devices you do not want to monitor to the Discovery Ignore List to minimize the SNMP load associated with discovering devices not meant for monitoring. and copy and paste the IP addresses or host names of the devices from your seed file into the field.  2. Log in to the Orion Web Console. or imported devices on your monitored network. Add ignored devices back to discovery  1. Complete the discovery and import the devices. and clicking Import Nodes.  1. Log in to the Orion Web Console and navigate to Settings > Network Discovery.  3. Select devices you want to ignore.

average response time. This polling method is used to monitor status and measure the average response time and packet loss percentage for managed devices. Windows Management Instrumentation (WMI) is a proprietary technology used to poll performance and management information from Windows- based network devices. Consider adjusting any network intrusion detection systems or your firewalls to allow for the ICMP traffic. or SNMP v3 credentials. Consider adjusting any network intrusion detection systems or your firewalls to allow for the ICMP traffic. Your devices must have ICMP and SNMP enabled to use this polling method. and components. 86 . WMI can provide much of the same monitoring and management data currently available with SNMP-based polling with the addition of Windows specific communications and security features. switches. If you want to poll with a specific version of SNMP. and computers. When used as an alternative to SNMP. Use this method when you need limited information or to monitor devices that do not support SNMP or WMI. Click Remove from Ignore List. This polling method requires that you enable ICMP on your nodes. Most Devices: SNMP & ICMP This method allows you to query the Management Information Base (MIB) and performance indicators that are tied to specific Object Identifiers (OIDs) in addition to polling the device status. This method is suitable for SNMP-enabled devices such as routers. External Node (No Status) The node is not polled. The node is included in your environment and used to monitor an application or another element on the node. This method allows you to build a more complete map of your network environment within your SolarWinds Orion Platform product. Status Only: ICMP Limited information is gathered using Internet Control Message Protocol (ICMP) or ping. Windows Servers: WMI and ICMP This polling method can only be used for Windows computers. The devices removed from the list will be included in the discovery again. Choose the polling method to use Select a polling method to monitor nodes in the way that best suits your environment. and no data is collected from the node. and packet loss percentage.  3. you must disable all other versions on the device. Confirm that you want to stop ignoring selected items by clicking OK.  4. applications. You must provide the appropriate SNMP community strings for SNMP v1 or v2c.

87 . Due to specific characteristics of WMI polling requests.Your devices must have WMI and ICMP enabled to use this polling method. For example. and network links. to test the connectivity between your Orion server and your Windows computer. high latency connections  n Polling nodes across domains where no domain trusts have been established  n Full end-to-end encryption between the monitored host and the poller View monitored objects on maps Maps in the Orion Web Console can show monitored nodes. polling a single WMI enabled object uses approximately five times the resources required to poll the same or similar object with SNMP on the same polling frequency. Display nodes in the Worldwide Map of Orion nodes resource Nodes and groups that contain information about their location in the OpenStreet format are displayed automatically. the Quality of Experience plug-in collects packet traffic. Information collected by plug-ins depend on the type of plug-in installed on the agent. and display them in the Orion Web Console. You can use WBEMTest. Agents automatically download the plug-ins for all installed products. This polling method is most useful in the following situations:  n When host and applications are behind firewall NAT or proxies  n Polling node and applications across multiple discrete networks that have overlapping IP address space  n Secure encrypted polling over a single port is required  n Support for low bandwidth. which is included on every computer that has WMI installed. while a SAM plug-in collects application data used to monitor the applications.exe. Open Street Map Display nodes on maps powered by Open Street Map. interfaces and volumes. Network Maps Create customized maps in Network Atlas. Windows and Linux Servers: Agent An agent is software that provides a communication channel between the Orion server and a Windows or Linux-based computer. SAM applications and components. Consider adjusting any network intrusion detection systems or your firewalls to allow for the ICMP traffic. See Place nodes automatically on the Worldwide Map Objects with the same position are displayed as one location. Agents are used to communicate the information that SolarWinds plug-ins collect to the Orion server.

click x next to the node in the Selected Objects section. If you want to further edit the map. Click > next to a node group to expand a list of all nodes in the group. Click Place on Map. If you cannot see the Worldwide Map resource on a view. Add or remove nodes in locations. or center the map on different coordinates. click Submit or Save and Continue if you want to further edit your worldwide map. or rename locations  1. 88 . Click Manage Map in the Worldwide Map resource. and click Edit Location. Click Submit. use different titles and subtitles.  3. Edit the position of locations If the exact position is not known or important.  2. Click Save Changes.  3. click Save and Continue.  1.  2.  1. Click Place Nodes on the Map Manually. you can add the Worldwide Map resource to multiple views.  4.  3.  5. add the resource. If you want to further edit the map. and click Edit at the top right of the list of nodes at the selected map location. Use the Grouping and Search tools to select nodes which you want to place on the map.  4.  n Select nodes to be added in the Available Objects section. Click the map location you want to edit. Click Submit.  n To remove nodes.  5.  6. and click into the map where you want to place the nodes. Add nodes manually Add a new location into the map. click Save and Continue. you can apply different zoom levels.  2. and define the nodes positioned in the location. and display different objects and information on each view. If you want to rename the location. Provide the Latitude and Longitude of the new location. Click Manage Map in the Worldwide Map resource. and click Save. you can drag locations to their positions. type the new name in the Name of Location field at the bottom of the Available Objects section. For example. See Add resources and columns to views. Click a map location. Provide a name for the location.Although there is one Worldwide map. Add or remove nodes in the location.  4. and define subviews. To apply your changes in the resource. Click Manage Map in the Worldwide Map resource.

they can be added into the Worldwide Map resource automatically. If you want to further edit the map. To verify whether the automatic placement of objects is enabled:  1. In the Product Specific Settings. click Web Console Settings. state. Place nodes automatically on the Worldwide Map If your devices contain information about their location in the OpenStreetMap format.  3. Log in to the Orion Web Console as an administrator. city.  2. Select the map location. PA. Click Settings > All Settings in the menu bar.  5.Delete locations  1. click Save and Continue. state 300 Granite Run Dr. Click Remove from Map. 17601 89 . postalCode Lancaster. Scroll down to Worldwide Map Settings and make sure Automatic Geolocation is selected. PA.  3. and then confirm the map location removal. its position will not be updated if you change the values for longitude and latitude. If you move an automatically placed location. Lancaster. 17601 postalCode 17601 street. Click Submit. Locations will display in the Worldwide Map resource within an hour after you select this option. In what format should the location on a Cisco device be configured? You can use any format the mapquest API is able to parse. See Place objects into the map using custom properties. state (AA3) city. state (AA3) city (AA5). Lancaster. Click Manage Map in the Worldwide Map resource.  4. postalCode 300 Granite Run Dr. FORMAT EXAMPLE city (AA5). You can specify the position for automatic geolocation with custom properties. Click Submit to apply the current settings. state. Automatic geolocation does not change locations for manually placed objects. PA street. Objects with the same position appear as one location in the map.  2.  4. city.

FORMAT EXAMPLE street.csv file with longitude and latitude custom properties. and match these to Latitude and Longitude (World Map) column. click Export Values. 90 . and then click Manage Custom Properties. Clear the Remove unchanged rows box.  b.329999 Place objects into the map using custom properties If you have longitude and latitude for your nodes or groups defined as custom properties. Select Longitude and Latitude. and click Next.  a. Import the . Click Import.  2. select the export file with Longitude and Latitude.07546.  1.  b. 17601 latLng 40. Click Settings > All Settings.-76.  c. click Import Values. you can use the coordinates to automatically place the nodes on the WorldWide Map. In the Custom Property Editor. there are no changes. If the box is selected. After an automatic export. only the data you changed manually in the exported file will be imported.  d. postalCode 300 Granite Run Dr. and click Export.  a. and thus no data will be imported. You can create the custom properties using the Longitude and Latitude property templates. Match Longitude and Latitude to the World Map columns. Export the values for the custom properties Longitude and Latitude.

such as floor plans.  n Nest maps. Add custom background graphics. as specified by the Longitude and Latitude (World Map) properties. Maps provide a graphical depiction of the network. You can now see the nodes in the Worldwide Map. It is preinstalled with your Orion Platform product. and volumes. or images. What can you see on maps?  n Monitored SolarWinds NPM nodes. SAM applications and components. The values for Longitude (World Map) should match the Longitude values. Optional: Verify that the values were imported successfully. and use them to document your network. Network Atlas Network Atlas is an application for creating custom maps and network diagrams. Click Settings > All Settings. and values for Latitude (World Map) should match the Latitude values. and style of map links to illustrate the status of the relative bandwidth of associated objects. interfaces. Select Longitude and Latitude and click View / Edit Values.  n Customize the shape. You can export or print maps. Add the Longitude (World Map) and Latitude (World Map) columns. and click Manage Custom Properties. and network links What customization options are there?  n Customize the map background with default colors. and the status of nested map child objects may be bubbled up to the parent map. size.  a. nested maps. color. You can also view Network Atlas maps in the Orion Web Console.  c.  n Select a graphical style for objects to reflect the network status on maps. and be notified if devices on the floor map are down. You can for example nest floor maps into a map of a building. textures. so that you can drill down to reveal increasing levels of detail.  b.  3. 91 .  n Link dynamic real-time weather or natural disaster maps to your network maps as the background.

Memory 1 GB Hard Drive 150 MB Space Ports Remote instances of Network Atlas require TCP on port 17777 to either the SolarWinds NPM or the Orion EOC server. Users can also run Network Atlas as a standalone application on a remote computer. 92 .NET 4.Installing and using Network Atlas See Install Network Atlas to install and use the application. Start the Orion Web Console in the SolarWinds Orion program folder.5 Framework Install Network Atlas on a remote computer  1. In the Map resource. click Download Network Atlas.NET . and it can be run as a local application on those Orion servers. HARDWARE/ REQUIREMENTS SOFTWARE Operating   Windows Server 2008 R2 SP1 System   Windows Server 2012 and 2012 R2 Windows Server 2012 R2 Essentials is not supported. When installed you can open the application to create these maps:  n Create network maps  n Create wireless heat maps  n Advanced mapping techniques  n  Advanced map layouts Install Network Atlas Network Atlas is pre-installed on Orion EOC and SolarWinds NPM.  3.  2. Network Atlas Requirements Network Atlas users must have the Map Management rights in SolarWinds NPM or in Orion EOC. . The user logged in to Network Atlas must be able to access the Network Atlas synchronization folder to ensure synchronization with the SolarWinds Orion database. Log in to your SolarWinds NPM or Orion EOC server.

Now on the Network Atlas Welcome screen. Rescaling maps in views results in distorting of icons and texts.exe) on the remote computer. Create network maps Before you start creating maps. Start Network Atlas in the SolarWinds program folder. If you have previously installed Network Atlas.  d. click Edit.  n To create a new network map. See Create network maps. Provide an appropriate installation destination folder. select EOC as the Connect To target. select what map you want to open:  n To open a recent map. and click Submit.  3. Log in to the computer hosting your Network Atlas installation. Accept the terms in the license agreement. click Browse and navigate to the map. Provide your Orion Web Console user name and password. Click Connect.  1.  4.  b.  2. Consider the following recommendations:  n Map only static objects. select Orion as the Connect To target. you need to adjust their location on maps. you may be prompted to change. Run the installer on the remote computer.  5. Save the installer (NetworkAtlas. prepare a map management strategy. and click Next.  e. Click Finish when the Setup Wizard completes. and click Next on the Welcome window. Click Repair. Connect to your primary Orion server:  a. If you do not see the download link in the Map resource.  6. click Network Map in the Create New section. If you are connecting to an SolarWinds NPM server. If objects move.  n Build maps to match the column width of your Orion Web Console views. To create a network map: 93 . click Repair again on the Ready to repair window. and it is difficult to keep maps up-to-date. select Show Network Atlas Download Link. repair or remove your installation.  4. select it in the Open Recent section. and complete the Setup Wizard.  n To open a map available in a certain location. See Create network maps. and click Next.  c. If you are connecting to an Orion EOC server.  8. Provide the IP address or hostname of your primary Orion server in the Address field. Start Network Atlas Users must have the Map Management right in SolarWinds NPM or in Orion EOC.  7. Click Install on the Ready to Install window.  9.

 3. Click Connect. Navigate to your existing map. Start the Network Atlas in the SolarWinds program folder. volumes. interfaces.  5.  2. hover over it with the mouse pointer. click its network resource in the left pane. Provide your Orion Web Console credentials.  n To locate a specific map object in your map. 94 . Click Network Map in the Create New section. If you are creating a new map. such as:  n SolarWinds NPM nodes. Click Open Map.  4. Connect objects on maps automatically with ConnectNow Using the ConnectNow tool.  c.  1. This selects the map object. and click Open. If you are starting Network Atlas on a remote computer.  n To add all the objects of a type on a node to your map. and Universal Device Pollers (UnDPs)  n SAM applications and components  n VoIP & Network Quality Manager operations  n Network Atlas maps  n Network links To add objects on a map:  1. Network Atlas can automatically draw lines between directly connected nodes on your network. click + next to the node name to reveal all its associated monitored network objects. If you are adding objects to an existing map:  a.  b. and click New Map. Expand and navigate the node tree in the left pane to locate the network nodes and monitored objects you want to add to your map. If you are launching Network Atlas on the local computer. Drag selected objects onto the drawing area.  3. Click the Network Atlas button ( ).  4. Add objects on a map Any objects monitored by SolarWinds NPM or SAM may be added to a Network Atlas map.  n A check mark ( ) next to a node or network resource indicates you have already added it to your map.  n To view details about a map object. provide the IP address of the main polling engine. A new empty network map will open in the Network Atlas. type localhost into Address.  2. and drag all objects in the object group onto the drawing area. click the Network Atlas button ( ).

In the Node & Group Management grouping. These devices might be switches. if nodes A and C are connected indirectly through node B. Click Settings > All Settings in the menu bar. An unidentified node is a node that was found on the network but which is not managed by Orion. Click an object with the line drawing tool to begin drawing the link  4.  2.  1. Click ConnectNow ( ) in the Home ribbon. The values in the TopologyConnections table will be re-calculated and your topologies will be updated. as appropriate.  1.  2.  l Orion Enterprise Operations Console (EOC) does not support ConnectNow. You can update the data manually. Log in to the Orion Web Console as an administrator. routers. when a topology calculation cannot find any direct connections between two nodes. Connect objects on maps automatically using ConnectNow  1.  l The ConnectNow tool cannot draw indirect connections between nodes. generated to signify an indirect connection in your map. hubs.  4. In the More Actions drop-down list. For example. For example.  3. Add the nodes to an open network map. click Manage Nodes. Click a second object to finish drawing the link.ConnectNow displays connections based on data polled for nodes with enabled L2 and L3 topology pollers. you must manually add node B to the map to create the connections. Click Straight ( ) or Curved Line ( ) in the Lines group. any connected links change color to red. 95 . Click and drag as needed to set optional anchor points along the link path. By default. Update the Topology ConnectNow displays data stored in the TopologyConnections database table. Unidentified nodes can be virtual. an unidentified node is generated between the two known nodes. Make sure the Home ribbon is selected. the data are re- calculated every 30 minutes.  3.  5. If a connected object is down. select Update Topology. See Add objects on a map.  2. or other devices without names or addresses. and for unidentified nodes. Connect objects on maps manually You can represent network links in your map by drawing lines between map objects.

Click Appearance and set the default width and style for the link. right-click a link. To show the link utilization in percent. Expand Connection Display Options. Right-click a link. and click Don't Show Additional Info. Reshape map links You can use anchor points to change the shape of object links on your map. Right-click a link. and select Add Label. select Link Utilization. clear the Include Link Labels. To change the objects. A default label appears. drag objects from the Network Atlas navigation tree to the appropriate endpoint box. and select Properties.  2. Click Status and review the objects from which the link gets its status. Click and drag the link you want to reshape.  c. and select Properties. To add a label.  1. the link speed. Links can then display the status. Drag the appropriate interface objects from the left pane of the Network Atlas window to the link status assignment areas.  5. Use multiple anchor points to create more complex shapes and curves. You can set interfaces through which linked objects are connected. They can display status of the connection. Interface states and performance data are determined from SolarWinds NPM polling data. or utilization.  2. To specify what should be displayed for connections:  a. Select Status in the left pane of the Link Properties page. Click Hyperlink to specify what should open when you click the link in the Orion Web Console. To display the link speed. Down links are always red.  4.  6. speed or link utilization of the connection. Configure display of connections on maps Links created on Network Atlas maps are not merely connectors between network objects.  3.  6. Select in the Tools group. Interface performance information in maps can be communicated using the interface status or performance:  n Determine interface status in connections  n Specify interfaces that determine the status of connections on maps  n Display interface performance in map links 96 .  c. To hide all labels for the connections. select Show Link Speed. Edit the label text or move the link label.  b. or click the middle mouse button. If you want the links connecting your mapped objects to communicate the status of connected interfaces:  a.  b. Select the color for links that are UP.  1.

This option is default on new maps. with InterfaceA. A solid line indicates that the connection is UP.  n Include Link Labels enables or disables displaying connection labels.  2.  1. A dotted line indicates that the connection is DOWN. and select Properties. Select Status in the left pane of the Link Properties page. Expand Connection Display Options in the bottom left pane. 97 . The connection status is only shown as either UP or DOWN. Right-click a link in a map. To emphasize potential problems. Select display options:  n Show Link Speed provides interface connection speed information in colored links.  2. with InterfaceB. Utilization data is not shown for manually created links. textures.Determine interface status in connections Connections are shown as either solid or dotted lines.  3. Display interface performance in map links Map links can show either interface utilization or interface connection speed.  n Don't Show Additional Info provides only interface UP/DOWN status information on device links. The following table shows how interface states are reflected in the status of a connection between NodeA.  n Show Link Utilization provides interface utilization information in colored links. The connection status depends on the status of interfaces at both ends of the connection. Drag the interface objects from the left pane of the Network Atlas window to the link status assignment areas. This is the default option for previously created maps. InterfaceB Status UP DOWN UNKNOWN InterfaceA Status UP UP DOWN UP DOWN DOWN DOWN DOWN UNKNOWN UP DOWN DOWN Specify interfaces that determine the status of connections on maps  1. Add a background You can select colors. A legend is available to interpret colors representing interface performance data. and NodeB. DOWN status is granted a higher priority. and locally-hosted or Internet-hosted images to serve as your map backgrounds.

Select a background texture  1. Requirements and recommendations  n Files used for linked backgrounds must be continuously accessible by URL reference. non-animated)  n Tagged Image File Format (.  4. Select a background image Add images accessible on the hard drive or on the Internet as the background for your maps.bmp)  n Portable Network Graphics (.  2. Click Background > Background Color ( ). consider web page layouts and display screen resolutions.  n When determining map size and resolution.  2. click Home.png) Linked backgrounds are updated when you access the map. plan graphics to display at full size in the Orion Web Console. or click More Colors to select a custom color. and click Background > Clear Background ( ).  1. The default values are the smallest area bounding the existing map objects and labels. Select a texture.gif. Supported formats  n Graphics Interchange Format (.tiff)  n Joint Photographic Experts Group (.jpg)  n Microsoft Windows Bitmap (. 98 .  n To ensure optimal quality of images. To clear the current map background.  3. and click OK. or refresh the browser page. Click Home.  3. Click Background > Background Texture ( ). Enter the Width and Height of your map in the Map Size in Pixels area. Select a background color Network Atlas supports 24-bit color backgrounds.  n Files used for static backgrounds must be available within the local file system. Select a color from the palette. Click Home. Example backgrounds are in the NetworkAtlas Backgrounds folder located in your default shared documents folder.

Type the URL of the image.  4.  2. and copy the static link.Add an image as the background  1. and click Save. map background images linked from the Internet are refreshed with the Orion Web Console refresh. name the map.  d.  b. 99 .  3. Add a dynamic background for a map Weather conditions can affect availability of a certain location. To use a background image the disk. Click Linked Background. the map will refresh every time the Orion Web Console refreshes.  b. click Background > Background Image.  1. Provide a File name.  1. Click Background > Linked Background.  3.  n If the Orion server is behind a web proxy which requires authentication. and navigate to the image. Save maps Network Atlas saves your maps directly to the server to which you are connected. Click OK. If you want to save your map to your hard drive:  a. If you are saving the map for the first time.  c. Navigate to the page which you want to link as the background. When you add the map to the Orion Web Console. You can specify the saved image as the linked background image. The dynamic map will now display as the map background. and click Home. Click the Network Atlas button ( ).  2. Open the map in the Network Atlas. Click Validate. A workaround is to write a script that periodically downloads the image and saves it to a folder on the web server. Open the map in the Network Atlas. Click  > Export > Export Map.  3. and paste the URL. and click OK. You can add weather maps displaying the current weather as a background for maps.  n In the web console.  2. and click OK.  c. you cannot link directly to the background image. and click Save. Validate the URL. Navigate to a location on your hard drive. To use a background image from the Internet:  a.

Open maps Maps are loaded from the Orion server to which you are connected. and it is not saved with the map. You can then click the Oklahoma object to open the child map. Click + to expand the Maps group in the left pane of the Network Atlas window. They appear in the left pane of the Network Atlas window. 100 .  1.  n Click the Zoom slider on the status bar.  n Click View. and change metric thresholds  n Add independent map objects and floating labels  n Change the appearance of map objects  n Customize the width. Zoom level is a visual aid. and then slide the zoom control to the zoom level you want. and line styles of network links in maps  n Customize labels  n Customize the page that opens when you click on a map object  n Link or embed maps in web pages using the map URL Zoom in and out of a map Zoom into a map to enlarge details or to zoom out to reduce its size.  2. Create nested maps Nested maps allow you to navigate through a map to see multiple levels of detail. Advanced mapping techniques  n Zoom in and out of a map  n Create nested maps  n Display the status of child objects on maps. color. a map of the United States can include an icon for a child map of Oklahoma. For example. Double-click the map you want to open. and select the type of zoom you want to use from the Zoom group. Use any of the following methods:  n Press and hold CTRL while rotating the mouse wheel button.

Right-click the map object. and click OK. This secondary status indicator appears at the bottom right corner of the status icon.  2. If you want the status of a child map to also indicate the status of its child objects. Click any nested object to view the next level of map detail. and select Properties.  2. click the threshold value. If your maps load slowly. Click OK. CPU load. To add the secondary status indicator:  1. such as up or down. Open the parent map.  3. deployed on it. Position the new map object on the parent map. and select Properties. and type a new value.  2.  3.  5.  1. and change metric thresholds The status of a map object icon reflects its current state. Right-click the child map icon on the map.  4. or the state of any child objects. Each child map can include a view of the objects. To change the thresholds of the metrics:  1. and save the map. The object status icon now includes the secondary status indicator. You can add a secondary status indicator to a map object to reflect metrics such as response time. and click OK. To change the warning or critical threshold for a metric. and drag a map from the Maps group onto the parent map. either devices or other maps. affects how fast the map loads in the Orion Web Console.  b. 101 . decrease the number of map objects.The map of Oklahoma can become a parent map to a network diagram. Right-click the map object. Click Metrics to view the Metrics properties page. Select Include Child Status on the Status properties page. including objects on child maps. The total number of objects on a map. clear the metric. To ignore a metric. and select Properties. complete the following steps:  a. Select Include Child Status on the Status properties page.  4. Create all maps to be nested in the Network Atlas. until you reach the final network device and see all available network information. Display the status of child objects on maps.

Click Home.  2. Drag a corner handle on the map object to resize the shape.  2. Click Add Label in the Labels group. you can set an object icon to visually designate the type of the monitored device. If you want the map object to appear as a fixed-size. Select a style from the Orion LED Status Icon Style list.  n All child objects and selected metric thresholds are taken into account to determine secondary status. Select an appropriate default style for each available map object. such as 3D Pad Underneath. Click Home. Set the default representations of map objects  1. to illustrate the object status.  4. complete these steps:  a. To add an independent object:  1. 102 . Change the representation of single map objects  1.  3. Click Graphic Styles in the left column. Click the Orion Network Atlas button .  b.  b. For example. Select a style from the Shape Style list. Select Orion LED Status Icon. If you want the map object to appear as a scalable shape. Add independent map objects and floating labels Independent objects and floating labels do not have associations to network nodes or resources. complete these steps:  a. LED-type graphic. Right-click a map object. Click Add Object in the Objects group to add a gray map object to the map. and click OK. and select Properties.  c.  n The secondary status indicator respects the Orion Web Console Status Rollup Mode setting for displaying status. A label is added to the map.  3. Change the appearance of map objects Changing the graphics that represent map objects allows you to increase the information density of your map without increasing the map complexity.  2. Select Shape. You can then select a status style. and click Network Atlas Settings. Click Appearance in the left column of the Properties page. and click OK. To add an independent label:  1.  2.

 1.  n Name the graphic files according to their roles. The added icons are also saved on the Orion server in the path %APPDATA%\SolarWinds\NetworkAtlas\Maps\Orion\<orion server address>\NetObjects\Imported.del to the file name (for example. Add custom icons from graphics files The custom graphic files must meet the following requirements:  n Supported image formats: Windows Media File (. mypicture.  2. Add . ROLE FILE NAME Critical status iconName-critical. Select Graphic.  4. Open the icon image in a graphics program.  2.  d. and click OK. Right-click on the map and then click Paste. select an appropriate graphic. Start Network Atlas on the Orion server to delete the icons from the database. Enter a name for the image. If you want the map object to appear as a scalable graphic. Select a status style from the Graphic Style list.  b. mypicture.  a. Click OK. Drag a corner handle on the map object to resize the graphic.  3.  n The file name must not contain any other dash (-) characters other than depicted in this table.  d. Determine which file on the Orion server contains the icon (for example. complete these steps. Paste custom icons from the Windows clipboard You can paste graphics from the Windows clipboard into Network Atlas maps. Paste the image as a new object following these steps:  a.wmf). and click OK.  c. Pasted icons saved to the SolarWinds Orion database can be used by remote instances of Network Atlas. Select Paste the Image From the Clipboard as a New Object.wmf. and display an overlay behind them to depict their status.wmf) or Graphics Interchange Format (. %APPDATA% is typically located in C:\Users\<logged on user>\AppData\Roaming Delete a custom icon  1. such as Visio or Photoshop.gif 103 .gif). Icons that you paste into Network Atlas are saved to the SolarWinds Orion database.  b.  c. Open the appropriate map in Network Atlas.  5. Copy the image to the Windows clipboard with the Copy command.  3. Click Select Graphic. and made available for reuse in other maps under the "Imported" icon grouping.del).

paste the icons into the following folder: %APPDATA%\SolarWinds\NetworkAtlas\Maps\Orion\<orion server address>\NetObjects\User Graphics. Select the graphic image. and then click Select Graphic. The custom icon will display on the map.gif Unknown status iconName-unknown.  6. 104 . color. %APPDATA% is typically located in C:\Users\<logged on user>\AppData\Roaming  3. Start Network Atlas on the SolarWinds NPM server.wmi files.  5. You can now assign the custom icons to objects on Network Atlas maps.gif Add custom icons from graphics files  1.gif Warning status iconName-warning. Assign a custom icon to an object  1.gif External status iconName-external. Select User Graphics in the left pane.  2. Click OK. Select a line width in pixels from the Width list. Right-click a link.  3. Customize the width. and click OK. On your SolarWinds NPM server.gif or .gif Unreachable status iconName-unreachable. Select Appearance in the left column of the Properties page. Select a line color from the Color list. ROLE FILE NAME Down status iconName-down.gif Unplugged status iconName-unplugged.gif Icon with no status iconName. The color setting only changes the color of links that have the Up status. and line styles of network links in maps  1. and select Properties.  2.  2. Right-click the object on the map. Select a line style from the Style> list.gif Up status iconName-up.  3.gif Unmanaged status iconName-unmanaged.  4. Prepare the icons and save them as .

and select a color. To add a label border. select 0 from the Border Width list.  4. Customize text attributes. and select a color.  10. Right-click the label. Select Appearance in the left column of the Properties page.  2.  2.  6. To change the text color. drag it to the new location.  11. Right-click the map object.Customize labels To move a label. Click OK. To change the label border color. map objects are linked to the most relevant details page for the object. and select a color. and type the URL. To change the text alignment.  3. 105 . Double-click the label. Customize the page that opens when you click on a map object By default. To link to the relevant Orion page for the map object.  9.  7.  12.  5. Click OK. To change the font attributes. select the border width in pixels from the Border Width list. click the Background Color box. To remove label borders. select the font attributes. To add a label background. and background colors  1.aspx?Map=mapName orionServer This is the IP address or host name of your SolarWinds NPM server.  8. To change the label background color. and click OK. select Logical Page in Orion. Link or embed maps in web pages using the map URL The map URL is in the form: http://orionServer/Orion/NetPerfMon/MapView. click the Text Color box.  2. borders.  1.  3. and select Edit Hyperlink. to remove a label background. select an alignment from the Text Alignment list. Customize the URL hyperlink to link to external web sites and pages. and select Properties. clear Transparent Background. Press <SHIFT>+<ENTER> to separate multiple lines within the same label. click the Border Color box. Edit a label text  1.  4. To link to a custom URL. click the … button. select Manually Set Address. select Transparent Background.

Click Submit.  n If Orion EOC is configured to use Active Directory accounts to access Orion servers. substitute %20 for the spaces when specifying the name. Locate the Map resource. and other text.  3.  n Orion EOC does not support custom web console tooltips. Import Network Atlas maps into Orion EOC Maps created for use in SolarWinds NPM must be converted before they may be used in Orion EOC. Click Customize Map Tooltips. a tooltip with the current identification and status of the object appears. and affect all maps.  4. Type the variables and any text in the text field for the map object type. Map import requirements and configuration The Orion to EOC Map Converter utility imports maps into Orion EOC v1. only AD accounts that were individually added to the Orion Server may be used to import a map.mapName This is the display name of the map. Environment requirements  n Orion EOC must currently be managing at least one SolarWinds Orion server.  5.  2. Additionally.  n To enter a carriage return. the user must also meet the following specifications: 106 . If the name contains space characters. Log in to the Orion Web Console as an administrator. Customize tooltips for all map object types in the Orion Web Console to display additional information using alert variables. custom properties. confirm that you have entered the password for the AD account in the Orion Logins section of EOC. and click Edit. Add additional information to map object tooltips  1. Active Directory group accounts are not compatible with Map Converter.  n Tooltip customizations are global. User requirements To run the Orion to EOC Map Converter utility. use ${CR}. Customize map tooltips When you hover over map objects in the Orion Web Console.5 from other SolarWinds Orion products.

Download SolarWinds-OrionToEOCMapConverter-1. Execute SolarWinds-OrionToEOCMapConverter-1.  2.  4. 107 . and complete the installer.  2. Troubleshoot importing maps into Orion EOC Map name conflict Maps you import from different Orion servers may share the same name. Click Import.solarwinds.  n The user must have Orion EOC access to at least one Orion server.0. Active Directory group accounts are not compatible with Map Converter.  n The user must have Node Management rights on the remote Orion server Configure environment for the map import  1.com/.  3. To edit the name of an Orion EOC map you are importing.5. Import maps into Orion EOC  1. Any pre-existing child/parent relationships for any renamed map will break.  4. Copy SolarWinds-OrionToEOCMapConverter-1.5.exe from http://downloads.5.exe to your Orion EOC server. Start the converter utility by running Convert Orion Maps to EOC in your SolarWinds program folder. See Microsoft TechNet Library for more information.exe. Select the Orion server hosting your maps from the Orion list.  n The user must log into the Map Converter using an Orion EOC account that was individually added to Orion EOC. Resolution: Rename the maps so that each has a unique name in Orion EOC.50727\Temporary ASP.  n The user must run the Map Converter using a Windows Administrator account that also has Orion EOC Administrator role permissions. Log in to the Orion EOC server with a Windows Administrator account that has Orion EOC Administrator role permissions. and edit the name. See Microsoft TechNet Library for more information.NET\Framework\v2.  3. You must manually reconfigure parent/child relationships after importing. Allow the Everyone group Full Control to the folder <volume>:\Windows\Temp\SolarWinds\NetworkAtlas\EOC\SolarWinds\NetworkAtlas\ MapsWeb\EOC\localhost and all of its child objects. Select the maps you want to import into Orion EOC. click the map name in the New Name column.  5. Provide members of the Users group Full Control of files in the folder <volume>:\Windows\Microsoft.NET Files.

108 . If the utility crashes. Hide nodes from users who have account limitations  1. and select Map Properties. Right-click any empty portion of the map. To prevent this. Slide the Map Status Will Be UP slider to configure the up state threshold on the Map Properties page.  2. but cannot retrieve any additional information about the nodes. Users with account limitations.  2. and select Map Properties. Advanced map layouts  n  Position map objects  n  Display grid  n  Align map objects  n  Distribute map objects  n  Arrange map objects according to a layout style Position map objects Drag objects from the tree on the left to the appropriate position on the map. Users with restricted access to the nodes will only see the restricted nodes. Set when a map is displayed as Up on parent maps using the Up status threshold The UP status threshold is the percentage of map objects that must be in an up state on a given map for the map to be represented as up on the parent map.  1. do not give node management permissions to users who have account limitations. User Access Control (UAC) If using an operating system that has UAC. Select Allow All Users to View All Nodes On This Map. Select Remove Nodes That Users Do Not Have Permission to View.Windows 2008 issues Windows 2008 customers may encounter problems either after manually clicking the Refresh button or after selecting a different Orion server. Reveal nodes to all users  1. restart it and resume importing. you must run the program using Run as Administrator. Display restricted nodes for users with account limitations If Orion Web Console users have account limitations that prevent them from seeing network nodes. Right-click any empty portion of the map. but with the permission to run and use the Network Atlas can change this setting in the map.  2. and select Map Properties. Right-click any empty portion of the map. set whether the users should see the restricted nodes on maps.

Select the map objects you want to align.  4.0). In the Size & Position area. Customize grid  1.  3. Align map objects  1.  3. 109 . select the object. enter the X and Y coordinates. click Grid Options > Grid Size. and press <Ctrl> + <arrow>. Click Edit.Y) = (0. Click the map object. click Grid Options >Grid Points.  2.To nudge a map object. Click the Edit ribbon.  3. nor displayed in the Orion Web Console. To display grid points. To change the grid size. Map center is designated as (X. Click the button in the Align group to arrange the object.  2. click Grid Option > Grid Lines.  2.  1. and select a grid size. BUTTON FUNCTION DESCRIPTION Align Left Aligns all selected objects on the left edge of the group Align Right Aligns all selected objects on the right edge of the group Align Bottom Aligns all selected objects on the bottom edge of the group Align Top Aligns all selected objects on the top edge of the group Center Vertically Centers all selected objects vertically Center Horizontally Centers all selected objects horizontally Distribute map objects  1.  2. Display grid A grid guide helps you maintain structural and spatial relationships as you arrange your map objects.  2. Select the map objects you want to distribute. To display grid lines. Click View. Grids are neither saved with a map. To reposition a map object:  1. Click the View ribbon. Click Show Grid in the Grid group. Click the Edit ribbon.

Use orthogonal layouts for maps that need to depict multiple clusters in a space-efficient manner. Object groups have radial placements. Reorganize Moves all mapped objects back to the center of the map view. add the Map resource on the view. Click Edit. Labels Display Network Atlas maps in the Orion Web Console To see a graphical overview of devices on your network. It emphasizes an even distribution of objects. create a Network Atlas map. BUTTON FUNCTION DESCRIPTION Circular Emphasizes the clusters inherent in the topology of a map. Click the appropriate button in the Distribute group to arrange the selected objects. Orthogonal Emphasizes compact drawings. Use hierarchical layouts to depict data dependencies. Use circular layouts for maps containing ring and star network topologies.  1. Child objects are arranged farther from the root object than their parent objects.  2.  2.  3. and uses only horizontal and vertical edges. Log in to the Orion Web Console as an administrator. Click Edit in the Map resource. Arrange Restores the default relative position of all object labels. Use tree layouts for maps that have a central control object. Object groups have star spiral placements. It emphasizes prominent links between main objects and its peripherals. Objects are enlarged if necessary to provide enough space for edge connections. Symmetrical Emphasizes the symmetrical patterns inherent in the map topology. Use symmetrical layouts for maps that have fairly homogenous or uniform clusters. 110 . and specify the map you want to see in the resource. Click a layout style from the AutoArrange group. and minimizes edge crossings. Hierarchical Emphasizes mapped dependency relationships by placing objects at different levels. Tree Emphasizes parent and child relationships. BUTTON FUNCTION DESCRIPTION Distribute Distributes all objects so that they are equidistant from the left edge of Horizontally the leftmost object to the right edge of the rightmost object Distribute Distributes all objects so that they are equidistant from the top edge of Vertically the topmost object to the bottom edge of the bottommost object Arrange map objects according to a layout style  1.

See Import maps into Orion EOC. Click Settings. and volumes. and click Edit View. Click Resource. 111 . Stop monitoring devices Deleting a node also deletes all its applications.  6. Log in to the Orion Web Console as an administrator. You need node management rights. Click Submit.  2.  n Click Manage Nodes in the All Nodes resource. Click Network Map in the Added list. and click Save.  5. Click Settings > Manage Nodes.  1. Access the Node Management view in two ways:  n Click Settings > Manage Nodes.  8. Select the map from the Select Network Map list.  7. interfaces. Click OK. Select your map from the Select Map list. Select Home. Click the Home view to see the map. Manage devices in the Orion Web Console In the Orion Web Console.  1. Display maps in the Orion EOC Web Console Network Atlas maps must be converted to display in an Orion EOC Web Console.  3.  2. The selected map will now appear in the Map resource.  4.  3. Log on to the Orion EOC web console with an administrator account. click OK. The All Nodes resource is included on the Orion Summary Home view by default.  9. but you can include it on any other view.  10. you can add and remove devices. Save Changes. quickly view and edit device properties from the Node Management view. Click Manage Views.  4. If prompted to confirm your changes. An individual event may be recorded for each deleted network object.

Available properties depend on the Orion Platform products you have installed. and click Edit Properties. and select the object. Unmanaged.  n To find a node. View node data in tooltips Hover over a monitored node in the Orion Web Console to view an immediate status overview of the device. Select the node. and select the interfaces. Response Time Packet Loss The percent of all transmitted packets that are lost by the selected node as of the last node poll. Average The measured average response time of the selected node as of the last node poll. Locate the node for which you want to edit properties. Warning. 112 . or volume. Select the object. Down.  1. To find the node. Address Machine Type The vendor icon and vendor description of the selected node. select a property in the Group By list. Edit node properties Only edit node properties in a single browser tab to prevent database errors and data losses. Click OK to confirm deletion.  2. use the search tool above the table to find the nodes. use the filter and search tools above the nodes list.  3. Polling IP The IP address currently assigned to the selected node.  3. interface.  n To group found nodes. and click Delete. To find a monitored application. use the filter and search tools above the node list. expand the parent node. CPU Load The percent of available processing capacity on the selected node that is currently used as of the last node poll. Click Settings > Manage Nodes. Memory Used The percent of available memory on the selected node that is currently used as of the last node poll. N ODE DATA IN TOOLTIPS Node Status Current status of the node (Up.  4. To delete multiple interfaces on different nodes. You need Node Management Rights. or Unreachable).

 4. Changing the IP address affects data collection. select Dynamic IP Address (DHCP or BOOTP). Changing the SNMP port applies to statistics polls. you can:  a. Do not change the IP address. Change the polling method for the node.  2. Some vendor implementations of 64-bit counters produce faulty data. Collect Statistics and Poll for Topology Data fields. IPv4 resolution will be used by default. and SNMP trap collection.  6. and select Allow 64-bit Counters. To change the template for the address used in the Node Details resource that allows you to navigate to the node from the resource. If the device is dual-stack. Click Submit. or click Select IP Address and select the new IP address. community string. It does not impact the node as it is referenced on the network. click Change Polling Engine. Privacy and Authentication settings (for SNMPv3). To dynamically assign the IP address of the selected node.  5. 113 . If you are using SNMP to poll the selected node.  3.  4. To rename the node. To change the polling IP address. scroll down to Web Browse Template. and change the default http://{{HrefIPAddress}}. or SNMP port unless they have changed on your network. Edit the Community Strings (for SNMPv1 and SNMPv2c) or Credentials. Click Test to test your provided SNMP settings. provide the DNS Hostname. Changing the community string or SNMP port affects data collection. If you notice erratic or incorrect data. Edit polling settings  1. and which view opens when you double-click the node  1. Universal Device Pollers (UnDPs).  c.  7. confirm that the monitored device supports 64-bit counters. and you are experiencing frequent counter rollovers. Click Submit. web address. If you have high-speed interfaces. Change the IP address only if it changed on your network to continue collecting the statistics without reconfiguring the node.  3. provide new intervals in the Node Status Polling. and select the IP Address Resolution format. Edit the SNMP Version and SNMP Port.  b.  d. type the new IP address.  2. type the new name in the Name field. To change the existing polling intervals.Edit the node name. To change the view which displays details about this node. select the View Type from the list. clear the box to disable 64-bit counters. Changing the node name only affects the way the node is identified on charts and graphs in the Orion Web Console. If there are multiple polling engines in your environment and you want to change the polling engine that polls the node.

 5. and packet loss. Click Test to verify that the credentials are valid for the selected UCS Manager.  b.  c. or delete an existing dependency that includes the node. Click Test to validate. Click Submit. Scroll down. Click Settings > Manage Nodes. if required. If a node which you added to the SolarWinds Orion database as an ICMP only node also supports SNMP. To poll for VMware.  4. Click Submit. average response time. Log in to the Orion Web Console as an administrator. If SolarWinds SAM is installed. edit. provide the vCenter or ESX Server credentials.  3. and you want to start collecting additional statistics.  3. Select Nodes from the Show drop-down list. you can poll Layer 3 data. and click Test.  1. Select Disable VRF Context Polling. If you have SolarWinds User Device Tracker (UDT) installed and the node has UDT ports attached. Select Active Directory Domain Controller.  1. Add what additional data you want to poll on the node  1. and define the credential. Select the credential to be used. Provide values for custom properties on the node. If the node is a UCS Manager and you want to poll for UCS data.  2. and enter the Layer 3 Polling Interval. Click Submit. The default is 30 minutes. select Poll for UCS.  2. click Manage Custom Properties to create or manage custom properties. and locate the node which you want to edit. or select <New Credential>. and adjust the default values. Enter the Domain Controller Polling Interval to be used. you can monitor Active Directory users that log in to your network. Select Poll Layer 3 Data from Device. Promote a node from ICMP to SNMP monitoring Orion Platform products only use ICMP to poll devices for status. Administrator credentials are needed only for installing agents. click Manage Dependencies and adjust the dependencies. provide the Port on which the UCS manager listens and credentials.Edit dependencies or custom properties  1. To add. select Poll for VMware. 114 . Customize alerting thresholds Be informed when polled values for a metric on the node reach unwanted values by specifying custom thresholds for the node. change the polling method to SNMP. select Override Orion General Thresholds for the metric.  a. If you cannot see the required custom property.  2.  3. and provide the following information.  2. See Monitor virtual infrastructure in the Orion Web Console for more details.

The Community String is a password to authenticate data sent between the management station and the device. For more information. select Allow 64-bit Counters. If you have installed multiple polling engines. select the Polling Engine you want to use to collect statistics from the added node. and contact the hardware manufacturer.  6. Select the node. Collected statistics are displayed in the Orion Web Console. See the vendor documentation for your network device for further information. the Read/Write Community String. The interfaces and volumes for this nodes are displayed. installing new software. while performing node maintenance. enter the Community String and. Locate the node to view:  n Use the search tool above the node list. If the SNMP port on the added node is not the Orion default of 161. Scheduling a Node Maintenance Mode Time Period When you need to perform maintenance on a node or its components. maintains the accuracy of your data and prevents unnecessary alert messages. see Setting Interface Management States. or setting a node status as Unmanaged. For SNMPv1 or SNMPv2c. Click Submit.  1. and click List Resources on the Node Management toolbar. and expand the group including the node to view. clear the Allow 64 Bit Counters box for the device. Select the node.  n Select a Group By option.  10. you may want to discontinue polling while the device is down for maintenance. The default is usually "public".  3. In the Polling Method section. Click Test to validate the strings. Use the strings configured on the device. For SNMPv3.  4.  5. select Most Devices: SNMP and ICMP. If the added node supports 64-bit counters and you want to use them. Click Settings > Manage Nodes. The List Resources view also lists statistics monitored on the node. and click Edit Properties.  11. You can temporarily suspend data collection on individual nodes and resume data collection as necessary.  12. View the resources and statistics monitored on a node Resources monitored on a node include interfaces and volumes. 115 . Disabling polling. showing which are being currently monitored. Suspend collecting data for monitored nodes Monitored devices are regularly polled for operational status. Select the version of SNMP to use. enter the actual port number. such as upgrading firmware. If you notice erratic or incorrect data when using 64-bit counters. This option is not displayed if you are only using one polling engine.  7.  2.  9.  8. The default is SNMPv2c. The status of objects is signified by an icon. provide the credentials and click Test to validate the credentials. optionally. or updating security.

 4. Log in to the Orion Web Console as an administrator. click More Actions > Poll Now. Poll and rediscover devices immediately Devices are polled for statistics and status regularly.  1. Then they total the amount of memory in use by each allocation to compute what percentage of the physical memory is in use. Use the Rediscover option to update node data such as machine type. You can poll a device or rediscover a node manually at any time. Troubleshoot Windows Server memory over 100% When Orion Platform products poll a Windows server for CPU load and memory utilization. To poll the selected node or interface. To rediscover the selected node. Discoveries run according to their schedule. as specified in the Polling Settings. Click Settings > Manage Nodes. as many applications pre-allocate memory and swap before it is actually needed.  2. Select the node or interface you want to poll or rediscover. Resume data collection for nodes On Manage Nodes. Suspend polling data for the node while the device is down for maintenance to maintain the accuracy of data and prevent unnecessary alert messages.  3. and click OK. Log in to the Orion Web Console as an administrator. If you suspend data collection for a node. Click Settings > Manage Nodes. they pull the amount of physical memory to define the 100% level. Provide start and end times and dates for your management suspension.  4.  1. and click Unmanage. This can result in memory utilization readings over 100%. it is suspended automatically for all interfaces and volumes on the selected node. all monitored interfaces and volumes on it will be collected again. This information does not often change. or location. Information for the selected node. system name. or updating security. Suspending data collection is helpful when you need to perform maintenance on a node or its components.  2. click More Actions > Rediscover.  3. Locate the node(s).  5. select the node. 116 . Data for the selected node and monitored resources on the node will be suspended for the specified time period. Select the nodes. installing new software. and click Remanage. such as upgrading firmware.  5.

you can group all nodes managed by DevOps that are mission critical and then add that group to a more inclusive list of mission critical objects. For example.  4. For example. When monitored as a volume. click Edit Properties. Check the node you want to promote.Workaround Add physical memory as a volume for monitoring these servers.  3. the values will be more in line with your expectations. Without dependencies. 117 . Dependencies between objects allow you to better represent the status of objects on your network. interfaces. Group monitored objects A group is a collection of monitored objects. By establishing dependencies. and even other groups as groups. Promoting a Node to WMI Monitoring You may need to log in with an administrator account to perform this action. click Submit. Nesting a group within another does not create a strict parent/child relationship. the child objects are displayed as Unreachable instead of down. Group objects and mirror network dependencies in the Orion Web Console Groups and dependencies help you organize how data about your network is presented in the Orion Web Console and can improve or simplify alerts. all monitored objects on an unresponsive monitored node report as down. and then select Windows Servers: WMI and ICMP. you can group nodes from the same location and create alerts and reports about the status of the group. navigate to Settings > Manage Nodes. applications. You can include groups in other groups. volumes. You can manage Orion objects such as nodes. Enter the appropriate WMI credentials. such as a group of nodes from the same location. You can include any group as a member in any number of other groups.  1. then click OK. Click Test to confirm your settings.  2. By using groups. On the web console. and use the groups as the basis of alerts. When done. This prevents false object down alerts. you can logically organize monitored objects. or group of all nodes owned by a department.

including alerts and dependencies. Click Preview to verify that the dynamic query is selecting the intended objects. See Custom properties. Objects added through dynamic queries are automatically added or removed from the group.  n Automatically select group members based on shared properties by clicking Add Dynamic Query and creating conditions.  2. Manually or automatically select objects for this group.  5. Click Add New Group. To create custom properties. click Manage Custom Properties in a new tab. or any custom properties. The new group is listed on the Manage Groups page and can be used in other parts of the product. Click Settings > All Settings in the menu bar.Create groups Select objects you want the group to contain.  4. click Manage Groups.  6. how often objects refresh in the group. Click Advanced to set the Status Rollup Mode.  3.  1.  n Select the check box next to the object to select object manually. Click Create Group. or specify group members using a dynamic query based on shared properties. In the Node & Group Management grouping. 118 .

Click Settings > All Settings in the menu bar. select the query or object.  3. The Show Best Status selection is useful for displaying groups that are defined as collections of redundant or backup devices.  6. In the Node & Group Management grouping. click Add & Remove Objects.  2. Down) (Up) (Up.  1. Click Submit again to save the group.  n Select the check box next to the object to select object manually. Click Preview to verify that the dynamic query is selecting the intended objects.  5. Select a group.  3. Select a group you want to edit.Edit group properties or change the group members You can edit the properties of an existing group. click Manage Groups.  4. and clicking Edit Dynamic Query. Manually or automatically select objects for this group. To add or remove the group members. Warning.  2. In the Node & Group Management grouping. Click Submit to save the edited objects and queries. and click Remove. or add and remove objects. open Manage Custom Properties in a new tab. If you remove an object from the group and that object has triggered an alert while it was a member of the group. To create custom properties. how often objects refresh in the group. or any custom properties. You can also change group members directly on the Manage Groups page.  10. Click Advanced to set the Status Rollup Mode. Set the group status based on the status of the group members The status of a group is determined on the status of the group members. Click Settings > All Settings in the menu bar. Down) (Up) 119 . To remove an object or query from a group.  9.  7. click Manage Groups. and click Delete. and click Edit Properties.  8. the alert continues to be active until it's acknowledged. Delete groups  1.  n Automatically select group members based on shared properties by clicking Add Dynamic Query and creating conditions. Edit an existing query by selecting a dynamic query. OBJECT STATES GROUP STATUS (Up.

Down) (Down) (Warning. In the Node & Group Management grouping. For example. or the result of the physical architecture of the network itself. then a Mixed Availability ( ) warning status is displayed for the whole group.  2. goes down or becomes unresponsive all interfaces on the switch will also be unresponsive. 120 . even though they may be working. such as a switch. If there are no warning-type states. Unknown) (Warning) The Show Worst Status selection ensures that the worst status in a group of objects is displayed for the whole group. click Manage Dependencies. OBJECT STATES GROUP STATUS (Up. Create a dependency between network objects  1. when a parent object. Down. OBJECT STATES GROUP STATUS (Warning. Unknown) (Down) The Mixed Status Shows Warning selection ensures that the status of a group displays the worst warning- type state in the group. Click Settings > All Settings in the menu bar. OBJECT STATES GROUP STATUS (Critical) (Critical) (Mixed Availability) Mirror network object dependencies in the Orion Web Console Dependencies are parent-child relationships between network objects that allow you to account for constraints on the network. Up) (Warning) (Warning. Down. The constraints can be the result of the design of a specific device. but the group contains a mix of up and down states. To account for this situation. Warning. and their own status cannot be determined. Enable Auto Dependencies in the Polling Settings page to create 1:1 parent-child node dependencies automatically. You can choose to ignore dependencies created this way in the Manage Dependencies view. the Unreachable status is used for the interfaces. because their parent node reports as down. such as interfaces on a switch or router.

 5.  3. The dependency appears on the Manage Dependencies page. and click Next.  1. select the child entities. Edit a dependency between network objects Automatic Dependencies cannot be edited. If there are active alerts on child objects.  2. 121 . Click Manage Dependencies in the Node & Group Management grouping. Click Add New Dependency. Select the parent object or group. Click Settings > All Settings in the menu bar. and click Next. they are listed on this view. Type a Dependency Name. Review the settings for the dependency. Click Submit.  6.  7. You can also display the dependency on custom views in the Orion Web Console.  4.

 3. Select a dependency. Active alerts that rely on the deleted dependency stay active until acknowledged. and select it on this view. Select the child object or group. Click Settings > All Settings in the menu bar. Changes are saved to the dependency. To define a dependency so that the reported states of multiple child objects depend on the status of one or more parent objects. create a group including all parent objects.  1. they are listed on this view. Click Submit. Click Manage Dependencies in the Node & Group Management grouping. and click Alerts on Child. the listed alerts might be suppressed. it is polled as usual. Its status does not switch to Unreachable. Select the dependency that includes the child object on which the alerts are active.  1.  3.  7. and alerts are not suppressed. Review the settings for the dependency. Select the dependency. even if you remove the object from the dependency. alerts based on polled statistics are not triggered.  2. Click Settings > All Settings in the menu bar.  6. If there are active alerts on child objects. but you can display active alerts on child objects manually. 122 . Alerts based on default or custom property values are not affected.  5. Select the parent object or group. View active alerts on child objects when the parent object is down When a parent object is down and the dependent child objects are Unreachable. If the parent object is down. Click Yes to confirm.  4. and click Edit. and click Delete. If a child object can be polled using a different route. To define a dependency so that the reported states of child objects depend on the status of multiple parent objects. Deleted dependencies are removed from the Manage Dependencies page. and select it on this view. You can ignore them in the Manage Dependencies page.  2.  3. and click Next. The dependencies are not removed from historical logs. create a group including all child objects. Click Manage Dependencies in the Node & Group Management grouping. Active alerts that affect members of the dependency stay active until acknowledged. and click Next. Delete a dependency between network objects Automatic Dependencies cannot be deleted.  4.

 n Viewing node and application data in tooltips . the application templates used in the scan.  n Application Discovery. To use the wizard. click Settings > All Settings > Discovery Central > Discover Applications.Modify resources displayed in the Application Summary page. Set up application monitoring with application monitors and templates. On the Web Console. Click [+] to expand the node groups. You can also access this through the Settings > All Settings > SAM Settings > Scan Nodes for Applications.  n Customize SAM Application Summary views .You can view node and application data directly through hover-over tooltips. see Monitor your network in the Orion Web Console.Learn how to add application monitors to currently monitored nodes. then click Next.  1. Application Discovery SolarWinds SAM can scan nodes and automatically assign the Application Monitors it deems suitable for each scanned node. the application templates used in the scan.  n Add application monitors to nodes .  n Add SolarWinds SAM data to the Node Details view . 123 . For details on adding and monitoring nodes. and the scanning parameters that determine a match. You control the nodes to be scanned. You may need to log in with an administrator account to perform this action. You control the nodes to be scanned. You may need to log in with an administrator account to perform this action. adding many applications at once can take a great deal of time.  n Customize the application details view .Modify Node Details to display SAM resources.Discover applications in your environment SolarWinds SAM can scan nodes and automatically assign the Application Monitors suitable for each scanned node. click Discover Applications. and then select the nodes you want to scan. and the scanning parameters that determine a match. In larger environments.  2. In larger environments.Discover and add applications through discovery. adding many applications at once can take a great deal of time.Learn how to customize the application and template views.

As you select templates across the filter groups. To scan for these templates. the credentials in this list are tried in the order in which they appear. Some application templates require credentials either to access restricted resources. click Next.  n Strong Match . A banner message appears near the top of the screen.Most of the components must match to assign the template. When you are finished entering credentials. If you have domains sharing user names with different passwords. 124 . Assign Anyway from the Do you want to assign duplicates list. click More Details in the banner message. or go to the Application Summary screen. Select the applications to locate in the scan.  4.At least one component must match to assign the template. You are notified by a message near the top of the screen when scanning is complete. When you are finished selecting applications. If a template you are scanning for requires credentials. click Next. To adjust the template assignment criteria. Warning: Credentials are tried several times over the course of a scan. select Yes. To avoid potential account lockouts that affect actual users.  7. no actual user is affected by an account lockout if a password should be entered incorrectly. so an incorrect password is likely to lock out an account. If the automatic discovery matches templates that are already assigned to the node. cancel the scan. or to run within the context of a specific user.  3. With service accounts. Click Application Summary to display the summary page. SolarWinds recommends that you run separate application discoveries for each domain. by default the template is not assigned a second time. Click Start Scan to begin the scan.Some of the components must match to assign the template. If you want to assign duplicate templates.  n Exact Match . Click More Details to see the results of the scan. SolarWinds recommends that you create and use service accounts. expand Advanced Scan Settings and move the slider to the desired setting:  n Minimal Match . they display in the selected applications section.  n Partial Match . SAM scan in progress. running in the background.  8.All of the components must match to assign the template. To view the progress of the scan. add the necessary credentials to the list. From this screen you can see the progress of the scan. Review the summary for the scan. You can use the Show only drop-down list to filter the application template list.  6. A service account is an account created specifically for the purpose of providing credentials to use for SolarWinds monitoring.  5.

 6.  1. Select or enter the appropriate credentials. Select the Application Monitor(s) you want to assign.  3. modify any of the information as needed. On the Add Application Monitors step. You can modify the assigned application monitors for the node at any time. use the Show Only drop-down to select a category of Application Monitors. and then click Next.Add application monitors to nodes After adding individual nodes. Add a node from the web console by clicking Settings > All Settings > Add a Node.  2. On the Change Properties page. For a list of monitors. you are prompted to add applications for monitoring the desired application(s) on the new node.  5. such as the Node Status Polling interval (in seconds) and the Collect Statistics Every frequency (in minutes). 125 .  4. A list of monitors displays. Click OK and complete adding the node. see Component Monitor Types.

You may need to log in with an administrator account to perform this action. use < TemplateName > Details View in the field Custom Application Details View. Select a view for a template You may need to log in with an administrator account to perform this action. then proceed with your customizations. Select Yes. Click Submit. Return to Applications > SAM Summary then click the Application Monitor to view its application details page.  1.  1. You may need to log in with an administrator account to perform this action. Select an Application Monitor and then click Edit Properties. If you want applications based on this template to use the default view. set Custom Application Details View to No. click Settings > All Settings > SAM Settings > Manage Application Monitors.  3. click Settings > All Settings > SAM Settings > Manage Application Monitors. Applications inherit the custom view setting from their templates in the same way as other template settings.  4.  2. Click Customize Page and proceed with your customizations.Customize the application details view Applications inherit the custom view setting from their templates in the same way as other template settings. Custom application details view You can select and create a custom application details view.  4. On the Web Console. use Default Application Details View. If you want applications based on this template to use the custom view. On the Web Console. You can customize the templates through overrides or creating a copy of the template and editing that content. Find an assigned Application Monitor without a Custom View. then click the name of the assigned Application Monitor to view its application details page. Click Customize Page. After creating a customized application details view for a template.  3. you can change the Custom Application Details View setting in the template properties to switch between the default view and the custom view. set Custom Application Details View Yes.  3. On the Web Console. where TemplateName is the name of the 126 .  2.  1. Click Modify Template Settings in the field Custom Application Details View. This custom view is applied at the template level.  6. Select a template and then click Edit.  5. use <TemplateName> Details View.  2.  4. click Settings > All Settings > SAM Settings > Manage Templates.

where <TemplateName> is the name of the selected template.  1. Click Submit. If you want this application to use the custom view. If you want this application to use the default view. selected template.  3.  6. Select a view for an application You may need to log in with an administrator account to perform this action.  2. Click Submit.  5. use <TemplateName> Details View. 127 . use Default Application Details View. set Custom Application Details View to Yes. On the Web Console. click Settings > All Settings > SAM Settings > Manage Application Monitors.  5. Click Modify Template Settings in the field Custom Application Details View.  4. Select an Application Monitor and then click Edit Properties. set Custom Application Details View to No.

or create a copy to refine with filters and resources for your own summary. locate and select Application Summary. You can create a copy of the Applications Summary view simply by selecting and copying through the Manage Views page. On the Web Console.Customize SAM Application Summary views You can edit the current SAM Application Summary.  2. and click Copy. Select the Copy of the Application Summary and click Edit. You may need to log in with an administrator account to perform this action.  1.  3. You can change the name of the view. and more. 128 . click Settings > All Settings > Manage Views. add and remove resources. The SAM Application Summary page is called Application Summary in the Manage Views list. modify column layouts.

The Add Resource page opens to select one or more resources to add. A NOC mode view is also available to enable. These options include resources like All Applications Tree. and many other application/component monitors.  6. click Preview to verify the data and layout. delete. AppInsight resources. Click [+] in a column you want to display SAM resources. AppStack Environment. If satisfied. 129 . You can also create and modify NOC views for cycling through network monitoring resources. To list SAM specific resources. You can add Limitations for access and content through the View Limitations section. click Done to save. you can Group By Classic Category and select Sam Application Summary Resources. see Create.  5. For details on how to modify and enhance the view. When done. modify.  4. or restrict views.  7. Top XX Monitored Processes.

You can click the objects to access details pages for deeper data or to manage alerts and use management options. or unmanaged Status SolarWinds SAM now supports the ability to include applications in calculation of node child status. down. providing at-a-glance updates and data for quick responses.Viewing node and application data in tooltips You can hover over objects such as nodes and groups to view additional information. but application on that device is down. These tooltips also include SAM specific data. warning. unplugged. you will see a child status icon indicating there is a problem. So if node is up. IP The IP address currently assigned to the selected node Address Machine The vendor icon and vendor description of the selected node Type Average The measured average response time of the selected node as of the last node poll Response Time Packet The percent of all transmitted packets that are lost by the selected node as of the last node Loss poll CPU Load The percent of available processing capacity on the selected node that is currently used as of the last node poll Memory The percent of available memory on the selected node that is currently used as of the last Used node poll # of Number of running VMS and total VMS Running VMS ESX Host Status of the ESX Host Status Application tooltips TOOLTIP DATA DETAILS App Name The name of the application 130 . Node tooltips TOOLTIP DETAILS DATA Node Current status of the node: up.

unknown. or unmanaged Components with List of the components with problems and their statuses Problems   131 . down. down. warning. or critical Server Status Operational status of the server: up. unplugged. TOOLTIP DATA DETAILS App Status The status of the application: up. warning.

For more details on modifying a view.  1. You can modify the content of the view through the layout and resources included. click Settings > All Settings > Manage Views. you may need to edit the Node Details . see Add resources and columns to views. and define subviews.Summary view. 132 .Add SolarWinds SAM data to the Node Details view To view SAM data including application and component monitor information. On the web console. Select the Node Detail summary and click Edit. You may need to log in with an administrator account to perform this action.

AppStack Environment. The Add Resource page opens to select one or more resources to add. To check the view. Top XX Monitored Processes. Click [+] in a column you want to display SAM resources. Click Done to update the view. You can edit the view again to further modify the content. AppInsight resources. You can move these resources to other columns or click [+] to add resources to those columns.  4. To list SAM specific resources. 133 . you can Group By Classic Category and select Sam Application Summary Resources. These options include resources like All Applications Tree. navigate to a node you edited to see the added resources and layout. and many other application/component monitors.  3.  2. Click Add Selected Resources to save all selections to the column.

alerts. Devices and applications you want to monitor must be added to the SolarWinds Orion database through discovery. The web console provides in depth monitoring data and captured status and configurations for all monitored applications. traps. forecast usage.  1. you can access investigate further to troubleshoot alerts. traps. To display messages for specific devices. and syslogs in the Orion Web Console Message Center The Message Center provides a view where you can see all events. See Discover and add network devices. and provide the number of messages you want to show. To monitor your network. Click Alerts & Activity > Message Center.Monitor your network in the Orion Web Console Like all Orion Platform products. select the Time period for the messages you want to review. and servers. select device properties in the Filter Devices area. As you view data. and Syslog messages on your network.  3. In the Filter Messages area. 134 . services. and syslogs in the Orion Web Console Message Center  n View the resources and statistics monitored on a node  n View network events in the Web Console  n View notifications  n Monitor hardware health  n Monitor virtual infrastructure in the Orion Web Console  n Monitor devices with SolarWinds Orion agents  n Monitor Syslog messages  n Monitor SNMP traps  n Monitor Quality of Experience metrics  n Monitor fibre channel devices and virtual storage area networks (VSANs)  n Monitor wireless networks  n Monitor EnergyWise devices  n Set up and monitor Cisco Unified Computing Systems (UCS) View events. alerts. and modify configurations. alerts. SolarWinds SAM offers immediate insight into the performance of your network. review the following:  n View events. traps.  2.

and expand the group including the node to view. You can view and remove them as your network management policies require.  2. To show all messages. event type. Remove events from the Web Console Clearing an event removes the event from the Events view. select Show Acknowledged in the Filter Messages area.  4. Click Refresh.  1. provide the maximum number of events to view. showing which are being currently monitored. 135 . Filter events by object.  4. Select the node.  1.  3. Cleared events are not removed from the event log and can still be used for reporting. You can choose how long network events are kept in the Events Retention field in Orion Polling Settings under Database Settings. To display only certain types of messages.  3. View network events in the Web Console All events that occur to monitored devices on your network are automatically logged and displayed in the Orion Web Console. such as a 1000. Locate the node to view:  n Use the search tool above the node list. To show events that have already been cleared. including messages that have been acknowledged. Click Clear Selected Events.  5.  2. Click Settings > Manage Nodes. Select individual events to clear or click Select All. select Show Cleared Events. or time period. select the messages to be displayed. Click Alerts & Activity > Events in the menu bar.  1. The interfaces and volumes for this nodes are displayed. Click Alerts & Activity > Events in the menu bar. and click List Resources on the Node Management toolbar. View the resources and statistics monitored on a node Resources monitored on a node include interfaces and volumes. Showing a large number of events. Click Apply to update the list of displayed messages.  6.  2.  3. Filter the displayed logged events in the Web Console Network events are logged and shown in the order they occur in the Events view of the Orion Web Console. can negatively impact performance.  5. The status of objects is signified by an icon. The List Resources view also lists statistics monitored on the node. In the Show X Events field.  n Select a Group By option.

HP.  1. Warning. Monitoring hardware health on Cisco.  n If you are monitoring Hyper-V nodes. and inform you if any discovered ESX nodes require credentials. F5. 136 . results display in the notification bar when the discovery completes.Selected events are removed from the view. When adding a device into the SolarWinds Orion database for monitoring. Dell.  n If you configured a scheduled discovery. and click Apply. new and unread posts to the Orion Product Team Blog are announced in the notification bar. or hotfix becomes available. View notifications Click the bell icon in the top-right corner to display unread notifications. such as any upgrade. service pack. Notifications include the following messages:  n If you configured the Orion Web Console to check for product updates. Monitor hardware health Get immediate insight into hardware issues on your network. Critical. the notification bar informs you when Hyper-V servers were found during a discovery.  n If you are monitoring any VMware ESX or ESXi Servers. enable polling hardware health statistics. To view the events again. or Unknown states. and Juniper devices informs you which of these devices are in Up. the notification bar displays the number of ESX nodes found during any discovery. an announcement displays when an update.  n If you configured the Orion Web Console to store blog posts. select Show Acknowledged.

137 . make sure that the correct MIB is selected. Hardware health statistics are polled through SNMP.  2. To verify that hardware health statistics are being collected. and click Submit.  3. For Cisco devices. click List Resources. from a MIB tree on your devices. Monitored Hardware Sensors SENSOR UP WARNING CRITICAL UNKNOWN Fan status Power Supply status Temperature Enable hardware health monitoring When you add nodes using Network Sonar Discovery. Make sure the correct sensors are enabled for the nodes. When adding individual nodes with the Add Node wizard.  3.  4. you can enable or disable hardware health monitoring in the wizard. click the node you want to monitor. In the Management resource on the Summary tab of the Node Details view. In the All Nodes resource. list monitored resources for the node and ensure that hardware health monitoring is enabled. Click My Dashboards > Home in the Orion Web Console. the hardware health sensors are enabled for devices that support hardware health monitoring automatically. Enable hardware health monitoring on a node  1. Enable monitoring from the Add Node wizard When selecting resources for monitoring a node in the Add Node wizard. select the Hardware Health Sensors box to enable hardware health monitoring.  2. Make sure the Hardware Health Sensors box is selected.

select Node in the Group by list. or shorten the retention periods. Enable hardware sensors Hardware health information is collected only for nodes where the hardware sensors are enabled. select Manage Hardware Sensors. To improve the performance. all sensors available in the selected MIB are monitored on devices with enabled hardware health monitoring. Enable. Hardware health information for the selected nodes will be collected now. To find all sensors available on a node. To immediately update hardware health statistics for a node. or use the Search box.  n Consider how often you need to update the health statistics and how long you need to keep historical records. Update hardware health statistics All changes are applied in the Orion Web Console with the next poll. Hardware health statistics will be immediately updated. see step 3.  3. click Settings > All Settings. Disable hardware sensors If you do not want to collect specific hardware health information or any hardware health information. This will not affect the performance as if you shortened the polling interval. Select the sensor that you want to enable on the node.  3. or change hardware health thresholds. disable. disable sensors. enter a longer polling interval. Go to the node details view.  n We recommend that you do NOT enter a shorter polling interval here because it might affect the polling performance. You can either use the Group by pane. 138 .  2.  1. and then select the node. and click Poll Now in the Management resource.  1. On the Manage Hardware Health Sensors page. and in the Node & Group Management grouping. and click Polling Settings in the Thresholds & Polling grouping. By default. Look up the current polling interval.  2. poll for the statistics manually. Scroll down to Hardware Health Polling section.Hardware health statistics for enabled hardware sensors are collected for the node. Go to Manage Hardware Sensors view (Settings > All Settings > Node & Group Management > Manage Hardware Sensors). and note the Default Statistics Poll Interval. and if necessary. Click Settings > All Settings. and click Enable. Find the sensor(s) you want to enable. or adjust hardware health sensors To view all currently monitored sensors. you can enable or disable polling on individual sensors.

Force to Up If you are not concerned about a sensor. You can either use the Group by pane. select this option. an event triggers together with the alert "Hardware is in warning or critical state. To find all sensors available on a node. Click Submit."  1. Change hardware health temperature units By default.  2. Log in to the Orion Web Console. or customize thresholds. Select the sensor that you want to edit. hardware health resources display temperature in degrees Fahrenheit. or use the Search box. This is the default setting.  3. Select the unit for temperature display (Fahrenheit or Celsius). Find the sensor(s) you want to enable. Click Submit.  2. Go to the Current Hardware Health resource. select Node in the Group by list. select Node in the Group By list. Go to Manage Hardware Sensors view (Settings > All Settings > Node & Group Management > Manage Hardware Sensors). The sensor will always be displayed as UP.  1.  3.  5. Set Custom Thresholds Use the dynamic query builder to define the status for the selected sensor. To find all sensors available on a node. and click Edit.  1. and click Edit Thresholds. and select the node. The status of the hardware health sensor will now be governed by the specified threshold. Navigate to a node details view. set a sensor to always appear to be up. and then select the node.  4. 139 . and click Disable. Go to Manage Hardware Sensors view (Settings > All Settings > Node & Group Management > Manage Hardware Sensors). You can either use thresholds available on the device. Select the sensor(s) which you want to disable on the node. ignoring the real data from the sensor. Select how you want to change the selected hardware sensor's status: Use Orion Defaults Use thresholds configured on the device. Hardware health statistics for the selected sensors on the selected nodes will not be collected now. Edit hardware health thresholds Hardware states displayed in the Orion Web Console change based on thresholds set for the sensors. When values polled on a node reach the threshold value.  2.  4.  3.

respectively. The status for most items will read OK. You can also access the temperature unit setting when editing a user in the Hardware Health Package Settings. When collapsed. the top level view (or roll-up status) of each hardware item will display the worst status of an item in that branch. depending upon the set threshold values and the returned values. which suggests a polling failure. the Hardware Health Details group appears on the Node Details page and looks similar to the following illustration. Gray icons indicate a status of Unknown. Hardware Details Once you have chosen the hardware you want to monitor. Current hardware health status The current status of your hardware's health can be determined by the Current Hardware Health grouping. You can click on the [+] and [-] icons to expand and collapse a particular tree branch of hardware that is being monitored. providing general information about your hardware and its status: This view will be hidden if hardware monitoring is disabled. as shown below. Warning. or Critical. and it is connected with your user account.The selected unit will be applied in all hardware health resources in the Orion Web Console. and red. This setting is user-specific. The icon colors for each item will change between green. 140 . yellow.

141 . You can see an overview of your monitored hardware's health. The default temperature measurement is in degrees. To change this to Celsius (ᵒ C). Hardware Health Overview chart This resource provides immediate insight into hardware issues on your network. Hover over each pie segment to display a tooltip with more detailed information. The Temperature Unit drop down menu can be found under the Server & Application Monitor Settings category. Fahrenheit (ᵒ F). On the Web Console. click Settings > Manage Accounts > Select Account > Edit.

To modify hardware thresholds.  3. 142 . You may need to log in with an administrator account to perform this action. disabled.  4. Dell OpenManage Server Administrator is one such example. select the objects. you can navigate to the Details page of each server by clicking any icon in the list. check the objects.  1. Click Submit.  c. then click Edit Thresholds. click Settings > All Settings > Manage Hardware Sensors.  b. The status is always Up.  2. Use Orion defaults: Use the built-in Orion logic for translating sensor reading to status. Choose from the following three options:  a. some values can be configured through the Hardware Monitoring Agent Software installed on your hardware. To enable or disable objects from being monitored. Additionally. then click either Enable or Disable. Force to Up: Ignore sensor readings when calculating status. Complete the logic form for both the Warning threshold and the Critical threshold as needed to satisfy your requirements.  d.Click a server icon in the chart to bring up a list of the servers with the indicated status. On the Web Console.  5. Change hardware health threshold values Hardware thresholds can be enabled. or modified via the Manage Hardware Sensors screen. The illustration below shows how threshold values for the temperature can be changed from the default values using Dell's software. From here. Set custom thresholds: Create your own logic for mapping sensor readings to Orion status. Note: Threshold modification may not be available for certain objects where information is not available.

Different default thresholds exist for different items in the Hardware Monitoring Agent Software. Consult your Hardware Monitoring Agent Software user guide for specific information about editing thresholds. VIM monitors the following:  n ESXi and ESX Server version 4. some may not. or as a standalone solution. 143 .Different default thresholds exist for different items in the Hardware Monitoring Agent Software.1 or later  n VMware vSphere version 4. Some of these thresholds may be accessible and open to editing. 2012 R2 Prerequisites to monitoring virtual infrastructure  n SolarWinds NPM or SolarWinds VIM is installed.  n SNMP on your virtual servers is enabled.1 or later  n Microsoft Hyper-V Server versions 2008 R2. some may not. It is available as a feature of SolarWinds NPM or SolarWinds SAM. Some of these thresholds may be accessible and open to editing. in integration with SolarWinds VMAN. 2012. Monitor virtual infrastructure in the Orion Web Console SolarWinds Virtual Infrastructure Monitor (VIM) is the feature that enables virtual monitoring directly from the Orion Web Console. Consult your Hardware Monitoring Agent Software user guide for specific information about editing thresholds.

Log in to the Orion Web Console as an administrator. VMware vCenter. Assess the status of the virtual environment The Virtualization Summary view shows the overall status of your virtualized infrastructure.  n VMware Tools are installed on all virtual machines you want to monitor.  n ESX credentials on ESX servers are created. Log in to the Orion Web Console.  2. add them.  1.  4.  1.  3. If your virtual machines are on monitored ESXi and ESX servers. On the Virtualization page. and if the vCenter or ESX Credentials are not listed. Launch Network Discovery in the Orion Web Console through Settings > Network Discovery > Add New Discovery.  2. Add the nodes using Network Sonar Discovery. VMware Tools are not a requirement but provide access to additional information. select Poll for VMware.  n You virtual infrastructure is discovered. ESX servers.  5. add Windows credentials for accessing Hyper-V nodes. and virtual machines which you want to monitor must be added to the SolarWinds Orion database. Complete the wizard and import the results. Click My Dashboards > Home > Virtualization in the menu bar. such as IP addresses. 144 . On the Windows page. Add virtual servers for monitoring Hyper-V nodes.

or when adding the node to the database.  5. select Hyper-V. or select New Credential. Click Settings > All Settings > Manage Virtual Devices. and specify a new credential set.  2. Click Settings > All Settings > Manage Virtual Devices. Select a Hyper-V server from the list. Assign credentials to Hyper-V servers  1. Assign credentials to VMware servers  1. and click Edit Properties. On the Virtualization Polling Settings page. VMware ESX or vCenter accounts used as credentials must have read-only permissions as a minimum. Click Test to verify the credential set. select VMware. and click Submit.View ESX host details Click an ESX Host server in the Virtualization Summary page to open the ESX Host Details view.  2.  4. 145 . choose a credential. Under Polling Method > Windows Servers. On the Virtualization Polling Settings page. assign credentials based on the server vendor.  3. Assign credentials to virtual servers If you did not provide the credentials within the Network Sonar Discovery.

click Manage Virtual Devices. or specify a new credential set.  5. On the VMWare Settings page. Log in to the Orion Web Console as an administrator. Click Settings > All Settings in the menu bar. Poll ESX hosts controlled by vCenter servers directly If your VMware ESX hosts are controlled by VMware vCenter servers. In the Product-Specific Settings grouping.  2.  3. Click Poll Through > Poll ESX server directly.  4. and click Edit Credential to make the necessary changes. Orion Platform products obtain the status of the ESX hosts from the vCenter server. 146 . Click Settings > All Settings in the menu bar.  3. Select a VMware server from the list. Choose an existing credential. To poll the ESX servers directly.  5. Click the VMware Credentials Library tab.  4. change the Poll Through setting of the ESX host. update the credentials in the Orion Web Console.  5. and click Assign Credential to assign it to the VMware server. Change VMware credentials in the Orion Web Console If credentials for a VMware account change on the device.  4.  3. and click Assign ESX Credential. In the Node & Group Management grouping.  2.  1. click Virtualization Settings > VMware Settings. Click Test to verify the credential set. Select the credential you want to update. you can also disable and enable polling for ESX hosts and vCenter servers.  1. Select the ESX hosts you want to poll directly. Log in to the Orion Web Console as an administrator.

This port must be opened on the server firewall so the Agent can connect.includes settings.includes instructions for Windows and Linux  n Agent management . see:  n Monitor devices with SolarWinds Orion agents  n Agent settings  n Agent communication modes  n Configure SNMP for agents  n Credentials and privileges used on Linux-based computers  n Certificates and the agent  n Agent deployment . for the User Experience Monitor template you may not want to measure response time locally from the server where the application is installed.Monitor with Orion agents in SAM When using the Orion agent. you can switch the application to poll without using an agent. No change to the Agent firewall is required. For full details on Orion agents. and modifying agents  n Upgrade agents manually  n Agent migrations Overriding agent and agentless monitoring You can override data collection behavior in specific instances per application monitor or template. If this is the case. SAM collects all data from application monitors for that server. For more information. SAM can deploy and consume collected data using Orion agents for Windows and Linux. You can configure an application or template to collect data through a preferred polling method as agent or agentless. see: 147 . For example. Communication type Agent Communication can be deployed as either Active or Passive:  n Agent initiated Communication (Active): The Agent initiates communication with the server on the default port of 17778 (this can be changed if needed). status.

Templates and component monitors Application templates provide collections of application monitors with configurable settings to collect and monitor data for Orion managed nodes. To use component monitors in Linux environments with the Orion agent for Linux. you need complete additional configurations. prerequisites. The following component monitors supported for Orion Agent for Windows:  n Process Monitor . This port must be opened on the Agent computer's firewall so the server can connect. No change to the server firewall is required. For details. This information is added to the component monitors and available in this section. and configuration requirements for application templates and monitors.Windows  n DNS Monitor .  n Orion Server initiated Communication (Passive): The Agent waits for requests from the server on the default port of 17790 (this can be changed if needed).TCP  n DNS Monitor . These templates include a variety of options based on operating systems. see SAM Component Monitor Types and SAM Template Reference.UDP  n Exchange Web Services User Experience Monitor  n HTTP Monitor  n Performance Counter Monitor  n SMTP Monitor  n TCP Port Monitor  n ODBC User Experience Monitor  n Oracle User Experience Monitor  n Windows Event Log Monitor  n Windows PowerShell Monitor  n Windows Service Monitor  n WMI Monitor The following component monitors are supported for Orion Agent for Linux:  n Process Monitor  n Linux/Unix Script Monitor  n Nagios Script Monitor  n JMX Monitor  n SNMP Monitor  n ODBC User Experience Monitor  n Oracle User Experience Monitor  n TCP Port Monitor  n TomCat Server Monitor 148 . and services. applications.

Reports The following reports are installed for use with the Orion Agent:  n Agent Inventory  n Agent Plugin Version 149 .

Under Product Specific Settings. This can be beneficial in situations such as:  n Polling hosts and applications behind firewall NAT or proxies. Microsoft Azure. Under Product Specific Settings.  n Define Global Agent Settings: opens the Global Agent Settings page from which you can allow automatic agent registration and allow automatic agent updates. Click Settings > All Settings in the menu bar. After deployment. Click Settings > All Settings in the menu bar. edit. high latency connections.  n Polling nodes across domains where no domain trusts have been established. Navigate to the Agent Settings page  1. The following options are available on the Global Agent Settings page:  n Allow automatic agent registration: (Recommended. This communication is fully encrypted using 2048-bit TLS encryption. update. Rackspace. Products install plugins on agents to collect the data that the agents send back.  n Support for low bandwidth. You can monitor servers hosted by cloud-based services such as Amazon EC2. or reboot an existing agent. Agent settings The Agent Settings page provides access to all of the global settings and tools needed to install and manage agents.  n Download Agent Software: opens the Agent Downloads page from which you can mass deploy or manually install an agent. click Agent Settings. and other Infrastructure as a Service (IaaS). all communication between the Orion server and the agent occur over a single fixed port. Click Define Global Agent Settings.  n Manage Agents: opens the Manage Agents page from which you can add a new agent. Additional agent settings can be modified locally on the agent.  2. click Agent Settings. The agent protocol supports NAT traversal and passing through proxy servers that require authentication.  n Secure. end-to-end encryption between the monitored host and the main poller. encrypted polling over a single port. enabled by default) Select this option to automatically register the agent and verify communication with the Orion server.  n Polling node and applications across multiple discrete networks that have overlapping IP address space.  3.Monitor devices with SolarWinds Orion agents An agent is software that provides a communication channel between the Orion server and a Windows or Linux computer.  2. Registered agents 150 .  n Full. Adjust the Global Agent Settings  1.

 n XX Hours: Control the length of time the agent are considered new in the Manage Agents list. Ensure all agent versions match the version of the server. Click Settings > All Settings > Manage Agents > Add Agent > Connect to a previously installed agent. it updates itself. Server-initiated communication All communication between your Orion server or additional polling engine and the agent is initiated by the Orion server. 151 . can communicate with the Orion server. enabled by default) Select this option to automatically upgrade the agent software when updates are available. You can register any waiting agents manually. You do not need to have a direct route from the Orion server or additional polling engine to the host where the agent is installed.  n Automatically create node: When you deploy an agent on a new node. Outdated agents may not be able to communicate with the server. You cannot use agent-initiated communication through proxy using NTLM authentication if you install the agent on a Linux-based computer. This communication method is also known as a passive agent. Agent-initiated communication All communication between your Orion server or additional polling engine and the agent is initiated by the agent. If you do not enable this option. You must have a direct route from the Orion server or additional polling engine to the host where the agent is installed. This is frequently influenced by where the computer you want to monitor is on your network. After the agent receives the new version. This process pushes a new version of the agent to client computers over the agent communication channel. the node is automatically added to your Orion server. port 17790 must be open on the firewall of the remote host to retrieve information from the agent. This process typically does not require rebooting. ports 17778 and 17791 must be open on the Orion server firewall to receive information from the agent. you will need to manually upgrade agents during product upgrades. and the agent does not initiate communication to your Orion server. Agent communication modes Communication modes determine how the agent and the Orion server communicate. To use this communication method.  n Allow automatic agent updates: (Recommended. To use this communication method. and your Orion server does not initiate communication with the agent.

In active mode. Review this information to locate and resolve any issues when troubleshooting connectivity. and you have no easy way to connect the two. you need to install the SNMP daemon if missing. 152 . Configure SNMP for agents SNMP is a polling method used by Orion agents and as default to collect for monitors and resources. access. there are no listening ports on the agent. You can manually configure SNMP. The following components and resources depend on SNMP connections:  n Location. The Orion agent configures SNMP for you during deployment. the configurations are verified and updated during agent deployment. and SysObjectID of the Node Details resource  n Asset Inventory page and resources  n Hardware Health data and resources  n SAM SNMP component monitor Configure SNMP To configure SNMP. Contact. If settings need to be modified for Orion agent.This communication method is most useful when the agent is installed on a network separated from your Orion server by one or more NAT devices. and data polled in SAM. This communication method is also known as an active agent.

SAM adds the community string.  n Checks the snmpd. SNMP v3 will not be auto-configured on deployment.conf file for the configuration of an agent owned community string. SNMP is restarted. You can provide SNMP credentials manually at the node level to configure access. SAM will not modify the configuration file. If the string is missing. To install: PyCrypto installation on ubuntu apt-get install python-pip pip install pycrypto 153 . Prerequisites To add SNMP credentials. you also need to install a common python extension pycrypto on the target machine to make polling possible. You cannot test the credentials until the agent is deployed. Deploying the agent automatically configures SNMP.If you need to install the SNMP daemon. SNMP cannot be configured. you can install the daemon using a command according to your Linux distribution. For encryption. Configure SNMP v3 If you have SNMP v3 configurations detecting users through the configuration file without an SNMP v2 community string. If the SNMP daemon is not installed. you can enter the credentials through the Add Node Wizard or edit an existing node. The string is "agent owned" = with an SNMP v2 community string in form of an agent guid (randomly generated value that is unique for each agent). For example: ### BEGIN SolarWinds Agent SNMP auto config rocommunity 36343901-D61F-4C72-B860-A8E18DD892E4 localhost ### END SolarWinds Agent SNMP auto config If SAM adds the community string. To install:  n Install on Ubuntu: sudo apt-get -y install snmpd  n Install on Red Hat / CentOS: yum -y install net-snmp  n Install on SUSE: zypper -y install net-snmp Auto-configuration of SNMP executes on the following actions:  n The first step during a Discovery  n Anytime you initiate a List resource on any node managed by the Orion agent for Linux SAM completes the following changes during auto-configuration:  n Checks the snmpd service is configured to start automatically after system reboots.

a service account is also created to run the agent service. Credentials and privileges used on Linux-based computers Agents installed on Linux-based computers may use three different credential sets to install and configure the agent. you need a properly connected agent deployed to the target node. During this process. Review the credentials and click Test.Test Credentials You can test any manually entered credentials by editing the Node. You need sufficient privileges to be able to do the following to install and configure the agent:  n open a SSH connection remotely  n SFTP or SCP  n install software 154 . To test.

Most Linux distributions require the user's password when using sudo. switching to the elevated credentials. and SNMP component monitor information. some Linux-based computers do not allow user accounts to connect remotely and install software. This account does not have remote access privileges and cannot be used to log in to the computer. Service account privileges When the agent software is installed. The agent software detects if you have SNMP installed on the computer and attempts to use your established SNMP credentials. SSH credentials Agents require a credential set that allows the user to open an SSH session from a remote computer. Upload a private key file or paste the private key in PEM format. and add it to its own group.  n create a user  n create a group Credentials are used to install and configure the agent and are not used at any other time. No data is collected if the agent does not have the correct SNMP credentials. Other distributions. When this is selected. Verify the credentials by opening an SSH connection to the remote computer. may require the root password. If this applies to the computer you want to monitor. and entering sudo -l. you need credentials with administrator or root-level privileges. enter the required credential for the Include Credentials with Elevated Privileges to install the package. you may need to include another set of credentials to use su or sudo for package installation. This is required if SNMP v3 is installed. we create a service account (SWIAgent). You can add these credentials selecting the Include Credentials with Elevated Privileges. This can be provided as either a user name and password or as a certificate. Verify your privileges by opening an SSH connection to the remote computer. you can select Include Credentials with Elevated Privileges and enter credentials that have the correct privileges. such as SUSE. Certificate credentials You can use any certificate-based credential that is supported by SSH. 155 . Depending on your Linux distribution. Credentials with elevated privileges To install the package. Depending on your network security policies. SNMP credentials Select Include SNMP Credentials in order to collect SNMP data to use in Hardware Health. You may remove the credentials from the credential store once the agent is deployed. we connect to the Linux-based computer using the provided SSH credentials and then switch users to the account with elevate privileges to install and configure the agent. For Linux-based computers. Asset Inventory.

For SAM users. such as Group Policies. SolarWinds Orion products supports multiple methods of deploying agent software.Manually move the installer to the remote computer and then install and configure it locally. For more information.  n Deploy an agent with the Add Node wizard  n Deploy an agent to a monitored node Manual deployment .Deploy the agent software from the Orion serverr to one or more client computers. Software deployment .  n Deploy the agent manually to a Windows computer  n Deploy an agent manually to a Linux-based computer Mass deployment . you must download the Root CA certificate and install it to the Local Computer\Trusted Root Certification Authority store on the server hosting the agent. If your certificate is not current.microsoft. The service account and group are removed when the agent is deleted from the node. When updating the agent. search for "Add the Certificates Snap-in to an MMC" at technet.The service account is used to run the swiagentd service.  n Mass deploy an agent on Windows  n Deploy agents on Linux-based computers through a repository  n Deploy with a Gold Master Image  n Deploy on Windows Core Servers Cloud deployment . if you do not enter credentials or select Inherit from node. SolarWinds Patch Manager.Mass deploy the agent software to multiple computers using a mass deployment technology. Certificates and the agent The Verisign Root Certificate Authority (CA) must be current.Deploy the agent to a computer in the cloud which can be manual or automated.update) for the duration of the update. These credentials may not have the elevated permissions required for executing scripts. the monitor executes the script under the agent credentials (SWIAgent). a second service runs (swiagentd.  n Manually deploy an agent on Amazon Web Services  n Automatically deploy an agent on Amazon Web Services  n Automatically deploy an agent on Microsoft Azure 156 . This is required because the agent software is signed using a Verisign certificate. Agent deployment Agents provide an additional method to poll devices that are part of a separate network or have intermittent connectivity to the network with your Orion server.com. Agents do not work with AppInsight for SQL in a clustered environment. or Puppet.

Most Linux distributions require the user's password when using sudo. you can choose to add SNMP credentials to collect SNMP data for Asset Inventory and Hardware Health from the remote computer. Choose the resources to monitor on the agent.  1. enter the required credential for the Include Credentials with Elevated Privileges to install the package. To monitor Linux-based computers. and click OK. it operates under a local account. Deploy an agent with the Add Node wizard This is the recommended method to deploy an agent to a computer.  11. Choose a credential from the list. In the Polling hostname or IP address field. The Orion server must be able to communicate with the client computers. After the agent is installed. or enter new credentials. Add application monitors on the agent. Other distributions. When the connections is successful. After the agent is deployed. Click Settings > All Settings in the menu bar. Click Add Node.  n The credentials must have administrator or root-level privileges. On Linux-based computers you can connect with one credential set and then use another credential to use su or sudo for package installation. may require the root password. Select Windows & Linux Servers: Agent as the Polling Method.  4.  5. such as SUSE.  2. the agent appears in the agent list on the Manage Agents page. the credentials may change with no impact to the deployed agent.  n These credentials are only used to connect to the remote computer and install the agent software. Change properties or keep the defaults.  7.  10.  3. Click Start Install on the Install Agent Software window. The Orion server deploys the agent software to the target computer. click Manage Nodes.  n For Linux-based computers. Select the operating system type of the remote computer.Windows Core requires specific setup before you can install the agent software. enter the IP address or fully qualified domain name (FQDN) of the computer you want to manage. installs the software using the credential you select.  6. and click Next.  8. 157 . Depending on your Linux distribution. and adds the node to the Orion server as a monitored node. Under Node & Group Management. Add Node. and click Next. TCP port 22 (outbound) must be open on the Orion server or additional polling engine and open (inbound) on the computer you want to monitor. and then click Next.  9.

To monitor Linux-based computers.  n You can assign credentials to multiple locations or nodes by selecting multiple entries.  6. Click Windows.  7. may require the root password. 158 . and click Next.  n These credentials are only used to connect to the remote computer and install the agent software. Click Install Manually. Under Node & Group Management.  n The credentials must have administrator or root-level privileges. Click Settings > All Settings in the menu bar. Click Add Agent.  2. Depending on your Linux distribution. Click Download MSI. choose where you want to install the agent by selecting existing nodes from the list. Select a node and click Assign Credentials.  5. Under Product Specific Settings. the agent displays in the agent list on the Manage Agents page.  8. On Linux-based computers you can connect with one credential set and then use another credential to use su or sudo for package installation. Click Settings > All Settings in the menu bar. enter the required credential for the Include Credentials with Elevated Privileges to install the package. Other distributions. This method is usually performed when you need to install the agent on multiple computers or if the computers are already monitored by the Orion server. When the connection is successful. After the agent is deployed. TCP port 22 (outbound) must be open on the Orion server or additional polling engine and open (inbound) on the computer you want to monitor.  3. Deploy the agent manually to a Windows computer Selecting this method of deployment may be helpful in troubleshooting connectivity issues with another form of agent deployment.  3. the credentials may change with no impact to the deployed agent.  2. such as SUSE.  1. click Manage Agents. Most Linux distributions require the user's password when using sudo. On the Deploy Agent on Network page.Deploy an agent to a monitored node Select this method of deployment to deploy agents from the Orion server. Click Next. This method is also helpful when the Orion server cannot communicate directly with the computer where the agent will be installed.  1. Select Deploy the agent on my network. The IP address field does not accept ranges. Click Deploy Agent.  4. click Agent Settings > Download Agent Software. The Orion server must be able to communicate with the client computers.  5. or entering the IP address or host name of a node that has not been managed.  4. and click Next.

 2. This is also known as a pull deployment.  3.  8.  4. On the Download Agent Software page. Copy and paste the command in the terminal open to the Linux computer.  1. this is port 17790.  8. Click Generate Command. The command downloads the software from the selected polling engine. Click Linux. click Advanced  n For Server initiated communication (passive). Select the items you want to monitor. Enter the Orion server IP address or hostname. Enter the Connection Settings. On the Manage Agents page.  5.  9.  7.  4. If you connect through a proxy. Select your Distribution and Communication Mode.  2. Click Download Agent Software File for Manual Installation. You can choose to copy the installer file to the Linux computer manually and then install it instead of using wget or curl. select your distribution. Deploy an agent manually to a Linux-based computer Use this method if the Orion server cannot push the agent to the Linux-based computer over SSH. Click Settings > All Settings in the menu bar. Select your distribution Agents are officially supported on the following Linux operating systems.  n For Agent initiated communication (active). the agent appears in the agent list on the Manage Agents page. enter the listening port number used to communicate with the Orion server or additional polling engine. 159 . Move the file to the Linux computer and extract it. Under Product Specific Settings. By default. select Agent Initiated Communication or Orion Server Initiated Communication. and then click Choose Resources.  6. select the new agent. When installation is successful and communication between the agent and the Orion server is successful.txt file. the computer you want to manage may be behind a NAT or is hosted in the cloud. and the SolarWinds Orion administrator account credentials. This uses wget or curl to download the installation files from your chosen polling engine. In the Installation wizard.  6. the agent displays in the agent list on the Manage Agents page. When installation is successful and communication between the agent and the Orion server has been established. and run it.  1. click Agent Settings > Download Agent Software. and click Submit. and click Next. Copy the MSI file to the client machine. select or enter the polling engine you want to collect the agent's data.  10.  7. Click Manually Install by Downloading Files via URL.  3. and Next. For example. Follow the instructions in the readme.

and click Next. but will attempt to install the software for the distribution you select.  2. Polling engine selection is important. 160 . Windows Installer can dynamically add or modify data in the installation database to customize the installation of the application. 64-bit only If your operating system is not listed. the agent appears in the agent list on the Manage Agents page. When you download the MST file. Additional information on creating MST files can be found on technet. you can use MST files to customize the software for your organization. the file includes the polling engine IP address and other vital information. What is an MST file? A Microsoft Transform (MST) file is a collection of specified changes applied to a base Windows Installer package file at the time of deployment. Generate and download the MST file  1. Click Windows.  3. After the software you want to install is packaged in the Windows Installer package format. such as installing only specific features. Under Product Specific Settings. this deployment method is an easy way to get agents on a large number of computers. 64-bit only  n Amazon AMI.  n Red Hat Enterprise Linux 5  n Red Hat Enterprise Linux 6  n Red Hat Enterprise Linux 7  n CentOS 5  n CentOS 6  n CentOS 7  n SUSE Linux Enterprise Server 10  n SUSE Linux Enterprise Server 11  n SUSE Linux Enterprise Server 12  n Ubuntu 14. Click Settings > All Settings in the menu bar. along with the MST file on the managed node. When you apply transforms to an MSI file. the agent will be installed and pointed to the correct polling engine. SolarWinds cannot guarantee that the software will work as intended on a non-supported OS.microsoft. The modular design of Windows Installer packages simplifies deployment. The MST file modifies the Microsoft Installer package.com. When you deploy the agent using the MSI file. When installation is successful and communication between the agent and the Orion server has been established. click Agent Settings > Download Agent Software. It is an overlay on top of an existing MSI file that defines what specific components or features of an application get installed. select the closest match to your Linux distribution. Mass deploy an agent on Windows If you are already using a mass-deployment technology.

or organizational unit (OU).  6. and click Next.MST. select Use Connection Details from Polling Engine. Select the agent communication mode. Use the host name and IP address of the polling engine that you can access from the client. and save the file. domain.  4. Click Linux. and click Next.  2. This method allows you to use automation tools to mass deploy agents on your Linux-based computers. To use an existing polling engine. Click Mass Deploy to Multiple Machines. Click Download .  n For server-initiated communications. enter the IP address of the Orion server or the additional polling engine as it is accessible from the host where the agent will be installed. Select your distribution. add the Software installation policy. to install agent software on your Linux-based computers. A container is a site. The IP address is required. When installing the software.MSI. Select the network path for the agent MSI and MST files. In Advanced Options.  5. This happens when the monitored host is behind a NAT or proxy device.  2. and then enter the host name and IP address. You may be prompted for the root password to add the repository. and then select a polling engine from the list.  a.  1. The Orion server and Additional Web Servers are Linux repositories for the agent. and then access the container properties.  6. such as yum. Add the MST file to a Group Policy  1. or zypper.  n For agent-initiated communication.  7.  3. To manually enter the polling engine IP address. apt-get. In these cases. The agent is deployed at login and is registered by Orion (if auto-registration is enabled).  3. Create a Group Policy object. locate the container where you want to advertise the application. enter the polling engine you want the agent to use. Copy the repository command and paste it in a terminal open to the Linux-based computer. you may be prompted that you are using a deprecated command.  7. Click Settings > All Settings in the menu bar. click Agent Settings > Download Agent Software. Deploy agents on Linux-based computers through a repository You can use built-in package management tools.  4. Click Install via Package Management Tool. enter your agent communication port number. and Next. select Enter Connection Details Manually.  5. and save the file.  b. In Active Directory. Share a folder containing the MST and MSI files with proper permissions. Under Product Specific Settings.  4. You may need to manually enter the polling engine information if the IP address is different from what the Orion server reports. The default port is 17790. Click Download . 161 .

enter the IP address of the Orion server or the additional polling engine as it is accessible from the host where the agent will be installed. Click Distribute via a Golden Master Image. Install an agent offline  1.  7.  n For agent-initiated communication.  6.bat. Click Windows. This saves time for virtual machines. The default port is 17790.  10. Click Download . physical servers. and cloud instances. and click Next. You must add the location of the repository to every Linux-based computer that you want to install the agent software from the repository. You may need to manually enter the polling engine information if the IP address is different from what the Orion server reports. The IP address is required. To use an existing polling engine. Repositories are generally added by the root account. enter the polling engine you want the agent to use.  4. Select the agent communication mode. Disable the SolarWinds Orion agent service before you create your gold master.  8. Enter 7 to save your changes. This happens when the monitored host is behind a NAT or proxy device. Follow the instructions in the Installation wizard. Whenever a new server is brought online using this image. copy and run the install command. In these cases. click Agent Settings > Download Agent Software. The agent software is downloaded from the repository and installed on the computer. select Use Connection Details from Polling Engine. In the terminal.  5. Deploy with a Gold Master Image Use a Gold Master Image when you want to maintain a master image of agent software that is copied when a new Windows server is provisioned. Use the host name and IP address of the polling engine that you can access from the client. This can be automated by an automation tool.  n For server-initiated communications.  3. enter your agent communication port number. Click Settings > All Settings in the menu bar.  2. Under Product Specific Settings. select Enter Connection Details Manually.  11.  8. and save the file.ZIP. and then select a polling engine from the list. The Orion repository The SolarWinds Orion repository is available when you install any SolarWinds Orion platform product running on version 2016. Configure the agent communication mode and polling engine information.  9. Extract the contents of the ZIP file. and then start it on the remote computer when the gold master is cloned. and then enter the host name and IP address.2 or later.  a. the agent will already be installed. 162 . To manually enter the polling engine IP address.  b. type service swiagentd init. After the repository is registered with the computer. and click Next. and double-click setup.

 5.  5. Download the installation files  1. take the following steps to enable agent communication with your Orion server. 163 .Enable server-initiated communication on deployed agents If you are deploying a server-initiated agent.  6. and click Next. Click Settings > All Settings in the menu bar. For more information. Click Add Agent > Connect to a previously installed agent > Next.  3. and publish the package. This method contains four parts you must perform in order: download the installation files.  6.  1. Enter the IP address of the node where the agent is deployed. see Mass deploy an agent on Windows. Click Windows. Download and save the MSI and MST files to a location on your Patch Manager server. and click Server-initiated communication. Deploy an agent with Patch Manager You can only perform this deployment method if you have successfully configured Patch Manager to push software in your environment. Record the Latest Version value under the MSI file download. and click Next. Enter a name for the agent. The default port is 17790. Click Submit.  2.  3. Under Product Specific Settings. Select the communication method and enter the required information.  4. build the package. Optional: Rename the SolarWinds agent files to SolarWinds Agent <version> for easier tracking. click Agent Settings > Download Agent Software.  4. Click Mass Deploy to Multiple Machines. Click Settings > All Settings in the menu bar. click Manage Agents.  2. and the port number for the agent. Under Node & Group Management. This is needed when creating a package in Patch Manager. add deployment rules.

Inc.  3.  4. From the SolarWinds. Inc.Build the package  1. enter the following general information for the package:  n Package Title: SolarWinds Orion Agent (version number) MSI  n Description: SolarWinds Orion Agent  n Classification: Tools  n Vendor: SolarWinds.  2. In the navigation pane. Packages. 164 . In the package information screen. Inc. expand Administration and Reporting > Software Publishing. Packages action pane. and then click SolarWinds. Launch SolarWinds Patch Manager. Click Next.  5.  n Product: Orion Agent (This must be entered the first time)  n Severity: None  n Impact: Normal  n Reboot Behavior: Can request reboot All other fields can be left empty. click New Package. This launches the Patch Manager Package Wizard.

Select Includes additional files with the package. and then select I already have the content for the package locally on my network. In the Package Content Editor.Add deployment rules  1. click Add Rule. and enter the following information:  3. Copy the GUID product code that you will use later.  2.msi). 165 . Use the one displayed in your environment. Click OK to save this rule. select the Package Type as a Microsoft Installer File (. Select Windows Version as the Rule Type. Click OK to close the Package Content Editor.  10. Select None for the Binary Language.  5. Click the browse icon and locate the MSI file for the SolarWinds Orion agent. click Yes.  7. and click the button to the right to open the Package Content Editor. On the Select Package window. On the Prerequisite Rules window.  8. The GUID product code is extracted from the MSI file and displayed for review. and browse to the MST File for the SolarWinds Orion agent. The GUID is detected from the installer.  9. click Add Files. To confirm that you want to add these files to the cache. The Download URL field will automatically populate. and click Next.  4.  6.

In the Command Line field. Registry Value: InstallDir  c. and leave all other fields empty. Comparison: Equal To. and click Next.  16.951. On the Applicability Rules window. Select Rule Type: Product Installed. Click Next to save. and then click Next. and select Not Rule. Click OK to save the rule. click Add Rule > Create MSI Rule. In the SolarWinds. and click OK. Publish the package  1. For the Rule Type. select the SolarWinds Orion Agent package that you created. Review the Summary Page.  18.0. enter: TRASNFORMS=(MST FILE NAME) Example: TRANSFORMS=SolarWinds_Agent_1.mst  12.  20. Click Next.  d.  14.  13. Version: Version number of the agent  19. Enter the following values:  a.5. Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SolarWinds\Agent  b. Enter the product code without the brackets. 11. and enter notes at the bottom. select File Version with Registry Value. When the file packaging and uploading completes. Inc. On the Installed Rules window. 166 . click OK to save the rule.  17. a Package Saved dialog displays.  15. Click Add Rule > Basic Rule. Packages view in Patch Manager.

NET 2. no web browser is installed with Windows Core. Requirements for manual agent deployment  n Agent-initiated communication: The poller must have a public IP address which is visible from the node with the agent installed.NET framework from www. and then click Next.0 layer. Consider transferring the necessary files with FTP or a flash drive. you may need to reboot the host server.  n Server-initiated communication: The node with the agent installed must have a public IP address. or choose a specific Windows Server Update Services (WSUS) server for publication. The agent can then be deployed to the host server and operate normally. Prerequisites to installing an agent on Windows Core  n Start WoW64.NET 2. Port 17778 must be open on the poller.  n Start the .  5.  4. Port 17790 must be open.  3. you must install the . You are notified when the package publishes. Accept the default selections. By default. Manually deploy an agent on Amazon Web Services You can manually deploy agents to a virtual machine using Remote Desktop Connection. The package for the SolarWinds Orion agent is packaged and published to your WSUS server. In the SolarWinds Orion Agent action pane. Click Finish to close the Publishing Wizard.5 and the latest Windows service pack and critical updates. Deploy on Windows Core Servers If you are installing the agent on a Windows Core Server.0 layer for WoW64.  2.NET Framework is installed.  n Start the .  n Download and install the .NET Framework 4. click Publish Packages. You can manually deploy the agent in one of two ways: 167 .microsoft.com. After the .

and click Next. and click Next.  10. Click Mass Deploy to Multiple Machines. Create an instance.  3. click Agent Settings > Download Agent Software. Right-click the instance and click Instance Settings > View/Change User Data. Click Windows.  2. Click Mass Deploy to Multiple Machines. Click Mass Deploy to Multiple Machines. and paste your PowerShell script under Advanced Details in the User Data text box. Automatically deploy an agent on Amazon Web Services  1. Automatically deploy an agent on Microsoft Azure  1. Download the MSI and MST files.  3. Select the As Text option. downloading and executing the agent. and click Next. click Agent Settings > Download Agent Software.  9. This script will run on each virtual machine when it is launched for the first time. Click Settings > All Settings in the menu bar. Click Windows.  4.mst" Deploy the agent manually using the interactive wizard Follow the instructions in Deploy the agent manually to a Windows computer. and click Next. Under Product Specific Settings.  2. Create a bucket and upload the MSI and MST files.  5.  4. Download the MSI and MST files. 168 .  6.  5. Click Windows. Click Settings > All Settings in the menu bar.  6. Run a command prompt as administrator from the context menu.  11. Log in to your Amazon Web Services S3 account. For instances that are already created.  7.  2. Click Settings > All Settings in the menu bar.  8. Enter the following command: msiexec /i "SolarWinds-Agent. You can perform the following steps through the API or AWS command line interface.  c. click Agent Settings > Download Agent Software. Stop the instance where you want to deploy the agent  b. and click Next. Under Product Specific Settings.  3. take the following steps:  a. Under Product Specific Settings. Create a PowerShell script to use on each virtual machine where you want to install the agent.  4. Paste your PowerShell script in the text box as Plain Text.Install through the command prompt  1. Log in to your Amazon Web Services account.  7.msi" TRANSFORMS="SolarWinds-Agent. and click Next.

Manage Agents toolbar options BUTTON DESCRIPTION Add Agent Go to the Add Agent page. This step can also be accomplished via the API or AWS command line interface. Upload the MSI and MST files to your Azure Blob Storage. where you can adjust the agent name and automatic 169 . Edit Go to the Edit Agent Settings page. or connect to a previously installed agent. downloading and executing the agent. Under Node & Group Management. Create a PowerShell script to use on each virtual machine where you want to install the agent. click Manage Agents. Agent management Check agent connection and deployment status on the Manage Agents page. where you can deploy the agent on a network. This script will run on each virtual machine when it is launched for the first time.  2. Click Settings > All Settings in the menu bar.  7. Add your PowerShell script to virtual machines manually on the last step of the Create a Virtual Machine wizard in the Azure management portal.  6. Download the MSI and MST files.  8.  1.  5.

plug- in. Agent Status Current status of the listed agent. Manage Manage the agent as a new node by navigating to the Add Node page with pre-configured as Node agent details. and plug-in version. This button is disabled by default. This button is disabled by default.  n Reconnect to passive agent: The server tries to re-establish the connection to the passive agent when the connection is lost and automatic reconnection fails. It is enabled when the installation of an agent requires a system reboot. Agent Status can be as follows: 170 .  n Reboot Agent Machine: Reboots the server that hosts the selected agent. COLUMN HEADER DESCRIPTION Agent/Node Name or IP address of the listed node. plug-in status. Manage Agents table columns The table on the Manage Agents page displays information on the status and connection of your agents.  n For Multiple Agents: From here.  n Retry agent installation: Attempts to install the agent in the event of a file transfer timeout due to network connectivity issues.  n The selected agent requires an update. connection status. Choose Displays a list of resources and statistics to monitor. This can also be used for connecting to an agent that was deleted but not uninstalled. It becomes enabled when:  n Automatic updates for the agent is disabled. More  n View installed agent plug-ins: Displays a dialog detailing the node the agent is Actions deployed on. BUTTON DESCRIPTION Settings updating. plug-in status.  n View installed plug-ins report: Generates a report detailing node status. automatic update enabled. the agent status. and plug-in version. This is only available for agents that are Resources deployed on nodes. Delete Remotely uninstall the agent. connection status. You can choose items on the nodes to monitor.  n Update: Updates the agent software to the latest version available. Orion discovers available resources on the agents you have selected using Network Sonar Discovery. agent status. agent DNS name.  n For a Single Agent: Go to the List Resources page to choose items on the node you want to monitor. agent version.

 n Service not Responding: The agent management service is running.  n Unknown: The agent management service is not running.  n Deployment Pending: An agent deployment is going to start. but has not started.  n Deployment in Progress: The agent is being deployed to the target node.  n Deployment Failed: Agent deployment failed. It may be temporarily offline or there may be some other issue. Connection status can be as follows:  n Connected/OK: The agent is connected. Mode Agent communication type:  n Agent-initiated: The agent initiates the connection to the agent management system.  n Update in Progress: The agent is currently being updated.  n Server-initiated: The agent listens on its designated port for connections from the Orion server. Connection Status Current connection status of the listed agent. Registered On Date when the agent was added to the agent management system.  n Reboot in Progress: The agent is currently being rebooted.  n Waiting for Connection: The agent was approved. This is helpful in determining which agents should be updated.  n Invalid Response: The status displayed if the agent responds in an unexpected manner. 171 . but the agent is not connected. Once reboot is complete.  n Update Available: The agent version is older than the version on the server and should be updated.COLUMN HEADER DESCRIPTION  n Connected/OK: Everything is working. Version Version of the agent software.  n Unknown: The agent is connected but no communication is received. the agent should finish installation of plugins.  n Reboot Required: The agent needs to be rebooted in order to finish the installation of plug-ins. but has yet to connect to the Orion server.  n Plugin Update Pending: A plugin on the agent has an older version than the one that is on the server and should be updated.  n Reboot Failed: The agent cannot be rebooted.

For example.1 x64 is the installed OS version for this SUSE distribution. opensuse 42.  n Troubleshooting:  n Log level: the amount of detail saved to the log. Track your polling method If nodes are using different polling methods. Name opensuse displays for an installed SUSE distribution. Agent . Agent .  n Allow automatic agent updates: choose whether the Orion server can update the agent software to the latest version available. For example.  3. the table includes additional columns of data.When viewing Linux-based nodes monitored by Orion agents for Linux.  1. These columns include the following: COLUMN HEADER DESCRIPTION Agent . For example. Under Node & Group Management. suse displays as the common installer for all 64-bit SUSE distributions.Package Displays the installation package name and version for the distribution. The installer Operating System package version may differ from the installed Operating System version. suse 10. There are several methods you can use to identify the polling method of nodes: 172 . Select an agent. you may want to keep track of the polling method of each node to troubleshoot issues more easily.  n Communication type: displays whether the agent uses server-initiated or agent-initiated communication. Edit agent settings Editing the configuration of an agent may be necessary if you experience problems and want to collect diagnostics. Send the zip file to our support team if requested. Click Settings > All Settings in the menu bar.  2.OS Distro Displays the general distribution name of the Operating System. For example.Operating Displays the installed Operating System name and version. This is the name of the Distro Name common installer for Linux distributions.  n Diagnostics: click Collect new diagnostics. and click Edit Settings. click Manage Agents. Agent settings and troubleshooting options  n Agent Name: change the display name displayed in Orion. and then Download to save to your local disk.Package Displays the distribution name of the installer package. This value will differ System from the package installer version. Agent .0 x64 is the package version for this SUSE distribution.

expand a node tree and click a node to go to the Node Details page. navigate to Reports > All Reports.  3.  3. locate the Polling Method. expand an application tree and click an application to go to the Application Details page. click Manage Agents.  2. click My Dashboards > Home. Select an agent.  n Node Details page: view individually  n Application Details page: view individually  n Manage Nodes page: view as a list  n Create a report to identify agent usage Identify the polling method from the Node Details page  1. Create a report to identify agent usage  1. All applications default to agent-based polling. In the Polling Details resource. Under Node & Group Management. From the Orion Web Console. Identify the polling method from the Application Details page  1. Click Agent Inventory to view the report.  3. Use this option to override the default behavior. 173 . In the All Nodes resource.  3. and click More Actions > View installed agent plug-ins. Click Settings > All Settings in the menu bar. From the web console. Under Node & Group Management. Identify the polling method from the Manage Nodes page  1. View the status of agent plug-ins  1. Enter agent in the Search box.  3. From the web console. In the Application Details resource. click My Dashboards > Applications. Click Settings > All Settings in the menu bar. In the All Applications resource.  2. click Management > Edit Application Monitor.  2. If not already visible. click Manage Nodes.  2.  2. Expand the Advanced heading to locate the Preferred Polling Method. even when no agent is installed. add the Polling Method field by clicking >> in the upper-right of the table.  4.

you may need to check your purchased products or manually update your agent. Edit agent settings once deployed You can modify settings such as the communication mode or to which polling engine the agent sends information by modifying the agent on the computer.  5. you must set a shared secret. When the Orion server connects to the agent. Installation Pending The plug-in is waiting to be deployed. Unknown The status is unknown due to networking interruptions. In Progress The plug-in is either being installed or uninstalled. You may need to su to an account with root- level privileges. Open Orion Agent Settings in the Control Panel. working correctly. STATUS MEANING The plug-in is installed The plug-in is installed. If the agent loses connectivity to the Orion server. Linux-based computers  1. it verifies the secret to connect. type service swiagentd init 174 . or is unable to connect after being manually installed. Select the Agent Communication Mode. If you think a plug-in should be available and cannot find it in the list. In the terminal. Edit the Connection Settings.  3.  2. you can configure its settings directly on the computer you are monitoring. It is normal for agents to have different plug-ins.  4. communication problems with the agent. Windows computers  1. This enables the agent to reconnect to the Orion server. Log on to the computer with the agent installed on it.  2. or because some other process on the remote host has interrupted the installation process. The Agent Shared Secret is provided for security. Orion deploys and removes plug-ins as needed when you enable and disable features. Click OK to save your changes. Log on to the computer with the agent installed on it with an administrator account. It may be waiting for the computer it is installed on to reboot. and communicating with no problems. When you install the agent. or because the plug-in is no longer installed. It may take a few minutes before the status changes. New plug-ins and updates to existing plug-ins are installed when an agent is updated. Error The plug-in may have installed incorrectly or failed to load.

Select Allow automatic agent updates. Configure the agent communication mode and poller information.  3.  8. click Manage Agents. and click Next.  5. Disabling this option requires you to upgrade agents manually after upgrading your SolarWinds products and modules. Select the agent from the Agent list. You should confirm the agent communication mode before connecting.  4. The steps are different depending on the agent communication mode.  7. Connect to an agent using server-initiated communication If the communication mode is server-initiated (passive). Click Submit. Expand Advanced to change the port number.  6. Expand Advanced to change the proxy. click Manage Agents.  4. and select Agent-initiated communication. Click Submit.  3.  1.  7. Enter 7 to save your changes. When the connection is successful.  9.  8. Click Add Agent. and click Next. Enter the name of the agent you want to connect to.  3.  5. and select Server-initiated communication. assign the agent to a different poller. When the connection is successful. Connect to or register a previously installed agent You may need to connect and register an agent manually when agents are configured with server-initiated communication or when Allow Automatic Agent Registration is not enabled.  4. the agent displays in the agent list on the Manage Agents page. Click Connect to a previously installed agent. Disabling this option requires you to upgrade agents manually after upgrading your SolarWinds products and modules. a shared secret was required during installation. Click Settings > All Settings in the menu bar. 175 . the agent displays in the agent list on the Manage Agents page. Under Node & Group Management. Click Settings > All Settings in the menu bar. Select Allow automatic agent updates. Click Add Agent. Enter the name of the agent you want to connect to. Connect to an agent using agent-initiated communication  1. Under Node & Group Management.  9. This secret must be entered again here. or use a proxy to connect to the agent.  2.  2.  6. Click Connect to a previously installed agent. Enter the IP address or hostname where the agent is installed.

dl l. Log in to the computer with the deployed agent.  4. No change to the agent firewall is required. Log in to the host where the agent is installed. Save the file. 176 . Select an agent communication mode. Change the port number on the following line: <agentManagementServiceConfiguration messagingPort="17778" />  3. Start the Orion Agent Settings application in the Control Panel. the port number is set automatically.  n Server-initiated communication: The agent waits for requests from the server on a specified port. Manually change the port on agents deployed on Windows  1.Change the agent communication mode You can change how the agent communicates with the Orion server.  n Agent-initiated communication: The agent initiates communication with the Orion server on port 17778. you must download a new MST file from the server after you change the port number.ServiceCore.  n If you used the MST file for mass deployment. edit the following configuration file using a text editor: C:\Program Files (x86) \SolarWinds\Orion\AgentManagement\SolarWinds.  3. You can select server-initiated or agent-initiated communication. No change to the Orion server firewall is required.  n If you deployed the agent from the server.  3.  1.  2. Enter a new port number.  n If you installed the agent manually.  2. Change the agent port Agents deployed on Windows  1. you can change the port number during installation through the wizard in the web console. On the computer with the deployed agent. Log on to the computer with the agent installed on it. You may need to su to an account with root- level privileges. Restart the SolarWinds Orion Module Engine service. This port must be open on the Orion server firewall so the agent can connect. In the terminal.  2. This port must be open on the firewall of the agent computer so the Orion server can connect.  4. Open Orion Agent Settings in the Control Panel.AgentManagement. and click OK. Click OK. Agents deployed on Linux-based computers  1.config  2. type service swiagentd init.

 3.  4.  n Manually change the Orion server IP address the agent uses using the Control Panel. Agent migrations Depending on migration needs for new servers. Upgrade agents manually If you do not enable the Allow automatic agent updates option in AgentUp Settings. See the following information as needed:  n Migrate agents from one Orion instance to another  n Migrate certificates to a new server  n Deploy an agent to a monitored node  n Connect to or register a previously installed agent  n Edit agent settings once deployed  n Use a group policy to migrate agents  n Troubleshooting agent deployment Migrate agents from one Orion instance to another When you migrate your SolarWinds Orion server to a different computer. you may need to modify your agents so they communicate with the new server.  3. you may need to complete migration steps. 177 . you must migrate them to the new server.  4. If any of the following have changed. Agents requiring upgrades display Update Required in the Agent Status column.  n Use the Group Policy Administrative template to redirect existing agents to the new Orion server. Select all agents needing updates and click More Actions > Update. Under Product Specific Settings. Click Settings > All Settings in the menu bar. For details on product upgrades.  1. click Agent Settings. Enter 7 to save your changes. you must modify your agents:  n IP address  n DNS  n Database Modify agents to point to the new server in one of the following ways:  n Re-deploy the agents from the Orion server. see the SolarWinds Upgrade Guide.  2. Choose option 3 and enter the new port number. you must manually upgrade the agents during a product upgrade. If you have not cloned your certificates. This requires endpoints be joined to an active directory domain. The agents upgrade in the background.

Migrate certificates to a new server

SolarWinds encrypts your sensitive data with a security certificate stored on the original SolarWinds
server. To grant a new server access to this encrypted data, you must copy the original security certificate
to the new server.

If you do not replicate the original certificate, the new server cannot access any credentials used by
agents.

Export the credential from the original server

 1. Open the Certificates MMC snap-in.
 2. Click Certificates (Local Computer) > Personal > Certificates group, and then export the SolarWinds
Agent Provision certificate.
 3. Export the private key.  
 4. When prompted, type and confirm a password for the private key, and complete the wizard.

The certificate is saved with a .pfx file name extension.

Import the certificate to the new server

 1. Copy the .pfx certificate file to the new server.
 2. Open the Certificates MMC snap-in.
 3. Click Certificates (Local Computer) > Personal > Certificates.
 4. If there is a SolarWinds SAM Engine item in the list, delete the SolarWinds Agent Provision certificate.
 5. Select the Certificates (Local Computer) > Personal > Certificates node, and import the .pfx certificate
file.
 6. When prompted, enter the password for the private key, and select Mark this key as exportable.
 7. Select Place all certificates in the following store, and then select Personal as the Certificate Store.
 8. Complete the wizard.

Deploy an agent to a monitored node

Select this method of deployment to deploy agents from the Orion server. This method is usually
performed when you need to install the agent on multiple computers or if the computers are already
monitored by the Orion server.

The Orion server must be able to communicate with the client computers. To monitor Linux-based
computers, TCP port 22 (outbound) must be open on the Orion server or additional polling engine
and open (inbound) on the computer you want to monitor.

 1. Click Settings > All Settings in the menu bar.
 2. Under Node & Group Management, click Manage Agents.
 3. Click Add Agent.

178

 4. Select Deploy the agent on my network.
 5. On the Deploy Agent on Network page, choose where you want to install the agent by selecting
existing nodes from the list, or entering the IP address or host name of a node that has not been
managed.

The IP address field does not accept ranges.

 6. Click Next.
 7. Select a node and click Assign Credentials.

 n These credentials are only used to connect to the remote computer and install the
agent software. After the agent is deployed, the credentials may change with no impact
to the deployed agent.
 n The credentials must have administrator or root-level privileges. On Linux-based
computers you can connect with one credential set and then use another credential to
use su or sudo for package installation. Most Linux distributions require the user's
password when using sudo. Other distributions, such as SUSE, may require the root
password. Depending on your Linux distribution, enter the required credential for the
Include Credentials with Elevated Privileges to install the package.
 n You can assign credentials to multiple locations or nodes by selecting multiple entries.
 8. Click Deploy Agent.

When the connection is successful, the agent displays in the agent list on the Manage Agents page.

Connect to or register a previously installed agent

You may need to connect and register an agent manually when agents are configured with server-initiated
communication or when Allow Automatic Agent Registration is not enabled. The steps are different
depending on the agent communication mode. You should confirm the agent communication mode
before connecting.

Connect to an agent using agent-initiated communication

 1. Click Settings > All Settings in the menu bar.
 2. Under Node & Group Management, click Manage Agents.
 3. Click Add Agent.
 4. Click Connect to a previously installed agent, and click Next.
 5. Enter the name of the agent you want to connect to, and select Agent-initiated communication.
 6. Select the agent from the Agent list.
 7. Expand Advanced to change the proxy.
 8. Select Allow automatic agent updates.

Disabling this option requires you to upgrade agents manually after upgrading your
SolarWinds products and modules.

 9. Click Submit.
When the connection is successful, the agent displays in the agent list on the Manage Agents page.

179

Connect to an agent using server-initiated communication

If the communication mode is server-initiated (passive), a shared secret was required during installation.
This secret must be entered again here.

 1. Click Settings > All Settings in the menu bar.
 2. Under Node & Group Management, click Manage Agents.
 3. Click Add Agent.
 4. Click Connect to a previously installed agent, and click Next.
 5. Enter the name of the agent you want to connect to, and select Server-initiated communication.
 6. Enter the IP address or hostname where the agent is installed.
 7. Expand Advanced to change the port number, assign the agent to a different poller, or use a proxy to
connect to the agent.
 8. Select Allow automatic agent updates.

Disabling this option requires you to upgrade agents manually after upgrading your
SolarWinds products and modules.

 9. Click Submit.
When the connection is successful, the agent displays in the agent list on the Manage Agents page.

Edit agent settings once deployed

You can modify settings such as the communication mode or to which polling engine the agent sends
information by modifying the agent on the computer.

If the agent loses connectivity to the Orion server, or is unable to connect after being manually installed,
you can configure its settings directly on the computer you are monitoring. This enables the agent to
reconnect to the Orion server.

Windows computers

 1. Log on to the computer with the agent installed on it with an administrator account.
 2. Open Orion Agent Settings in the Control Panel.
 3. Select the Agent Communication Mode.
 4. Edit the Connection Settings.

The Agent Shared Secret is provided for security. When you install the agent, you must set a
shared secret. When the Orion server connects to the agent, it verifies the secret to connect.

 5. Click OK to save your changes.

Linux-based computers

 1. Log on to the computer with the agent installed on it. You may need to su to an account with root-
level privileges.
 2. In the terminal, type service swiagentd init

180

 3. Configure the agent communication mode and poller information.
 4. Enter 7 to save your changes.

Use a group policy to migrate agents

You can use a group policy to change the connection settings of the agents to the new instance of your
Orion server. Use this method if you have a few agents deployed.

 1. After you migrate your server, create a domain-based Group Policy Object (GPO). You can use this
Administrative Template (.admx) file on THWACK.
 2. Copy the Administrative Template to the appropriate directory in the Central Store, and create the
GPO within the Group Policy Management Console. For more information, search for "Editing
Domain-Based GPOs Using ADMX Files" at http://technet.microsoft.com.
 3. Ensure the group policy will apply to the computer objects where the agent is installed. This can be
done by linking to the appropriate Organizational Unit (OU) or filtering to specific computer objects
or groups.
 4. Ensure the policy is updated on the target computers.
 a. Open a command prompt in the Administrator context. (Right-click cmd.exe and select, Run
as Administrator.)
 b. Enter gpupdate /force and then press Enter.

The following registry key is created when the GPO is applied:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\SolarWinds\Agent

You can create your own Group Policy Object by editing the following registry key and providing the
correct values: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\SolarWinds\Agent.

 

REGISTRY VALUE N AME REGISTRY TYPE VALUE DEFAULT

TargetHost REG_SZ Enter the name of the Orion server  
to which the agent reports

TargetIp REG_SZ Enter the IP address of the Orion  
server to which the agent reports

TargetPort REG_DWORD The port used for agent 17778
communication

Troubleshooting agent deployment

Agent is not able to connect to the Orion server

 n Ensure that you can ping the Orion server from the client machine.
 n Ensure that port 17778 is open on the Orion server and that the client machine can connect to it.
 n Ensure that you are using the correct Orion administrator credentials.

181

Credential test for deployment fails

 n Ensure that the account can access and create a folder at the following location: \\<hostname_or_
ip>\admin$\temp
 n Ensure that Remote Procedure Call (RPC), a Windows service, is running
 n Ensure the required ports are open
 n If you are using a domain account, use the complete name when entering credentials. For example:
domain\username

Agent deployment fails

 n Ensure there are no other installations in progress. For example, Windows updates prevent other
installations from finishing successfully. If this is the case, retry installing the agent after the other
installations complete.
 n On the target machine, check if the SolarWinds Agent service is installed and running. If it is, the
agent may be experiencing connectivity issues with the Orion server. Ping the Orion server from the
client machine, and ensure that port 17778 is open on the Orion server. Ensure the client machine
can connect to the Orion server web console.
 n Install the agent manually on the target machine, and set the permissions correctly.

Agent deployment can fail if a previous installation or upgrade is awaiting a reboot. To resolve
this issue, you must reboot the server before the agent installation can proceed.

 n Install the agent manually on the target machine, ensuring that permissions are set correctly.
 n If a host name or Fully Qualified Domain Name was used, ensure that it can be resolved from the
client computer.
 n If the Orion server or the additional poller is behind a NAT, ensure that the IP address specified
when creating the MST file is the correctly routed IP address the client uses to access the Orion
server.

Monitor Syslog messages
Syslog messages are received by the SolarWinds Syslog Service, which listens for incoming messages on
UDP port 514. Received messages are decoded and stored in the SolarWinds Orion database. The
SolarWinds Syslog Service can handle large numbers of simultaneously incoming Syslog messages from all
your monitored devices.

A SolarWinds installation can process approximately 1 million Syslog messages per hour, which is
about 300 Syslog messages per second. You can process more by increasing your hardware
requirements over the minimum requirements.

You can view Syslog messages in the Orion Web Console or in the Syslog Viewer application.

Before you begin
 n Confirm that your network devices are configured to send Syslog messages to the Orion server IP
address. For proper configuration of network devices, refer to the documentation supplied by the

182

device vendor.
 n Ensure UDP port 514 is open for IPv4 and IPv6.
 n The message must be formatted according to the Request for Comments (RFC) requirements.
 n If a long message is split into smaller parts, these parts should be formatted to not be skipped.

SolarWinds recommends setting up Enable RFC Relay in the service to true to allow the
service to restructure the message by adding the default facility, severity, or date.

Configure the SolarWinds Orion server to use the correct syslog port
By default, SolarWinds Syslog Service listens for syslog messages on port 514 (UDP). If your devices use a
different port for sending syslog messages, consider reconfiguring the port on devices, or change the port
on which the service listens.

 1. Log in to the Orion Web Console as an administrator.
 2. Go to Advanced Configuration settings. Copy /Admin/AdvancedConfiguration/Global.aspx,
and paste it into your browser address bar, after /Orion.
The address in the address bar should look as follows:
<your product server>/Orion/Admin/AdvancedConfiguration/Global.aspx
 3. On the Global tab, scroll down to SyslogService.SyslogSettings, and enter the UDP port
number in the UDPListenPort entry.
 4. Click Save.
 5. Restart the syslog service from the notification bar or the Orion Service Manager.

Syslog message priorities
At the beginning of each Syslog message, there is a priority value. The priority value is calculated using the
following formula:

Priority = Facility * 8 + Severity

Syslog facilities

The facility value indicates which machine process created the message. The Syslog protocol was originally
written on BSD Unix, so Facilities reflect the names of UNIX processes and daemons.

If you are receiving messages from a UNIX system, consider using the User Facility as your first
choice. Local0 through Local7 are not used by UNIX and are traditionally used by networking
equipment. Cisco routers, for example, use Local6 or Local7.

N UMBER SOURCE N UMBER SOURCE

0 kernel messages 12 NTP subsystem

1 user-level messages 13 log audit

2 mail system 14 log  alert

183

N UMBER SOURCE N UMBER SOURCE

3 system daemons 15 clock daemon

4 security/authorization messages 16 local use 0 (local0)

5 messages generated internally by Syslog 17 local use 1 (local1)

6 line printer subsystem 18 local use 2 (local2)

7 network news subsystem 19 local use 2 (local3)

8 UUCP subsystem 20 local use 2 (local4)

9 clock daemon 21 local use 2 (local5)

10 security/authorization messages 22 local use 2 (local6)

11 FTP daemon 23 local use 2 (local7)

Syslog severities

The following table provides a list of Syslog severity levels with descriptions and suggested actions for
each.

N UMBER SEVERITY SUGGESTED ACTIONS

0 Emergency A "panic" condition affecting multiple applications, servers, or sites. System is
unusable. Notify all technical staff on call.

1 Alert A condition requiring immediate correction, for example, the loss of a backup
ISP connection. Notify staff who can fix the problem.

2 Critical A condition requiring immediate correction or indicating a failure in a
primary system, for example, a loss of a primary ISP connection. Fix CRITICAL
issues before ALERT-level problems.

3 Error Non-urgent failures. Notify developers or administrators as errors must be
resolved within a given time.

4 Warning Warning messages are not errors, but they indicate that an error will occur if
required action is not taken. An example is a file system that is 85% full. Each
item must be resolved within a given time.

5 Notice Events that are unusual but are not error conditions. These items might be
summarized in an email to developers or administrators to spot potential
problems. No immediate action is required.

6 Informational Normal operational messages. These may be harvested for network
maintenance functions like reporting and throughput measurement. No
action is required.

184

N UMBER SEVERITY SUGGESTED ACTIONS

7 Debug Information useful to developers for debugging an application. This
information is not useful during operations.

View Syslog messages in the Orion Web Console
The Orion Web Console provides both syslog-specific resources and a syslog view with a table of syslog
messages received by your Orion server.

The Syslog view displays a list of all the syslog messages generated by monitored network devices. The
messages are listed by time of transmission, with the most recent at the top of the list.

 1. Log in to the Orion Web Console, and click Alerts & Activity > Syslogs in the menu bar.
 2. To filter syslog messages so that only messages relevant for specific devices are displayed:
 n To view messages for a specific syslog-enabled network object, select it in the Network Object
list.
Only objects that have sent a syslog message to the Orion server will be listed in this
field.

 n To view messages for a specific device, provide the IP address in the IP Address field.
 n To view messages for a specific device type, select it in the Type of Device list.
 n To view messages for a specific vendor, select the vendor in the Vendors list.
 3. To select which syslog messages should be displayed:
 n To view only messages with a severity, select the severity.
 n To view messages for a facility, select the facility.
 n To view messages of a type, type the string into the Message Type field.
 n To view only messages containing a pattern, provide the string in the Message Pattern field.
You can use the following wildcards:
Asterisk (*)
Use * before or after the pattern string if the provided pattern is not the
beginning, the end or the full message.
Underscore (_)
Use _ as a placeholder for one character.

 n To view syslog messages from a specific period of time, select either a period of time or enter
custom Beginning and Ending Date/Times.
 n Type the number of syslog messages you want to view into Number of Displayed Messages.
 n To view cleared and acknowledged syslog messages, select Show Cleared Messages.
 4. Click Refresh to update the syslog messages list with your settings.

Syslog messages matching the selected criteria display in a list beneath the search area.

Click Hide or Show in the top-right corner of the view to remove or restore the Syslog messages search
criteria area.

Click the Hostname or Message to open the Device Details view for the device.

185

Clear Syslog messages in the Orion Web Console
 1. Log in to the Orion Web Console.
 2. Click Alerts & Activity > Syslogs in the menu bar.
 3. Define what you want to see in the Syslog messages table, and click Refresh.
 4. Select the messages you want to acknowledge, and click Clear Selected Messages.

The messages are cleared. You can see cleared messages when you select the Show Cleared Messages
box.

View and clear Syslog messages in the Syslog Viewer
Syslog Viewer collects Syslog messages from your network and presents them in a readily reviewable and
searchable list so that you can easily monitor your network. Clear messages you have already read and
acted upon.

You must be able to log in to the computer running your Orion server.

 1. Click Start > All Programs > SolarWinds Orion > Syslog and SNMP Traps > Syslog Viewer.
 2. Click View > Current Messages.
 3. Clear read messages:
 n Right-click any message, and select Acknowledge Selected.
 n Add an Acknowledged column to the Syslog Viewer, and select the messages that you want to
acknowledge.

Selected messages are acknowledged now.

Search for Syslog messages in the Syslog Viewer
In the Syslog Viewer, you can search through collected Syslog messages and format search results.

 1. Click View > Search Messages.
 2. Enter the search criteria.
 3. Click Search Database.
 4. To group messages for easier navigation, select the type of grouping from the Grouping list.

You can acknowledge messages both in the search results and in the Current Messages view.
See Define the number of messages displayed, message retention, and the displayed
columns in the Syslog Viewer.
 5. To limit the number of displayed message, enter or select a number in the Maximum Number of
Messages to Display field.
 6. To view messages that meet your search criteria as they arrive, select a number for the Auto Refresh
Every number of seconds field.

Auto Refresh is only available when you are viewing current messages. The Date/Time Range
must be set to Today, Last 24 Hours, Last 2 Hours, or Last Hour.

186

Automatically refresh the current messages view by selecting the option. select the Message Parsing tab. Click Alerts/Filter Rules. This setting significantly affects the database size and performance.  3. Clearing Syslog messages is easier if you add the Acknowledged column to your view.Define the number of messages displayed. Click the Displayed Columns tab.  8. Click the General tab in the Syslog Server Settings window. If you do not expect to use the Syslog Viewer as your primary viewer for Syslog messages. Click Start > All Programs > SolarWinds Orion > Syslog and SNMP Traps > Syslog Viewer. 187 .  1. message retention.  4.  2. Trigger alerts when receiving specific Syslog messages You must be able to log in to the computer running your Orion server.  9. select Word Wrap Long Messages.  3. To wrap Syslog message text in the Current Messages view.  4.  5. Click Add New Rule to create a rule.  2.  6. Removing the added data from each record helps you reduce the size of your SolarWinds Orion database. Click File > Settings. Click File > Settings. and select what should be removed:  n Remove embedded Date/Time from Syslog Messages  n Remove Message Type from Syslog Messages  n Remove Domain Name from DNS Lookups. Adjust Retain Syslog Messages for How Many Days to set the length of time Syslog messages should stay in the database.  1.  10. and setting the refresh rate with the middle slider. or edit a selected rule.  7. Click Start > All Programs > SolarWinds Orion > Syslog and SNMP Traps > Syslog Viewer. Adjust the Maximum Number of Messages to Display in Current Messages view slider to set the number of messages you want to display. Use the arrow keys to select and order the fields of information you want to see in the Current Messages view. and the displayed columns in the Syslog Viewer You must be able to log in to the computer running your Orion server.

 7.  5. All alerts suppressed during the time period are discarded. complete the following steps:  a.  b.  10. Syslog rules may not be applied to nodes in an unmanaged state. click the DNS Hostname tab. select Use Regular Expressions in this Rule. and click Delete Action. and enter a DNS Hostname Pattern. To delete an action. Select the servers from the Apply this Rule To list. By default. select the action. Enter the IP addresses or subnets to which this rule applies in the Source IP Addresses area.  f. from top to bottom. all message severities and facilities are selected. select the Time of Day tab. To suppress alert actions until a specified number of messages arrive that match the rule.  e. select Enable Time of Day Checking. Configure Syslog alert actions on the Alert Actions tab:  a. When the time period expires. Click OK to save all changes and return to Syslog Viewer Settings. Configure the action. When Suspend Further Alert Actions For is selected. and select the days of the week on which to apply the rule.  8. and select Define a Trigger Threshold for this Rule.  9. Messages received outside the specified time frame will not trigger alerts.  b.  c. On the General tab.  12. To edit an action for the rule. Enter option values. Actions are processed in the order listed. enter the time period. To use regular expressions. To limit the rule only to specific message types or texts within a Syslog message.  d. 188 . complete the following procedure:  a. To limit the rule only to messages from specific hosts.  6. click Add New Action. and click Edit Selected Action. Provide or edit the Rule Name. or host name patterns. Use the arrow buttons to arrange the order in which the rules are applied.  b. and enter rules for Message Type Pattern and Syslog Message Pattern. Select the Trigger Threshold tab. from top to bottom. To apply the rule only during a specific period of time. Use the arrow buttons to set the order in which actions are performed. Syslog alerts use a unique set of variables. To apply specific severity or facility types. domains. go to the Severity / Facility tab. only new alerts are sent.  c. go to the Message tab. and select the severity and facility types.  d.  11. Rules are processed in the order they appear. To create an action for the rule. Select Enabled. select the action. The DNS Hostname Pattern rule is case-sensitive. alert actions are not sent until the specified amount of time has expired. Enabling Time of Day checking creates more overhead for the CPU.

Monitor SNMP traps If you monitor a large number of devices. You can set up the SNMP Trap Server. The following procedure assumes you are editing a Forward the Syslog Message alert action. Additionally. Higher capacity can only be achieved with significant hardware improvements over minimum SolarWinds requirements. see Trigger alerts when receiving specific Syslog messages.0 or later installed on your Orion server. To keep the original IP address of the syslog source device. select Spoof Network Packet.Forward syslog messages The Syslog message forwarding action allows you to forward received syslog messages. you can forward syslog messages as spoofed network packets. which listens for incoming trap messages on UDP port 162. To designate a specific IP address or hostname as the Syslog source. filter. displays. By default.  b. and select the Network Adapter. select Use a Fixed Source IP Address. The SolarWinds Trap Service can receive and process SNMP traps from any type of monitored network device. Click OK to complete the configuration. Specify what IP address should be used for the source device in the syslog message. For more information. to view. The default is UDP port 514. You can monitor SNMP traps with SolarWinds NPM or SolarWinds SAM. A SolarWinds installation can process approximately 500 traps per second.  a. and the source IP of the device in the syslog message used in the alert action. and each managed device can notify it about any issues by sending a trap message.  3. select Retain the Original Source Address of the Message. port for sending the syslog message. Provide the UDP Port you are using for Syslog messaging.  4. and search for traps. and provide the IP address or hostname. The Trap Viewer application allows you to configure trap-specific alerts. where each device may have many connected objects of its own. select Retain the Original Source Address of the Message. and can handle large numbers of simultaneously incoming traps.  1. requesting information from each device is impractical. if you have WinPCap version 3. the device IP is replaced by the Orion server IP address. You can view SNMP traps either in the Orion Web Console or in the Trap Viewer application. 189 .  2. SNMP traps are received by the SolarWinds Trap Service. You have defined the destination. Provide the hostname or IP address of the destination to which you want to forward the received syslog message. and then decodes. and stores the messages in the SolarWinds Orion database.

select the time period from the Time Period menu. Click View > Current Traps. noauth. select the device type in the Type of Device field.  2. select the string in the Community String field. Click Refresh to update the Traps view with your new settings. View current traps in the Trap Viewer The Trap Viewer is an application which allows you to view. Click Start > All Programs > SolarWinds Orion > Syslog and SNMP Traps > Trap Viewer. or configure filters and alerts. Click Alerts & Activity > Traps in the menu bar.  n To view traps for certain device type.  5. confirm that the same authentication type (auth. or priv) is configured for both polling and traps. select the type in the Trap Type field.Before you begin  n Configure devices to send SNMP traps to the IP address assigned to the Orion server. Log in the Orion Web Console. specify the device:  n To display only traps for a device. 190 .  n To view only traps with a designated community string. View SNMP traps in the Orion Web Console  1. Search for traps in the Trap Viewer You can search collected trap messages and format the search results list in the Trap Viewer. To display only traps relevant for a specific device. Configure the Trap Viewer by clicking and dragging columns to order the presentation of trap characteristics.  6. refer to the documentation supplied by the vendor of your devices.  4. You must be able to log in to the computer running your Orion server.  4.  3. Click a column header to order listed traps by the selected trap characteristic. select the device in the Network Object field. For more information about proper configuration. search for traps. type the IP Address in the Source IP Address field.  3.  n When you use SNMPv3 for polling a device and receiving traps from it.  2.  n To view only traps from a specific period of time. Confirm the number of traps displayed in the Number of Displayed Traps field.  n To view only traps originating from a specific IP address. The current traps are now displayed according to your settings. Define what traps you want to view:  n To view only traps of a designated type.  1.  n Make sure the UDP port 162 is open for IPv4 and IPv6.

If you want to Automatically Refresh the Current Traps View. select the option.  5. Click File > Settings.  4.  2. 191 . use the arrow keys to select and order the fields of information you want to see in the Current Traps view. To group messages for easier navigation. To hide the search criteria pane. Selecting this option can slightly reduce the size of your database. select a number for the Auto Refresh Every number seconds field. On the General tab.  3. To limit the number of displayed messages. or Last Hour. if you want to refresh the traps view. enter or select a number in the Maximum number of messages to display field. You can now see the traps according to your settings. and click Search Database. To view messages that meet your search criteria as they arrive. and configure actions that trigger when received trap messages match defined rules. Define how many traps to display.  b. select Remove Domain Name from DNS Lookups on the Message Parsing tab. Position the top slider to set the Maximum Number of Traps to Display in Current Traps View. Last 24 Hours. trap retention. With the exception of the asterisk (*) and underscore (_) wildcards.  6.  2. Last 2 Hours. On the Displayed Columns tab.  c.  1. The Date / Time Range must be set to Today. Click Start > All Programs > SolarWinds Orion > Syslog and SNMP Traps > Trap Viewer.  7.  3. Trap rules are not applied to unmanaged nodes.  5. and the information displayed in the Trap Viewer  1. Position the Retain Trap Messages For How Many Days slider to set the length of time that traps remain in the database. Configure Trap Viewer filters and alerts In the Trap Viewer. configure the Trap server settings:  a. Click Start > All Programs > SolarWinds Orion > Syslog and SNMP Traps > Trap Viewer. you can filter trap messages. toggle the pane open and closed by clicking the double up arrows in the top right of the page. SolarWinds recommends against using non-alphanumeric characters in filter definitions. If you do not need the domain name in your trap messages. and position the middle slider to set the refresh rate. Auto Refresh is only available when you are viewing current messages. Enter search criteria. Click View > Search Traps.  4. select the type of grouping from the Grouping list.

Apply the rule to specific messages. and enter a Trap Details Pattern to apply the rule based on the Trap Details field.  1.  n Click Browse (…) to insert conditions. Select the servers from the Apply This Rule To list.  12. Use the arrow buttons to arrange the order in which the rules are applied. When Suspend Further Alert Actions For is selected.  6.  n Edit an existing action for the rule. All alerts that are suppressed during the time period will never be sent.  5.  13.  n Click Community String. and click the Alerts / Filter Rules tab. Click OK to save all changes and return to Trap Viewer Settings. Click Add Rule or click Edit Rule. alert actions are not sent until the specified amount of time has expired. Click Conditions to define the what triggers the rule. Use the arrow buttons to set the order in which actions are performed. Click Alert Actions. 192 . from top to bottom. only new alerts are sent.  4.  n Associate the rule with a new action by clicking Add New Action.  3. Actions are processed in the order they appear. from top to bottom. Click Trigger Threshold > Define a Trigger Threshold for this Rule to suppress alert actions until a specified number of traps arrive that match the rule.  8. Click the General tab. Rules are processed in the order they appear. Click Start > All Programs > SolarWinds Orion > Syslog and SNMP Traps > Trap Viewer. Messages received outside the specified time frame will not trigger alerts. Click Time of Day > Enable Time of Day Checking to apply the rule during a specific period of time.  n Click Trap Details. domains. When the time period expires.  n Click DNS Hostname. and select Enabled. Trap messages are now filtered by the rules and alert actions are triggered when the rule conditions are met. Click File > Settings.  10. The DNS Hostname Pattern rule is case-sensitive.  9. Enabling Time of Day checking creates more overhead for the CPU. and then selecting an action from the list to configure. or hostname patterns. and enter a DNS Hostname Pattern to apply the rule to messages from specific hosts.  7. and enter the patterns in the Community String Pattern field to apply the rule to specific community strings.  n Select object identifiers and comparison functions from the linked context menus.  11.  2.

1.1" MIB="SNMPv2-SMI" When the template is used in an Name="enterprises.3.1.3.What is a Trap Template? Trap templates are used to format your trap messages.6. this line displays the alert Value="${AlertMessage}" DataType="4" message associated with the ValueName="${AlertMessage}" HexValue="" triggered alert.2. The templates are placed in the following locations:  n /SolarWinds/Common/Orion-Detailed-Alert.3.1. This is the section you modify to display the information you want in your trap messages.11307" DataType="6" ValueName="enterprises.4.1.4.1.11307" HexValue="" OID OID="1.0" Value="0" DataType="67" device has been up.10.1.1. TEMPLATE OID LINE INFORMATION RETURNED OID OID="1.trap  n /SolarWinds/Common/Orion-Generic-Alert.3.11307. Add more information by adding another OID element and incrementing the OID.6.3.11307.6. ValueName="0" HexValue="" OID OID="1.1.10.1.0" MIB="RFC1213-MIB" This line displays how long the Name="sysUpTime.0" associated with the trap.4.6.3.1. 193 . Value="1.1" alert.trap  n /SolarWinds/Orion/ForwardSyslog. You can use SolarWinds macros or variables in the OID Value and ValueName attributes or call values from your MIB.0" MIB="SNMPv2-MIB" This line displays the enterprise Name="snmpTrapEnterprise.3.6.trap The following table describes the OIDs section of the Orion Generic Alert trap template.

 n Monitor risky types of traffic. These sensors collect packets using either a dedicated Windows SPAN or mirror port monitor or directly on your Windows server. you can:  n Compare statistics. QoE uses Packet Analysis Sensors to provide packet-level traffic information about key devices and applications. In addition. These metrics provide information about application health and allow you to identify possible application performance issues before they are reported by end-users. With the ability to analyze packet traffic. traffic that might bypass firewalls or lead to data leaks. such as network response time (TCP Handshake) and application response time (Time to First Byte) to determine if a bottleneck is on the application or the network. Packet Analysis Sensors capture packets from the local network interface (NIC) and then analyze collected packets to calculate metrics for application performance monitoring. Traffic data is captured using Packet Analysis Sensors. for example.  n Use data volume trends to pinpoint traffic anomalies and investigate the cause.Monitor Quality of Experience metrics On the Quality of Experience (QoE) dashboard you can monitor traffic on your network. see Common Packet Analysis Sensor deployment scenarios. QoE provides real observed network response time (NRT) and application response time (ART). Packet Analysis Sensors can classify and categorize traffic for over 1000 different applications by associated purpose and risk-level. For more information about specific implementations of QoE. 194 . With QoE.

which includes statistics such as volume.  n Packet Analysis Sensors for Servers (server sensor) collect and analyze packet data of specific applications that flow through a single node. transactions. and network response time for each application on a node. mirror port. and the amount of RAM available on the monitoring server. The system requirements increase for every 100 Mbps of traffic. such as response times or traffic volume. monitored switch for up to 50 discrete applications per node. It identifies packets that are sent to or from the monitored application and analyzes them for QoE metrics. Network Packet Analysis Sensor (NPAS) Your network administrator must create a dedicated SPAN. it captures packets and analyzes them to calculate performance metrics for the monitored applications. the number of cores.  n Packet Analysis Sensors for Networks (network sensor) collect and analyze packet data that flow through a single. SENSOR LIMITATIONS VALUE Maximum throughput (NPAS and SPAS) 1 Gbps 195 . Data are then sent to the Orion server using the SolarWinds agent. the sensor captures all packets that flow through the switch and categorize the packets by application. You can configure how long you retain the packet data in the Database Settings section of the Polling Settings screen. The packet data are then saved to the SolarWinds Orion database. After a sensor is deployed and configured. Limitations to Packet Analysis Sensors The number of nodes you can monitor is limited by the data throughput per node. such as response time or traffic volume. application response time. After you deploy and configure the network sensor to the node monitoring the switch. Server Packet Analysis Sensor (SPAS) A SPAS can monitor:  n packet traffic on a single node  n up to 50 applications per node A SPAS captures packets traveling to and from the node. The information is used to populate your QoE dashboard. Data are then sent to the Orion server using the agent. Packets that correspond to monitored applications are analyzed for QoE metrics.How SolarWinds Packet Analysis Sensors work SolarWinds provides two types of Packet Analysis Sensors to monitor and analyze your network traffic. An included communication agent allows the sensor to send back sampled packet data to the Orion server. or in-line tap monitor on the physical or virtual switch before you can deploy or configure a network sensor.

000 sensors Maximum number of applications per node or sensor 1. 196 .000 applications per node (NPAS and SPAS) Common Packet Analysis Sensor deployment scenarios After you install your Orion platform product.000 pairs (NPAS and SPAS) Maximum number of sensors deployed on your network 1. This impacts the QoE metrics. If you select QoE during the installation. ensure that you do not monitor the same node with multiple sensors. a sensor is already on your SolarWinds Orion server collecting data about applications that SolarWinds Orion is using. SENSOR LIMITATIONS VALUE Maximum number of nodes per sensor (NPAS) 50 nodes Maximum number of node and application pairs 50. there are three main deployment scenarios per sensor type. Based on how you want to aggregate the returned QoE metrics. AGGREGATION LEVEL SENSOR DEPLOYMENT CONFIGURATION I HAVE ACCESS TO MY NETWORK (NPAS) Per application Deploy an NPAS to a port mirror that monitors Automatic all traffic to and from the application Per site Deploy an NPAS to a port mirror that monitors Add a sampling of endpoints to all traffic to and from the site the NPAS as managed nodes Per client Deploy an NPAS to a port mirror that monitors Add all of the endpoints to the all traffic to and from the site NPAS as managed nodes I HAVE ACCESS TO MY APPLICATION SERVERS (SPAS) Per application Deploy the SPAS directly on the application Automatic server Per site Deploy the SPAS to select endpoints Automatic Per client Deploy the SPAS to all endpoints Automatic  n When deploying both network and server sensors on the same network. deploy network sensors on a server dedicated to monitoring a network switch or deploy server sensors directly on physical or virtual servers or workstations.

You can also manually monitor applications and managed nodes or ignore them. Aggregation with access to network (NPAS)  n Create a port mirror. navigate to Settings > All Settings. and activate the auto-detect option. and click on QoE Settings. or network tap setup to monitor your network switch.  4.  n All monitored nodes must be managed by your Orion Platform product before they can be monitored by sensors. Click QoE Settings > Manage QoE Packet Analysis Sensors > Add Packet Analysis Sensor. SPAN. If packet data is not collected. or network tap on the switch with all the network traffic to or from the application.  1.  n You can monitor multiple applications using the same NPAS. Select the Network option. Choose the node with the port mirror. 197 .  3. Aggregation per application This deployment scenario provides a broad indication of the overall response time between computers and the monitored application.  n Applications and nodes are detected by default if the node is managed by your Orion server. and then click Add Nodes. SPAN. Click Settings > All Settings in the menu bar. Click Manage Global QoE Settings.  2.

Click Add Nodes and Deploy Agents to deploy the network sensor to the node. 198 .  6. You then use the users' computers as data points to monitor with Packet Analysis Sensors. For example. Aggregation per site This deployment scenario provides an aggregated response time per monitored site or network to the application. Select the Server option.  4. the response time for the application is four seconds. Assign and test the credentials for the selected node. Choose the nodes with the application you want to monitor. Assign and test the credentials for each node.  5. and then click Add Nodes. Click Settings > All Settings in the menu bar.  5. Aggregation with access to application servers (SPAS)  1.  6. Click Add Nodes and Deploy Agents to deploy a sensor on the node. This method requires you to identify users who best represent how the application is used. the response time from your Detroit office to your datacenter is one second. If you used the aggregation per application deployment method. Click QoE Settings > Manage QoE Packet Analysis Sensors > Add Packet Analysis Sensor.  3. but the response time from Boston to your datacenter is seven seconds.  2.

 2.Aggregation per site with access to network (NPAS)  n Create a port mirror.  1.  n Identify a sample set of users whose computers are monitored by the NPAS.  6. SPAN.  n You can monitor multiple applications using the same NPAS. or network tap on the switch with all the network traffic to or from the application. Select the Network option. Click QoE Settings > Manage QoE Packet Analysis Sensors > Add Packet Analysis Sensor. Click Add Nodes and Deploy Agents to deploy the network sensor to the node. and then click Add Nodes. SPAN. Assign and test the credentials for the selected node. Click Settings > All Settings in the menu bar.  3. or network tap setup to monitor your network switch. 199 . Choose the node with the port mirror.  5.  4.

Choose the nodes with the application you want to monitor.  1.  5. Select the Server option. and then click Add Nodes.  3. Click Settings > All Settings in the menu bar. which may not be caught when aggregated per site or per application. One or two workstations can experience long response times.Aggregation per site with access to application servers (SPAS) Identify a sample set of users whose computers are monitored by the SPAS.  2. Click Add Nodes and Deploy Agents to deploy a sensor on the node. Click QoE Settings > Manage QoE Packet Analysis Sensors > Add Packet Analysis Sensor. This method requires all workstations to be managed within your Orion Platform product. Aggregation per computer This deployment scenario provides highly granular response times for the application because metrics for each computer are recorded. 200 . Assign and test the credentials for each node.  4.  6.

201 .Aggregation per computer with access to network (NPAS)  n Create a port mirror.  5. or network tap on the switch with all the network traffic to or from the application.  n You can monitor multiple applications using the same NPAS. Click Settings > All Settings in the menu bar. or network tap setup to monitor your network switch. Click Add Nodes and Deploy Agents to deploy the network sensor to the node. Assign and test the credentials for the selected node. and then click Add Nodes. SPAN.  6. SPAN. Select the Network option.  3.  4. Choose the node with the port mirror.  1.  2. Click QoE Settings > Manage QoE Packet Analysis Sensors > Add Packet Analysis Sensor.

The network sensor must be installed on a Windows computer that is monitoring the switch's SPAN or mirror port. Monitor traffic to and from a port mirror. and then click Add Nodes.  5.Aggregation per computer with access to application servers (SPAS)  1. Before you begin  n Data from sensors is directed to the polling engine assigned to the node when the sensor was deployed. SPAN.  6. Select the all user computers to monitor. such as response time or traffic volume. After you deploy a network sensor to the port mirror. Click QoE Settings > Manage QoE Packet Analysis Sensors > Add Packet Analysis Sensor. the sensor monitors packets to and from the node. and analyzes the packets for QoE metrics.  2. Click Settings > All Settings in the menu bar. Select the Server option. SPAN.  4. or network tap. identifies the application or the URL. Click Add Nodes and Deploy Agents to deploy an agent on the node. 202 . Assign and test the credentials for each node.  n A high number of applications or nodes can cause performance issues with the sensors.  3. or network tap Network sensors monitor all packets that flow through the switch and categorize the packets by application.

click Edit Sensor. Select Network. and click Submit. and verify the selected NIC. and click Add Selected Nodes. 203 .  2.  6. Click Settings > All Settings in the menu bar. and click Add Nodes. Click QoE Settings > Manage Global QoE Settings.Install the network sensor  1.  2.  5.  4. Click QoE Settings > Manage QoE Packet Analysis Sensors > Add Packet Analysis Sensor. Assign and test the credentials for the node. Click Add Nodes and Deploy Agents. you can filter application traffic based on domain names instead of all http traffic. a message is displayed in Notifications. Click Settings > All Settings in the menu bar. Deploying the sensor and receiving the first set of data can take several minutes. Move the node that monitors your switch to the Selected Nodes panel. When the deployment is finished. Monitor website traffic based on domains After you deploy a network sensor. select the sensor on the Manage Quality of Experience (QoE) Packet Analysis Sensors page.  1. Make sure you select the Windows machine that is monitoring the SPAN or mirror port of the switch.  3. When the sensors are successfully deployed.

Click Settings > All Settings in the menu bar. To specify which nodes and applications to monitor manually.  3. and click Submit. Monitor traffic to and from a specific node After you deploy a server sensor to the application node. QoE can automatically detect the first 50 applications. and analyzes the packets for QoE metrics. 204 . Set the HTTP application domain detection level. click QoE Settings > Manage (QoE) Applications.  3. such as response time or traffic volume.  5. Click Add Nodes and Deploy Agents. Select the applications. and click Submit. the sensor monitors packets to and from the node. Discovered applications have the "No Risk" Risk Level and the "Both Business and Social" Productivity Rating associated with them. Assign and test credentials for each node. Select Server.  4. QoE auto-discovers the applications on the servers. and click Disable Monitoring or Disable Discovery. To modify the Risk Level and Productivity Rating. Click QoE Settings > Manage QoE Packet Analysis Sensors. and click Add Nodes.  6. Move the Windows nodes that will host the server sensors to the Selected Nodes panel.  2. a message is displayed in Notifications.  4.  1. and click Add Packet Analysis Sensor. or you can add specific applications. Nodes are automatically detected and added by default. see Monitor QoE applications and nodes. Set the Auto-detect QoE applications option to Active. and edit the application. and click Add Selected Node. Use the Global QoE Settings page to disable monitoring or discovery of multiple applications. identifies the application or the URL. When the sensors are successfully deployed.

Click Uninstall.  c. Monitor QoE applications and nodes By default nodes and applications are automatically monitored by QoE when you deploy a Network or Server Sensor. Remove a sensor Removing a sensor from a node is a two-step process.  2. Follow the onscreen prompts to completely uninstall the agent.  n QoE automatically chooses settings. during deployment. including the interface to capture traffic data and limits to memory and CPU.  e.  1. Select the node. See Global QoE Settings for more information on changing these settings. You can manually update an agent from the Manage Agents page. Applications are automatically detected and added by default. Select SolarWinds Agent. The sensor is removed from the list and the communication agent is uninstalled and cannot gather traffic data or send data. Click Delete Sensor.  e. Remove the agent directly from the node:  a. and then remove the communication agent directly from the node.  b. First delete the sensor using the Orion Web Console. see Monitor applications for QoE.  d.  d. Server Sensors automatically monitor the top 50 applications on the node they are installed on based on the global settings. Click Delete when prompted.  n You can confirm the deployment status on the Manage QoE Packet Analysis Sensors page. To specify manually which applications to monitor. You can automatically filter which nodes or applications are monitored. Delete the sensor using the Orion Web Console:  a. Click Settings > All Settings in the menu bar. Click QoE Settings > Manage QoE Packet Analysis Sensors. You can change which applications are monitored after the sensor is deployed. You can change these settings after deployment is complete by selecting the sensor and clicking Edit.  c. Settings are distributed to sensors regularly when the agent is updated. Manage global QoE settings You can control how Packet Analysis Sensors behave by changing the settings on Manage Global QoE Settings page.  b.  n Deployment may take some time and will run as a background process. Log in to the computer with administrative credentials. 205 . Navigate to Control Panel > Programs and Features.

Nodes with QoE traffic Control how you monitor QoE nodes for Network Packet Analysis Sensor.Separate and monitor http traffic based on the domain and first level directory within each domain.  n Transaction destinations (servers) .  n Third level (http://hostname/path1/*) . This is active by default.Monitor all application traffic.  n Second level (http://hostname/*) .Monitor applications that receive traffic based on the destination IP address of the packet. You must select applications manually when this option is disabled.QoE applications Control how you monitor QoE applications for both Network Packet Analysis Sensors and Server Packet Analysis Sensors. include top X application that have at least Y% of total QoE traffic. Auto-detect QoE nodes Use this to detect and monitor the first 50 nodes with network traffic.  n Transaction sources (client) .Separate and monitor http traffic based on domains. or all application traffic. you should also automatically detect applications to receive all metrics. Packet sources and destinations are based on the source or destination IP address included in the packet. If you automatically detect nodes. This is active by default. Add auto-detected applications Refine the monitored applications by choosing to monitor all application traffic sources. Filter the number of monitored applications to applications that generate a certain amount of network traffic. For each node. traffic destinations.  n Top level (http://*) . You must select nodes manually when this option is disabled. 206 . HTTP application domain detection level Choose how QoE breaks up monitored http traffic.Monitor applications that generate traffic based on the source IP address of the packet.  n Either a source or destination . Auto-detect QoE applications Use this to detect and monitor traffic associated with all applications that fulfill the auto-detection rules defined on this page.Monitor all http traffic.

 n Either a source or destination . Add auto-detected monitored nodes Further refine the nodes that are monitored by choosing to monitor all nodes that are traffic sources.Monitor nodes that receive traffic based on the destination IP address of the packet.Monitor all traffic. Change other settings to refine the number of applications you automatically monitor.  5. Click Submit. If you automatically detect nodes. Select Active in Auto-detect QoE applications. Monitor applications for QoE Applications are automatically monitored when traffic is detected by the Packet Analysis Sensor. RDP. the settings may have changed or you may have upgraded from a version of QoE that does not automatically monitor applications. QoE installs with the ability to monitor over 1000 pre-defined applications. SQL. you should also automatically detect applications to receive all metrics.  n Transaction destinations (servers) . you can monitor up to 1000 applications.  1. or all nodes that generate or receive network traffic. 207 . you can manually select specific applications to monitor.  3. However.  4.  n You should not assign more than 50 applications to a single node due to potential performance issues. CIFS. It may take some time for the settings to apply.Monitor nodes that generate traffic based on the source IP address of the packet. Packet sources and destinations are based on the source or destination IP address included in the packet. Only applications that meet the criteria selected in QoE Applications are monitored automatically.  n Transaction sources (client) . traffic destinations. including FTP. and Exchange. SolarWinds recommends that you preferentially monitor business-critical nodes and applications.  2. Monitor QoE applications automatically While QoE sensors automatically detect and monitor applications by default. See Global QoE Settings for more information on the settings. You can also define your own custom HTTP applications. Click QoE Settings > Manage Global QoE Settings. However.  n Because of the hardware requirements needed to process large amounts of traffic. Click Settings > All Settings in the menu bar.

QoE automatically monitors the first 50 nodes with traffic.  n Applications can be disabled. You must first add a Network or Server Sensor before you can enable any applications. Click Add New. Your newly enabled application will display on the Manage QoE Applications page in alphabetical order. Use the Search or Group By options to find the application you want to monitor. However. Risk Level.  7. see Monitor applications for QoE.  6. On the Configure Application view. the settings may have changed or you may have upgraded from a version of QoE that does not automatically monitor nodes.  n Only nodes that meet the criteria selected in Nodes with QoE Traffic are added automatically.Monitor applications manually You may choose to add monitored applications manually to QoE.  9. Only nodes that have already been specified as nodes to monitor on the Manage QoE Nodes page display in this list. select it.  5.  n Enabled applications are currently being monitored on at least one node.  8. Add nodes automatically While Network Sensors automatically detect and monitor nodes by default. and then click Next. Click Next. Select Choose a pre-configured application. or Productivity Rating as necessary. In the Settings grouping. Review your choices on the Summary page. click QoE Settings > Manage QoE Applications. Click Settings > All Settings in the menu bar.  4. For information about adding applications. and then click Next. Monitor nodes with a network sensor Nodes are automatically detected and monitored when network traffic originates from or terminates at a node.  n Applications are only listed if there are monitored nodes.  2. Applications that are already enabled do not display in the list. you can manually specify the nodes after the network sensor has been successfully deployed.  1.  3. and then click Finish. edit the Category. which means that no traffic for the application is currently collected on any node. On the Specify Nodes view. choose the nodes you want to monitor for this type of traffic.  n Automatic node discovery may not be 100% accurate due to devices with the same IP addresses in your network. 208 . You can monitor up to 50 nodes per network sensor.

 4.  4. 209 .  3. Toggle Monitoring or Discovery OFF. It may take some time for the settings to apply. See Global QoE Settings for more information on the settings.  1. disable discovery or monitoring for that application in the Manage QoE Applications page. choose the applications you want to monitor for these nodes.  3.  5.  2.  1. Click QoE Settings > Manage Global QoE Settings. On the Select QoE Applications page. View the nodes and applications selected by expanding the Network Sensor you just configured. Click Finish.  6. Change other settings to refine the number of nodes you automatically monitor. choose the managed nodes you want to monitor with this network sensor. Click Submit.  1. you must delete the node from the original sensor before you can add it to the new network sensor.  2.  2.  3. These settings are on a global level. Ignore application traffic If you decide to no longer monitor an application. See Monitor applications for QoE for more information.  5. Click QoE Settings > Manage QoE Applications. You cannot turn application discovery or monitoring on or off for specific sensors. Navigate to the Manage QoE Packet Analysis Sensors page. Click Settings > All Settings in the menu bar. Expand the Network sensor that you want to add a node to. Click the Add Node to Monitor button. Select Active in Auto-detect QoE nodes. Use the following table to determine which combination of settings you want to use. Click Settings > All Settings in the menu bar.  7. On the Create QoE Node page. Add nodes manually If a node is already monitored and you want to monitor it with a different sensor. Ignore traffic from applications or nodes You can ignore traffic generated by applications or from a specific node. Review your selections on the Summary page.

Select the node you want to remove. and add them to nodes you are monitoring. On the Select Application page. Click Settings > All Settings in the menu bar. Click Settings > All Settings in the menu bar. select Create a new HTTP application.  2. and application traffic is not monitored monitored Ignore node traffic You can permanently ignore all traffic from specific nodes that you monitor on a network sensor. and application traffic is discovered. DISCOVERY ON discovered and application traffic is but application traffic is not monitored monitored Applications cannot be automatically Applications cannot be automatically DISCOVERY OFF discovered. In the Settings grouping. Risk Level. This is often used to reassign a node to a different network sensor. and then choose the Category. enter the name and description of the application you’re creating. click QoE Settings >  Manage QoE Packet Analysis Sensors. You cannot add a node back to its original network sensor. and click Delete.   MONITORING ON MONITORING OFF Applications are automatically Applications are automatically discovered. 210 .  3. On the Configure Application page. and click Edit. Click QoE Settings > Manage QoE Applications. and click Next. The node is removed from the sensor and all traffic to and from the node is ignored. you can define custom HTTP applications. Click Add New.  1.  5.  2. and Productivity Rating appropriate for the application.  4.  3.  1. Select a network sensor.  4. Define custom HTTP applications In addition to choosing from predefined applications.

and then click Next. Advanced sensor configuration Sensors cannot be edited until they are fully deployed. selecting Hostname contains changes the help text to http://*. The status of completely deployed and working sensors is Up. or you can check the Manage QoE Packet Analysis Sensors page. 211 .  1.  9.  5. On the Specify Nodes page. Click Save.  6. you can configure:  n the monitored interface  n the allocated CPU cores and memory Configure which interface to monitor for traffic When you deploy a sensor.. This specifies the HTTP application traffic to monitor. Click Edit Sensor.  2. Select the desired interface from the Interface to capture QoE data drop-down list.  8. notice that the example changes to indicate how the accompanying text field will be used. Once the sensor is installed. Set the URL Filter. Your new application will display on the Manage QoE Applications page in alphabetical order.. When you choose which filter to use in the drop-down. Only nodes that have already been specified as nodes to monitor (on the Manage QoE Nodes page) will display in this list. Click Settings > All Settings in the menu bar.  7. choose the nodes to monitor for this type of traffic. you can go back and change the monitored interface. For example. An entry displays in the notification area when your sensor is deployed.*/path/page. Review your choices on the Summary page.  6. Click Next. the first available interface is monitored for traffic. Enter the hostname or URL for your filter. Any text you enter will be included in the filter where the "…" is. Select the sensor to edit.  3.html. and click Finish. When you click Edit Sensor.  4. Click QoE Settings > Manage QoE Packet Analysis Sensors.

Click QoE Settings > Manage QoE Packet Analysis Sensors.  1. the more memory you need.  3. In the Memory field. and transaction thresholds that are used to alert you to irregularities in your network. and click Edit. If you allocate less than the recommended amount of memory.  7. The more flows that are going on the line. For sensors.  2. Select Override Orion General Thresholds next to each data type. 212 . In the CPU Cores field. Select the application to edit.Set the number of CPU cores and the amount of memory QoE can use When a sensor is deployed. and then click Next again. Click QoE Settings >  Manage QoE Applications. QoE automatically allocates one CPU core and 256 MB of memory to the sensor.  3. select the number of CPU cores you want to allocate to the sensor. Click Next. network response time (NRT). the memory usage scales with the traffic load. Select the sensor to edit. you may see reduced performance.  2. Configure QoE thresholds You can modify the application response time (ART). Click Settings > All Settings in the menu bar. After the sensor is installed. select the number of GB you want to allocate to the sensor.  6. volume. you can change the allocated CPU cores and memory.  5.  4. Click Edit Sensor. NUMBER OF GUIDELINES CPU CORES 1 Not Recommended 2 Suitable for 100 Mbps links 3-4 Gigabit links with low utilization 5-6 Gigabit links with medium utilization 7+ Gigabit links with high utilization  1. you may see reduced performance. click the plus sign by Thresholds. On the Summary page. If you allocate fewer than the recommended number of CPU cores.  4.  5. We recommend that the sensors collect a few days' worth of data before setting thresholds. Click Settings > All Settings in the menu bar.  6. Click Save.

 5.  d.  n Polling Engine  n UCS Port  n UCS User Name  n UCS Password  e. Set up and monitor Cisco Unified Computing Systems (UCS) To gain an overview of all information provided by UCS. or external mask are set to 0. Review your information. and click Yes to add the device.  g.  c. Click Finish. click on it.  f. Add Node. Click Test under the UCS fields.0. Repeat step 3 for each device.  7. If the external gateway.  h. Select UCS Manager Credentials.  2. and provide the credentials.  1.  a. and the primary fiber interconnect devices into the SolarWinds Orion database for monitoring. Verify in the UCS console that the fiber connects have external IP addresses. Add the UCS Master node to the database. Packet Analysis Sensor agents The software that provides a communication channel between your SolarWinds server and the monitored object to which you have deployed your Packet Analysis Sensor is called an "agent". and click Next. The agent runs as a service. Provide the IP Address. If the node shows up in the All Nodes list in italics or with ‘n/a’ as the state. Double-click on the UCS Master node in All Node. which is configurable in the Orion Polling Settings page. and find the UCS Overview resource. or provide the host name and select Dynamic IP Address.  8. 213 . Agents are used to send the data that QoE collects back to the Orion server. Add each UCS fabric interconnect switch and blade device.0. Add relevant pollers. edit them with values valid for external devices. and it has a small installed footprint (under 100MB installed). Click Manage Nodes in the All Nodes resource if the node is not in the list.0. Change the threshold.  3. external IP address. The default baseline is seven days. Confirm that LDAP authentication is not enabled on your UCS device. Select External Node or Status Only: ICMP as the polling method.  4. See the device documentation for details. and click OK. add the UCS master device. Select the resources to monitor on the node.  b. You can use specific thresholds or you can use a dynamic threshold based on the baseline established. Click Add Node.

This same mechanism is also used for the ESX VMWare API. 214 . To select the proper view we use the existing View By Device Type feature. If any UCS device shown in the UCS Overview is not currently managed. and add the node.  6. To ensure that Standard Poller does not overwrite MachineType and other fields. double-click the device. we use EntityType to identify UCS node in the Standard Poller (and so force Standard Poller not to overwrite our required fields).

You can filter the application view through using the filter options and filter properties. This view provides quick insight into issues in the stack and overall statistics. See Understanding the AppStack data for details on icons and colors of icons for at-a-glance monitoring. monitor.Monitor your environment using AppStack The Application Stack. In the AppStack view. You can further understand. The AppStack Environment view is an interactive visual mapping within Orion that provides an in-depth perspective through the entire environment to help identify the root cause of performance and availability issues. and displays them in a customizable view. AppStack automatically gathers information about objects in your environment. To access the AppStack. you can hover-over each node and application to see a tooltip of data and status. The AppStack environment supports only server and virtual server node types. click My Dashboards > Environment. and customize the AppStack with the following:  n AppStack categories and data  n Customize the AppStack view  n Filtering the AppStack  n Create an AppStack layout  n Understanding the AppStack data 215 . as well as their respective relationships. You can save and reuse these filters as layouts to display specific views of the AppStack. or AppStack. Some relationships. is a term used to describe the various layers that make up a complex application delivery infrastructure. Select each item on the view to load related items throughout the environment. such as groups and dependencies can be defined by the user.

the illustration below displays all objects in the current environment. is in a Critical state. MSSQLSERVER. To see what this application is related to. the system automatically updates the view to select and highlight related objects. as shown: If you want to completely hide unrelated objects from the view. and click on an object to see related objects. Once it is selected. To investigate further. Simply navigate to the AppStack Environment view.Troubleshooting with AppStack Using AppStack as a troubleshooting tool is fairly straightforward. click the MSSQLSERVER icon. In this example. 216 . The application. As you select objects in the AppStack. as indicated by its icon. you can click the Spotlight. navigate to the Details page of the object or any related object. Select an object then click Spotlight in the upper right-hand corner to hide them. related objects are highlighted by the fading of unrelated objects. MSSQLSERVER is selected. For example.

The Category Status Summary can be toggled to either be displayed at all times. The Category Status Summary (located to the right of each category) parses. the following AppStack Environment categories are available in SAM:  n Groups  n Applications  n Database Instances (with Orion DPA integrated)  n Servers  n Hosts  n Virtual Clusters  n Virtual DataCenters  n Virtual Centers  n Volumes Other Orion products offer additional categories. You can manage the setting through the Change Layout Settings settings drop down option. enumerates.To navigate to the details page of a selected object. You can review and managed the critical and warning issues per node. click the icon of the selected object next to the chart at top or double-click the larger icon in the main view. 217 . AppStack categories and data By default. Empty categories can be hidden through the Change Layout Settings option in the drop down menu. and displays the number of objects in a given category. or only when categories are collapsed. emphasizing the status as indicated by the colors.

and peripheral devices. as access to data files. The server makes services. Virtualization Manager (VMAN).g. Servers       A server is a computer capable of accepting requests from the client and giving responses accordingly. and Oracle. For example. as indicated with the check mark for Storage Resource Monitor (SRM). Applications         In SAM. MySQL.Supported categories and data The following matrix outlines all of the categories associated with the AppStack Environment view. SAM. programs. Different categories are available with each SolarWinds product. CATEGORY SRM SAM VMAN WPM DPA DEFINITION Groups   Groups enable you to more effectively manage your environment by giving you the ability to logically organize monitored objects. Transactions         A transaction is a recording of web browser steps assigned to a specific location. Each virtual cluster is formed with physical machines or a VM hosted by multiple physical clusters. Database         A database is an organized collection of data. 218 . available to workstations on a network. and Database Performance Analyzer (DPA). the actions required to navigate to a specific URL make up one step. regardless of device type or location. Web Performance Monitor (WPM). Hosts       A Host is defined as a server running a Hypervisor for virtualization. (E. an application is a collection of component monitors grouped together to collect specific metrics concerning the application as a whole. Steps         A step is a collection of actions. Instances The displayed database instances including Microsoft SQL. It hosts multiple virtual machines. The VMs in a virtual cluster are logically connected by a virtual network across several physical networks.) Virtual       Virtual clusters are built with VMs installed at Clusters distributed servers from one or more physical clusters.

Some data stores represent data in only one schema. Volumes       A volume. A data store is a general concept that includes not just repositories like databases. or LUN. but also simpler store types such as flat files. but is most often used to refer to a logical disk as created on a SAN. consolidated disk storage through a standard Ethernet connection. NAS Volumes         Network-attached storage (NAS) is a type of dedicated file storage device that provides local-area network (LAN) users with centralized. typically resident on a single partition of a hard disk. which is a device addressed by the SCSI protocol or Storage Area Network protocols which encapsulate SCSI. or logical drive. management. is a number used to identify a logical unit. such as a tape drive. 219 . Virtual       A VMware virtual center (vCenter) server is a Centers centralized management application that lets you manage virtual machines and ESXi hosts centrally. CATEGORY SRM SAM VMAN WPM DPA DEFINITION Virtual       A virtual datacenter is a centralized virtual Datacenters repository for the storage. The vSphere client is used to access vCenter Server and ultimately manage ESXi servers. is a single accessible storage area with a single file system. and dissemination of data and information organized around a particular body of knowledge or pertaining to a particular business. A LUN may be used with any device which supports read/write operations. LUNS         A Logical Unit Number. These objects are modeled using classes defined in a database schema. such as Fibre Channel or iSCSI. Data Stores         A data store is a repository of a set of data objects. while other data stores use several schemas for this task.

they are bound to the physical cluster on which they exist. or a single Infinite Volume. the volumes and LIFs are exclusive to the V-Server. In a cluster. power supplies. and so on) often up to the point where all single points of failure are eliminated from the design. This AppStack provides a sample of categories and multiple nodes in various health states: 220 . you select the desired capacity (number of disk drives) and assign a RAID level to it which provides a redundancy level. However. fans. A VServer can either contain one or more FlexVol volumes. Each VServer has a separate administrator authentication domain and can be managed independently by a VServer administrator. VServers         A virtual storage server (VServer) contains data volumes and one or more LIFs through which it serves data to the clients. resiliency. A VServer securely isolates the shared virtualized data storage and network. a VServer facilitates data access. Multiple Vservers can coexist in a single cluster without being bound to any node in a cluster. A cluster must have at least one VServer to serve data. When you create a storage pool. However. Storage Arrays         Storage Arrays consist of two or more disk drives built into a stand-alone unit. VServers use the storage and network resources of the cluster. and maintainability by using existing components (controllers. and appears as a single dedicated server to its clients. CATEGORY SRM SAM VMAN WPM DPA DEFINITION Pools         A storage pool (also called a RAID array) is a collection of disk drives that become a logical entity. Storage arrays provide increased availability.

You may need to log in with an administrator account to perform this action. such as limiting the amount of objects displayed. 221 . and increasing or reducing the update interval. Modifying these settings can help with performance.Customize the AppStack view You can customize this view by clicking Change Layout Settings in the Layout drop down menu of the AppStack page. hiding empty categories. These setting affect the look of content and refresh rate of the page.

 n Align Objects: By default. This can be changed by selecting either Center or Right-Aligned. Filtering the AppStack You can filter the AppStack by status. limiting the number of Up objects displayed can improve AppStack performance. with the worst status being shown on the left side of the view. indicating the number of objects in a particular state.  n Update Interval: Change the time between AppStack refreshes. giving the view a cleaner look. and applications.  n Empty Categories: Selecting this option hides categories with no objects. You can also create filters selecting from all filtering properties. 222 . all objects are left-aligned. display name.  n Object Names: Highlights distressed objects by displaying the names of these objects. Additionally. useful for quickly troubleshooting the servers and virtual servers.  n Show Category Status Summary: The Category Status Summary are the colored numbers to the right of each category.You can modify the following:  n Limit on Up Objects Shown per Category: Objects in the AppStack Environment view are ordered from left to right. Limiting the number of Up objects can provide more room for objects needing attention. You can use these filters as layouts for different displays of AppStack data. or only when categories are collapsed. This can visible at all times.

you can filter the view by selecting one or more statuses and then applying the filter. The filtering sidebar includes the following options: Statuses only become available for filtering when an object in your environment is in that state. Additionally. the Down status will not be available when filtering. Creating filters Creating filters using the AppStack filter properties gives you more options for refining the content displayed in the AppStack: 223 . every object is displayed when you enter the AppStack Environment view. If you are concerned only about objects with a certain status. as well as one or more keywords. For example. Filter options By default. if no objects have a status of Down. you can filter objects based on various properties. You may need to log in with an administrator account to perform this action.

Apply the filter to update the AppStack. Under the Layout menu. click Save As New Layout.  2. You cannot modify the default layout. you can load them through the Layout menu. As you create and save layouts. click Add column.  3. When done.  1. select one or more objects from the Orion Object drop down list. 224 . From the pop-up menu. Click My Dashboards > Environment. and then click [+] Add Filter Properties. New layouts are created by:  1.  2. Create a filter by selecting options in the sidebar or selecting filter properties. A default layout is provided that contains all currently monitored objects visible in the AppStack Environment. You can tailor these layouts to view to specific objects of interest using a filter. Enter a name and save. The layout adds to the Layout menu. Create an AppStack layout A Layout is a user-defined filter (view-limitation) with configured settings you can save and use when viewing the AppStack.  3. The new filter appears in the filter column.

hover overs. To remove a layout. to create a Layout where only IIS objects in the AppStack Environment view are shown. and navigation options to help identify object status as you monitor:  n Object status and colors  n Using quick links  n Using the overview bar 225 . The layout is added to the Layout menu. If you want to save as a new layout.You can modify the layout by making changes to the filter and clicking Save to update. add the IIS filter property. For example. click Save as New Layout. Understanding the AppStack data The AppStack uses specific colors and icons. select the layout as currently used and select Delete this Layout. The dot to the left of the layout in the menu indicates the layout currently used. allowing you to easily navigate to that layout with its defined filter and settings. Apply the filter and save it as a new layout.

226 . Objects will be in one of the following states according to the icon color and shape: STATUS COLOR EXAMPLE Down Red Critical Pink Warning Yellow Unknown Gray Unreachable Black Up Green Other Blue - External Purple - You can only filter against statuses actively monitored in the AppStack. memory. For example. Servers can only provide an Up or Down status. hover over the server icon to view the detailed tooltip. or hardware health status. To check CPU. The reported status for applications and LUNs is based on performance thresholds. if no objects have a status of Down.Object status and colors Objects in the AppStack display with colors based on their current status. providing a quick summary of your environment. the Down status is not available for filtering.

revealing the visible objects within each category. Each category can be individually expanded and collapsed by clicking [+] and [-] next to the category name. Each category can be individually expanded and collapsed by clicking [+] and [-] next to the category name. Using quick links The Quick Links bar allows you to quickly open and close all visible object categories. hiding the objects within each category. you can toggle whether or not to show the names of objects that have a distressed status.The AppStack Environment view offers a parent/child relationship. Additionally.) This relationship is represented as a mixed icon. 227 . (Parents can be either servers or hosts. For example. The parent is the larger of the two icons that is hosting the child. Expand All Opens all categories. Collapse All Closes all categories. the following illustration graphically shows that an application (child) is Down on a node (parent) that is Up.

Unknown and Unreachable. an additional 50 objects that are hidden from view. meaning only 87 objects of 111 total objects in this category are being displayed. (87 of 111). Critical.Show/Hide Names Allows you to toggle between showing and hiding the names for each object that is in a distressed state. Using the overview bar The Overview Bar summarizes your environment in a compact space. Objects shown here will be in one of the following distressed states: Down. This provides a numerical summary of your environment. An icon and count will only appear if at least one object is currently in that state. Individual filtered objects The doughnut chart in the Overview section graphically displays the ratio of objects to one another in all possible states using indicative colored slices. The default number of 50 can be changed in the Settings page. the category name will display the number of displayed objects followed by the total number of objects. For example. If more objects exist than are allowed to be displayed on the screen. the filtered objects will be displayed above the Overview Bar. Objects under the Issues header are parsed and enumerated according to status. 228 . by default. If your view is currently filtered. Warning. Related objects may be found by clicking More. as shown. The total number of objects in your environment is also displayed. Clicking More (located after the last visible object in the category) will display.

see:  n Enable and disable the Asset Inventory dashboard  n Asset Inventory data collection  n Add server hardware monitoring 229 . or managing and maintaining your infrastructure. gathering information for insurance purposes. Automatic inventory data collection benefits those interested in tracking asset depreciation.Manage Asset Inventory The Asset Inventory dashboard lets you maintain a current and detailed inventory of your environment's hardware and software. For more information.

Navigate to the Node Details view by clicking any node. Disable Asset Inventory data collection by un-checking this box.     230 . Enable Asset Inventory data collection via the Management Resource  1. The Asset Inventory option is available only if the node supports Asset Inventory polling. Select the Asset Inventory box to enable Asset Inventory data collection.  2. click List Resources.  3.Enable and disable the Asset Inventory dashboard The Asset Inventory sub-view is automatically displayed for each node supported. From the Management resource. You can enable Asset Inventory data collection for an individual node via the Add Node Wizard or by navigating through the Management resource.  The option to display Asset Inventory information may not be available if the node does not have a supported operating system.

 1. Add Node Wizard From the Add Node wizard. Asset Inventory data collection occurs once daily. On the Web Console. Add server hardware monitoring There are two ways for administrators to add server hardware monitoring for nodes. Note: 1 is the minimum allowable value for this field. the impact on your polling engine is minimal.  Required sub-views are enabled by default for nodes with Asset Inventory enabled. and through the Node Details group of the Node Details page. Inventory data does not need to be collected with the same degree of regularity as status information.000 servers.Asset Inventory data collection Asset Inventory data collection is automatically enabled during the Network Sonar Discovery and/or the upgrade process. 231 . through the Add Node wizard.  3. Change the Default Asset Inventory Collection Period You may need to log in with an administrator account to perform this action. therefore. Click Submit. Adjust the number of days for the Default Asset Inventory Poll Interval field. This data collection  interval can be configured to suit your needs. the option to display Hardware Health of Servers is available after a node has been defined. For a larger environment consisting of roughly 1. the total Asset Inventory data should total just under 100MB. Data collected for Asset Inventory purposes uses less than 100KB of database space per node.  2. Check this box to enable hardware health monitoring. click Settings >All Settings > Orion Polling Settings.

click My Dashboards > Home.  1.Manually add hardware monitoring You may need to log in with an administrator account to perform this action. In the All Nodes resource. To disable hardware monitoring. Click List Resources. click the node you want to monitor. see Troubleshooting hardware health. For information on troubleshooting hardware health polling. 232 . On the Web Console. and click Submit. then click Submit.  3.  2.  4. navigate back to this screen and uncheck Hardware Health of Servers. Select Hardware Health Sensors.

and events in real time  n The Real Time Process Explorer  n The Service Control Manager  n The Windows Scheduled Task Monitor  n The Real Time Event Log Viewer 233 .Manage processes. tasks. services.

The Real Time Process Explorer
The Real Time Process Explorer (RTPE) is available for WMI and SNMP monitored nodes. The advantage of
the RTPE is that you no longer need to physically or remotely log in to a computer and run the Task
Manager to retrieve that machine's vital statistics. Information for monitored and unmonitored processes
is displayed directly through SAM using the RTPE.

Notes:

 n Only SAM administrators can end processes as well as enable and disable the RTPE.
 n The User Name and Command Line columns are hidden by default.
 n Using the RTPE on a node monitored via ICMP, which has no working component, requires you to
select Windows credentials manually. Consider promoting the selected node to SNMP or WMI to
avoid this prompt.

234

Access the Real Time Process Explorer from the application details page
The Real Time Process Explorer (RTPE) is available for WMI and SNMP monitored nodes. The advantage of
the RTPE is that you no longer need to physically or remotely log in to a computer and run the Task
Manager to retrieve that machine's vital statistics.

Pop-ups must be enabled for the Real Time Process Explorer to be viewed.

 1. On the Web Console, click My Dashboards > SAM Summary page.
 2. In the All Applications group, click an Application.
 3. Locate the Management resource and click Real-Time Process Explorer.

The Real Time Process Explorer can also be accessed from the Component Details page and Node
Details page.

235

Monitor unmonitored processes
Processes currently monitored by SAM are indicated by the application icon and name of the assigned
application. Processes that are not currently monitored by SAM are indicated by the [+] symbol, followed
by the words, Start monitoring.

 1. From the RTPE, click Start monitoring.
 2. From the Edit Properties section of the Component Monitor Wizard you can begin setting up the
selected component monitor.

236

Use the Real Time Process Explorer
Different information is displayed in the RTPE depending on which protocol you use to monitor a node.
The table below shows the differences in the information gathered based on the protocol used.

MONITOR PROCESS WMI SNMP ORION AGENT FOR LINUX
Name Yes Yes Yes

Process ID Yes Yes Yes

Assigned Application Yes Yes Yes

CPU usage Yes Yes Yes

Physical Memory Yes Yes Yes

Virtual Memory Yes No Yes

Disk I/O Yes No Yes

User Name Yes No Yes

Command Line Yes* Yes* Yes*

Polling interval Five seconds Up to two minutes  

Windows servers update their SNMP statistics every two minutes. It takes two updates to these statistics to
provide an accurate calculation. Data displayed in the RTPE via SNMP can take up to four minutes to
display.

* Information on certain processes may not be exposed which can result in certain rows being
blank.

By default, all available columns, with the exception of the User Name and Command Line, are
shown for the top ten running processes. Each column can be sorted, added, or removed by clicking
the column head and then clicking the drop down arrow.

Show all running processes

Click Show All in the bottom-left of the window.

Show a set number of running processes

Change the number in the text box next to the Show All button

Pause polling

If available, click Pause Polling in the top-left of the window.

237

End processes

Check the boxes next to the processes you want to end and then click End Process. This option
is only available when the RTPE is using a WMI connection.

Start polling

Click Start Polling in the top-left of the window.

For Windows-based nodes, change the credentials by clicking the Use Different Credentials button to bring
up the credential library dialog box.

Clicking Refresh will re-poll the running processes.

238

Real Time Process Explorer alerts
Three alerts are included with the Real Time Process Explorer:

 n High CPU Percent Utilization with Top 10 Processes
This alert sends an email when the CPU utilization is greater than 80%.
 n High Physical Memory Utilization with Top 10 Processes
An alert is sent when physical memory usage is at or above 90%.
 n High Virtual Memory Utilization with Top 10 Processes
An alert is sent when virtual memory usage is at or above 90%.

These alerts can be found in the Alert wizard. For more information, see Use alerts to monitor your
environment.

Alerts may lag if you are monitoring hardware via SNMP. It takes two updates to these statistics to
provide an accurate calculation, meaning an alert can take up to four minutes to reach its recipient.
To expedite this process, change the protocol to WMI, which updates every five seconds. Also,
consider adjusting the trigger time to a value greater than two minutes.

239

Real Time Process information in top 10 alerts
SAM provides additional troubleshooting information for high CPU, memory, and virtual memory by
sending email alerts. This is done by utilizing the Top Offending Processes metric running on the server at
the time of the alert.

Find the executable path SolarWinds.APM.RealTimeProcessPoller.exe and its command line
arguments below.

Command line argument syntax:
SolarWinds.APM.RealTimeProcessPoller.exe -n=<NodeID> [-
count=<NumberOfProcesses>] [-sort=<SortBy>] [-timeout=<PollingTimeout>]
[-alert=<AlertDefID>]

Command line argument variables

VARIABLE DEFINITION
-n ID of a Node (NodeID), which is polled.
-count The number of processes to show.
-sort The criteria used for the selection of top processes.

Process:

n CPU - Processor time. This is the default value if the command line argument is not
specified.
n PhysicalMemory - Process physical memory.
n VirtualMemory - Process virtual memory.
n DiskIO - Process disk I/O per second.
-timeout Timeout for polling in seconds.
-alert The AlertDefID of associated triggered alert. If this argument is provided, then alert notes
are updated with the results from polling.
-activeObject The ActiveObject property of the associated triggered alert. If this argument is not
provided, NodeID is used.

Example 1
This example returns the top 20 processes with the highest virtual memory consumption running on
the host with node ID 123.

SolarWinds.APM.RealTimeProcessPoller.exe -n=123 -count=20 -sort=VirtualMemory -
timeout=300

Example 2
This example uses the Execute an External Program alert action:

240

SolarWinds.APM.RealTimeProcessPoller.exe -n=${NodeID} -alert=${AlertDefID}
Example 3
This example uses the Execute an External Program alert action for an alert defined for the Volume
object type:
SolarWinds.APM.RealTimeProcessPoller.exe -n=${NodeID} -alert=${AlertDefID} -
activeObject=${NetObjectID} -sort=VirtualMemory

241

The Service Control Manager
The Service Control Manager (SCM) is similar to the Real Time Process Explorer, except with the SCM you
manage the services of monitored Windows nodes instead of processes. The advantage of the SCM is that
you no longer need to physically, or remotely, log in to a Windows computer to view and control its
services. Information for running and stopped services is displayed directly through SAM using the Service
Control Manager.

Services viewed in the Service Control Manager are polled every 25 seconds using WMI.

242

Pop-ups must be enabled in your browser to view the Service Control Manager.  2. 243 .Access the Service Control Manager (SCM) from the Node Details page You can access the Service Control Manager (SCM) through node details pages. On the Node Details page. On the Web Console. You may need to log in with an administrator account to perform this action. click a node.  3. click My Dashboards > Home. Click the option to open and manage the SCM. Clicking Service Control Manager opens the SCM in a new window and the services are sorted alphabetically.  1. In the All Nodes group. the Service Control Manager button can be found at the bottom of each Top 10 list. as highlighted below: The Service Control Manager button is not available on the Node Details page in situations where Top 10 lists are hidden.

Service Poll Interval This is used to specify the refresh frequency of the 25 seconds information reported by the service. 244 . Start monitoring this service. 3 minutes Timeout By default. Start and stop a service  1. or Restart service. At the top of the window. Service Action Job This reports the timeout for a service. Hovering the mouse over the row of any service will give you detailed information about that service.Use the Service Control Manager The Service Control Manager (SCM) shows all the services that are on the monitored computer. Click the row of a service to select it. Monitor a service with SAM  1. The Edit Properties section of the Component Monitor wizard opens. select Stop Service.  2. Start Service. Begin customizing the selected component monitor.  2. all available columns are shown. Services monitored by SAM are indicated by the application icon and name of the assigned application. Click Start monitoring this service in the row of the service to monitor. followed by the words. Services that are not monitored by SAM are indicated by the [+] symbol. The table below shows the default settings for the Service Control Manager: ACTION DESCRIPTION DEFAULT SETTING Service Job Life Time This is used to specify how long the information for a service 3 minutes exists.

as well as web-based reports that show all scheduled tasks configured across all servers in your environment. there is a dedicated Task Failure Report you can view on-screen or have emailed to you. The WSTM will not work for tasks from every level of the Task Scheduler Library.The Windows Scheduled Task Monitor The Windows Scheduled Task Monitor (WSTM) is a resource designed to provide you with quick visual access to the status of scheduled tasks configured on your Windows nodes. 245 . Additionally. This resource is hidden when the WSTM is not being monitored on a node. Only tasks from root directory can be monitored. The WSTM comes with an alert that will notify you of any task execution failures.

 n Only tasks from root directory can be monitored. The WSTM will not work for tasks from every level of the Task Scheduler Library.   246 . scheduled tasks on Windows 2008 or later cannot be polled by the Windows Scheduled Task Monitor (WSTM).  n The WSTM consumes five license units per node.Requirements for the Windows Scheduled Task Monitor The WSTM supports monitoring tasks on the following operating systems:  n Windows 2003 R2 SP2  n Windows 2008  n Windows 2008 R2  n Windows 2012  n Windows 2012 R2 Notes:  n When SAM is installed on Windows 2003 R2 SP2.

Enable the Windows Scheduled Task Monitor You may need to log in with an administrator account to perform this action. click Settings > Manage Nodes.  2.  1. Complete the wizard as instructed. The Windows Schedule Tasks option is checked when tasks are already being monitored.  3. On the Web Console. or is hidden when a task is not found on the target machine. is unchecked by default when at least one task is found on the target machine. Click Next and then select Windows Scheduled Tasks. Click [+] Add Node and then select the Windows Servers: WMI and ICMP option and enter the credentials. 247 .  4.

and then click a Windows node to be taken to the Node Details page for that node.  1.  2.  3. the Windows Schedule Task Monitor resource is only on the Node Details view of the monitored server. as shown: When monitored. find the Windows Scheduled Task resource.Access the Windows Scheduled Task Monitor You can access the Windows Scheduled Task Monitor through the All Nodes resource in the Orion Web Console. 248 . On the Node Details page. Expand the Windows tree by clicking Windows. On the Web Console. click My Dashboards > Home > All Nodes resource.

 n From Edit Settings.  n Hovering over any item in the Task Name column will provide detailed information about the listed task. you can:  n Change the polling frequency  n Change the polling timeout period  n Change credentials  n Add custom notes You can also use the Windows Task Monitor in alerting: Alert me when task last run result is non successful 249 .  n Sort the display by clicking the head of each column. at the bottom of the resource.Understand the Windows Scheduled Task Monitor Only tasks from root directory can be monitored. The WSTM will not work for tasks from every level of the Task Scheduler Library.

(0x8004130A) One or more of the properties required to run this task have not been set. (0x41300) The task is ready to run at its next scheduled time. but not all specified triggers will start the task. (0x8004020D) Cannot modify or delete an object that was not added using the COM+ Admin SDK. but may fail to start. (0x41304) There are no more runs scheduled for this task. (0x41305) One or more of the properties that are needed to run this task on a schedule have not been set. (0x8004130D) The task object could not be opened. 250 . (0x41302) The task will not run at the scheduled times because it has been disabled. (0xA) The environment is incorrect. (0x8004130C) The Task Scheduler service is not installed on this computer. (0x4131C) The task is registered.Windows Scheduled Task Monitor returned status codes Below is a list of status codes and their meanings that may appear in the WSTM resource: Hex Status Description Code (0x0) The operation completed successfully. (0x41301) The task is currently running. (0x41325) The Task Scheduler service has asked the task to run. (0x1) Incorrect or unknown function called. (0x41307) Either the task has no triggers or the existing triggers are disabled or not set. (0x8004130B) There is no running instance of the task. (0x2) File not found. (0x41303) The task has not yet run. (0x80041309) A task's trigger is not found. (0x41308) Event triggers do not have set run times. (0x41306) The last run of the task was terminated by the user. (0x4131B) The task is registered. Batch log in privilege needs to be enabled for the task principal.

(0x8004131D) The task XML contains too many nodes of the same type. (0x80041328) The task settings do not allow the task to start on demand. (0x8004130F) No account information could be found in the Task Scheduler security database for the task indicated. (0x80041314) The task has been configured with an unsupported combination of account settings and run time options. (0x800700C1) Not valid Win32 application. (0x80041323) The Task Scheduler service is too busy to handle your request. (0x8004131A) The task XML is malformed. (0x80041320) The task will not run because the user is not logged in. (0x80041311) Corruption was detected in the Task Scheduler security database. (0x80041324) The Task Scheduler service attempted to run the task. (0x8004131F) An instance of this task is already running. but the task did not run due to one of the constraints in the task definition. (0x80041317) The task XML contains an element or attribute from an unexpected namespace. (0x80041322) The Task Scheduler service is not available. Please try again later. (0x80041316) The task XML contains an unexpected node. (0x80041327) The task has properties that are not compatible with earlier versions of Windows. (0x80041319) The task XML is missing a required element or attribute. (0x80041321) The task image is corrupt or has been tampered with. 251 . (0x8004131E) The task cannot be started after the trigger end boundary.(0x8004130E) The object is either an invalid task object or is not a task object. (0x80041318) The task XML contains a value which is incorrectly formatted or out of range. (0x80041313) The task object version is either unsupported or invalid. (0x80070002) The system cannot find the file specified. (0x80041312) Task Scheduler security services are available only on Windows NT. (0x80041315) The Task Scheduler Service is not running. The database has been reset. (0x80041310) Unable to establish existence of the account specified.

(0x800704DD) The operation being requested was not performed because the user has not logged on to the network. For a complete list of error codes. The specified service does not exist. 252 . (0xC000013A) The application terminated. (0xC06D007E) Unknown software exception. see Task Scheduler Error and Success Constants. (0x800704C7) The operation was canceled by the user.

Not Available. to be triggered: Available Not Available Undefined Task Success Trigger Not Found Default Task Ready Task Not Ready   Task Running Task Not Running   Task Disabled Service Not Installed   Task Has Not Run Cannot Open Task   Task No More Runs Invalid Task   Task Not Scheduled Account Information Not Set   Task Terminated Account Name Not Found   Task No Valid Triggers Account Database Corrupt   Event Trigger No Security Services   Some Triggers Failed Unknown Object Version   Batch Log on Problem Unsupported Account Option   Task Queued Service Not Running     Unexpected Node     Name space     Invalid Value     Missing Node     Malformed XML     Too Many Nodes     Past End Boundary     Already Running     User Not Logged On     Invalid Task Hash     Service Not Available   253 . or Undefined.WTSM status The following table lists the conditions that must be met in order for a status of Available.

  Service Too Busy     Task Attempted     Task Not V1 Compatible     Start On Demand     Service Does not Exist     No File Specified     Cannot Delete Object     Not Valid Application     Incorrect Function     File Not Found     Environment Is Incorrect     Application Terminated     Unknown Software Exception     Operation Canceled   254 .

You can also select which event logs you want to monitor from within this resource. Event logs can be filtered by log type.The Real Time Event Log Viewer View Windows event logs in real time using the WMI protocol with the Real Time Event Viewer (RTEV). 255 . and the level of severity. event source.

In the All Nodes group. click My Dashboards > Home. Click Real-Time Event Viewer. On the Web Console.Access the Real Time Event Viewer from the Node Details page You may need to log in with an administrator account to perform this action. 256 .  3.  2. and then locate the Real Time Event Viewer in the Management resource.  1. click a node. Pop-ups must be enabled for the RTEV to be viewed.

Filter events in the Real Time Events Viewer Different events are displayed in the RTEV depending on the log type and filters you choose. Select only the sources you want to keep when the filter is applied. After you select a Log Type from the drop-down list.  2. Filter collected events After the events of the selected Log Type are collected and displayed in the window on the right. SAM immediately begins collecting these logs and display them in the message window to the right. as shown: Select a log type Select a Log Type from the drop-down menu. Select Custom Sources from the Event Sources drop-down menu. you can filter the results with various criteria.  1. as highlighted below: 257 .

258 . Click Apply Filter to have the events filtered and displayed.  4. 3. Select the type of messages you want the filter to keep by selecting the Event Level.

Reading events in the Real Time Events Viewer After filtering is complete. The Level column icons correspond to the Event Level icons in the legend of the events pane. Click the green bar to add these new events to the display window. hide and unhide the filtering pane on the left by clicking either of the two arrows. Clicking any message in the display window brings up a message box providing the entire message along with additional details. a green bar at the top of the window indicates that new events have arrived. Should any new events occur while this window is open. highlighted in red: The display window shows a list of the most recent events. 259 .

This takes you to the Add Component Monitor wizard and lets you to create an application based on your selection.Monitor events in the Real Time Events Viewer Begin monitoring events from within the RTEV by clicking Start Monitoring in the Message Details view. Component Monitor Wizard After you begin the Component Monitor Wizard. 260 . you encounter the option to Disable Keyword Matching. the Include Events drop-down menu will help you filter results.

issues.  n Click any performance counter within a resource to view the Exchange Performance Counter Details page. modify. and a host of performance counters without the use of agents or templates.  2. you can access additional Exchange details pages including performance counter. databases. verify you have the correct requirements and account permissions.  3. 261 . Expand the AppInsight for Exchange tree and click [+]. click [+]. It was designed exclusively for the Exchange Mailbox role that offers a detailed view of your Exchange environment. Through the resources. The AppInsight for Exchange Details view provides a customizable view of resources for monitoring your Exchange servers and services. You can add AppInsight for Exchange automatically for your environment through Discovery or adding it to a node manually. and mailbox details. Expand the node tree. View the AppInsight for Exchange Details page: You may need to log in with an administrator account to perform this action. complete configuration.  1. and then click the application. AppInsight uses the Exchange credentials you enter to directly access the servers. locate the All Applications resource by clicking My Dashboards > Applications > SAM Summary. Navigating AppInsight for Exchange AppInsight for Exchange can be found in the All Applications resource on the Application Summary view. AppInsight for Exchange is considered an application and reports data to SAM through a set of component monitors. see 5 Tips to Optimize Exchange Server for Improved Performance. Advanced Manual Configuration of AppInsight for Exchange provides additional configuration and usage options. To further refine AppInsight for Exchange monitoring:  n Customize the view of resources  n Add and remove component monitors in the AppInsight for Exchange template  n Enable. Before adding AppInsight. database. After it is applied to a node.AppInsight for Exchange Applnsight for Exchange monitors virtually every aspect of your Exchange environment. On the web console. and collect data at polling intervals. Manual configuration is recommended for experienced Exchange administrators. and thresholds To optimize your Exchange server performance. and use alerts for receiving notifications of Exchange server usage. It provides detailed metrics on mailboxes.

 n Click any database within a Database resource to view the AppInsight for Exchange Database Details page. 262 .

Your environment may have a unique baseline and performance expectation compared to the default thresholds. 263 .  n Watch and monitor the alerts for two weeks. to allow for generating stable baselines.  n Click any user name within a Mailbox resource to view the AppInsight for Exchange Mailbox Details page.  n You can create customized NOC and resource views including AppInsight for Exchange resources for different user groups in your company and organization. You can configure to use the new baselines for refining monitoring and alert actions for the usage and performance in your specific environment.  n When first testing alerts. Recommendations for AppInsight for Exchange When using and configuring AppInsight for Exchange. only assign the alerts to your own or other tester email addresses. Resources and polling have varied polling intervals at the minutes to hours to an amount per day. After the first 24 hours. and best practices:  n After first configuring AppInsight for Exchange. tricks. SolarWinds recommend the following tips. your resources should all start reporting data. you may not receive active data for all of your resources and alerting for the first 24 hours.

 n To provide organization-wide capability. creating or deleting users. select AppInsight for Exchange.)  n In order to gather information. If you convert an SNMP managed node to WMI. check the following requirements and permissions:  n Local administrator permissions are required for automatic configuration.  4. You do not need these credentials for monitoring Exchange.  5. Before configuring.Configure AppInsight for Exchange on nodes To configure and monitor Exchange servers in SAM. without providing any domain or local access on the Exchange server. On the Web Console. It also prevents abuse by an unauthorized user. Complete the information on the Define Node step.  n Nodes that are not added via WMI do not display in the List Resources dialog. add AppInsight for Exchange to a node manually or through Discovery. SolarWinds recommends adding this application on WMI managed nodes. Membership to this group gives the user object read-only access to the entire Exchange environment. the user object must be assigned the Mailbox Search management role within Exchange. Add via Discovery Add AppInsight for Exchange to a node via Discovery:  1. On the Choose Resources step in the Add Node Wizard. AppInsight for Exchange should only be applied to the physical IP address of each mailbox server in the DAG individually. To configure the account. Click Next and complete the wizard as instructed.  n Monitoring an Exchange Database Access Group (DAG) by way of a Virtual IP address (VIP) is not supported. the service account (Domain User) needs to be a member of the View-Only Organization Management group. and so on. it must be a member of the Local Administrators group. To convert SNMP managed nodes to WMI. see Promoting a Node to WMI Monitoring AppInsight and SAM do not support the following:  n Multiple instances of Exchange on the same server are not supported.  3. for example (modifying Exchange environment configuration. click Settings > All Settings > Add a Node. Navigate to the All Applications resource and click your AppInsight for Exchange application. and then click Next.  2. interface statistics become lost. 264 .

From the Management resource. and then click Configure Server. 265 . Add via manual configuration Locate your Exchange node and add AppInsight for Exchange:  1. Navigate to the Node Details view by clicking any node. The list may take a few minutes to generate. Enter your Exchange credentials when prompted.  2. click List Resources.  6.

see the following:  n Advanced Manual Configuration of AppInsight for Exchange  n Troubleshoot permissions 266 . For more information for configuring AppInsight for Exchange. click Configure Server. click Submit. Click on the newly added AppInsight for Exchange application in this view and then enter your Exchange credentials when prompted. When done. Select Microsoft Exchange to enable AppInsight for Exchange data collection.  5. Navigate to the All Applications resource to verify the addition by clicking the Applications tab in the web console.  3.  4.  6. Once your credentials are entered.

When planning your application monitors. You can modify and add application monitors to shape your monitoring to your environment and company's needs. click Submit at the bottom of the page. click Settings > All Settings > SAM Settings > Manage Templates.Edit the AppInsight for Exchange template The AppInsight for Exchange template includes a number of component monitors configured to collect and report metrics for your environment. Some limitations may apply. The template includes a set of default application monitors for monitoring and managing Exchange. you can edit certain component monitors within the template.  2. You may need to log in with an administrator account to perform this action.  1. You can also make a copy of the template to edit. From here. Check the AppInsight for Exchange template in the list and click Edit. consider your business rules and the needs of different departments. When done editing. On the Web Console.  4. 267 .  3. creating different versions as needed by your business and needs.

The tool then reports back to SAM with the results. Once on the Exchange Server. If errors are reported. it will automatically remove and unregister itself. 268 . Once this tool completes remote configuration.0  n PowerShell v2.Advanced Manual Configuration of AppInsight for Exchange Manual configuration is only recommended for experienced Exchange administrators. The target machine must have the following:  n WinRM 2. the tool uses a custom PowerShell script to make configuration changes. see Configure AppInsight for Exchange on nodes. SAM will add the Mailbox Search Role to the Exchange server with the credentials provided.0  n IIS SAM will make the following configuration changes:  n Enable WinRM  n Enable Windows Authentication for PowerShell's web site  n WinRM and Windows Authentication configurations are performed remotely from SAM SAM uses a specially designed configuration tool to make the necessary changes for enabling AppInsight for Exchange.  n Configuration changes to enable AppInsight for Exchange  n Find Exchange credentials  n Manually configure the Exchange server  n Set PowerShell permissions for Exchange  n Find Exchange URL settings  n Changes that will be made to enable AppInsight for Exchange  n Edit the AppInsight for Exchange template Configuration changes to enable AppInsight for Exchange The configuration tool first transfers to the Exchange Server by using the Windows administrative share. you will be asked to configure Exchange. For quick credential configuration.

you can add a custom domain security group to define a specific type of administrator with specific permissions to the Local Administrators group. more mature environments.Find Exchange credentials For an account to access Exchange:  n The account must be a domain account.  n In order to modify IIS and PowerShell settings on the Exchange server. this is handled using GPOs. Run the following cmdlet in the Exchange Management Shell (EMS): Get-ManagementRoleAssignment -RoleAssignee “USER_IDENTITY” 269 . Verify you have valid Exchange credentials. Smaller organizations may perform this task manually. the account must be a Local Administrator.  n The account is recommended not to be a member of the Domain Administrators group. In larger. Typically.

the following items must be installed and configured on the server.0  n Set PSLanguageMode to FullLanguage for the PowerShell website  n Create a self-signed certificate  n Configure WinRM 2. (Ensure the location is set to either the domain where the account is located or Entire Directory. Define Exchange credentials Local accounts (Non-Domain) cannot access Exchange Management interfaces and therefore are not supported by AppInsight for Exchange. add this privilege using the Active Directory console.Manually configure the Exchange server To manually prepare an Exchange server for AppInsight for Exchange. Add the type in the Active Directory user name of the account you want to grant administrative privileges. see Troubleshooting Error Codes in AppInsight for Exchange. Before configuring:  n Make sure to have credentials and a proper Exchange account  n Review the configuration changes to enable AppInsight for Exchange Use the following instructions to configure Exchange:  n Define Exchange credentials  n Grant Exchange access  n Set mailbox search access  n Install PowerShell 2.  1.)  4.0  n Create a firewall rule  n Configure IIS  n Test the application For a list of possible configuration errors with solutions. Navigate to the Administrators group. For information on the Exchange account. On Windows 2012. Please select an Active Directory account or create a new one to use with AppInsight for Exchange. you can add an Active Directory group to the local administrators group and add the Active Directory user accounts to that group. Alternatively. 270 . open a Computer Management console. On the server where you wish to grant local administrative privileges. Save your changes. see Find Exchange credentials.  2.  3.

@{N='ObjectType'.AccountManagement.$GroupName) $LocalAdmin = $group.  2. run the following in a PowerShell session: $Recurse = $true $GroupName = 'Administrators' Add-Type -AssemblyName System. add the user name of the account you want to grant access to the Exchange organization. samaccountName. See Microsoft.GetMembers($Recurse) | select @{N='Domain'.ObjectType -eq "user"} Grant Exchange Access Granting Least Privilege access to the Exchange Organization can be accomplished using Active Directory Users and Computers (ADUC).GroupPrincipal]::FindByIdentity ($ct.Context.DirectoryServices. E={$_.AccountManagement $ct = [System.DirectoryServices.StructuralObjectClass}} -Unique</code> $LocalAdmin = $LocalAdmin | Where-Object {$_. E={$_. Open Active Directory Users and Computers (ADUC) and find he Microsoft Exchange Security Groups OU.com for detailed instructions.To verify the account and local group membership has been configured properly.Name}}.DirectoryServices. 271 .  1.ContextType]::Machine $group = [System.AccountManagement. From the View-Only Organization Management group.

0 If you have Microsoft Server 2012. open PowerShell in the Run as Administrator context. When the download is complete.0 is installed fully. If not.0. enter the following command: Get-ManagementRoleAssignment -RoleAssignee <Username of account> Install PowerShell 2. Set PSLanguageMode to FullLanguage for the PowerShell website The can be done on the IIS Manager on the Exchange server for the application settings of the default website and PowerShell virtual directory. If you have Microsoft Server 2008 R2. Create a self-signed certificate SolarWinds has created a PowerShell script to create a self-signed certificate suitable for AppInsight for Exchange. click Download.0 typically comes installed. To verify the management role has been properly assigned. open the EMS. Review the information on the web page. On the Update page. See Set PowerShell permissions for Exchange for details.Set Mailbox Search Access Mailbox Search access is required to determine attachment counts and sizes.com/fwlink/?LinkId=177670). This can be found at: Self-signed Certificate PowerShell script for AppInsight for Exchange. To create a self-signed certificate using PowerShell and CertEnroll. See Microsoft. PowerShell 2. Typically.com for detailed installation instructions.  3. Type: New-ManagementRoleAssignment -Role "Mailbox Search" -User <Username of account being granted access> and then press Enter.com for detailed instructions. Determine if PowerShell 2. See Microsoft. This can be granted using the Exchange Management Shell (EMS). this can be done from the Server Manager. Navigate to Windows Management Framework (http://go. click Finish.  2.  2. you need to fully install PowerShell 2. and then click the link for the download of the Windows Management Framework Core for your platform in the Download Information section. From the Start menu. If you choose not to download this script.microsoft. 272 . PowerShell 2.  1. If you need to download and install PowerShell:  1.0 comes fully installed.  3. you can create your own self-signed certificate with the following instructions and code:  1. You may also need to set the PowerShell permissions. You need to recycle the MSExchangePowerShellAppPool application pool.

NotAfter = $cert. "") For more information.1" $key.MachineContext = 1 $key.CObjectIds.5.CX509PrivateKey.0  1.0xd01f01ff.Encode() $enrollment = new-object -com "X509Enrollment.KeySpec = 1 $key.199.SecurityDescriptor = "D:PAI(A.1") $ekuoids = new-object -com "X509Enrollment.106_Solarwinds_ Exchange_Zero_Configuration” $name = new-object -com "X509Enrollment..Encode("CN=TestServer".Issuer = $cert.X509Extensions.Subject = $name $cert.Length = 1024 $key.1" $enrollment.BA) (A.InitializeEncode($ekuoids) $cert = new-object -com "X509Enrollment. To configure WinRM on an Exchange server. Configure WinRM 2.Add($ekuext) $cert.1" $ekuext.CX509Enrollment.  2.0x80120089.5.NS)" $key.InstallResponse(2.. open a command prompt in the Run as Administrator context.CX509ExtensionEnhancedKeyUsage.1" $serverauthoid.. 273 .Create() $serverauthoid = new-object -com "X509Enrollment.ProviderName = "Microsoft RSA SChannel Cryptographic Provider" $key.add($serverauthoid) $ekuext = new-object -com "X509Enrollment.InitializeFromValue("1.1" $name.. 0) $key = new-object -com "X509Enrollment.SY)(A.Subject $cert.7. $certdata.." For Example: “10. see Generating a Certificate.InitializeFromRequest($cert) $certdata = $enrollment.. Enter the following code: The CN (Subject) should be in the following format: "<IP Address of Server>_ Solarwinds_Exchange_Zero_Configuration.NotBefore = get-date $cert. $key.1" $ekuoids.CreateRequest(0) $enrollment.1.0xd01f01ff.CObjectId.AddDays(3650) $cert.NotBefore.. 0.1" $cert.. "") $cert.CX500DistinguishedName.CX509CertificateRequestCertificate.6.3.3.15.InitializeFromPrivateKey(2..

Enabled = $true $rule.ApplicationName = $appName } if ($serviceName -ne $null) { $rule.Add($rule) } 274 .Protocol = 6 #NET_FW_IP_PROTOCOL_TCP $rule.EdgeTraversal = $false $fw.Profiles = 7 # all $rule.  2.Grouping = "@firewallapi.serviceName = $serviceName } $rule.  2.FWRule $rule.Name = $name if ($appName -ne $null) { $rule.Hostname="<IP Address of Server>_Solarwinds_Exchange_Zero_ Configuration"} and then press Enter.LocalPorts = $tcpPorts $rule. Open PowerShell using Run as Administrator. Create a function for adding firewall rules using the following code: function Add-FirewallRule { param( $name. $tcpPorts.Rules.  3. Create a firewall rule  1.Action = 1 # NET_FW_ACTION_ALLOW $rule. Type: winrm create winrm/config/listener?Address=*+Transport=HTTPS @ {Port="5986". $appName = $null. Verify the configuration by typing the following: winrm get winrm/config/listener?Address=*+Transport=HTTPS. $serviceName = $null ) $fw = New-Object -ComObject hnetcfg.-23255" $rule.dll.fwpolicy2 $rule = New-Object -ComObject HNetCfg.CertificateThumbprint="<Thumbprint value of certificate>".

Configure IIS  1.  5. Type: (Get-WebConfiguration system. Verify the rule was created. Run the function to create the firewall exception for WSMAN using the following command:Add- FirewallRule "Windows Remote Management" "5986" $null $null  4.  4. 275 .enabled and then press Enter to determine if Windows Authentication has been configured. Change the directory to C:\Windows\System32\Inetsrv. Type: Import-Module WebAdministration and then press Enter.webServer/security/authentication/windowsAuthentication 'IIS:\sites\Default Web Site\PowerShell').webServer/security/authentication/windowsAuthentication and then press Enter.  3. Open a command prompt in the Run as Administrator context.exe unlock config - section:system.  6. Open PowerShell in the Run As Administrator context. Type: appcmd.  2.  3.

 ii. then take the following steps:  i.enabled to verify the setting has changed.  v.exe lock config - section:system. Type: Set-WebConfiguration system.webServer/security/authentication/windowsAuthentication 'IIS:\sites\Default Web Site\PowerShell' -value True and then press Enter. 7. Type: (Get-WebConfiguration system. Close the command prompt.webServer/security/authentication/windowsAuthentication 'IIS:\sites\Default Web Site\PowerShell'). you do not need to do anything. If the value returned is True. type: appcmd. In the open command prompt. 276 . If the value returned is False.webServer/security/authentication/windowsAuthentication and then press Enter.  iv. Close PowerShell.  iii.

Test the application  1. When you are finished with configuration. your screen should look like the illustration below: 277 .  2. navigate to the Application Edit page and click Test. If successful.

Open Notepad and copy and paste the following text .0.0.) 278 . you need to set the permissions.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine] "ApplicationBase"="C:\\Windows\\System32\\WindowsPowerShell\\v1.  2. open the PowerShell console.  1. Execute this command:Set-PSSessionConfiguration Microsoft.ConsoleHost.0. (A reboot may be required. Version=1.ConsoleHost.0 or higher.  4. and select Allow. Enable Full Control under the Permissions for Everyone group. On the remote computer.0" "PSCompatibleVersion"="1. or installing PowerShell 2. These permissions are required for AppInsight for Exchange and the Exchange server.0" 2.  3.0 was installed on Windows Server 2012 with Exchange 2013 and subsequently uninstalled. Ensure that the group containing the polling user has access to Microsoft PowerShell.dll" "PowerShellVersion"="2. You can create the required registry key by following these instructions:  1. 2. PublicKeyToken=31bf3856ad364e35. Resolving errors after a reinstall If PowerShell 2. ProcessorArchitecture=msil" "ConsoleHostModuleName"="C:\\Windows\\System32\\WindowsPowerShell\\v1. Culture=neutral.  5.Set PowerShell permissions for Exchange After verifying an install. Verify all permissions are set and saved.reg and then double-click it to add it to the registry. Security patches or updates may also cause this issue.0. a Microsoft error removes the required registry key for remote PowerShell to work properly.0" "RuntimeVersion"="v2.PowerShell. and click OK.Powershell - ShowSecurityDescriptorUI -Force The permissions dialog should appear. Save the file as PowerShellv1.0. Windows Registry Editor Version 5.50727" "ConsoleHostAssemblyName"="Microsoft.PowerShell.0\\Mi crosoft.

Open the IIS Manager and navigate to the default website then to the PowerShell virtual directory. By default. Verify a server's WinRM PowerShell instance:  1. If either of these have been modified. The two items of interest for the URL are Port and URLPrefix. Open a command prompt using Run as Administrator. you should verify the PowerShell Exchange and WinRM URLs are correct.  2.  2. and do not match the default values.  n Exchange: https://${IP}/powershell/  n WinRM: https://${IP}:5986/wsman/ Verify the PowerShell instance used by Exchange on a server:  1. Verify the Virtual Path value (typically in the Advance Settings). Enter the command winrm get winrm/config/listener?Address=*+Transport=HTTPS to get the current configuration for the HTTPS protocol. where ${IP} is the IP address of the server node being added.Find Exchange URL settings As part of the AppInsight for Exchange configurations. AppInsight for Exchange uses the following URLs for the Exchange and WinRM sessions. edit the AppInsight for Exchange application with the correct values:  n PowerShell Exchange URL: https://${IP}/powershell/  n PowerShell Windows URL: https://${IP}:9886/Custom_wsman/ 279 .

the value of Hostname must match the CN of the certificate listed in the Certificate Thumbprint property: For more information.Additionally. see: 280 .

 n Manually configure the Exchange server  n Set PowerShell permissions for Exchange 281 .

msg .tmp .pps .arj .mp3 .pdf .accdb .xls 282 .gif .sql .bmp .jar .wks .vbs .png .svg .iso .mid .xps .mobi .gzip .wmv .bin .psd .hta .inf .epub .doc .htm .pot .avi .cab .wma .txt .img .ini .mdb .wav .xml .dot .jpeg .bak .pst .pub .ps1 .tar .csv .eml .log .rtf .mov .Attachment extensions acknowledged by AppInsight for Exchange The following table lists the default attachment extensions that are acknowledged by AppInsight for Exchange: .mmp .zip .lnk .swf .jpg .ppt .flv .bat .mpeg .cmd .rar .reg .

Website and Application Pool performance issues. disable sites when unused instead of deleting them. see AppInsight for IIS requirements and permissions. You may need to log in with an administrator account to perform these actions. To start using AppInsight for IIS. AppinSight for IIS leverages PowerShell to collect data about your IIS servers. easily stop or restart servers and pools as required. click My Dashboards > SAM Summary. On the Web Console. apply it to a monitored node through Discovery or manually by node. The following reports are installed for use with AppInsight for IIS:  n IIS SSL Certificate Expiration Report  n Site Connections Report  n Site Log Size by File  n Site Size by File Navigate the AppInsight for IIS details view Access AppInsight for IIS through the All Applications resource in the SAM Summary page. Enable sites anytime you need them through the Site Details pages in AppInsight for IIS. For full details on requirements. You also need WinRM installed and configured on the Orion server and monitored IIS servers. You need PowerShell 2. site. Locate the All Applications resource and expand the AppInsight for IIS tree by clicking [+]. To reduce alert noise. The default IIS Application name is Microsoft IIS. see:  n AppInsight for IIS requirements and permissions  n Configure AppInsight for IIS on nodes  n Manually configure AppInsight for IIS  n Troubleshooting AppInsight for IIS For advanced managing of IIS sites. As sites and application pools change through the IIS Manager.AppInsight for IIS AppInsight for IIS automatically monitors your IIS environment to automate identification of IIS Server. This option and others are available in the Management resource per ISS server. the information and connections update in SAM. Enter access credentials to add and monitor the IIS servers. To view the AppInsight for IIS details view:  1. and application pool. To quickly set up and use AppInsight for IIS. As you determine issues. 283 . The dashboard provides ease of monitoring with at-a- glance performance metrics for sites and applications pools. updated through access to the IIS.0 or later installed on the Orion server. disable any alerts associated with those disabled sites.  2.

The Application Pools resource lists up to 5 instances of IIS application pools. click a performance monitor in any resource. If an issue occurs with an application. Click an IIS application to view it.  3. The Sites resource lists the sites (front and backend) for the IIS server. connections. To view the Performance Counter details view. Click a site to view additional site details including response time. 284 . it may only affect other applications in the pool. not all applications in your environment. Click a pool to view additional worker process details. You use application pools to separate out applications from one another. and requests.

Add via Discovery You can also quickly and easily configure AppInsight for IIS during Discovery. Or you can automatically add AppInsight during Discovery.  5.  3. Before adding.  4. Add via manual configuration Locate your IIS node and add AppInsight for IIS: 285 . and then click Configure Server. Navigate to the All Applications resource and click your AppInsight for Exchange application. On the Choose Resources step in the Add Node Wizard. and then click Next.  6.Configure AppInsight for IIS on nodes For existing nodes currently managed in the Orion Web Console. Complete the information on the Define Node step.  2. On the Web Console. you can add AppInsight to the node through the Node Details page.  1. Click Next and complete the wizard as instructed. review the AppInsight for IIS requirements and permissions. Enter your Exchange credentials when prompted. click Settings > All Settings > Add a Node. select AppInsight for IIS.

 5. Navigate to the All Applications resource to verify the addition by clicking the Applications tab in the web console. 286 . Select Microsoft IIS to enable AppInsight for IIS data collection. When done.  4.  2. click List Resources. From the Management resource. Navigate to the Node Details view by clicking any node. Click on the newly added AppInsight for IIS application in this view and then enter your IIS credentials when prompted. 1. click Submit.  3.

 6. Click Configure Server to complete. click Configure Server.  7. Once your credentials are entered. see:  n AppInsight for IIS requirements and permissions  n Edit the AppInsight for IIS template 287 . For more information.

When done editing. including threshold values. component monitor description.  4.  3. You may need to log in with an administrator account to perform this action. And like other applications.  2.Edit the AppInsight for IIS template The AppInsight for IIS application behaves like any other application in SAM. Check the AppInsight for IIS template in the list and then click Edit. Edit the AppInsight for IIS Template  1. From here. you can edit certain component monitors within the template. click Submit at the bottom of the screen. Some limitations may apply. click Settings > All Settings > SAM Settings > Manage Templates. and so on. number of records to retrieve. On the Web Console. the AppInsight for IIS template can be edited. 288 .

Configure AppInsight for IIS on nodes.0 and the WebAdministration snapin  2. Create a firewall rule  5. For automatic AppInsight for IIS configuration see. 289 . Create a self-signed certificate  4. visit the sections below in order and take the steps outlined to manually configure the remote computer. Update WsMan limits  6. Set execution policy on the target computer  3. Important: Ensure that Windows Remote Management (WS-Management) is running and that this service's Startup Type property is set to Automatic. Install PowerShell 2. Once this is verified.Manually configure AppInsight for IIS In the event automatic configuration of AppInsight for IIS failed. Create a WinRM listener You can also edit the Edit the AppInsight for IIS template. continue manual configuration in the order listed below:  1.

net/learn/manage/powershell/installing-the-iis-powershell-snap-in. download and install the PowerShell WebAdministration snapins found at the following link: http://www. On the Update page.0 on Windows Server 2008 The following steps are not necessary for Windows Server 2008 R2 and Windows Server 2012. Navigate to Windows Management Framework (http://go.  4. For Managed Nodes with IIS 7. Review the information on the web page. click Finish.  2.microsoft.0 and the WebAdministration snapin The following procedures outline the installation of PowerShell and the required snapins. When the download is complete.0  1.  3.microsoft. Install PowerShell 2. click Download.iis.0 on Windows Server 2008 and 2008 R2 Installation of PowerShell 2.com Install the WebAdministration Snapins. For installation instructions. Download and Install PowerShell 2. The IIS PowerShell Snap-in requires the following prerequisites  n Windows Server 2008 or higher  n Microsoft PowerShell 2. and then click the link for the download of the Windows Management Framework Core for your platform in the Download Information section. Download PowerShell 2.Install PowerShell 2.0 can typically be done from the Server Manager as shown below.0 290 . visit www.0.com/fwlink/?LinkId=177670).

 2. the IIS PowerShell snap-in is registered automatically.  2.  n IIS 7. Run the MSI file to install the IIS PowerShell Snap-in.PSC1 file located in the $env:programfiles\IIS\PowerShellProvider directory: PS C:\> & "$env:programfiles\IIS\PowerShellSnapin\iisConsole. The prompt of the new PowerShell command window is set to "IIS:\" . Navigate to Start > All Programs > IIS 7.psc1" 291 .0 Install the IIS PowerShell snap-in  1.the root of the IIS snap-in namespace. Manual Registration If you want to use the IIS PowerShell snap-in from an existing PowerShell command window. Automatic Registration by using the IIS PowerShell Management Console The IIS PowerShell snap-in setup creates a new program menu shortcut. you have to register the IIS snap-in manually. By starting this shortcut. The IIS PowerShell Snap-in is available as x86 and x64 version. Use the PowerShell snap-in PowerShell snap-ins like the IIS PowerShell Snap-in have to be registered with PowerShell.0 Extensions > IIS PowerShell Management Console. There are two ways to do this:  1. You can do this by simply executing the IISConsole. Download the 32-Bit version or 64-Bit version.

Set execution policy on the target computer For AppInsight.  2.  1. the Execution Policy needs to be set to RemoteSigned. Enter the following command: Set-ExecutionPolicy RemoteSigned 292 . Open a PowerShell session in the Administrator context (Right-click and select Run as Administrator).

com/Success_Center/Server_%26_Application_Monitor_(SAM)/AppInsight_for_ IIS:_Create_certificates Once downloaded.ps1' 192. 293 .solarwinds.168.2.2. This can be found at: https://support. The following parameters apply:  n IP address: Mandatory  n Certificate lifetime in days: Optional You can run this script with the default arguments from the PowerShell console or specify each one.69 3650 where 192. For example: & '.168.Create a self-signed certificate SolarWinds has created a PowerShell script to create a self-signed certificate suitable for AppInsight for IIS. execute the script by right-clicking it and selecting.650 days (10 years).69 is the IP address of the node to be monitored by AppInsight for IIS and 3650 is 3. Run with PowerShell.\Create self-signed certificate script.

\Add firewall rule. as in the example above that uses port 5988.  n With two parameters: Non-default custom port and rule name You can run this script with the default arguments from the PowerShell console or specify each one. "Windows Remote Management HTTP/SSL" for port 5986.ps1' 5988 "My custom firewall rule name" The default port for this rule is 5986 and does not need to be specified. The following parameters apply:  n Without parameters: The rule is created with the default name. execute the script by right-clicking it and selecting.solarwinds. must be specified.com/?title=Success_Center/Server_%26_Application_Monitor_(SAM) /AppInsight_for_IIS:_Create_a_firewall_rule Once downloaded. For example: & '. Run with PowerShell.Create a firewall rule SolarWinds has created a PowerShell script to create a firewall rule. This can be found at: https://support. Custom ports. 294 .  n With one parameter: Non-default custom port.

Default value is 5  n maxShellsPerUserDefaultValue .com/?title=Success_Center/Server_%26_Application_Monitor_(SAM) /AppInsight_for_IIS:_Update_WsMan_limits Once downloaded.\Update WsMan Limits. The following parameters apply:  n maxConcurrentUsersDefaultValue . Run with PowerShell. execute the script by right-clicking it and selecting. SolarWinds has created a PowerShell script to update the WsMan limits suitable for AppInsight for IIS.solarwinds. This can be found at: https://support.Default value is $false You can run this script with the default arguments from the PowerShell console or specify each one. For example: & '.ps1' 295 .Default value is 5  n maxMemoryPerShellMBDefaultValue .Default value is 150  n serviceRestartRequired .Update WsMan limits WsMan provides methods and properties used to create a session.

​Hostname="<IP Address of Server>_Solarwinds_Zero_ Configuration"} and then press Enter. 296 . open a command prompt in the Run as Administrator context.  2. use the following steps to configure the listener on an available port by changing "5986" to an available port number throughout these steps.CertificateThumbprint="<Thumbprint value of certificate>".Create a WinRM listener Important: If you received the following error: An HTTPS listener currently exists on port 5986.  1. Type: winrm create winrm/config/listener?Address=*+Transport=HTTPS @ {Port="5986". To configure WinRM on an IIS server.  3. Verify the configuration by typing the following: winrm get winrm/config/listener?Address=*+Transport=HTTPS.

Find IIS URL settings By default. Additionally. the value of Hostname must match the CN of the certificate listed in the Certificate Thumbprint property. Type: winrm get winrm/config/listener?Address=*+Transport=HTTPS to get the current configuration for the HTTPS protocol. Open a command prompt in the Run as Administrator context. where ${IP} is the IP address of the server node being added. 297 .  2. WinRM: https://${IP}:5986/wsman/ Verify a server's WinRM PowerShell instance  1. AppInsight for IIS uses the following URL for the IIS and WinRM sessions.

298 .

click a database in the All Databases resource. AppInsight for SQL provides a level of detail and expert knowledge far beyond what a SQL template can provide. To navigate to the AppInsight for SQL details view. AppInsight for SQL monitors as an application using multiple component monitors. from the AppInsight for SQL Details view. See AppInsight for SQL requirements and permissions for requirements. By default. from the AppInsight for SQL Details view. Select an SQL instance to view by clicking it.  2. Expand the AppInsight for SQL tree by clicking [+]. see the following:  n Add AppInsight for SQL to a node via discovery  n Monitor an SQL named instance  n Edit the AppInsight for SQL template  n Monitor clusters with AppInsight for SQL Navigate the different AppInsight for SQL views Select a Microsoft SQL node through the All Applications resource on the Application Summary view. When applied to a Microsoft SQL instance. click My Dashboard > Applications > SAM Summary > All Applications resource. and more. You can also select an SQL Server view for all monitored Microsoft SQL applications. Click My Dashboards > Applications > SQL Server. On the Web Console.AppInsight for SQL SAM offers a detailed view of your SQL databases' performance without the use of agents or templates by using the AppInsight for SQL embedded application. click a performance counter in any resource. alerts. sub-views enable once you navigate to the AppInsight for SQL Details page. a list of all databases on the node. 299 . AppStack. To see the database details view.:  1. The view includes details. To see the performance counter details view.  3. To learn more about AppInsight for SQL. You may need to log in with an administrator account to perform these actions. allowing you to monitor virtually every aspect of your SQL instances and databases.

In the Network panel. see AppInsight for SQL requirements and permissions. 300 . To add through the Discovery Wizard:  1. To see all supported versions. Click Settings > Discovery Wizard. On the Web Console. To add an SQL server manually: When added.  4. check the appropriate AppInsight Application for the SQL server you will monitor. enter the IP addresses to scan through. Run through the screens as instructed. On the Choose Resources panel. all detected and supported Microsoft SQL Servers display. Select the polling method and continue. Click Next and complete the wizard as instructed. you need to select the appropriate Microsoft SQL server version from the AppInsight Applications list. Select the servers to add for monitoring as nodes.  3.  3.  4. Only supported versions of Microsoft SQL are located and displayed for monitoring. Enter the IP address or hostname for the SQL server.Add AppInsight for SQL to a node via discovery Quickly and easily add SQL servers as monitored nodes in the web console through the Discovery Wizard or by manually adding a node. Complete the wizard as instructed to add the nodes for monitoring.  1. You may need to log in with an administrator account to perform this action.  2.  2. On the Applications panel. click Settings > All Settings > Add Node.

add the named SQL instance as a node for monitoring:  1. you will not see AppInsight for SQL in the List Resources page for the server.  2.  6. check the appropriate AppInsight Application for the SQL server to monitor. If you have additional pollers and want to use templates to poll AppInsight for SQL. Open a command prompt. You may need to log in with an administrator account to perform this action. install the additional poller software on the poller(s) that are used. Enter the VIP address for the SQL named instance for the Polling Hostname or IP Address. click Settings > All Settings > Add Node. SAM includes a number of out-of-the-bow templates to modify or customize copies for your environment needs. If you do not know the VIP.  4. youcan add the SQL server as a node to monitor through the Orion Web Console. SAM provides additional monitoring options to collect and report metrics and status through AppInsight for SQL. use the following method:  1. You can add AppInsight for SQL to an actively monitored SQL node or add the SQL server through Discovery. Complete the wizard as instructed to add the node for monitoring. Monitor with AppInsight for SQL You need the VIP IP address of the SQL instance to add and monitor the SQL named instance. You want to capture the returned IP.  5. Without the proper software installations. You can define AppInsight for SQL monitoring through application monitor templates for SQL. On the Choose Resources step. 301 . then select the polling engine for that node.  2. Ping the server name as shown below.  3. On the Web Console. With the IP.Monitor an SQL named instance To monitor SQL named instances. Select a polling method.

the status color updates.  4. you can edit one or more templates by checking the boxes and selecting MultiEdit. These instances are default. Search or browse for SQL Server templates.  3. This instance is grayed until the poller has polled this node. In Microsoft. Monitor with application templates If you want to monitor without AppInsight for specific nodes. you need to add them as nodes for monitoring.  2.  5. You may want to assign multiple templates to the node. An instance is an installed Microsoft SQL in a specific directory path. we recommend using SQL templates. the SQL server is a series of instances. Data captured through the templates should display on the Node Details for those monitored nodes. Once polled. Select the SQL Server template you want to assign to SQL named instances to monitor. such as a service provider with SQL instances per customer. For example. not the server. All component or application monitors in a template relate to the SQL named instance. You can further modify the templates and application monitors as needed. To monitor these SQL named instances. You may not want AppInsight running for each of these instances. Once assigned. Click Settings > All Settings > SAM Settings > Manage Templates. 302 . unnamed instances or specifically named SQL instances. you may have a large amount of SQL database instances to monitor.  6. Assign these one at a time. You can assign and modify templates to monitor:  1. Enter the SQL named instance for the SQL Server Instance.

For more details. then click Submit. From the resource. On the AppInsight details page. click Submit.  1. Select resources as needed.  3. click Settings > All Settings > SAM Settings > Manage Templates. consuming data provided by the template application and component monitors. you can edit certain component monitors within the template. you can modify the listed resources.Edit the AppInsight for SQL template The AppInsight for SQL template includes numerous component monitors for providing data on all AppInsight monitored SQL instances.  2. When done editing. 303 . the details in AppInsight update to match. From here.  2. Each component monitor has different settings and options including threshold values.  4. On the Web Console. see the AppInsight for SQL template. You may need to log in with an administrator account to perform this action. click Edit in the upper right-hand corner of the resource. Check the AppInsight for SQL template in the list and then click Edit. Each resource provides data configuration and display options. number of records to retrieve. and component monitor description. Pertinent data for each resource is grouped together by default. If you modify these settings and configurations.  1.

Connect to the instance that you want monitor using SQL Management Studio.g. for example: “P111SQLV23 (cluster)” during the final step of the Add Node Wizard.Monitor clusters with AppInsight for SQL  1. “ping P111SQLV23”)  4. add it. the node name of the active cluster member populates.  2.  5. Enter the proper information and manually assign the Appinsight for SQL template to the node with the appropriate IP address. The application should begin polling. If the IP address represents a cluster.  6. Determine the IP address of the target node (e. If it is not. 304 . Execute the following query to make sure you have the proper target node and instance name: SELECT SERVERPROPERTY('ServerName')  3. It is recommended that you change the node name to something more easily understood. Make sure that the node with this address is being monitored by SAM.

You can create. remove. You can set separate thresholds to indicate warning and critical conditions. You would have component monitors to check tire pressure. and other important subsystems of that vehicle. each containing settings that define what is monitored and how to monitor it. To work with templates and monitors. water temperature.Manage application monitor templates and component monitors SAM includes a number of out-of-the-box templates to assign to nodes as needed. or if the battery voltage drops too low. Some types of component monitors allow you to set threshold conditions on the monitored parameters. Application Monitor Templates 305 . or add component monitors. There are several different types of component monitors. For example. Component Monitors Component monitors are the building blocks of SolarWinds SAM. engine RPM. battery voltage. you can set a warning threshold at 15%. see the following:  n Create and manage templates  n Modify and customize monitors  n Monitors and templates using WMI  n Assign and edit application monitors to nodes  n Create component monitors from the Component Monitor Wizard  n Scan nodes for applications  n Manage templates and groups  n Unmanage and manage assigned application monitors  n Script custom component monitors  n Application Monitor Thresholds  n Example tasks for application monitors For details on application templates and monitors. if you are monitoring the percentage of free space remaining on a volume. You can set alerts to give notification if the water gets too hot. pretend SolarWinds SAM is monitoring a car. SolarWinds recommends creating a copy of these template to customize. As an analogy. each with specific configurations and options to configure. and configure Application Monitor templates to monitor and report on all applications monitored in SAM. Templates have a number of component and application monitors. Each monitors the status and performance of a different aspect of an application. modify. and a critical condition at 5%. see SAM Component Monitor Types and SAM Template Reference.

Each actively monitors its assigned node according to its settings. The template can either be one included with SolarWinds SAM. Assigned Application Monitors An assigned Application Monitor runs its assigned component monitors at regular intervals. the user name and password usually differ for each node. thus overriding the template setting for the Credentials field. and you would select a different credential for each assigned Application Monitor. click Inherit From Template next to the setting. breaking the inheritance relationship between the component monitor and its template. when you assign the Dodge Charger template to a Dodge Charger vehicle. The difference between an assigned Application Monitor and a template is that the template is only a blueprint and does not perform any monitoring on its own. you can assign a pre-made template. that same change is rolled out to all assigned Application Monitors based on the template. Instead of creating component monitors one-by-one for every application server. you can define all the component monitors in a Dodge Charger template. For example. Assigned Component Monitors Assigned component monitors are created by assigning Application Monitor templates to server nodes. A template is a group of component monitors modeling the total availability and performance level of an application. and so forth. and then uses the status results from the component monitors to determine an overall status for the application. A complicated application such as Windows Server may require dozens of component monitors to accurately assess its current status and performance. the Application Monitor follows the Status Rollup Mode setting in the SolarWinds Web Console Settings to show either the worst status of the group or a warning status. pretend you want to monitor a fleet of 50. A template is only a blueprint and does not perform any monitoring on its own. engine RPM. Only after assigning the template to a server node does SolarWinds SAM conduct any actual monitoring on the node. For example. you now have a set of assigned component monitors for monitoring the vehicle’s tire pressures. or a custom template you make yourself. To continue the car analogy. 2010. To restore the inheritance relationship between a component monitor and its template. Instead of defining the component monitors for 50 cars. Continuing the car analogy. If you make a change to a template. If some of the component monitors are up and others are down. Component monitors inherit these initial settings from the template. You can override the template settings at any time. you can assign the included Microsoft Windows Server 2003-2008 template to your Windows 2003 and Windows 2008 computers and obtain vital statistics on all of them. Only after assigning the template to a server node are active assigned component monitors created. blue Dodge Charger automobiles. 306 .

To complete the car example. the fleet may be 95% available at a given time due to warnings for some of the cars. The following diagram illustrates the work flow involved in creating an application to be monitored by SAM. For example. you assign the Dodge Charger template to all the Dodge Charger vehicles to create the assigned Application Monitor for determining the overall status for your Dodge Charger fleet. 307 .

Create and manage templates You can create a new template. 308 . Creating a new template does not include any configured settings beyond the defaults for polling frequency and timeout (300). You can:  n Create a template. tags. For details on each monitor. description. To quickly create a template with multiple instance of a component monitor. you can modify the configurations and custom settings per monitor. You can access all templates through the All Settings > SAM Settings > Manage Templates page. See Component Monitor Types. click Settings > All Settings > SAM Settings > Manage Templates > Create New Template. you can access the help link.  2. editing in the template view) or Browse for Component Monitors (opens the Component Monitor Wizard). You can select Manually Add Component Monitors (select and add. This page includes all currently existing templates. You may need to log in with an administrator account to perform these actions.  4. When added. use the Component Monitor Wizard. assigned monitors. and thwack imports.  3. including a SolarWinds Windows Services template  n Assign a template to a node  n Edit a template  n Copy a template  n Export and import templates  n Delete templates  n Tag a template  n Change between 32-bit and 64-bit polling Create a template You can create a template through the SAM Settings page or when managing templates. You have two options for adding component monitors.  1. and polling frequency. When done. Add general information and settings for the template including the name. copy a current template. or manage existing templates. click Submit to save the changes. On the Web Console.

the port through which SolarWinds communicates with the SQL Server. use these instructions with variations based on the services you are monitoring:  1. Edit the template name to remove any extra spaces in the name. and select TCP Port Monitor. 309 . and tags.  n Service component monitors for the following windows services:  n SolarWinds Alerting Engine  n SolarWinds Network Performance Monitor  n SolarWinds Job Engine  n SolarWinds Job Scheduler  n SolarWinds Module Engine  n SolarWinds Syslog Service  n SolarWinds Trap Service  n HTTP component monitor to monitor port 80. Create an application template with the following component monitors:  n TCP port component monitor to monitor port 1433.  4. the port through which you access the SolarWinds Web Console. If so. a TCP port monitor for your SQL Server. Click Add Component Monitor. Add general information to the template including a name. Create a custom template (Example) The following procedure creates a SolarWinds SAM Application Monitor template that monitors a locally installed SQL Server instance.  2. The template is simplified by using the Windows Service component monitors. description. and click OK. On the Web Console. application resources may not list all applications.  3. Make sure the name of the template does not begin or end with a space. expand the Network Protocol Component Monitors list. Tags are used for searching or opening lists of templates per tag. and an HTTP monitor for the local Web Console. Click Submit to add. Create a SolarWinds Windows service application template You can create templates specifically for the following SolarWinds Windows services:  n SolarWinds Network Performance Monitor  n SolarWinds Job Engine v2  n SolarWinds Job Scheduler  n SolarWinds Module Engine  n SolarWinds Syslog Service  n SolarWinds Trap Service When creating the templates. Click Rename and name the TCP port monitor. click Settings > All Settings > SAM Settings > Create New Template.

By default.  4.  9.  4. see Discover and add network devices. 310 . Check an application template and click Edit. Click Add Component Monitor. can be modified. expand the Process and Service Component Monitors.  5. and click OK.  10. On the Web Console.  5. See Modify and customize monitors for details.  2.  5. then click OK. Assign a template to a node To begin monitoring with templates. You can change the name. and application monitors.  3. You can edit one or more monitors. including default SAM templates. the template collects and reports on polling data to the node according to the application monitors and configuration settings. You can also create a copy of a template and modify the copy. Ensure the Port Number field corresponds to the port you use for the SolarWinds Web Console port. When assigned and enabled. Click Rename.  11. To add a monitor. and more. you need to assign the application templates and monitors to a node. Enter or select the appropriate credentials. Enter or select the credential set to use when accessing the Windows service information. name the HTTP port monitor. this is port 1433. general settings.  7.  12.  6. update settings per monitor. click Settings > All Settings > SAM Settings > Manage Templates. Expand and filter through the options to add one or more monitors to the template.  2.  8. To add nodes. Specify the values for the Polling Frequency and Polling Timeout fields. name the SolarWinds Alerting Engine monitor. Ensure the Port Number field corresponds to the port used to communicate with the SolarWinds SQL Server instance. Check the template(s) to assign. Enter the name of the SolarWinds Alerting Engine service in the Net Service Name field. and click Assign to Node. click Add Component Monitor. To assign templates to nodes:  1. use the help option in the web console. and then check HTTP Monitor. On the Web Console. Setting a polling frequency below 30 seconds can result in erratic monitor behavior.  6. To review help information per monitor.  1. click Submit to save the changes. description. and check Windows Service Monitor and click Submit. Click Rename. Click Assign Application Monitors. When done.  3. Edit a template Every template. then click Submit. Click Add Component Monitor then expand the User Experience Component Monitors list. click Settings > All Settings > Settings > Manage Templates. Specify the node(s) to monitor and click Next.

If you want to completely modify a current template. click Settings > All Settings > SAM Settings > Manage Templates. data is not immediately removed from the database. Delete templates Before you begin:  n Deleting a template also deletes all of its assigned applications.Copy a template You can modify current templates. including any configured settings. Select an application template.apm-template extension.apm- template extension. On the Web Console. Select the application template you want to copy.  2. click Settings > All Settings > SAM Settings > Manage Templates. the name of the imported template is modified by appending (n) to the name.  1. Using a copy for a new template can make the process much faster than starting a new template without pre-filled monitors and configurations. The copied templates use the same name of the original name with ".  2. If you import a template with the same name as one of your existing templates. imported templates. If you receive an invalid file error. then select the template file. To export to a file:  1. or templates you created. click Import Export > Export as File. and click Copy. unzip the contents then import the template file. Export and import templates Templates can be exported and imported to share and use between all Orion users. or create a copy. A new template is added copying all of the application and component monitors. where n is an integer.  2. With copies. click Settings > All Settings > SAM Settings > Manage Templates. On the Web Console. The template packages into a file.  3. To import templates:  1. check the file format. 311 . both modified and unmodified. use a copy to keep the original. Ensure the imported file format is XML with . If you are importing a ZIP. Unzip templates before importing. but systematically updated every few minutes in the background. Click Submit. Exporting templates creates a file you can share on thwack with other users. Click Import/Export > Import > Browse. The template should be XML code with .  n To speed user interface interaction.Copy" appended. On the Web Console. then click Open. and click Save. you can use a base template from the default templates.

On the Web Console.  4. Select an AppInsight Application (Exchange. In the Platform to run polling job field. Check the template(s) to delete and then click Delete. On the Web Console. then click Tags.  2. separating multiple tag entries with commas. IIS) and then click Edit Application Monitor. Expand Advanced. and then click Override Template. SQL. Click Submit.  2. Using AppInsight applications with 32-bit polling on 64-bit computers via an agent prevents certain performance counters from collecting information. Select the templates you want to tag. The application templates included in SolarWinds SAM have already been tagged with several descriptive labels you can modify as you see fit. change the value to x64. Confirm deletion by clicking Yes.  2. On the Web Console. Select the templates you want to tag. Select the tags from the list. click Settings > All Settings > SAM Settings > Manage Templates.  4. Change to 64-bit polling at the template level:  1.  2. Click Add existing tag(s) or select the tags from the list. then click Submit.  5. 312 .  3. On the Web Console. Change between 32-bit and 64-bit polling You should use 64-bit polling on 64-bit OS systems. To remove tags:  1.  1. On the Web Console. To add tags:  1. click Settings > All Settings > SAM Settings > Manage Templates. Change to 64-bit polling at the application resource level:  1.  3. You may need to log in with an administrator account to perform these changes.  2. click Settings > All Settings > SAM Settings > Manage Templates. then click Submit.  3. Type the tags. Tag a template Tags are descriptive labels that help you classify and sort your application templates on the Manage Application Monitor Templates page. click Settings > All Settings > SAM Settings > Manage Templates.  3. click My Dashboards > Applications > SAM Summary. then click Tags > Remove Tags. Select an AppInsight application and click Edit.

 3. and in the Platform to run polling job on field. 313 . Expand Advanced. change the value to x64.

To modify the specific configurations per monitor. drag and drop them in the table view.  n Test: Run a communication test on the monitors using agent or agentless communication as configured. the Fetching Method for the three Services selected can be changed from RPC to WMI. and disable or delete templates.  n Assign Credentials: Modify the credentials as needed for the selected monitors. Every template consists of one or more application or component monitors.Modify and customize monitors Through the Manage Application Templates page.  n Delete: Permanently removes the monitor. add new monitors. You can modify each of these monitors one at a time or in multi-edit. see:  n Monitors and templates using WMI  n SAM Template Reference You can edit each monitor or select more for multi-editing. The multi- edit function only updates shared settings between the selected monitors.  n Set Test Node: Modify the test node for communication tests. Multi-edit components You can simultaneously edit multiple component monitors within a template. When editing a template. without needing to be of the same type. To begin collecting data. these monitors and templates need to be assigned to a node. You can select multiple monitors using the checkboxes to modify. lets you to change the order of each monitor.  n Disable/Enable: Start and stop polling for the monitor. you should edit each monitor individually. you can modify default and new templates. For example. SeeComponent Monitor Types. To reorder the monitors. You can access the help information per monitor through the Orion Web Console for more information. 314 . For details on supported templates. You may need to log in with an administrator account to perform these actions. This new order is respected only on the All Applications resource and the Application Details resource. Different types of monitors have different options available for editing. the green arrows to the right of each component monitor. You can perform the following types of multi-edit options:  n Multi-Edit: A prompt displays with editing options specific to the type of monitors selected. highlighted below.

 n If you want to monitor using the monitor again. This information is also included with the SAM Component Monitor Types and SAM Template Reference.conf: find /etc -iname httpd. select the monitor you want to remove. Linux system configurations for component monitors You need to consider and complete the following configurations for component monitor and templates to effectively monitor your Linux systems with the Orion agent for Linux. select and click Enable. Confirm by clicking Yes. Grant yourself root permissions (so root). Some of this information requires reviewing configurations with your vendors documentation.  n Apache configurations  n Tomcat configurations  n ODBC  n JMX  n Squid  n Nagios  n IBM DB2 (with ODBC) Apache configurations You should have the following packages installed:  n Apache httpd  n LWP::UserAgent (Perl) To install and configure:  1. The monitor is permanently removed from the template. You can disable one or monitors. When you disable. the monitor remains in the Orion Web Console without communicating and collecting data. you can delete to permanently remove it from the Orion Web Console.  2.Delete or Disable a monitor You can disable or delete application monitors as needed. click Disable. When editing a template. Locate httpd.conf The file is typically located in /etc/httpd/conf/httpd. You may need to work with your NOC and server management groups to complete modifications.  1. 315 . If you no longer want the monitor in the template.conf. Use the command: yum install perl-libwww-perl  3. Login to your Apache server using SSH or telnet client.  n If you want to stop all monitoring using the monitor.  2.

Locate the following section: #<Location /server-status> # SetHandler server-status # Order deny. Determine the version of Tomcat you want to install. The following information walks through installing and configuring Tomcat servers to work with SAM component monitors. To locate all versions.i386 : Apache Servlet/JSP Engine. Also make sure the ExtendedStatus is On: ExtendedStatus On <Location /server-status> SetHandler server-status Order deny.example. you can skip to step 4 to create an account used for polling.  4.0 API tomcat5-admin-webapps. Uncomment the code. Locate the versions to install from the search results. RI for Servlet 2. you can install the tomcat package and the admin webapps package. You may have multiple versions available to install. use this command: yum search tomcat  2.com #</Location>  5.allow # Deny from all # Allow from . After determining the version. Use localhost only if the Apache server services the loopback interface. For example: tomcat5.allow Deny from all Allow from localhost </Location> ExtendedStatus On  6. If you have Tomcat installed. implementing several Java EE specifications.i386 : The administrative web applications for Jakarta Tomcat 316 .  1. Edit the Allow from rule substituting the IP address or hostname of your Apache server for localhost.4/JSP 2. Restart the Apache httpd: service httpd restart or Reload the configuration: service httpd reload Tomcat configurations Apache Tomcat is an open-source web server.

uncomment the configuration. use this command: find /etc -iname tomcat-users. complete installations and configurations for component monitors on Linux:  n No database. you need the following installed:  1. Edit the file and locate the <tomcat-users> section. The template uses this account to access data.role1" /> </tomcat-users>  6. For example. To install the example above: yum install tomcat5 tomcat5-admin-webapps  4. Restart the service. Install the versions using the located versions. Install the DBMS driver: yum install postgresql-server postgresql-odbc  3. To locate. Next.'manager-gui').xml  5. The command depends on the version you installed. Install unixODBC: yum install unixODBC  2. Edit to add a user of tomcat with the password of tomcat.manager.  3.  n Postgre SQL  n MySQL General ODBC setup For monitoring ODBC on Linux. Install the ODBC driver: yum install mysql-server mysql-connector-odbc Postgre SQL Install Postgre SQL and ODBC: #!/bin/bash # install needed packages 317 . <tomcat-users> <user name="tomcat" password="tomcat" roles="tomcat. follow the General ODBC setup. If commented out. you need to modify the tomcat-users. this command restarts the installed service above: service tomcat5 restart ODBC Depending on your database.manager-gui" /> <user name="role1" password="tomcat" roles="role1" /> <user name="both" password="tomcat" roles="tomcat.xml file to create and provide a user account to access the web manager ('manager'.

then ver=(`echo $sysver | tr '. then sudo useradd -m postgresuser sudo echo 'postgresuser:Password1' | chpasswd fi # start postgresql sudo service postgresql start # create testdb sudo su . CREATE DATABASE testdb.1" fi reponame="suse-${sysver}-oss" repo="http://download. \q logout # verify testdb sudo su . echo $?` -eq 0 ]. echo $?` -eq 0 ].opensuse.org/distribution/$sysver/repo/oss/" if ! [ `zypper lr | grep "$reponame"` ]. if [ `yum --version &>/dev/null. SYSVER: $sysver" if [ "$sysid" == "sles" ]. then sudo apt install -qqy unixODBC postgresql postgresql-server postgresql-odbc else sysid=`cat /etc/os-release | egrep -i ^ID= | cut -d= -f2` sysver=`cat /etc/os-release | egrep -i ^VERSION_ID= | cut -d= -f2` echo "SYSID: $sysid.postgresuser psql -d testdb 318 . then sysver="${ver[0]}. GRANT ALL PRIVILEGES ON DATABASE testdb to postgresuser. then sudo zypper ar -f $repo $reponame fi fi psqlodbcpkg=`zypper pa | cut "-d|" -f3 | tr -d " " | egrep -i 'postgres|psql' | grep -i odbc | grep -v dbg | cut -d/ -f1 | head -n 1"` sudo zypper --non-interactive --no-gpg-checks --quiet install --auto-agree- with-licenses unixodbc postgresql $psqlodbcpkg fi Then create and configure a user and database: # add psql user if ! [ `cut -d: -f1 /etc/passwd | grep postgresuser` ].postgres psql template1 CREATE USER postgresuser WITH PASSWORD 'Password1'.' $'\n'`) if [ "${ver[1]}" == "" ]. then sudo yum install -qqy unixODBC postgresql postgresql-server postgresql-odbc elif [ `apt --version &>/dev/null.

319 . You may need to open a port to 9060 on the websphere host.rpm yum update yum install mysql-server systemctl start mysqldsudo mysql_secure_installation mysql -u root -p create database testdb.  4. JMX For JMX configurations. use testdb. For details.  5.\q logout MySQL To configure MySQL. Use the credentials for the account created during installation.rpm sudo rpm -ivh mysql-community-release-el7-5.mysql.* to 'testuser' identified by 'password'. You can access by pointing a browser to http://<websphere-host>:9060/ibm/console.  2. install. Start and stop the WebSphere AppServer. first_name TEXT. see the IBM WebSphere documentation site. Access the WebSphere AppServer console to continue configurations. You need to expose the JMX platform mbeans in the WebSphere AppServer using the console. Click Servers > Server Types > WebSphere application servers and select the listed application server. You may need to create a new package group.noarch. last_name TEXT). you need to install and configure WebSphere per your Linux distribution. During installation. The overall steps include:  1. wget http://repo. see the documentation at the MySQL documentation center.  3. you need to install the appropriate MySQL repo. You may require credentials for the installation. The following commands provide an example of those installations and configurations. and configure. Get and install WebSphere.noarch. You may also need to create an administrator account. you can turn off the secure storage option as this is not needed. For details.com/mysql-community-release-el7-5. Make sure to select the Application Server during installation. create table customers (customer_id INT NOT NULL AUTO_INCREMENT PRIMARY KEY. grant all on testdb.

sun.Enable the SNMP feature for Squid. Locate the Java and Process Management > Process definition. You can use the Nagios Script monitor and Linux/Unix Script monitor for monitoring Nagios. 'random number: ' + str(randint(1.sun.initial= There is nothing after the = sign. If using Squid-2. It has a wide variety of uses. Review your vendor documentation for details at http://www. applications. you will need to enable the feature using a series of scripts then configure.  6.management. The argument would be python $(SCRIPT) with a body of: from random import randint STAT_PAIRS_COUNT = 10 for stat_id in range(STAT_PAIRS_COUNT): print 'Statistic.conf.ssl=false Dcom. DNS and other computer network lookups for a group of people sharing network resources.management.Add per your Linux distribution vendor's documentation. In the dialog box titled "Generic JVM arguments" enter the following: Djavax.jmxremote. you need to download. Dcom.management.org/. to aiding security by filtering traffic. For details. and configure DB2. To configure Squid for agent polling:  n SNMP is required . you need to enter a script as follows.management. Refer to your vendor's documentation to properly install and configure Nagios according to your Linux distribution.random%d: %d\nMessage. If you are using this component monitor with Nagios and polled by Orion agent for Linux. stat_id. see the IBM DB2 documentation site.jmxremote=true Dcom.100))) IBM DB2 (with ODBC) For IBM DB2.port=8686 Dcom.random%d: %s' % (stat_id. If using Squid-3. this feature is available to enable by adding a configuration option to squid.squid-cache.jmxremote.builder. 320 . Nagios Nagios monitors systems.jmxremote. Squid Squid is a caching and forwarding web proxy. Restart the AppServer.  n perl-switch is required . to caching web.sun. networks. from speeding up a web server by caching repeated requests. switches.authenticate=false  7.management. and services. randint (1. It offers monitoring and alerting servers.sun. install. and infrastructure.100).

The instance user should be used to connect to the database and continue running commands.First.ini: [testdb] Description = My very best DB2 Driver = DB2 The drivers should match in both files. Connect locally to the database to continue with the next instructions: isql -v testdb db2inst1 Password1 #means datasource user password Finally. Install the ODBC package with this command: yum -y install unixODBC  2.ini: [DB2] Description = DB2 Driver Driver = /opt/ibm/db2/V10.  4. Update the ODBC config files. Logged in with the instance user (db2inst). CREATE DATABASE testdb ACTIVATE DATABASE testdb CONNECT TO testdb CREATE TABLE tbl (id int. connect DB2 through ODBC to the Orion Platform:  1. Complete installation commands. Download and unpack the IBM DB2 package.  3. data varchar(30)) INSERT INTO tbl VALUES(10. Add the following settings to /etc/odbcinst. "entervalue") SELECT * FROM tbl Next.  4. Access as the instance user and run the command line tool for DB2: su db2inst1 db2  5. Grant execute on function SYSPROC. You may need to install 32-bit PAM.  2. you will need to create a DB user. Add the following settings to /etc/odbc. and instance user.i686  3. These steps may take additional time to complete. install IBM DB2:  1.5/lib64/libdb2.MON_GET_TABLE to the instance account db2inst1.so has the correct file path. Navigate to the source directory and run the installer. use the DB2 command line tool to enable the following: UPDATE DBM CFG USING DFT_MON_BUFPOOL ON UPDATE DBM CFG USING DFT_MON_LOCK ON UPDATE DBM CFG USING DFT_MON_STMT ON UPDATE DBM CFG USING DFT_MON_UOW on  2. run this command and run the installer again: yum -y install pam. 321 . To install. fence user. install ODBC for IBM DB2:  1.so FileUsage = 1 DontDLClose = 1 Verify libdb2. During the installation.

Uid=${USER}.  4.Hostname=${IP}.Port=50000.Uid=${USER}. Modify the connection strings for monitors to match your DB. or existing data source in odbc. Provide credentials for the db2inst1 user.Protocol=TCPIP. 322 . Add the IBM DB2 application template to your monitored node. Pwd=${PASSWORD}. either specifying the actual DB and driver: Driver= {DB2}.ini: DSN=testdb.Pwd=${PASSWORD}.Database=TESTDB. 3.

Monitors and templates using WMI These lists provide the component monitors and templates that use and support WMI. Microsoft Windows by default uses a random port between 1024 and 65535 for WMI communications.0 Core counters  n Citrix XenApp 6.0 Presentation Server 323 .0 ICA Session  n Citrix XenApp 6.2012 Services and Counters  n Apache (Windows)  n APC PowerChute Agent (Windows)  n AppInsight for Exchange  n AppInsight for IIS  n AppInsight for SQL  n BizTalk Server 2010-2013 Adapters Performance Counters  n BizTalk Server 2010-2013 Host Throttling Performance Counters  n BizTalk Server 2010-2013 Message Box and Orchestrations Performance Counters  n BlackBerry Delivery Confirmation  n Blackberry Enterprise Server  n BlackBerry Enterprise Server 10 Services (Windows)  n CiscoWorks LAN Management Solution  n Citrix XenApp 5.65535 or the component monitors and templates that use WMI will not work. Component monitors using WMI  n Performance Counter Monitor  n Process Monitor – Windows (if script uses WMI access)  n Windows Event Log Monitor  n Windows PowerShell Monitor (if script uses WMI access)  n Windows Script Monitor  n Windows Service Monitor (if script uses WMI access) Templates using WMI For information on these templates.0 Presentation Server WMI counters  n Citrix XenApp 5.0 Services  n Citrix XenApp 6.  n Active Directory 2003-2008 Services and Counters  n Active Directory 2008 R2 . see the template reference.0 Core WMI counters  n Citrix XenApp 5.0 ICA Session WMI counters  n Citrix XenApp 5. You must create firewall exceptions to allow TCP/UDP traffic on ports 1024 .

 n Citrix XenApp 6.0 Services
 n Distributed File System (DFS)
 n Errors in Application Event Log
 n Exchange 2007 Client Access Role Counters (Advanced)
 n Exchange 2007 Edge Transport Role Counters (Advanced)
 n Exchange 2007 Hub Transport Role Counters (Advanced)
 n Exchange 2007 Mailbox Role Counters (Advanced)
 n Exchange 2007 Unified Messaging Role Counters (Advanced)
 n Exchange 2007-2010 Client Access Role Services and Counters (Basic)
 n Exchange 2007-2010 Common Performance Counters
 n Exchange 2007-2010 Edge Transport Role Service and Counters (Basic)
 n Exchange 2007-2010 Hub Transport Role Service and Counters (Basic)
 n Exchange 2007-2010 Unified Messaging Role Service and Counters (Basic)
 n Exchange 2010 Client Access Role Counters (Advanced)
 n Exchange 2010 Edge Transport Role Counters (Advanced)
 n Exchange 2010 Hub Transport Role Counters (Advanced)
 n Exchange 2010 OWA Form Login (PowerShell)
 n Exchange 2010 Unified Messaging Role Counters (Advanced)
 n Exchange 2013 Client Access Role Counters (Advanced)
 n Exchange 2013 Client Access Role Services and Counters (Basic)
 n Exchange Active Sync Connectivity
 n Exchange Server 2000 and 2003
 n File Count Script
 n GoodLink Server for Microsoft Exchange
 n Group Policy Object (System and Application Logs)
 n Helix Universal Media Server (Windows)
 n Internet Information Service (IIS) 6
 n JD Edwards EnterpriseOne Server Manager (Windows)
 n Kaspersky Security Center Antivirus
 n Kiwi Syslog Server
 n Log Parser (PowerShell)
 n Microsoft DirectAccess 2008 R2
 n Microsoft DirectAccess 2012
 n Microsoft DirectAccess 2012 R2
 n Microsoft DirectAccess 2012-2012 R2 (Health with PowerShell)
 n Microsoft Dynamics CRM 4.0 Events
 n Microsoft Dynamics CRM 4.0 Statistics
 n Microsoft Dynamics CRM 2011 Events

324

 n Microsoft Dynamics CRM 2011 Statistics
 n Microsoft Forefront Endpoint Protection 2010 Client
 n Microsoft Forefront Endpoint Protection 2010 Server
 n Microsoft Forefront Threat Management Gateway 2010
 n Microsoft IIS SMTP Server
 n Microsoft Lync Server 2013 (Edge Role)
 n Microsoft Lync Server 2013 (Front-End Role)
 n Microsoft Lync Server 2013 (Mediation Role)
 n Microsoft Lync Server (Edge Role)
 n Microsoft Lync Server (Front-End Role)
 n Microsoft Lync Server (Mediation Role)
 n Microsoft Message Queuing Events
 n Microsoft Message Queuing Performance
 n Microsoft Network Policy Server Events
 n Microsoft Network Policy Server RADIUS Proxy
 n Microsoft Network Policy Server RADIUS Server
 n Microsoft Routing and Remote Access 2008-2012 R2
 n Microsoft Routing and Remote Access 2008-2012 R2 (Events)
 n Microsoft System Center Configuration Manager 2012
 n Microsoft System Center Operations Manager 2012 (Agent)
 n Microsoft System Center Operations Manager 2012 (Management Server)
 n Microsoft Windows Internet Name Service (WINS) Events
 n Microsoft Windows Internet Name Service (WINS) Statistic
 n Microsoft Windows Server 2003 Failover Cluster
 n Microsoft Windows Server 2008 Failover Cluster
 n Microsoft Windows Server 2008 R2-2012 R2 Failover Cluster (Advanced)
 n Microsoft Windows Server 2012 Failover Cluster
 n Microsoft Windows Server 2012-2012 R2 Failover Cluster
 n MongoDB (Windows)
 n Novell GroupWise Message Transfer Agent (Windows)
 n Novell GroupWise Post Office Agent (Windows)
 n Office 365 User Statistics with PowerShell
 n Orion Server
 n Remote Desktop Services Licensing
 n Server Clock Drift (PowerShell)
 n SharePoint Server 2010
 n SharePoint Server 2013
 n SharePoint Server (MOSS) 2007

325

 n SharePoint Services (WSS) 3.0
 n SolarWinds Failover Engine
 n SolarWinds NetFlow Traffic Analyzer
 n SolarWinds Web Performance Monitor (WPM) Player
 n SQL Server 2005 Analysis Services
 n SQL Server 2008 Analysis Services
 n SQL Server 2008 R2 Reporting Services
 n SQL Server 2008 Reporting Services
 n SQL Server 2008-2012 Reporting Services (Events)
 n SQL Server 2012 Analysis Services
 n SQL Server 2012 Reporting Services
 n Squid (Windows)
 n Streaming Media Services 2008
 n Symantec Backup Exec Remote Agent
 n Symantec Backup Exec Server
 n Symantec Endpoint Protection Client
 n Symantec Endpoint Protection Server
 n Symantec NetBackup Client
 n Symantec NetBackup Server
 n Terminal Licensing Server
 n Trend Micro OfficeScan Client
 n Trend Micro OfficeScan Server
 n Trend Micro Server Protect (Windows)
 n UniData Database (Windows)
 n Veeam Backup and Replication Server
 n VMware vCenter Server 5.5
 n Websense Web Security
 n Windows 2003-2008 FTP Service
 n Windows 2008 R2 - 2012 FTP Service
 n Windows DHCP Server
 n Windows DNS Server
 n Windows Network Load Balancing
 n Windows Print Services
 n Windows Remote Desktop Services (Session Host Role)
 n Windows Server 2003 Domain Controller Security
 n Windows Server 2003-2012 Services and Counters
 n Windows Server 2008-2012 Domain Controller Security
 n Windows Update Monitoring

326

Assign and edit application monitors to nodes
To begin collecting data in SAM, you need to assign the application monitors or templates to nodes
managed by the Orion Web Console. The quickest way to assign Application Monitors to nodes is through
the Add New Application Monitors Wizard. You can also assign them through the Manage Templates page.

You may need to log in with an administrator account to perform this action.

To assign a template using the Add New Application Monitors Wizard:

 1. On the Web Console, click Settings > All Settings > SAM Settings > Manually Assign Application
Monitors.
 2. Select the Application Monitor template to apply, and then click Next.
 3. Select the server nodes to which you want to apply the Application Monitor template, and then click
Next.
 4. Select existing credentials or create new credentials, then click Assign Application Monitors.

To assign a template through the Manage Application Monitor Templates page:

 1. On the Web Console, click Settings > All Settings > SAM Settings > Manage Templates.
 2. Browse and select the template you want to assign.
 3. Click Assign to Node, then select the server nodes to which you want to apply the Application
Monitor template, and then click Next.
 4. Select existing credentials or create new credentials, then click Assign Application Monitors.
 5. Review the information for the assigned Application Monitor and then click Done.

To remove application monitors:

 1. On the Web Console, click Settings > All Settings > SAM Settings > Manage Templates.
 2. Select a template and click Edit. The template opens displaying all currently assigned monitors.
 3. Select the monitors you want to remove and click Delete.

327

Create component monitors from the Component Monitor Wizard

Create component monitors from the
Component Monitor Wizard
The Component Monitor Wizard provides a starting point where you can select
component monitors based on a specific process, performance counter, or service.
You can add these monitors with modifications to application monitors and
templates for assigned node monitoring. You can then discover and monitor nodes
that match the selected process.

Component monitors are a part of the larger whole of application monitors and
templates used to monitor applications. Templates include multiple application
monitors, which include multiple component monitors, for tracking and providing
data on nodes and applications. The application template can then be applied to
nodes running the application the template was designed for. To learn how to create
an application template, see Assign and edit application monitors to nodes.

You may need to log in with an administrator account to perform this action.

 1. On the web console, click > Settings > All Settings > SAM Settings > Component
Monitor Wizard.
 2. Select a component monitor type top add to your application or template.
These include monitors based on operating system: Windows Systems, Linux -
Unix Systems, VMWare Systems, and Applications.

When using the Component Monitor Wizard, the only component
monitor supported for Orion Agent for Linux is the Linux - Unix System:
Process Monitor. To create and assign component monitors and
templates for Orion Agent for Linux, see the available list here: Monitor
with Orion agents in SAM

328

 3. Depending on the component monitor you select, a new set of steps display.
For example, if you create a Process Monitor, you should select a Target system
by browsing to supported systems in your environment. You may also need to
select a platform bitness and enter credentials for the target system. Select
and enter all required information.
 4. When you click next, if you entered credentials, a connection test runs. If it
passes, continue adding component monitors and properties. Depending on
the components, you may need to enter additional server and credentials data.
 5. With your component monitors set, you can add the component monitor to
other application monitors and templates.
 6. Finally, assign the application monitor or template to nodes in your
environment. When confirmed, the node details page will include these new
monitors and resulting data.

329

Scan nodes for applications
SolarWinds SAM can scan nodes for you and automatically assign the Application Monitors it deems
suitable for each scanned node. You select the nodes to be scanned, the application templates to use in
the scan, and the scanning parameters to determine a match. When run, SAM compares applications
located on nodes with the parameters to automatically assign monitors.

You may need to log in with an administrator account to perform these actions.

You cannot scan for user experience (UX) monitors, but you can assign them to nodes manually.
Adding monitors from this page does not affect your scan.

Use the Scan Nodes for Applications to configure, scan, and assign monitors:

 1. On the Web Console, click Settings > All Settings > SAM Settings > Click Scan Nodes for Applications.
 2. Browse or filter to select nodes for scanning. You can select all or pick and choose from lists. The
number of nodes selected lists on the page. Click Next.
 3. Browse, filter, and select the applications you want to scan for. These applications have associated
monitors. Expand the Advanced Scan Settings to set the exactness for matches. Click Next.

To keep the time it takes to scan to a minimum, we recommend you initially scan for only a
limited number of application templates. To see more application templates, select a different
template group from the Show Only list.

 n Exact Match: All the components must match to assign the template.
 n Strong Match: Most of the components must match to assign the template.
 n Partial Match: Some of the components must match to assign the template.
 n Minimal Match: At least one component must match to assign the template.
 4. Some application templates require credentials either to access restricted resources, or to run within
the context of a specific user. To scan for these templates, add the necessary credentials to the list,
moving them into an order for using. If a template you are scanning for requires credentials, the
credentials in this list are tried in the order in which they appear. You can add credentials or allow
credentials to inherit from the node's local credentials. Click Next.

If you have domains sharing user names with different passwords, we recommend you run
separate application discoveries for each domain.

Credentials are tried several times over the course of a scan, so an incorrect password is likely
to lock out an account. To avoid potential account lockouts that affect actual users, we
recommend you create and use service accounts. A service account is an account that is
created specifically for the purpose of providing credentials to use for SolarWinds monitoring.
With service accounts, no actual user is affected by an account lockout if a password should
be entered incorrectly.

 5. Review the selected options before scanning. If the automatic discovery matches templates that are
already assigned to the node, by default the template is not assigned a second time. If you want to
assign duplicate templates, select Yes, Assign Anyway from the Do you want to assign duplicates list.

330

 6. Click Start Scan to start the discovery and assignments.
 7. The scan runs in the background. You are notified by a message near the top of the window when
scanning is completed. Click View results to see the results of the scan.

You can modify the assigned applications monitors through the Manage Application Monitors page at
Settings > All Settings > SAM Settings.

331

Manage templates and groups
Learn more about managing templates and groups through SAM. This section provides FAQs on managing
these objects.

 n Assign an application template to a group
 n Unassign application monitors from a group

Following are frequently asked questions and answers concerning templates and groups.

Q: If I assign a template to a group and then add a node that already has the same template assigned
to it, what happens?

A: Nothing will happen since the application has already been created.

Q: If I assign a template to a group that is OS specific, such as the Microsoft Windows Server 2003
Failover Cluster template, and then I add a Windows Server 2012 R2 server to the group, will the 2003
specific temple be added to the 2012 R2 node?

A: Yes. The logic is that members of the group get assigned to the template.

Q: What happens if I add a Linux template to a Windows group?

A: The application will be created but the status will be reported as Unknown.

Q: If I delete a group that has applications assigned to it, what happens to the templates that were
assigned via the group? Do they get removed from those nodes?

A: This depends on whether or not you unchecked the default behavior of the group found in Advanced
section. By default, the answer is yes. All members will be removed and therefore all of the applications on
them will be removed.

Q: If I have a node in two different groups that share application templates, will the node get assigned
to copies of the same template?

A: No. If you remove a node from the first template, the application is not removed and it is marked as
assigned to the second node.

332

The new application created from the template will use credentials from the node that is assigned to. you can select Inherit Credentials from Node when using WMI or an agent. 333 .Q: Can I assign credentials to a node and have all of the templates assigned to that group use that credential? A: There is no credential associated with a group. however.

On the web console. To create a group. 334 . Application assignment to a group happens in the background and can take some time to be created depending on the size of the application. click Settings > All Settings > SAM Settings > Manage Templates > Application Monitor Templates. Assign to Group.  1. Select an application template and then click.  2. a group must be created. Nested groups are not supported. see Create groups.Assign an application template to a group Assigning an application template to a group is more efficient than applying the template to individual nodes one at a time. Before you begin. AppInsight applications cannot be assigned to groups.

Click Done. By default. When a node is removed from a group. For example.  5. the application is deleted from the node by default. Select your credentials and then click. You can create dynamic groups and assign templates to these groups. 335 . To view the applications within a group.  3. and then click Next. in the web console. Assign Groups. You can override this by selecting No under the Advanced section. the template is assigned to those nodes in the group that are running a server operating system. a dynamic group can be created for all Windows computers and the Windows Update template can be applied to the nodes of the group dynamically. Select a group from the Available Groups column. Your application templates are now assigned to a group.  4. click My Dashboards > SAM Summary and then click a group in the Application Templates Assigned to Group resource. This can be changed in the Advanced section at the bottom of the page. click the green arrow.

336 . On the Template Assignments page.  2. Unassign.  4. click Settings > All Settings > SAM Settings > Manage Templates > Application Monitor Templates. and then click the link in the Assigned To column. Click Close.  3.Unassign application monitors from a group  1. click the Group tab and then click Unassign > Yes. On the web console. Select the application monitor you want to unassign from the group.

Monitors have an enable/disable option. the application monitor template immediately begins polling per the configured intervals. a scheduler opens to set the date and time to begin and end the unmanaged state. 337 . When a template of application monitors is unmanaged. you need to manage the application monitors template.  1. You cannot unmanage specific application monitors within a template. On the Web Console.  5. Locate the application monitor template you want to manage or unmanage. you no longer receive data in SAM. Click OK to save.Unmanage and manage assigned application monitors You may need to unmanage or manage assigned application monitors.  2. You may need to log in with an administrator account to perform this action.  4. When unmanaging. click Settings > All Settings > SAM Settings > Manage Application Monitors.  3. To resume viewing status and polled data. When managing. Select the option as needed: Manage or Unmanage.

 n Linux/Unix Script monitor  n Windows Script monitor  n Nagios Script monitor  n Windows PowerShell monitor For general information about the settings for each component monitor. click the More Information help link in the SolarWinds SAM component monitor description. we do not provide customer support for custom scripts written by outside sources. and number of recipients. refer to the following sections:  n Conversion value  n Available data transformations 338 . however. hour.  For information on using Data Transformations. the remainder above the tenth output pair is ignored. A usage example using the PowerShell script monitor might go like this: Imagine you have an Exchange PowerShell script. The following sections provide information and guidance to help you create some of the more complicated types of component monitors. With multiple values returned. you can get a mail traffic report broken down by day. SolarWinds fully supports scripts written and provided by the company.Script custom component monitors Ten output pairs can be returned when using script monitors. SolarWinds does provide sample scripts that we do support located at: C:\Program Files\SolarWinds\Orion\APM\Sample- Script Monitors. If you exceed the maximum number of allowed output pairs of ten. message size.

You need to verify your installation of python and python-xml. Agentless monitoring does not require these credentials. you may have need to install these libraries. A maximum of 10 output pairs can be returned. You can verify your Python installed libraries with the following command: python -c "import sys. you may need to verify install and configure specific applications and services to use the Linux/Unix Script monitor. The following command typically updates and installs the required Python libraries: apt-get install python Depending on your Linux distribution. to use the Linux/Unix Script monitor with Apache services (as with the Apache template). To create this monitor. Enable Component Determines whether the component is enabled.minidom import parseString. For example. Prerequisites for Orion agent for Linux You need to include credentials that can run scripts on the monitored Linux-based computer. If you exceed the maximum allowed. remove the excess output pairs or they will simply be ignored.version" See the Python site for documentation and install commands. see Create a Linux or Unix script monitor. 339 . print sys. we recommend using the Nagios Script monitor. Depending on your Linux distribution. see Linux system configurations for component monitors. you need to configure Apache access. Disabling the component leaves it in the application in a deactivated state not influencing either SolarWinds SAM application availability or status. To use scripts with Nagios formats. Statistic The statistic for this component monitor is the Statistic value returned by the script. The variable to access this field is ${UserDescription}. For full configuration details for all services. which is automatically saved. from xml. You have the ability to override the default description by adding to or replacing the text. Field Descriptions Description This field provides a default description of the monitor.dom. runs the script on the server.Linux/Unix Script monitor This component monitor uses SSH to upload a script to a Linux/Unix server. and then processes the return value and text output.

Port Number This field allows you to specify the port number used for the SSH connection. see Credentials and privileges used on Linux-based computers. The default value for this field is 22.pl. The length of the Command Line field is limited to 266 characters for Solaris systems. These credentials may not have the elevated permissions required for executing scripts. Script Working Directory This field allows you to specify the working directory of the script process. use the Quick Credentials section to add a new credential. Count Statistic as Difference Changes the statistic to be the difference in query values between polling cycles. the monitor executes the script under the agent credentials (SWIAgent). The default command line value perl ${SCRIPT} arg1 arg2 attempts to run in a Perl interpreter the script defined in the Script Body field using the parameters arg1 arg2. and that has sufficient rights to run scripts. If you need to pass a longer command line to the target node. this means that the actual user Command Line input cannot be longer than 266 – 16. If you do not enter credentials or select Inherit from node. The second option allows you to use certificates for authentication. If the credentials you need are not already present in the credentials list. Command Line This field allows you to specify the shell command run after the SSH connection is established. you can create a shell script on the target node (for example myscript.Authentication Type Choose either User name and Password or User name and Private Key.sh 340 .sh) that contains the long command line. make sure:  n The account exists on the system receiving the executed script  n The account has elevated permissions For details on credentials used by Orion agents. or about 250 characters (not including the length of the 9 characters for the “${SCRIPT}” variable itself). and place the call to this script in the Command Line field. When providing credentials. Credential for Monitoring Select a credential that can access the Linux or Unix server over SSH. for example: /opt/sw/myscript. minus the length of the ${SCRIPT} variable after being resolved to a file name such as the following: APM_ 937467589. Since the length of the file name will typically be around 16 characters.

The default selection is “Show worst status. Status Roll-Up This option allows you to choose how you would like the monitor to report based on the output provided by the script. You can access this field by using the variable. Adapt an existing Perl script to a Linux/Unix Script component monitor in a new template  1. then return the values.  4.  3. and then select Linux/UnixScript Monitor.” User Notes This field allows you to add notes for easy reference. two: The code in red shows where the output pairs are defined. A temporary file is created in temp directory for the script. {SCRIPT} is replaced by the actual file name of the script after it’s deployed to the target node. expand the Custom Component Monitors group.Script Body This field allows you to specify the script you want to run on the Linux or Unix server. Click Get Script Output. Type the Linux command that runs the script in the Command Line field.  8. When collecting information for this monitor. Click Edit to open the script dialog and enter your script into the Script Body field. It should be similar to the following: perl ${SCRIPT} arg1 arg2. then specify the critical and warning thresholds and click Submit. On the Web Console.  7. and then name the template  2. Click Submit then select credentials with SSH permissions in the Credential for Monitoring field. #!/usr/bin/perl if (@ARGV[0] =~ /\bhelp\b/) { 341 . More than 10 defined pairs results in a failure of the monitor. Create a Linux or Unix script monitor Linux and Unix Script component monitors allow you to execute a command line script that can return statistical data.  6. in this case. A maximum of 10 output pairs can be monitored per script monitor. Type a valid working directory in the Script Working Directory field  5. SAM runs the script with the credentials defined with the Credential Library. Click Save. click Settings > All Settings > SAM Settings > Create a new template. SAM then tests the script by executing it and parse its output. Click Add Component Monitor. Here is a sample Perl script using the Linux/Unix component monitor returning multiple output pairs. ${UserNotes}.

$community = shift || "public".) { if ($line =~ /\bINTEGER\b/) { $indval = index($line. $indval=inde($line. $hostname = shift || $localhost. $results = "".community name of SNMP protocol\n".2: $val \n". print "Statistic.OUTMEM&gt. $val =~ s/[a-zA-Z\/\n ]// print "Message. Below is the output from this script: Linux/Unix scripts Linux/Unix scripts are uploaded by SSH and then run on the target node using the string from the Command Line field. exit 1. open(OUTMEM.1: $val\n".pl SNMPver community hostname\n".length($line) . } # Get hostname and trim newline $localhost = `hostname`. the available memory at host \"$hostname\": $ in kB\n". while ($line = &lt.2: Again. print "MemoryUsage. print "Message."="). } } print "Statistic: 0\n". print "community . exit 0. exit 1.$indval+1. $version = shift || "v1".Target host\n".$indval). $val = substr($line. $localhost =~ s/\s*$//g.$indval).0".$outres) || die "Unable read pipe\n".0".1: Available memory at host \"$hostname\": $val in kB\n print "Statistic. $MIB_TotalMemory = "UCD-SNMP-MIB::memTotalReal.":". #$MIB_TotalMemory = "UCD-SNMP-MIB::memTotalReal. You can use the following variable in the command line field: 342 .version of SNMP protocol\n". print "hostname . print "SNMPver . $outres = "snmpget -$version -c $community $hostname $MIB_TotalMemory |".

If the component only returns Down (1) or Unknown (4) on first use. you must first return an exit code which results in an Up (0).  n ${USER} .Name1: abc Statistic. Warning (2). Statistic. or Critical (3) status.  n ${PASSWORD} . you would exit the script using code similar to the following. where 0 reports Up: Wscript.Name1: xMessage. if you want to inform SolarWinds SAM that a Script reports Up status.quit(0) Scripts with Text Output Scripts report additional details by sending text to the script’s standard output. SAM supports multiple values returned by a script using the following format.Replaced with the script body. in the folder: C:\Program Files\SolarWinds\Orion\APM\SampleScriptMonitors\LinuxScripts Scripts Must Report Status Through Exit Codes Scripts must report their status by exiting with the appropriate exit code. You can use the following variables in the script body field:  n ${IP} . These sample scripts are installed on your SolarWinds SAM server.Name2: yMessage. When one of these exit codes is received the appropriate dynamic evidence table structure is created and all further exit codes are handled correctly. Example Scripts There are several sample scripts installed with SolarWinds SAM you can use to create Linux/Unix script component monitors. the appropriate dynamic evidence table structure is not created appropriately.  n ${SCRIPT} . To correctly create this component monitor. EXIT CODE MEANING 0 Up 1 Down 2 Warning 3 Critical Any other value Unknown.Replaced with the password from the credential.Replaced with the user name from the credential.Name2: abc 343 .Replaced with the target node’s IP address. for example 4 For example.

randint (1. 344 . These can be placed anywhere in the script output.CPU: 31.CPU: svchost.RAM: 1234. Ten pairs are possible. Note: Multi-line messages are supported.random%d: %d\nMessage. Statistic. This must be an integer value.100). Sample output: # Script comment: This shows two pairs. DETAIL REQUIRED MEANING TYPE Statistic Yes A numeric value used to determine how the monitor compares to its set thresholds. 'random number: ' + str(randint(1. (negative numbers are supported). stat_id.random%d: %s' % (stat_id. The Statistic and Message names you give must contain valid letters and/or numbers.exe cpu usage Statistic.Name2: 456 Message No An error or information message to be displayed in the monitor status details.RAM: svchost.Name2: def There is a limit of ten Statistic and Message pairs for the script. To use this functionality print each line using a separate command. we recommend using the Nagios Script monitor.Name1: 123 Statistic.exe ram usage Nagios scripting If you are using this component monitor with Nagios and polled by Orion agent for Linux.Name1: abc Message. The argument would be python $(SCRIPT) with a body of: from random import randint STAT_PAIRS_COUNT = 10 for stat_id in range(STAT_PAIRS_COUNT): print 'Statistic.56 Message. you need to enter a script as follows. Statistic.100))) To use scripts with Nagios formats.08 Message. For example: Message.

which will then be automatically saved. To create this monitor. remove the excess output pairs or they will simply be ignored. The default value is vbscript. Script Engine This field allows you to specify the scripting language to be used. Enable Component This option determines whether or not the component is enabled. Statistic The statistic for this component monitor is the value returned by the script. Disabling this component leaves it in the application as deactivated and does not influence application availability or status. see Create a Windows Script Monitor.e. Field Descriptions Description This field provides a default description of the monitor. This is best used in conjunction with the Multiple Statistic Chart. Script Monitor Formatting At least one message and statistic is required.Windows Script monitor This component monitor runs a Windows script on the SolarWinds SAM server and then processes the script's exit code and text output. the credentials also need WMI rights on the target node. however. Component Type This describes the type of monitor you are using. i. depending upon your application) to do whatever the script needs to do.: 10 statistic values + 10 [optional] messages. if the script does something with WMI. There is no maximum length for the message. use the Quick Credentials section to add a new credential. The variable to access this field is ${UserDescription}. Below is a list of scripting engines that the Windows Script Host supports: 345 . A maximum of 10 output pairs can be returned. If you exceed the maximum allowed. only alphanumeric characters and the underscore are allowed. For example. The statistic must be a valid integer and be able to be converted to double. and has sufficient rights on the target node (which may be the SAM server itself. You have the ability to override the default description by adding to or replacing the text. Credential for Monitoring Select a Windows credential that is both a user who can log on to the SolarWinds SAM server. otherwise it is handled as Not as Number (NaN). If the credential you need is not already present in the credentials list. This monitor has the ability to return up to ten pairs.

With the ability to have multiple values returned. PowerShell uses WINRM that runs over TCP ports 5985 and 5986.vbs Installed by default JScript . To enter your script.pls Freeware ooRexxScript .js Installed by default PerlScript . All Linux. User Notes This field allows you to add notes for easy reference.rxs Freeware PythonScript . NAME FILE EXTENSIONS AVAILABILITY VBScript ." Script This field allows you to enter the script you want to run on the target node.pys Freeware TclScript . Body This field is in the script editing window and allows you to enter your script via typing or pasting. Unix.tcls Freeware ActivePHPScript . click the Edit button that reveals the script editing window. You can access this field by using the variable. 346 . the credential user name.phps Freeware RubyScript . You may include the variables ${IP}. and the credential password. selecting how your scripts report back to you offers more flexibility. and Nagios script monitors use SSH over TCP Port 22. which are replaced respectively by the IP address of the target node. and ${PASSWORD}. Script Arguments This field is in the script editing window and allows you to specify arguments to pass to the script.  Roll-Up This option allows you to choose how you would like the monitor to report the returned results based on the output provided by the script. The default selection is “Show worst status. ${UserNotes}. ${USER}.rbs Freeware Object Rexx engine   Commercial Delphi scripting engine   Commercial VBscript runs locally on the SAM server only.

The SolarWinds SAM server uses the decimal separator set by its Microsoft Windows regional settings. Click Submit. 347 . and that also has appropriate permissions to do whatever else the script requires. Scripts run on the SolarWinds SAM server and use the credentials you specify. Copy the Visual Basic script into the Script Body field. Adapt an existing Visual Basic script to a Windows Script Monitor in a new template  1. click Settings > SAM Settings > Create a New Template. but can be extended with other scripting languages.  6. then name the template. Format the Statistic value to use the same decimal separator as the SolarWinds SAM server. On the Web Console.  2. Type any script arguments into the Script Arguments field. Specify the critical and warning thresholds. and then check Windows Script Monitor. Windows Script Host comes with VBScript and Jscript. The script must both return an exit code and output a text string containing a statistic value conforming to the specifications described later in this section. You may need to log in with an administrator account to perform this action. then expand the Custom Component Monitors group. Scripts Must Report Status Through Exit Codes Scripts must report their status by exiting with the appropriate exit code.  3.Create a Windows Script Monitor You can create a Windows Script monitor to have SolarWinds SAM run a script using Windows Script Host. You can use the following variables as script arguments: ${IP} This is replaced with the target node’s IP Address. ${USER} This is replaced with the user name from the credential set.  4. and then select credentials with the appropriate permissions to run the script on the SolarWinds SAM server. Click Add Component Monitor. Macros for Script Arguments Specify script arguments in the Script Arguments field if needed. ${PASSWORD} This is replaced with the password from the credential set. then click Submit.  5.

CPU: 31. For example:Message.08Message. The Statistic and Message names you give must contain valid letters and/or numbers.Name2: abc DETAIL REQUIRED MEANING TYPE Statistic Yes A numeric value used to determine how the monitor compares to its set thresholds. SAM supports multiple values returned by a script using the following format.56Message. if you want to inform SolarWinds SAM that a VBScript reports Up status.Name1: abc Message. Note: Multi-line messages are supported.Name2: def There is a limit of ten Statistic and Message pairs for the script.CPU: svchost. Statistic. you must first return an exit code which results in an Up (0). Warning (2). or Critical (3) status. If the component only returns Down (1) or Unknown (4) on first use. Statistic.Name2: 456 Message No An error or information message to be displayed in the monitor status details. you would exit the script using code similar to the following.Name1: 123Statistic. Statistic.To correctly create this component monitor.RAM: svchost. When one of these exit codes is received the appropriate dynamic evidence table structure is created and all further exit codes are handled correctly.quit(0) Scripts with Text Output Scripts report additional details by sending text to the script’s standard output. where 0 reports Up: Wscript.RAM: 1234.Name1: xMessage.Name1: abc Statistic. These can be placed anywhere in the script output. Ten pairs are possible. EXIT CODE MEANING 0 Up 1 Down 2 Warning 3 Critical Any other value Unknown. for example 4 For example.exe cpu usage Statistic. This must be an integer value.exe ram usage 348 . Sample output: # Script comment: This shows two pairs. (negative numbers are supported). the appropriate dynamic evidence table structure is not created appropriately. To use this functionality print each line using a separate command.Name2: yMessage.

Count*2 ) &amp.Quit( 0 ) Else WScript.Echo( "Message: Folder Not Found" ) WScript.vbs [pathToFiles]" &amp.CreateObject( "Scripting.FileSystemObject" ) If fso.FolderExists( path ) Then Set objDir = fso.Quit( 1 ) End If WScript.Quit( 1 ) End If Set objFiles = objDir.vbCRLF &amp.Echo "Message. To use this script.Total: " &amp." WScript. copy and paste the following code into the Script Body field. In the Scripts Arguments field.Echo "Statistic: 0" WScript.Echo "Message: Usage: wscript. objDir." WScript.Echo "Statistic: 0" WScript. the total number of files in a folder."[pathToFiles] Local or UNC Path" WScript.Echo "Statistic: 0" WScript.Files If( IsEmpty( objFiles ) = true) Then WScript.Count ) WScript.vbs [pathToFiles]" &amp.Arguments If lstArgs. " files in this folder. CInt( objFiles.Twice: " &amp.Echo "Message: Usage: wscript.exe filelist.Echo "Statistic.Count ) &amp.Echo "Statistic: 0" WScript.Echo "Message. and twice the total number of files in the same folder. " = twice the number of files in this folder.Count = 1 Then path = Trim( lstArgs( 0 )) Else WScript. type in C:\Windows. CInt( objFiles.Echo "Message: Object Not Initialized" WScript.Quit( 1 ) End If Set fso = Wscript.Echo "Statistic.Total: " &amp. CInt( objFiles. fso. The code that represents these two values are bold. objFiles.Count*2 ) WScript.GetFolder( path ) If( IsEmpty( objDir ) = True ) Then WScript.vbCRLF &amp."[pathToFiles] Local or UNC Path" WScript.Example Scripts Below is a sample vbscript that returns two values. objFiles2 Set lstArgs = WScript. CInt( objFiles.Echo "Message: Object Not Initialized" WScript. path.Twice: " &amp. Option Explicit On Error Resume Next Dim lstArgs.Quit( 1 ) End If 349 . or any other folder you want to monitor.Echo "Statistic: 0" WScript.exe filelist.

There are several examples of Windows Script component monitors included in templates. Run 3rd Party Application. and Windows Event Log Count. LDAP Connection Monitor. These include: File Count. Sample scripts are installed on your SolarWinds SAM server. in the folder: C:\Program Files\SolarWinds\Orion\APM\SampleScriptMonitors\WindowsScripts 350 . File Modified.

351 . Agentless monitoring does not require these credentials. Prerequisites for Orion agent for Linux You need to include credentials that can run scripts on the monitored Linux-based computer.100). A maximum of 10 output pairs can be returned.net/docs/3_0/pluginapi. Enable Component This option determines whether or not the component is enabled. remove the excess output pairs or they are ignored. Disabling this component leaves it in the application as deactivated and does not influence application availability or status. randint(1.Nagios Script monitor This component uses SSH to upload a Nagios script to a Linux/Unix server. You have the ability to override the default description by adding to or replacing the text. 'random number: ' + str(randint(1. The second option allows you to use certificates for authentication.html.random%d: %s' % (stat_id. If you are using this component monitor with Nagios and polled by Orion agent for Linux. which is automatically saved. see http://nagios. Component Type This describes the type of monitor you are using. stat_id. you need to enter a script as follows. The variable to access this field is ${UserDescription}.100))) Field Descriptions Description This field provides a default description of the monitor. Authentication Type Choose either User name and Password or User name and Private Key. Statistic The statistic for this component monitor is the value returned by the script. This monitor has the ability to return multiple values.sourceforge. For more information.random%d: %d\nMessage. If you exceed the maximum allowed. runs the Nagios script on the server and then processes the script's exit code and text output. This component monitor has the ability to return multiple results and has the ability to process Nagios resulting output. The argument would be python $(SCRIPT) with a body of: from random import randint STAT_PAIRS_COUNT = 10 for stat_id in range(STAT_PAIRS_COUNT): print 'Statistic.

For more information. return codes of 1 result in a host state of DOWN.pl. see http://nagios. For example. The default value is 22. minus the length of the ${SCRIPT} variable after being resolved to a file name such as the following: APM_937467589. this means that the actual user Command Line input cannot be longer than 266 . If you need to pass a longer command line to the target 352 . The length of the Command Line field is limited to 266 characters for Solaris systems.net/docs/3_ 0/pluginapi.html. Count Statistic as Difference Changes the statistic to be the difference in query values between polling cycles. otherwise return codes of 1 will result in a host state of UP. or 250 characters (not including the length of the 9 characters for the “${SCRIPT}" variable itself). RETURN CODE SERVICE STATE HOST STATE 0 OK Up 1 Warning Up or Down/Unreachable† 2 Critical Down/Unreachable 3 Unknown Down/Unreachable _______________________ † If the Use Aggressive Host Checking option is enabled.16. and has sufficient rights on the target node to do whatever the script needs to do.sourceforge. Script Working Directory This field allows you to specify the working directory of the script process. Command Line This field is in the script editing window and allows you to specify the script you want to run on the target node followed by the arguments. if the script does something with WMI. Since the length of the file name will typically be around 16 characters. the credentials also need WMI rights on the target node. If the credential you need is not already present in the credentials list. Port Number This field allows you to specify the port number used for the SSH connection.Credential for Monitoring Select a Windows credential that is both a user who can log on to the SolarWinds SAM server. To enter your script. use the Quick Credentials section to add a new credential. Check Type This determines how the return code is evaluated. click the Edit button that reveals the script editing window.

sh Script Body This field is in the script editing window and allows you to enter your script via typing or pasting. The following table shows a list of valid return codes. Nagios scripts must exit with a valid return code and a line of text output. for example: /opt/sw/myscript. Warning (2). along with their corresponding service or host states. If the exit code is 0 (OK). return codes of 1 will result in a host state of Down. See Test script output for details. Scripts must report status through return codes Nagios determines the status of a host or service by evaluating the return code. You can access this field by using the variable.” User Notes This field allows you to add notes for easy reference. You can save these definitions to the component monitor for further configurations. you can create a shell script on the target node (for example: myscript. or Critical (3) status. otherwise return codes of 1 will result in a host state of Up. Every saved definition is listed as Script Output with an assigned number and name. the appropriate dynamic evidence table structure is not created appropriately. To return up to ten optional statistics. To correctly create this component monitor. you must first return an exit code which results in an Up (0). The default selection is “Show worst status. the component status may be further modified by thresholds from the optional statistics. The exit code determines the status of the component. RETURN CODE SERVICE STATE HOST STATE 0 OK Up 1 Warning Up or Down/Unreachable† 2 Critical Down/Unreachable 3 Unknown Down/Unreachable ___________________ †If the Use Aggressive Host Checking option is enabled. When one of these exit codes is received the appropriate dynamic evidence table structure is created and all further exit codes are handled correctly. ${UserNotes}. You can test the script to receive output definitions. node. If the component only returns Down (1) or Unknown (4) on first use.sh) that contains the long command line and place the call to this script in the Command Line field. Status Roll-Up This option allows you to choose how you would like the monitor to report based on the output provided by the script. separate the statistics from the status message with the pipe (|) symbol using the following syntax: statusMessage [|'statisticName'=value] 353 .

You may be prompted to specify a test node and credentials. On the Edit Script dialog. and additional configuration options. To save changes to the template or application monitor. Locate and edit the application monitor or template with the Nagios Script monitor.sourceforge." This error displays if the named fields could not be located in the script output. you may have an issue in the script. see http://nagios. To test the script and save output definitions:  1. Locate and expand the component using the Nagios Script monitor type in the template. Click Save to add the output definitions. Review the results to ensure all formatting is correct and fields properly load. display name. The component monitor will display the definitions with a unique ID. you may receive an error: "Script output values are not defined or improperly defined. | 'CPU%'=75. If you receive an error.  2. click Settings > All Settings > SAM Settings > Manage Application Monitors.Below is an example of valid output with a status message and two statistics: The script ran.2 'MemoryRemainingInKB'=600784 Test script output You should test the script output while editing the script prior to testing the script in the template or application component pages. Open the template or application monitor using the Nagios Script monitor. To open.  6. 354 .  5.net/docs/3_0/pluginapi. You can store the output definitions returned by the script test as Script Output in the component monitor. Locate the Script Body field and click Edit Script.  7. click Submit. click Get Script Output.  4. The results should populate with values returned by the script.  3.html. For more information on formatting and outputs. If the output formatting or values are not correctly defined or missing. Wait for the Output Result.

Credential for Monitoring Select a Windows credential that is both a user who can log on to the SolarWinds SAM server. Statistic The statistic for this component monitor is the Statistic value returned by the script. use the Quick Credentials section to add a new credential. Field Descriptions Description This field provides a default description of the monitor. However some PowerShell commands used in scripts require the use of the ${CREDENTIAL} variable. see the following KB article for some useful tips: https://support. If you exceed the maximum allowed. Execution Mode This field allows you to specify where to run the PowerShell script: 355 .0. If the credential you need is not already present in the credentials list. Disabling the component leaves it in the application in a deactivated state not influencing either SolarWinds SAM application availability or status. To create this monitor. the credentials also need WMI rights on the target node. which will then be automatically saved. The Windows PowerShell Monitor requires Windows PowerShell 2. remove the excess output pairs or they will simply be ignored. The PowerShell monitor handles requests from PowerShell for the credentials to run the script and resolves them using the selected Credential for Monitoring. It does not work with Windows PowerShell 1. If you are having trouble using the Windows PowerShell Monitor. Enable Component Determines whether the component is enabled.com/success_center/Server_%26_Application_Monitor_(SAM)/Problems_using_ the_Orion_APM_Windows_PowerShell_Monitor A maximum of 10 output pairs can be returned. See the note in the Script Body section below regarding the use of the ${CREDENTIAL} variable. if the script does something with WMI. see Create a Windows PowerShell monitor. and has sufficient rights on the target node to do whatever the script needs to do.0. The variable to access this field is ${UserDescription}.solarwinds. For example. You have the ability to override the default description by adding to or replacing the text.Windows PowerShell monitor This component monitor runs a Windows PowerShell script on the SolarWinds SAM server or a remote target node and then processes the script's exit code and text output.

the ${CREDENTIAL} variable should not be placed in the Script Arguments field. As a result. since it is set automatically.Custom.)  n Local Host can run scripts only locally. For WinRM 1. as shown in the following example: $avg = Get-WmiObject win32_process -ComputerName '${IP}' -Credential '${CREDENTIAL}' | Where-Object {$_.exe" } | Measure-Object -property ReadOperationCount -Average.  n URL Prefix .XXX} where xxx is the name of the custom property. (This works only in local script execution mode. Run the script under specified account Select this option to enable impersonation with the component's credentials. WRM should be configured separately to get it working with the Windows PowerShell monitor. it prompts for a password.specifies the TCP port for which this listener is created. The user name from the specified Credential for Monitoring is stored automatically in the ${CREDENTIAL} variable for you by the monitor.  n Port Number . Script Body This field allows you to specify the PowerShell script you want to run. This is the default value.if checked.specifies a URL prefix on which to accept HTTP or HTTPS requests. You may include the variable ${IP}. When the script is run by PowerShell. which is replaced by the IP address of the target node. specifies that the secure HTTPS protocol should be used to send and receive WS-Management protocol requests and responses. that is.  n If Remote Host is selected. Script Arguments This field allows you to specify arguments to pass to the script. the default HTTP port is 80. Custom Properties can be passed by using the following format: ${Node. such as the ${CREDENTIAL} variable.0. Some PowerShell commands (such as Get-WmiObject as shown in the example above) require the ${CREDENTIAL} variable. 356 . the default HTTP port is 5985.1 and earlier. The monitor automatically provides the password from the specified Credential for Monitoring. For WinRM 2. on the SolarWinds SAM server. The default is wsman.Count Statistic as Difference Changes the statistic to be the difference in query values between polling cycles. Use the ${CREDENTIAL} variable in the script where the credentials are required. the following options are available:  n Use HTTPS Protocol . Otherwise the HTTP protocol is used.  n Remote Host can execute scripts remotely (on the selected target node) using the Windows Remote Management (WRM) system component.Name -eq "lsass. You should not include variables that are stored automatically.

 4. Lsass. and that also has appropriate permissions to do whatever else the script requires (in this case. click Settings > All Settings > SAM Settings > Create a New Template  2. You can access this field by using the variable. then expand the Custom Component Monitors group.exe PowerShell Monitor. you want to monitor the average number of read operations performed to check for spikes. changing passwords. you can create a monitor that runs a Windows PowerShell script to monitor specific performance information for troubleshooting a Windows process that may be having issues. for example. In particular.User Notes This field allows you to add notes for easy reference. On the Web Console. and so forth.  n Remote Host can execute scripts remotely (on the remote target node to which the Windows PowerShell monitor is assigned) using the Windows Remote Management (WRM) system component. WRM should be configured separately to get it working with the Windows PowerShell monitor. and then select Windows PowerShell Monitor and click Add.  1. What needs to be monitored The process you want to monitor is lsass. Create a Windows PowerShell monitor With this.exe. If you exceed the maximum allowed. ${UserNotes}. A maximum of 10 output pairs can be returned. remove the excess output pairs or they will simply be ignored. on the SolarWinds SAM server. Click Add Component Monitor. Select the Execution Mode to use:  n Local Host can run scripts only locally. Select the Credential for Monitoring with appropriate permissions to run the script on the SolarWinds SAM server.exe process and monitor its value. 357 . to get the average number of read operations performed on the target node). Name the template. that is. You may need to log in with an administrator account to perform this action. You decide to use the Windows PowerShell monitor to run a PowerShell script that uses the Get-WmiObject call to measure the average ReadOperationCount for the lsass.  5.  3. which enforces security on the system for users who are logging on.

You can then access the value in the script body using the variable ${IP}.exe from the computer whose IP address is specified by the variable ${IP} using the credential specified by the variable ${CREDENTIAL}. 358 . This works only in local script execution mode. and then click Test to confirm the credentials and component monitor against the test node. Select Inherit credentials from template.  15. and then click Next. Select Count Statistic as Difference to change the statistic to be the difference in query values between polling cycles.  13. Select Lsass. Writes the statistic information gathered by the script. greater than 800. and then click Select.  16.  12.  8. select the desired target node for the PowerShell script.  b.  c. Click Set test node. Change the Statistic Critical Threshold to. Copy the following PowerShell script.exe PowerShell Monitor.exe process. if you type ${IP} for Script Arguments the PowerShell script will be able to access the IP address for the target node using the variable ${IP} in the script body. and then click Submit.  17. Change the Statistic Warning Threshold to. Click Test. When the script is run by PowerShell. Write-Host 'Statistic: ' $avg. it prompts for a password.  10.Name -eq "lsass.  14. Click All in the Select tag to filter by list. greater than 1000. The user name from the Credential for Monitoring that is specified is stored automatically in the ${CREDENTIAL} variable by the monitor.  9.  7. Browse the tree view. The monitor automatically provides the password from the Credential for Monitoring. Expand the tree view and select the target node.  6. into the Script Body field: $avg = Get-WmiObject win32_process -ComputerName '${IP}' -Credential '${CREDENTIAL}' | Where-Object {$_. The script does not perform error checking.exe PowerShell Monitor and then click Assign to Node.exe" } | Measure- Object -property ReadOperationCount -Average.Averageexit(0) The PowerShell code does the following:  a.  18. For example. Reads the average ReadOperationCount information for the process lsass. Click Assign Application Monitors and then click Done. which uses the Get-WmiObject call to measure the average ReadOperationCount for the lsass. Enter the following Script Arguments: Use the token ${IP} and the IP address will be filled in with the IP address of the target node. and then locate the Lsass.  11. Exits the script. Do not add the ${CREDENTIAL} variable in the Script Arguments field. Select Run the script under specified account to enable impersonation with the component's credentials.

com/success_center/Server_%26_Application_Monitor_(SAM)/Problems_using_ the_Orion_APM_Windows_PowerShell_Monitor 359 . Warning (2). the appropriate dynamic evidence table structure is not created appropriately. you must first return an exit code which results in an Up (0). Make sure that the RPC server is available and that the Windows PowerShell execution policy is not set to Restricted (the default setting).exe PowerShell Monitor Verify that you are entering the user name and password of an administrator-level account. If you think you have entered an incorrect credential. To correctly create this component monitor. or Critical (3) status. EXIT CODE SERVICE STATE 0 Up 1 Down 2 Warning 3 Critical Any other value Unknown.solarwinds. You can check the execution policy by entering the following command at the PowerShell command prompt: Get-ExecutionPolicy If you are having trouble using the Windows PowerShell Monitor.Report status through exit codes Scripts must report their status by exiting with the appropriate exit code. If the component only returns Down (1) or Unknown (4) on first use. The exit code is used to report the status of the monitor. which is seen by the user through the interface. for example 4 Troubleshooting the Lsass. see the following KB article for some useful tips: https://support. correct the mistake and then retest. When one of these exit codes is received the appropriate dynamic evidence table structure is created and all further exit codes are handled correctly.

as well as Warning and Critical thresholds for application monitors. refer to the following sections:  n Inheriting Thresholds  n Adjust threshold settings and apply baseline data  n Multi-Value scripts and thresholds  n Apply baseline thresholds at the template level  n Apply baseline thresholds at the application level  n View latest baseline details   360 . The option to enter thresholds manually remains available. Normally. Baseline data. an administrator would need to monitor applications for several weeks in order to collect enough data to be used as a baseline. If set too high. problems can occur without the administrator's knowledge. the administrator would be getting alerts all the time. By default. For more information.Application Monitor Thresholds Thresholds are markers that indicate certain levels have been reached. Once set. thresholds can act as trigger points. If thresholds are set too low. if you are monitoring CPU usage. the administrator can make an educated guess how to set Warning and Critical thresholds for the component monitors. You can use this threshold as a trigger to send an email alert to inform you of the Critical status once that threshold has been breached. Many component monitors used in SAM applications have thresholds that can be adjusted and set. I/O thresholds of Windows Service Monitors are not set. a Critical threshold set at 90% would be typical. For example. can be gathered and calculated automatically. Once a baseline has been established.

Inheriting Thresholds Thresholds can be adjusted at the template level or on the individual component monitor level of an application. only thresholds of the individual component monitor are affected. This means the component monitors within the application inherit the changes made in the template. Threshold Adjustments at the Template Level If adjusting thresholds on the template level. Threshold Adjustments at the Component Monitor Level If you change thresholds at the component monitor level. any changes made trickles down to the component monitor level for applications based on this template. Thresholds on the parent template. 361 . are not be affected. or other applications based on that parent template. either manually entered or calculated using baseline data.

Warning.DisplayName} n ${Threshold.Critical.DisplayName} 362 .Multi-Value scripts and thresholds The format for using the threshold macros with multi-value scripts is as follows: n ${Threshold.

 4.  5. This macro can be used when configuring alerts. as shown.  3.  1. select Statistic Threshold > Use thresholds calculated from baseline data. Select a component monitor. Thresholds can be used based on calculated baseline data or you can create your own thresholds based on your needs. click Save > Submit. You can edit multiple component monitors and their thresholds if the monitors are the same type and thresholds are available. Select Use thresholds calculated from baseline data: Once this box is checked. You may need to log in with an administrator account to perform this action.Apply baseline thresholds at the template level Applying and editing thresholds at the template level affect all applications that are based on that template.  2. Select the options for sustained thresholds. Select a template and click Edit from the toolbar. and then click Submit. ${USE_BASELINE}. click [+] to expand the monitor details. Edit thresholds. the Warning and Critical fields automatically populate with the macro. click Settings > All Settings > SAM Settings > Manage Templates. On the Web Console. After you click Multi Edit. 363 . Multi Edit only become available when the selected component monitors are the same type.

I/O thresholds of Windows Service Monitors are not set. 364 .By default.

 b. the values change and a blue icon appears indicating that baseline thresholds are being used. click [+] to expand the monitor details. From the Application Details resource. From the All Applications resource. The current values for the thresholds appear in the Warning and Critical fields. If selecting only one Component Monitor. click My Dashboards > Applications > SAM Summary. you can apply baseline thresholds at the application level. Click Multi-Edit. When applied.  1. Using the following instructions. and then click Multi-Edit. Click Use Latest Baseline Thresholds.  a. Multi-Edit only becomes available when the selected component monitors are of the same type. 365 . expand the tree and then click an application.  3. click Edit Application Monitor.  4.Apply baseline thresholds at the application level To customize your monitoring. On the Web Console. you can modify those thresholds per specific node. use the check boxes to select the monitors you want to edit. If selecting more than one component monitor.  2. The Orion Web Console has a set of global thresholds that apply to all monitored nodes. as shown:  c. You may need to log in with an administrator account to perform this action.  a.  5. Click Override Template.

 b. Click Save. Check the Statistic Threshold check box on the pop-up window. 366 . the Warning and Critical fields automatically populate with the macro. then check the Use thresholds calculated from baseline data.  6. Once the second box is checked. ${USE_BASELINE}. and click Submit.

seven days of data is the recommended minimum amount of data needed for baseline calculations to be considered accurate. baseline data is calculated on demand. are automatically calculated during nightly database maintenance. On the Web Console. click Settings > All Settings > SAM Settings > Manage Templates. the thresholds remain static until manually re-applied. however. Change the amount of data used in baseline calculations You may need to log in with an administrator account to perform this action. Apply baseline thresholds at the template level You may need to log in with an administrator account to perform this action. This is not a moving baseline that is calculated nightly based on the last seven days of data. and then click Submit. A moving baseline would mask data spikes and other anomalies that need to be highlighted. Thresholds set manually may yield more desirable results if you are familiar with the nuances of your environment. Check a template and click Edit from the toolbar. Baseline data for macros.  1. such as  ${USE_BASELINE}. 367 . Enter a number of days. click Settings > All Settings > SAM Settings > Data & Database Settings.  2.  1. Once thresholds are calculated and applied to component monitors.  2. The value for the Baseline Data Collection Duration field cannot exceed the value defined for the Detail Statistics Retention field (located at the top of the Data & Database Settings section). On the Web Console.Adjust threshold settings and apply baseline data In general.

Once Use thresholds calculated from baseline data is checked. Select the options for sustained thresholds as needed:  4. ${USE_BASELINE}.  3. If selecting more than one component monitor. click My Dashboards > Applications > Summary.  5. Click Use Latest Baseline Thresholds. click [+] to expand the monitor details.  a. If selecting only one component monitor.  2.  a. The Use thresholds calculated from baseline data check box does not become available until Statistic Threshold has been checked. select the monitors you want by checking the boxes next to their names.  3. From the Application Details resource. the Warning and Critical fields automatically populate with the macro. then click Submit.  b. ${USE_BASELINE}. From the All Applications resource. Check Statistic Threshold on the pop-up window. the Warning and Critical fields automatically populate with the macro. Apply baseline thresholds at the application level You may need to log in with an administrator account to perform this action.  1. 368 . Click Save. click Edit Application Monitor. Multi-Edit only becomes available when the selected component monitors are of the same type. as shown: Once this box is checked. Click Multi-Edit. expand the tree and then click an application.  b. On the Web Console. then check the Use thresholds calculated from baseline data.

 b.  6. then check the Use thresholds calculated from baseline data. When applied. click Edit Application Monitor. the Warning and Critical fields automatically populate with the macro.  5. From the All Applications resource. On the Web Console. Use latest baseline details You may need to log in with an administrator account to perform this action. as shown:  c. then click Submit. Note: Multi-Edit only becomes available when the selected component monitors are of the same type.  a. click [+] to expand the monitor details.  4.  2. Check the Statistic Threshold check box on the pop-up window. Click Save. From the Application Details resource. the values change and a blue icon appear indicating that baseline thresholds are being used.  b. If selecting more than one component monitor.  a. The current values for the thresholds appear in the Warning and Critical fields. Click Use Latest Baseline Thresholds. click My Dashboards > Applications > Summary. Once the second box is checked. 369 . use the check boxes to select the monitors you want to edit. and then click Multi-Edit. expand the tree and then click an application.  3. If selecting only one Component Monitor. ${USE_BASELINE}. Click Override Template.  1. Click Multi-Edit.

Click Manage Orion General Thresholds.  4. click a node to navigate to the Node Details page for that node. Make your selections. Click Override Template.  1.  4. then click Latest Baseline Details. In the Management resource.  3. Edit capacity planning thresholds You may need to log in with an administrator account to perform this action. The Capacity Planning options appear under each object:  5.  2. On the Web Console. 370 .  5. then click Submit on both the Orion General Thresholds screen and the Edit Properties screen. Find a component monitor in the list and click [+] to expand the monitor details. click Edit Node.

Click Override Template click Latest Baseline Details.View latest baseline details Details about how baseline data. Find a component monitor in the list and click [+] to expand the monitor details.  4. In the All Applications resource. click My Dashboards > Applications > SAM Summary. On the Web Console. This page details the data collection and calculation process using several graphs and tables. can be found on the Latest Baseline Details page.  1. expand the tree and then click an application.  5.  2. View the Latest Baseline Details Page You may need to log in with an administrator account to perform this action.  3. From the Application Details resource. click Edit Application Monitor. as well as Warning and Critical thresholds are calculated. 371 .

 n Create your first application and alert  n Monitoring Internal and External Web Site Performance  n Monitor IIS application pools  n Scan for applications to monitor  n Monitor VMware performance counters using an application monitor  n Monitor and restart stopped Windows services  n Creating a Windows PowerShell Monitor  n Monitor large directories  n Use the JMX component monitor wizard  n Configure the SOAP monitor 372 .Example tasks for application monitors These are scenarios for monitoring with SAM.

Enter thresholds or select Use thresholds calculated from baseline data. Alert on the WMI application via email  1. You may need to log in with an administrator account to perform this action. Select credentials or Inherit Credentials from Node. Applications created from templates are used to report metrics based on your needs. click Add. We also provide information for creating an alert for the WMI application to send email notices based on monitored thresholds. On the Web Console.  7.  5.  6. Click Submit. Click Add New Alert and name the alert. Name the template and click Add Component Monitor. You will create a template with added monitors. enter a WQL query to return a statistic to be reported.Create your first application and alert After applied to a node. click Settings > All Settings > SAM Settings > Create a New Template. This example provides steps for creating a template for monitoring WMI. On the Properties tab.  3. then apply the template to nodes for monitoring. Locate your template and click Assign to Node.  2. Choose the credentials.  3. In the Query field.  4. enter required information. and click Next. On the Web Console. click Assign Application Monitor. and click Next. click Alerts & Activity > Alerts > Manage Alerts.  3. also known as performance counters. Create a WMI monitor  1. Select the Windows node from the left pane. click the green arrow to move it to the right pane. click Settings > All Settings > SAM Settings > Manage Templates. On the Web Console. Apply the WMI monitor template You may need to log in with an administrator account to perform this action. which is comprised of component monitors. a template becomes an application.  4. Select WMI Monitor.  1.  2. 373 . then click Done.  2. configure the monitors.

 4.  8. For Trigger Actions. Enter the required information. Review and edit the Reset Actions and the Summary. then click Configure Action.  7.  5. 374 . complete the section as shown: Important: Add the second trigger condition by clicking [+]. then click Submit. the second for the specific application instance (indicated by 1 Object). select Send an Email/Page. The Manage Alerts page indicates the alert was created successfully. then click Submit.  6. click Add Action. The first trigger condition tests for Status (Down). For the Trigger Conditions. click Next and complete the wizard as instructed.

and then click Start Scan. SAM scans your network for applications. then click View results after the SAM scan is complete. Click View SAM Summary Page.  2. Enter the credentials for the servers you are scanning. Select applications from the displayed list to add as monitored nodes.  1. Select nodes by clicking [+] to expand the node groups. and then click Next. On the Web Console. click Settings > All Settings > SAM Settings > Scan Nodes for Applications.  3.Scan for applications to monitor You can scan for applications to monitor as added nodes through the Scan Nodes for Applications page. then select the nodes you want to scan. You may need to log in with an administrator account to perform this action.  4. Select applications to find. and then click Next.  5. 375 .

 6. www. and then click Next.  5. All usage and performance displays as a node with details pages of collected data.google. click Settings > All Settings > Add a Node.  7.  2. select Web Pages. make any changes.com).  1. and then drill down to your specific node in the All Nodes resource. click My Dashboards > Home. 376 . Navigate to the Node Details page to review the results. On the Web Console. and then click OK. On the Change Properties page. Select External Node: No Status. Add Node. and then click Next. Check Web Link and select Inherit credentials from Template. Click Test. Enter the Hostname or IP Address you want to monitor (for example. From the Show only: drop-down.  8.  3.  4. To do this. You may need to log in with an administrator account to perform this action.Monitor a specific URL You can add a specific URL as a monitored node.

then click Next. In this case. You may need to log in with an administrator account to perform this action.  8.  2. the first Host System). When done. Select whether you want to monitor A single system or Multiple systems. 377 . Select New Application Monitor. Therefore.  5. then click Next. used by application monitor templates and component monitors. Create. click Settings > All Settings > SAM Settings > Component Monitor Wizard.  3. or click Browse. monitors in the application created contain the special ${VMWARE_ENTITY_NAME} variable in the Entity Name field of the monitor. Then enter a name for the new Application Monitor. Choosing A single system provides specific counters that apply to the target system only. From the Edit Properties page you can modify settings as desired. choosing Multiple systems provides more generic counters that can be applied to multiple systems.  7.Monitor VMware performance counters using an application monitor Learn more about monitoring VMware performance counters. Select the desired VMware Entity to monitor.  9. Click [+] next to Component list to expand the list of counters or counters to be added.  1.  4. When the monitor runs. select the node from the list. Select a VMware performance counter. On the Web Console. then click Next. Select the counters to monitor for the selected Performance Object. click Next.  2. this variable is resolved to the first available entity on a target host with the desired Entity Type (for example. the Application Monitor created based on them can be considered as generic and assigned to different ESX/vCenter target hosts. Add components to the application monitor  1. then click Next.  6. Enter the IP address of the VMware node you want to browse. and then click Select. Choosing Multiple systems provides only aggregate performance counters (without instances). then OK. Select or enter the appropriate credentials. then select the desired Performance Object (group) to monitor.

The polling results for the new monitor are updated after a few minutes. DRS (Distributed Resource Scheduling). and EVC (Enhanced vMotion Compatibility). In a parent/child hierarchy of resource pools and virtual machines. 378 . Click View SAM Summary Page. This Entity Type is specific to vCenter systems. You can subdivide Resource pools by creating child resource pools. This object type provides methods for configuring and controlling a virtual machine. or resources spanning multiple hosts. the root resource pool is the single resource pool that has no parent pool.  n Resource Pool – Represents a set of physical resources which may be a single host. The cluster services such as HA (High Availability). including templates that can be repeatedly deployed as new virtual machines. In order to run. Your new VMware monitor appears in the tree view for the All Applications resource. a virtual machine must be associated as a child of a resource pool. 3.  n Cluster Compute Resource (only available if the VMware vCenter Performance Counter Monitor type is selected) – Data object that aggregates the computation resources of its associated Host System objects into one single computation resource for use by virtual machines.  n Virtual Machine – Managed object type for manipulating virtual machines. a subset of a host's resources. enhance the usefulness of this single computation resource.  n Host System – Managed object type that provides access to a virtualization host platform.

 5.  d. For more information about restarting Windows services with an alert action.  3.  b. Create the monitor  1. to create the assigned Application Monitor.  4. Click Done. Select the Trigger Actions tab and then click Add New Action. Click OK. Create. and then click Next. To send an e-mail notification for the service restart:  a. Enter the IP address of the Windows node you want to browse. On the Web Console. or click Browse.  2. then click Next. Select Windows Service Monitor. select the node from the list. You may need to log in with an administrator account to perform these actions. Complete the e-mail info and click OK. Check the services to monitor.  3. On the Web Console.  e. Click OK. Select Send an E-Mail / Page and click OK. Create an alert that restarts any stopped Windows services and sends an email  1. then click Next. Scroll to the bottom of the list in the Manage Alerts dialog. then click Next. and check the box for Restart a service.  8.  c. click Alerts & Activity > Alerts > Manage Alerts.  7.  4.  2. 379 . see Adding Alert Actions.  6.  5. Ensure that New Application Monitor Template Name is selected and then enter a name for your new template. then click Select. adjust thresholds as needed.Monitor and restart stopped Windows services Learn more about monitoring and restarting stopped Windows services. Highlight Restart a Service and click Edit. Enter or select the appropriate credentials. Select the desired nodes to monitor and then click Next. click Settings > All Settings > SAM Settings > Component Monitor Wizard. Click Add New Alert > Configure Alerts.

Select credentials with appropriate permissions to run the script on the SolarWinds SAM server.  2. Click Large Directory Monitor and then click Next.  e.  7. then click Submit. Displays the message with the folder name and the folder size.  b.  f. Displays the statistic (folder size in bytes).FileSystemObject and stores it in fs. Use the variable ${IP} for the IP address of the target node to which the monitor is assigned when the Windows Script monitor runs.Arguments(0) Set fs=WScript.  a. Retreives the folder name from the saved command line argument and stores it in folder.  c.Echo "Message: Folder " &folderPath & " is " & folder.Monitor large directories You may need to log in with an administrator account to perform this action. 380 .  a. and then click Done. click Settings > All Settings > SAMSettings > Create a New Template. On the Web Console. Enter itadmin in the Credential Name field and then enter your credentials. Creates the Scripting. Select All in the Show only list.Echo "Statistic: " & folder. then expand the Custom Component Monitors group.  c.  8. then click Submit.CreateObject ("Scripting. Click Test.  b. Locate and select the desired node and then click Next. click Settings > All Settings > SAM Settings  > Manually Assign Application Monitors.GetFolder(folderPath) WScript. On the Web Console.  4.  d.Size  6.  3. The Visual Basic code does the following:  a. select Windows Script Monitor. Name the template. Create an assigned Application Monitor by assigning the Large Directory Monitor template to the node.Size & " bytes large" WScript.FileSystemObject") Set folder= fs. click Large Directory Monitor and then click Next. Copy the following Visual Basic script to get the directory size into the Script Body field: Dim folderPath folderPath = WScript. Specify the critical and warning thresholds for the desired directory size. Enter the UNC path name for the directory to monitor into the Script Arguments field. Reads the first argument passed to the UNC path name for the directory to monitor and stores it in FolderPath.  g. click Add Component Monitor. click Assign Application Monitors. Click Manually Assign Application Monitors and Select All in the Show only list.  1.

381 .The script does no error checking.

exe instances.exe.  b. select the web server.WMI as the monitor type. From the SolarWinds Web Console. differentiated by application pools separately if you specify the application pool names in the component monitors. and then click Select. and then click Next. Change Monitor Name to Webpool1. Change the CPU Warning Threshold to greater than 40. Click OK. then click Next.  b. then enter webpool1 in the Command Line Filter field. Click Browse.  g. Select Process Monitor .  d. After creating the monitors for all five w3wp. and then click Next. and then click Next.  d.exe process on the web server.  k.exe.  e. then Change the CPU Critical Threshold to greater than 50.  f.  a.  1. Select New Application Monitor and enter Web Server Application Pools as the Application Monitor Name. click Settings.  i. From the Change Properties page. From the Add Application Monitors page.  3. Click the last page button to view the last page. Enter your credentials in the fields provided. Click Add a Node then enter the hostname or IP address of the Intranet web server.  h. Add Node. Create. Enter WebServerAdmin in the Credential Name field. then check the check box next to w3wp.  j. for example.  c.Monitor IIS application pools SolarWinds SAM can monitor five instances. Select the web server node. of w3wp. Click Add Another Component.  a. 382 . click Next. Find the wp3w. Check the ICMP (Ping only) check box and then click Next.  c. Add the web server to the Orion database. click Settings > All Settings > SAM Settings > Component Monitor Wizard. click Next. From the SolarWinds Web Console. then click OK.  2. and then click Next.

Non-numerical data is shown without a check box. For details. Protocol type.  3. Click Next. From here you can drill down to select the attributes you want by checking them. Add a JMX component monitor You may need to log in with an administrator account to perform this action. String data is not supported at this time. URL path. However.  5.  7. see the JMX monitor. adding this monitor to your environment has been made simple with the use of a wizard driven interface. Click Next. Only values that return numerical data can be monitored. For Server IP Address. Expand the folders by clicking the arrows (or [+]) to expand the tree view folder structure. click Settings > All Settings > SAM Settings > Component Monitor Wizard. Select JMX Monitor from the drop down list and then click Next.  2. 383 . On the Web Console.  1. The following MBean selection screen appears:  6. and Credentials for the remaining fields. click Browse.Use the JMX component monitor wizard Creating a standard template for this monitor is not practical because of the amount of variables in any one specific environment.  4. Add the Port number. then select the node you want to monitor.

which must be exposed on a URL. structures. you can specify values for the available arguments. list. and so on) must be user-defined in the XML format. and complex. It is recommended that complex arguments be used only by experienced users. the file is parsed automatically and the fields. Important: If changes are made to any of the base SOAP settings. A complex argument (e. A simple argument is one where you can define the value directly. highlighted below.g. There are two types of arguments. the Advanced Settings values should not be changed. The SOAP XML field contains the SOAP envelope which is generated by the WSDL and dynamically changes as you make changes to the SOAP settings. the content of the SOAP XML is re- generated and your changes become lost. Once the WSDL file is successfully loaded.Configure the SOAP monitor The are two ways to configure the SOAP monitor:  n Loading a WSDL file. 384 . simple. Once the WSDL file has been successfully loaded. The Advanced Settings are read-only and displays additional information. In this field you can check what is to be sent to the web service. classes. Load WSDL Files The SOAP monitor within SAM currently supports the WSDL schema.  n Manually entering XML. Because the SOAP envelope is based on the WSDL schema. populates.

SAM automatically takes the code and place it where it belongs in the envelope: <tempPhoneNumber xmlns:ns2="http://schemas.org/soap/encoding/" xsi:type="ns2:Array" ns2:arrayType="ns1:TemporaryPhoneNumber[3]"> <item xsi:type="ns1:TemporaryPhoneNumber"> <startDate xsi:type="xsd:int">37060</startDate> <endDate xsi:type="xsd:int">37064</endDate> <phoneNumber xsi:type="xsd:string">+1-212-5551234</phoneNumber> </item> 385 .Manually Enter XML The following is an example of a Complex argument and would be placed in the Parameters field.xmlsoap.

<item xsi:type="ns1:TemporaryPhoneNumber"> <startDate xsi:type="xsd:int">37074</startDate> <endDate xsi:type="xsd:int">37078</endDate> <phoneNumber xsi:type="xsd:string">+1-212-5554321</phoneNumber> </item> <item xsi:type="ns1:TemporaryPhoneNumber"> <startDate xsi:type="xsd:int">37088</startDate> <endDate xsi:type="xsd:int">37092</endDate> <phoneNumber xsi:type="xsd:string">+1-212-5557890</phoneNumber> </item> </tempPhoneNumber> XML can also be entered manually by typing or pasting XML. 386 .

which is accessed through a single Virtual IP (VIP) address to route incoming requests and messages to the current. the secondary server becomes the active server and continues to act as the active server until another failover event occurs. such as the SolarWinds Information Service. and NetFlow information through the VIP. the software initiates a failover to the standby server. and virtual-to-virtual failover in an IPv4 LAN environment. the HA feature allows your secondary server to take over all services. The secondary server assumes all of the responsibilities of primary server. virtual-to-physical. place your secondary server on the same subnet as the primary server. SNMP traps. The SolarWinds HA software monitors the health of both servers in the pool. 387 . including receiving syslogs. After a failover to the secondary server is complete. SolarWinds supports physical-to-physical. and additional polling engines. add both servers to an HA pool. How does it work? When you configure your environment for SolarWinds High Availability. with minimal downtime. also known as your main polling engine. SolarWinds HA protects your main server. active server. In the Orion Web Console. When a critical service goes down. such as polling and alerting. If your primary server fails. physical-to-virtual. Configure the secondary server to use the same network and database resources as the primary server.High Availability in SolarWinds products SolarWinds High Availability (HA) provides failover protection for your Orion server and additional polling engines to reduce data loss. and both servers keep open communication channels over TCP port 5671 to exchange information. If the service goes down a second time within a set amount of time. the software attempts to restart the service. It does not protect your databases or your additional web servers. You can manually failover to your primary server to return it to active service.

The IP address with the most consecutive. All inbound communication goes through the VIP address.  n Use your original Orion server's IP as your VIP. you must make configuration changes to your devices because the HA pool may send polling requests from one of three IP addresses. How do I choose a VIP address? You have two options when choosing a VIP address. The VIP and each pool member must be part of the same subnet.What is a Virtual IP address? A Virtual IP (VIP) address is an IP address that is shared by both members of a HA server pool. may be sent by the primary or secondary server's IP address or the VIP address. and add a new IP address to your manually configured network adapter for your Orion server. Windows chooses which IP address is used as the originating IP address. The IP address with the most high order bits that match the destination of the next hop is used as the source IP address for all outbound polling activity. You can determine the source IP address by doing the following:  1. This option requires no device configuration change if your devices can only send information to specific IP addresses. Convert the IP addresses to binary. Because there are multiple IP addresses bound to a single NIC.  n Use a new IP address as your VIP when you have no device restrictions. matching bits is used for the HA pool's source IP address. The active pool member has a minimum of two IP addresses available: the IP address of the server and the VIP address for the pool. the other pool member takes over the VIP address and responds to requests sent to the VIP. such as WMI or SNMP polling requests. compare how many bits in the IP addresses match the default gateway's IP address. SolarWinds High Availability does not support IPv6 addresses.  2. Which IP address is used as the source? Outbound communication from the HA pool. This allows devices that you have configured for limited access to a set number of IP addresses to continue to send information to the same IP address. You can use SolarWinds Network Configuration Manager to update your router and switch configurations. When a member of the pool goes down. If you lock down the IP addresses you send information to and receive information from. 388 . From left to right.

NetFlow.15. Reserve an available IP address to use as the Virtual IP (VIP) address on the same subnet as the primary and standby servers.62 00001010-11000111-00001111-00111110 26 In this example. such as syslog.61 00001010-11000111-00001111-00111101 26 Secondary pool member 10.20 00001010-11000111-00001111-00010100 27 Primary pool member 10. When a failover occurs. Open port 5671 (TCP) on the primary (incoming) and standby (outgoing) servers.199.  2.15. It has 27 consecutive matching high order bits to the default gateway. and accessing the Orion Web Console.61 00001010-11000111-00001111-00111101 26 Secondary pool member 10.  1.199.62 00001010-11000111-00001111-00111110 26 The longest match in the example above is the VIP. IP ADDRESS IP ADDRESS CONVERTED TO BINARY # OF MATCHING BITS Default Gateway (first hop) 10.15.15. 389 .199.199. The VIP address is only used for inbound traffic.1 00001010-11000111-00001111-00000001   VIP 10.15.   IP ADDRESS IP ADDRESS CONVERTED TO BINARY # OF MATCHING BITS Default Gateway (first hop) 10. Examples of matching the binary bits The following is an example where the VIP is used as the outbound IP address.15.  4.199. Build a standby server on the same subnet as the server you want to protect. SNMP traps. the longest match is the pool members' IP addresses.15.199.15. You can also modify the converted bits to be the IP address with the longest match and convert it back to an IP address. the IP address of the active Orion server is used as the source IP for all polling requests. The following is an example where pool members' IP addresses are used as the outbound IP address. Before you begin. review the requirements and how to choose a VIP address.82 00001010-11000111-00001111-01010010 25 Primary pool member 10.199.199. These ports are not required when protecting additional polling engines. Open ports 4369 and 25672 (TCP) on the main Orion server and its standby server.Choose an IP address close to the default gateway's IP address so outbound communication comes from the VIP address.  3.1 00001010-11000111-00001111-00000001   VIP 10. High Availability deployment walk-through The following provides a high-level walk-through of how to set up high availability protection on your main server or additional polling engines.

or NetFlow data to your Orion server to use the VIP instead. Before you begin.  n Modify your DNS to point your Orion Web Console's host name to the VIP. On the dialog. server takes over all tasks in case of a failover.  5. click Get started setting up a server. SNMP traps.  4.  2. Open the Orion Web Console. Optional deployment steps Depending on your network and device configuration. Download or move the backup server installer on the secondary server.  3. The installer uses the information on the main server or polling engine to install the correct products and product versions. Activate your HA pool licenses. Create your HA pool. You can open the main server's Orion Web Console while logged in to the secondary server to download the server software instead of moving the installer to the secondary server. 390 .  n Modify devices that send syslog messages. Click Settings > All Settings > High Availability Deployment Summary. See What is a Virtual IP address? for more information.  n Modify the firewall settings to all communication to the VIP address and from the primary and secondary servers. you may need to perform some or all of the following steps. Set up the standby server Your secondary. Depending on your network setup. or backup. Click Setup a new HA server.  6. Download and install the secondary server software. If you upgrade an HA pool member. the products installed on the secondary server must match your primary server.  n Modify devices' SNMP settings to accept requests from the VIP address and the primary and secondary IP addresses.  1. you may be able to change your primary server's IP address to another address in the subnet and use the already established SolarWinds IP address as the VIP address. you need the credentials for your SolarWinds Orion SQL database.  7. including the version numbers.

If a HA pool license is not available.  2. You may need to refresh the page to see the correct pool and server status. it is the standby member. the main Orion server must stay up. If the main server is down for more than 14 days. Enter the pool name and the virtual IP (VIP) address. On the Setup a High Availability Server dialog. A failover audit event is logged when you create the pool. click Download installer now. Each server is called a pool member and can take over all responsibilities of the other server.  n Enter your SQL credentials for your Orion SQL database when prompted. The main Orion server does not require Internet access.  7. Set up an HA pool An HA pool is a group of two servers that have access to the same network and database resources. Because of the web-based License Manager. you are prompted to activate an HA pool license.  4. click Settings > All Settings > High Availability Deployment Summary.  6. The VIP must be unassigned and on the same subnet as the primary and secondary servers. Failover events will be logged and you can receive email notifications. Your main server or additional polling engine is now highly available and can failover to the standby server. When the pool is created.  3. When a pool member is waiting to take over. you need the following:  n A VIP address  n The secondary HA server  n An available HA pool license  1. The pool includes one main server or additional polling engine and one secondary server or polling engine. Before you begin. it is the active member. Click Setup High Availability pool next to your standby server. When a pool member is sending and receiving data. Move the downloaded installer to your secondary server and run it. your licenses may be invalidated. 391 .  5. In the Orion Web Console.  n Select which type of backup server you want to install under High Availability. Activate your HA pool license. the High Availability Deployment Summary displays the active and standby servers grouped under the pool name. You can now add the backup server to a pool with your main server or additional polling engine. Click Create Pool to complete the pool setup.

SolarWinds recommends disabling this setting due to a potentially large message volume. By default. or resource. Facilities are used to gauge the health of the system and may trigger a failover condition. Provide the interval in seconds. Resources are generally SolarWinds specific processes or services that are monitored by the High Availability software that can trigger a failover condition. SolarWinds recommends disabling this setting due to a potentially large message volume. Set up the default High Availability email The information you provide in the default email action is used to send email messages when there is a status change in an HA pool member. For example. facility. the computer may restart and failover if the CPU stays over 100% for a significant amount of time. High Availability notifications do not depend on the SolarWinds alerting service or the Orion database so you receive High Availability alerts when the service or database is down. Default interval to consider a member as down in a pool Define how long the active pool member can be down before a failover occurs. Email me when facility status is changed Receive email messages when the status of a low-level component changes. the active server fails over to the standby server. such as the polling or job engines. 392 . such as the percent used of the CPU or RAM. Email me when server status is changed Choose to receive email messages when a failover occurs. This is enabled by default and uses the default email settings to send notifications. if the job engine is down and does not restart successfully. High Availability is enabled and an email is sent when a failover occurs.SolarWinds recommends that you perform a manual failover after you create your pool and observe the data collected to ensure that all network and device changes are correct. You can change the default interval and modify your default email settings. Email me when resource status is changed Receive email messages when a SolarWinds Orion component changes. Configure High Availability settings Click Settings > All Settings > High Availability Settings to access these options. For example. This is also used as the default information for the Send an Email/Page alert action.

Select a license.  3.com. You do not need to purchase a second additional polling engine license or additional product licenses for the secondary servers and polling engines in your HA pools. High Availability-specific notifications are sent independent of the SolarWinds alerting service.  1. Separate email addresses with a semicolon. Click Settings > All Settings > License Manager. Click Settings > All Settings in the menu bar.  4. which is an internal grouping of a primary and secondary server.  5.com. Enter your license information. Enter the default SMTP server information. activate all of your HA pool licenses.  2. Click Configure Default Send Email Action. 393 . Click activate.  3. you can still receive email notifications for failover events as long there is a network connection available and your SMTP server is up.While the information in the default email action is used by default for all SolarWinds email notifications. Provide the default sender and reply address.com  4.  1. How failovers work After High Availability is enabled and you have set up a pool.  2. For example: email@company. email2@company. Activate High Availability pool licenses High Availability is licensed per pool. You receive a 30-day evaluation license for an unlimited number of HA pools. each pool monitors itself for failover conditions such as:  n Inability to connect to the network  n Stopped SolarWinds services Stopped Agent services is not a failover condition. When you set up your HA pools. Under the Default Recipients heading. distrolist@company. provide the email addresses of all default recipients for any email alert action. Licenses are automatically assigned to the pool with the Main poller and then to pools without licenses. Selecting SSL encryption automatically changes the SMTP port number to 465. When the SolarWinds alerting service or the database is down. If you are setting up multiple pools. each pool automatically consumes one HA pool license until no more licenses are available.

the Orion server tries to allow the service to recover before failing over to the secondary server. When you upgrade a product that is installed on a pool member. An email is also sent to your default recipients. If the job engine fails again within 1 hour. If the job engine fails within 61 minutes.  n Power loss  n Network connection loss to the primary server When a monitored service is down. if the job engine service is down. For example. 394 . If the same service fails within the default self-recovery period. then a failover occurs and the event is logged. a failover event is logged and can be viewed in the Event Summary resource or the Events view. Upgrade High Availability pool members Pool members must have the same SolarWinds products and product versions installed. the pool is disabled and cannot be enabled until the product is also upgraded to the same product version on the other pool member. When a failover condition is met and failover occurs in a pool. a failover occurs. a failover does not occur. the High Availability software attempts to restart it.

395 . such as a server becoming unresponsive. You can alert against volumes and nodes with most Orion Platform products. You can still customize individual email actions if you configure the default email action.Use alerts to monitor your environment An alert is an automated notification that a network event has occurred. or information that you may need to request from other departments. you can create an alert to notify you if a node in a specific location goes down or if the network response time is too slow when you have NPM. Configure the default information in the email action The information you provide in the default email action is used to populate the Send an Email/Page action. and applications. You can schedule alerts to monitor your network during a specific time period. The types of events for which you can create alerts vary. Alert preconfiguration tasks Some alerts require extra configuration. databases. and create alerts that notify different people based on how long the alert has been triggered. Alert actions that require set up before creating or configuring alerts include:  n Send an email or page  n Dial a paging or SMS service  n Play a sound when an alert is triggered  n Send an SNMP trap  n Use the speech synthesizer to read alerts Monitored objects in the SolarWinds Orion database must exist before creating or configuring alerts. Use the following topics to get started if you have never used Orion Platform products:  n Alert preconfiguration tasks  n Best practices and tips for alerting  n Navigate to the Alert Manager  n Create new alerts to monitor your environment  n Alert me when a server goes down You can also view our Alert Lab on THWACK for community-based alert information. depending on the Orion Platform products you have installed. You can create alerts for any monitored object. The network event that triggers an alert is determined by conditions you set up when you configure your alert. For example. Monitored objects can include items such as nodes. you can receive alerts about application response times or when your Exchange mailbox database is almost full. If you have installed SAM. separate software installations.

You can customize the alert actions for those alerts. Plan which devices to monitor To reduce the number of alerts sent out. Click Configure Default Send Email Action. Selecting SSL encryption automatically changes the SMTP port number to 465. Click Settings > All Settings in the menu bar. you may want to receive alerts only for mission-critical interfaces instead of every interface on a device. Use the out-of-the-box alerts as templates SolarWinds recommends using the alerts that are included when you install the product as templates for your new alerts. consider which devices are most important. For example. use the alert as a template. Restrict who receives alerts During your initial evaluation and testing. you do not want to receive notifications for all of your servers.  2. Best practices and tips for alerting Use these best practices and tips to help you configure and test your alerts. Provide the default sender and reply address. This can prevent overloading your email server while you fine-tune your alerts. provide the email addresses of all default recipients for any email alert action.  1. distrolist@company.  3. like the following: email@company.  n Separate email addresses with a semicolon. Fields are pre-populated so you can skip to specific parts of the Alert Wizard where there is data you want to change. Find an alert that is similar to one you want to create and then click Duplicate & Edit in the menu bar.  n All email actions require a designated SMTP server. but if the router goes down and the servers can no longer be polled. For example. enable them in your environment. 396 . you may want to be emailed if servers in your server farm go down.  5. send alerts to a few people instead of to a large distribution list. Enter the default SMTP server information.com. Under the Default Recipients heading. Establish dependencies Establish dependencies to prevent you from receiving duplicate alerts that stem from a single network event. email2@company.com  4. Enable out-of-the-box alerts If there are out-of-the-box alerts that match your monitoring needs.com. If you want to modify the conditions.

 n Active Alerts Details  n From the Active Alerts Details page. The name is displayed in the Alert Manager and can be used to sort your alerts. edit. You can skip to different steps if you clicked Duplicate & Edit or if you are editing a saved alert. When the alert is enabled.  6. or duplicate an alert that is similar to the alert you want to create.  4. including which users can view the alert. click Manage Alerts. Name of alert definition This is a required field. consider a naming convention that allows you to quickly scan through them. 397 . If you intend to create a large number of alerts. Set alert properties After creating a new alert. Review your alert. delete. it is added to the list of available alerts in the Alert Manager. Schedule when you want the alert to monitor your environment. it immediately monitors your environment for the conditions necessary to trigger it.  1.  2. severity. and how frequently the alert conditions are evaluated. Define what happens when the alert is reset.  7. Enter the alert properties. which includes who can view the alert.Navigate to the Alert Manager Use the Alert Manager to create. use the Alert Properties to describe the alert. Define what happens when an alert is triggered. You can access the Alert Manager in one of three ways:  n Settings Page (Recommended)  n Click Settings > All Settings in the menu bar. Create new alerts to monitor your environment Navigate to the Alert Manager to create a completely new alert definition. Define the conditions must exist to trigger the alert. click Manage Alerts in the Management resource. Under Alerts & Reports.  5. enable. or disable alerts.  n Node Details  n On the Node Details page. Define what event occurs to reset the alert. Once you have created an alert. including the number of alerts that will be triggered based on the conditions you defined. and then click Manage Alerts. navigate to the All Alerts this Object can trigger resource.  3.

Child conditions are represented as a line item under the Actual Trigger Condition. such as a changed IP address. but by when the change is reported based on the polling interval. you may want to disable this alert until it is ready for use. see the Alert me when a server goes down topic. Alert Custom Properties Use custom properties to organize your alerts. You can have multiple trigger condition blocks with multiple child conditions. Evaluation Frequency Set how frequently you want to evaluate the conditions. Use the Show List link to view all of the objects that the alert monitors. If you choose to alert on an event. Alert Limitation Category Restrict who can view the alerts. Severity of Alert Control how the alert in the Active Alerts resource looks. the condition is not evaluated by frequency. Create a new alert limitation by editing or creating a user account. If you are in the process of refining your alert. 398 . Filter your environment to only display the objects you want to monitor in The scope of alert. The alert is enabled. Description of alert definition Describe the alert. Define the conditions that must exist to trigger an alert The trigger condition is the most complex step in creating an alert. you can use "Email NetAdmins when router goes down" as the name of an alert. Before you begin. This is displayed on the Manage Alerts page. you can create a "Responsible Team" custom property and use it to help audit who receives specific alerts. Trigger conditions are built using child conditions that are evaluated in order. you may want to revisit the Best practices and tips for alerting. SolarWinds recommends using intervals longer than one minute to evaluate alert conditions. so important information should be near the front. To see an example of completed trigger conditions. managed service providers can restrict alerts to their specific customers. For example. Enabled (On/Off) Choose to evaluate the alert immediately after it is created and saved. For example. For example. and use the severity to group or filter alerts more easily. You must create a custom property for alerts before you can use it in an alert. SolarWinds recommends a name that describes the condition and most visible alert action. Shorter frequencies can negatively impact your network performance or computing resources.

SolarWinds' community website. or visit THWACK. 1.  d.At least one child condition must be false  b. such as Status and OS  n Add And/Or block . the comparison is "is equal to" and the value is "Down". Click the + sign to add child conditions.  c. enable complex conditions under Advanced options. like Status  n Add Double Value Comparison . See Building Complex Conditions for more information.  a. You can monitor all objects in your environment or filter your environment to a specific set of objects.  3. Select how you want to compare the polled value of the field to the value entered here. In the example screenshot. and then select which field you want to evaluate. Choose if the child conditions must be true or false to trigger the alert.Every child condition must be false  n At least one child condition must NOT be satisfied .Every child condition must be met  n At least one child condition must be satisfied (OR) . for support from other users.  n All child conditions must be satisfied (AND) . In the example screenshot. To use more complex conditions. or use the drop-down menu at the top of the block to delete the entire condition.The child condition evaluates two conditions. such as evaluating when an application on a specific server is down and a different application on another server is down. and then enter the value.At least one child condition must be true  n All child conditions must NOT be satisfied . You can evaluate objects based on variables or macros.  e. Create your trigger condition. Choose what objects you want to monitor in the I want to alert on field. Select the object you want the child condition to evaluate.  n Add Single Value Comparison (Recommended) . the object is "Node" and the field is "Status".Adds a sub condition block Use the X at the end of each child condition to delete it. Establish how much of your environment you want to monitor in The scope of alert.The child condition evaluates a single field.  2. 399 .

Trigger conditions that involve volatile components. if the trigger conditions still exists after 48 hours. you can move to the next step in the alert wizard.168. can trigger excessively with this reset condition. If you have successfully created an alert condition.4. This reset condition is especially useful to remove event-based alerts from Active Alerts. For example. which is as soon as the objects are polled for this example. You can use the Condition must exist for more than option in the trigger conditions in conjunction with this reset condition. This option prevents multiple alerts firing if the condition is temporary. the alert is removed from Active Alerts. The alert is reset and triggers as soon as the trigger condition is detected. the "Email me when a Node goes down" alert automatically resets when the node comes back up. this selection automatically resets the alert.32 goes down. The Summary step evaluates the conditions against your environment and returns how many objects will trigger the alert.  n Reset this alert automatically after Select to reset an alert after a set amount of time has passed. such as high CPU utilization. You can also add actions that occur when the reset conditions are met. When reset conditions are met.168. 400 . If the trigger condition is no longer true when the objects are next polled. Define the conditions that must exist to reset an alert Use the reset condition to define what must occur to remove an alert instance from the active alerts list. and entering how long the condition must exist.32 goes down. you can use this to trigger your alert actions again. escalation actions are halted. If you have created reset actions. the reset actions fire.  n Wait before sending an alert by selecting Condition must exist for more than. When the alert is reset.  f. all trigger actions stop and a new alert fires the next time node 192. For example. For example. If node 192. the alert fires for that specific instance of the trigger condition and any escalation levels you create continue until you reset the alert.  n Send an alert immediately when the condition is met by clearing any selection for Condition must exist for more than. the escalation levels that occur after this interval do not fire. You can use the built-in reset conditions or create your own. If this interval is less than the amount of time you wait for different escalation levels. After the alert is reset. This prevents receiving alerts when the alert condition. Select one of the following reset conditions:  n Reset this alert when trigger condition is no longer true (Recommended) SolarWinds recommends using this reset condition. such as high CPU utilization. Choose how long the condition must exist before an alert is triggered. occurs briefly or only once during a certain time period.4. you can create an alert that triggers when nodes in your lab go down.

you can schedule the alert to monitor your network during off hours. when the alert for node 192. Schedule when an alert monitors your environment You can configure when an alert monitors your environment. See Define the conditions that must exist to trigger an alert or Build complex conditions for more information on creating conditions.  2.168. alerts monitor your network for changes all the time.  1.  n No reset action The alert is active and is never reset.168. a new alert for 192. To re-trigger the alert.32 going down fires. or go back to previous steps. you can choose to reset the condition when the node has been up for more than 10 minutes. Click Add Schedule. For example. For example. you can proceed to the next step. Select Specify time of day schedule for this alert. If there are no errors. By default.32 fires every time the node is down when it is polled.4. and disable the alert during your maintenance windows.Trigger this alert each time the trigger condition is met The alert fires each time the trigger conditions are met.  n Create a special reset condition for this alert Select to build a specific reset condition. The alert wizard evaluates the reset condition for errors. 401 .4. the alert must be manually cleared from the Active Alerts view. Alerts must be enabled to allow schedules to run. You can create multiple schedules that control when an alert is enabled or disabled.  n No reset condition . For example. Schedule when you want to monitor your network for the trigger conditions you created for the alert.

 n Right now . This option is useful when you have quarterly or monthly maintenance windows. You can also set up escalations levels so that different actions occur if the alert has not been acknowledged quickly enough. including its schedule and execution settings. weekly. such as Thursday. You may want to disable alerts during a weekly maintenance window.  n Frequency Choose when to monitor on a high level.  n Enable or Disable every These options change based on the frequency.  n If you selected Weekly: Choose which days the alert is enabled or disabled. Alert actions can also have schedules. but may help you organize or troubleshoot your schedules.  n Specific Date . Choose either a specific date. Define what happens when an alert is triggered Choose actions that occur whenever the trigger conditions are met. off-site backups of your critical data.  n Starting on Choose when to begin the schedule. You can create a new action or use an action that you have already created. When you add a schedule to an alert. If you do not enter a name.  n If you selected Monthly: Choose which months the alert is enabled or disabled. it is enabled all other times unless otherwise scheduled.  n If you selected Daily: You can choose to enable or disable the alert every few days. Click Add Schedule to create the schedule.  n Ending on Choose an end date for the schedule. or a day. a name is automatically generated from the time period. you are also reusing all of its configurations.  3. or monthly. or does not monitor during that time. When you reuse an action. such as June 22nd. so not all alert actions may occur during the scheduled period. For example.  4. you may want to disable network or disk activity alerts if you run daily.  n Enable or Disable alert during following time period If you choose to disable the alert.Start the schedule immediately. You can also select business days. the alert only monitors during the time period you have scheduled. what you enter into the Message displayed when this alert field is displayed in the All Active Alerts resource. Enter the following information:  n Schedule Name This is not required. such as daily. 402 .Select a time and day to begin the schedule. up to every 31 days. Add actions to alerts By default. if necessary.

Select one or more actions from the list. For example.You can select both options. 403 .You can choose different actions to occur at different times of the day or month. You can configure the alert to perform different actions per escalation level. Each action requires different information.This is not required. or a single option.  3. SolarWinds recommends that you notify a small number of users while you fine tune your alerts. Each action has the following sections:  n Name of action . If you are alerting others through email. Escalation Level 1 contains all initial actions that you want to occur when the trigger conditions are met and the alert activates. if you want to send a page. you can add that action to a separate alert. Some actions require extra configuration steps. Select from the list of Alert Trigger Actions for more information per action. See Alert Actions for a complete list of available actions.  1. including schedules. Select an action from the list.  n Time of Day . Add a preexisting action to the alert You can add actions that have already been configured to an alert. Click Assign. is used in every alert the action is assigned. Enter the necessary information for the action.  n Do not execute this action if the alert has been acknowledged already (Recommended)  n Repeat this action every X minutes until the alert is acknowledged  5.  2.  4. specific information. Click Configure Action.  3.  1. or special software. If you use a preexisting action. Click Add Action. Click Assign Action(s).  n Execution settings . Escalation Levels 2 and above include all actions you want to occur if no one acknowledged the alert during the previous escalation levels. but makes it easier to organize and find your actions in the Action Manager. neither option. See Alert preconfiguration tasks. Add what happens when an alert is not acknowledged Escalation levels in Orion Platform products refer to user-defined time intervals between when an alert is activated and when a user acknowledges that alert. if you configured an action to reboot a VM.  2. Click Add Action to save it to the list of actions in the alert. you might send it to a different person on weekends or holidays rather than during the week. For example. any configuration change you make to the action.

You can copy all of the actions as Reset Actions. click Copy Actions From Trigger Actions Tab.This is not required. if you want to send a page. Click Add Action to save it to the list of reset actions in the alert. the actions will be performed in the order that they are listed. When an alert is reset. Each action requires different information. In an existing alert.  n Time of Day . Reset actions are usually used to notify others that the situation has been resolved or to write the resolution to a log file. such as writing to the log that the issue has been acknowledged.  1. You can test each action to ensure the action does what you expect it to do. For example.  3. Choose how long you want to wait after the previous escalation level before performing the actions in the new escalation level. See Preconfiguration Tasks. Click Copy Actions to Reset Actions Tab. To perform the same actions as when the alert was triggered. Define what happens when the alert is reset Use reset actions to perform specific tasks when an alert is no longer active. When an alert is triggered. then the actions fire in the second escalation level. Select from the list of Alert Actions for more information per action.  1.For example. Click Configure Action. you might send it to a different person on weekends or holidays than during the week. Enter new actions in this escalation level. These actions may include emailing managers or other backup staff. click Trigger Actions. 404 . Select an action from the list. if an alert for a critical server activates and all of the recipient or first-level responders are out for training and do not acknowledge the alert.  3.  4.  4. You can test each action to ensure the action does what you expect it to do. Click Add Action. specific information. but can make it easier to organize and find your actions in the Action Manager. or special software. Below the action. This lets you quickly craft actions to indicate that the issue has been acknowledged or resolved.  5. Some actions require extra configuration steps.  2. the actions will be performed in the order that they are displayed on the list. Each action has the following sections:  n Name of action .You can choose different actions to occur at different times of the day or month. Use the copied trigger actions as a base and modify them to reflect that the alert is no longer active.  2. See Alert Actions for a complete list of available actions. click Add Escalation Level. Enter the necessary information for the action.

and then click Trigger Condition or Next.10. You can further refine your scope by entering another AND condition. In The scope of alert. Commonly created alerts The following sections walk you through the easiest method to create common alerts and include tips on how to build more complex alerts.  2. Search for "Email me when a Node goes down" in the Alert Manager. by expanding Alert Integration. such as AlertCentral or Web Help Desk.Review the alert's configuration The Summary tab allows you to check your alert definition before you save any changes. it is added to the list of available alerts in the Alert Manager. such as "Notify me when Windows 2008 servers go down".  1. This box lists the number of objects that will trigger the alert immediately based on your current trigger condition. select Only following set of objects. you can enter Node IP Address starts with 10. When the alert is enabled.  5. Once you have created an alert. review the information box above it. You can integrate your alerts with other SolarWinds' products. and then click Duplicate & Edit. Alert me when a server goes down Use the following procedure to create an alert that writes to a log and sends an email when a Windows server goes down. it immediately monitors your environment for the conditions necessary to trigger it. Enter a name for the alert.  6.45 to restrict the scope of the alert to a specific subnet.  4. Modify any section by clicking Edit next to that section.  3. Select Node Machine Type is equal to Windows 2008 Server as the child condition. Enable the alert. 405 . Before you click Submit. Select the check box next to the alert. For example.

 You can also use a variable that allows you to acknowledge an alert from email (${N=Alerting.M=AcknowledgeUrl}). Upon triggering. and then click Add Action. 406 . the alert will write to a local log file. Click Add Action. You can test and view the results of each of your alert actions.  14.  a.  16. Enter your SMTP server information if you have not already done so.  a. and modify your message to Node ${N=SwisEntity. Select and enter a value for Condition must exist for more than to prevent being alerted when a node enters the down state frequently within a set amount of time. Click Configure Action. This prevents you from receiving alerts until the node has been in the down state for longer than the time you have selected.  11. You can enter a default SMTP server that is used for all your email in the Configure Default Send Email Action setting. and modify your message.  c.  c. Click Add Action in Escalation Level 2. You can also delete the email if you do not want to know if the situation has been resolved. Go to Execution settings to click Add Action. send a syslog message. This allows you to choose to wait until multiple nodes are down before triggering a single alert.  12. Click Edit next to your email action. and select Send an Email/Page. and then click Configure Action.  d.txt in the Alert Log Filename Field.  b.M=Caption} is back up. Add a message.  15. Enter the location of the log. Click Edit next to your logging action.  9. and send an SNMP trap. The default action should be to reset the alert when the node is up. The actual trigger condition should be Node Status is equal to Down. Click Summary to see if any object will trigger the alert. Once you have created the alert. In the Message text box. enter C:\ExampleAlertLog. Click Copy Actions to Reset Actions Tab. Click Reset Condition. You can further suppress alerts by enabling complex conditions in the Advanced options.  b.M=Caption} is currently down.  8.  7. it is added to the list of available alerts in the Alert Manager. Enter your email as the recipient. Click Add Escalation Level. and then click Submit. type Node ${N=SwisEntity. For example.  10. Select Log the Alert to a file. See Testing Alerts for more information. and then click Next. and enter 5 minutes to wait for 5 minutes before escalating to the next level. Alert on custom properties The following example creates multiple alerts using the NodeLocation custom property. You can use variables to customize your message. Click Trigger Actions. An alert triggers when a node goes down.  13.

Click Trigger Condition. it is added to the list of available alerts in the Alert Manager. Click Summary to see if any objects will trigger the alert.0. Click Add Action. You can also add the All Active Alerts resource to any view.  b. A child condition should already exist for a node being down. Click Add Action.1 as the SNMP Trap Destination. and then click Manage Alerts. In the Message text box.0. Click Alerts & Activity > Alerts in the menu bar. View triggered alerts in the Orion Web Console View active triggered alerts through Alerts & Activity > Alerts in the menu bar. and then click Configure Action.0. Click Add Action. 407 .  n You can view results of your Syslog message action in the Web Console or through the Syslog Viewer on your Orion server. Select the node object.  a.  b. and click Submit.  8. which includes a historic count of how frequently the object triggers the alert and other objects that are experiencing the same set of conditions that triggered the alert you are viewing. and select Send SNMP Trap. Click each alert to view the details. Click Next. and then type the following in the Message field: Node ${N=SwisEntity.  2. click Start > All Programs > SolarWinds Orion > Syslog and SNMP Traps > Trap Viewer.M=Caption} is currently down.  n To view the results of your SNMP Trap action. Select the check box next to Node is down.0.  9. Type 127.M=Caption} is currently down. The ${variable} syntax is required for variables.  c.  7. Type 127. Select Log the Alert to a file. and then click Add Action.  4.  1.  5.  a. Click the Trigger Actions.1 as the Hostname or IP Address of the Syslog Server. Click Add Action.M=Caption} is currently down.  c. Click Add Action. Enter the log filename in the Alert Log Filename field. and then click the Duplicate & Edit button. After you have created the alert. Click Configure Action. type the following: Node ${N=SwisEntity. and choose NodeLocation in the field drop-down menu. Enter a comparison and value. and add a child condition. and then type the following in the Alert Message field: Node ${N=SwisEntity. and select Send a Syslog Message.  6.  3.  a.  b. Click Configure Action. You can test and view the results of each of your alert actions.

You must enable the Allow Account to Clear Events privilege to acknowledge alerts.  2. The trigger condition is automatically evaluated and trigger and reset actions can be tested individually.  1. and text to speech actions without sending an email by clicking Simulate. Test email. Click Acknowledge next to the alerts you want to acknowledge. 408 . you should reduce the recipient list to yourself and a small number of team members until you are confident the alert is ready to be enabled in your production environment. and Text to Speech Output actions do not have to fire. For more information about access privileges for Orion Web Console users. The Send Email/Page. the action will be performed regardless of whether the trigger condition is true. Scroll to the bottom of the page and view the information box above the Submit button. Click Trigger Actions or Reset Actions. Test alert triggers and actions You do not have to actually experience a device failure to confirm that your alerts are working.  4. see User Account Access Settings.Remove alerts from the Active Alerts list When an alert has triggered and becomes active. You can view what the message will look like when the trigger or reset action fires without performing the action. After an alert is acknowledged. If the action sends a message to a recipient. Click Simulate next to the alert action you want to test. The most common purposes are to provide an audit trail or to prevent multiple people from working on the same issue.  3. Test trigger conditions Alert conditions are automatically evaluated on the Summary tab. and then selecting Hide Acknowledged Alerts. you can then acknowledge it. Select an object to resolve any variables you have used in your alert action. acknowledging an alert can have different purposes outside of halting further notifications. Play a Sound. Depending on your organization. Click Execute. you can acknowledge an alert directly from an email notification. Test alert actions while creating or editing an alert When you simulate actions. Tip: Depending on how you configure the email.  2. Click Alerts & Activity > Alerts in the menu bar. alert actions in higher escalation levels are halted and the time it was acknowledged and the account that acknowledged it is recorded. You can also add notes that other users can read. You can hide acknowledged alerts by clicking More. play a sound.  1.

Test alert actions in the Action Manager You can also test actions independent of the trigger or reset conditions by using the Action Manager. typically <Volume:>\ProgramData\Solarwinds \Logs\Orion\ActionsExecution. even if it is scheduled to run. You can send this file to other coworkers or share it in the SolarWinds THWACK community. Alerts must be enabled to be executed.com to download and import alerts created by others. Export an alert to save the alert definition as an XML file on your local computer. Modify multiple alerts or share alerts Use the Alert Manager to bulk edit multiple alerts.solarwinds. For example. After the alert test completes. a trigger action to send an email is usually a notification that an event happened. Test email actions without sending an email by clicking Simulate. Click Execute.log. click Start > All Programs > SolarWinds Orion > Syslog and SNMP Traps > Syslog Viewer. Alerts are exported to XML and can only be imported from XML. Visit THWACK. You can enable or disable multiple alerts or add pre- configured actions. For example. You can assign multiple actions to multiple alerts. while the associated reset action is usually a notification that the event has been resolved.  l To view results of your Syslog message action.  4. Click Test. Select the action you want to test. you can view the results of your alert actions. Share alerts with others SolarWinds customers share their customized alerts in the SolarWinds THWACK community. Add actions to alerts without opening the Alert Wizard Assign actions that you have already configured to alerts. A disabled alert will not be executed.  2. click Start > All Programs > SolarWinds Orion > Syslog and SNMP Traps > Trap Viewer.  l To view the results of your Syslog message action.  l To view the results of your email alert action. if an alert is scheduled to run for a short period of time each year.  1. Actions are categorized into trigger and reset actions based on how the action was created in the Alert Wizard. SolarWinds does not provide generic actions due to the differences in intent behind trigger and reset actions. open EvaluationAlertLog in your Orion folder. Select an object to resolve any variables you have used in your alert action. 409 .  3. it must be enabled so the schedule runs.

Expand Advanced options. select Alert can be triggered if.  3.  2. Before you share an alert. Do not use complex conditions until you have tested the trigger conditions individually. Also review your company policy on sharing this type of file. such as SMTP server credentials.  1. In the trigger condition. Select Enable complex conditions. Do not use this setting until you are confident that the trigger condition is correct. Creating an alert with complex conditions without testing it may prevent you from receiving important alerts.  3. if you were monitoring computers used in a high availability cluster. and delete before making it public. you can choose to trigger alerts only when multiple objects meet the trigger condition. Navigate to the Trigger Condition page. Enter how many objects must meet the trigger condition before sending an alert. You can use complex conditions to do the following:  n Wait for multiple objects to meet the trigger condition before alerting  n Evaluate multiple condition blocks  n Evaluate multiple object types Wait for multiple objects to meet the trigger condition With complex conditions enabled. This setting can prevent important alerts from triggering. the following option is available in your trigger condition: This setting combines all alerts that would be sent for each object into a single alert. After you have enabled complex conditions.  1. Enable complex conditions.  2. or who have trialed alerts using the normal trigger conditions and require more control over the trigger conditions to better refine the environmental conditions that trigger an alert. check the exported file for confidential information. For example. 410 . Build complex conditions Complex conditions are generally enabled by users who are comfortable with building normal trigger conditions. you may only want to be alerted if more than half the cluster is down at the same time.

Manage alert actions You can edit. Enable complex conditions. Choose a different value in I want to alert on. View meta data about the action to help troubleshoot alert actions from a single area instead of trying to find the action in an alert. If they are all true based on the conditions. or sections. For example.  3. if you want to be alerted if the backup system is active for more than an hour. Enable complex conditions. Mostly for bulk actions and assigning previously created actions to alerts. For example.  1. For example. Click Add Section. test. and C must be true in order for the alert to trigger. Evaluate multiple object types To evaluate multiple object types. Choose how long to wait before evaluating the next section. you should use complex conditions. A condition block can be evaluated at a different time than other condition blocks. (Condition A) & (Condition B) & (Condition C) Condition blocks are evaluated using variations of AND. 411 . Click Add Section. the alert triggers. you may want to create an alert when an application is down and when your fail-over server is active for more than an hour. Complex conditions can be used to alert on different object types within the same alert. How condition blocks are evaluated The condition blocks are evaluated at the same time. independently. disable. and delete alert actions from the Action Manager. so the trigger condition in each section must be met. before evaluating whether the backup system is still active.  4.  2.  5. Select And then after from the drop-down menu between the two condition sections. where the application going down is the trigger condition.Evaluate multiple condition blocks You can use complex conditions to evaluate multiple condition blocks.  2. you can create an alert to notify you when IIS is down and the free space on the volume is less than 30 GB. condition A. you can choose to wait an hour after the primary condition block.  1. enable. Create the next condition block. For example.  3. B.

Assign an action to an alert
You can use actions that you have already configured in multiple alerts.  For example, if you have
configured an action to email emergency response teams, you can assign this action to multiple alerts.
When you assign an alert, it is added to the highest escalation level.

Enable and Disable Alerts
Use the On/Off toggle or select an alert and click Enable/Disable to enable or disable alerts.

Alerts must be enabled to be evaluated. For example, if an alert is scheduled to run for a short period of
time each year, it must be enabled so the schedule runs. A disabled alert will not be evaluated, even if it is
scheduled to run.

Available alert actions
Orion Platform products provide a variety of actions to signal an alert condition on your network.

Change a custom property
Custom properties are additional fields, such as country, building, asset tag, or serial number, that you can
define and store in your SolarWinds Orion database. After properties are added, you can view or filter
using them.
 1. When editing or adding an alert, click Add Action in the Trigger or Reset Action section of the Alert
Wizard.
 2. Select the Change Custom Property option, and then click Configure Action.
 3. Under Custom Property Settings, select the custom property and enter the value you want to change
it to.
 4. Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action. This
schedule only applies to the alert action you are editing.

This is often used to prevent an action from occurring during specific windows.

 5. Select how frequently this action occurs for each triggered alert in Execution Settings.
 6. Click Add Action.

The action is added to the trigger or reset action list, and you can test the action using the Simulate
button. When the trigger or reset conditions of the alert are met, the value of the custom property you
selected changes.

Create a ServiceNow incident
This alert management action is only available if the integration with ServiceNow® is enabled.

412

For information about configuring ServiceNow integration, see Configure an Orion Platform product with
ServiceNow.

To use this action, make sure the integration with ServiceNow is enabled on the Alert Summary
page. If the Integrate alert with other SolarWinds box is not selected, the incident is created but the
integration is not two-sided, so you cannot reset or clear the incidents in ServiceNow®.

Use reference fields

When you configure ServiceNow incidents, you can use reference fields to refer to different database
tables in ServiceNow.

The reference value you provide in the Orion Web Console is used in ServiceNow to locate a referenced
record. This enables you to use advanced ServiceNow filter expressions.

The reference field's value is usually the Sys ID of the referenced record, and the application by default
tries to locate the referenced record by Sys ID.

You can also specify which fields should be used for specific referenced tables when trying to locate a
referenced record. Some definitions are defined by default. For example, setting a field user_name for the
sys_user table allows you to use the user name in reference fields such as Caller or Assigned to.

You can specify your own reference fields in the SolarWinds Alert Integration application, under
Configuration > Incident Reference Fields Definitions, and you can control the order of different fields on
the same table by setting different priorities.

Filter expression examples

Reference fields can also be used as filter expressions. The following examples show the configuration of
reference fields.

REFERENCE
VALUE PURPOSE
FIELD

Assignment name=Hardware Assigns the incident to the group called
group Hardware.

Location state=TX^city=Austin^streetLIKESouthwest Sets the location to Southwest Parkway,
Parkway Austin, TX.

Configuration mac_address=${N=SwisEntity;M=MAC} Locates the configuration item based on the
item MAC address of the interface, by using a
macro.

For more information, see the ServiceNow Wiki about reference fields.

Configure a ServiceNow incident
 1. When editing or adding an alert, click Add Action in the Trigger or Reset Action section of the Alert
Wizard.
 2. Select Create ServiceNow Incident, and click Configure Action.

413

 3. Under Select ServiceNow Instance, specify the ServiceNow instance where you want to create the
incident.
 4. Under Incident Detail, define the properties of an incident template that will be used for new
incidents. For example, here you can define the urgency, impact, and other properties of incidents.
Text areas can hold macro variables to add information about alerts and alert objects.

If the property you want is not displayed in the Incident Detail section, click Select Properties
at the bottom of the section, and select the property from the list. Then you will be able to use
the properties as reference fields.

 5. Under State Management, define the status of the incident when the incident is reset, reopened,
acknowledged, and closed. You can also specify notes to be added to the incident.
 6. Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action. This
schedule only applies to the alert action you are editing.

This is often used to prevent an action from occurring during specific windows.

 7. Select how frequently this action occurs for each triggered alert in Execution Settings.
 8. Click Add Action.

The action is added to the trigger or reset action list, and you can test the action using the Simulate
button. When the trigger or reset conditions of the alert are met, an incident will be created or updated in
the specified ServiceNow instance.

When you use this alert action, we recommend that you only use it on the trigger tab. It is also
recommended that you only use one ServiceNow action per alert.

To deactivate the integrated behavior, remove the alert action from the alert definition.

You can specify one alert action for one ServiceNow instance. To create an incident in another
ServiceNow instance, specify another alert action and use a different ServiceNow instance.

Dial a paging or SMS service
This action forwards alerts to a paging or SMS service. You must download and install NotePager Pro from
Notepage.net to your Orion server to use this action.

For instructions on configuring this action, see the NotePage Technical Support page at
http://www.notepage.net/solar-winds/technicalsupport.htm and SolarWinds Network Performance
Monitor Integration at www.notepage.net.

Email a web page to users
Send a web page, including content of resources available in the Orion Web Console, to others.

 1. When editing or adding an alert, click Add Action in the Trigger or Reset Action section of the Alert
Wizard.
 2. Select the Email a Web Page option, then click Configure Action.

414

 3. Enter the Recipients.

Multiple addresses must be separated with commas.

 4. Enter the Subject and Message of your alert trigger email/page.
 n For the Optional Web Server Authentication section, select User currently logged in, Another
user, or No user defined.
Use variables to make the message dynamic.

 n You can create a dynamic URL to send information about the object that triggered the alert.
 5. Enter your SMTP server information.
 6. Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action. This
schedule only applies to the alert action you are editing.

This is often used to prevent an action from occurring during specific windows.

 7. Select how frequently this action occurs for each triggered alert in Execution Settings.
 8. Click Add Action.

The action is added to the trigger or reset action list, and you can test the action using the Simulate
button. When the trigger or reset conditions of the alert are met, an email is sent to the recipients.

Create a dynamic URL

Use variables to create a URL that changes based on the object that triggers the alert. Click Insert Variable
and search for URL to find the all of the variables you can use to create the dynamic URL.

For example, enter ${N=SwisEntity;M=DetailsUrl} in the URL field to email a link to the Details view of the
object that triggered the alert. When the email is sent, the variable resolves to a valid URL such as
http://myserver/Orion/View.aspx?NetObject=N:3 and the email contains the content of the
Details view in the body.

Execute an external batch file
There are several circumstances where you may want to execute a program when a specific network event
occurs. For example, you may want to run a custom script to reboot your SQL servers.

External programs selected for this action must be executable using a batch file called from the command
line. Programs executed this way run in the background. However, you can set the SolarWinds Alerting
Engine Service to Interact with Desktop.

SolarWinds recommends that scripts and batch files be placed on the root of c:\ to simplify the path
for the batch file.

 1. When editing or adding an alert, click Add Action in the Trigger or Reset Action section of the Alert
Wizard.
 2. Select the Execute an External Program option, then click Configure Action.

415

 3. 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 your main poller and test.bat
is your external program to be executed.
 b. Select either Define User or No User Defined for Optional Windows Authentication
 4. Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action. This
schedule only applies to the alert action you are editing.

This is often used to prevent an action from occurring during specific windows.

 5. Select how frequently this action occurs for each triggered alert in Execution Settings.
 6. Click Add Action.

The action is added to the trigger or reset action list, and you can test the action using the Simulate
button. When the trigger or reset conditions of the alert are met, the external program runs.

Execute an external Visual Basic script
In some situations, you may want to execute a Visual Basic (VB) script when a network event occurs to
perform a specific action.

SolarWinds recommends that scripts and batch files be placed on the root of c:\ to simplify the path
for the batch file.

 1. When editing or adding an alert, click Add Action in the Trigger or Reset Action section of the Alert
Wizard.
 2. Select the Execute an External VB Script option, then click Configure Action.
 3. 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 your main Orion poller and
test.vbs is your external VB Script to be executed.
 c. Select either Define User or No User Defined for Optional Windows Authentication
 4. Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action. This
schedule only applies to the alert action you are editing.

This is often used to prevent an action from occurring during specific windows.

 5. Select how frequently this action occurs for each triggered alert in Execution Settings.
 6. Click Add Action.

The action is added to the trigger or reset action list, and you can test the action using the Simulate
button. When the trigger or reset conditions of the alert are met, the VB script runs.

416

Log the alert message to a file
SolarWinds can be configured to log alerts to a designated file which can be viewed at a later time.

 1. When editing or adding an alert, click Add Action in the Trigger or Reset Action section of the Alert
Wizard.
 2. Select the Log the Alert to a File option, then click Configure Action.
 3. Under Log to File Settings:
 a. Enter the log filename in the Alert Log Filename field.
 b. Enter a maximum log file size in MB (0 = unlimited).
 c. Enter the Message of your alert trigger in the field provided. 
 4. Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action. This
schedule only applies to the alert action you are editing.

This is often used to prevent an action from occurring during specific windows.

 5. Select how frequently this action occurs for each triggered alert in Execution Settings.
 6. Click Add Action.

The action is added to the trigger or reset action list, and you can test the action using the Simulate
button. When the trigger or reset conditions of the alert are met, the alert is logged to the file with the
message you created.

Log the alert to the NPM event log
Record when an alert is triggered to the NetPerfMon (NPM) event log on your Orion server or on a remote
server for later investigation.

 1. When editing or adding an alert, click Add Action in the Trigger or Reset Action section of the Alert
Wizard.
 2. Select Log the Alert to the NetPerfMon Event Log from the options, and then click Configure Action
 3. Under Log the Alert to the NetPerfMon Event Log settings, enter the text you want written to the file.

Use variables to make the message dynamic.

 4. Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action. This
schedule only applies to the alert action you are editing.
This is often used to prevent an action from occurring during specific windows.
 5. Expand Execution Settings to select when the action occurs.
 6. Click Add Action.

The action is added to the trigger or reset action list, and you can test the action using the Simulate
button. When the trigger or reset conditions of the alert are met, the alert is logged to the NPM event log
with the message you created.

417

Change the resource allocation of a virtual machine
If a virtual machine is experiencing performance issues, you can have an alert trigger a specified allocation
of resources. This alert management action is available if the integration with Virtualization Manager is
enabled.
 1. When editing or adding an alert, click Add Action in the Trigger or Reset Action section of the Alert
Wizard.
 2. Select Manage VM - Change CPU/Memory Resources, and click Configure Action.
 3. Enter a name for the action.
 4. Under Select Virtual Machine, specify the virtual machine on which you want to adjust the number of
CPUs, the memory capacity, or both.
 a. To change the resource allocation of the virtual machine that triggered the alert, click Execute
this action.
This option is only available if the alert is built to trigger for virtual machines.

 b. To change the resource allocation of a different virtual machine, click Select specific VM, and
search for a virtual machine.
 5. To power off the virtual machine before changing the resource allocation, and then power it on again
after the resource allocation has been changed, select the relevant option.

If the option is not selected, the action will be performed live on the virtual machine.

 6. Under Specify New Resources, specify whether you want to add more resources to the virtual
machine, or replace the existing resources with new resources, and then specify the parameters of
the new resource or resources.
 a. Select Number of processors, and specify the number of processors to allocate.
 b. Select Memory, and specify the memory capacity to allocate.
 7. Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action. This
schedule only applies to the alert action you are editing.

This is often used to prevent an action from occurring during specific windows.

 8. Select how frequently this action occurs for each triggered alert in Execution Settings.
 9. Click Add Action.

The action is added to the trigger or reset action list, and you can test the action using the Simulate
button. When the trigger or reset conditions of the alert are met, the specified CPU and memory resources
will be allocated to the virtual machine.

Delete a snapshot of a virtual machine
If a virtual machine is experiencing resource issues, you can have an alert trigger a virtual machine
snapshot to be deleted. This alert management action is only available if the integration with Virtualization
Manager is enabled.
 1. When editing or adding an alert, click Add Action in the Trigger or Reset Action section of the Alert
Wizard.
 2. Select Manage VM - Delete Snapshot, and click Configure Action.

418

 3. Under Select Virtual Machine, 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.
This option is only available if the alert is built to trigger for virtual machines.

 b. To delete a snapshot of a different virtual machine, click Select specific VM, and search for a
virtual machine.
 4. Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action. This
schedule only applies to the alert action you are editing.

This is often used to prevent an action from occurring during specific windows.

 5. Select how frequently this action occurs for each triggered alert in Execution Settings.
 6. Click Add Action.

The action is added to the trigger or reset action list, and you can test the action using the Simulate
button. When the trigger or reset conditions of the alert are met, the snapshot of the specified virtual
machine will be deleted.

Move a virtual machine to a different host
If a virtual machine is experiencing issues, you can have an alert trigger the virtual machine to be moved
to a different host. This alert management action is only available if the integration with Virtualization
Manager is enabled.
 1. When editing or adding an alert, click Add Action in the Trigger or Reset Action section of the Alert
Wizard.
 2. Select Manage VM - Move to a Different Host, and click Configure Action.
 3. Under Select Virtual Machine, specify the virtual machine that you want to move.
 a. To move the virtual machine that triggered the alert, click Execute this action.
This option is only available if the alert is built to trigger for virtual machines.

 n To apply the action only to virtual machines of a specific vendor, select the relevant
option, and specify whether you want to perform to action on Hyper-V or VMware
virtual machines.
 b. To move a different virtual machine, click Select specific VM, and search for a virtual machine.
 4. To power off the virtual machine before moving it to a different host, and then power it on again
after the action has been completed, select the relevant option.

If the option is not selected, the action will be performed live on the virtual machine.

 5. Under Select Target Host, search for the host where you want to move the selected virtual machine.
 6. Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action. This
schedule only applies to the alert action you are editing.
This is often used to prevent an action from occurring during specific windows.
 7. Select how frequently this action occurs for each triggered alert in Execution Settings.
 8. Click Add Action.

419

The action is added to the trigger or reset action list, and you can test the action using the Simulate
button. When the trigger or reset conditions of the alert are met, the specified virtual machine will be
moved to a different host.

Move a virtual machine to a different storage
If a virtual machine is experiencing storage issues, you can have an alert trigger the moving of the virtual
machine to a different storage location. This alert management action is only available if the integration
with Virtualization Manager is enabled.
 1. When editing or adding an alert, click Add Action in the Trigger or Reset Action section of the Alert
Wizard.
 2. Select Manage VM - Move to a Different Storage, and click Configure Action.
 3. Under Select Virtual Machine, specify the virtual machine that you want to move.
 a. To move the virtual machine that triggered the alert, click Execute this action.
This option is only available if the alert is built to trigger for virtual machines.

 n To apply the action only to virtual machines of a specific vendor, select the relevant
option, and specify whether you want to perform to action on Hyper-V or VMware
virtual machines.
 b. To move a different virtual machine, click Select specific VM, and search for a virtual machine.
 4. 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, select the relevant option.

If the option is not selected, the action will be performed live on the virtual machine.

 5. Under Select Target Datastore, search for the datastore where you want to 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 click either Use the
default location to move the virtual machine to the default location of the datastore, or click
Specify custom path, and enter a custom location.
 6. Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action. This
schedule only applies to the alert action you are editing.

This is often used to prevent an action from occurring during specific windows.

 7. Select how frequently this action occurs for each triggered alert in Execution Settings.
 8. Click Add Action.

The action is added to the trigger or reset action list, and you can test the action using the Simulate
button. When the trigger or reset conditions of the alert are met, the specified virtual machine will be
moved to a different datastore.

Pause a virtual machine
If a virtual machine is experiencing issues, you can have an alert trigger a pause for the virtual machine.
This alert management action is only available if the integration with Virtualization Manager is enabled.

420

click Select specific VM. click Add Action in the Trigger or Reset Action section of the Alert Wizard.  3. Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action.  2. click Add Action in the Trigger or Reset Action section of the Alert Wizard. Select Manage VM .  5.  a. This option is only available if the alert is built to trigger for virtual machines. To pause the virtual machine that triggered the alert.  4. Under Select Virtual Machine. specify the virtual machine that you want to power off.Pause. and you can test the action using the Simulate button. Select how frequently this action occurs for each triggered alert in Execution Settings. To pause a different virtual machine.  1. This alert management action is only available if the integration with Virtualization Manager is enabled. Under Select Virtual Machine. When editing or adding an alert. and you can test the action using the Simulate button. When the trigger or reset conditions of the alert are met. Select how frequently this action occurs for each triggered alert in Execution Settings. To power off the virtual machine that triggered the alert. and search for a virtual machine.  3. and click Configure Action. Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action.  2. This is often used to prevent an action from occurring during specific windows. This schedule only applies to the alert action you are editing. To power off a different virtual machine. click Execute this action. This is often used to prevent an action from occurring during specific windows. 421 . Click Add Action. the specified virtual machine will be paused. Select Manage VM .  6.Power Off. click Select specific VM. This schedule only applies to the alert action you are editing. Power off a virtual machine If a virtual machine is experiencing issues.  5.This action can only be configured for Hyper-V virtual machines.  b. The action is added to the trigger or reset action list. The action is added to the trigger or reset action list. When editing or adding an alert.  4. This option is only available if the alert is built to trigger for virtual machines. and click Configure Action. the specified virtual machine will be powered off.  6. click Execute this action. specify the virtual machine that you want to pause. Click Add Action.  a. and search for a virtual machine.  1. you can have an alert trigger the virtual machine to be powered off.  b. When the trigger or reset conditions of the alert are met.

click Add Action in the Trigger or Reset Action section of the Alert Wizard. specify the virtual machine that you want to reboot.  3. This schedule only applies to the alert action you are editing. Under Select Virtual Machine. Select how frequently this action occurs for each triggered alert in Execution Settings. This option is only available if the alert is built to trigger for virtual machines. This is often used to prevent an action from occurring during specific windows. and search for a virtual machine. This alert management action is only available if the integration with Virtualization Manager is enabled. When the trigger or reset conditions of the alert are met. When editing or adding an alert. you can have an alert trigger the virtual machine to be restarted. Under Select Virtual Machine. specify the virtual machine that you want to power on. When editing or adding an alert. Select how frequently this action occurs for each triggered alert in Execution Settings.  a. Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action. click Select specific VM.Reboot.  4.  a.Power on a virtual machine If a virtual machine is powered off. This alert management action is only available if the integration with Virtualization Manager is enabled. click Add Action in the Trigger or Reset Action section of the Alert Wizard.  5. the specified virtual machine will be powered on.  6. and click Configure Action.  5. To power on a different virtual machine. The action is added to the trigger or reset action list. This schedule only applies to the alert action you are editing.  3. click Execute this action.  1.  b.  4.  b. To reboot a different virtual machine. To power on the virtual machine that triggered the alert. and click Configure Action. Select Manage VM . Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action. and you can test the action using the Simulate button. To reboot the virtual machine that triggered the alert.  6. Restart a virtual machine If a virtual machine is experiencing issues.  1. This option is only available if the alert is built to trigger for virtual machines.Power On. and search for a virtual machine.  2. click Select specific VM. 422 .  2. click Execute this action. Click Add Action. Select Manage VM . This is often used to prevent an action from occurring during specific windows. you can have an alert trigger the virtual machine to be powered on. Click Add Action.

423 . you can have an alert trigger the virtual machine to be suspended. click Add Action in the Trigger or Reset Action section of the Alert Wizard. Select Manage VM .  5.  2. When editing or adding an alert. Click Add Action. click Add Action in the Trigger or Reset Action section of the Alert Wizard. Select how frequently this action occurs for each triggered alert in Execution Settings. To take a snapshot a different virtual machine. Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action. and click Configure Action. This option is only available if the alert is built to trigger for virtual machines. the specified virtual machine is suspended.  1. Select Manage VM . When editing or adding an alert.  b. This is often used to prevent an action from occurring during specific windows.  a. specify the virtual machine of which you want to take a snapshot. This alert management action is only available if the integration with Virtualization Manager is enabled. This alert management action is only available if the integration with Virtualization Manager is enabled. click Select specific VM. and you can test the action using the Simulate button.  2. Take a snapshot of a virtual machine If a virtual machine is experiencing issues. the specified virtual machine restarts.Suspend. and search for a virtual machine. When the trigger or reset conditions of the alert are met. To suspend the virtual machine that triggered the alert. This option is only available if the alert is built to trigger for virtual machines.  3. The action is added to the trigger or reset action list. To take a snapshot of the virtual machine that triggered the alert.Take Snapshot. Suspend a virtual machine If a virtual machine is experiencing performance issues. Under Select Virtual Machine.  b. click Execute this action. click Select specific VM. and click Configure Action. and search for a virtual machine.The action is added to the trigger or reset action list. specify the virtual machine that you want to suspend. To suspend a different virtual machine. Under Select Virtual Machine. When the trigger or reset conditions of the alert are met.  6.  1.  3. and you can test the action using the Simulate button. This schedule only applies to the alert action you are editing. you can have an alert trigger a snapshot of the virtual machine to be taken. click Execute this action.  4.  a.

configure which sound you want to play when an alert is received. This schedule only applies to the alert action you are editing. Run the installer and follow the on-screen instructions to install the client.  6. When editing or adding an alert. Computers that do not have the desktop notification client installed on them do not play a sound when an alert arrives. After installing the desktop notification client.  1.  2.  4. When the trigger or reset conditions of the alert are met. Play a sound when an alert is triggered The Play a Sound action uses the SolarWinds desktop notification client to play the sound on your computer when an alert arrives. a snapshot is taken of the specified virtual machine. The action is added to the trigger or reset action list. click Add Action in the Trigger or Reset Action section of the Alert Wizard. 424 . and you can test the action using the Simulate button. This alert action is frequently used in NOC environments. and then click Configure Action. Select the Play a Sound option.msi. Click Add Action. you must install and configure the desktop notification client on that computer. Select how frequently this action occurs for each triggered alert in Execution Settings.DesktopNotificationTool. This is often used to prevent an action from occurring during specific windows. The desktop notification client requires the following information to connect to your Orion server and receive alerts:  n Orion Server Name or IP Address  n Orion User Name  n Password You can use the server name and credentials that you use to logon to your SolarWinds product. SolarWinds can be configured to play a sound upon alert trigger or reset. The following procedure configures a sound to play for an alert. Download the desktop notification client from <Your SolarWinds Orion server>/DesktopNotificationTool/SolarWinds.  5. You must download and install the client on every computer that you want to play a sound when an alert arrives. If you want an alert notification sound to play on your desktop or laptop. Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action. The SolarWinds Desktop Notification client must be installed on each computer that you want to play a sound.

   4. When the trigger or reset conditions of the alert are met. and you can test the action using the Simulate button.  5.  6. The action is added to the trigger or reset action list. Enter the Message of your alert trigger in the field provided. Select how frequently this action occurs for each triggered alert in Execution Settings.  1. Enter Computer Name or IP address in the field provided. Select how frequently this action occurs for each triggered alert in Execution Settings. click Download our desktop notification client to download and install the notification client. This schedule only applies to the alert action you are editing. you can have an alert trigger a Windows Net Message to be sent to a specific computer or to all computers. When editing or adding an alert. 425 . This schedule only applies to the alert action you are editing. the message is sent to the selected computers. click Add Action in the Trigger or Reset Action section of the Alert Wizard.  5. and you can test the action using the Simulate button. The only operating systems supporting Windows Net Messaging are Windows Server 2003 and Windows XP or earlier. Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action. a sound plays through the client.  3. Click Add Action.  4. The action is added to the trigger or reset action list. This is often used to prevent an action from occurring during specific windows. select an alert sound. This is often used to prevent an action from occurring during specific windows. Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action. Under Play a sound settings:  n If not installed. Under Send a Net Message settings:  a.  b.  3.  2. From the notification client. The following steps configure Windows Net messaging for triggered or reset alerts. Select the Send Net Message option. Alerts can be configured to display a pop-up Windows Net Message either on a specific computer or on all computers in a selected domain or workgroup. then click Configure Action. You can enter multiple computers or IP addresses by separating them with commas. When the trigger or reset conditions of the alert are met. Send a Windows Net message If a computer is experiencing issues.  6. Click Add Action.

Restart IIS sites or application pools If IIS or application pools are experiencing performance or resource issues.  5.  2. then click Configure Action. Multiple IP Addresses should be separated by commas or semicolons.  a. Expand Restart IIS Site/Application Pool Settings.  b. This schedule only applies to the alert action you are editing.  4. When the trigger or reset conditions of the alert are met.  3. When editing or adding an alert. and you can test the action using the Simulate button. Click Add Action. Select the Send SNMP Trap option. Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action.  2. you can use an alert to restart them. You can have an alert trigger this action to inform you of these events. This is often used to prevent an action from occurring during specific windows. Optionally click Insert Variable to add variables using the following procedure: 426 . This action requires the following information:  n UDP port number  n SNMP version number  n SNMP credentials  1. Select Restart IIS Site/Application Pool from the options. click Add Action in the Trigger or Reset Action section of the Alert Wizard. You must know the IIS Server name and the Site or Application Pool to restart a remote instance of IIS. Send an SNMP trap SNMP traps signal the occurrence of significant events by sending SNMP messages to a monitoring device.  4. Enter the Message of your alert trigger in the field provided.  1. click Add Action in the Trigger or Reset Action section of the Alert Wizard. Enter SNMP Trap Destinations in the field provided. Choose the Site or Application Pool. Select how frequently this action occurs for each triggered alert in Execution Settings. and then click Configure Action. Select the IIS Action to Perform from the drop down list.  b. The action is added to the trigger or reset action list. When editing or adding an alert.  a.  3.  6. the selected site or pool restarts. Select a Trap Template from the drop down lists. Under Send SNMP Trap Message:  a.

This is often used to prevent an action from occurring during specific windows. Enter a UDP Port number in the field provided. then click Configure Action.  6. Select how frequently this action occurs for each triggered alert in Execution Settings. Select the Send a SysLog Message option. Click Add Action. Send a syslog message SolarWinds can log received alerts to the syslog of a designated machine for later investigation. click Add Action in the Trigger or Reset Action section of the Alert Wizard. Select either Use HTTP GET or Use HTTP POST. The following procedure configures an alert to send a message to a designated syslog server.  4. Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action.  b.  2. by correctly formatting the GET function.  2. Under HTTP request settings:  a. This is often used to prevent an action from occurring during specific windows. Select an SNMP Version from the drop down list.  7. Enter a URL in the field provided. When the trigger or reset conditions of the alert are met. Send a GET or POST request SolarWinds can be configured to communicate alerts using HTTP GET or POST functions. then click Configure Action. When editing or adding an alert. the GET or POST request is sent to the server. and. You can view the server logs to confirm that the action occurred. This schedule only applies to the alert action you are editing. The action is added to the trigger or reset action list. Select how frequently this action occurs for each triggered alert in Execution Settings. As an example. click Add Action in the Trigger or Reset Action section of the Alert Wizard. and you can test the action using the Simulate button. When editing or adding an alert.  b. The action is added to the trigger or reset action list.  5. 427 . Select the Send a GET or POST Request to a Web Server option.  5. Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action. and you can test the action using the Simulate button. Click Add Action.  1. new trouble tickets may be created automatically.  c. This schedule only applies to the alert action you are editing. a URL may be used as an interface into a trouble ticket system. the SNMP trap message is sent. When the trigger or reset conditions of the alert are met.  3.  6. Expand SNMP Properties.  a.  1. Enter the SNMP Community String in the field provided.  8.

Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action. if necessary  n Default sender email address Configure the SMTP server in the alert action or from the Settings page. and you can test the action using the Simulate button. Under Send a SysLog message settings:  a. Select how frequently this action occurs for each triggered alert in Execution Settings.  2. Enter the Hostname or IP Address of the syslog server in the field provided. This schedule only applies to the alert action you are editing. click Add Action in the Trigger or Reset Action section of the Alert Wizard.  4. Multiple syslog servers should be separated by commas. Enter the Message of your alert trigger in the field provided. The action is added to the trigger or reset action list. Before configuring this alert you must first configure the default SMTP server the product uses to send email.  6. You can change the default SMTP server later or use different SMTP servers for specific alerts. Select the Send an Email/Page option. Send an email or page This action sends an email from the product to selected recipients for investigation into the cause of the alert. When the trigger or reset conditions of the alert are met.  3. 428 .  1. the syslog message is sent. You need the following information:  n The SMTP host name or IP address  n The SMTP port number  n Whether the SMTP server uses SSL  n The SMTP credentials.   5. When editing or adding an alert.  7. then click Configure Action. Select a Severity and a Facility from the drop down lists.  b. Click Add Action. This is often used to prevent an action from occurring during specific windows.

 1. Change the status to use the polled status from the node details page or create a reset action to set the status to use the polled status. Select Use polled status if you are creating a reset action. Select how frequently this action occurs for each triggered alert in Execution Settings. Select Change to a specific status if you are creating a trigger action. but the server is down or unresponsive. if the custom status is set to Up.  3. This is often used to prevent an action from occurring during specific windows.  b. The action is added to the trigger or reset action list. When editing or adding an alert. Select how frequently this action occurs for each triggered alert in Execution Settings. the email or page is sent. Click Add Action. and multiple addresses must be separated with commas. such as packet loss. the status for the object changes. Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action. Alerts based on the status do not trigger in this instance. do trigger.  3. The status must be switched manually to a different status or configured to use the polled status. and choose a status. Select the Set Custom Status option. When the status is set with an alert. Click Add Action.  5. polled values.  7. and you can test the action using the Simulate button. The action is added to the trigger or reset action list.  5. Enter recipients and the message. packet loss continues to be 100%. then click Configure Action. the status does not update to the actual.  6.  2. 429 . Under Change Object Status Manually:  a. polled status. Some pager systems require a valid reply address to complete the page. click Add Action in the Trigger or Reset Action section of the Alert Wizard. Manually set a custom status Setting a custom status can be useful if you want to change the status of a familiar node. This is often used to prevent an action from occurring during specific windows.  4.  6. but does not affect actual. This schedule only applies to the alert action you are editing. Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action. and you can test the action using the Simulate button. When the trigger or reset conditions of the alert are met.  4.  n You must provide at least one email address in the To field. For example.  n Messaging is disabled if both the Subject and Message fields are empty. This schedule only applies to the alert action you are editing. When the trigger or reset conditions of the alert are met. Enter the SNMP information. but alerts based on a polled value.

Select how frequently this action occurs for each triggered alert in Execution Settings. The following procedure configures text-to-speech output for an alert trigger or reset. install. then click Configure Action. click Add Action in the Trigger or Reset Action section of the Alert Wizard.  1. The action notifies users of new alerts by reading the alert out loud. Enter the Message of your alert trigger. the Text to Speech action is not available to SolarWinds installations on Windows 7 or Windows Server 2008 and higher. Select either Use Event Log Message on Network Performance Monitor Server or Use Event Log Message on a Remote Server.  4. and configure the notification client. Select the Text to Speech Output option. The action is added to the trigger or reset action list. Due to restrictions on Windows service applications. then click Configure Action. Download and install the client on each computer that you want to play a sound.  2. Select the Windows Event Log option.  430 . Log an alert to the Windows Event Log on a specific server Add an entry to the Windows Event Log either on the SolarWinds Orion server or on a monitored remote server later investigation.  6.Use the speech synthesizer to read alerts The Text to Speech Output action uses the SolarWinds desktop notification client and your computer's speech synthesizer to convert text messages-to-speech messages. Click Add Action. When editing or adding an alert.  2. This is often used to prevent an action from occurring during specific windows. SolarWinds uses Microsoft® Speech Synthesis Engine version 5. When editing or adding an alert.  b. click Add Action in the Trigger or Reset Action section of the Alert Wizard. When the trigger or reset conditions of the alert are met. This capability is especially helpful for users who are visually impaired or who are not always at their desks to read alerts onscreen.  5. Under Text to Speech Output settings click Download our desktop notification client to download. If you are under active SolarWinds maintenance.  3.  1. you may also install and use other text-to-speech engines by visiting the SolarWinds website. This schedule only applies to the alert action you are editing. The server with the Windows Event Log that the alert writes to must be monitored by your Orion server. Then configure which synthesizer you want to play. Under Event Log Settings:  a. Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action. and you can test the action using the Simulate button. the message is read.  3.0.

the alert message is added to the Windows Event log. Use options. Alerts that you created in the desktop-based Alert Manager are migrated to the web-based alerting engine when upgrading to Core version 2015. Schedule the action by selecting Time of Day > Use special Time of Day schedule for this action. in the trigger conditions to accomplish similar tasks. When the trigger or reset conditions of the alert are met. Advanced Alerts Manager or Basic Alerts Manager. Changed or removed functionality The suppression section has not been carried over to web-based alerting. Click Add Action. Some alerts may not be successfully migrated and include information about why they were not migrated in the migration log. and NodesStatistics. Select how frequently this action occurs for each triggered alert in Execution Settings. such as the AlertHistory table. Alerts are instead created and managed in the SolarWinds Orion Web Console.  4. You can view the alert migration logs in the informational banners displayed after you update your installation. NodesData.1. alerts are no longer created with the desktop-based.  6. Database changes The following are a list of tables that have been changed that you may be using in custom SQL queries:  n Engines has been renamed to AllEngines. This schedule only applies to the alert action you are editing.3) 431 . and you can test the action using the Simulate button. Changes in the alerting engine As of Orion Platform version 2015. The new alerting engine also includes the following new alerting tables:  n Actions  n ActionsAssignments  n ActionsProperties  n AlertActive  n AlertActiveObjects  n AlertConditionState  n AlertConfigurations  n AlertHistory  n AlertHistoryView (introduced in 2015.  n History has been split into table-specific history tables.  5. The action is added to the trigger or reset action list.1. This is often used to prevent an action from occurring during specific windows. such as Condition must exist for more than.  n Nodes has been split into NodesCustomProperties.1 or later.

 n Large alert scope .Determines if the node supports SNMP or is ICMP only. A web-based alerting engine replaces the previous alerting engine and includes new alerting variables. part of the upgrade process migrates alerts created with the desktop-based alerting engine to the web-based alerting engine.Some conditions are no longer supported. You can select a new variable with the specific property you want to view.ObjectSubType as the macro name.When the alert is no longer active. column changes. You can no longer click the alert in the views.Some variables are no longer supported.  n Invalid conditions .When the alert active. You can select a new variable with the specific property you want to view.  n ${AlertEndTime} . see the online Database Changes spreadsheet. All alerts are migrated.The number of objects that are relevant to an alert may be too large to migrate. You can use the Time of Day scheduler to control when the alert is active. You can use Node. you can only view the alert definition through the web-based Alert Manager.  n ${TriggeredValue} . 432 .The value that triggered the alert. Limitations to migrated alerts After an alert has been migrated.2. including new tables.  n AlertMigrationLog  n AlertObjects  n AlertSchedules For a list of database changes from Orion Platform version 2014.The property the alert is monitoring. Common reasons that migration may not be successful include:  n Invalid alert variables or macros .2 to version 2016. Alert migration to the web The Advanced Alert Manager and the Basic Alert Manager are deprecated in SolarWinds Orion Core 2015. You can use the Time of Day scheduler to control when the alert is not active. including alerts that are disabled. or data constraint or data type changes. Macro or variable changes The following variables are no longer valid:  n ${Property} . To facilitate using the web-based alerting engine.  n ${ObjectSubType} .1 and later. The migration log records all alerts that are migrated and includes error messages for alerts that either cannot be migrated or that are not migrated successfully.  n ${AlertStartTime} . Migration issues Some alerts may not be successfully migrated.

Select the Integrate alert with other SolarWinds check box. Include additional alert properties in the alert by clicking Insert Variable and choosing the ones you want to include.  3.3. Open this port for outbound communication. You can choose to use this name as the subject field for the alert.  n The communication between the SolarWinds server and the ServiceNow instance uses HTTPS port 443. close.0. Before you begin Before you can configure the integration details in your SolarWinds Orion product.  2. 433 . check the prerequisites and configure your ServiceNow instance.  5. see the administrator guide of your product. Web Help Desk. Provide an Alert Subject. you can:  n Automatically create incidents in ServiceNow and assign them to the correct tech or group  n Synchronize the acknowledgment of alerts and tickets in SolarWinds Orion and ServiceNow  n Update. This information may be used to determine how a shared alert is handled by the other product. The integration with ServiceNow allows for two-way communication between your Orion Platform product and ServiceNow. On the Alert Summary page.  n Download the ServiceNow integration application from the ServiceNow app store.1 or later.Share alerts with other SolarWinds products Alerts may be shared with selected other SolarWinds products that are not part of the SolarWinds Orion Platform. By integrating the two systems.  4. This ensures that the variables you used in the alert message are translated correctly to the other product. and reopen tickets  n Suppress ticket storms You can integrate one Orion Platform product with multiple ServiceNow instances. or any other Orion Platform product running Core version 2016. such as AlertCentral.  n Install the integration app and configure your ServiceNow instance for the integration. The integration requires NPM 12.  1. expand Alert Integration. SAM 6. Choose the alert Severity.  n For minimum hardware and software requirements. or ServiceNow. Integrate an Orion Platform product with ServiceNow Integrate your Orion Platform product with ServiceNow® to automatically open new ServiceNow tickets based on critical events defined in your Orion Platform product.

Test the connection to your ServiceNow instance. After downloading the SolarWinds Alert Integration application from the ServiceNow store. and add the x_sow_intapp. Click Add Instance. click ServiceNow Instances.  5.  n Password  6. In the Orion Web Console. After the installation is complete. see Configure proxy settings. If you are accessing your ServiceNow instance through a HTTP proxy. SolarWinds recommends that you create a ServiceNow integration user with Web service access only. Navigate to the user administration section in ServiceNow. you receive descriptive messages to help you solve the issue. update.  3. When the installation is complete.Install and configure the SolarWinds Alert Integration application in ServiceNow The SolarWinds Alert Integration application enables the communication between your SolarWinds server and the ServiceNow instance. deploy the application in ServiceNow. click Settings > All Settings.  4. Edit the newly created user. Locate the SolarWinds Alert Integration application.integration_user role to the role list.  4.  2. For more information. and resolve alerts that were raised in your Orion Platform product in your ServiceNow® instance. and click Install. you can configure the integration to be able to automatically create.  7.  1. Click Save.  1. select Use a HTTP proxy server. a password.  8.  3. In the Alerts & Reports group. Specify that the new user should have Web service access only. you can now configure the integration with ServiceNow in your SolarWinds Orion server. If the connection is not working. Enter a name and the URL for the ServiceNow instance. and click the Configure your HTTP proxy settings link to edit the details. Configure an Orion Platform product with ServiceNow After completing the configuration of the integration in ServiceNow. Enter the ServiceNow credentials:  n Username The user name of the account that is configured for the SolarWinds integration role. and other required information. After installing the integration application and creating an integration user.  2.  2. Provide a user ID. the caption of the Install button will change to Installed. 434 . Create a ServiceNow integration user with Web service access only  1. Navigate to your downloaded system applications. and create a new user.

SSH. locate the Management resource. web browser integration for the user account must be enabled. Launch remote access applications from any Details view. You can use SSH commands to modify device settings and troubleshoot server issues. Click . 435 . Depending on the security settings of your browser. routers.  1. Access nodes using HTTP. Open the Node Details view for the server you want to view remotely.  2. Verify the Server IP address or hostname. and click SSH. For more information. and Telnet The Orion Web Console supports the use of HTTP. and telnet directly from the Orion Web Console.Access remote nodes You can access nodes through RDP. you may be asked to install an ActiveX control for remote desktop viewing. search the MSDN online help for "Registering an Application to a URI Scheme". located at the of the Node Details view. Web-based SSH You can access network devices and servers using SSH through a web-based feature. select an appropriate Screen Size. This can be accomplished within the Orion Web Console. Through the node details page. and ensure Allow Browser Integration is set to Yes. A web-based terminal launches providing an SSH direct terminal connection. Navigate to the user account. switches. including Linux hosts. Follow all prompts to install this required control. SSH.  3. and Telnet protocols for remote device access if associated applications like PuTTy and FiSSH on your Orion server are properly registered. Use Integrated Remote Desktop Sometimes it is necessary to console into a remote server to troubleshoot an issue. Press Ctrl+Alt+Break to enter/exit full screen mode. SSH. and then click Connect. virtual machines. The easiest way to open the Node Details view is to click the remote server you want to view in any All Nodes resource. To use the remote access applications. The web-based SSH supports all servers with SSH access capable and configured. The server or network device must be reachable by the Orion server. and firewalls.

Create. There are two ways to create a new report:  l Modify an existing web-based report (recommended). schedule. and select Web-based from the list. Click Add Content. Click Reports > All Reports in the menu bar. Use the web-based interface to customize these predefined reports and create your own reports. featuring the same charts. tables. can be created directly from the Orion Web Console.  4.  3. These predefined reports are sufficient for most needs. You can also create new reports. 436 . You must use the Orion Report Writer to maintain legacy reports created with Orion Report Writer.  2. export.  1. Add new content to or edit the existing content of an existing report. You can add pre-existing resources or create a custom table or chart. Create reports in the Orion Web Console Highly customizable reports. and import reports in the Orion Web Console The Orion Web Console does not allow you to edit legacy reports created with the Orion Report Writer. Select Report Origin in the Group by drop-down menu in the left pane. Predefined reports Your SolarWinds installation comes with many predefined reports that can be used as soon as there is data to be reported on.Create and view reports SolarWinds provides predefined reports for each Orion Platform product. You can also edit information about each resource. Select the layout and contents for the report. gauges.  l Create a completely new report. but can be further customized. This is the recommended approach for new users. Select the report to use as the basis for your new report. View a list of predefined reports by clicking Reports > All Reports in the menu bar. and click Duplicate & Edit. Modify an existing web-based report Modifying an existing web-based report is often the simplest way to generate a new report. and resources available in your views. and click Manage Reports.

SolarWinds recommends that you duplicate and edit an existing web-based report instead of creating a new one. and can be restricted to specific users through report limitations. Available options depend on the type of resource you add. On the Layout Builder panel. such as categories or custom properties. Use the report limitation category to restrict the report to specific user accounts. Schedule the report by clicking Schedule this report to run regularly. Click Next.  1. Click Next to display the Preview view. Select the resource to add to the report. Create a new web-based report Web-based reports are created in the Orion Web Console.  8. Review the Summary and click Submit to save the report.  9. Add report properties. click Add Content. Click the Edit button on the resources to make changes such as filtering the objects. group columns. You may be prompted to add content as soon as you click Create New Report.  5. or setting a sample interval.  2.  10. Click Reports > All Reports > Manage Reports > Create New Report. For example. and click Next. you must choose the application when adding the resource. and creating a new schedule or adding the report to an existing schedule. Users may be assigned specific report limitation categories and can only view reports that are in the same report limitation category. and click Select and Continue.  7. 437 . Click Next. if you want to track how many people use a specific application. Some resources require you to choose a specific object to report on.  6.

if you want to track how many people use a specific application. you must choose the application when adding the resource. The Layout Builder view is displayed with the selected resource added. For example. 438 . 3. Select the first resource to add to the report and click Select and Continue. Some resources require you to choose a specific object to report on.

In the Content area.  a. To filter a resource to include a specific set of data. click Edit Resource. 4. add resources and sections to the report.  b.  5. Click Add content to add resources to your report. 439 . Not all resources can be filtered. Click Add section to add more rows of content to this report.

create a new schedule or assign a schedule. Click Browse for logo to change the default logo.  n Enter a new value.  6. Select a report to edit from the Report Manager.  1. emailed. 440 . Review the Summary and click Submit to save the report. After adding and filtering the resource. header. or limitations. click Next.  3. in the Report width field. By default a report is 960 pixels wide with a header and footer.  9. On the Preview panel.  11. in pixels (px).  7. In the Layout Builder page. and click Next. Each resource has different filter options. Customize a web-based report layout You can customize how the report looks. To schedule the report. The Logo check box must be selected in the Header area. and a single column for content. such as categories. saved. The maximum image size is 600 pixels wide and 240 pixels high. or printed.  10. Add report properties.  Changing the logo does not affect other reports. and click Next. You can schedule a report to be generated.  8. enter a report name. or number of columns. change the width of your new report by doing one of the following:  n Click Fit to window width so the content of the report expands to the width of the browser window. Filter the resource and click Submit.  2. custom properties. and click Next. such as the width. click Schedule this report to run regularly.

In the Content area. You can now add content to this row as described above. Click Add to Layout. You can select a predefined page layout or manually add columns and rows.  3. You can reuse customized charts or tables by clicking Use previously specified objects when adding the chart or table and then selecting the object. click Add section. Click Select and Continue.  5. The Classic category grouping provides the most comprehensive list of available resources. Select Custom Chart or Custom Table. Add a custom chart or table to a web-based report You can create custom charts or tables for inclusion in web-based reports. change the number of columns or rows. and what you do with them to ensure that your custom charts and tables show meaningful results.  4.  1. see Add a custom chart or table to a web-based report. Select the resource from the list in the main pane.  3.  2. Select the required objects from the left pane.  7. If the resource requires you to select specific objects:  a. Select each option you want included.  4.  b. The following procedure assumes you are already creating or editing a report in the Orion Web Console. click Add Content in the column to which you want to add a new resource. Custom charts or tables are usually added when you are familiar with your SolarWinds Orion database or are comfortable creating SQL or SWQL queries. and click Select and Continue.  n Click Add section to add more rows  5. Because the Orion Platform generates so much data. You can edit the resource if you want to change the title or subtitle. If you want to add another row to your report. Click Add Content in the column to which you want to add a custom chart. Add content to a web-based report You can include any Orion Web Console resource. you need to ensure that you know exactly what data you are using. from which instances it originates.  6.  1. If you are an advanced user and want to add a Custom Chart or Table. including charts and graphs. 441 . Group by Reports to find the Custom Chart or Custom Table resources.  2. Resources can be dragged between columns and sections.  n Enter a number in the Layout columns field to change the number of columns. On the Layout Builder page. Select the Footer check box to include a footer in your report. in a report. Use the Group by field to filter the available resources or search for a specific resource.

Choose the object type you want to include. Filter or search for the data series.  b. if required. Select SQL or SWQL.  3. You must now edit the chart or table to choose the data series or columns you want to use and modify display and filtering settings.  n Select a custom Color for this data series.  b. click More.  6. and enter your query. and select the Show the sum of all data series. Here you can:  n Edit the Display name for this data series. Click Preview Results to test your query. Add a data series and customize a chart Once you have specified the objects for your custom chart.  n Advanced DataBase Query (SQL. the Edit Resource page opens.  a.only use if you are comfortable querying your SolarWinds database directly using SQL or SWQL. If you have just added a custom chart. 442 .  b.  5. Enter a Custom label for the Left axis. Click Add Data Series in Left Y-axis.  c.  4.  2. It is also the preferred method for relatively permanent network objects.  a.  n Show Trend for this data series. This is the most straightforward selection method. Click Add Data Series.use when you know which objects you want to include in your chart or table. For additional settings for each data series. Enter a name for this selection in the Selection Name field.use to select objects based on object properties. and click Add to Layout. Click Edit Chart on the resource in the Layout Builder page to open this page.  4. and select the one you want to use. This is the preferred selection method for groups of objects of a specified type that may change over time. Select Basic Selector to create and/or queries or select Advanced Selector to create complex queries.  n Dynamic Query Builder . Chart type. The groups available and the data series within these groups will depend on the object selected. Select the objects' check boxes. "All Cisco nodes in Austin" is an example of a group best defined using the Dynamic Query Builder. You can also change the sample interval and filter the results. The data series is added to the Left Y-axis. Enter your conditions.  7. Filter or search for the objects you want to include. you need to select the data series. Select the Units displayed.  n Show the 95th percentile line for this data series. and recommended for new users. Use one of the following methods to configure the objects displayed in the chart or table:  n Specific Objects (static selection) .  1.  5.  a. SWQL) .

 7. click Advanced.  5.  n Select the Data aggregation method to use for this column. Choose how you want to filter your report. Add a data series and customize a table After you have specified the objects to be reported on for a custom table. Select either Ascending or Descending from the Sort order drop-down. Click the plus sign in the table layout section to add more columns. This can be left.  3. Filter the number of records shown in the table by either a specific number or a percentage. Click Submit to return to the Add Report page. select the data series. 443 . This can be as frequent as once a minute to once a week.  6.  1. the Edit Resource page opens. and select the column you want to use. Select the Sample Interval. This applies the selected formatting to the data in this column. to summarize your data by time period. You can also sort and filter the results. The columns and options available depend on the objects selected. if you want to use this column when querying the database but do not want to show it. Filter or search for the column. Select the Data aggregation method required to summarize your data by time period.  11.  10. Click Add Column.  n Select the Display settings to be used for this column. You cannot use a separate time period or filter results settings for the right axis series.  n Select Allow HTML tags.  4. Click Add Column. you may want to use this column's data in the time-based settings but not show the data in the table.   It is possible to select a sample interval that is longer than the reporting period. Here you can:  n Edit the Display name for this column. and chart type. You can open this page by clicking Edit Table on the resource in the Layout Builder page.  d.  n Select the Alignment for this data. For example.  8. Data within each sample interval are summarized so that a single point or bar is plotted for each of these periods.  n Select Hide this column in the resulting table.  c.  a. If you have just added a custom table. For additional settings for a column. or center.  2. Select how you want to sort this selection of records from the Sort records by drop-down menu. right. Click Advanced if you want to sort records using a secondary field. Set up additional data series using the right axis to superimpose two charts using different labels. The choices depend on the data series selected. units.  b. if you want to use any HTML tags retrieved from the database for this column.  9.

Select the column used to specify the time period from the Date/Time column in this table drop-down menu. Select All child conditions must be satisfied (AND) or At least one child condition must be satisfied (OR).  b.  2. For the Basic Selector:  a. Click Add Simple Condition if you want to add another condition. Select the type of objects to report on from the I want to report on drop-down menu. a conditional relation.  b. Select which field you want to evaluate.  a. Click Add Condition.  10.  For example. you will replace or upgrade various pieces of equipment. Use the Group results by option to organize the table by the values in the columns you select.Adds a sub condition block Restrict who can access reports Use report limitation categories to limit access to any SolarWinds report created on SolarWinds Orion Platform versions 2013. Select the Sample Interval. such as Status and OS  n Add And/Or block . Users with a report limitation category set can only see reports that are in the same report limitation category.  d. or you can create a dynamic query that adds objects to the custom chart or table based on the properties you select.The child condition evaluates a single field.  1. Select All child conditions must be satisfied (AND) or At least one child condition must be satisfied (OR). Select the type of selector query you want to use (Basic or Advanced).The child condition evaluates two conditions. a conditional relation. You can only do this if your table contains a column with historical data. Click the + sign to add child conditions. Restrict data in your table to a specific time period by selecting Yes from the Time-based settings drop-down menu. as your network ages. This is used to summarize your data by time period. and provide a value.  b. The Advanced Selector provides access to all network object characteristics. and provide a value.  c.1 and later. Click Submit to return to the Add Report page. You can select each piece of equipment individually.  9.  8.  3.  4. like Status  n Add Double Value Comparison . For the Advanced Selector:  a.  n Add Single Value Comparison (Recommended) . 444 . Build conditions Use the Dynamic Query Builder selection when objects may change over time. and the Basic Selector provides access to a smaller subset of the most frequently used network object characteristics.  c. Select a property of the monitored object.

After the report limitation is created and the report saved.  2. the limitation is available in the user settings.X or later. save them to disk. Choose an existing limitation or enter a new one.1. created. reports are stored in a folder on the primary SolarWinds server (default location C:\Program Files\SolarWinds\Orion\Reports). reports are stored in the SolarWinds database. 445 . or email them to selected recipients.  n Reports can be assigned to schedules when they are being edited. Place reports into subfolders and restrict user access to the file system to limit user access.  n If you are running SolarWinds Orion Platform version 2013. or assign reports to existing schedules. Schedule a report to run automatically while creating or editing a report You can directly assign a report to a schedule while editing the report. In addition. Each report can have only one limitation. Create or add a report limitation category When you create or edit a report. Generate reports on a schedule Schedules enable you to set up report actions to occur at specific times. it is available in the user account's Define Settings page. These actions let you generate reports and print them. The No Reports limitation is a special report limitation category that removes all access to reports when applied to a user account.  n If you are running SolarWinds Orion Platform versions 2012. or in the Schedule Manager. and select Create new schedule. Restrict user access to the report After the report limitation is saved. Click Schedule this report to run regularly.  n Schedules can be created from the Report Manager. expand Report Limitation on the Properties page to add a report limitation. the Schedule Manager. you can add URLs to the schedules so that screen captures of specific websites at the time the reports were generated are included. You do not need to add No Reports as a limitation in the report properties.  1.2.X or earlier. select the limitation. You can create schedules for single or multiple reports. In the Report Limitation Category. and both users and reports may be assigned a report limitation category to restrict who can access the report. or when you create or edit a report. and save your changes. Navigate to the Schedule Report page.

 3.  n For email actions. You can create schedules and assign reports to schedules.  n To delay when the report runs.  4. You can assign multiple webpages. Click Add Time to select additional dates and times. Create and assign report schedules in Report Manager The Report Manager provides a list of all reports that have been set up for your SolarWinds Orion web- based reports. The action is added to the Actions list.  5. and the SMTP server. select Ending On. Click Add Frequency. Click on Schedule Report > Create New Schedule to display the Properties view. and select the action (Email. Click Add Action. and then select the date and time when you want the schedule to start. the message. Click Add Action. Select Include Report's URL to allow recipients to access the report remotely. or Save to Disk) to be executed on the configured schedule. Expand Advanced Settings to specify a user account so that its limitations are applied to this schedule. You can add multiple actions. Click Next to display the Frequency view. the credentials in domain\username format.  7. 446 . enter the recipients. and enter the User name or Account ID and Password. Print.  n To delay when the report runs. Start each URL with http:// or https://. Click Configure Action. select Ending On. Click Add Frequency.  3.  n For print actions. and print settings. select Specific Date in the Starting On field. Click Add Frequency. enter the location you want to save the report to. and enter the URL in the field displayed. and then select the date and time when you want the schedule to start.  5. Click Assign Webpage to include a snapshot of the selected website.  6. the printer. Create a report schedule  1. enter the Windows credentials necessary to access your printer. Click Another User.  2.  7.  n To stop the report from running automatically. Add additional reports to this schedule by clicking Assign another Report. and then select the date and time when you want the schedule to end. and the file type you want to save the report as.  n For save actions. Click Add Time to select additional dates and times. and then select the date and time when you want the schedule to end. The location must be accessible from the Orion Web Console server. and then select when you want to run the report. Select a report. and then select when you want to run the report. select Specific Date in the Starting On field.  n To stop the report from running automatically.  6.  4.

 11. Click Add Action.  8. Print. and assign reports to schedules. You can create. Click Add Frequency. If the schedule summary is correct. Assign a report to a schedule or multiple schedules  1. Click Reports > All Reports in the menu bar. Click Add Action.  n For email actions.  3. the message. Click Create New Schedule to add a new schedule. Select the schedule and click Assign to a Report. Select Include Report's URL to allow recipients to access the report remotely. the printer.  9. click Create Schedule.  n For print actions. run and delete schedules from this page. Click Configure Action.  13. which includes the associated reports and report actions. and the SMTP server. The schedule is displayed in the Schedule Manager. enter the location you want to save the report to. Click the Schedule Manager tab.  12. Select one or more reports. and then click Next to display the Actions view. enter the recipients. edit. and print settings. Click Next to display the Summary view.  n For save actions.  2. 447 . Schedule reports from the Schedule Manager The Report Scheduler provides a list of all report schedules that have been set up for your SolarWinds Orion web-based reports. or Save to Disk) to be executed on the configured schedule.  2. and select the action (Email. Select the schedule and click Run Now.  10. and then click Manage Reports in the upper right.  5. the credentials in domain\username format. The location must be accessible from the Orion Web Console server. Select the schedule or schedules in the Assign existing schedule list and clicking Assign Schedule(s) to confirm that you want to assign the report. The most common export formats have their own icons on the Orion Web Console report page. Export reports Select a supported export format based on how you want to use the exported file.  3. Report Writer is a legacy feature that you can access on your Orion server.  1. The selected schedule runs. enter the Windows credentials necessary to access your printer. and the file type you want to save the report as.  4. Click Schedule Report > Assign Existing Schedule.

Click Save.)   ✓ Export reports as XML You can save reports from the Orion Web Console in XML format and import them back. Modify legacy reports in Report Writer Before using Report Writer. Click Reports > All Reports in the menu bar. Click Export/Import. The file will be imported and its name displayed at the top of the list of reports. etc. Import XML reports If you import a report with the same name as an existing report.  1. Display the web-based reports. and click Manage Reports in the upper-right corner.  4. A variety of reports are included with Report Writer. you must collect some data in a database populated with devices you want to monitor. Click Reports > All Reports in the menu bar. GIF. Supported Formats Orion Web Console Report Writer XML ✓   Excel ✓ ✓ PDF ✓ ✓ HTML and MHTML   ✓ Image (BMP. Display the web-based reports. Click the report > Export/Import. The following procedure starts Report Writer. Export Excel and PDF reports from the Orion Web Console You can view and edit Excel files as spreadsheets. and click Manage Reports in the upper right corner.  1.  5. Click either Export as Excel or Export as PDF. JPG. The Export to Excel button is only displayed if the report contains only custom table resources. 448 . Click Reports > All Reports in the menu bar. Other resources cannot be converted to the Excel format. and then click Export Report.  3.  4.  1. it will be prefixed with "Copy of".  2. and then click Open. Navigate to the required XML file on a network drive. and icons that precede report names distinguish available report types. Open the report. PNG.  2. and click Manage Reports in the upper-right corner.  2.  3. and then click Import Report. You can create read-only files using the PDF export that retain the exact formatting used in the original report.  3.

 4. based upon the type of report. Click File > Settings. or switch to Preview mode from Design mode. The image must be in JPEG format with a height of no more than 150 pixels.  n Page navigation buttons: First Page.  n Print report Report Writer Design Mode Use Design mode to create new reports and modify or rename existing reports. see Report Writer Design Mode. typically located in C:\Program Files\. the query to generate the report runs. and presented. and then selecting Display horizontal lines between each row. Reporting.  2. Customize report headers and footers with Report Writer To add your company logo as the report header and footer. Separate the data for individual network objects with horizontal lines by clicking Report Style. and Mapping > Report Writer. and then click Refresh. 449 .  3. When you open a report in Preview mode.  1. Page Down. and then Report Writer displays the results. Report Writer Preview Mode Preview mode shows a report as it will print.jpg in the SolarWinds\Common\WebResources folder. The options available depend on the type of report being designed. In the General tab of the Report Writer Settings window. For more information. For more information about creating reports in Report Writer.  n Preview displays the report as it will appear in printed form. filtered. and report presentation. The options available for creating and modifying reports are the same. For more information. save your logo as Header. Click Start > All Programs > SolarWinds Orion > Alerting. see Create and modify reports in Report Writer. see Report Writer Preview Mode. but all reports require that you select the data to include and decide how that data will be sorted.  n Report Designer is the report creation and editing interface.  n Current page number and total number of pages in the report. Design mode options are also dynamic. Page Up. ordered. Click OK to exit Report Writer Settings. select either of the following as a default viewing mode: You can toggle between Preview and Report Designer modes at any time by clicking Preview or Design in the toolbar.  5. and Last Page  n Zoom views Double-click a preview to zoom in and double-right-click to zoom out. included report data.

 1. clear Make this Report available from the Orion website. Subtitle. Specify the Report Group.Create and modify reports in Report Writer Use the following procedure to modify or create reports in Report Writer. If you do not want to make this report available on your Orion Web Console. showing titling and display options. 450 . and Description. By default. To perform an operation on the data in the current field.  c. Click Preview to enter Preview Mode. If you are configuring a historical report and you do not want to group data by days. Click the asterisk after Field.  b. Report Writer General Options tab The General tab is displayed by default.  a. and then select the type of information to include in the current report field. To sort the data in the current field.  1.  3. data in some availability and historical reports is grouped by days when displayed in the Orion Web Console. some formatting tabs described in the following sections may not be available. the new report is added to that existing group in the left pane of the main window. Depending on the report. clear Group historical data by days. Click Report > Show SQL to add a read-only SQL tab to the Design window. select Add a new field. If you are creating a new report or adding fields to an existing report. Click Select Fields. click the ellipsis. By default.  2. Data grouping by days is not viewable in Report Viewer.  3. Report Writer Select Fields Options tab Select the data fields in a report.  n A preview of your report is also available at any time. Modify an existing report by clicking an existing report from the inventory in the left pane of the main Report Writer window. and then click OK. Each report offers different configuration options. Select the type of report that you would like to create.  1.  n The SQL query used to generate a report may be viewed in an additional tab. If you use an existing report group name. click the sort asterisk and select a sort order. Select the display Orientation of your report. Report Title. and then click Design to return to Design Mode. most reports are made available for display in the Orion Web Console.  4. Click File > New Report to create a new report.  2. click the function asterisk and select an operation.  2. and then dynamically define each new report field.

click Execute SQL Query to view the current query results. complete the following steps:  a. Report Writer Top XX Records Options tab You can limit the number of records shown in your report to either a top number or a top percentage of all results.  1. To test that your selections will give you the results you want.  b. Report Writer Filter Results Options tab Use the Filter Results tab to generate filter conditions for field data by selecting appropriate descriptors from the linked context menus.  n Select Move current condition forward or Move current condition backward to change the order of your conditions. Select either Show only the Top number Records or Show the Top percentage % of Records. To preview your report. To show all records in your report. To sort the data in the current field.  c.  n Select Delete current condition to remove a selected condition. and then select the appropriate action. Select individual filter conditions to enable them in your report. To perform an operation on the data in the current field.  a. but their sort and function configurations are retained.  n Select Add a new complex condition to define a condition that filters other defined conditions.  2.  6.  n Select Add a new advanced elementary condition to generate a condition based on a comparison of device data fields and values. click the asterisk after Sort and select a sort order. select Show All Records. Click Browse.  1.  d. Top XX options are configured as shown below. Click the asterisk after Field.  b. click the Field. To specify a truncated list of eligible items for your report. click Preview. or function that you want to change and select a new value.  2. Cleared fields are not displayed in your report. sort. click Browse. To delete a field or rearrange the order of the fields that are listed in your report.  5. The lists of available linked descriptors are dynamically generated in consideration of all other variables within the same condition. select a field. Select the type of information to include in the current report field. and then select from the following options:  n Select Add a new elementary condition to generate a condition based on a direct comparison of network object data fields.  3. Provide appropriate number or percentage values. 451 .  4. click the asterisk after Function and select an operation. If you are modifying an existing report.

face. Select a location for the Summary Date/Time field. you may edit the timeout setting in the SWNetPerfMon. To configure Time Frame options. select a field from the list to define your group.  4. or right. Add.  l If you receive a SQL Timeout error message. and then select the summarization period. To add a new report group. Month. and delete report groups to organize the data in your report. or Specific Time Frame.  1.  l Because the Relative Time Frame is continuously variable. even if they are run close together in time. complete the following steps:  a. and so on. select the field from the Report Groups list. To format results fields.  2. If you do not want to summarize your results. Report Writer Report Grouping Options tab Use the Report Grouping tab to group results by field descriptor within your report.  n The Web URL is the dynamic location of your published report with respect to your Orion Web Console. reports run with it may show different results.  3. select a Named.  n Alignment may be left.Report Writer Time Frame Options tab You can limit the scope of your report to a specific period of time.db file. Relative. this file is located in the C:\Program Files\SolarWinds\Orion directory.  c.  b. Report Writer Field Formatting Options tab Use the Field Formatting tab to customize the format of the various results fields in your report. confirm that Do not Summarize the Results is selected. select the field you want to format. and then click Add Report Group to add your selected field to the Report Groups list. and then click Edit Report Group. Report Writer Summarization Options tab You can generate summaries of your results over specific periods of time using the Summarization tab. and then select or provide required values. use the up and down arrows to change the grouping order. To edit an existing report group. If you want to summarize your results.  n The formatting options available for each field may be different according to the nature of the 452 . color. center.  1. edit. Establish and edit report groups as follows. By default. Specify the location of the summary field for your report.  n Select Transparent Background for better results when publishing your report to the Web. and then edit labels and select options. Select Summarize the Results by Hour.  n Font size. Date. The following options may be changed as needed:  n The Group Header is the text that designates groups on your report.  2. and background may all be modified by clicking associated ellipses. To change the grouping order.

data contained in that field. Click Settings > All Settings in the menu bar. For more information.  3. Open the Orion Reports folder. account-limited user folder. Click Start > All Programs > SolarWinds Orion > Alerting.  4.  1.  1. Allow access to restricted Report Writer reports SolarWinds Report Writer reports respect Orion Web Console account limitations.  6. Click the required file format. Create a new folder using the name of the account-limited user.  2. All reports created or predefined in Report Writer are. To export to XML.  2. In the Reports section. Click Save. Log in to the Orion Web Console as an administrator. Type a name for the exported file.  5. by default.  6. select the Orion Reports folder you created in the Report Limitation Category list. Click Submit. Select the account-limited user.  5. For security. Click File > Export. see Creating New Accounts and Setting Account Limitations. reports are not available to users with limited accounts unless an SolarWinds Orion administrator specifically provides access.  n To view your changes at any time. Copy the reports you want the account-limited user to see from the Orion Reports folder into the new. Export reports from Report Writer Report Writer provides an export menu that enables you to save your report in all formats listed in Export reports except XML. 453 .  3.  9. in C:\Program Files\SolarWinds\Orion\Reports.  n Select Hidden Field to hide any field in your report. Click Manage Accounts in the Accounts grouping of the Orion Website Administration page.  7.  4. stored.  8. and then click Edit. click Preview. Click the report you want to export. you need to use the SolarWinds Orion Web Console. Reporting and Mapping > Orion Report Writer.