srm profiler administrator guide

ADMINISTRATOR GUIDE

Storage Resource Monitor -ProfilerVersion 6.2

Last Updated: Friday, July 28, 2017

Retrieve the latest version from: https://support.solarwinds.com/Success_Center/Storage_Resource_Monitor_(STM)/STM_Documentation

Copyright © 2017 SolarWinds Worldwide, LLC. All rights reserved worldwide.

No part of this document may be reproduced by any means nor modified, decompiled, disassembled,published or distributed, in whole or in part, or translated to any electronic medium or other meanswithout the written consent of SolarWinds. All right, title, and interest in and to the software anddocumentation 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 INCLUDINGWITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULARPURPOSE, AND NONINFRINGEMENT. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS, NOR ITS LICENSORSBE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY EVENIF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The SOLARWINDS and SOLARWINDS & Design marks are the exclusive property of SolarWinds Worldwide,LLC and its affiliates, are registered with the U.S. Patent and Trademark Office, and may be registered orpending registration in other countries. All other SolarWinds trademarks, service marks, and logos may becommon law marks, registered or pending registration in the United States or in other countries. All othertrademarks mentioned herein are used for identification purposes only and may be or are trademarks orregistered trademarks of their respective companies.

page 2

Table of Contents

Introduction to SolarWinds SRM Profiler 18

Supported devices 18

SRM Profiler architecture 20

SRM Profiler server 20

SRM Profiler agents 20

SRM Profiler proxy agents 20

Architecture diagram 22

Installation 23

SRM Profiler system requirements 23

SRM Profiler server requirements 23

Port requirements 24

Ports required by SRM Profiler 25

Application Module requirements 26

Agent requirements 28

Install SRM Profiler 28

Install SRM Profiler server on Windows 29

Installation path 29

Windows clean install 29

Uninstall SRM Profiler 30

Install SRM Profiler server on Linux 30

Install on a Linux server 31

Stop the server 31

Uninstall SRM Profiler on Linux 31

Download the installer and activation key 31

License SRM Profiler 32

ADMINISTRATOR GUIDE: STORAGE RESOURCE MONITOR - PROFILER

page 3

SRM Profiler only 32

Share the license between SRM Profiler and SRM 33

Install SRM Profiler agents 33

Install an agent on Windows 34

Installing an Agent on Windows Cluster 34

Install an agent on Linux 37

Uninstall the Linux agent 38

Configure an agent 38

Change the default OS policy 38

Turn off Performance Reporting 39

Turn off Real Time Status 40

Manually upgrade JAVA (JRE) v1.8 for the SRM Profiler agent 40

Integrate SRM and SRM Profiler 41

Reclaim your license 41

Reclaiming your license from SRM 42

Reclaiming your license from SRM via SRM Profiler 42

Enable integration between SRM and SRM Profiler 43

Disable integration between SRM and SRM Profiler 43

Verifying your License Count with SRM Profiler 44

Verify your license count with SRM 44

Authentication between SRM and SRM Profiler 45

Key scenarios when SRM Profiler and SRM are integrated 46

SRM on startup 46

Add an array to SRM 46

Add an array to SRM Profiler 47

Integrate Orion NPM with SRM Profiler 47

Install the SRM Profiler /Orion NPM integration piece 47

Integrate Virtualization Manager 48

page 4

Back up and scan the SRM Profiler database 48

Upgrade SRM Profiler 48

Verify there is sufficient disk space 49

Back up your SRM Profiler database 50

Upgrade the SRM Profiler server 50

Upgrade the SRM Profiler server on Linux 50

Upgrade your license 51

Verification of software version 51

Upgrade SRM Profiler agents 52

Upgrade agents from the Web Console 52

Upgrade agents manually 52

Upgrade agents on Linux 52

Upgrade to SRM Profiler 6.2 from 6.0 or earlier 52

Administer 54

Deploy SRM Profiler 54

Minimum recommendations for small, medium and large environments 54

SRM Profiler proxy agent deployment 56

Minimum recommendations for agent hardware 56

Recommended resources per proxy agent 56

Number of SRM Profiler agents and proxy agents per SRM Profiler server 57

Sample deployment 57

File Analysis 59

The Getting Started page 59

The Getting Started page 59

The Web Console 60

SRM Profiler Health Status 61

Monitors 61

Reports 62


page 5

Server and NAS Groups 62

SAN Groups 62

LUN Groups 62

Virtualization 63

The Health Status Overview page 63

Server performance metrics 64

Services 64

Database status 65

Device types 65

SRM Profiler proxy agents 66

Collection jobs queue 66

Help and support 67

Manage user accounts 67

Adding users 67

Level of user privileges 68

Editing user profiles 69

Managing user email notifications 69

Setting up notifications 69

SRM Profiler Settings 70

Agents settings 71

Array settings 72

Database settings 72

Email settings 72

File Analysis settings 73

GUI settings 73

Real Time settings 74

Reporter settings 75

Server settings 75

page 6

Trap Forwarding settings 77

Forwarding traps for SRM Profiler server 77

Forward traps for SRM Profiler agent 78

User Authentication settings (LDAP settings) 78

Virtualization settings 79

Manage agent assignments 80

Enabling SSL login for the website 80

RM Profiler database 82

Backup the SRM Profiler database 83

Recover the SRM Profiler database 84

Database maintenance using dbutil 84

Run dbutil in Windows 84

Run dbutil in Linux 85

Advanced configuration of SRM Profiler 85

Increase Memory for SRM Profiler Services 86

Adjust memory settings for Storage Manager Collector 86

Adjust memory settings for SRM Profiler agent or SRM Profiler proxy agent 87

Adjust memory settings for Storage Manager Event Receiver 88

Adjust memory ssettings for Storage Manager Poller 89

Adjust memory settings for Storage Manager Maintenance Service 90

Increasing web server memory 90

Modifying database memory settings 92

Antivirus and intrusion detection 93

SRM Profiler Server exclusions - Windows 93

SRM Profiler Server exclusions - Linux 94

SRM Profiler agent exclusions - Windows 94

SRM Profiler agent exclusions - Non-Windows 94

Port exclusions for SRM Profiler server and agents 94


page 7

Library and support via thwack! 94

Use reports and schedules 94

Administrator reports 95

User reports 95

Enterprise storage reports 96

File repository 96

Define a File Repository 96

Manage reports 97

Run a report 97

Schedule a report 97

Report schedule list 98

Exporting report data 98

Create a new report 99

Delete a report 100

Example report 100

Using groups 104

Group examples 105

Creating, editing, and deleting groups 105

Create a new group 105

Create a new subgroup 107

Edit or delete a group 107

Create, edit, and delete file type groups 107

Create a file type group 107

Edit and delete a file type group 108

Using rules 108

Create a new rule 109

File Analysis rules 109

What is File Analysis? 109

page 8

What does it report? 110

Threshold rules 111

Windows Event Log rules 112

Directory Analysis rule 113

Manage Rules 115

Schedule Rules 117

Asset Change rules 117

Using external scripts 118

Add a script 118

Edit a script 118

Use scripts 119

Run Client Script 120

Run Server Script 120

Use policies and set alerts in SRM Profiler 120

Set alerts in SRM Profiler 121

Alert notifications 122

Data retention policies 123

Calculating data retention duration 123

Policies 124

Create a policy 124

Edit a policy 125

Select rules for your policy 126

Add devices 127

Add and configure devices 127

Add a device 127

Edit a device 127

Change the IP Address for any agents 127

Delete a device 128


page 9

Activate/deactivate polling 128

Add storage arrays 128

Use the Add A Device wizard 129

Troubleshoot with the Add a Device wizard 132

The provider for this array is not responding 132

The provider rejected your login credentials 132

The provider is responding with a namespace different than the array you are trying toconfigure 132

The provider does not have any arrays configured 133

Arrays with no Assigned Agents 133

3PAR 133

Before you begin 133

Add the array 134


Manual configuration 134

Dell Compellent 135

Before You Begin 136

Add the array 136



Dell Equalogic 138


Add the array 138

Configure the array 139

Dell MD3xxx 139


Add the array 140


page 10


EMC Celerra 141


Add the array 141


EMC Isilon 143


Add the array 143


EMC Symmetrix, Symmetrix DMX, Symmetrix VMAX 144


Add the array 145



EMC VNX/CLARiiON 146


Add the array 147



Hitachi Data Systems (HDS) 149


Add the array 149



HP EVA 150


Add the array 151



page 11


Additional information 152

HP Lefthand P4000 153


Add the array 153


HP XP 154


Add the array 155



IBM DS3xxx, DS4xxx, DS5xxx 156


Add the array 157



IBM DS6xxx and DS8xxx 158


Add the array 159



IBM ESS 161


Add the array 161



IBM N-Series 162


page 12

Add the array 163


IBM N-Series Operations Manager 165


Add the array 165


IBM SVC, V7000 165


Add the array 166



IBM XIV 168


Add the array 168



NetApp E-Series LSI 169


Add the array 170



NetApp Filer 172


Adding NetApp filer 172

Configuring NetApp filer 173

Additional information 174

NetApp Operations Manager 175



page 13

Adding NetApp Operations Manager 175

Configuring NetApp Operations Manager 175

Assigning NetApp filers 176

Removing NetApp filers 176

ONStor 177


Add the array 178


Pillar 178


Add the array 179



Sun StorageTek 2xxx, 6xxx, and FLX Series 180


Add the array 181



Sun StorageTek 99xx Series 182


Add the array 183



Xiotech Emprise 7000 184


Add the array 185


Xiotech Magnitude 3D 3xxx 185

page 14


Add the array 186


Xiotech Magnitude 3D 4000 186


Add the array 186


Adding Fibre Channel devices 187

Fibre Channel switch requirements 187

Community string 189

Configure a McData Fibre Channel switch device 189

SnapMirror monitor 190

Virtualization dashboard 190

Discover VM targets 191

P2V simulator 191

Thin provisioning 191

Add VMware monitoring 192

VMware device requirements 192

Adding VMware 193

Step 1: Configuring a VMware VC Instance 194

Step 2: Assigning VMware ESX Hosts 194

Removing VMware ESX hosts 195

SRM Profiler and vCenter Asset Collection 196

Setting up file analysis 197

Requirements 197

Assign remote shares 198

Assign local shares 199

Enabling file analysis 199


page 15

Summary for configuring file analysis 200

Common tasks 201

Use LDAP to add a new user 201

Delete an administrator account with root privileges 201

Change the default Web Console port from 9000 202

Assign remote shares on virtual machines 203

Configuring SRM Profiler agents to use a specific NIC (Network Interface Card) on servers withmultiple NICs 203

Hide report queries from being displayed in the HTML source code 204

How to change the temporary directory when running a myisamchk 204

Changing trap severities on the Event Monitor webpage 204

Set up disaster recovery with SRM Profiler 205

Set up an alert for disk Failure on a SAN 206

Create a threshold rule for disk failure 207

Create a policy for the disk failure rule 207

Alert notifications 208

What is a SMI-S provider? 208

SMI-S provider deployment types 209

SMI-S FAQ 209

Configure storage arrays for use with SRM Profiler 210

SMI-S provider tools 211

CIMWorkshop 211

EMC TestSMI provider 213

General troubleshooting 215

Device Diagnostic wizard 215

Troubleshooting resources 215

thwack! user community 215

Providing feedback 216

page 16

Install local help files 216

Upload modules 216

Alert severity in SRM Profiler 216

Operational status properties 217

Performance chart time ranges and their corresponding units 218

Backup requirements for SRM Profiler 219

CA ARCserve 219

CommVault 219

EMC/Legato NetWorker 220

IBM TSM 221

Symantec Backup Exec 222

Symantec Veritas NetBackup 222


page 17

Introduction to SolarWinds SRM ProfilerThe SolarWinds SRM Profiler provides accurate, critical classification and performance information forSAN, NAS, Fibre Channel switches and HBAs, enabling you to monitor, alert, forecast, and act on storageperformance, utilization, and storage provisioning.

Earlier releases of the SRM Profiler were named STM or Storage Manager.

COMMON USES FOR SRM PROFILER

Increased Efficiencyl Reclaim system administrator time through automationl Resource Optimizationl SLA metrics & storage reallocation cost savings

Strategic Planningl Forecasting & trending for business continuity & capital expenditureplanning

l Risk Mitigationl Reduce the human error associated with managing backup & storageenvironments

l Historical trending

l Supported devices

Supported devices

SRM PROFILER CURRENTLY SUPPORTS THE FOLLOWING PLATFORMS, APPLICATIONS, ANDDEVICES:

OSl Linuxl Windows ®l Unix (IBM AIX, HP-UX, Sun Solaris)

Virtualization

Virtualization is disabled when running SRMProfiler in evaluation mode.

l VMware ®

Applicationsl Oracle ®l SQL Server ®

page 18

SRM PROFILER CURRENTLY SUPPORTS THE FOLLOWING PLATFORMS, APPLICATIONS, ANDDEVICES:

SAN and NAS:l Dell™ EqualLogic™l Dell PowerVault MD3000il Dell Compellentl EMC Celerra ®l EMC VNX/CLARiiON ®l EMC Isilon™l EMC Symmetrix DMX ,VMAX™l Hitachi Data Systems ™l HP 3PARl HP StorageWorks EVAl HP LeftHand P4000l HP StorageWorks XPl IBM® System Storage DS® 3xxx, 4xxx,5xxx, 6xxx, 8xxx

l IBM System Storage™ N seriesl IBMSystem Storage™ SANVolumeController (SVC)

l IBM V7000l NetApp®l LSI™l ONStor™l Pillarl SGI

Fibre ChannelSwitches and Fabric

l Brocade Switchesl Cisco Switchesl McDatal QLogic switchesl Host Bus Adapters (HBAs) (Emulex®and QLogic)


page 19

SRM Profiler architectureThe SRM Profiler Server collects data from agents, traps, pollers, and saves the data to a central databaseand distributes information to users via the web interface. SRM Profiler server also allows the user tomanage the SRM Profiler agents and SRM Profiler proxy agents remotely.

The SRM Profiler server can also serve as a SRM Profiler agent or SRM Profiler proxy agent.

SRM Profiler agents provide the framework to gather storage, server performance and file analysisinformation from the local device and transmit it to the SRM Profiler server.

SRM Profiler proxy agents provide the framework to gather storage, server performance and file analysisinformation from local devices and collect Storage, Application, Virtual and Server information fromexternal devices.

The Architecture diagram illustrates the relationship between the proxy agents and the SRM Profilerserver.

SRMPROFILER SERVERThe SRM Profiler server consists of a database, web server, collector, poller, event receiver, and amaintenance process.

SRM Profiler uses a variety of methods to collect data, both local and remote. SRM Profiler can collect mostdata remotely, including storage arrays (NAS and SAN), VMware® hosts and virtual machines, FibreChannel switches, databases (SQL and Oracle®) and file analysis.

Virtualization is disabled when you are running SRM Profiler in evaluation mode.

For physical servers, agents are required on those servers. Some of the methods that SRM Profiler uses tocollect data includes: SMI-S, Telnet/SSH, SNMP, CIFS/NFS, API, WMI, SQL queries, Web Services, commandline, and log parsing. Primary communication between the SRM Profiler server and agents occurs on ports4319 TCP (HTTP) and 162 UDP (SNMP).

SRMPROFILER AGENTSSRM Profiler agents reside on operating systems, and monitor statistics about the operating system onwhich they are installed.

The SRM Profiler agent will pull CPU, Memory, Disk (storage and speed), Network Values and File Analysisfrom the server it is installed on. The SRM Profiler agent can also alert on events generated from theserver.

SRMPROFILER PROXY AGENTSSRM Profiler proxy agents perform the same task as the SRM Profiler agent, and collect storage,application, virtual and server information from external devices.

page 20

To use the SRM Profiler agent as a SRM Profiler proxy agent, you must install the agent software on eithera Windows or Linux platform. The SRM Profiler agent and proxy agent use the same installer software.

The SRM Profiler agent and SRM Profiler proxy agent are the same software; the naming conventionis determined by how the agent software is deployed in your environment.

l If you want the agent software to just monitor the server it is installed on, it will be considered anagent.

l If you want the agent software to monitor external devices such as SAN, NAS, and Fibre ChannelSwitches, it is consider this a proxy agent.

The following illustration shows SRM Profiler proxy agents collecting information from two VMware VirtualCenters and one EMC VNX/Clariion via its SMI-S Provider.


When the SRM Profiler proxy agent has collected enough data, it sends an SNMP trap (UDP port 162, 10162or 20162) to the SRM Profiler server notifying it that data is waiting to be received. After receiving the trap,SRM Profiler server establishes a connection via HTTP or HTTPS Port 4319 to the SRM Profiler proxy agentand retrieve the data.

After all information has been retrieved, the SRM Profiler proxy agent deletes it from its temporary datasub directories and the process starts over again.

The SRM Profiler server stores all retrieved information in the SRM Profiler database.

Click here to see the ports required by SRM Profiler proxy agents for collecting information.

The following tables summarize the differences between agents and proxy agents.


page 21

OPERATING SYSTEMS

Windows32/64 bit

Linux32/64 bit

AIX (PPC32/64)

HP_UX(Itanium)

Solaris (SPARC orIntel 32/64 bit)

Agent Yes Yes Yes Yes Yes

ProxyAgent

Yes Yes No No No

Resources Monitored

Server (Disk, Memory, CPU, Network) SAN/NAS Virtual Fibre Channel Switch

Agent Yes No No No

Proxy Agent Yes Yes Yes Yes

ARCHITECTURE DIAGRAMThe SRM Profiler architecture diagram illustrates the relationship between sources, the SRM Profiler proxyagent, and the SRM Profiler server.

page 22

Installationl Requirementsl Install SRM Profilerl Install SRM Profiler agentsl Integrate SRM Profiler and SRMl Upgrade SRM Profiler

SRM Profiler system requirementsVerify that you have downloaded the correct versions for your environment and that your system meetsthe minimum requirements.

l Server requirementsl Agent requirementsl Application Module requirementsl Port requirementsl VMware requirementsl Fibre Channel requirements

SRMPROFILER SERVER REQUIREMENTS

OPERATING SYSTEM REQUIREMENTS

Windows (64 bit) Windows Server 2003 R2, Windows Server 2008 R1/R2, Windows Server 2012 R1/R2

Evaluations can be run on XP, Vista, 7 and 8 (x86-64)

Linux (64 bit) Red Hat Enterprise Linux(RHEL) 5.x, 6.x

SUSE 10, 11

CentOS 5, 6

PORTS REQUIREMENTS

Port Web server port (HTTP) for the GUI. This port can be changed in the server.xml.


page 23

PORTS REQUIREMENTS

9000

Port4319

Communications port with SRM Profiler agents (HTTP). This port can be changed system wide,or on an agent by agent basis.

Port 162 Default SNMP port. Must be changed 10162 if using Orion NPM.

Port3306

Used by the SRM Profiler database.

Port8443

Used by SolarWinds Information Service (SWIS)

MINIMUM HARDWARE REQUIREMENTS

CPU 2 CPUs

Memory 8 GB

Storage 40 GB

BROWSER REQUIREMENTS

Internet Explorer IE8, IE9, IE10

FireFox 3.6 and above

Chrome 10 and above

The installation does NOT require a reboot.

PORTREQUIREMENTSThis graphic shows the SRM Profiler with supported storage devices and the ports required forcommunications.

page 24

This graphic shows SRM Profiler integrated with SRM main poller, additional poller, additional web server,and the port required for communications.

PORTS REQUIRED BY SRM PROFILER

PORT TYPE DESCRIPTION

22 TCP Used on the control system for EMC Celerra Storage Devices

80 TCP Used on the NetApp head/cluster node and any available


page 25

PORT TYPE DESCRIPTION

CIFS/NFS.

161 UDP Used for polling of Fiber Channel Switches: Cisco MDS, Brocade,McData, and QLogic Switches. Used on the EqualLogic Group IP.

162 UDP Agents use this port to notify SRM Profiler server wheninformation is available to be retrieved from the agent. If port 162is in use by Orion NPM, then SRM Profiler will use 10162 or 20162when SNMP traps are sent to the SRM Profiler server.

443 TCP SRM Profiler uses this port to communicate with VMware VirtualCenter or ESX server. Used on the NetApp head/cluster node andany available CIFS/NFS.

APPLICATION MODULE REQUIREMENTSThe following requirements apply to any application modules you may want to monitor.

MICROSOFT SQL SERVER

Versions/Models 2000, 2005, 2008

Requires SRM Profileragent?

No

Prerequisites Domain or Local DB user with:

l Read-only access to ALL tables in the MASTER databasel Permission to execute Stored Proceduresl Permission to execute DBCC commands

Credentials Account and password stored in SRM Profiler database and configuration fileson SRM Profiler proxy agent using custom encryption

Read/Write Actions Read Only

Ports Used 1433 or 1094 on MS SQL Server (depends on SQL configuration)

Communication SQL Queries over IP

Requires a SRMProfiler proxy agent?

Yes –via SRM Profiler server

ORACLE

page 26

MICROSOFT SQL SERVER

Versions/Models 10G, 11G


No

Prerequisites Requires ID with Table name Permissions

V$SGASTAT select

v$version select

v$statname select

v$sesstat select

v$session select

v$sysstat select

dba_rollback_segs select

dba_indexes select

dba_tables select

dba_segments select

sys.dba_extents select

sys.dba_data_files select

sys.dba_tablespaces select

sys.dba_free_space select

V$OSSTAT select

V$SYSMETRIC_HISTORY select



Ports Used Depends on Oracle configuration

Communication SQL Queries over IP


Yes – via SRM Profiler server


page 27

AGENT REQUIREMENTS

OPERATING SYSTEM

REQUIREMENTSSUPPORTED VERSIONS

Windows (32 or 64 bit) Windows Server 2003 R2, Windows Server 2008 R1/R2, WindowsServer 2012 R1/R2

Evaluations can be run on XP, Vista, 7 (x86-32 and x86-64), and 8 (x86-32 and x86-64)

Windows 64 bit Windows Server 2003 R2, Windows Server 2008 R1/R2, WindowsServer 2012 R1/R2

Unix (x86-32 and x86-64) Solaris Sparc 9, 10

Solaris 10 (x86-32)

AIX PPC64: AIX 6.1, 7.1

HP-UX-PA-RISC and Itanium: HP-UX 11i versions 1 through 3

HP-UX (Itanium-64) 11.x

Linux (32 or 64 bit) Red Hat Enterprise Linux

(RHEL) 5.x, 6.x

SUSE 10, 11

CentOS 5, 6

Evaluations can be run on Ubuntu Server 10, 11

VMware VMware 4.x, 5.x ESX and VM

When monitoring Solaris servers it is important to have the SRM Profiler agent installed in a globalzone. This prevents issues with executing native OS commands such as ptrconf.

Install SRM ProfilerSRM Profiler consists of two separate components:

l Server installationl Agent installation

After SRM Profiler is installed, add the devices to be monitored. Some devices require the installation orconfiguration of a SMI-S Provider or similar communication software.

page 28

To determine if your device requires additional installations see Add Storage Arrays.

INSTALL SRMPROFILER SERVER ONWINDOWSBefore Installing:

l Ensure you have downloaded the correct installer.l Close any service window(s). Installation will not work properly if you leave this window open.l Stop your anti-virus software. Some anti-virus software packages can interfere with the productinstallation.

l Back up the SRM Profiler database. See Backing up the SRM Profiler database for moreinformation.

l Uninstall any previous instances of the MariaDB or MySQL. Only one instance of the MariaDB issupported on the SRM Profiler server.

l SRM Profiler versions 5.6 and newer use MariaDB. For previous versions, MySQL is used.l For versions prior to 5.6, substitute MySQL for MariaDB.

INSTALLATION PATH

All SRM Profiler binary and data files are located under the installation directory. When installing, select adirectory located on a partition with enough space (at least 40 GB) to accommodate the SRM Profilerdatabase over time.

SolarWinds SRM Profiler cannot be installed on the same server as SolarWinds VirtualizationManager.

WINDOWS CLEAN INSTALL

After downloading the product from the SolarWinds website:

1. Navigate to your downloaded .zip file, and extract the package to an appropriate location.2. Launch the SolarWinds SRM Profiler server executable.3. Review the Welcome text, and click Next.4. Select setup type.

Express Install is recommended for Evaluations.

5. Accept the terms of the license agreement, and click Next.l License: The built-in 30 day evaluation license will be used during install. After installing youcan enter your activation key.

l Path: The default install path is: C:\Program Files\SolarWinds\SRM ProfilerServer\

l Database Password: The default password is "solarwinds".

SRM Profiler Server installs these services:


page 29

l MariaDB: the database for all data collected by SRM Profiler.

SRM Profiler versions 5.6 and newer use MariaDB. For previous versions, MySQL is used.For versions prior to 5.6, substitute MySQL for MariaDB

l SolarWinds SRM Profiler Collector: collects data from agents.l SolarWinds SRM Profiler Event Receiver: receives traps.l SolarWinds SRM Profiler Maintenance: runs maintenance routines in the background.l SolarWinds SRM Profiler Poller: remotely polls devices or applications by a variety ofmethods.

l SolarWinds SRM Profiler Web Services: the tomcat web server.6. Click Finish to exit the Setup Wizard.7. Click the SRM Profiler icon on your desktop or point your web browser at http://localhost:9000. You

should see a Login Screen.

The default Web Server Port can be changed in the server.xml file in the configurationfolder C:\Program Files\SolarWinds\SRM Profiler Server\conf. After changing,you need to restart the Tomcat web service.

8. Log in with the user name Admin and no password:9. To complete the server installation, enter your product activation key that was previously copied on

the License page, or continue running the product under the 30 day evaluation mode.10. Next step: Installing SRM Profiler agents on the devices you want to monitor.

UNINSTALL SRM PROFILER

Use the Add or Remove Programs for Windows Server 2003 R2 or Programs and Features for WindowsServer 2008 R1/R2 and Windows Server 2012 R1/R2 to remove SRM Profiler.

INSTALL SRMPROFILER SERVER ON LINUXPre-Installation requirements and notes:

l 32-bit agent/server should only be installed on 32-bit Linux systems. 64-bit agent/server shouldonly be installed on 64-bit Linux systems.

l Linux (x86-64) operating system supported versions: RedHat, CentOS, SUSEl SRM Profiler does not support installations on an OS with existing installations of a SRM Profilerdatabase.

l Before installing SRM Profiler, rename or delete my.cnf. This file is generally found in the path,/etc/my.cnf.

l SRM Profiler versions 5.6 and newer use MariaDB. For previous versions, MySQL is used. Forversions prior to 5.6, substitute MySQL for MariaDB

page 30

l Before installing SRM Profiler, verify there are no current instances of mariadb running on theserver. If there are, you must uninstall it before installing SRM Profiler. You must also rename ordelete my.cnf if present before installing SRM Profiler. This file is generally found in the path,/etc/my.cnf.

INSTALL ON A LINUX SERVER

1. Log in as root.2. Execute the install binary:

# ./Storage_Manager_Agent-linux-x86_64.bin

3. Installation might take several minutes. You are prompted for the following information:l Destination Path: The path where you want to install the agent. A directory will be createdunderneath this path if it does not already exist.

l Agent Port: Correlates to the web services port that is used by the server to communicatewith the agent. The default port '4319' is recommended.

l Server Trap Port: Also related to the agent setup, the 'Server Trap Port' must be set to the portlistening on the server for incoming trap events. The default port '162' is recommended.

l SRM Profiler Database password: The password needed to access the SRM Profiler database.It is important to write it down and keep it in a safe place. This password is used by the SRMProfiler services to access the SRM Profiler database. This is NOT the password used to log into the GUI.

4. To start the server, execute the following: #/usr/bin/storage_manager_server start

STOP THE SERVER

#/usr/bin/storage_manager_server stop

UNINSTALL SRM PROFILER ON LINUX

1. Log in as root.2. Go to install path: # cd /opt/Storage_Manager_Server

3. Execute the Uninstall folder: # ./uninstall -mode silentThis command uninstalls the SRM Profiler server.

DOWNLOAD THE INSTALLER AND ACTIVATION KEYTo download the SRM Profiler installer, you will need your SolarWinds ID (SWID) and password to login intothe customer portal.

1. Log in to the customer portal:http://www.solarwinds.com/customerportal/

2. Enter your email address and password, and click Log In.


page 31

http://www.solarwinds.com/customerportal/

3. Under Downloads select the SRM Profiler server installer appropriate for your OS, and clickDownload.

4. Click View All to list all available activation keys.5. Copy the string of characters under Activation Key to the clipboard.

Before exiting the customer portal, download any Agent installers that are relevant to yourdeployment if needed.

LICENSE SRMPROFILERThis section explains how to apply your license in the following scenarios:

l SRM Profiler onlyl Share the license between SRM Profiler and SRM

SRM PROFILER ONLY

Once you have obtained your license from your customer portal:

page 32

1. Log into the SRM Profiler web console.2. Click Settings > License Manager.3. Click Enter Activation Key, and paste the string you copied from the customer portal.

l If the SRM Profiler server has internet access, the key will activate.l If your server does not have internet access, there is a manual process to complete. Followthe onscreen instructions for offline activation.

SHARE THE LICENSE BETWEEN SRM PROFILER AND SRM

SRM Profiler can be integrated to run with SRM. When integrated, both products share the same licenseand users can see the functionality of both the SRM and SRM Profiler. For more information, see KeyScenarios when SRM Profiler and SRM are integrated.

If your license is currently applied to SRM and you wish to use the two products (SRM and SRMProfiler) integrated with a single license, you must first reclaim the license from SRM, and thenapply it to SRM Profiler. For more information, see "Reclaiming your License from SRM."

For more information on sharing your license between SRM and SRM Profiler, see Integrate SRM and SRMProfiler.

After the install has completed, you can license your installed product provided you have a SRM licenseavailable in your customer portal. If you are installing for the first time and decide not to license yourproduct, it will run in evaluation mode for 30 days. If you do not apply your license immediately afterinstallation, the following topics explain how to add your license later.

Install SRM Profiler agentsThe SRM Profiler Server works with SRM Profiler Agents and SRM Profiler Proxy Agents. Depending onhow many devices SRM Profiler is monitoring, SRM Profiler agents can help improve overall performancewith SRM Profiler through load balancing across multiple servers.


page 33

You can download agents for multiple platforms and quickly install them. After installation, they self-register with the SRM Profiler server and automatically start monitoring the server on which they areinstalled.

Before installing an agent, edit the Default Policy for Operating Systems on the server, as thesesettings are pushed out to the agent when it self-registers.

The self-registration process will create an OS Resource on the SRM Profiler server. Resources can also bedefined manually.

If there is a firewall between your SRM Profiler agent and your SRM Profiler server, you must openPort 4319 so the agent can send data back to the server.

INSTALL AN AGENTONWINDOWS

To install an agent on Windows 2008 Cluster, see Install an agent on Windows 2008 Cluster.

1. Execute the install file, typically Storage_Manager_Agent-Windows-xxx-nnn.exe (where xxx isthe architecture and nnn the version).

2. You are prompted for the install directory. Accept the default (recommended) or select a differentone.

3. Accept the license agreement.4. You are prompted for the following (fresh install only):

l Server Address: Type the IP Address of the server where the SRM Profiler server is runningl Server Trap Port: Type the port the SRM Profiler server is listening for incoming traps. Thedefault port, 162, is recommended.

l Agent Web Port: Type the port to be used for communication between the server and theagent. The default port, 4319, is recommended.

If you plan to use the SRM Profiler agent as a proxy for NAS (Network Attached Storage) file analysis,you must manually configure the login account of the Agent service. Use an account with the rightprivileges to view/read the NAS shares. If you are upgrading and have configured the loginpreviously, you must configure the login again after the install.

5. Leave the Start Services for SRM Profiler agent checkbox activated, if you want to start the agentservice immediately. If you choose not to start the service, then you must manually start it later.

6. For a fresh install, the agent should self-register and self-configure on the SRM Profiler server7. Configure your agent from the SRM Profiler server's console by clicking on the Device Configuration

icon, which leads you to the configuration page for that resource.

INSTALLING AN AGENTONWINDOWS CLUSTERThe following steps detail the installation of SRM Profiler agents onto a Windows Cluster.

page 34

https://support.solarwinds.com/Success_Center/Storage_Manager_(STM)/Storage_Manager_and_Storage_Resource_Monitor_Profiler_Agent_download_links

1. Log in remotely to the Active node of the cluster as Local Administrator.2. Execute the installer.3. Enter the destination path where you want to install the agent, select the location on the shared

drive, and then enter the Server IP Address of the SRM Profiler server.4. Leave remaining options set to default.5. Do not start the agent. Click No when prompted.6. After the agent is installed on this node in the cluster, failover to the other node and repeat the

steps above.

When prompted, select the same destination path previously selected.

To create a new cluster device:

1. Remotely log in to the server with the virtual IP Address.2. Click Start > All Programs > Administrative Tools > Failover Cluster Manager.3. Right-click on Services and Applications > More Actions > Create Empty Service or Application.4. Right-click Create Empty Service or Application > Properties. Give a proper name, and then save it.5. Right-click on the service, and select Take this service or Application Offline from the menu.

6. Right-click the offline Server, and then select Add a Device > Generic Service.


page 35

7. Select SolarWinds SRM Profiler agent Service from the list, and then click Next.

8. Click Finish.9. Right-click and select Bring the service or application online.

10. Log in to SRM Profiler web console, and click Settings > All Devices > Choose Type > OS Windows >Add.

page 36

11. Enter the Virtual IP Address of the cluster and provide a Display Name.

12. Click Next, and then Save.

INSTALL AN AGENTON LINUXCheck the Agent Requirements before you begin.

The agent install does NOT require a reboot.

In case of RHEL 5/OEL 5 install, certain libXP packages are not installed along with the default RPMPackages. These are needed for SRM Profiler to work correctly on Linux. Hence they must beinstalled manually. Packages details: libXp-1.0.0-8.1.e15 and libXp-devel-1.0.0-8.1.e15 (Thesepackages are available on the RH5 distribution DVD).

32bit agents should only be installed on 32bit Linux systems and 64bit agent should only beinstalled on 64bit Linux systems.



Installation may take several minutes. You are prompted for the following:

l Destination Path: The path where you want to install the agent. A directory is createdunderneath this path if it does not already exist.

l Server IP Address: The IP address of the device running the SRM Profiler server.l Agent port: The agent server port to use.


page 37

l Web Services Port: The 'Web Services Port' correlates to the web services port that is used bythe server to communicate with the agent. The default port '4319' is recommended.

l Trap Destination Port: The 'Trap Destination Port' must be set to the port listening on theserver for incoming trap events. The default port '162' is recommended.

3. To start the agent, execute the following:

#/usr/bin/storage_manager_agent start

To stop the agent: #/usr/bin/storage_manager_agent stop

UNINSTALL THE LINUX AGENT

1. Log in as root.2. Go to install path: # cd /opt/ Storage_Manager_Agent

3. Execute the Uninstall folder: # ./uninstall -mode silentThis command uninstalls the SRM Profiler agent.

CONFIGURE AN AGENTIn most cases, an agent self-registers with the SRM Profiler server as a device. However, you can alsodefine OS Policies manually. This allows you to push the configuration parameters out to your devices asconfigured in the policy.

CHANGE THE DEFAULT OS POLICY

1. Click Settings > Policies > Default OS Policy.

2. Complete or change the following info:

page 38

3. Server IP Address: The Server IP Address of the server where the agent resides. This setting is notconfigurable after the agent is created.

4. Device Display Name: The name you want to display for this device throughout SRM Profiler.5. HTTP Port : The port used by SRM Profiler to collect data from the agent (default 4319). If you

change this setting, SRM Profiler immediately tries to connect to this agent and update itsconfiguration. If SRM Profiler is unsuccessful, then it aborts the changes. Otherwise, you might losecommunication with the agent.

6. Active: The active agent. Uncheck this box if you want SRM Profiler to stop collecting data from theagent. Even though you make a Device inactive, the agent continues to run and you still receivetraps and are able to configure the agent.

7. Device Groups: A device may be assigned to zero, one, or multiple groups. If you have any definedgroups, the names of those groups appear in the Available field:

l To assign a device to a group, click the group name in the Available field. The selected groupname is automatically moved to the Selected field.

l To remove a device from a group, click the group name in the Selected field and it moves tothe Available field.

If you save the device definition without assigning it to a group, then the device willappear as Unassigned in the Devices List.

l Monitor Agent: Select this box if you want the server to monitor the agent and send a trap ifthe agent has not been collected from. The inactivity threshold can be configured on theserver setup page.

8. To save this device definition, click Save.

TURNOFF PERFORMANCE REPORTING

If you do not need Performance Reports for SRM Profiler agents, and are trying to limit the load on the SRMProfiler server, you can turn off Performance Reporting for SRM Profiler agents.

1. From the Web Console, navigate to Settings.2. Under Device Management, click Policies.3. Click the Default OS Policy Edit icon.4. Click the Performance link.5. Choose Off for all Stats, check Override Agent Values, and click then Save.6. Click Push on the Edit Default OS Policy page.

Agents are included in the Default OS Policy. Repeat steps 3-5 for each OS Policy with agentsincluded in the policy. It might take a few minutes for the policy revisions to get pushed out to allagents. Check that the agent performance reports are empty to assure the configuration is pushedto all agents.


page 39

TURNOFF REAL TIME STATUS

If you do not need Real Time Status for SRM Profiler agents and you are trying to limit the load on the SRMProfiler server, follow these steps to turn off Real Time Status for SRM Profiler agents.

1. From the Web Console, navigate to Settings.2. Under Device Management, click Policies.3. Click the Default OS Policy Edit icon.4. Click the Real Time Status link.5. In the Enabled menu, select Off, check Override Agent Values, and then click Save.6. Click Push on the Edit Default OS Policy page.

The Server Status in the Server Monitor and Device Console tab shows a warning:

MANUALLY UPGRADE JAVA (JRE) V1.8 FOR THE SRMPROFILERAGENT

Upgrading JRE on the server will make the web console inaccessible.

1. Go the Java website and download the latest Java version.

For Windows, it is recommended to download the Java installer in the SRM Profiler installedmachine because the Java website automatically detects and downloads the respective version tothe current Windows bit. For other operating systems, refer to the download list in the Java websiteto select the file according to your preference.

2. Install the latest Java version.3. Stop SolarWinds SRM Profiler Service.4. Go to the location where the SRM Profiler agent is installed and backup the jre folder.

The default location is as follows:Windows: c:\Program Files\SolarWinds\SRM Profiler AgentLinux: /opt/Storage_Manager_Agent

page 40

5. Delete all the files in the <location of the installed SRM Profiler agent>/jre folder.6. Go to the <location of the Java installed>/jreX and copy all the files.7. Paste all the copied files to <location of the installed SRM Profiler agent>/jre.8. Start SolarWinds SRM Profiler Service.

The SRM Profiler agent should start without any errors.

Integrate SRM and SRM ProfilerThe following prerequisites must be met before product integration can happen:

l If your license has been applied to SRM, you must reclaim it and apply it to the SRM Profiler installbefore integrating the two products. For more information, see Reclaiming your License from SRM.When the two products are integrated, SRM Profiler is responsible for maintaining the sharedlicense.

l The SRM Profiler Integration Module for Orion is an integration module specific to earlier releasesof SRM Profiler.

Installing the SRM Profiler integration module for Orion after SRM and SRM Profiler areintegrated will cause the appearance of two storage tabs on the Orion web page. The two tabswill have different content one being for SRM and the other for SRM Profiler.

l If you are running the SRM Profiler integration module for Orion prior to integrating SRM Profilerand SRM, we recommend you first uninstall the SRM Profiler integration module for Orion beforeintegrating SRM and SRM Profiler. It is also recommend that you do not install the SRM ProfilerIntegration Module for Orion once SRM and SRM Profiler are integrated.

This section explains the following tasks:

l Enabling integration between SRM and SRM Profilerl Disabling integration between SRM and SRM Profilerl Verifying your license count with SRM Profilerl Verifying your license count with SRMl Authentication between SRM and SRM Profilerl Key Scenarios when SRM Profiler and SRM are integrated

RECLAIM YOUR LICENSEThis section explains the tasks of reclaiming your license from SRM. This task is useful if you want to dothe following:

l Run SRM Profiler onlyl Run SRM Profiler and SRM Orion Module with a single license (integrated)


page 41

http://www.solarwinds.com/documentation/storage/storagemanager/STM_OrionNPMIntegration.htm

If you choose to integrate SRM Profiler with SRM, the license must be shared between the two applicationsand the license must be applied to SRM Profiler. If the license is currently applied to SRM, you must usethis procedure to reclaim the license before applying it to SRM Profiler.

The following task explain how to reclaim your license:

RECLAIMING YOUR LICENSE FROM SRM

To reclaim your license from SRM using the license manager:

1. Click Start > All Programs > SolarWinds > SolarWinds License Manager.2. Check the products you want to deactivate on this computer, and then click Deactivate.3. Specify your SolarWinds Customer ID and password when prompted, and then click Deactivate.

RECLAIMING YOUR LICENSE FROM SRM VIA SRM PROFILER

1. Click SETTINGS > License Manager > Reclaim Licenses to open the Reclaim License pop-up window.

l If you are sure that you want to proceed with reclaiming your SRM Orion Module license, click Yes.l If you want to back out of the task of reclaiming your SRM Orion Module license, click No.

2. Click Reclaim, if you agree to the conditions associated with reclaiming SRM license. If you disagree,click Cancel. For more information on what happens when you reclaim your licenses from SRM, seeDisabling Integration between SRM and SRM Profiler.

3. Click Finish.

page 42

Your reclaimed license is available in your customer portal and ready for activation. For more informationon licensing SRM, see Licensing SRM. For more information on licensing SRM Profiler, see Licensing SRMProfiler.

ENABLE INTEGRATION BETWEEN SRMAND SRMPROFILERThe following tasks integrate SRM and SRM Profiler:

1. Log into the Orion web console and click Settings > SRM Settings > Manage SRM Profiler Module.This opens the setup web page for SRM integration.

2. Provide the following information for SRM Profiler integration website:

SERVER NAME OR IPADDRESS

LOCATION OF SRM PROFILER (SRM PROFILER) SERVER

Port assignment The default port is 8443

User Name A valid username or account of the server you wish tointegrate

Password A valid password of the server you wish to integrate

3. Perform the following tasks:a. Click Test Connection to verify your settings.b. Click Submit if the results from clicking Test Connection are successful. If the test fails, verify

your credentials and connectivity to SRM Profiler server.

DISABLE INTEGRATION BETWEEN SRMAND SRMPROFILERYou can disable integration between SRM and SRM Profiler. If integration is disabled between SRM andSRM Profiler the following happens:

l SRM Profiler remains licensed and polling continues for storage devices assigned to it.l If the 30 day evaluation period has not expired for SRM, polling continues for devices assigned to it.l If the 30 day evaluation period has expired for SRM, polling stops for devices assigned to it.

Use the following steps to disable integration between SRM and SRM Profiler:

1. Log into the Orion web console.2. Click Settings > SRM Settings > Manage SRM Profiler Integration. This opens the setup website for

SRM Profiler integration.3. Click Disable Integration on the Setup SRM Profiler Integration website.


page 43

VERIFYING YOUR LICENSE COUNTWITH SRMPROFILERTo view your licensing information in SRM Profiler, log into SRM Profiler web console and click Settings >License Manager. This opens a window showing your license count summary.

RUN SRM PROFILER ONLY

The following information is displayed:

l SRM Profiler version and maximum number of disks that can be monitored with your licensel License Key - The key used to activate your licensel License Size – Number of disks being monitored and the maximum number of disks that can bemonitored

l Maintenance Expiration – Date your maintenance expires

RUN SRM PROFILER AND SRM WITH A SINGLE LICENSE (INTEGRATED)


l SRM Profiler version and maximum number of disks that can be monitored with your licensel License Key - The key used to activate your licensel License Size – Number of disks monitored and the maximum number of disks that can bemonitored

l SRM Profiler Module – Total number of disks monitored in SRM Profilerl SRM Orion Module – Total number of disks monitored in SRMl Shared – Total number of disks monitored in both SRM and SRM Profilerl Available – Remaining number of disks that can be monitored with your licensel Maintenance Expiration – Date your maintenance expires

VERIFY YOUR LICENSE COUNTWITH SRMTo view licensing information in SRM, log into SRM web console and click Settings > Licensing Details.

RUN SRM ONLY

THE FOLLOWING INFORMATION IS DISPLAYED:

Version Current version number of the installed module

Service Pack Any service pack applied will be listed here

License Info Informing whether the license is a production or evaluation

Allowed Number of Disks Maximum number of disks that can be monitored with your license

Total Number of Disks Sum of the total disks monitored

page 44


Licensed Number Disks Number of licensed disks being monitored

Unlicensed Number ofDisks

Number of disks that have exceeded the license count and are not beingmonitored

Available Number ofDisks

Remaining number of disks that can be monitored with your license

RUN SRM AND SRM PROFILER MODULE WITH A SINGLE LICENSE (INTEGRATED)


Version Current version number of the installed module

Service Pack Any service pack applied will be listed here

License Info Informing whether the license is a production or evaluation

Allowed Number of Disks Maximum number of disks that can be monitored with your license

Total Number of Disks Sum of the total disks monitored

Licensed Number of SRM Disks Number of licensed disks being monitored by SRM

Licensed Number of SRMProfiler Disks

Number of licensed disks being monitored by SRM Profiler

Licensed Number of SharedDisks

Number of disks being monitored in SRM and SRM Profiler using theshared license

Unlicensed Number of Disks Number of disks that have exceeded the license count and are notbeing monitored

Available Number of Disks Remaining number of disks that can be monitored with your license

AUTHENTICATION BETWEEN SRMAND SRMPROFILERWhen SRM Profiler and SRM are integrated, SRM generates a hidden service account username andpassword and passes this information to SRM Profiler. SRM Profiler also generates a hidden serviceaccount username and password passing this to SRM. Once integration is complete, all requests to SRMand SRM Profiler are authenticated based on the service account information. Information transferredbetween SRM and SRM Profiler is encrypted and passed via HTTPS over TCP port 8443.

You can change the default port of 8443 to a different port


page 45

When integrated, SRM Profiler is the primary owner for holding license keys and is responsible forhandling any license related queries.

When integrated, the products will try to sync every 5 minutes. The following describes what happenswhen SRM and SRM Profiler cannot sync.

When SRM Profiler goes offline, the following happens:

l SRM continues connection attempts to SRM Profiler until connectivity is re establishedl SRM will not add any arrays when SRM Profiler is unreachablel If SRM Profiler is unreachable for more than 24 hours, SRM will mark all arrays as unlicensed andpolling will stop

When SRM goes offline the following happens:

l SRM Profiler continues workingl SRM Profiler will use the last retrieved license validation from SRM for 30 daysl After 30 days the last retrieved license validation from SRM is discarded and SRM Profiler reclaimsthe licenses from SRM and continues working

l SRM Profiler continues connection attempts to SRM until connectivity is re established. When SRMgoes offline, if desired, you can reclaim the licenses from SRM immediately. For more informationon reclaiming the license from SRM, see Reclaim your License.

KEY SCENARIOS WHEN SRMPROFILER AND SRMAREINTEGRATEDThis section discusses the possible scenarios for SRM Profiler and SRM when they are integrated.

SRMON STARTUP

SRM performs the following tasks on startup:

1. SRM retrieves licensing information from SRM Profiler. This information is kept in SRM licensecache.

2. SRM retrieves a list of licensed arrays for both SRM and SRM Profiler. This information is kept inSRM license cache.

The license cache is used by SRM to perform license checks when adding or removing arrays.

ADD AN ARRAY TO SRM

When an array is added to SRM, a check is performed to verify whether or not the array is being monitoredin SRM Profiler. This is done by a validation process to SRM license cache.

page 46

l If the array is licensed in SRM Profiler, then SRM adds the array to its inventory.l If the array is not licensed in SRM Profiler, a calculation is performed by SRM to verify whether ornot adding the array will exceed the total licensed disk count.

l If the total license disk count is not exceeded, SRM adds the array, updates the license cache forSRM and sends notification to SRM Profiler about the inventory change.

l If the total license disk count is exceeded, the user will receive a warning message and the array willnot be added.

ADD AN ARRAY TO SRM PROFILER

When an array is added to SRM Profiler, a check is performed to verify whether or not the array is beingmonitored in SRM. This is done by a validation process to SRM Profiler license cache.

l If the array is licensed in SRM, then SRM Profiler adds the array to its inventory.l If the array is not licensed in SRM, a calculation is performed by SRM Profiler to verify whether ornot adding the array will exceed the total licensed disk count.

l If the total license disk count is not exceeded, SRM Profiler adds the array, updates the licensecache for SRM Profiler and sends notification to SRM about the inventory change.

l If the total license disk count is exceeded, the user will receive a warning message and the array willnot be added.

INTEGRATE ORION NPMWITH SRMPROFILERIntegrating SRM Profiler with Orion NPM allows you to have the SRM Profiler and the Orion NetworkPerformance Monitor integrated on one browser tab rather using having to multiple browser tabs.

The SRM Profiler Installer package includes an integration module that can be installed on your Orion NPMserver. This light integration provides a Storage tab in your NPM web console that provides a quick view ofyour storage metrics.

This installation requires Orion core 2012.2.2 or later.

INSTALL THE SRM PROFILER /ORION NPM INTEGRATION PIECE

1. Locate the integration module installer (OrionIntegrationModuleforStorgaeManager.msi)that is included in the product download. Copy it to the Orion server (Core 2012.2.2 and later) andexecute it.


page 47

2. Go to NPM Settings > SRM Profiler Settings and enter the IP address and login credentials you wantto use.

On some browsers, if you click Test, it erases the password. If you are using HTTPS the Testbutton reports an error.

3. Click on the storage tab to see the SRM Profiler main console.

When SRM Profiler is configured to use LDAP authentication, then the domain is assumed by SRM Profilerbased on those settings. Therefore, when you configure the Orion SRM Profiler Settings, they should notspecify the domain when filling in the Login Name field.

If you have configured LDAP authentication in SRM Profiler and configured a domain of foodev, they willnot include this in the SRM Profiler settings page. For example, instead of foodev\john.doe, just usejohn.doe.

The user can also configure the credentials for the admin user, as that user will be authenticated againstthe local SRM Profiler user database, not LDAP, regardless of whether or not LDAP authentication isenabled.

INTEGRATE VIRTUALIZATION MANAGERIf you have SolarWinds Virtualization Manager, you can link data stores on the details page to open in theircorresponding VMan web pages. For more information see the Virtualization Manager AdministrationGuide.


BACK UP AND SCAN THE SRM PROFILER DATABASE

Using external software to scan or backup the SRM Profiler database is not recommended. Use the dbutiltool provided by the SRM Profiler team to backup and maintain the SRM Profiler database.

Upgrade SRM ProfilerThe following topics provide information for upgrading SRM Profiler:

page 48

https://support.solarwinds.com/Success_Center/Virtualization_Manager_(VMAN)/VMAN_Administrator_Guide

https://support.solarwinds.com/Success_Center/Virtualization_Manager_(VMAN)/VMAN_Administrator_Guide

l Upgrade to SRM Profiler 6.2 from 6.0 or earlierl Verify there is sufficient disk spacel Back up the SRM Profiler databasel Upgrade the SRM Profiler serverl Upgrade SRM Profiler server on Linuxl Upgrade your licensel Upgrade SRM Profiler agents

VERIFY THERE IS SUFFICIENT DISK SPACEVerify there is sufficient free disk space on the SRM Profiler server before upgrading. There must be TWICEas much free space as the largest table in your database.

SRM Profiler versions 5.6 and newer use MariaDB. For previous versions, MySQL is used. Forversions prior to 5.6, substitute MySQL for MariaDB

The database can be found at the following location:

l Windows: <installed drive>\Program Files\SolarWinds\SRM Profiler

Server\mariadb\data\storage directoryl Linux: <installed path>/Storage_Manager_Server/mariadb/data/storage directory

This is the default location of where the temporary database tables are created.

Sort the files within the database subdirectory making note of the largest table (*.MYD) in the folder andremember there must be TWICE as much free space as the largest table in your database. SRM Profilerbuilds temporary database tables from the actual database. If you have insufficient disk space you mustpoint the temporary database tables to a drive that has sufficient disk space.

To change the location of where the temporary database tables are stored, go to the following location:

l Windows: <installed drive>:\Program Files\SolarWinds\SRM ProfilerServer\mariadb

l Linux: <installed path>/Storage_Manager_Server/mariadb

Using a text editor open the file called my.cnf. After the file is open, search for the string #tmpdir=.Remove the # (comment) and change it to a drive that has sufficient space.

Example: Changing to E:\ drive will look like tmpdir=E:\

Save the file and restart the mariadb service.

l Windows: Restart the mariadb service via services.mscl Linux: Run the command /etc/init.d/storage_manager_server restart database


page 49

BACK UP YOUR SRMPROFILER DATABASESolarWinds recommends backing up your SRM Profiler database before running the SRM Profiler installer.See Back up the SRM Profiler requirements in the Appendices.

SRM Profiler versions 5.6 and newer use MariaDB. For previous versions, MySQL is used. Forversions prior to 5.6, substitute MySQL for MariaDB

The time it takes to complete the upgrade depends on the size of the database. Large database cantake more than 6 hours.

UPGRADE THE SRMPROFILER SERVERThe SRM Profiler installer upgrades your current SRM Profiler server in place. Simply execute the installeron the SRM Profiler server, and it will find the current installation and migrate the configuration andhistory into the upgrade.

SolarWinds recommends that you back up the SRM Profiler database before upgrading.

1. Start the MariaDB service before running the installer.2. Close all folders before running the installer.3. Run the installer.4. Upgrade SRM Profiler agents after the SRM Profiler server is upgraded.

The time it takes to complete the upgrade depends on the size of the database. Large databasesizes can take more than 6 hours.

UPGRADE THE SRMPROFILER SERVER ON LINUX


# ./Storage_Manager_Server-linux-x86_64.bin

3. Installation may take several minutes. You are prompted for the following information:l Destination Path: The path where you want to install the agent. A directory will be createdunderneath this path if it does not already exist.

l Agent Port: Correlates to the web services port that is used by the server to communicatewith the agent. The default port '4319' is recommended.

l Server Trap Port: Also related to the agent setup, the 'Server Trap Port' must be set to the portlistening on the server for incoming trap events. The default port '162' is recommended.

page 50

l SRM Profiler database Password: The password needed to access the SRM Profiler database.It is important to write it down and keep it in a safe place. This password is used by the SRMProfiler services to access the SRM Profiler database. It is NOT the password used to login tothe GUI.

4. To start the server, execute the following command:

#/usr/bin/storage_manager_server start

5. To stop the server, execute the following command:

#/usr/bin/storage_manager_server stop

UPGRADE YOUR LICENSELicense SRM Profiler by navigating to Settings > License Manager on the SRM Profiler web console.

Your license activation key is available on your customer portal:

http://www.solarwinds.com/customerportal/licensemanagement.aspx

VERIFICATION OF SOFTWARE VERSIONTo display the version of SRM Profiler currently installed, navigate to Settings > SRM Profiler server > Abouton the web console.


l Serverl Database Versionl Tomcat Versionl MariaDB Versionl Patch Historyl Versionl Applied


page 51

http://www.solarwinds.com/customerportal/licensemanagement.aspx

UPGRADE SRMPROFILER AGENTSSolarWinds recommends that you upgrade agents from the web console to avoid data loss.

UPGRADE AGENTS FROM THEWEB CONSOLE

After upgrading SRM Profiler, you must update the agents.

1. From the web console, navigate to Settings > Upgrade Agents.2. Set a name for the upgrade.3. Select all modules.4. Select all agents.5. Click Save.

UPGRADE AGENTSMANUALLY

Agent Upgrades can also be performed manually by executing the Agent build for that version on theAgent side.

UPGRADE AGENTS ON LINUX



3. Installation may take several minutes. You will be prompted for the following:l Destination Path: The path where you want to install the agent. A directory will be createdunderneath this path if it does not already exist.

l Server IP Address: The IP address of the device running the SRM Profiler serverl Agent port: The agent server port to use.

4. To start the agent, execute the following command:

#/usr/bin/storage_manager_agent start

5. To stop the agent, execute the following command:

#/usr/bin/storage_manager_agent stop

UPGRADE TO SRMPROFILER 6.2 FROM 6.0 OR EARLIERIf you are running a version of SRM Profiler prior to release 6.0 that is licensed with a Storage Profiler orBackup Profiler license, you must first deactivate your license before upgrading to SRM Profiler 6.2 or later.

page 52

If you wish to upgrade to SRM Profiler 6.2 and still use Backup Profiler, SolarWinds recommendsthat you clone or migrate your current Backup Profiler install to a different server. Once BackupProfiler is on a different server, proceed to deactivate the Backup Profiler license on the originalserver and then upgrade to SRM Profiler 6.2.

If you are running SRM Profiler with a Backup Profiler Evaluation license, contact SolarWindssupport for assistance before upgrading.

If you try to upgrade SRM Profiler when it is licensed with a Storage Profiler or Backup Profiler license, youwill receive the following error.

To deactivate your license go to Settings > License Manager and click the Deactivate link.

Once your license is deactivated, it will be in evaluation mode. Proceed with your upgrade to SRM Profiler6.2 and follow the steps in License SRM Profiler to license SRM Profiler 6.2.


page 53

Administerl Deploy SRM Profilerl The Getting Started pagel The Health Status Overview pagel Manage use accountsl SRM Profiler settingsl SRM Profiler databasel Advanced configurationl Use reports and schedulesl Use groupsl Use rulesl Use policies and set alerts

Deploy SRM ProfilerThis section covers small, medium, and large environments, and minimum recommendations for serverhardware and memory for SRM Profiler services.

l Minimum recommendations for small, medium, and large environmentsl SRM Profiler proxy agent deploymentl Number of SRM Profiler agents and proxy agents per SRM Profiler serverl Sample deploymentl File analysis

MINIMUMRECOMMENDATIONS FOR SMALL, MEDIUM AND LARGEENVIRONMENTSThis chart shows the minimal hardware and memory requirements for SRM Profiler server and Servicesbased on your environment size.

ENVIRONMENT SIZE

Resource Monitored Small Medium Large

Disks/LUNs Total Up to 500 Up to 3000 Greater than 3000

Physical Servers Up to 100 Up to 300 300 to 500

page 54

ENVIRONMENT SIZE

Virtual Machines 100 500 1000 +

Fibre Channel Switches 10 20 30

Minimum Recommendations for Server Hardware

Environment Size Small Medium Large

Operating System Windows or Linux Windows or Linux Linux

Architecture x64 x64 x64

Server Platform Physical or Virtual Physical or Virtual Physical

CPU 2 Cores 4 Cores 8 +Cores

Physical Memory 8GB 16 – 32GB 32 – 64GB

Free Disk Space 40GB 100-300GB 500GB

Proxy Agents Required No **Yes **Yes

Minimum Memory Recommendations for SRM Profiler Services

Environment Size Small Medium Large

Collector Service 1024MB (1 GB) 4096MB (4 GB) 8192MB (8 GB)

Event Receiver Service 1024MB (1 GB) 4096MB (4 GB) 4096MB (4 GB)

Maintenance Service 512MB 2048MB (2 GB) 4096MB (4 GB)

Poller Service 512MB 2048MB (2 GB) 4096MB (4 GB)

Web Service 1024MB (1 GB) 4096MB (4 GB) 8192MB (8 GB)

Database 2048MB (2 GB) 8192MB (8 GB) 8192MB (8 GB)

l SRM Profiler proxy agents are required for collecting information from external resources acrossmultiple servers thus reducing workload to the SRM Profiler server.

l Resources monitored should be interpreted as XX Virtual Machines and XX Fibre ChannelSwitches and XX Disk/LUNs before adding proxy agents. See Sample deployment.

l It is recommended that you perform maintenance on the SRM Profiler database using the dbutiltool. This tool will allow users to run maintenance routines keeping the database runningsmoothly and make backups of the database. For more information on using this tool see dbutil.


page 55

SRMPROFILER PROXY AGENT DEPLOYMENTThe following tables show the recommended server and resources for SRM Profiler proxy agents based onyour environment size.

MINIMUM RECOMMENDATIONS FOR AGENT HARDWARE

ENVIRONMENT SIZE SMALL MEDIUM LARGE

Server platform N/A Windows or Linux Linux

Architecture N/A x32 or x64 x64

CPU N/A 2 Cores 4 Cores

Physical memory N/A 4GB 8GB

Free disk space N/A 20GB 20GB

RECOMMENDED RESOURCES PER PROXY AGENT

ENVIRONMENT SIZE SMALL MEDIUM LARGE

Environment size Small Medium Large

Virtual Machines per proxy agent N/A x32 bit 200 VM 300 VM

x64 bit 300 VM

Fibre Channel switches per proxy agent N/A 10 10

Number of Disks/LUNs per proxy agent N/A 500 500

Resources Monitored should be interpreted as XX Virtual Machines and XX Fibre Channel Switches and XXDisk/LUNs before adding additional proxy agents. See Sample Deployment.

If you are running VMware VMotion, Storage VMotion or anything that can cause ESX host to dynamicallyswitch to another ESX server, be aware of how VMware distributes the load dynamically from one ESXserver to another. You should allow for additional room for the switch over. For example, if you arecurrently running 300 virtual machines on one proxy agent and a switchover occurs, this could allowmonitoring of 300 plus virtual machines on your SRM Profiler proxy agent.

SolarWinds recommends that you have no more than 500 Disk/LUNs PER SMI-S Provider. The SRMProfiler proxy agent works directly with the SMI-S Provider. For more information on SMI-S Providers,see SMI-S and for more information on the architecture behind monitoring SAN Arrays and SMI-SProviders see Architecture.

page 56

NUMBER OF SRMPROFILER AGENTS AND PROXY AGENTS PERSRMPROFILER SERVERThe maximum recommended number of SRM Profiler agents and Proxy Agents per SRM Profiler server is500. If you choose to go beyond 500 SRM Profiler agents then we recommend that you consider multipleSRM Profiler servers.

SAMPLE DEPLOYMENTThis example shows how to load balance external devices using SRM Profiler proxy agents.

The following diagram shows one way of assigning resources to proxy agents. Note the three proxy agentsat the bottom are monitoring both ESX servers and Fibre Channel switches. SRM Profiler agents arecomprised of modules. Each module is responsible for monitoring a different resource on the externaldevice being monitored. Because of this feature, we are able to monitor multiple functions from differentdevices via one agent.


page 57

The following table provides a breakdown of the devices being monitored in our example and the numberof agents needed to monitor those devices:

TYPE OF DEVICENUMBER OF

DEVICES

PROXY AGENT TO DEVICE

RATIO

NUMBER OF PROXY AGENTS

NEEDED

Symmetrix/VMAXArray

2 1:1 2

VNX/Clariion Array 12 1:5 3

NetApp Filers 24 1:10 3

Virtual Machines 600 1:300 3

Fibre ChannelSwitches

30 1:10 3

l All calculations are done using Linux x64 bit agents

Because SRM Profiler agents are capable of monitoring multiple resources from different devices, you cango a step further and optimize your setup by spreading the workload out even further, thus reducing thenumber of Proxy Agents needed.

Example: The table above can be divided out even further using the "Proxy Agent to Device Ratio" columnin the table above:

l Agent 1 – 2 ESX hosts with 200 Virtual Machines, 10 Fibre Channel Switches, 5 Clarrion/VNX arraysl Agent 2 – 2 ESX hosts with 200 Virtual Machines, 10 Fibre Channel Switches, 5 Clarrion/VNX arraysl Agent 3 – 2 ESX hosts with 200 Virtual Machines, 10 Fibre Channel Switches, 2 Clarrion/VNX arraysl Agent 4 – One Symmetrix/VMAX arrayl Agent 5 - One Symmetrix/VMAX arrayl Agent 6 – 8 NetApp Filersl Agent 7 – 8 NetApp Filersl Agent 8 – 8 NetApp Filers

If you are running VMware VMotion, Storage VMotion or anything that can cause ESX host todynamically switch to another ESX server http://www.virtualizationadmin.com/faq/vmware-vmotion-storage-vmotion-svmotion.html be aware of how VMware distributes the load dynamicallyfrom one ESX server to another. You should allow for additional room for the switch over. Forexample, if you are currently running 300 virtual machines on one proxy agent and a switchoveroccurs, this could allow monitoring of 300 plus virtual machines on your SRM Profiler proxy agent.

In summary, you can monitor all of the devices in this example with 8 Proxy Agents.

page 58

http://www.virtualizationadmin.com/faq/vmware-vmotion-storage-vmotion-svmotion.html

http://www.virtualizationadmin.com/faq/vmware-vmotion-storage-vmotion-svmotion.html

FILE ANALYSISIt is recommended NOT to use SRM Profiler server for File Analysis. You should instead use a SRM Profilerproxy agent. The proxy agent should be dedicated to running File Analysis and nothing else. This isbecause of heavy workloads that can be placed on the SRM Profiler proxy agent due to large file scans.

Determining how much File Analysis the SRM Profiler proxy agent can do is dependent on three things:

l The number of files being scanned.l The rate at which the SRM Profiler proxy agent can process them. It is best for you to run test inyour environment to determine your files per minute (Files/Min) rate. This result can be viewed inthe File Analysis Stats Report located in Quick Reports.

l The time window that you have to process the files. This is generally a few hours to overnight ifdaily, or weekend if weekly. Ideally, File Analysis should not run on a single target for more than 24hours.

The following formula will help determine if your current deployment of SRM Profiler can collect FileAnalysis in a timely manner.

Duration = Number of Files

--------------------------

Files/Min

If the duration is less than the time window, then you can do the File Analysis with one SRM Profiler proxyagent. If it is greater, you need to deploy another SRM Profiler proxy agent (and so on). For moreinformation on File Analysis see Setting Up File Analysis.

The Getting Started pageThe Getting Started page provides quick access to adding storage devices so you can get started with yourstorage monitoring.

l You can Explore each section of the SRM Profiler Web Console in Navigate the Web Console.l The Settings page provides documentation links to the settings you can configure in SRM Profiler.

THE GETTING STARTED PAGEThe Getting Started page is loaded when you first log into SRM Profiler. Use this page for quick access toadding and configuring the devices you want to monitor.

You can navigate to Getting Started with SRM Profiler from Home in the Left Navigation Pane.

Servers Add servers to be monitored by SRM Profiler. Follow the onscreen instructions foradding the OS agent.

Virtualization Add VC Instances and stand-alone VMware Hosts by following the onscreenconfiguration instructions. See Add VMware Monitoring for details on adding your


page 59

VMware to SRM Profiler.

Storage Arrays Use Add to select the type of storage array and follow the onscreen instructions. TheAdd Storage Arrays section provides details on adding and configuring your arrays inSRM Profiler.

FC Switches Select the type of fibre channel switches to add and follow the onscreen instructionsfor configuration. See the Add Fibre Channel Devices for more information andadding and configuring your Fibre Channel Switches in SRM Profiler.

Viewing Datafrom yourDevices andApplications

l Main Console - Summary of storage, servers and virtualization infrastructure.l Server Monitor - Health and status of all your servers, physical and virtual.l Virtualization Dashboard - Enterprise summary of the virtualizationinfrastructure.

Configurationl Server Setup - Configure system-wide settings, including e-mail server.l Devices - Manage all devices and applications.l Groups - Define groups of devices for reports and chargeback.l Rules - Set up thresholds and triggers on storage, performance and asset data.l Quick Reports - Configure, run and publish reports on demand and byschedule.

THE WEB CONSOLEThe SRM Profiler web console consists of a title bar, a help bar, left navigation pane, and a main view. TheSettings section provides links to documentation for commonly performed tasks.

When you log in to the web console for the first time, the Getting Started page is loaded in the main view,providing quick access to adding storage devices so you can get started with storage monitoring. The mainview changes as you navigate SRM Profiler.

Title Bar

The title bar contains the Profile link, the Log Out button, and the Settings button.

Profile

The profile link text describes the access level of the user and links to the user's profile page. The profilepage allows users to edit their profile and to add and edit email addresses

Log Out

page 60

Click Log Out to log out of the Storage Manage web console.

Settings

The Settings page provides links to the tasks you can perform in SRM Profiler. Documentation for thesetasks is available in the Settings section.

Help Bar

l Hide or Show the Left Navigation Pane with the Hide/Show Menu link.l Access the Thwack Storage User Community.l The Help link opens a new browser window and loads the SRM Profiler Administrator's Guide. Ingeneral, help topics relating to the Main View are accessed from the Help link.

l Use Search to find your devices using the IP address, Name, or OS of your device.

Left-Navigation Pane

The left-navigation pane provides easy access your SRM Profiler dashboards and reports.

Home

Links to Getting Started with SRM Profiler.

SRM PROFILER HEALTH STATUS

SRM Profiler (versions 5.7 and above) provides a web console consisting of a central place to view theoverall health and status of the SRM Profiler software. This includes the SRM Profiler server, SRM Profilerdatabase, and SRM Profiler proxy agents. For more information, see Health Status Overview.

MONITORS

l Main Console summarizes the storage, servers, and virtualization infrastructure you aremonitoring.

l Event Monitor summarizes the different events that are currently active.

SRM Profiler will show the trap values as a number for asset change conditions. For a description ofwhat those numerical values mean, see OperationalStatus.

l Server Monitor shows information on the servers you are monitoring. Click the Legend link fordetails about the symbols used to convey server status.

l SnapMirror Monitor shows the current transfer between the source and the destination for all thefilers in the group or a particular filer based on the filter selection.


page 61

REPORTS

Below are links to documentation for the types of reports in the Reports section of the Left-NavigationPane:

l My Reportsl Shared Reportsl Quick Reportsl Report Schedulesl Management Reportsl Enterprise Reports

SERVER AND NAS GROUPS

Server and NAS Groups includes information about Servers or Network Attached Storage devices you aremonitoring.

SAN GROUPS

l The San Groups aggregates information from both SAN devices and OS Devices that have filesystems assigned to a SAN device

l The SAN Storage Status is an overview of the OS device file systems that have been mapped to theSAN.

l The SAN File System Trends and Forecast are the trends and forecast for the file systems that havebeen assigned to that SAN group.

LUN GROUPS

User Defined Logical Unit Number (LUN) Grouping for NetApp, SMI-S, and SNMP enabled arrays. Users cangroup LUNs based on their own requirements. Once the LUNs are grouped users can view details aboutcapacity and performance for those LUN groups. For more information on grouping LUNs, see Chapter 10Using Groups.

The LUN Group Summary link provides the following information about all LUN groups:

l Usable Storage and RAW Storage.l Top 10 LUN Performance by Total IOPs, Latency, Read, and Write.

For customer created LUN groups, the following information is provided. This information is specific only tothe LUNS assigned to that group:

l LUN Group - Consolel Usable and RAW Storagel Top 10 LUN Performance by Total IOPs, Latency, Read, and Write

page 62

l LUN Group – Performancel Virtual Machine (VM) Disk Metrics per LUN - Shows performance metrics of VMs in a singleLUN. Users can select appropriate LUN from the Group and verify the VM Disk Performance

l LUN Metrics per VM - Shows performance metrics of the LUN for a single VM. Users canselect appropriate VM and verify LUN Performance

l LUN Performance - Displays performance for all of the LUNs assigned to the group.Comparisons can be made against other LUNS in the group

l LUN Performance Comparison – Shows LUN Performance and users can compare them withthe LUN's additional metrics

l LUN Group Summary – Provides summary information about the groupl LUN Group – Servers

l Allocated Volume Usage - Reports volume usage for servers and virtual machines that usestorage array LUNs belonging to user defined LUN groups. This report also provides volumeusage for servers and virtual machines with local storage and includes growth rates withforecast information.

l LUN Details - Explains the RAID group, associated disks, and information of each LUN for agiven LUN Group.

l ESX Logical Mapping – Shows the VMDK, VM, Datastore, and ESX Host of each LUN for a givenLUN Group.

l RDM Mapping - Showing RDM Mapping from VirtualDisk to Storage Array LUNs.l Logical Mapping - Shows the mapping of Server volumes and logical drives to an array LUN.

VIRTUALIZATION

Virtualization includes any VMware devices you are monitoring.

The Health Status Overview pageSRM Profiler (versions 5.7 and above) provides a web console consisting of a central place to view theoverall health and status of the SRM Profiler software. This includes the SRM Profiler server, SRM Profilerdatabase, and SRM Profiler proxy agents.

The Health Status page provides the following resources:

l Server Performance metricsl Servicesl Database statusl Device typesl Proxy agentsl Collection jobs queuel Help and support


page 63

SERVER PERFORMANCE METRICS

The Server Performance Metrics resource displays the health status of the server. The followinginformation is provided:

l CPU utilization – Amount of CPU resources being used.l Physical Memory (RAM) consumption – Amount of RAM being used.l Disk Usage – Disk space being consumed.l Collection List – Shows all agents that are waiting for collection.l An explanation of warnings that are generated.

When the CPU, Memory (RAM) or Disk Usage threshold reaches 70%, the indicator bar turns yellow,meaning warning, and when the threshold reaches 90%, it turns red, meaning critical.

If the server has less than 8GB of memory (RAM) a warning message is displayed.

SERVICES

The Services resource shows Java Heap memory consumption and Java Heap memory allocation of theservices excluding the database service.

Java Heap memory does not apply to the database, it only applies to the Maintenance, Web Server,Event Receiver, Collector, and Poller services. The database uses key buffer size as allocatedmemory while processed memory is considered used memory. User can learn more about allocatingphysical memory to the SRM Profiler services by clicking the Learn how to allocate physical memoryfor services link. Users can also learn more about allocating memory to the database by clicking theLearn how to allocate memory to the database link.

When a threshold reaches 70%, the indicator bar changes to yellow, meaning warning. When a thresholdreaches 90%, the indicator bar changes to red, meaning critical. If a service is stopped or in a stoppedstate, it is labeled as offline.

page 64

DATABASE STATUS

The Database status resource shows the current state of the SRM Profiler Database. This includes:

l The size of the database.l The largest table and the size.l The date of the last dbutil/index rebuild.

Database Status also provides the following information and help links:

l Show Process List - Shows all processes in the MariaDB database.l Show Crashed Tables - Shows a list of crashed tables if there are any.l Learn to maintain your database – Provides information about performing maintenance and fixingcrashed tables within the SRM Profiler database.

If there are any crashed tables in the database, a display message appears, notifying the user. Youcan then click the Show Crashed Tables link and view which tables are reporting as crashed.

DEVICE TYPES

The Device Types resource provides the status and type of devices being monitored by SRM Profiler:

l View Device Collection Status – Shows device collection status valuesl View All Devices – Shows a list all devices being monitored by SRM Profilerl Devices – The type of device being monitoredl Total – Total number of devices being monitored by SRM Profilerl Up – The number of devices responding to pollingl Down – The number of devices up at one time yet are not currently responding to pollingl Offline – The devices that have never been up and are not responding to polling


page 65

SRMPROFILER PROXY AGENTS

The SRM Profiler Proxy Agents resource displays the health status of the proxy agents that have devicesassigned to them. The following information is displayed:

l View all agents – Click to display a full list of proxy agents assigned to SRM Profiler.l Monitored Devices – The number of devices being monitored by the proxy agent.l Device – Name of the server hosting a SRM Profiler proxy agent and its current status.l CPU utilization – Amount of CPU resources being used by the proxy agent.l Physical Memory (RAM) consumption – Amount of RAM being used by the proxy agent.l Disk Usage – Amount of disk space being used by the proxy agent.l Forecast – Estimate of when the disk will run out of space on the server hosting the proxy agent.The user will be provided a percentage value along with how many days or a date approximation ofwhen the disk will run out of space.

When the CPU, RAM or Disk threshold reaches 70%, the indicator bar turns yellow, meaning warning, andwhen the threshold reaches 90%, it turns red, meaning critical.

COLLECTION JOBS QUEUE

The Collection Jobs Queue resource shows the last 10 devices that were either successful or failed whendata collection occurred with a proxy agent. The following information is displayed:

l Device – Device name.l Last Run – The last time SRM Profiler polled the device to retrieve information.l Last run duration - How long it took SRM Profiler to retrieve information from the device.l Frequency – How often SRM Profiler polls the device for information.l Job type – The information SRM Profiler requested from the device.

page 66

The Diagnose link within the Last 10 Failed Jobs provides users with additional information as towhy data collection could be failing.

HELP AND SUPPORTThe Help and Support resource provides links to:

l Video resourcesl thwack! storage communityl SRM Profiler help

Manage user accountsThe User account feature allows you to add, edit, and delete users from SRM Profiler. Users' privileges arecategorized into several levels, allowing administrators to create filtered views of information based on theuser's responsibilities. These filters are created according to groupings of managed devices. This functionallows administrators to assign users to the appropriate group or groups of monitored systems for whichthey are responsible.

l Add usersl Edit user profilesl Manage user email notificationsl Set up notifications

ADDING USERSTo perform the following you must be logged into SRM Profiler with an account that has Administrativeprivileges. The following steps detail how to add a user.

The Add User button will be missing when LDAP is enabled. To disable LDAP go to Settings > ServerSetup > User Authentication.

To add a new user:

1. Click Settings > Manage Users.2. Click Add New User, and then enter the name to be supplied at login, the name to be displayed on

the screen and the password to be used for this user.

The password must be at least one character long and is case sensitive. SRM Profiler requiresyou to retype the password in the Confirm Password field.

3. Check the Login box if you want this user to have Login privileges. Users with login privileges canaccess event screens as well as device inventory usage and performance reports for all devices intheir assigned groups.


page 67

http://www.solarwinds.com/resources/storage-manager/videos.aspx

http://thwack.solarwinds.com/community/cloud-virtualization-storage_tht

http://thwack.solarwinds.com/community/cloud-virtualization-storage_tht

4. Select a user type. This can be:l Root administratorl Read Only Administrator- User has read-access onlyl Group Administrator- User access is defined by the root administratorl User – User access is defined by the root administratorl User - Backup Monitor only

5. Select the areas of SRM Profiler to which this user should have access.6. Select the first screen to be displayed when this user logs in.7. Enter the user's email address.8. To indicate which device information the User is allowed to access, highlight the desired device

group(s) in the column entitled Available and click to move the desired group(s) to the selectedcolumn.For example, if only the NT Group was selected, then the user would only be able to access EventLists, Event Histories, Usage Reports and other information about Windows NT systems assigned tothe NT group.

9. Click Save.

LEVEL OF USER PRIVILEGES

LOGIN

Users with login privileges can access the SRM Profiler application, but the view of the SRM Profiler mainmenu will be filtered.

For example: Login users will not see the Administration portion of the menu that contains folders fordefining Groups, Devices, Server Setup and Users.

In addition, SRM Profiler allows you to select the type of data a user can see.

l Backup - Backup Servers and Clientsl Server and NAS - All DAS and NAS devicesl SAN - All SAN devices (Fibre Channel and EMC)l Application - Application devicesl Storage Group - Logical groupings of File systemsl Management Reports - Can run management reports

ADMINISTRATOR

Administrators can see all data about all devices in all groups. Administrators also have access to all SRMProfiler menus, screens, and reports, including the Administration menu. To grant administrator privilegesto a user, check the Administrator field and then click Add.

page 68

EDITING USER PROFILESTo edit a user:

1. Click Settings, and find Users in the lower left corner of the Settings website. Options to Add, editand remove user accounts are available here.

2. Click Manage Users.3. Click the Manage icon in the row for the user to manage. The User's Profile screen is displayed.4. Click Edit icon.

If you edit the password, SRM Profiler will require you to retype the password again in the ConfirmPassword field.

3. To change user privileges, check /uncheck the Login and/or Administrator boxes.

MANAGING USER EMAIL NOTIFICATIONSThe User Profile page allows you to enter email addresses and configure alert notifications for users.

1. To edit email addresses and/or notifications, return to the Profile page of the user to modify.2. To manager E-mail Address, click the Edit icon for settings already configured, or click Add to add a

new email account.3. To manager Notifications, click the Edit icon for settings already configured, or click Add to add a

new type of notification.

SETTING UP NOTIFICATIONSYou can set notification policies for users on either a device-by-device or group basis. For example, if amanager in a given department wants to be notified if a critical server is running out of disk space, butdoes not want to receive email about non-critical servers in that group, then you can specify a notificationpolicy for that server alone.

Specifying notification policies by groups can save time. For example, if there are multiple devices in agroup, a user can use a single command to specify notification destinations for all of those devicesconcurrently.

To create notification policies, click Edit on the Notifications section at the bottom of the User Profilescreen. A screen appears containing a drop-down menu field, allowing you to choose a type from thefollowing options:

l Devicesl Groups


page 69

Select either Devices (or Groups) to expand the screen, displing a drop-down menu that lists all of thedevices (or groups) for which the User has access privileges. Administrators will see all device devices (orgroups).

1. You can edit the email address of the user or add new email addresses. Multiple email addressesand aliases can be entered if necessary. Entered email addresses receive notifications from alldevices specified in the Notifications field.

2. To modify the list of devices that sends alert notifications to a user, click on the Edit icon in theNotifications frame.

3. Click the drop-down menu for Choose a Type to select either a group of devices or a specific deviceto be added to the notifications list.

4. Choose the severity of Notifications to be sent: critical, error, warning, information and debug. Formore information see "Alert Severity."

The event receiver is the service which is responsible for receiving alerts, traps events and sendingnotification to users via email.

The following covers the behavior of the event receiver:

l When an incoming trap is received, the event receiver checks to see if it already exist in thedatabase

l If the trap does not exist in the database, (new trap) the event receiver will send notification viaemail to the users assigned to the notification list.

l If the trap already exist, by default it will increment the counter for that trap and no notification issent. This prevents the user email account from being flooded with trap messages.

To be notified via email for each trap received:

1. Log into the SRM Profiler website and go to Settings > Server Setup:All > GUI2. and for the option "E-mail Notification for SNMP Alerts," change "First Occurrence only" to "Every

Occurrence." Finally, restart the SRM Profiler Event Receiver service to allow the changes to beregistered to SRM Profiler.

SRM Profiler SettingsThe Storage Settings page provides links to the tasks you can perform in SRM Profiler. To get to thesettings page, click the Settings icon in the upper right of the SRM Profiler website.

l Agents settingsl Array settingsl Database settingsl Email settingsl File Analysis settingsl GUI settings

page 70

l Real Time settingsl Reporter settingsl Server settingsl Trap Forwarding settingsl User Authentication settings (LDAP settings)l Virtualization settings

l Manage agent assignmentsl Enabling SSL login for the website

AGENTS SETTINGSThe Agent Settings define the behavior of the SRM Profiler server when it receives a registration trap froman agent trying to register. Enabling these allows you to receive real time alerts when an agent statuschanges from yellow to red or from green to yellow. This will send out a trap.

SETTING DESCRIPTION

Allow Self-Register Defines what SRM Profiler does when it receives a trap from an agentthat is not in the devices table. If set to true, SRM Profiler adds theagent to the device table, using the IP address as the device name.Default is yes.

Auto Assign OS License Determines if SRM Profiler automatically assigns an OS RTU Licensewhen it registers an agent. Default is yes.

Agent Inactivity Threshold Choose the threshold for agent inactivity. If there has been nocollection from an agent for the period specified, then an 'Agent notcollecting' trap is sent. This trap is only sent for the agents to which themonitor agent check box is selected in the edit page.

Agent Status Alert Sets Alert status to TRUE/FALSE. Any change made to this parametershould be followed by the restart of the Storage Manager EventReceiver service.

Always alert when Agent statusis Critical or Warning

Sets status to TRUE/FALSE. The 'Agent Status Alert' parameter shouldbe set to 'TRUE'

Agent Status Alert Frequency Sets Alert Frequency levels. Default is five minutes. The 'Agent StatusAlert' parameter should be set to 'TRUE'. Any change made to thisparameter should be followed by the restart of the SRM Profiler EventReceiver Service.


page 71

ARRAY SETTINGSThe Array Settings control the behavior of the NAS and the Xiotech Magnitude poller.

SETTING DESCRIPTION

EMC Celerra TCP Dump Interval Sets the TCP dump capture period.

EMC Celerra TCP Dump Frequency Sets the TCP dump capture frequency.

NetApp Include Snapshot Select YES / NO.

Xiotech Asset Frequency Sets the frequency that asset and allocation information is polled.

Xiotech Performance Frequency Sets the frequency at which performance information isgathered.

C-Level Data Collection Frequency Sets the frequency to Daily / Always / Never.

DATABASE SETTINGSThe Database settings control the behavior of the Oracle and the SQL-Server Poller.

SETTING DESCRIPTION

Oracle Performance PollingFrequency

Specify how often SRM Profiler gathers performance data from server-attached Oracle RDBMS.

Oracle Usage PollingFrequency

Specify how often SRM Profiler gathers usage data from erver-attachedOracle RDBMS.

SQL Server PerformancePolling Frequency

Specify how often SRM Profiler gathers performance data from server-attached SQL Server RDBMSs.

SQL Server Usage PollingFrequency

Specify how often SRM Profiler gathers usage data from server-attachedSQL Server RDBMSs.

SQL Server TableFragmentation Hour

Set the start time to run the DBCC ms-sql command to collect tablefragmentation stats.

EMAIL SETTINGS

SETTING DESCRIPTION

Email ServerEmail From

Specify the email account that SRM Profiler will use to send email notificationsand reports. The defaults should be changed immediately.

page 72

SETTING DESCRIPTION

Email Server Port Specify the port to be used for e-mail systems that requires authentication. Whenusing secure SMTPS protocol.

Email ServerUsernameEmail ServerPassword

Provide valid Username and Password for e-mail systems that requiresauthentication. For example: When using secure SMTPS protocol.

Use SMTPS Select 'Yes' if using e-mail systems that requires authentication. Else select 'No'.

FILE ANALYSIS SETTINGSAll settings that control the behavior of file analysis and data classification.

SETTING DESCRIPTION

File AgeCategories

Set the coding thresholds for File Age reporting values in reports.

Always Pre-Select All NASShares

Determine if all shares are selected to be available to assignment to an agentautomatically (Yes) or if you have to manually select the shares before you can assignthem to an agent (No).

UngroupedFile TypeDetails

Determine whether to store detailed information on ungrouped file types in database.

GUI SETTINGS

SETTING DESCRIPTION

ServerMonitorRefreshFrequency

Set the frequency at which you want to refresh the Server monitor.

Max DataPoints forStorageTrending andForecasting

Set the maximum number of data points that SRM Profiler will trend for storage usage.For example, 30 means SRM Profiler will go back 30 days (assuming one point per day)while doing analysis. The minimum is 15 points.


page 73

SETTING DESCRIPTION

ServerMonitor Filter

Filter the list of Servers in the Server Monitor and Server Status bar by last collect time.

EnableIPAddressChange

Allow the IP addresses of servers to be changed on the Device Page.

EnableStorage -Share GroupAssignmentby filter only

Select this feature to enable storage share group assignment using only the filter.Enable this option when there are a large number of shares.

Track invalidlog inattempts inWindow EventLog

Select True if you want to track any invalid log in attempts in the Windows Event Log.This is applicable only for Server installed on Windows OS.

EmailNotificationsfor SNMPAlerts

Select 'First Occurrence' to receive an email notification 'once' for the first time when atrap comes in (or) select 'Every Occurrence' to receive an email notification 'for everyrepeated occurrence of the trap. In case of iservice, this sends out an email notificationevery minute, whenever the iservice is down.

Delete Outputfiles OlderThan

Set the period after which files are deleted. This can be between 1 and 24 hours.

REAL TIME SETTINGSEach of the following parameters allows you to set the minimum threshold for the HIGH warning and errorconditions evaluated by the Real-Time confidence intervals.

For example: If the confidence interval evaluates CPU Busy on a server to 12% for warning and 33% for anerror, SRM Profiler will adjust those settings higher to meet the minimums set here (15% and 40%respectively).

SETTING DESCRIPTION

CPU Error Minimum Set the minimum CPU Busy for a HIGH Error threshold.

CPU Warning Minimum Set the minimum CPU Busy for a HIGH Warning threshold.

page 74

SETTING DESCRIPTION

Disk Error Minimum Set the minimum Disk I/O for a HIGH Error threshold.

Disk Warning Minimum Set the minimum Disk I/O for a HIGH Warning threshold.

Memory Error Minimum Set the minimum Memory for a HIGH Error threshold.

Memory Warning Minimum Set the minimum Memory for a HIGH Warning threshold.

Network Error Minimum Set the minimum Network I/O for a HIGH Error threshold.

Network Warning Minimum Set the minimum Network I/O for a HIGH Warning threshold.

REPORTER SETTINGS

SETTING DESCRIPTION

Maximum Report Rows Set the maximum number of rows a report is allowed. When you run a report,you can also specify the number of rows you want to display.

Delete Published filesOlder Than

Set the number of hours or days that published reports are retained.

Date Format Set the way dates will be displayed in reports and consoles.

Report Charset Set charset encoding for reports.

Percent Usage ColorCoding

Set the color coding thresholds for Percent Usage values in reports and onDevice Consoles. Enter "70,80,90" to show 0-70% as Green, 70-80% as Yellow,80-90% as Orange and 90-100% as Red. You can enter from one to threethreshold values. Enter "off" to turn off this feature.

Server Name Set the name of the Server.

Server Port Set the port of the Server.

Chart Font Determine the font used in charts.

Chart Top X Series Determine the value for the Top X series for charts.

SERVER SETTINGSThe Server settings control the overall behavior of the SRM Profiler server, the SNMP and DNS Poller. Thissetting also defines how the server sends email and the global configuration of File Age Categories.


page 75

SETTING DESCRIPTION

Delete Log files OlderThan

Set the duration server log files are retained on the server.

SNMP Trap Port Set the port you want to receive traps on.

If you change this setting, you should restart the event receiver.

Data Retention policyStart Time

Set the time you want Data Retention policies to be executed. Data RetentionPolicies can tax a system for a short period because every table is analyzed.It is recommended that you run this analysis when the machine is not busy.

Hosts Down MonitorEnable

The Default is YES. If set to NO, then the functionality of 'Host NotResponding to Ping' trap is disabled. Any change to this parameter either(YES / NO) should be followed by the restart of the SRM Profiler EventReceiver service.

Web Server Log Level Set the level of SRM Profiler Reporter Web Server log messages.

Maintenance Log Level Set the level of SRM Profiler Reporter Maintenance log messages.

Poller Log Level Set the level of SRM Profiler Reporter Poller log messages.

Event Receiver Log Level Set the level of SRM Profiler Reporter Event Receiver log messages.

SNMP Table Poll Timeout Set maximum time allowed for polling an SNMP table.

Automatic Clearing ofTraps Frequency

Set frequency to clear traps older than trap age threshold.

Automatic Clearing ofTraps Age

sets the trap age threshold for automatic trap clearing.

DNS Polling Frequency sets the frequency at which the DNS Poller will poll the DNS agents you havedefined.

Chart Image Format sets the chart image format to either PNG or JPG default format is PNG.

Collector Frequency Allow administrators to specify the maximum time between collectionattempts, ranging from 30 minutes to daily. Every 15 minutes, SRM Profilerchecks every device and if the time since the last successful data collectionis greater than the time specified in this field, the server adds the device tothe collection list and attempts to collect data from the agent on that device.

SNMP Frequency Set the interval (30 min. to daily) the server uses for SNMP-standard GETcommands to collect MIB II data from SNMP-enabled monitored devices.

page 76

The Storage Manager Event Receiver continues to receive SNMP traps as they arrive regardless ofthe setting in this field.

TRAP FORWARDING SETTINGSThe SRM Profiler server and its agents generate traps that are sent to the SRM Profiler Trap Receiver.These traps can also be forwarded to a network operations center.

FORWARDING TRAPS FOR SRM PROFILER SERVER

To forward SRM Profiler server traps to a network operations center, you must configure the trapforwarding features of SRM Profiler. You can also set up alerts based on traps.

SRM Profiler only forwards SRM Profiler traps.

To configure Trap Forwarding, navigate to Settings > Server Setup: All >Trap Forwarding, and thenconfigure the following fields:

SETTING DESCRIPTION

ForwardTraps

Enable the forwarding of traps when set to true.

DestinationIP

Set the IP address of the server to which you want to forward traps.

DestinationPort

Set the port of the server to which you want to forward traps.

CommunityString

Set the community string of the server to which you want to forward traps.

Disk UsageWarningLimit

Set the threshold for a file system, volume or drive that you want to forward as a Warningtrap.

Disk UsageCriticalLimit

Set the threshold for a file system, volume or drive that you want to forward as a Criticaltrap.

Disk UsageError Limit

Set the threshold for a file system, volume or drive that you want to forward as an Errortrap. In general, you want the Warning Limit to be less than the Critical Limit, which will beless than the Error Limit (e.g., 70 < 80 < 90).

PersistTrap

Determine if trap is persisted in database.


page 77

FORWARD TRAPS FOR SRM PROFILER AGENT

1. Click Settings on the SRM Profiler web console.2. Click the edit icon for the Default OS Policy.3. Select the Communication link.4. Click the Add Trap Destination bar.5. Place the IP address of the trap server you want to forward the traps to.6. Configure the port and community string to your desired settings.7. Select Override Agent Values, and then click Save.8. Push your changes to the external agents by clicking the Push button.

SRM Profiler agents do not filter any traps being forwarded to a remote host and many traps arelogged to the destination server. Filtering of these traps must be done by the destination. Pleasesee: Trap integration between Storage Manager and Orion.

USER AUTHENTICATION SETTINGS (LDAP SETTINGS)SolarWinds recommends enabling the following permissions:

l Read All Propertiesl Read All Permissionsl Allowed to Authenticatel Change Password

SETTING DESCRIPTION

Enable LDAP Authentication Enable LDAP Authentication when set to True.

LDAP Server Display Domain name Set display name for LDAP server.

LDAP Server URL Set URL for LDAP Server.

LDAP Server Manager DN Set Distinguished Name (DN) for LDAP Server Manager

LDAP Server Manager password Provide password for LDAP Server Manager

LDAP Search Base Specify LDAP search base.

LDAP Search Filter Specify LDAP filter.

LDAP Search Subtree Searches LDAP subtree when set to True.

LDAP Dereference Flag LDAP Server performs dereferencing when set to True.

page 78

https://support.solarwinds.com/Success_Center/Storage_Manager_(STM)/Trap_integration_between_Storage_Manager_and_Orion

The LDAP Server Manager DN (Distinguished Name) cannot contain forward "/" or backward "\"slashes.

VIRTUALIZATION SETTINGS

SETTING DESCRIPTION

VM AgeCategoriesby BootTime

Set the coding thresholds for VM Age Categories by Boot Time reporting values inreports.

CapacityForecastingTargetUtilization

Set the utilization range from 50% to 100%.

CPUDistributionCategory

Distribution of the number of CPU cores in the VM. For example, if you set this to 1,2,5, VMswith similar CPU core setups are categorized in the CPU pie chart under the AssetDistribution section.

MemoryDistributionCategory(MB)

Distribution of RAM allocated to the VMs. For example, if you set this to 1024,512, VMs withsimilar RAM capacity are categorized in the Memory pie chart under the Asset Distributionsection.

StorageDistributionCategory(GB)

Distribution of storage space allocated to the VMs. For example, if you set this to 10,20,VMs with similar storage size are categorized in the Storage pie chart under the AssetDistribution section.

HeatmapPercentageCategoryVM

CPU/Memory/Storage values are categorized as a green, yellow, or red status. For example,if the Heatmap Percentage Category is set to 70,90, all VMs CPU/Memory/Storage valuesless than 70 percent report as green, 70-90 report as yellow and greater than 90 report asred. Values are reported to the "VM Group" page under the VM Heatmap section.


page 79

The following table represents the parameters that require a restart of certain SRM Profiler Services forthe effect to take place.

Server Setup Parameter -Function

Name of the parameter Name of the service to be restarted

Server Agent Status Alert SolarWinds Storage Manager EventReceiver

Server Agent Status AlertFrequency

SolarWinds Storage Manager EventReceiver

For all others, the Services do not need to be restarted, but they take effect only going forward. No changesare made to historical data.

MANAGE AGENT ASSIGNMENTSThis option is available under Device Management.

1. Select the edit icon for the device you want to assign the agent to.2. Click Select Agent.3. Select an agent from the dropdown list and click Save.

You can also unassign agents during this process if the device is a Cluster/ESX host.

ENABLING SSL LOGIN FOR THEWEBSITESome users may want to utilize SSL logins for their website. Enabling SSL Login describes how to set up SSLon the SRM Profiler Web Console using port redirection from port 80.

When enabled, users can access the Web Console on port 80, and HTTPS is used automatically.

To enable SSL complete the following steps:

1. SRM Profiler already has a self-signed certificate in the < installation

path>/webapps/ROOT/bin directory called "jswis-keystore." To use this keystore, proceed to step4, otherwise proceed to step 2.

page 80

2. Run the command:C:\Program Files\SolarWinds\Storage Manager Server\jre\bin>keytool -genkey

-alias tomcat -keyalg RSA

and when prompted, enter your details and a password for the keystore. Remember this keystorepassword.

3. The certificate file is called .keystore and it can be found in the home directory of the user creatingit. Save this file to a location outside of the SRM Profiler installation directory, for example: C:\SRM_Certificate.

4. Using a text editor, open the server.xml file. This file is located in C:\ProgramFiles\SolarWinds\Storage Manager Server\conf\server.xml directory. Perform thefollowing changes:

a. Using the self-signed certificate you just created:

<Connector port="8443"

protocol="org.apache.coyote.http11.Http11NioProtocol"

URIEncoding="UTF-8" disableUploadTimeout="true"

connectionTimeout="20000" acceptCount="100" redirectPort="8443"

enableLookups="false" maxSpareThreads="75" minSpareThreads="25"

keystoreFile="webapps/ROOT/bin/jswis-keystore"

keystorePass="solarwinds" SSLEnabled="true" maxThreads="150"

scheme="https" secure="true" clientAuth="false" sslProtocol="TLS"

maxHttpHeaderSize="8192" ciphers="SSL_RSA_WITH_RC4_128_MD5,SSL_

RSA_WITH_RC4_128_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_DHE_RSA_

WITH_AES_128_CBC_SHA,TLS_DHE_DSS_WITH_AES_128_CBC_SHA,SSL_RSA_

WITH_3DES_EDE_CBC_SHA,SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA,SSL_DHE_

DSS_WITH_3DES_EDE_CBC_SHA"/>

b. Using your own self-signed certificate:

<Connector port="8443"

protocol="org.apache.coyote.http11.Http11NioProtocol"

URIEncoding="UTF-8" disableUploadTimeout="true"

connectionTimeout="20000" acceptCount="100" redirectPort="8443"

enableLookups="false" maxSpareThreads="75" minSpareThreads="25"

keystoreFile="C:\SRM_Certificate\.keystore"

keystorePass="solarwinds" SSLEnabled="true" maxThreads="150"

scheme="https" secure="true" clientAuth="false" sslProtocol="TLS"

maxHttpHeaderSize="8192" ciphers="SSL_RSA_WITH_RC4_128_MD5,SSL_

RSA_WITH_RC4_128_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_DHE_RSA_

WITH_AES_128_CBC_SHA,TLS_DHE_DSS_WITH_AES_128_CBC_SHA,SSL_RSA_

WITH_3DES_EDE_CBC_SHA,SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA,SSL_DHE_

DSS_WITH_3DES_EDE_CBC_SHA"/>


page 81

l The port numbers can be modified to whatever port you wish to use for HTTP orHTTPS communication.

l In the HTTPS connector, the 'keystoreFile=' points to the location of the keystore file.l In the HTTPS connector, the 'keystorePass=' contains the password for the keystorefile.

l If you update the HTTPS port you must also update the 'redirectPort= ' in the HTTP andHTTPS connectors.

5. Save your changes to the server.xml file.6. Using a text editor, open the web.xml file located in the C:\Program Files\SolarWinds\SRM

Profiler Server\conf\web.xml directory.7. Remove the <url-pattern> line and modify it by copying the following lines in the same </web-app>

tag location:l <url-pattern>/*</url-pattern>

l <http-method>GET</http-method>

l <http-method>POST</http-method>

The modified <security-constraint> tag in web.xml should like the following:

<security-constraint>

<web-resource-collection>

<url-pattern>/*</url-pattern>

<http-method>GET</http-method>

<http-method>POST</http-method>

</web-resource-collection>

<user-data-constraint>

<transport-guarantee>CONFIDENTIAL</transport-guarantee>

</user-data-constraint>

</security-constraint>

8. Save the web.xml file.9. Restart the Web Services service.

RM Profiler databaseSRM Profiler is bundled with its own database. The SRM Profiler database is flexible, making the databasebackup, external access (via ODBC) and handling easy tasks.

page 82

Using the SRM Profiler database's server for applications other than SRM Profiler can slow downperformance and consume additional CPU devices.

SRM Profiler Database Port:

SRM Profiler Database runs its server on port 3306. SolarWinds strongly recommends not changing thissetting. Contact http://www.solarwinds.com/support/ticket/ for assistance if you need to change it

The SRM Profiler database performs correctly under most situations and in most environments with thedefault configuration. If performance optimization is required, contact SolarWindshttp://www.solarwinds.com/support/ticket/ for assistance.

If you installed MariaDB before installing SRM Profiler server, the install will terminate. Only oneinstance of the MariaDB is supported on the SRM Profiler server.

Before installing the SRM Profiler server, stop the MariaDB Windows service (if any) and then uninstallMariaDB. DO NOT manually delete any MariaDB directories even after uninstall is completed! Olddatabase data is located under the MariaDB install directory.

Any external utility that scans or backs up the SRM Profiler database is NOT recommended instead useDbutil for backup and maintenance.

BACKUP THE SRMPROFILER DATABASEBoth backing up the SRM Profiler Database and data recovery are simple processes.

SRM Profiler versions 5.6 and newer use MariaDB. For previous versions, MySQL is used. Forversions prior to 5.6, substitute MySQL for MariaDB in the following instructions.

1. Stop SRM Profiler services.2. Stop MariaDB services.3. Make a copy of the entire data directory, and put it in a different location:

l The default path in Windows: <installed drive>:\Program Files\SolarWinds\SRM

Profiler Server\mariadb\data\storage directory.l The default path in Linux: <installed path> /Storage_Manager_

Server/mariadb/data/storage directory.

Versions prior to SRM Profiler version 5.6 use either of the following:

l \mysql\data\storage directory for Windows.l \mysql\data\storage_manager path for Linux.


page 83

http://www.solarwinds.com/support/ticket/


RECOVER THE SRM PROFILER DATABASE

1. Stop SRM Profiler services.2. Stop MariaDB services.3. Replace the data directory (see section above for paths) with the backed up directory.4. Restart MariaDB services.5. Restart SRM Profiler services.

DATABASE MAINTENANCE USING DBUTILdbutil is a script that ships with SRM Profiler and allows you to make backups of your database and runmaintenance routines to keep the database running smoothly.

All SRM Profiler Services are halted when this utility runs.

Depending on which platform you are running, directions are below explaining how to run dbutil in yourenvironment.

l Windows instructionsl Linux instructions

RUN DBUTIL INWINDOWS

The dbutil.bat file is located in the <installed drive>:\Program Files\SolarWinds\Storage

Manager Server\bin directory.

PREPARATION

1. Using a text editor, edit your dbutil.bat file and find the following string: SetBackupStage=C:\temp\mariadb_backup

2. Change the path C:\temp\mariadb_backup to the directory where you would like to backup yourprofiler database.

: It is recommended that you do not use a directory within the SRM Profiler install directory and youneed to verify that the location selected has sufficient free disk space for your database.

USAGE

dbutil.bat [backup|maintenance]

OPTIONS

l backup: Copy database to backup directoryl maintenance: Run database repair/analysis/optimization proceduresl default (no options specified): Executes maintenance and backup

page 84

SCHEDULING

To run this using Windows task scheduler.

1. Open Windows Task Scheduler and Create a Basic Task with your desired schedule (Weekly forexample).

2. Set the Action as Start a Program.3. Program/script = \bin\dbutil.bat

4. Set the arguments to "backup" to only do a backup if desired.

RUN DBUTIL IN LINUX

The dbutil.bat file is located in the <installed drive>/Storage_Manager_Server/bin directory.

PREPARATION

1. Edit your dbutil.sh file and find the following string: export backupStage=/opt/mariadb_backup

2. Change the path /opt/mariadb_backup to the directory where you would like to backup yourprofiler database.

: It is recommended that you do not use a directory within the SRM Profiler install directory and youneed to verify that the location selected has sufficient free disk space for your database.

USAGE

dbutil.sh [backup|maintenance]

OPTIONS

l backup: Copy database to backup directoryl maintenance: Run database repair/analysis/optimization proceduresl default (no options specified): Executes maintenance and backup

SCHEDULING

Create a cron job to run the dbutil.sh on a schedule.

Advanced configuration of SRM Profiler

This section is for advanced users. If you are uncomfortable with performing any of the steps below,please contact SolarWinds Support.

In this section:


page 85


l Increase memory for SRM Profiler servicesl Modify database memory settingsl Antivirus and intrusion detectionl Library and support via thwack!

INCREASE MEMORY FOR SRMPROFILER SERVICESTo increase memory for your SRM Profiler server services, SRM Profiler agents or SRM Profiler proxyagents, you must increase the Java Max Memory value.

Increasing Java memory is done by updating the –Xmx value within its respective configuration file.

Java uses the –Xmx value to define the largest allowable size of the heap. Heap is the total memoryallocation used by the Java Virtual Machine and –Xmx defines the maximum amount of memory that Javacan use for that service.

You can adjust memory setting for the following SRM Profiler services:

SRM Profiler services retain the original SolarWinds Storage Manager names.

l Storage Manager Collectorl Storage Manager Agent or Proxy Agentl Storage Manager Event Receiverl Storage Manager Pollerl Storage Manager Maintenancel Web Server Memoryl Database Memory Settings

ADJUST MEMORY SETTINGS FOR STORAGEMANAGER COLLECTOR

If you are running a large amount of SRM Profiler proxy agents, or if your environment switches from smallto medium or large, it may be necessary to adjust the memory settings for the Storage Manager CollectorService.

The Storage Manager Collector Service is responsible for handling the collection of data from SRM Profilerproxy agents. The Storage Manager Collector service also acts as a local data collector/agent. The defaultmaximum memory value in a small environment for the Storage Manager Collector service is 1024m. If youneed to adjust this value due to a larger polling environment, this section explains how.

1. Stop the collector service for SRM Profiler server.l For Windows, run the Windows application services.msc and look for a service calledSolarWinds Storage Manager Collector and stop the service.

l For Linux, SSH to the SRM Profiler server using an account that has root privileges and runthe following command: /etc/init.d/storage_manager_server stop collector

page 86

2. Locate the collector configuration file. The Java memory settings are located in this file.l For Windows the file will be located in the <installed drive>\Program

Files\SolarWinds\Storage Manager Server\webapps\ROOT\bin sub directory. Filename is SolarWinds.Storage.Collector.ini.

l For Linux the file will be located in the <installed path> /Storage_Manager_

Server/bin sub directory. File name is collector.sh.3. Using a text editor, open the file. Once you have opened the file search for the –Xmx value and

adjust it to a higher value that fits your environment according to the sizing chart below.l Example: -Xmx4096m for a medium environment

4. Save the file and start the collector service.l For Windows run the Windows application services.msc and look for a service calledSolarWinds Storage Manager Collector and start the service.

l For Linux, SSH to the SRM Profiler server using an account that has root privileges and runthe following command: /etc/init.d/storage_manager_server start collector

Sizing Chart for SRM Profiler Collector Service:

Environment Size Medium Large

Memory 4096m 8192m

Note: Linux is the recommended platform for SRM Profiler server when monitoring large environments.

** For environment size specifications see Small, Medium, Large Environments

ADJUST MEMORY SETTINGS FOR SRM PROFILER AGENT OR SRM PROFILERPROXY AGENT

1. Stop the agent service for SRM Profiler agent or proxy agent.l For Windows run the Windows application services.msc and look for a service calledSolarWinds Storage Manager agent Service. Stop the service.

l For Linux, SSH to the SRM Profiler server using an account that has root privileges and runthe following command: /etc/init.d/storage_manager_agent stop

2. We must now find the location of the file that contains the memory settings.l Windows the file will be located in the <installed drive>\Program

Files\SolarWinds\Storage Manager Agent sub directory. The file name will beSolarWindsStorage.Agent.ini.

l For Linux, migrate to the /etc/init.d sub directory and using a text editor, open the filecalled storage_manager_agent.

3. Using a text editor, open the file. Once you have opened the file search for the –Xmx value andadjust it to a higher value that fits your environment per the Storage Manager Proxy AgentDeployment table.


page 87

l Example: -Xmx4096M for a medium environment.4. Save the file and start the agent service.

l For Windows run the Windows application services.msc and look for a service calledSolarWinds Storage Manager agent Service. Start the service.

l For Linux, SSH to the SRM Profiler server using an account that has root privileges and runthe following command: /etc/init.d/storage_manager_agent start

You can turn off Performance Reporting and Real Time Status for improvedperformance of SRM Profiler proxy agents.

ADJUST MEMORY SETTINGS FOR STORAGEMANAGER EVENT RECEIVER

If you are running a large amount of SRM Profiler agents, it may be necessary to adjust the memorysettings for the Storage Manager Event Receiver Service.

The Storage Manager Event Receiver Service is responsible for receiving traps being sent from SRMProfiler agents. The default maximum memory value in a small environment for the Storage ManagerEvent receiver is 1GB. Most of the time this value is sufficient for the SRM Profiler server yet if you need toadjust this value, this section explains how.

The Storage Manager Event Receiver configuration file can be found in the following locations:

WINDOWS

1. Go to the <installed drive>\Program Files\SolarWinds\Storage ManagerServer\webapps\ROOT\bin

2. Using a text editor, open the file SolarWinds.Storage.EventReceiver.ini3. Look for param02=-Xmx1024m and modify it to a value that fits your environment per the Sizing

Chart below.l Example: Medium environment will be param02= -Xmx4096m

4. Save the file and restart the SolarWinds Storage Manager Event Receiver service via services.msc.

LINUX

1. Go to the <installed path>/Storage_Manager_Server/bin directory.2. Using a text editor open the file eventreceiver.sh.3. Look for –Xmx and modify it to a higher value that fits your environment according to the Sizing

Chart below.l Example: -Xmx4096m for a medium environment

4. Save the file and restart the Storage Manager Event Receiver service using the command/usr/bin/storage_manager_server restart eventreceiver

Sizing Chart for Storage Manager Event Receiver:

page 88


Memory 4096m 4096m

For environment size specifications see Small, Medium, Large Environments

ADJUST MEMORY SSETTINGS FOR STORAGEMANAGER POLLER

If you are monitoring a large amount of Fibre Channel Switches or other devices that are polled usingSNMP or devices such as EMC Celerra, MS-SQL, or Oracle which do not use SNMP, it may be necessary toadjust the memory settings for the Storage Manager Poller Service.

The Storage Manager Poller Service is responsible for monitoring devices that use SNMP. It also polls EMCCelerra, MS-SQL, and Oracle which do not use SNMP. The default maximum memory value in a smallenvironment for the SRM Profiler Poller is 512MB. Most of the time this value is sufficient for the SRMProfiler server yet if you need to adjust this value, this section explains how.

The SRM Profiler Poller configuration file can be found in the following locations:

SRM PROFILER SERVER - WINDOWS


2. Using a text editor, open the file SolarWinds.Storage.Poller.ini3. Look for param02=-Xmx512m and modify it to a value that fits your environment per the sizing

chart below.l Example: Medium environment will be param02=-Xmx2048m

4. Save the file and restart the SolarWinds SRM Profiler Poller service via services.msc.

SRM PROFILER SERVER - LINUX

1. Go to the <installed path>/Storage_Manager_Server/bin directory.2. Using a text editor open the file poller.sh.3. Look for –Xmx and modify it to a value that fits your environment according to the sizing chart

below.l Example: –Xmx2048m for a medium environment

4. Save the file and restart the Storage Manager Poller service using the command/usr/bin/storage_manager_server restart poller

Sizing Chart for SRM Profiler Poller Service:


Memory 2048m 4096m



page 89

ADJUST MEMORY SETTINGS FOR STORAGEMANAGERMAINTENANCE SERVICE

If you have a large database, it may be necessary to adjust the memory settings for the Storage ManagerMaintenance Service.

The Storage Manager Maintenance Service is responsible for performing maintenance on the database byrunning the rollup and cleanup scripts. The default maximum memory value in a small environment forthe Storage Manager Maintenance is 512MB. Most of the time this value is sufficient for the SRM Profilerserver yet if you need to adjust this value, this section explains how.

The Storage Manager Maintenance configuration file can be found in the following locations:

SRM PROFILER SERVER - WINDOWS


2. Using a text editor, open the file SolarWinds.Storage.Maintenance.ini3. Look for param02=-Xmx512m and modify it to a value that fits your environment per the sizing

chart below.l Example: Medium environment will be param02=-Xmx2048m

4. Save the file and restart the SolarWinds Storage Manager Maintenance service via services.msc.

SRM PROFILER SERVER - LINUX

1. Go to the <installed path>/Storage_Manager_Server/bin directory.2. Using a text editor open the file Maintenance.sh.3. Look for –Xmx and modify it to a value that fits your environment according to the sizing chart

below.l Example: –Xmx2048m for a medium environment

4. Save the file and restart the Storage Manager Maintenance service using the command/usr/bin/storage_manager_server restart maintenance.

Sizing Chart for Storage Manager Maintenance Service


Memory 2048m 4096m


INCREASINGWEB SERVERMEMORY

Most of the time, Web Server memory will not need adjusting. When SRM Profiler is initially installed it willcheck the specifications of the server and adjust itself given the resources provided. If you must adjust thememory settings for the Web Server Service, this section will explain how.

page 90

WINDOWS

1. Open a Windows command prompt to <installed drive>\Program

Files\SolarWinds\Storage Manager Server\bin directory.2. Run the following command: SolarWinds.Storage.WebServicew.exe

//RS//SWStmWebServerSvc

3. This will open a Web Services Properties GUI. On the Java tab increase the Max Memory Pool to ahigher value that fits your environment per the Sizing Chart below.

4. Restart the SolarWinds Storage Manager Web Services via services.msc.

LINUX

Linux uses a startup script for changing Web Server Service memory settings. The script is calledwebserver.sh. The script will be located in the <installed path> /Storage_Manager_Server/bin/

directory. Using a text editor open the file webserver.sh. The line that needs to be configured in this scriptis JAVA_OPTS="-XX:MaxPermSize=256M -Xmx512M" Increase the –Xmx value and modify it to a valuethat fits your environment according to the sizing chart below.

l Example: –Xmx4096m for a medium environment

This will increase the maximum memory allocated to the Web Server Service. Next save the file and restartthe SRM Profiler Web Service by typing the command /usr/bin/storage_manager_server restart

webserver.

Sizing Chart for SRM Profiler Web Server:


Memory 4096m 8192m



page 91

MODIFYING DATABASE MEMORY SETTINGS

This is an advanced topic and if you feel uncomfortable performing any of the following stepsplease contact SolarWinds Support.

Most of the time, the database memory settings will not need adjusting. When SRM Profiler is initiallyinstalled it will check the specifications of the server and adjust itself given the resources provided. If youmust adjust the memory settings for the database, this section will explain how.

SRM Profiler versions 5.6 and newer use MariaDB. For versions prior to 5.6, substitute MySQL forMariaDB.

Using a text editor, the my.cnf file can be modified to increase various memory settings for the database.

File Locations:

l Windows: <installed drive>:\Program Files\SolarWinds\Storage Manager Server\mariadb\my.cnfl Linux: <installed path>/Storage_Manager_Server/mariadb/my.cnf

The values you may want to consider changing are:

l key_buffer_size (size of the index buffers held in memory)l sort_buffer_sizel read_buffer_sizel myisam_sort_buffer_sizel thread_concurrencyl max_connections (be careful with this number, it should not exceed 700)l tmp_table_size (On a server with a lot of RAM this can dramatically help SQL performance. Thisshould be set to the largest table size in the database)

Explanations of these variables can be found at the MariaDB website:https://mariadb.com/kb/en/mariadb/server-system-variables

The following table shows sample configurations referencing Small, Medium, and Large environments:

Small Medium Large

key_buffer 2048 MB 4096 MB 8192 MB

sort_buffer_size 2 MB 4 MB 16 MB

read_buffer_size 2 MB 4 MB 16 MB

myisam_sort_buffer_size 2048 MB 4096 MB 8192 MB

tmp_table_size 292 MB 585 MB 1170 MB

page 92


https://mariadb.com/kb/en/mariadb/server-system-variables

max_heap_table_size 292 MB 585 MB 1170 MB

thread_concurrency 4 8 16

max_connections 400 600 600

thread_concurrency= should always equal 2x the number of processors on the machine.

Once you have made all necessary changes, restart the database service, this will also force a restart of theStorage Manager Collector, Event Receiver, Web, Maintenance and Poller services.

After performing changes to database memory it is recommended to run Dbutil.

Dbutil is a script that ships with SRM Profiler that allows you to run maintenance routines to keep thedatabase running smoothly. It also allows users to perform backups of the database. For more information,see Dbutil.

ANTIVIRUS AND INTRUSION DETECTIONAny external software that scans the SRM Profiler Database and module files can cause locks and potentialcorruption. Blockage of ports used by SRM Profiler can also cause problems. SolarWinds recommends thatyou add the following exclusions to your antivirus and intrusion detections software.

SRM Profiler versions 5.6 and newer use MariaDB. For previous versions, MySQL is used. Forversions prior to 5.6, substitute MySQL for MariaDB.

SRM PROFILER SERVER EXCLUSIONS - WINDOWS

l <Install Directory>\SRM Profiler Server\agent\systemic

l <install Directory>\SRM Profiler Server\agent\administrative

l <install Directory>\SRM Profiler Server\mariadb

l C:\Windows\Temp

If you are unable to exclude C:\Windows\Temp, perform the following steps:

1. Open my.cnf in C:\Program Files\SolarWinds\SRM Profiler Server\mysql.2. Search for "tmpdir". By default it is commented out. Uncomment and add your desired

subdirectory. This example uses a sub directory called MyTemp. (tmpdir=C:/MyTemp). Ensurethat the MyTemp folder is created on the C drive using a forward slash (/).

3. Add C:\MyTemp to the Antivirus exclusion list.4. Restart mysql.


page 93

SRM PROFILER SERVER EXCLUSIONS - LINUX

l <Install Directory>/Storage_Manager_Server/agent/systemic

l <install Directory>/Storage_Manager_Server/agent/administrative

l <install Directory>/Storage_Manager_Server/mariadb

SRM PROFILER AGENT EXCLUSIONS - WINDOWS

l <install Directory>\SRM Profiler Agent\systemic

l <install Directory>\SRM Profiler Agent\administrative

SRM PROFILER AGENT EXCLUSIONS - NON-WINDOWS

l <install Directory>Storage_Manager_Agent/systemic

l <install Directory>Storage_Manager_Agent/administrative

PORT EXCLUSIONS FOR SRM PROFILER SERVER AND AGENTS

Your Antivirus and Intrusion Detection software must allow access to the following ports:

l TCP 4319, 8443, 43501, 43502, 43503, 43504l UDP 162, 10162, 20162

SRM Profiler uses UDP 162 by default. If this port is being used by another application, it will useeither UDP 10162 or 20162.

LIBRARY AND SUPPORT VIA THWACK!More information about SRM and SRM Profiler can be found on thwack! athttp://thwack.solarwinds.com/docs/DOC-1100

Use reports and schedulesSRM Profiler supports a versatile reporting tool that provides summary, inventory and historicalinformation about network performance, storage and devices. The reports provide information aboutservers, databases, backup operations, NAS and SAN devices. SRM Profiler provides two levels of reportsand an Enterprise Report:

l Administrator reportsl User reportsl Enterprise report

For more information on running reports, see Manage reports.

page 94

http://thwack.solarwinds.com/docs/DOC-1100

ADMINISTRATOR REPORTSSRM Profiler is configured with two report options available to administrators and those users with specificpermissions only. These options provide instantaneous access to assets, operating systems, storage, andbackup statistics across the entire network. When an administrator logs in to SRM Profiler, two additionalselections are available under the Reports menu option.

l Management Reports: Provides a quick high-level summary of the current network assets, storageand backup.

l Enterprise Storage Reports: Present high-level summary views of network performance, whileallowing the administrator to drill down to see underlying data.

Click the Reports folders to expand the report options. The SRM Profiler user report options are listedbelow.

l My Reports: Reports you have createdl Shared Reports: Reports other users have created and shared with youl Quick Reports: Predefined reports

SRM Profiler uses a consistent format to display and manage reports regardless of which option isselected. Select an option and a table appears listing the reports available under that option. If no reportsare available an error message is displayed. Within each section, managing reports works the same. Youcreate, run, schedule, modify and delete reports the same way.

You cannot modify or delete quick reports.

USER REPORTSSRM Profiler allows each user to run preformatted and user-defined reports. Both types of reports may bescheduled to run periodically at specific times. The Reports menu selection has several options:

l My Reports: This option is for building user-defined reports. These reports will always be accessibleto the individual user or the administrator. The user has the option to set the permission level of areport so that the report can be shared with other users.

l Shared Reports: Reports created by any user in My Reports may be shared with other users in thesame group or with all users. If any reports are shared they will be listed under this menu option.Administrators always have access to all reports, regardless of who created the report.

l Quick Reports: This is a selection of reports preformatted by SRM Profiler. These reports cover abroad spectrum of file, device, and network parameters. Parameters include: disk usage, diskperformance, disk and file system inventory, CPU/Memory performance statistics, networkstatistics and virtual memory performance statistics.

You can "star" a report as favorite, on the My Reports, Quick Reports, and Shared Reports page. A checkbox is added to the top of each page so that the user can filter each page to only show the favorites.


page 95

ENTERPRISE STORAGE REPORTSEnterprise Reports present high-level summary views of network performance, while allowing theadministrator to drill down to see underlying data.

The administrator can look across the enterprise and see a summary view of how much storage spaceeach user is utilizing, then drill down to see the types of files and their locations for that individual user.

The report also provides visibility into how logical and physical storage and data are presented by storagetier, business unit, data center, location, or other logical group using flexible grouping of volumes, qtrees,LUNs, and directories.

FILE REPOSITORYThe File Repository or Central Repository is a location to publish and store reports.

Users can email or publish their reports. The published reports can either be published to a default pathor a defined target location. The user defined target location can be defined from the Reports Schedulewindow or from the File Repository window.

DEFINE A FILE REPOSITORY

1. Go to Settings > File Repository.2. In the File Repository window, click Add.3. In the Set up a Central File Repository, enter values for the following fields:

l Display Name: Enter a meaningful name for your File Repository.l Device name or IP: Enter the device name or IP address where you shared directory residesl CIFS Share Name or NFS Export Name: Choose the appropriate field for your environment,and enter name of your mapped drive

l Path: Enter the Path for your shared directory.4. Click Save. The repository is now available in the Publish Report > Target drop down menu.

Below is an example for a CIFS Share on C:\publish\reports:

Restrictions for the target file share include:

page 96

l Mapped directories require write access enabled.l The mapped drives must be within the same domain as the SRM Profiler server.

See the KB article, Create a SRM Profiler Report, for more information on publishing reports.

MANAGE REPORTSThe following steps detail how to run, schedule, create or modify a report.

l Run a reportl Schedule a reportl Create a new reportl Delete a reportl Example report

1. Click Reports.2. Select My Reports, Shared Reports or Quick Reports.

RUN A REPORTThe Action column contains icons indicating the action the user has permission to perform.

l Selecting the My Reports option will allow the user to Edit, Delete, Schedule and Run any reportscreated by that user. A user may also Schedule or Run any report available when the SharedReports or Quick Reports options are selected.

Administrators always have full access to user-defined reports.

l Reports listed under the Quick Reports option are preformatted by SRM Profiler and cannot beedited or deleted by users or administrators. To take an action, click the icon next to the report youwant to run, schedule, modify or delete.

l To run a report, click the right arrow. A Run Report screen appears with multiple drop-down menusfor selecting the scope and output format.

You can only see devices that are in the same groups as you. The Groups drop-down is limitedto the groups that you are a member of, and the Devices drop-down is limited to the deviceswithin those groups.

SCHEDULE A REPORTUse the Report Scheduler to schedule a report:


page 97

https://support.solarwinds.com/Success_Center/Storage_Manager_(STM)/Create_a_report_for_SRM_with_Profiler

1. Click the Schedule icon in the Report List.

2. This action shows a list of available schedules and the reports assigned to each schedule. You canalso schedule reports directly from the Schedule List page.

3. Create a new schedule to assign this report to by clicking the New Schedule icon. This will take youto the Create Schedule page.

4. To assign this report to an existing schedule, click the Add icon for that schedule. This brings up theCreate Scheduled Report page.

5. To create or edit a schedule, choose the frequency and time of day you want the report to run.

Summary of options:

l Frequency: Daily, Weekly (pick one or more days), or Monthly (choose the 1st, 15th or the Last Dayof the Month)

l Time To Run: The time at which to execute the Reportl Recipients: Select the users who will be notified when this report is run. The users listed are SRMProfiler users. You can add external email addresses as well.

l Reports: Scheduled Reports assigned to this Schedulel Publish: How you want to publish the report when it is executed.l Email Report: Send the report in an email to all recipientsl Publish Report (Overwrite): Outputs to the same file name every time report is executedl Publish Report (Do Not Overwrite): Outputs to a file name plus a time stamp each time the report isexecuted

l Email: Choose whether all reports should be sent in one email, or broken up into individual emails.l Name: The name of the schedule

Published reports can be redirected to another location like Sharepoint, UNC etc., with the ‚'Target'option available in the Edit Schedule page. For this users must have full access to the share towhich the reports are to be redirected to. You must provide an email address to publish to a share.

REPORT SCHEDULE LIST

Clicking on the Report Schedules icon under the Reports folder in the Tree Menu brings up the ReportSchedules List page.

Here you can see a list of all schedules, what reports are assigned to each schedule, the schedulefrequency and the next run time.

EXPORTING REPORT DATA

You can export the data from the report in several ways.

page 98

l Email the report in HTML format.l CSV output, with the following additional choices.

When the second browser window opens, the report has the following features:

l Click a column header to sortl Click a chart icon to chart that columnl The header will scroll up and down with youl Totals at the bottom for that pagel Pagination for multiple pages of datal The ability to email the reportl The ability to close the report

Remember, users can only see devices that are in the same groups as the user. If a user isrestricted to just Windows devices then the Enterprise reports visible to the user will containinformation about Windows only, not Solaris. If there is no data for the report or the user does nothave the permissions to see available data, the report displays: 'There is no data for this report'.

CREATE A NEW REPORTTo create a new report, click through the menu tree down to My Reports. If you have not previously built acustom report, the message "There are no reports available" will appear on the screen.

1. Click New Report.

To edit an existing custom report, click the edit icon.

2. Choose the Scope of your report.For example, if you choose Enterprise, you can run reports that apply to all devices across theenterprise. If you choose Windows, you can only run Windows specific reports.

3. Select Report Type. The report type defines the types of data you want to report.4. Click Continue.5. Select the fields you want for your report.6. Click Continue.7. Select the sorting, filtering and permission structures for this report.

Structure Scenarios to consider:

l You may sort according to any chosen statistic in ascending or descending order. Once thereport is executed, you can dynamically change the sort.

l Filters allow you to include or exclude statistics based on standard filter criteria (like, not like,>, >=, etc.). You can apply more than one filter to a query.


page 99

l Rows per page set the default rows per page for this report. Permissions options includemyself (only I can run the report), Group (all users in the groups I am a member of), or All (allusers).

8. Click Continue.9. Enter a name for the report.10. Click Save. The report now appears on the My Reports list.

DELETE A REPORTTo delete a report, click the Delete icon (trash-can) to the right of the report name in a reports list.

If you click the Delete icon, a message appears asking you to confirm your selection. To delete the report,click OK.

You cannot delete a Shared Report that you have access to, nor a Quick Report.

EXAMPLE REPORTWhen you build a custom report, you are simply selecting the fields you want to see, in the order you wantto see them, and adding filters to narrow the results.

When the report is run you can narrow the results by selecting a particular set of devices, time period, andother variables.

For example, assume you wanted to find all the servers in your environment where the C:\ drive wasgreater than 90% full, and you want to understand how fast they are growing.

There is a template "Volume Usage Forecast" you can use as a starting point.

page 100

1. Go to Reports > My Reports and click New Report.2. Select the template you want to use.3. Select Enterprise > Storage > Volume Usage Forecast, and then click Continue:

4. Select the columns you want in the report and the order of those columns.5. Each template has defaults for the columns selected, the column order and the sort order.6. Remove the Eighty and Ninety percent columns by highlighting them and clicking the left arrow.

7. Select the sorts and filters for the report, allowing you to narrow the output to exactly what youwant.


page 101

l Enter the name of the report "C Drives Over 90 Percent" and in this case, you will leave the defaultsort (server, volume) in place. If you wanted to change the sort order, you can remove current sortsby highlighting them in the text box and clicking Delete Sort, and add new sorts by selecting theSort By field and order by clicking "Add Sort".

The order of the fields in text box is the order the sort are applied to the report.

8. Select the filters. In general, you can filter by any column in the report, and the options of the filterwill match the data type:

l Text Fields: like, not like, <, >, =, <=, >=, <>, in, not in

l Numeric Fields: like, not like, <, >, =, <=, >=, <>, in, not in

l Date Fields: <, >, =, <=, >=, <>, before, within

The basic query you will build is "Volume Name like C: AND % Used > 90". So for the first part select"Volume Name" and "like" and enter "%C:%" and then click "Add Filter" - you should see the filter appearin the text box. For "like" filters, make sure you add the "%" before and after the text.

Since this is the first filter, you can ignore AND/OR drop down.

9. For the second filer, choose "AND", "% Used", " > " and enter "90" and click Add Filter.

10. Select the following items:

page 102

l Time Zone: The default time zone of the report, which can be changed at run time.l Row per Page: The default rows per page.l Permissions: What users can see this report: Myself, Group (All users in my groups), All (everyone).

11. Save the report and your page should look like the following:

Available actions:

l Save Report - saves the report and returns to My Reports.l Save and Run - saves the report and takes you to the Run Report pagel Cancel - abort changes to the report and return to the My Reports list.

For this report, if you select Save and Run, and then run the report, the output looks like this (assuming youhave some C:\ drives over 90%).

You have the ability to group filters, so you can do "Find all (C: OR D:) drives that are over 90%".


page 103

Here are some ways users can leverage the reporter functionality:

l Identify problem areas before they become "problems" - busiest LUNs, fullest drives, busiest VM orESX, etc.

l Chargeback - charge users, departments, customers, etc. for the storage, backups or servers theyare using.

l Backup Compliance - identify full backups that have not been successful for more than 7 days.l User Quotas - identify users exceeding their storage quota

Using groupsThe Grouping functionality allows an administrator to define a logical organization and permissionstructure to the data that is gathered by SRM Profiler. A Group console can quickly show an overview of itsdevices as a whole, and serve as a quick link to those devices.

Grouping also determines the permissions for what a user can see. Users can only see devices with thesame group(s) permissions.

Groups are completely user-defined, and can be used to represent departments, projects, server types,and lines of business, operator assignments or any other category that is relevant to your specificorganization. When you are assigning devices, objects and users to groups, it affects SRM Profiler'sinterface in the following ways:

l Tree Menu: (The structure of the tree menu) Users will only see groups and devices in the treemenu that their permissions allow.

l Reports: The groups available when a report is executed or scheduled: Only the groups and devicesthe user has access will be available.

l Consoles: Console can quickly show an overview of its devices as a whole, and serve as a quick linkto those devices.

When you define a group, you can put different types of objects in them, which include:

l Backup Clientsl Server and NASl SANl Storage – Volume

page 104

l Userl Storage – Qtreel Storage – LUNl SAN Switch portsl VMware VMl VMware ESX

GROUP EXAMPLESOne way to think of a group is as a bucket. You place all the objects that logically belong together into asingle bucket and SRM Profiler will sort them into categories and determine permissions. The defaultcategories that SRM Profiler sorts these objects into are:

l Devices (all OS and NAS Devices)l SAN devices (all supported Storage Arrays, Generic SAN Arrays, and Fibre Channel Devices)l Storage Groups (File Systems and Shares)l Fibre Channel Portsl LUNs & Qtreesl VMware VMs & ESX

If a category does not have any objects, then that group will not be represented in the tree menu.

You may also assign an accounting code to each group. This function will allow you to see the accountingcode in some management reports.

l Devices may belong to multiple groups. For example, all NT servers to be assigned to the group,"All NT Servers" and, at the same time, some of those NT servers could also be grouped as"Finance" while others are grouped as "Sales."

l When you put a device into a group, it does not automatically add the file systems to the group.You must assign each file system individually. File systems can only be assigned to one group.

l When creating a device, if you do not associate it with a group you have defined, and then it will beassociated with the default group Unassigned. Once you have associated a device with at least onegroup, the association with the unassigned group is dropped.

l Only a user with administrator privileges can see the "Unassigned" group.

CREATING, EDITING, AND DELETING GROUPS

CREATE A NEWGROUP

1. Click Settings on the SRM Profiler website, and then select the Device Groups link under DeviceManagement.


page 105

2. Click Add Group on the Groups.3. Type the name of the new group in the Group Name field.4. Select from the available categories:

l Backup Client: All backup clients, including monitored and unmonitored devices (a monitoreddevice has an agent, an unmonitored device does not), not assigned to another group. BackupClients can belong to multiple groups.

l SAN: This function allows you to group SAN into logical groups for monitoring.l Servers & NAS: All OS and NAS devices defined on the Devices page. A device can belong to one ormore groups.

l Storage - Volume: All volumes (file systems) from all OS and NAS devices not assigned to anothergroup. This allows you to associate volumes into logical collections of storage independent of thedevice it resides (Note each volume in the assignment window shows the device name and volumename). This allows for easy chargeback reports as they show storage allocation and usagesummaries per group. These groups are also used in the Management reports to show allocatedand used space per group. Volumes & file systems can be assigned to more than one group.

l User: All the users defined in SRM Profiler. Administrators are always a member of every group.This function is done in the background automatically. If you remove an administrator from agroup and then save it, SRM Profiler will add it back automatically. Users can belong to one ormore groups.

l Storage - Qtree This function allows you to group Storage Qtrees into logical groups for monitoringand chargeback.

l SAN Switch - Ports: This function allows you to group SAN Switch Ports into logical groups formonitoring.

l Storage - LUN This function allows you to group Storage LUNs into logical groups for monitoringand chargeback.

l VMware VM This function allows you to group VMware VMs into logical groups for monitoring.l VMware ESX This function allows you to group VMware ESX into logical groups for monitoring.

User will have access only to the file system/shares/Qtrees in the group assigned to him.

5. To save the new group click Save. The group list will reappear with the new group in the list.6. To cancel creation of the new group, click the Cancel. The group list will reappear.7. To assign an object to a group, click the object in the Available box and click the down arrow and it

will move the object to the Selected box (and vice versa).8. To assign multiple objects, CTRL-click multiple objects in the Available box. The double arrows will

move all Available objects into the selected box (and vice versa).

If your lists of objects are long, you can filter for the items you want to find by using the Filter by RegularExpression box.

page 106

You can filter by the beginning letter by clicking it, or you can enter you own regular expression to find theobject you are looking for.

CREATE A NEW SUBGROUP

There are only two levels of groups for backup clients.

1. Click Add Sub Groups on the Groups screen.2. Choose the super group for this subgroup.

A subgroup cannot be a super group. Enter a name for the subgroup.

3. To assign a backup client to the group, select backup clients on Available box and click the arrow tomove it to the Selected box. To remove a backup client from a group, select backup clients on theSelected box and click the arrow to move it to the Available box. Same applies for the Userssection.

4. To save the new subgroup click Save. The group list reappears with the new group added.5. To cancel creation of the new subgroup, click Cancel. The group list reappears.

EDIT OR DELETE A GROUP

The following options are available for editing groups:

l Group Name: Name of groupl ChargeBack: Customer charges for resources used.l Group Description: Give description of the groupl Click on a category to add or remove Objects: Allows user to add or remove resources from groups

To delete a Group, click the Delete icon from the Group list.

CREATE, EDIT, AND DELETE FILE TYPE GROUPSThe File Type Grouping functionality allows an administrator to define a logical organized structure to thedata that is gathered by SRM Profiler.

The File Type Groups Page displays the existing File Type Group Names.

CREATE A FILE TYPE GROUP

1. Click Settings on the SRM Profiler website, and then select the File Type Groups link under DeviceManagement.

2. Click Add Group to add a new Group. The 'Add Group' console appears.l Group Name: Enter the name of the group.l Case-sensitive: Define whether the file names will be case-sensitive. If the box is checked, filenames with capital letters will be different than names with lower case letters.


page 107

l File Types: A list of file types (extensions) returned by the console. The files can be selected byusing filters based on starting letters, expression, or by adding a new file type.

3. After the file types have been selected from the available area, click the arrow to add them to theselected list.

4. Click Save. The File Type Group list reappears with the new group in the list.

EDIT AND DELETE A FILE TYPE GROUP

To edit a File Type Group, click the edit icon from the File Type Group list. This is the same console andfunctions as in Add File Type Group will appear.

To delete a File Type Group click the Delete icon from the File Type Group list.

Using rulesThe Rules section details the various rules you can create to achieve certain actions. After you havecreated a rule you must then apply the rule to a policy.

For general instructions, see Creating a new rule.

The types of rules you can create are:

l File analysis rulesl Threshold rulesl Windows event logs rulesl Directory analysis rulesl Managing rulesl Scheduled rulesl Asset change rulel Using external scripts

page 108

CREATE A NEW RULE

1. Navigate to Settings > All Rules.2. Click Add New Rule.3. Select one of the following:

4. Enter the necessary information, and then click Save.

FILE ANALYSIS RULESThe File Analysis Rule lets you define rules to provide detailed file information.

SRM Profiler currently limits the number of files returned to 5000 per target. You can subdivide thecurrent target by doing local or remote shares, leveraging the depth function, which automaticallysubdivides the target per subdirectory.

WHAT IS FILE ANALYSIS?

l Analyzes how you are using your file storagel Works on any formatted storage: Server, VM or NAS device

For more information see Setting up File Analysis.


page 109

WHAT DOES IT REPORT?

l Summary Informationl By Owner, Age and Typel Find specific files via File Rulesl File Information - Size, owner, access, creation, modification

These rules are applied to devices via the Policies menu under Settings.

A new Rule must be specified under a policy before it can be used to run a report.

SETTINGS

Rule Name Enter the name of the rule.

Find X Y fileswith

X represents the max number of files reported on. It is on a per file system/share basis. Yrepresents the limit type to be used in cases where more than max(X) number of files arefound. The choices are largest, oldest accessed and oldest modified.

Size If you leave the value set at 0, then all files will be evaluated, and considered potentiallyvalid, regardless of size. Otherwise, only files that are at least the selected size (specifiedin megabytes) will be evaluated and considered potentially valid.

AccessedAge

If you leave the value set at 0, then all files will be evaluated, and considered potentiallyvalid, regardless of access time. Otherwise, only files that are at least this age, in regardsto access time, will be evaluated and considered potentially valid.

Modified Age If you leave the value set at 0, then all files will be evaluated, and considered potentiallyvalid, regardless of modified time. Otherwise, only files that are at least this age, inregards to modified time, will be evaluated and considered potentially valid.

Created Age If you leave the value set at 0, then all files will be evaluated, and considered potentiallyvalid, regardless of created time. Otherwise, only files that are at least this age, in regardsto created time, will be evaluated and considered potentially valid.

File PathRegularExpression:

You can specify a regular expression (based on the Java implementation of regularexpressions) that all files must match, in regards to file name and path, in order to beevaluated and considered potentially valid. If nothing is specified, then all files areevaluated, and considered potentially valid.

Regex Examples:

l To Find files that have a date in their extension, e.g. 2006-09-20 :Create a Rule with the File Path Regular Expression .*[\d]{4}-[\d]{2}-[\d]{2}.* This returns files like "Localdevice_log.2007-09-04.txt" as well as files like"bookmarks-2007-10-01.html".

page 110

SETTINGS

l To Find only log files that have a date in their extension:Edit the File Path Regular Expression in (1) to .*log.[\d]{4}-[\d]{2}-[\d]{2}.* This will give just the log files with a date in the file name.

l To modify the search in (2) to exclude years ending in 6 e.g. 2006\Edit the File Path Regular Expression to .*log.[\d]{3}[0-5[7-9]]-[\d]{2}-[\d]{2}.*

l To Find files with extensions line ab5e1073_ad9b_48df_b07f_3e445b5a45cf.Create a Rule with the File Path Regular Expression .*[\w]{8}_[\w]{4}_[\w]{4}_[\w]{4}_[\w]{12}.*

l To Find files that start with the numbers 118:Create a Rule with the File Path Regular Expression .*118[\d]{7}.*

l Regular expression to exclude all ZIP Files:Create a Rule with the File Path Regular Expression .*(?i:(?<!\.zip))$

l Regular expression to exclude PST and OST files:Create a Rule with the File Path Regular Expression .*(?i:(?<!\.[op]st))$

File Types A list of file types (extensions) returned by the rule. The files can be selected by usingfilters based on starting letters, expression, or by adding a new file type.

Case-sensitive

Define whether the file names will be case-sensitive. If the box is checked, file nameswith capital letters will be different than names with lower case letters.

Click Save.

THRESHOLD RULESThe Threshold Rules page allows you to add thresholds for conditions and determine if scripts need to berun or SNMP traps sent.

To add or edit a Threshold Rule, navigate to Settings > Threshold Rules > Add New Rule > Threshold Rule.


page 111

The following descriptions detail the available options.

l Rule Name: The name you would like to give this rule.l Section: The section of the devices that you would like to monitor. This can be done across theEnterprise or by system type. The Section defines the scope of resources to which the rule applies.

l Category: The category you would like to monitor. The Category defines the metrics that can beapplied to the Section.

l Choose Instances: If applicable, the Choose Instances allows you to choose specific instances onwhich you can run the rule. Click on to add an instance to the selected list.

l Condition: The Condition defines the threshold you want to set. First select the field to monitor,then the condition, and then the value to evaluate the condition against.

l Duration: The duration that the condition must be true for the action to be taken. This is the lengthof time the condition must be met before the threshold is triggered.

l Choose Action: Allows you to assign an action to be taken if the threshold condition and durationoccur.

l Run Client Script: Enter the path and file name of your script. (client-side based).l Run Server Script: Choose from the scripts uploaded to the SRM Profiler server. (server-side based).l Send Trap: Send out SNMP trap.

After the rule is created, it must be added to the SRM Profiler Policies.

WINDOWS EVENT LOG RULESWindows Event Log rules allow you to receive alerts whenever an event takes place. After the rule iscreated, you must 'Push' the policy to begin receiving alerts.

To enable a Windows Event Log Rule:

page 112

1. Ensure that Event log monitoring is enabled.2. Go to Settings > Rules and add a new Windows Event Log rule.3. Go to Settings > Policies and add the rule to the policy that the Windows host(s) belongs to:

l Rule Name: The name of the Windows Event Logs rule.l Event Log: The log file you wish to monitor (Application, System).l Event Source: The type of event in the event log you wish to monitor.l Event ID: The event ID you wish to monitor.l Record and Notify: The types of events you would like to either record or be notified on.

DIRECTORY ANALYSIS RULEThe Directory Analysis rules allows you to specify certain criteria for identifying directories. Limit Sizewhich helps you minimize the impact to the database by selecting one of the following limit sizes: 10 / 20 /50 / 100 / 250 / 500. This will be the limit size per file system/share.

SETTINGS

Rule Name The name you would like to give this rule.

Limit Type In cases where the result set is larger than the value you selected for limit size, the resultset will be trimmed based on one of the following criteria, depending on which one youselect:

l Total directory count, including sub-directories (lowest values will be trimmed)l Total file count, including sub-directories (lowest values will be trimmed)l Total file size, including sub-directories (lowest values will be trimmed)l Access age, including sub-directories (latest values will be trimmed, i.e. oldestdirectories kept)

l Modified age, including sub-directories (latest values will be trimmed, i.e. oldestdirectories kept)

l Files percentage, including sub-directories (lowest values will be trimmed)l Total file count, current directory ONLY (lowest values will be trimmed)l Total file size, current directory ONLY (lowest values will be trimmed)l Access age, current directory ONLY (latest values will be trimmed, i.e. oldestdirectories kept)

l Modified age, current directory ONLY (latest values will be trimmed, i.e. oldestdirectories kept)

l Files percentage, current directory ONLY (lowest values will be trimmed)

Limit Size In order to minimize the impact to the database, you will be able to select one of thefollowing limit sizes: 10 / 20 / 50 / 100 / 250 / 500. This will be the limit size per filesystem/share.


page 113

SETTINGS

MinimumDirectoryCount

Numeric values that you would like to set in order to filter out directories that do notcontain at least X number of directories. This count includes sub-directories.

MinimumFile Count

Numeric values that you would like to set in order to filter out directories that do notcontain at least X number of files. This count includes sub-directories.

MinimumTotal FileSize in MB

A numeric value that you would like to set in order to filter out directories that do notcontain at least X number of megabytes of files. This count includes sub-directories.

MinimumAccess Agein Days

Numeric values that you would like to set in order to filter out directories that do notcontain files that are at least X number of days old in terms of access time. This can beused to find high level directories that have not been accessed in a very long time. Thiscount includes sub-directories.

MinimumModifiedAge inDays

A numeric value that you would like to set in order to filter out directories that do notcontain files that are at least X number of days old in terms of modified time. This can beused to find high level directories that have not been accessed in a very long time. Thiscount includes sub-directories.

MinimumTotal FileSizePercentage

Numeric values that you would like to set in order to filter out directories that do notcontain files totaling X percent of the parent directory, in terms of size. This count includessub-directories.

MinimumFile Count

Numeric values that you would like to set in order to filter out directories that do notcontain at least X number of files. This count is for the current directory only.

MinimumTotal FileSize in MB

A numeric value that you would like to set in order to filter out directories that do notcontain at least X number of megabytes of files. This count is for the current directory only.

MinimumAccess Agein Days

Numeric values that you would like to set in order to filter out directories that do notcontain files that are at least X number of days old in terms of access time. This can beused to find the exact directories that have not been accessed in a very long time, based onthe files they contain. This count is for the current directory only.

MinimumModifiedAge inDays

A numeric value that you would like to set in order to filter out directories that do notcontain files that are at least X number of days old in terms of modified time. This can beused to find the exact directories that have not been accessed in a very long time, based onthe files they contain. This count is for the current directory only.

Minimum Numeric values that you would like to set in order to filter out directories that do not

page 114

SETTINGS

Total FileSizePercentage

contain files totaling X percent of the parent directory, in terms of size. This count is for thecurrent directory only.

DirectoryPathRegularExpression

A regular expression that you can set in order to restrict the directories considered to asubset. For instance, if the user were only trying to find information about directories below"C:\winnt\", a regular expression could be added to restrict directories considered valid, tobe within "C:\winnt\", ignoring all others. If this option is left blank, all directories will beconsidered valid.

Report Generate a report that matches the rule.

ScheduletheselectedAction

Schedule the action you selected above.

MANAGE RULES

l Schedule Rulesl Asset Change Rule

The SRM Profiler server has the capability of taking actions based on rules.

The Menu will show different sections of types of rules that the user can create.

File Analysis Rules consist of:

l Windows Event Logs Rulesl Threshold Rulesl Directory Analysis Rulesl Scheduled Rules

To define a File Analysis Rule provide the following:

SETTINGS

RuleName

Enter the name of the rule.

Find the XY files with

X represents the max number of files reported on. It is on a per file system/share basis. Yrepresents the limit type to be used in cases where more than max(X) number of files arefound. The choices are largest, oldest accessed and oldest modified.


page 115

SETTINGS

Size of If you leave the value set at 0, then all files will be evaluated, and considered potentiallyvalid, regardless of size. Otherwise, only files that are at least the selected size (specified inmegabytes) will be evaluated and considered potentially valid.

AccessedAge

If you leave the value set at 0, then all files will be evaluated, and considered potentiallyvalid, regardless of access time. Otherwise, only files that are at least this age, in regards toaccess time, will be evaluated and considered potentially valid.

ModifiedAge:

If you leave the value set at 0, then all files will be evaluated, and considered potentiallyvalid, regardless of modified time. Otherwise, only files that are at least this age, in regardsto modified time, will be evaluated and considered potentially valid.

File PathRegularExpression

You can specify a regular expression (based on the Java implementation of regularexpressions) that all files must match, in regards to file name and path, in order to beevaluated and considered potentially valid. If nothing is specified, then all files areevaluated, and considered potentially valid.

Regex Examples:

l To find files that has a date in their extension, e.g. 2006-09-20:Create a Rule with the File Path Regular Expression .*[\d]{4}-[\d]{2}-[\d]{2}.* thisreturns files like "Localdevice_log.2007-09-04.txt" as well as files like "bookmarks-2007-10-01.html".

l To Find only log files that has a date in their extension:Edit the File Path Regular Expression in (1) to .*log.[\d]{4}-[\d]{2}-[\d]{2}.* this will givejust the log files with a date in the file name.

l To modify the search in (2) to exclude years ending in 6 e.g. 2006\Edit the File Path Regular Expression to .*log.[\d]{3}[0-5[7-9]]-[\d]{2}-[\d]{2}.*

l To Find files with extensions line ab5e1073_ad9b_48df_b07f_3e445b5a45cf.Create a Rule with the File Path Regular Expression .*[\w]{8}_[\w]{4}_[\w]{4}_[\w]{4}_[\w]{12}.*

l To Find files that start with the numbers 118:Create a Rule with the File Path Regular Expression .*118[\d]{7}.*

File Types A list of file types (extensions) returned by the rule. The files can be selected by using filtersbased on starting letters, expression, or by adding a new file type.

Case-sensitive

Define whether the file names will be case-sensitive. If the box is checked, file names withcapital letters will be different than names with lower case letters.

page 116

1. After the file types have been selected from the available area, click to add it to the selectedlist.

2. Next, the rule can be filtered by file owner.

3. Select from the available owners and click to add it to the selected list.

4. Click Save.

SCHEDULE RULESThe Schedule Rules page lets you execute a script on the device machines at a given schedule.

SETTINGS

Rule Name Enter a name for this rule.

Script From the drop down list, select a script that you want this rule to execute. To add a newscript, go to Administration > Scripts page.

Parameters If you would like to send any parameters to the script while executing, enter them here.

Schedule Select the schedule for this rule. The rule is executed on the device machines according tothis schedule.

ASSET CHANGE RULESThe Asset Change Rule page lets you execute a script on the device machines when any asset changeoccurs.

1. Provide the following:l Rule Name: The name you would like to give this rule.l Section: The section of the devices that you would like to monitor.l Category: The category you would like to monitor.l Property: The property you would like to select.

2. Select one of the following:l Run Client Script: Enter the path and file name of your script. (Client-side based).l Run Server Script: Choose from the scripts uploaded to the SRM Profiler server. (Server-sidebased).

l Send Trap: Send out SNMP trap.


page 117

USING EXTERNAL SCRIPTSSRM Profiler can execute external scripts. The Scripts window lists scripts uploaded to the SRM Profilerserver. Scripts can be uploaded and edited from this page.

Scripts can be dispatched and executed when a threshold condition is met, on a schedule, or when anasset change occurs.

l SRM Profiler requires scripts with the .bat or .sh file extensions.l SRM Profiler does not support scripts containing double quotes.

l Add a scriptl Edit a scriptl Use scripts

ADD A SCRIPT

1. Go to Settings > Scripts.2. Click Add, and then enter the following information:

l Script Name: Enter a name for the script.l Description: Enter a description for the script.l Upload: Click browse to select a script from the local machine to upload to the SRM Profilerserver.

3. Click Submit.

Scripts added to SRM Profiler are available from the Run Server Script menu when adding or editingcertain Rules.

EDIT A SCRIPTThe Scripts Window offers two editing options:

page 118

l Click Edit to modify the Script Name and the Description.l Click the File Name to edit the content of the script.

You can also Download and Delete the script from this window.

SRM Profiler does not support scripts containing double quotes.

USE SCRIPTSScripts are associated with Rules, and Rules are associated with Policies. To associate a script with a rule,do the following:

1. Create a .bat or .sh script file.2. Select the rule you want associated with your script. Add or Edit the rule to define when the script is

run, what script to run, and script parameters. Select Run a Client Script or Run a Server Script. Formore information, see the Example below.

3. Add the Rule to a Policy, and Push the Policy to Devices.

Example: When editing a Rule, choose the Run Server Script, choose your script from the drop down menu,and enter parameters if applicable. If you have more than one parameter, enter a space after eachparameter.


page 119

RUN CLIENT SCRIPT

Select Run Client Script to execute a script on the SRM Profiler agent. Add the path to the script whenchoosing this option. The script must reside on the same network as the SRM Profiler agent where thescript will be executed.

RUN SERVER SCRIPT

Select Run Server Script if your script is uploaded to the SRM Profiler server. Server scripts are invoked onthe agents that call the script. Parameters are added in the Set the Static Parameter for the script field. Ifyou have more than one parameter, enter a space after each parameter.

Use policies and set alerts in SRM ProfilerThe SRM Profiler server has the capability of configuring multiple agents at once using policies. Policiesconsists of Rules that contain configuration parameters for the devices.

Policies are intended for advanced users. Typically the default policies do not need to be changed. You canmake changes by clicking on the pencil icon.

An agent can belong to only one policy. If you move an agent from one policy to another, all settings(even ones set specifically for that agent) are overwritten to the values of the policy.

page 120

Protection: You can protect an agent from being updated by the policy setup push to preserve specialsetups on a specific agent.

For example: On a critical server you might want the performance interval to be 1 minute, but on otherservers you want the interval to be 5 minutes. To accomplish this configuration, you would define thepolicy setup performance frequency at 5 minutes and then use the Device Config icon to configure thecritical server to 1 minute. The configuration for the one agent is automatically "protected" and isunaffected by changes to the policy. This setting is only overwritten in two cases:

l If you select the Override Protection box when you configure a policy.l If you move the agent from one policy to another.

Override Protection: You can also override protection. When choosing the agents to push parameter(s) toyou can choose to override any protection on the agent.

This override is for all parameters you select on a push, not parameter by parameter (unless youpush them one at a time). So for the above example, if you want to change a parameter (forexample: Disk Usage threshold) on the protected agent, you could do so by selecting Yes for theOverride Protection on the Push screen.

Self-Configure: When a new agent registers it automatically adds itself to the configuration push list (for allparameters). This function allows you to quickly set up all your agents during installation. As soon as theSRM Profiler server is running you should configure Policy Setup parameters so any agents that self-register subsequently will have the configuration you want.

Monitoring: You can also monitor the push list to see the progress of your configuration. From the pushreport, you can see pending pushes, as well as failures.

Notification of Failures: If the server cannot push a configuration to a server, it will try once an hour fortwenty-four hours, and then abort the push. When it aborts, it also sends a trap to the Event Receiver,which can then notify you of the failure.

Additional information about policies is available at the following links:

l Data retention policyl Policy list pagel Create a policyl Edit a policyl Select rules

SET ALERTS IN SRMPROFILERProcess for creating alerts in SRM Profiler:


page 121

l Define a Rule. The rule could be a File Analysis Rule, Windows Event Log Rule, Threshold Rule,Directory Analysis Rule, Scheduled Rule or Asset Change Rule.

l If the rule condition is met, the agent sends a trap to the SRM Profiler server.l After the trap has been received by the SRM Profiler server, the resource or group and severity ischecked and if there is a match, an email is sent to the designated user.

The following example shows how to create a Threshold Rule in SRM Profiler and configuring of emailnotification.

Create a threshold rule:

1. Click Settings > Threshold Rules > Add New Rule > Threshold Rules.2. Create this rule for the resource (Section) and Category you want to alert on, and then click Save.

For more information, see Rules.

Assign the rule to the resources via Polices:

1. Click Settings > Policies.2. Edit the policy that applies to the rule created. For example, if this is a rule for a Netapp filer, edit

the NetApp Filer Policy. General threshold rules are in the OS Policy.3. Edit the Policy, and then click Rules.4. Move the new rule from Available to Selected and then click Save.5. Click Devices to verify that the Resources are assigned to this policy.6. When done, click Push. This action pushes the policy to the relevant agents and updates the

configuration files for that resource (NetApp in this example).

For more information, see Policies.

You can verify the progress of the configuration push by clicking the Push List Report link in the topright corner. This will show No Data if the push has worked for the resource. You can also verify ifany trap events are being received (assuming the thresholds have been meet) by going to the webconsole > Monitors > Event Monitor.

These events are sent to the server from the SRM Profiler agents when a threshold is met. They can beedited to change any details of the trap going forward. For example, if you're seeing an event as Critical,you can edit this to reduce its priority.

ALERT NOTIFICATIONS

After you have confirmed SRM Profiler is receiving traps, you can define which users will receive alertnotification emails.

page 122

1. Configure the SMTP server by clicking Settings > E-mail.2. Configure the User and email alerts in Settings > Manage Users.3. Edit the user.4. Define the Email Address.5. Click Add beside Notifications.6. Define which resource or group to apply to.7. Define who the emails are sent to and determine the severity level of the event being sent.

DATA RETENTION POLICIESData Retention Policies allow Administrators to define the duration that they wish to keep each kind ofdata. The policies are executed once every twenty-four hours by the SRM Profiler Maintenance service.Data Retention Policies are divided into the following categories:

l Backupl Databasel Eventsl Operating Systemsl SMI-Sl SNMP/FC/HBAl Systeml Virtualization

These categories are subdivided into types of data. Each type of data has a retention policy for raw andhourly data. Raw data is collected in defined time intervals. For example, raw data for storage arrays iscollected every 15 minutes. Hourly data is the average of the raw data over an hourly interval.

The Data Retention Policy is responsible for maintaining the minimum data needed for data roll-up. Dataroll-up is a process of calculating the average of the raw data for use in performance tables.

For example, performance data is collected for a device every 2 minutes. When an hour of performancedata is collected, data roll-up calculates the average of the last 30 data points (the last hour of data) andinserts it into a summary table of HOURLY data. Once the device collects 24 hours of data, data roll-upcalculates the average of the last 24 HOURLY data points from the summary table and inserts it into asummary table of DAILY data. Once the device collects 31 days of data, data roll-up calculates the averageof last 31 DAILY data points (last one month of data) from the summary table and inserts it into thesummary table of MONTHLY data.

CALCULATING DATA RETENTION DURATION

The table below lists the number of days data is kept for each Data Retention Policy setting.

Data Retention Policy Setting Number of days data kept for Performance tables


page 123

1 day 1 day + x

7 days 7 days + x

1 month 1 month + x

2 months 2 months + x



1 year 12 months + x

Forever Data is kept indefinitely

The value of x depends on the day of the month the Data Retention Policy is run and 1 day<=x<=31 days.

For example: If you configured Settings > SRM Profiler server > Data Retention > Operating Systems > DiskUsage > Raw Data for one month, and if the Data Retention Policy is run on the 15th of December, then theData Retention Policy retains data for the month of November + 15 days of December. In this example, 45days of data are kept in the Performance table.

POLICIESThe Policies page is accessed via Settings > Policies, and allows you to add, edit, delete, or push allconfiguration parameters out to devices configured in the policy.

l To create a new policy, click Add New Policy and follow the onscreen instructions.l To export policies, click Export.The rules and policies are saved as a SQL file. A simple "Execute this SQL file against the database"is done to import the settings back when needed.

l To edit the policy, click the Edit icon.After the policy has been edited you must push the policy out.

l To push the policy to the configured devices, click the Policy (P)icon.l For a push list report, select Push List Report.

CREATE A POLICY

1. Click New Policy.2. Enter the necessary information:

l Policy Class: The type of policy that you are creating (OS, Magnitude, etc.)l Base Policy on: Use a predefined policy as a template for the design of the new policy.l Name:The name that is assigned to the policy.

3. Click Save.4. Define any necessary configurations, and then click Push.

page 124

The Push List Report link displays a list of pushed agents/modules/policies.

EDIT A POLICY

1. Click on the Settings link in the left navigation tree.2. Under Device Management, select Policies.

The Menu will show different sections of parameters that you can edit.

3. Click on the edit policy icon for the policy you want to edit. Once you select the desired report it willdisplay a menu with all of the option available for modification. The following example shows the"Default SMI-S Policy (SMI-S)."

l Rules – Choose which rules to include in this policyl Devices – Choose which devices to include in this policyl SMI-S Configuration – Set the configuration parameters for a Storage Array Device


page 125

4. Click Push. This will allow the policy changes to be populated to all the proxy agents listed in the"Devices" option of the policy.

After clicking Push, you are returned to the "Policy" web page. Click Push List Report to displayany pending reports waiting to be pushed to proxy agents.

SELECT RULES FOR YOUR POLICYSelect from the available rules for your policy, and then push the policy to a group of devices. The rules areactivated for those devices, and when the condition of the rule is met, a trap or script is triggered.

For the example threshold rule in the image below, if the VMware memory usage is >= 85% for 10 minutes,then an event trap is triggered.

See the Using Rules sections for more information on how to set up Rules and Scripts in SRM Profiler.

page 126

Add devicesThe All Devices page displays all the OS and NAS devices that are added to SRM Profiler monitoring.

See Configuring devices for details on adding, editing, and deleting devices as well as details on activatingand deactivating polling.

Find more details on adding and configuring your devices in the following sections:

l Adding storage arraysl Adding Fibre Channel devicesl Adding VMware monitoringl Virtualization dashboardl Adding application monitoringl SnapMirror monitorl Setting up file analysis

Add and configure devices

ADD A DEVICE

1. Click the Settings link under the left tree navigation.2. Click All Devices under Device Management.3. The All Devices page displays a listing of all devices currently defined in SRM Profiler.4. Add a device by selecting the device and clicking Add.5. After entering the necessary information, the device appears in the device list for management.6. Click the appropriate icon to edit, delete, configure Agents, verify the agent health, or download

support bundles for the selected device.

EDIT A DEVICE

1. Click the Edit icon.2. Enter new information in the desired fields.3. Click Save.

CHANGE THE IP ADDRESS FOR ANY AGENTS

1. Set the self register option as 'no' in Server setup page.2. Change the IP Address in the Agent.3. Change the IP Address in SRM Profiler server.


page 127

4. Set the self-register option as 'yes' in Server setup page.

DELETE A DEVICETo delete a device from SRM Profiler, return to the device screen and click the trash can icon. A dialog boxwill appear requesting confirmation.

ACTIVATE/DEACTIVATE POLLING

From the Edit screen verify that the Active checkbox is checked.

For SRM Profiler to poll and collect data from a device; the Active checkbox should be checked. Similarly, tostop SRM Profiler from collecting or polling data from a device, uncheck the active box. The change willtake effect at the next scheduled collection time.

Even when a device is marked inactive, you can still change the agent's configuration, the agent willcontinue to send traps, and you can still view data about that device.

Add storage arraysSRM Profiler can monitor arrays from different vendors. Find vendor-specific instructions for adding yourarray to SRM Profiler.

If there is a firewall between your SRM Profiler agent and your SMI-S provider, you must open HTTPPort 5988 or HTTPS Port 5989 so SRM Profiler can collect data from your configured devices. For acomplete listing of SMI-S vendors supported see SMI-S Vendor Support Matrix.

l Using the Add a Device Wizard provides guidance on adding arrays that use SMI-S providersl Troubleshoot with the Add a Device wizard provides details on error messages you mightencounter when using the Add a Device Wizard.

SRM Profiler can monitor the following Storage Array types:

l 3PARl Dell Compellentl Dell Equalogicl Dell MD3xxxl EMC Celeral EMC Isilonl EMC Symmetrix, DMX, VMAXl EMC VNX/CLARiiONl Hitachi Data Systems (HDS)l HP EVA

page 128

http://thwack.solarwinds.com/community/cloud-virtualization-storage_tht/smi-s-vendor-reference

l HP Lefthand P4000l HP XPl IBM DS3xxx, DS4xxx, and DS5xxxl IBM DS6xxx, DS8xxxl IBM ESSl IBM N-Series Operations Managerl IBM N-Seriesl IBM SVC, V7000l IBM XIVl NetApp E-Series LSIl NetApp filerl NetAPP Operations Managerl OnStorl Pillarl Sun StorageTek 2xxx, 6xxx and FLX Seriesl Sun StorageTek 99xx Seriesl Xiotech Emprise 7000l Xiotech Magnitude 3D 3xxxl Xiotech Magnitude 3D 4000

USE THE ADD A DEVICE WIZARDSRM Profiler makes adding storage devices easy. Enter the IP address of the array provider, and the wizardwalks you through adding your array.

If there is a firewall between your SRM Profiler agent and your SMI-S provider, you must open HTTPPort 5988 or HTTPS Port 5989 so SRM Profiler can collect data from your configured devices.


page 129

1. From the Getting Started page, click Add More in the Storage Arrays section, and choose your arrayfrom the drop-down menu.

2. Enter the Provider IP Address, Provider Admin Username, and Provider Password, and then clickTest Connection, or choose an existing provider, and then click Test Connection.

3. Click Next.The Assign Storage Arrays window lists all arrays found on the provider. Each array is listed with thearray name configured in the provider, the array type, the number of disks in the array, and theagent to which the array is assigned. The overall License Usage for all arrays is provided.

page 130

4. Select the box next to each array you want to add, and then click Assign to Agent. You can choosemultiple arrays.

5. From the drop down menu, select the agent to which you want to assign the array, and then clickAssign to Agent.

l Each agent in the Select Agent list displays the number of disks the agent is monitoring.l Arrays with disks falling within the allowed license count can be assigned.l The total of all disks in the selected arrays must be within the allowed license count.

6. In the Node(s) assigned successfully window, click OK.7. When all agents are assigned, click Finish.

8. Confirm the arrays are added by checking the SAN Groups section in the left-hand navigation:


page 131

TROUBLESHOOTWITH THE ADD A DEVICE WIZARDThe Add a Device wizard provides error messages for common problems encountered when adding anarray to SRM Profiler.

THE PROVIDER FOR THIS ARRAY IS NOT RESPONDING

l Make sure you are using the correct Provider IP address and you have the correct credentials.l Make sure the network connection between the SRM Profiler server and provider is good. Fordetails on testing the connection, see Make sure the network connection between the Agent andProvider on port x or y is good.

l See the article Restarting the SMI-S Provider on Storage Array for information on restarting yourarray provider.

l Use manual configuration.

THE PROVIDER REJECTED YOUR LOGIN CREDENTIALS

This message indicates a problem with the SMI-S provider username or password. Check your credentials.

THE PROVIDER IS RESPONDINGWITH A NAMESPACE DIFFERENT THAN THEARRAY YOU ARE TRYING TO CONFIGURE

l Another provider is listening on the IP address and port you entered for your array.l Validate that you are using the correct provider IP address.l Validate that your array provider is listening on the default ports 5988 or 5989. If not, use themanual device creation to add your array.

page 132

http://knowledgebase.solarwinds.com/kb/questions/4022/Make+sure+the+network+connection+between+the+Agent+and+Provider+on+port+x+or+y+is+good

http://knowledgebase.solarwinds.com/kb/questions/4022/Make+sure+the+network+connection+between+the+Agent+and+Provider+on+port+x+or+y+is+good

http://knowledgebase.solarwinds.com/kb/questions/4023/Restarting+the+SMI-S+Provider+on+Storage+Arrays

THE PROVIDER DOES NOT HAVE ANY ARRAYS CONFIGURED

Your array provider is installed but your array is not assigned. Add your array to the array provider. Forassistance adding your array to the provider, check your array documentation or refer to you arrayadministrator.

ARRAYSWITH NO ASSIGNED AGENTS

The Arrays with no Assigned Agents message appears when arrays are found on the provider but are notassigned to an agent. SRM Profiler can only report on arrays that are assigned to an agent. Click Canceland follow the Assign to Agent instructions.

If there is a firewall between your SRM Profiler server and your SMI-S provider you must open ports5988 and 5989 so the SRM Profiler discovery can locate the SAN devices configured in the SMI-Sprovider.

3PARFind the information you need to add a 3PAR array to SRM Profiler. This section includes what you needbefore you begin, instructions on using the Add a Device Wizard, and guidance for resolving thetroubleshooting messages you might encounter.

BEFORE YOU BEGIN

l The SMI-S provider is embedded in the 3PAR array. There is no need to install a 3 PAR Provider.

By default the 3PAR SMI-S Provider is disabled and must be enabled by an administratorbefore SRM Profiler can monitor your 3PAR array. For more information, see the Enabling the3PAR SMI-S Provider or contact your 3PAR vendor for support.

l The 3PAR InformOS should be 2.3.1 or later


page 133

https://support.solarwinds.com/Success_Center/Storage_Manager_(STM)/SRM_Profiler/0300-Appendices/0030-Configuring_storage_arrays/0010-3PAR_Provider


l Before adding your 3PAR array to SRM Profiler, you must collect the following information:l Provider IP Address: IP address of the SMI-S providerl Provider Admin Username: The Administrator Username for the array you want to monitorl Provider Admin Password: The Administrator Password for the array you want to monitor

ADD THE ARRAY

Use the Add a Device wizard to add a 3PAR array to the SRM Profiler.

TROUBLESHOOTWITH THE ADD A DEVICEWIZARD

Troubleshoot with the Add a Device wizard provides details and guidance about the error messages youmight encounter.

MANUAL CONFIGURATION

Use the manual configuration if you must specify parameters that are not available from the Add a DeviceWizard.

1. In Step 1 of the Add a Device Wizard, select 3PAR.2. From the Add a Device – 3PAR window, click the Manual Configuration link.3. In the Create New Device for Agent: Storage Array window provide the following information:

a. Server IP Address: From the drop down menu, select the SRM Profiler agent you want tomonitor your array.

b. Device Display Name: Enter a meaningful name for your array.c. Storage Array Type: Set to Storage Array 3PAR.d. Active: Keep this box checked. Clearing this check box stops data collection for your array.e. Click Next.

4. In the Configure Device window, provide the values for the following fields.l Status : Select On.l User Name : Enter the user name used to access the providerl Password : Enter the password used to access the provider.l Provider IP Address : Enter the IP address of the providerl Node WWN : Enter the 3PAR identifier.

Other parameters are editable from this window. Make changes only if you are sure of theparameter value, otherwise leave the default value.

l Click Test to test the connectivity between the agent and the array's SMI-S provider. You mustenter the username, password, and provider IP before you can test the connection.

l Click Save to save the configuration and push it to the agent to begin monitoring the array.

page 134

ADDITIONAL INFORMATION

Versions/Models All F Class and T Class InForm OS 2.3.1 and higher

Features Asset

Storage

Performance

Requires SRMProfiler agent?

Yes

Prerequisitesl IP Address of the 3PAR storage arrayl SMI-S provider is embedded on the storage array. The provider must bestarted prior to connecting to it. Login to the CLI on the array and run"startcim".

l Type: "showcim" to confirm Inform OS versionl Identifier– Type:"showport", Node_wwn is the identifierl Username and Password to the array

Credentials Account and password are stored in SRM Profiler database and configuration fileson SRM Profiler proxy agent using custom encryption


Ports Used Configurable: 5988 (HTTP) or 5989 (HTTPS) used by 3PAR provider.

Communicationl Can be HTTP/HTTPS between SRM Profiler proxy agent and 3PAR SMI-Sprovider.

Installationl Configuring a 3PAR device

Requires a SRMProfiler proxyagent?

Yes – Windows or Linux

DELL COMPELLENTFind the information you need to add your EMC array to SRM Profiler. Below are details about what youneed before you begin, instructions on using the Add a Device Wizard, and guidance for resolving thetroubleshooting messages you might encounter.


page 135

BEFORE YOU BEGIN

l The SMI-S provider for the Dell Compellent array is contained in the Enterprise Manager asillustrated in the diagram below. Before SRM Profiler can monitor you Dell Compellent array, theSMI-S provider must be set up either during the Enterprise Manager installation or at a later timethrough the Enterprise Manager interface.

l The Dell Compellent Provider knowledge base article contains frequently asked questions andguidance on configuring the Dell Compellent provider and creating a user account in the EnterpriseManager. Or contact your Dell Compellent vendor for SMI-S provider support.

l Before adding your Dell Compellent array to SRM Profiler, you must collect the information listedin the table below.

Provider IP address IP Address/Hostname of the Dell Compellent Storage Center

Provider Admin Username The Administrator Username for the provider IP

Provider Admin Password The Administrator Password for the provider IP.

Dell Compellent does not allow special characters in thepassword.

ADD THE ARRAY

Use the Add a Device Wizard to add your Dell Compellent array to SRM Profiler

SRM Profiler provides no mapping between block storage and file systems.





page 136

https://support.solarwinds.com/Success_Center/Storage_Manager_(STM)/SRM_Profiler/0300-Appendices/0030-Configuring_storage_arrays/0020-Dell_Compellent

1. In step 1 of the Add a Device Wizard , choose Dell Compellent.2. From the Add a Device – Dell Compellent window, click the Manual Configuration link.3. In the Create New Device for Agent: Storage Array window, provide the following information:


b. Device Display Name: Enter a meaningful name for your array.c. Storage Array Type: Set to Storage Array Dell Compellent.d. Active: Keep this box checked. Clearing this check box stops data collection for your array.e. Click Next.

4. In the Configure Device window, provide the values for the following fields.

l Status: Select On.l User Name: Enter the user name used to access the provider.l Password: Enter the password used to access the provider.l Provider IP Address: Enter the IP address of the provider.l Storage Center: Enter the IP address of the Dell Compellent.


5. Click Test to test the connectivity between the agent and the array's SMI-S provider. You must enterthe username, password, and provider IP before you can test the connection.

6. Click Save to save the configuration and push it to the agent to begin monitoring the array.


Versions/Models Storage Center 6.0

Features Asset

Storage

Performance


No agent installed on array

Prerequisitesl IP Address/Hostname of the Dell Compellent Storage Centerl Username and Password of Provider IPl Provider CIMOM Name space & Vendor Name space (e.g)/root/pg_interop

All these info automatically obtained using 5.3.0's Add a Device option.


page 137


Credentials Account and passwords are stored in SRM Profiler database and configuration fileson SRM Profiler proxy agent using custom encryption

Read/WriteActions

Read Only

Ports Used Configurable: 5988 (HTTP) or 5989 (HTTPS) used by Dell Compellent provider.

Communication Can be HTTP/HTTPS between SRM Profiler proxy agent and Dell Compellent provider.

You can verify the connection of provider through your TestProvider Tool[Administrator mode] and execute the following commands to get thetestprovideroutput file.

1. Command: ein / ClassName:CIM_StatisticsCollection2. Command: ein / ClassName:CIM_HostedCollection3. Command: ein / ClassName:CIM_StoragePool4. Command: ein / ClassName:CIM_StorageVolume



DELL EQUALOGICFind details about adding a Dell Equalogic array to SRM Profiler. This section includes what you needbefore you begin, details about adding your array, and guidance for configuring your array.

BEFORE YOU BEGIN

l Your array must be installed and running before it can be added to SRM Profiler. Contact your arrayvendor for additional support on installing and troubleshooting your array.

l Get the IP address of the array. Refer to your array administrator or your array documentation withquestions about obtaining this information.

ADD THE ARRAY

When adding a device, choose Dell Equalogic from the Choose your Array Type menu. Click OK.

Complete the fields in the Create New device for Agent: EqualLogic PS Series.

1. Select Agent: Select the SRM Profiler agent you want to monitor your array.2. IP Address: Enter the IP address of your array.3. Active: Keep this box checked. Clearing this check box stops data collection for your array.

page 138

4. Click Next.

CONFIGURE THE ARRAY

1. Click Test to confirm the default values are working. The test can take up to 90 seconds.2. Click Show Advanced Fields to customize your array configuration. Click Test to confirm the

connection. The test can take up to 90 seconds.3. When the Test Results show successfully connected, save your configuration.


Versions/Models 4.x

Features Asset

Storage

Performance

Requires SRM Profiler agent? No agent installed on array

Prerequisitesl IP Address of the storage arrayl Read-only SNMP version 1 community string for theEqualLogic group

Credentialsl UNIX - Run as rootl Windows - Local System account/Domain Account


Ports Used 161 (UDP) on the EqualLogic Group IP

Communication See the SRM Profiler Ports section below.

Requires a SRM Profiler Proxyagent?

Yes –Windows or Linux

DELL MD3XXXFind the information you need to add your Dell MD3xxx array to SRM Profiler. Below are details about whatyou need before you begin, instructions on using the Add a Device Wizard, and guidance for resolving thetroubleshooting messages you might encounter.


page 139

BEFORE YOU BEGIN

l An SMI-S Provider must be installed and configured before SRM Profiler can monitor your DellMD3xxx array. The Dell MD3xxx array requires the installation of a separate SMI-S provider asillustrated in the diagram below.

l See the Provider article for details on downloading and installing the provider for your Dell MD3xxxarray. Or contact your Dell MD3xxx vendor for additional SMI-S provider support.

l Before adding your Dell MD3xxx array to SRM Profiler, you must collect the information listed inthe table below.


Provider IP address IP address of the SMI-S provider

Provider Admin Username The Administrator Username for the SMI-S provider

Provider Admin Password The Administrator Password for the SMI-S provider

ADD THE ARRAY

Use the Add a Device Wizard to add your Dell MD3xxx array to SRM Profiler





page 140

https://support.solarwinds.com/Success_Center/Storage_Manager_(STM)/SRM_Profiler/0300-Appendices/0030-Configuring_storage_arrays/0100-NetApp_E-Series_LSI_Provider

1. In step 1 of the Add a Device Wizard choose Dell MD3xxx.2. From the Add a Device – Dell MDxxx window, click the Manual Configuration link.3. In the Create New Device for Agent: Storage Array window, provide the following information:


b. Device Display Name: Enter a meaningful name for your array.c. Storage Array Type: Set to Storage Array Dell MD3K series..d. Active: Keep this box checked. Clearing this check box stops data collection for your array.e. Click Next.

4. In the Configure Device window, provide the values for the following fields.l Status: Select On.l User Name: Enter the user name used to access the provider.l Password: Enter the password used to access the provider.l Provider IP Address: Enter the IP address of the provider.l Identifier: Enter the array identifier (the WWN of the MD3K array).




EMC CELERRAFind details about adding an EMC Celerra array to SRM Profiler. This section includes what you needbefore you begin, details about adding your array, and guidance for configuring your array.

BEFORE YOU BEGIN


l You need the IP address of your array. Refer to your array administrator or your arraydocumentation for questions about obtaining this IP address.

ADD THE ARRAY

When adding a device, choose EMC Celerra from the Choose your Array Type menu. Click OK.

Complete the fields in the Create New device for Agent: EMC Celerra


page 141

l UNIX Device List: Select a UNIX or Linux server to retrieve the NFS shares exposed by the NASdevice.

l Control Station IP Address: Enter the IP Address of the Celerra control station.l Device Display Name: Enter a display name for this resource.l Control Station Username: Enter name of the user with permissions to log into the control station.l Control Station Password: Enter the password for the user with permissions to log into the controlstation.

l TCP Dump: Control Station Root Password: Enter the password of the root user with permissions tolog into the control station

l TCP Dump Data Mover IP Address: Enter the IP Address of a data mover that is chosen to storetemporary files. The user defined above must have access to this file system.

l TCP Dump: Data Mover File system: Enter the name of the file system chosen to store temporaryfiles. The user defined above must have access to this file system.

l TCP Dump: Access Path to Data Mover: Specify the UNC path (Windows) or mount point(Unix/Linux) to the Data Mover file system. For example, \\data_mover_share for Windows, and/mount_point_to_data_mover for Unix/Linux.

l Active: Keep this box checked. Clearing this check box stops data collection for your array.

CONFIGURE THE ARRAY

l In the Configure Device window, click Test to confirm the default values are working.l Click Show Advanced Fields to customize your array configuration. Click Test to confirm theconfiguration is working.

l When the Test Results show Successfully connected, save your configuration to begin monitoringthe array.


Versions/Models NS Series

Features Asset

Storage

Performance

VDMs

Data Classification (File Analysis)


No

Prerequisitesl nasadmin login or equivalentl Same login for all Control Stations; passwords can be different

page 142


l SSH connectivity between SRM Profiler server and EMC Control Station

Credentials Account and password are stored in SRM Profiler database and configurationfiles on SRM Profiler proxy agent using custom encryption


Ports Used Non-Configurable: 22 on the Control station

Communication SSH between SRM Profiler server and each EMC Control Station

Data Classificationl Occurs via SRM Profiler proxy agent.l CIFS Shares require a SRM Profiler Windows Agent and domain account toaccess the shares being analyzed

l NFS Shares require a SRM Profiler UNIX Agent and root access to sharesbeing analyzed.


l Yes – via SRM Profiler server

EMC ISILONFind details about adding an EMC Isilon array to SRM Profiler. This section includes what you need beforeyou begin, details about adding your array, and guidance for configuring your array.

BEFORE YOU BEGIN

Your array must be installed and running before it can be added to SRM Profiler. Contact your arrayvendor for additional support on installing and troubleshooting your array.

Collect the information in the following table:


IP Address IP address of the EMC Isilon cluster.

SNMP community string The SNMP community string is configured on the EMC Isilon array.

Refer to your array administrator or your array documentation with questions about obtaining thisinformation.

ADD THE ARRAY

When adding a device, choose EMC Isilon from the Choose your Array Type menu. Click OK.

Fill in the required fields in the Create New Device Agent: EMC Isilon.


page 143

l Select Agent: Select the SRM Profiler agent you want to monitor your array.l Windows Device List: Select a Windows server to retrieve the CIFS shares exposed by the NASdevise.

l UNIX Device List: Select a Unix or Linux server to retrieve the NFS shares exposed by the NASdevise.

l IP Address: Enter the IP address of your EMC Isilon array.l Device Display Name: Enter a descriptive name for your device. This will be displayed within SRMProfiler.

l Active: Keep this box checked. Clearing this check box stops data collection for your array.

CONFIGURE THE ARRAY

l Click Test to confirm the default values are working. The test can take up to 90 seconds.l Click Show Advanced Fields to customize your array configuration. Click Test to confirm theconnection. The test can take up to 90 seconds.

l When the Test Results show Successfully connected, save your configuration to begin monitoringthe array.

EMC SYMMETRIX, SYMMETRIX DMX, SYMMETRIX VMAXFind the information you need to add your EMC array to SRM Profiler. This section provides details aboutwhat you need before you begin, instructions on using the Add a Device Wizard, and guidance forresolving the troubleshooting messages you might encounter: Use these instructions for these EMC arrays:

l EMC Symmetrix arrayl Symmetrix DMX arrayl Symmetrix VMAX array

BEFORE YOU BEGIN

l An SMI-S provider must be installed and configured before SRM Profiler can monitor yourSymmetrix, DMX, and VMAX arrays. The EMC provider is a separate piece of software as illustratedin the diagram below.

page 144

l See the EMC Provider article for information on downloading, installing, and configuring thesoftware for this provider. Or contact your EMC vendor for additional SMI-S provider support.

l Collect the information listed in the table below before adding your array to SRM Profiler.

SETTINGS


Provider Admin Username The Administrator Username for the EMC provider

Provider Admin Password The Administrator Password for the EMC provider

ADD THE ARRAY

Use the Add a Device Wizard to add your array to SRM Profiler



Troubleshoot with the Add a Device wizard provides details and guidance about the error messages youmight encounter



1. In step 1 of the Add a Device Wizard, select EMC Symmetrix, DMX, VMAX.2. From the Add a Device – EMC Symmetrix, DMX, VMAX window, click the Manual Configuration link.3. In the Create New Device for Agent: Storage Array window, provide the following information:


b. Device Display Name: Enter a meaningful name for your array.c. Storage Array Type: Set to Storage Array EMC Symmetrix..d. Active: Keep this box checked. Clearing this check box stops data collection for your array.e. Click Next.


page 145

https://support.solarwinds.com/Success_Center/Storage_Manager_(STM)/SRM_Profiler/0300-Appendices/0030-Configuring_storage_arrays/0030-EMC_Provider_and_Solutions_Enabler_Appliance_VNX_CLARiiON_Symmetrix_VMAX


l Status: Select On.l User Name: Enter the user name used to access the provider.l Password: Enter the password used to access the provider.l Provider IP Address: Enter the IP address of the provider.l Serial No: Enter the array identifier (the serial number of the Symmetrix/DMX array).


l Click Test to test the connectivity between the agent and the array's SMI-S provider. You must enterthe username, password, and provider IP before you can test the connection.


EMC VNX/CLARIIONFind details about adding an EMC VNX/CLARiiON array to SRM Profiler. This section includes what youneed before you begin, details about adding your array, and guidance for configuring your array.

BEFORE YOU BEGIN

l An SMI-S provider must be installed and configured before SRM Profiler can monitor yourVNX/CLARiiON array. The EMC provider is a separate piece of software as illustrated in the diagrambelow.

l See the EMC Provider section for information on downloading and installing the software for thisprovider. Or contact your EMC vendor for additional SMI-S provider support.

l Collect the information listed in the table below before adding your array to SRM Profiler.

SETTINGS


Provider Admin Username The Administrator Username for the EMC provider

Provider Admin Password The Administrator Password for the EMC provider

page 146


ADD THE ARRAY

Use the Add a Device Wizard to add your array to SRM Profiler.

Note: SRM Profiler provides no mapping between block storage and file systems.





l In step 1 of the Add a Device Wizard , choose EMC VNX/CLARiiON.l From the Add a Device – EMC VNX/CLARiiON window, click the Manual Configuration link.l In the Create New Device for Agent: Storage Array window, provide the following information:

l Server IP Address: From the drop down menu, select the SRM Profiler agent you want tomonitor your array.

l Device Display Name: Enter a meaningful name for your array.l Storage Array Type: Set to Storage Array EMC VNX/CLARiiON..l Active: Keep this box checked. Clearing this check box stops data collection for your array.l Click Next.

l In the Configure Device window, provide the values for the following fields.l Status: Select On.l User Name: Enter the user name used to access the provider.l Password: Enter the password used to access the provider.l Provider IP Address: Enter the IP address of the provider.l Serial No: Enter the array identifier (the serial number of the VNX/CLARiiON array).

Other parameters are editable from this window. Make changes only if you are sure of aparameter value, otherwise leave the default value.

l Click Test to test the connectivity between the agent and the array's SMI-S provider. You must enterthe username, password, and provider IP before you can test the connection.



Versions/Models All

Features Asset


page 147


Storage

Performance


No agent installed on array.

Prerequisitesl IP Addresses of Controller A (SPA) and Controller B (SPB)l Identify firmware/Flare code of array and confirm it is compatible with latestSMI-S provider. *Some older firmware is only compatible with older SMI-Sprovider versions.

l If the array has Flare Code 26 it requires EMC SMIKit 6.4.2 (Provider 3.2.2) andhigher

l Install EMC Solutions Enabler with SMI-S on a Windows/Linux server with IPconnectivity to the array controllers.

l User account on Unisphere with admin/manager privileges on the CX arrayl For each CX, enable "Statistics Logging" for all storage processors viaUnisphere

l If SMI-S provider is on a server connected to the SAN being monitored seeFAQ-92.

CX600 arrays – require a Flare code higher than 16 (2.16.x.x.x) for data tobe gathered using SMI-S

Credentials Account and password are stored in SRM Profiler database and configuration files onSRM Profiler proxy agent using custom encryption

Read/WriteActions

Read Only

Ports Usedl Configurable: 5988 (HTTP) or 5989 (HTTPS) used by EMC Solutions Enablerl Non-configurable: TCP Port 443 bi-direction between provider andVNX/Clariion.

Communicationl See the SRM Profiler Ports section below.l Can be HTTP/HTTPS between SRM Profiler proxy agent and EMC SolutionsEnabler



page 148

HITACHI DATA SYSTEMS (HDS)Find the information you need to add your Hitachi Data Systems (HDS) array to SRM Profiler. This sectionprovides details about what you need before you begin, instructions on using the Add a Device Wizard,and guidance for resolving the troubleshooting messages you might encounter:

BEFORE YOU BEGIN

l The SMI-S provider for your HDS array is part of the HiCommand Device Manager as illustrated inthe diagram below.

l See the Hitachi Data Systems (HDS) Provider section for details on installing the HDS provider inthe HiCommand Device Manager. Or contact your HDS vendor for additional SMI-S providersupport.

l Before adding your HDS array to SRM Profiler, you must collect the information listed in the tablebelow.

SETTINGS


Provider AdminUsername

The Administrator Username set up when adding a subsystemto theHiCommand Device Manager

Provider AdminPassword

The Administrator Password set when adding a subsystem to the HiCommandDevice Manager

ADD THE ARRAY

Use the Add a Device Wizard to add your HDS array to SRM Profiler.






page 149

https://support.solarwinds.com/Success_Center/Storage_Manager_(STM)/SRM_Profiler/0300-Appendices/0030-Configuring_storage_arrays/0040-Hitachi_Data_Systems_HDS_Provider

1. In step 1 of the Add a Device Wizard, choose HDS.2. From the Add a Device – HDS window, click the Manual Configuration link.3. In the Create New Device for Agent: Storage Array window, provide the following information:


l Device Display Name: Enter a meaningful name for your array.l Storage Array Type: Set to Storage Array HDS.l Active: Keep this box checked. Clearing this check box stops data collection for your array.

4. In the Configure Device window, provide the values for the following fields.l Status: Select On.l User Name: Enter the user name used to access the provider. Typically it is the HiCommandDevice Manager login.

l Password: Enter the password used to access the provider.l Provider IP Address: Enter the IP address of the provider.l Serial No: Enter the array serial number.




HP EVAFind the information you need to add your HP EVA array to SRM Profiler. This section provides detailsabout what you need before you begin, instructions on using the Add a Device Wizard, and guidance forresolving the troubleshooting messages you might encounter:

BEFORE YOU BEGIN

l The SMI-S provider is part of your HP EVA Command View as illustrated in the diagram below. TheHP provider must be installed and configured before you can add your HP EVA array to SRMProfiler.

page 150

l The HP Provider can be installed through Command View or can be downloaded and installedseparately. See the HP Eva Provider KB article for details on installing and configuring this provider.Or contact your HP EVA vendor for more HP EVA SMI-S provider support.

l Before adding your HP EVA array to SRM Profiler, you must collect the information listed in thetable below:

SETTINGS


Provider Admin Username The Administrator Username set in the HP Storage Admin group

Provider Admin Password The Administrator Password set in the HP Storage Admin group

l See the HP Eva Provider for more information on the HP Storage Admin Group.

ADD THE ARRAY

Use the Add a Device Wizard to add your array to SRM Profiler






1. In step 1 of the Add a Device Wizard , select HP EVA.2. From the Add a Device – EVA window, click the Manual Configuration link.3. In the Create New Device for Agent: Storage Array window, provide the following information:


l Device Display Name: Enter a meaningful name for your array.l Storage Array Type: Set to Storage Array HP EVA.l Active: Keep this box checked. Clearing this check box stops data collection for your array.

4. In the Configure Device window, provide the values for the following fields.l Status: Select On.l User Name: Enter the user name used to access the provider. Typically this is the CommandView EVA login in the format DomanName\userName. For a local user, this is<MachineName\UserName>.


page 151

https://support.solarwinds.com/Success_Center/Storage_Manager_(STM)/SRM_Profiler/0300-Appendices/0030-Configuring_storage_arrays/0050-HP_EVA_Provider_Command_View


l Password: Enter the password used to access the provider.l Provider IP Address: Enter the IP address of the provider.l Node WWN: Enter the array identifier (the Node WWN of the HP EVA array). Specify the NodeWWN without the dashes.





Versions/Models 4000, 5000, 6000, 8000

Features Asset

Storage

Performance


No

Prerequisitesl CommandView 8.02 with SMI-S CIMOM installed is recommended by HP,but CommandView 7.x will provide asset and storage info.

l EVA8000 requires CommandView 8.0.2 and Firmware 6200 for SRMProfiler to be able to show array Performance.

l CommandView ID and Password for the provider.l Define user account on Command View EVA managing EVAs. Local userfor CV-EVA v7.x; Domain/Local user for CV-EVA v8.x



Ports Used Configurable: 5988 (HTTP) or 5989 (HTTPS) used by HP CommandView

Communicationl See the SRM Profiler Ports section below.l Can be HTTP/HTTPS between SRM Profiler proxy agent and HPCommandView



page 152

HP LEFTHAND P4000Find details about adding an HP LeftHand P4000 array to SRM Profiler. This section includes what you needbefore you begin, details about adding your array, and guidance for configuring your array.

BEFORE YOU BEGIN


l Get the IP address of your array. Refer to your array administrator or your array documentationwith questions about obtaining this information.

ADD THE ARRAY

1. When adding a device, select HP LeftHand P4000 from the Choose your Array Type menu. Click OK.2. Fill in the fields In the Create New Device for Agent: HP P4000 Series window.

l Select Agent: Select an Agent for this device.l IP Address: Enter the IP address of your array that you obtained in the "Before you begin"section.

l Device Display Name: Enter the name you want displayed for this resource.l Active: Keep this box checked box. Clearing this check box stops data collection for yourarray.

3. Click Next.

CONFIGURE THE ARRAY

Test your array In the Configure Device window.

l Click Test to confirm the default values are working. The test can take up to 90 seconds.l Click Show Advanced Fields to customize your array configuration. Click Test to confirm theconnection. The test can take up to 90 seconds

l When the Test Results show Successfully connected, save your configuration

For details on enabling SNMP polling, see the HP LeftHand KB article.


Versions/Models P4000

Features Asset

Configuration

Storage


page 153

https://support.solarwinds.com/Success_Center/Storage_Manager_(STM)/SRM_Profiler/0300-Appendices/0030-Configuring_storage_arrays/0060-HP_Lefthand



No

Prerequisitesl SNMP enabledl IP address of management node and each nodel SRM Profiler Proxy Agent in Access Control List



Ports Used 161 on management node and each node

Communicationl See the SRM Profiler Ports section below.l SNMP from SRM Profiler proxy agent to management node and eachnode



HP XP

This information is provided 'as-is' as a reference for our customers. SolarWinds provides noguarantees as to the accuracy of this information as the software is built and distributed by 3rdparty vendors who may make changes at any time. SolarWinds does not provide official support forproblems related to vendor's SMI-S Providers, but customers can seek support via Thwack. Ourproduct team and other knowledgeable customers regularly use these forums and may be able toassist you.

Find details on how to add your HP XP array to SRM Profiler. Below are details about what you need beforeyou begin, instructions on using the Add a Device Wizard, and guidance for resolving the troubleshootingmessages you might encounter.

BEFORE YOU BEGIN

l The HP XP array requires an SMI-S provider before it can be monitored by SRM Profiler. The HDSprovider is part of the HiCommand Device Manager as illustrated in the diagram below.

page 154

http://thwack.solarwinds.com/welcome

l See the Hitachi Data Systems (HDS) Provider KB article for details on installing the HDS provider inthe HiCommand Device Manager. Or contact your HP XP vendor for HDS SMI-S provider support.

l Before adding your HP XP array to SRM Profiler, you must collect the information listed in the tablebelow.

SETTINGS



The Administrator Username set up when adding a subsystem to theHiCommand Device Manager


The Administrator Password set when adding a subsystem to theHiCommand Device Manager

ADD THE ARRAY

Use the Add a Device Wizard to add your HP XP array to SRM Profiler.





1. In step 1 of the Add a Device Wizard, select HP XP.2. From the Add a Device – HP XP window, click the Manual Configuration link.3. In the Create New Device for Agent: Storage Array window, provide the following information:


l Device Display Name: Enter a meaningful name for your array.l Storage Array Type: Set to Storage Array HP XP.l Active: Keep this box checked. Clearing this check box stops data collection for your array.



page 155


l Status: Select On.l User Name: Enter the user name used to access the provider. Typically this is theHiCommand Device Manager.

l Password: Enter the password used to access the provider.l Provider IP Address: Enter the IP address of the provider.l Identifier: Enter the serial number for the array.




IBM DS3XXX, DS4XXX, DS5XXXFind the information you need to add your IBM DS 3xxx, IBM DS4xxx, and DS5xxx arrays to SRM Profiler.Below are details about what you need before you begin, instructions on using the Add a Device Wizard,and guidance for resolving the troubleshooting messages you might encounter.

BEFORE YOU BEGIN

l An SMI-S provider must be installed and configured before you can add the IBM DS3xxx, DS4xxx,or DS5xxx array to SRM Profiler. The SMI-S provider is a separate piece of software as illustrated inthe diagram below.

l See the Provider section for more information on downloading and installing the provider softwareor contact IBM for support.

l Before adding your IBM DS3xxx, DS4xxx, IBM DS5xxx array to SRM Profiler, you must collect theinformation listed in the table below.

SETTINGS



The Administrator Username is assigned when the SMI-S provider isinstalled.


The Administrator Password is assigned when the SMI-S provider isinstalled.

page 156

https://support.solarwinds.com/Success_Center/Storage_Manager_(STM)/SRM_Profiler/0300-Appendices/0030-Configuring_storage_arrays/0090-IBM_XIV_Provider

ADD THE ARRAY






1. In step 1 of the Add a Device Wizard, select IBM DS3xxx, DS4xxx, DS5xxx.2. From the Add a Device – IBM DS3xxx, DS4xxx, DS5xxx window, click the Manual Configuration link.3. In the Create New Device for Agent: Storage Array window, provide the following information:


l Device Display Name: Enter a meaningful name for your array.l Storage Array Type: Set to Storage Array IBM DS 3k, 4k, 5k series.l Active: Keep this box checked. Clearing this check box stops data collection for your array.

4. In the Configure Device window, provide the values for the following fields.l Status: Select On.l User Name: Enter the user name used to access the provider.l Password: Enter the password used to access the provider.l Provider IP Address: Enter the IP address of the provider.l Storage Array WWN: Enter the array identifier (WWN of the IBM DS3xxx, DS4xxx, and DS5xxxarray).





Versions/Models 3000, 4000, 5000

Features Asset

Storage


page 157


Performance

l Disk Performance


No

Prerequisitesl IP Address of Storage Processorsl Latest LSI Engenio SMI-S Provider installed on a 32 bit Windows/Linuxserver that has IP connectivity to the storage processors



Ports Used Configurable: 5988 (HTTP) or 5989 (HTTPS) used by SMI-S provider

Non-Configurable: 2463 used to set RPC sessions to the storage controller fromSMI-S provider.

Communicationl See the SRM Profiler Ports section below..l Can be HTTP/HTTPS between SRM Profiler proxy agent and the LSI EngenioSMI-S provider.

Requires SRMProfiler proxy agent?


IBM DS6XXX AND DS8XXXFind details on how to add your IBM DS6xxx or DS8xxx arrays to SRM Profiler. Below are details about whatyou need before you begin, instructions on using the Add a Device Wizard, and guidance for resolving thetroubleshooting messages you might encounter.

BEFORE YOU BEGIN

l An SMI-S Provider must be installed and configured before you can add IBM DS6xxx or DS8xxxarrays to SRM Profiler. The IBM Provider is a separate piece of software as illustrated in thediagram below.

page 158

l For more information about downloading and installing an IBM Provider, see the IBM Provider FAQor contact IBM for support.

l Before adding your IBM DS6xxx or IBM DS8xxx arrays to SRM Profiler, you must collect theinformation listed in the table below.

SETTINGS



The Administrator Username is assigned when the IBM Provider isinstalled.


The Administrator Password is assigned when IBM Provider is installed.

ADD THE ARRAY






1. In step 1 of the Add a Device Wizard , select IBM DS6xxx, DS8xxx.2. From the Add a Device – IBM DS6xxx, DS8xxx window, click the Manual Configuration link.3. In the Create New Device for Agent: Storage Array window, provide the following information:


l Device Display Name: Enter a meaningful name for your array.l Storage Array Type: Set to Storage Array IBM DS 6k/8k series.l Active: Keep this box checked. Clearing this check box stops data collection for your array.


page 159

https://support.solarwinds.com/Success_Center/Storage_Manager_(STM)/SRM_Profiler/0300-Appendices/0030-Configuring_storage_arrays/0070-IBM_DS_6000_8000_or_ESS_Provider

4. In the Configure Device window, provide the values for the following fields.l Status: Select On.l User Name: Enter the user name used to access the provider.l Password: Enter the password used to access the provider.l Provider IP Address: Enter the IP address of the provider.l Storage Array WWN: Enter the array identifier (WWN of the IBM DS6xxx or DS8xxx array).


5. Click Test to test the connectivity between the SRM Profiler proxy agent and the array's SMI-Sprovider. You must enter the username, password, and provider IP before you can test theconnection.

6. Click Save to save the configuration and push it to the SRM Profiler proxy agent to beginmonitoring the array.


Versions/Models 6000, 8000

Features Asset

Storage

Performance


No

Prerequisitesl IP Address of the SRM Profilerl ID and Password to SRM Profilerl Latest IBM SMI-S Provider installed on a Windows/Linux server that has IPconnectivity to the SRM Profiler server.

Can also monitor these via the HMC. Needs to be enabled via IBM.




Communicationl See the SRM Profiler Ports section below.

page 160


l Can be HTTP/HTTPS between SRM Profiler proxy agent and the IBM SMI-Sprovider.



IBM ESSFind details on how to add your IBM ESS array to SRM Profiler. Below are details about what you needbefore you begin, instructions on using the Add a Device Wizard, and guidance for resolving thetroubleshooting messages you might encounter.

BEFORE YOU BEGIN

l An SMI-S Provider must be installed and configured before you can add a IBM ESS array to SRMProfiler. The IBM Provider is a separate piece of software as illustrated in the diagram below.

l For more information about downloading and installing an IBM Provider, see the IBM Provider FAQor contact IBM for support.

l Before adding your IBM ESS array to SRM Profiler, you must collect the information listed in thefollowing table:

SETTINGS


Provider Admin Username The Administrator Username is assigned when the IBM Provider is installed.

Provider Admin Password The Administrator Password is assigned when IBM Provider is installed.

ADD THE ARRAY



page 161






1. In step 1 of the Add a Device Wizard , select ESS.2. From the Add a Device – ESS window, click the Manual Configuration link.3. In the Create New Device for Agent: Storage Array window, provide the following information:


b. Device Display Name: Enter a meaningful name for your array.c. Storage Array Type: Set to Storage Array IBM ESS.d. Active: Keep this box checked. Clearing this check box stops data collection for your array.e. Click Next.


l Status: Select On.l User Name: Enter the user name used to access the provider.l Password: Enter the password used to access the provider.l Provider IP Address: Enter the IP address of the provider.l Storage Array WWN: Enter the array identifier (WWN of the IBM ESS array).

Other parameters are editable from this window. Make changes only if you are sure of a parametervalue, otherwise leave the default value.

l Click Test to test the connectivity between the SRM Profiler proxy agent and the array's SMI-Sprovider. You must enter the username, password, and provider IP before you can test theconnection.

l Click Save to save the configuration and push it to the SRM Profiler proxy agent to beginmonitoring the array.

IBM N-SERIESFind details about adding an IBM N-Series array to SRM Profiler. This section includes what you need toknow before beginning.

page 162

BEFORE YOU BEGIN


l IP address of the IBM N-Series to be monitored.l IBM N-Series login credentials, typically root or equivalent.l The selected SRM Profiler proxy agent is in the list of IBM N-Series trusted hosts.l Windows Security Context: Please ensure that the SRM Profiler proxy agent service is running withthe "Log On" rights of a Domain Account that has read access on the shares assigned to it via the'Assign Shares' page

If the IBM N-Series is not accessible directly from any of the SRM Profiler proxy agents, then the followingitems are required to collect data via a DFM Server:

l Ensure that a SRM Profiler proxy agent is running on the server to be used to monitor this IBM N-Series

l DFM Server IP addressl IBM N-Series IP address used by DFM Server Ensure that the IBM N-Series IP address is accessibleto DFM Server via http/https

l DFM Server login with GlobalFullControl privileges

One or more SRM Profiler proxy agents for Windows/Unix/Linux must be used to perform FileAnalysis on an IBM N-Series. Use Windows Proxy Agents to perform analysis on CIFS shares, andUnix/Linux Proxy Agents to perform analysis on NFS mounts.

ADD THE ARRAY

1. When adding a device, select IBM N-Series from the Choose your Array Type menu, and then ClickOK.

2. Complete the fields in the Create New device for Agent: IBM N Series window.l Select Agent: Select the SRM Profiler proxy agent you want to monitor the IBM N-Series.l IBM N Series IP Address: enter the IP Address of the IBM N-Series / IBM N-Series's head.l Device Display Name: Enter a descriptive name for the IBM N-Series device (ex:IBMN NY).l Active: Keep this box checked. Clearing this check box stops data collection for your array.l Cost Per GB: Optional - the cost per GB of storage on this IBM N-Series to be used forchargeback purposes.

CONFIGURE THE ARRAY

l Status : Select Onl Username: Enter the username used to access the IBM N-Seriesl Password: Enter the password used to access the IBM N-Series


page 163

l DFM Server IP Address: Enter the IP address of the DFM server if the IBM N-Series is to bemonitored via a DFM Server. Leave as blank otherwise.


Versions/Models All

Features Asset

Storage

Performance


No

Prerequisitesl IP Address of NetApp head/cluster nodel Define user account on NetApp. Minimum access - a role with access toexecute specific API calls. List available upon request. Usually provided justthe root login

l Add the SRM Profiler proxy agent to list of trusted hosts on the NetAppstorage system

l ONTAP 7.3.x: Turn off API XML validation on each filer (FAQ-132)


Read/WriteActions

Read Only

Ports Usedl 80 (HTTP)/443 (HTTPS) on NetApp head/cluster nodel Any available for CIFS/NFS

Communicationl See the SRM Profiler Ports section below.l Can be HTTP/HTTPS between SRM Profiler proxy agent and the NetApphead/cluster node

DataClassification

l Occurs via SRM Profiler proxy agent.l CIFS Shares require a SRM Profiler Windows Agent and domain account toaccess the shares being analyzed

l NFS Shares require a SRM Profiler UNIX Agent and root access to shares beinganalyzed.

Requires SRMProfiler proxyagent?

l Yes

page 164

IBM N-SERIES OPERATIONS MANAGERFind details about adding an IBM N Series Operations Manager array to SRM Profiler. This section includeswhat you need before you begin, details about adding your array, and guidance for configuring your array.

BEFORE YOU BEGIN


l You must obtain the following information:l DFM Server IP Addressl Usernamel Password

Contact your array administrator or refer to your array documentation for questions about obtainingthis information.

One or more SRM Profiler proxy agents for Windows/Unix/Linux must be used to perform FileAnalysis on an IBM N-Series. Use Windows Proxy Agents to perform analysis on CIFS shares, andUnix/Linux Proxy Agents to perform analysis on NFS mounts.

ADD THE ARRAY

When adding a device, choose IBM N-Series Operations Manager from the Choose your Array Type menu.Click OK.

Complete the fields in the Create New device for Agent: IBM N Series Operations Manager window.

l Select Agent: Select the SRM Profiler proxy agent you want to monitor your array.l DFM Server IP Address: Enter the IP address of the DFM Server.

CONFIGURE THE ARRAY

1. Enter the username and password you obtained in the Before you begin section.2. For the other values, you can use the default values or you can click Show Advanced Fields to enter

your custom values.3. Click Save.

IBM SVC, V7000Find the information you need to add IBM SVC and IBM Storwize V7000 arrays to SRM Profiler. This sectionincludes what you need before you begin, instructions on using the Add a Device Wizard, and guidance forresolving the troubleshooting messages you might encounter.

IBM SVC and IBM V700 are used interchangeably in this document.


page 165

BEFORE YOU BEGIN

l An SMI-S provider is embedded in the Management Console of the array as illustrated in thediagram below. There is no need to install additional software.

l See the IBM SVC Provider KB article for additional information or contact IBM for IBM SVC Providersupport.

l Before adding your IBM SVC array to SRM Profiler, you must collect the information listed in thetable below.

SETTINGS

Provider IP address The IP address of the SVC Provider.

Provider Admin Username The Administrator Username for SVC Provider.

Provider Admin Password The Administrator Password for the SVC Provider.

l See the IBM SVC Provider troubleshooting section for information about the default username andpassword, or contact your array vendor for additional support.

ADD THE ARRAY

Use the Add a Device Wizard to add your IBM SVC array to SRM Profiler





1. In step 1 of the Add a Device Wizard , select IBM SVC, V7000.2. From the Add a Device – IBM SVC, V7000 window, click the Manual Configuration link.3. In the Create New Device for Agent: Storage Array window, provide the following information:

page 166

https://support.solarwinds.com/Success_Center/Storage_Manager_(STM)/SRM_Profiler/0300-Appendices/0030-Configuring_storage_arrays/0080-IBM_SVC_V7000_Provider


l Server IP Address: From the drop down menu, select the SRM Profiler proxy agent you wantto monitor your array.

l Device Display Name: Enter a meaningful name for your array.l Storage Array Type: Set to Storage Virtualization IBM SVC.l Active: Keep this box checked. Clearing this check box stops data collection for your array.l Click Next.

4. In the Configure Device window, provide the values for the following fields.l Status: Select On.l User Name: Enter the user name used to access the provider.l Password: Enter the password used to access the provider.l Provider IP Address: Enter the IP address of the provider.l Identifier: Enter the array identifier (WWN of the array).





Versions/Models SVC

Features Asset

Storage


No

Prerequisitesl IP Address of IBM SVCl Latest IBM SMI-S Provider installed on a Windows/Linux server that has IPconnectivity to SVC





page 167


Communicationl See the SRM Profiler Ports section below.l Can be HTTP/HTTPS between SRM Profiler proxy agent and the IBM SMI-Sprovider.



IBM XIVFind the information you need to add an IBM XIV array to SRM Profiler. This section includes what youneed before you begin, instructions on using the Add a Device Wizard, and guidance for resolving thetroubleshooting messages you might encounter.

BEFORE YOU BEGIN

l The SMI-S provider for the IBM XIV array is embedded in the administrative modules of the array asillustrated in the diagram below.

l There is no need to install additional software. The provider is enabled and running by default in alladministrative modules. Additional information is available in the IBM XIV Provider KB article. Orcontact IBM for additional support.

l The IBM XIV must be version 10.1.0 or higher.l Before adding your IBM SVC array to SRM Profiler, you must collect the information listed in thetable below.

SETTINGS


Provider Admin Username The Administrator Username used to access the SMI-S provider.

Provider Admin Password The Administrator Password used to access the SMI-S provider.

ADD THE ARRAY

Use the Add a Device Wizard to add your IBM XIV array to SRM Profiler

page 168






1. In step 1 of the Add a Device Wizard , select IBM XIV.2. From the Add a Device – IBM XIV window, click the Manual Configuration link.3. In the Create New Device for Agent: Storage Array window, provide the following information:


l Device Display Name: Enter a meaningful name for your array.l Storage Array Type: Set to Storage Array IBM XIV.l Active: Keep this box checked. Clearing this check box stops data collection for your array.

4. In the Configure Device window, provide the values for the following fields.l Status: Select On.l User Name: Enter the user name used to access the provider.l Password: Enter the password used to access the provider.l Provider IP Address: Enter the IP address of the provider.l Identifier: Enter the array identifier (WWN of the IBM SVC array).




NETAPP E-SERIES LSIFind the information you need to add your NetApp E-Series LSI array to SRM Profiler. Below are detailsabout what you need before you begin, instructions on using the Add a Device Wizard, and guidance forresolving the troubleshooting messages you might encounter.

NetApp acquired LSI and their arrays are now referred to as E-Series. If you are working with Eagle5.0 or 5.1 providers and firmware at version 7.8.0 or higher, you can claim E-Series support.

NetApp E-Series LSI Arrays include:


page 169

l Dell MD3xxxl IBM DS3xxx, DS4xxx, and DS5xxxl Sun StorageTek x222, 6xxx, and FLX Series

BEFORE YOU BEGIN

l An SMI-S Provider must be installed and configured before you can add your array to SRM Profiler.Your array requires the installation of a separate SMI-S provider as illustrated in the diagram below.

l See the Provider KB article for more details on downloading and installing this provider. Or contactyour array vendor for additional SMI-S provider support.

l Before adding your NetApp E-Series LSI array to SRM Profiler, you must collect the informationlisted in the table below.

SETTINGS


Provider Admin Username The Administrator Username of the SMI-S provider

Provider Admin Password The Administrator password of the SMI-S provider

ADD THE ARRAY

Use the Add a Device Wizard to add your NetApp E-Series LSI array to SRM Profiler





1. In step 1 of the Add a Device Wizard , choose LSI.

2. From the Add a Device – LSI window, click the Manual Configuration link .

3. In the Create New Device for Agent: Storage Array window, provide the following information:

page 170



l Device Display Name: Enter a meaningful name for your array.l Storage Array Type: Set to Storage Array LSI.l Active: Keep this box checked. Clearing this check box stops data collection for your array.

4. In the Configure Device window, provide the values for the following fields.l Status: Select On.l User Name: Enter the user name used to access the provider.l Password: Enter the password used to access the provider.l Provider IP Address: Enter the IP address of the provider.l Storage Array WWN: Enter the array identifier (WWN of the NetApp E-Series LSI array).





Versions/Models All

Features Asset

Storage

Performance

Disk Performance


No





page 171


Ports Usedl Configurable: 5988 (HTTP) or 5989 (HTTPS) used by SMI-S providerl Non-Configurable: 2463 used to set RPC sessions to the storage controllerfrom SMI-S provider.

Communicationl See the SRM Profiler Ports section below.l Can be HTTP/HTTPS between SRM Profiler proxy agent and the LSI EngenioSMI-S provider.



NETAPP FILERAdd your NetApp filer so SRM Profiler can query it directly. Find the information you need before youbegin and steps for adding and configuring your NetApp filer. Review the NetApp Operations Managersection if you have many Filers to add to SRM Profiler.

BEFORE YOU BEGIN

l Ensure that a SRM Profiler proxy agent is running on the server to be used to monitor your NetAppfiler.

l One or more SRM Profiler proxy agents for Windows/Unix/Linux must be used to perform FileAnalysis on a NetApp filer. Use Windows agents to perform analysis on CIFS shares and Unix/Linuxagents to perform analysis on NFS mounts.

l NetApp filer IP address.l NetApp filer login credentials, typically root or equivalent.l The selected SRM Profiler proxy agent is in the list of the filer's trusted hosts.l Windows Security Context: Please ensure that the SRM Profiler proxy agent service is running withthe "Log On" rights of a Domain Account that has read access on the shares assigned to it via the'Assign Shares' page.

l Note: Operations Manager and DFM are used synonymously in SRM Profiler.

ADDING NETAPP FILER

l When adding a device, choose NetApp filer from the Choose your Array Type menu. Click OK.l Select Agent: Select a SRM Profiler proxy agent to monitor the device.l NetApp IP Address: Enter the NetApp filer IP address obtained in Before you begin.l Device Display Name: Enter a descriptive name to identify the device.

page 172

l Active: Uncheck this box if you want to stop collecting data for the device.l Cost Per GB: Optional - Enter the cost per gigabyte.l Click Next.

CONFIGURING NETAPP FILER

Provide the appropriate information about the array you want to monitor. If you are unsure about a value,do not change the default value.

l Status: Select On.l User Name: Enter the User Name obtained in Before you begin.l Password: Enter the Password obtained in Before you begin.l Transport Type: Choose HTTP or HTTPS.l Use Operations Manager: This field is set to False by default. When the flag is set to True, and avalid DFM Server IP Address is provided, SRM Profiler requests data from the NetApp OperationsManager. If the value is set to false, SRM Profiler queries the NetApp filer directly.

DFM Server and Operations Manager are used synonymously in SRM Profiler.

l DFM Server IP Address: If you enter True for Use Operations Manager, enter the OperationsManager (DFM) IP address.

l Advanced Fields: The Operations Manager Port and Data Window Size are advanced configurationfields.



page 173


Versions/Models All

Features AssetStoragePerformance


No

Prerequisitesl IP Address of NetApp head/cluster nodel Define user account on NetApp. Minimum access - a role with access toexecute specific API calls. List available upon request. Usually provided justthe root login

l Add the SRM Profiler proxy agent to list of trusted hosts on the NetAppstorage system

l ONTAP 7.3.x: Turn off API XML validation on each NetApp filer (FAQ-132)l For ONTAP 8.1:

l 7 Mode is requiredl Clustered Mode is not supported


Read/WriteActions

Read Only


Communicationl See the SRM Profiler Ports section.l Can be HTTP/HTTPS between SRM Profiler proxy agent and the NetApphead/cluster node

DataClassification

l CIFS Shares require a SRM Profiler Windows Agent and domain account toaccess the shares being analyzed

l NFS Shares require a SRM Profiler Linux Agent and root access to shares beinganalyzed.

l Occurs via SRM Profiler proxy agent



page 174

NETAPP OPERATIONS MANAGERIf you have many NetApp filers in your environment, using NetApp Operations Manager can be aconvenient way to add the Filers to SRM Profiler. Operations Manager can discover NetApp filers andcollect data on the Filers it manages.

Operations Manager and DFM Server are used synonymously in SRM Profiler.

After the NetApp filers are added, you can easily configure SRM Profiler to query the NetApp filers directlythrough the All Devices page or through the NetApp filer Policy Configuration page. See ConfiguringNetApp filer for more information.

Adding your NetApp filers using NetApp Operations Manager is a two-step process.

Step 1: Adding and configuring your NetApp Operations Manager to SRM Profiler.

Step 2: Selecting which NetApp filers to monitor and assign them to a SRM Profiler proxy agent for datacollection.

Discovery can take a few minutes in large environments.

BEFORE YOU BEGIN

Obtain the following information before you begin adding NetApp Operations Manager to SRM Profiler.

l DFM Server IP addressl DFM Server User Name and Password with GlobalFullControl privilegesl Ensure that the NetApp filers are accessible to DFM Server via http or https

ADDING NETAPP OPERATIONSMANAGER

1. When adding a device, choose NetApp Operations Manager from the Choose your Array Typemenu. Click OK.

2. Fill in the fields In the Create New Device for Agent: NetApp Operations Manager window.3. Select Agent: Select a SRM Profiler proxy agent to monitor this device.4. Device Display Name: Enter the name you want displayed for this resource.5. DFM Server IP Address: Enter the IP address of your array.6. Click Next.

CONFIGURING NETAPP OPERATIONSMANAGER

Provide the appropriate information about the array you want to monitor. If you are unsure about a value,do not change the default value.


page 175

l Status: Select Onl User Name: Enter the DFM User Name.l Password: Enter the DFM Password.l Transport Type: Choose HTTP or HTTPS.l Discovery Frequency: Choose the discovery frequency.l Advanced Fields: The Operations Manager Port and Data Window Size are advanced configurationfields.


ASSIGNING NETAPP FILERS

To Assign NetApp filers to the SRM Profiler proxy agent, go to Settings > NetApp Operations Manager >Assign NetApp Filers page.

l Select the DFM Serverl Select the NetApp filers from "Available" box. You can select more than one by holding the ControlKey while making your selections.

l Select the SRM Profiler proxy agent.l Click on the down arrow; this will move the NetApp filers down to the "Selected" box.l Click Save. When you save the change, a push will be scheduled immediately to update the SRMProfiler proxy agent(s) with the changes.

REMOVING NETAPP FILERS

l Select the NetApp filers from the "Selected" box. You can select more than one by holding theControl Key while making your selections.

l Click on the up arrow; this will move the NetApp filers up to the "Available" box.l Click Save. When you save the change, a push will be scheduled immediately to update the SRMProfiler proxy agent(s) with the changes.


Versions/Models All

Features AssetStoragePerformance


No

Prerequisitesl IP Address of NetApp head/cluster node

page 176


l Define user account on NetApp. Minimum access - a role with access toexecute specific API calls. List available upon request. Usually provided justthe root login

l Add SRM Profiler proxy agent to list of trusted hosts on the NetApp storagesystem

l ONTAP 7.3.x: Turn off API XML validation on each NetApp filer (FAQ-132)l For ONTAP 8.1

l 7 Mode is requiredl Clustered Mode is not supported


Read/WriteActions

Read Only


Communicationl See the SRM Profiler Ports section.l Can be HTTP/HTTPS between SRM Profiler and the NetApp head/cluster node

DataClassification

l CIFS Shares require a SRM Profiler Windows Agent and domain account toaccess the shares being analyzed

l NFS Shares require a SRM Profiler UNIX Agent and root access to shares beinganalyzed.

l Occurs via SRM Profiler proxy agent



ONSTORFind details about adding an ONStor array to SRM Profiler. This section includes what you need before youbegin, details about adding your array, and guidance for configuring your array.


page 177

BEFORE YOU BEGIN


l You will need the IP address of the array you want to monitor. Contact your array administrator orrefer to your array documentation for assistance obtaining this IP address.

ADD THE ARRAY

When adding a device, choose ONStor from the Choose your Array Type menu. Click OK.

Complete the fields in the Create New Device for Agent: ONStor window.

l Select Agent: Select the SRM Profiler proxy agent for this device.l Windows Device List: Select a Windows server to retrieve the CIFS shares exposed by the NASdevice.

l Unix Device List: Select a Unix or Linux server to retrieve the NFS shares exposed by the NASdevice.

l IP Address: Enter the IP address of the device to be monitored.l Device Display Name: Enter the display name for this resource.l Active: Keep this box checked box. Clearing this check box stops data collection for your array

CONFIGURE THE ARRAY

l Status: Select On.l SNMP Community String: Enter the community string of the Array (default is public).l In the Configure Device window, click Test to confirm the default values are working.l Click the Show Advanced Fields to customize your array configuration. Click Test to test SNMPcommunication between the SRM Profiler proxy agent and the ONStor device.

You must select a SRM Profiler proxy agent, enter an SNMP community string, and enter adevice IP address before you click Test.

l When the Test Results show Successfully connected, save your configuration.

PILLARFind details on how to add your Pillar array to SRM Profiler. Below are details about what you need beforeyou begin, instructions on using the Add a Device Wizard, and guidance for resolving the troubleshootingmessages you might encounter.

BEFORE YOU BEGIN

The SMI-S Provider is embedded in the Pillar array as illustrated in the diagram below. No installation isrequired

page 178

The SMI Provider is enabled by default on systems with 2 GB Pilots.

l Upgrades for the Pillar SMI-S Provider are bundled with system software upgrades.l In older Pillar Axiom systems with the 512 MB Pilot hardware, the Provider is disabled by default.Pillar does not recommend enabling the SMI_S Provider if the array is the older 512 MB Pilots. Ifyou want to use the SMI-S provider, upgrade to the 2 GB versions.

l See the Pillar Provider KB article for additional information or contact your Pillar vendor for SMI-Sprovider support.

l Before adding your Pillar array, collect the information in the table below.

SETTINGS


Provider Admin Username The Administrator Username of the Pillar provider

Provider Admin Password The Administrator password of the Pillar provider

ADD THE ARRAY

Use the Add a Device Wizard to add your Pillar array to SRM Profiler.





1. In step 1 of the Add a Device Wizard, choose Pillar.2. From the Add a Device – Pillar window, click the Manual Configuration link.3. In the Create New Device for Agent: Storage Array window, provide the following information:



page 179

https://support.solarwinds.com/Success_Center/Storage_Manager_(STM)/SRM_Profiler/0300-Appendices/0030-Configuring_storage_arrays/0120-Pillar_Provider

l Device Display Name: Enter a meaningful name for your array.l Storage Array Type: Set to Storage Array Pillar.l Active: Keep this box checked. Clearing this check box stops data collection for your array.

4. In the Configure Device window, provide the values for the following fields:l Status: Select On.l User Name : Enter the user name used to access the Pillar providerl Password: Enter the password used to access the Pillar provider.l Provider IP Address: Enter the IP address of the Pillar provider.l Identifier: Enter the array identifier (the WWN of the Pillar array).




SUN STORAGETEK 2XXX, 6XXX, AND FLX SERIESThe following information provides details for adding a Sun StorageTek 2xxx or 6xxx Series array to SRMProfiler.

BEFORE YOU BEGIN

l An SMI-S Provider must be installed and configured before you can add your Sun/StorageTek 2xxxor 6xxx Series array to SRM Profiler. The SMI-S Provider is a separate installation as illustrated inthe diagram below.

See the Provider KB article for more details on downloading and installing this provider. Contactyour Sun StorageTek vendor for additional SMI-S provider support.

l Before adding your Sun/StorageTek 2xxx or 6xxx Series array to SRM Profiler, you must collect theinformation listed in the table below.

SETTINGS


page 180

https://support.solarwinds.com/Success_Center/Storage_Manager_(STM)/SRM_Profiler/0300-Appendices/0030-Configuring_storage_arrays/0140-Sun_StorageTEK_2K_6K__FLX_Provider

SETTINGS

Provider Admin Username The Administrator Username used to access the SMI-S provider.

Provider Admin Password The Administrator password used to access the SMI-S provider.

ADD THE ARRAY

Use the Add a Device Wizard to add the array to SRM Profiler.





1. In step 1 of the Add a Device Wizard , choose Sun Storage Tek 2xxx, 6xxx Series or Sun Storage TekFLX Series.

2. From the Add a Device – Sun Storage Tek window, click the Manual Configuration link.3. In the Create New Device for Agent: Storage Array window, provide the following information:


l Device Display Name: Enter a meaningful name for your array.l Storage Array Type: Set to Sun Storage Tek 2xxx, 6xxx Series or Sun Storage Tek FLX Series.l Active: Be sure this box is selected. Clearing this check box stops data collection for yourarray.

4. In the Configure Device window, provide the values for the following fields:l Status: Select On.l User Name: Enter the user name used to access the provider.l Password: Enter the password used to access the provider.l Provider IP Address: Enter the IP address of the provider.l Storage Array WWN: Enter the array identifier (WWN of the array).


5. Click Test to test the connectivity between the SRM Profiler proxy agent and the array's SMI-Sprovider. You must enter the username, password, and provider IP before you can test the


page 181

connection.6. Click Save to save the configuration and push it to the SRM Profiler proxy agent to begin

monitoring the array.


Versions/Models All

Features Asset

Storage

Performance

Disk Performance


No




Ports Usedl Configurable: 5988 (HTTP) or 5989 (HTTPS) used by SMI-S providerl Non-Configurable: 2463 used to set RPC sessions to the storage controllerfrom SMI-S provider.

Communicationl See the SRM Profiler Ports section below.l Can be HTTP/HTTPS between SRM Profiler proxy agent and the LSI EngenioSMI-S provider.



SUN STORAGETEK 99XX SERIESThe following information provides details for adding a Sun StorageTek 99xx Series array to SRM Profiler.

page 182

BEFORE YOU BEGIN

l An SMI-S Provider must be installed and configured before you can add your Sun StorageTek 99xxSeries array to SRM Profiler. The HDS provider is part of the HiCommand Device Manager asillustrated in the diagram below.

l See the Hitachi Data Systems (HDS) Provider section for details on installing the HDS provider inthe HiCommand Device Manager. Contact your Sun StorageTek 99xx vendor for additional SMI-Sprovider support.

l Before adding your Sun StorageTek 99xx Series array to SRM Profiler, you must collect theinformation listed in the following table:

SETTINGS

Provider IP address The IP address of the HiCommand Device manager


The Administrator Username set up when adding a subsystem to theHiCommand Device Manager


The Administrator Password set when adding a subsystem to theHiCommand Device Manager

ADD THE ARRAY

Use the Add a Device Wizard to add the array to SRM Profiler.





1. In step 1 of the Add a Device Wizard, select Sun Storage Tek 99xxSeries.2. From the Add a Device – Sun Storage Tek 99xxSeries window, click the Manual Configuration link.3. In the Create New Device for Agent: Storage Array window, provide the following information:


page 183



l Device Display Name: Enter a meaningful name for your array.l Storage Array Type: Set to Storage Array HDS.l Active: Be sure this box is selected. Clearing this check box stops data collection for yourarray.

4. Click Next.5. In the Configure Device window, provide the values for the following fields.

l Status: Select On.l User Name: Enter the user name used to access the provider. Typically this is the usernameused to access the HiCommand Device Manager.

l Password: Enter the password used to access the provider. Typically this is the password usedto access the HiCommand Device Manager.

l Provider IP Address: Enter the IP address of the HiCommand Device Manager.l Serial No: Enter the serial number of the array.

Other parameters are editable from this window. Make changes only if you are sure of aparameter value, otherwise use the default value.

6. Click Test to test the connectivity between the SRM Profiler proxy agent and the array SMI-Sprovider. You must enter the username, password, and provider IP before you can test theconnection.


XIOTECH EMPRISE 7000Find details about adding a Xiotech Emprise 7000 array to SRM Profiler. This section includes what youneed before you begin, details about adding your array, and guidance for configuring your array.

BEFORE YOU BEGIN


l You will need to obtain the following information:l The Serial Number for the Xiotech device you want to monitor.l The IP address of the XWS that manages the array.l The Client / User Name used to log into the ICON. By default, this is set to Administrator.l The ICON password for the Client / User Name.l Refer to your array administrator or your array documentation for assistance obtaining thisinformation.

page 184

ADD THE ARRAY

1. When adding a device, choose Xiotech Emprise 7000 from the Choose your Array Type menu. ClickOK.

2. Complete the fields in the Create New Device for Agent: Emprise 7000 window:l Select Agent: Select a SRM Profiler proxy agent for this device.l Serial Number: Add the Serial number you obtained in the Before you begin section.l Device Display Name: Enter the display name for this resource.

3. Click Next.

CONFIGURE THE ARRAY

1. From the Configure Device window, enter the information you collected in the "Before you begin"section:

l Poll Status: Select On.l XWS IP Address: The IP address of the XWS that manages the array.l Client /User Name: The client / User Name used to log into the ICON. By default, this is set toAdministrator.

l Password: The password for the ICON server.l ICON: Select the ICON managing the Magnitude.

2. The default values can be used for the remaining configuration fields, or you can click ShowAdvanced Fields and enter custom configuration values.

3. Click Save.

XIOTECH MAGNITUDE 3D 3XXXFind details about adding a Xiotech Magnitude 3D 3xxx array to SRM Profiler. This section includes whatyou need before you begin, details about adding your array, and guidance for configuring your array.

BEFORE YOU BEGIN


l You will need to obtain the following information.l The Serial Number for the Xiotech device you want to monitor.l The IP address of the XWS that manages the array.l The Client / User Name used to log into the ICON. By default, this is set to Administrator.l The ICON password for the Client / User Name.

Contact your array administrator or refer to your array documentation for assistance obtaining thisinformation.


page 185

ADD THE ARRAY

l When adding a device, choose Xiotech Magnitude 3D 3xxx from the Choose your Array Type menu.Click OK.

l Select Agent: Select a SRM Profiler proxy agent for this device.l Serial Number: Add the Serial number you obtained in the "Before you begin" section.l Device Display Name: Enter the display name for this resource.

CONFIGURE THE ARRAY

From the Configure Device window, enter the information you collected in the "Before you begin" section.


l Password: The password for the ICON server.l ICON: Select the ICON managing the Magnitude.l The default values can be used for the remaining configuration fields. Or you can click the ShowAdvanced Fields and enter your custom configuration values.

XIOTECH MAGNITUDE 3D 4000Find details about adding a Xiotech Magnitude 3D 4000 array to SRM Profiler. This section includes whatyou need before you begin, details about adding your array, and guidance for configuring your array.

BEFORE YOU BEGIN


l You will need to obtain the following information.l The Serial Number for the Xiotech device you want to monitor.l The IP address of the XWS that manages the array.l The Client / User Name used to log into the ICON. By default, this is set to Administrator.l The ICON password for the Client / User Name.

Contact your array administrator or see the array documentation for assistance on obtaining thisinformation.

ADD THE ARRAY

When adding a device, choose Xiotech Magnitude 3D 4000 from the Choose your Array Type menu. ClickOK.

Complete the fields in the Create New Device for Agent: Magnitude 3D 4000 window.

page 186

l Select Agent: Select a SRM Profiler proxy agent for this device.l Serial Number: Add the Serial number you obtained in the "Before you begin" section.l Device Display Name: Enter the display name for this resource.

CONFIGURE THE ARRAY

From the Configure Device window, enter the information you collected in the "Before you begin" section.


l Password: The password for the ICON server.l ICON: Select the ICON managing the Magnitude.l The default values can be used for the remaining configuration fields. Or you can click the ShowAdvanced Fields and enter your custom configuration values.

Adding Fibre Channel devicesThe following section covers how to add Fibre Channel switches to SRM Profiler.

To add and configure a Fibre Channel switch for vendors like Brocade, Cisco, McDATA,and Qlogic, obtainthe required information before you begin, ensure you meet the requirements, and follow the example inthe Configuring a McData Fibre Channel switch device section.

l Fibre Channel switches requirementsl Configure a McData Fibre Channel switch device

FIBRE CHANNEL SWITCH REQUIREMENTSThe following items are required before you begin:

l Switch IP Address. This IP must be accessible via telnet from the selected SRM Profiler proxy agentto collect Zoning information from Brocade Switches

l SNMP v1 read-only community string

CISCOMDS

Versions/Models Any

Features Asset

Storage

Performance


page 187

CISCOMDS

Topology (Tabular)


No

Prerequisitesl Create SNMP version 1 community string from command linel If there is an access list for SNMP on the switch, include the SRMProfiler proxy agent(s)'s IP address to the list

Credentials SNMP community string for each FC Switch


Ports Used 161 UDP on the switch

Communication See the SRM Profiler Ports section below

Requires SRM Profilerproxy agent?

Yes – Window or Linux

Topology requires Windows agent on SAN attached host to any switch in thefabric

BROCADE, MCDATA, AND QLOGIC SWITCHES

Versions/Models Any

Features Asset

Storage

Performance

Topology (Tabular)

Zoning


No

Prerequisitesl Enable FA-MIB on switches (on Brocade, command to run issnmpmibcapset)

l If there is an access list for SNMP on the switch, include The SRMProfiler proxy agents(s)'s IP address to the list

Credentialsl SNMP community string for each FC Switchl Zoning (v4.8+): Login and Password (telnet) for each FC Switch

page 188

CISCOMDS


Ports Used 161 UDP on the switch


Requires SRM Profilerproxy agent?


Topology requires Windows agent on SAN attached host to any switch in thefabric

COMMUNITY STRING

l SNMP V1 needs to be enabled to collect data from a CISCO switch.l If the community string is defined from any CISCO Device/Fabric Manager, then it's implicitly set forSNMP V3.

l The community string MUST be defined from the command line.

SRM Profiler can monitor any switch (or device) that supports the Fibre Alliance MIB. Some switches (forexample, McDATA) use an alternate MIB, called the Fibre Channel Management MIB, which provides thesame information. For those switches using this MIB, you must check the McDATA box when creating thedevice. If you are unsure, create the device without checking the box first. If you do not see data after 15-30 minutes, try checking the box and see if data begins to be collected.

To set up Brocade switches, execute the following commands to change the SNMP configuration:

l To enable FA MIB: snmpConfig --set snmpv1

l For access control: snmpConfig --set accessControl

l To check: snmpconfig: snmpConfig --show

CONFIGURE A MCDATA FIBRE CHANNEL SWITCH DEVICE

1. On the new device page enter the appropriate values.l Select Agent: Select the SRM Profiler proxy agent you want to monitor the Fibre Channell Switch IP Address: Type the IP address of the switchl Device Display Name: Type a descriptive name for the Fibre Channel (ex: FC NY1)l Active: Do not clear this check box, doing so stops information collection from the FibreChannel

l McDATA Switch: Check this if the device uses the FIBRE-CHANNEL-MGMT MIB rather than thestandard Fibre Alliance MIB (for example, McDATA switches use this MIB)

McData i10K series switches do not require the McData checkbox to be enabled.


page 189

l Device Groups: Optional - if you have configured groups, you can add this Fibre ChannelSwitch to them by clicking the group name

l Zoning: Check this box and provide credentials, which will generate the Zoning reports.

Zoning option is supported via a Windows Agent only.

2. Click Next.3. Provide the appropriate information about the Fibre Channel switch you want to monitor. If you

are unsure about a value, do not change the value from the default.a. Status: Select Onb. SNMP Community String: An SNMP v1 read-only community string

4. Click Save to save the configuration and push it out to the SRM Profiler proxy agent to beginmonitoring the Fibre Channel.

Click Test to test SNMP communication between the SRM Profiler proxy agent and the FibreChannel Switch device. You must select a SRM Profiler proxy agent; enter a SNMP communitystring and device IP address, before you click Test.

SnapMirror monitorThe SnapMirror monitor shows the current transfer between the source and the destination for all thefilers in the group or a particular filer based on the filter selection.

FILTERING/SORTING THE VIEW

Groups All Groups assigned to the logged in user with NetApp or IBM N Series Filers devices will bedisplayed.

SourceFiler

Filers in all the Groups will be displayed. On selection of a particular group, source filer dropdown box will be loaded with filers in that groups.

Status Displays the possible statuses that can happen during snap mirror transfer, user can filterbased on the selected status by selecting the desired status and clicking on 'GO' button.

Virtualization dashboardThe SRM Profiler Virtualization dashboard provides quick views into your current virtualized environmentincluding:

l Asset Summary (including Clusters)l Capacity Analysisl Storage by type

page 190

l Data storesl VMDK Utilizationl VMs by last boot timel Storage Utilization by VMl VMware snapshotsl Overall performance of each device- CPU, Memory, Disk

DISCOVER VM TARGETSThis feature allows you to assign one or more VM(s) for SRM Profiler to discover shares/file systems on.Select the VMs from the available section to be moved to the selected box and click Discover Now.

Works with Windows Guest OS Only.

P2V SIMULATOR

P2V (physical to virtual) is the migration of operating systems and their associated applications fromphysical, dedicated hardware into virtualized environments. The P2V migration can be handled throughspecialized software tools that automate the process. Or, the P2V migration can be performed manually—for instance, by installing an OS and appropriate applications on an assigned virtual machine.

To access the P2V Simulator:

1. Click Virtualization > P2V Simulator.2. Select the group you want to simulate, and then click Go.3. Select Target Group and a Physical Server to Virtualize.4. Click Run Report.

The capacity planning results display a Before and After chart similar to the following example:

THIN PROVISIONING

Thin provisioning is a system that applies to large scale, centralized computer disk storage systems, SANs,and storage virtualization systems. Thin provisioning allows for administrators to allocate storage space tomultiple servers easily and allows distributed storage systems to be deployed as needed provisioning.


page 191

The Virtualization Dashboard provides a graphical display of your datastore Thin Provisioning. Displaysthin provisioning info on virtual disks, so you can see the level of over commitment on your datastores.

The legend for thin provisioning is as follows:

l Used Space is the actual amount of space used.l Free is the physical amount of storage still available.l Overcommitted is how much storage is committed above the physical storage available.l Thin provisioning percent is the percentage of over commitment above the physical storage.

Add VMware monitoringSRM Profiler Proxy Agents can monitor the VMware infrastructure remotely (VC, ESX and VM). Installedagents will discover the ESX Servers connected to virtual center.

Select from the following topics:

l VMware requirementsl Addi VMwarel SRM Profiler and vCenter Asset Collection

VMWARE DEVICE REQUIREMENTSFor SRM Profiler to reliably collect data from VMs, SolarWinds recommens that you do not exceed 300 VMsper 64-bit SRM Profiler proxy agents and 200 VMs per 32-bit SRM Profiler proxy agents. To accommodatefailover situations, allow a margin of safety when calculating your VM per SRM Profiler proxy agent limits. Ifyou are monitoring a cluster with more than 300 VMs, consider assigning SRM Profiler proxy agents tomonitor specific hosts.

WMWARE

Versions/Models 4.0, 4.0i, 4.1, 4.1i, 5.0, 5.1, 5.5

page 192

WMWARE

Features Asset - (VC, Cluster, ESX, and VM levels)

Storage - (VC, Cluster, ESX, and VM levels)

Performance - (VC, Cluster, ESX, and VM levels)

Capacity Planning


No

Prerequisites Create user on Virtual Center with a role containing the following privileges

l Datastore.browsel Global.Licensesl System.viewl System.Anonymousl System.Read

Credentialsl Run as root user on Unix/Linuxl Local System account/Domain Account (Windows)l Account and password are stored in SRM Profiler database andconfiguration files on SRM Profiler proxy agent using custom encryption


Ports Usedl Virtual Center: HTTPS Port 443l SRM Profiler Agent Ports


l Yes – Windows or Linuxl SRM Profiler Proxy Agent must not be installed on the Virtual Center server

ADDING VMWAREConfiguring SRM Profiler to monitor your virtual infrastructure is a two step process.

l First step, SRM Profiler must connect to the VC instance and discover all the ESX hosts it ismanaging.

l Second step, you must select which ESX hosts to monitor. Discovery can take a few minutes in largeenvironments.


page 193

For SRM Profiler to reliably collect data from VMs, it is recommended to not exceed 300 VMs per 64bit SRM Profiler proxy agents and 200 VMs per 32 bit SRM Profiler proxy agents. To accommodatefailover situations, allow a margin of safety when calculating your VM per SRM Profiler proxy agentlimits. If you are monitoring a cluster with more than 300 VMs, consider assigning agents to monitorspecific hosts.

Requirements:

The following items are required before you begin:

l A SRM Profiler proxy agent located on the same network as the VC instancel Login credentials to the VC Instance.

STEP 1: CONFIGURING A VMWARE VC INSTANCE

1. Click Settings > Getting Started>Virtualization> Add More, and then provide the appropriate valuesfor the following fields:

l Select Agent: Select the SRM Profiler proxy agent you want to collector data.l Device Display Name: Type a descriptive name for the VMware VC Instance (ex: VMwareVC NY)l VMware VC IP Address: Type the IP Address of your Virtual Center management console

2. Click Next to continue to the next configuration screen.3. Provide the appropriate information about the VMware VC Instance you want to monitor. If you are

unsure about a value, do not change the value from the default.l Status: Select ONl UserName: Virtual Centre login [Do not include Windows domain even if this is a domainaccount]

l Password: Virtual Centre passwordl Collect Orphaned VMDK: Select Yes unless you do not need reports on orphan VMDK Filesl Collect Device Pools: Select Yes

4. Click Save to save the configuration and push it out to the poller to begin monitoring the VCinstance.

You can also configure a VMware VC Instance at any time from the Devices page (Settings > AllDevices).

STEP 2: ASSIGNING VMWARE ESX HOSTS

After SRM Profiler has discovered your ESX Hosts, you can then assign them to a poller for data collection.

If ESX Hosts are not listed in the Available list after 15 minutes, you may have an authentication problemwith vCenter.

page 194

Verify your credentials and try again or contact SolarWinds for support. You can always test theauthentication yourself from this machine by manually connecting to the vCenter using a web browser:https://<VC IP Address>/ui.

1. On the Assign ESX Hosts page:a. Select the Virtual Centre Instance in the top drop down, you should see ESX Hosts appear.b. Select the ESX Hosts you want to monitor.c. Select the poller you want to use from the drop-down list .d. Click the down arrow button to assign the ESX host to the poller and move them to the

selected list below.

2. Click Save. This pushes the configuration out the selected poller(s) and begin data collection.

A VMware VC Instance appears in the SRM Profiler Devices list. Wait for about 10-15 minutes aftercompletion of the previous step in order to license your ESX Hosts.

REMOVING VMWARE ESX HOSTS

Complete the following procedure to remove ESX Hosts from a poller.

1. Under Settings in the navigation menu, click Virtualization (Assign ESX Hosts).2. On the Assign ESX Hosts page:

a. Select the ESX Hosts you want to remove and use the up arrow button to move them back tothe Available list.

b. Click Save. A push is scheduled immediately to update the SRM Profiler proxy agent(s) withthe changes.

Clusters can also be assigned in the same manner by selecting 'Cluster' instead of 'ESX' in the ESX HostAssignment page.

If after selecting the Assign by 'Cluster' option, the user clicks on the Save button without actually makingany changes, then the ESX hosts which are assigned to a different poller will be re-assigned under thecluster poller. If this happens then, you need to re-assign the ESX hosts to its original poller through the'Assign ESX Hosts' page, by selecting the Assign by 'ESX' option.

VMware vCenter can be defined and assigned to an OS Proxy Agent after an OS Proxy Agent has beeninstalled and registered with the SRM Profiler server. VMware vCenter can discover the ESX Serversconnected to Virtual Center.

To create a VMware vCenter, make sure that a SRM Profiler proxy agent is running on the IP Addressyou want to use to gather data from.


page 195

SRMPROFILER AND VCENTER ASSET COLLECTIONCustomers with very large virtual environments might encounter an issue where asset data is not beingreported for virtual devices. This issue can be caused by timeout issues due to an influx of too much datato SRM Profiler. SRM Profiler versions 6.0 and above have resolved this issue by adding a feature allowingcustomers to throttle the amount of data being polled by SRM Profiler. The new feature can be seen whenclicking the "Show Advanced Fields" button in the device configuration window for the virtual device. Thefields are:

l Number of Connection to VC for Assetl Number of connection to VC for Storagel Number of connection to VC for Performance

The default settings is 3 yet customers can adjust the values to fit their environment. You can also modifythe time for when Configuration, Performance, Storage and Discovery Frequency is collected thus avoidingany scheduled overlap with data collection from the virtual device.

page 196

When you set the values and click Save, the changes are automatically cascaded to any additional proxyagents that are monitoring ESX servers associated with the vCenter, thus saving you time from having tomanually duplicate the settings for each proxy agent.

Setting up file analysisThe following section describes how to setup file analysis and is based on the scenario of determining whohas files, what kind of files and how old the files are.

This information can be used for:

l Obtaining size and details on each sharel Quota enforcementl Compliance reportingl Storage recovery

You can also group shares into logical collections for chargeback.

REQUIREMENTS

l First, we need a list of shares from the device. For NetApp, this is done automatically through theAPI. For Celerra, Virtual Machines, and other NAS devices, you assign this work to an agent.

l An agent that is assigned the work must be able to access the share. For Windows, this meanschanging the Service Account to a domain user that has access to those CIFS shares. ForUnix/Linux, it means the root user should have access to the NFS shares.


page 197

l All CIFS scanning is done by agents on Windows servers, and all NFS scanning by agents onUnix/Linux servers.

l You must enable File Analysis on the agent doing the work.

If you select Settings > Assign Remote Shares and see a partial list or no list of shares on this page,then most likely you have a permissions issue. You must use an account that has proper permissionto see all the files you wish to perform File Analysis against.

ASSIGN REMOTE SHARESThe following example shows how to assign remote shares to a NetApp device.

1. Go to Settings > Assign Remote Shares.

2. Assign By:l NAS or VM: Lets you choose if you want to see NAS devices or Virtual Machinesl [NAS/VM] Device: Select one device or all devices.l Share Type: CIFS or NFS. Automatically changes the available agent to match the protocol.

3. After you have set the above criteria, you can then select the shares you want:

4. You can narrow it down the shares by using a regular expression filter.l Select the shares you want. You can select multiple shares by using CTRL or SHIFT.l Device: select which agent you want to do the work.l Share Depth: Used to move the start point of file analysis further down the share. SRMProfiler will treat each folder at that level as its own root directory.

page 198

Increasing Share Depth increases the amount of work File Analysis must do. It shouldonly be set greater than 0 if required. Using the default Share Depth of 0 will still gatherdata on all files in all sub folders.

l Move: Click the down arrow to assign the share, or the up arrow to unassign shares.5. After you have assigned the shares to the agents you want, click Save. This immediately assigns out

the shares to that agent, and file analysis is performed at the next scheduled file analysis start timefor that agent. If you want to change the start time, click on the Device Configuration icon for theagent doing the scanning and under "File Analysis" you will see the option to change the start time.

ASSIGN LOCAL SHARESYou can perform File Analysis on local shares. The process is basically automatic when enabling FileAnalysis on the agent. In the screen shot below you can see the server has a local c:\ drive. When FileAnalysis is enabled it will scan the local c:\ drive. If you do not wish to perform File Analysis on local shares(in this scenario c:\ drive) then you must move the drive to the "Excluded" list and click Save.

ENABLING FILE ANALYSISTo enable file analysis for a specific server:

1. Go to the Devices page (Settings > Devices) and click the Device Configuration icon for the serveryou want to configure.

2. On the configuration pop-up, navigate to the file analysis section.3. Set the Status to On and set the Start Time (defaults to midnight). File analysis will run every night

at midnight unless it is changed from the default.


page 199

SUMMARY FOR CONFIGURING FILE ANALYSIS

l The agent that is monitoring the shares should have proper privileges to access shares.l When enabling File Analysis for that agent, you should see the shares under the "Assign RemoteShares" page in SRM Profiler.

l Select those shares accordingly and assign to the respective agent.l When File Analysis run next time for that agent, it will do the scan the shares and on the deviceconsole, you should see the File Analysis details.

With File Analysis working properly we can now apply rules which will filter the results obtained by the FileAnalysis scan. For more information on building File Analysis rules see FA Rules.

For more information on File Analysis see the following thwack! post:

l http://thwack.solarwinds.com/community/solarwinds-community/product-blog/blog/2010/07/08/files-files-everywhere

l http://thwack.solarwinds.com/community/solarwinds-community/product-blog/blog/2010/10/14/file-analysis-on-nas-netapp-celerra-etc-and-virtual-machines

page 200

http://thwack.solarwinds.com/community/solarwinds-community/product-blog/blog/2010/07/08/files-files-everywhere

http://thwack.solarwinds.com/community/solarwinds-community/product-blog/blog/2010/07/08/files-files-everywhere

http://thwack.solarwinds.com/community/solarwinds-community/product-blog/blog/2010/10/14/file-analysis-on-nas-netapp-celerra-etc-and-virtual-machines

http://thwack.solarwinds.com/community/solarwinds-community/product-blog/blog/2010/10/14/file-analysis-on-nas-netapp-celerra-etc-and-virtual-machines

Common tasksThis chapter provides a number of common scenarios for which SRM Profiler provides solutions.

l Use LDAP to add a new userl Delete an administrator account with root privilegesl Change the default Web Console port from 9000l Assign remote shares on Virtual Machinesl Configure SRM Profiler agents to use specific NIC (Network Interface Card) on servers with multipleNICs

l Hide report queries from displaying in the HTML source codel Change the temporary directory when running a myisamchkl Change trap severities on the Event Monitor webpagel Set up disaster recovery with SRM Profilerl Set up an alert for disk failure on a SAN

Use LDAP to add a new user

The Add User button is not available when LDAP is enabled.

1. Have the user log into SRM Profiler using their domain credentials.2. After the new user has successfully logged into the SRM Profiler website, a second user with

Administrative rights must log into the SRM Profiler website and go to Settings > Manage Users andclick the Manage icon for the new user.

3. By default the new user does not have any privileges to the SRM Profiler website. Click the Manageicon and the Edit button to provide login rights to the new user.

Delete an administrator account with root privilegesIf you want to delete an account with Root Privileges, you must first change the account to another UserType. By design SRM Profiler does not allow users to delete accounts with Root Administrator access. Tochange and then delete an account that currently has Root Administrator privileges do the following:

1. Click Settings, and then select Manage Users.2. Click the Manage Icon for the account you want to delete3. The Profile page for the account is displayed. Click Edit.4. For User Type, select the pull down and then choose a user type that is different from Root

Administrator. Click Save.

When you go back to the Manage Users page, you will now see an option to delete the account.


page 201

Change the default Web Console port from 9000By default the SRM Profiler Website uses port 9000. Some customer may wish to change this to anotherport due to port availability or firewall issues. There is a configuration file within the install subdirectory ofSRM Profiler that will allow users to change from default port 9000 to another port.

In this example we will change the SRM Profiler Website port to 80. This example will also show you how tochange the port assignment for SRM Profiler running on Windows or Linux.

The file we must modify is called server.xml and it can be found in the following locations:

l Windows: <installed drive>:\Program Files\SolarWinds\SRM ProfilerServer\conf

l Linux: /opt/Storage_Manager_Server/conf

Open the file with a text editor and do a search for "9000". You will see a section that looks like thefollowing snippet:

<Connector port="9000" protocol="HTTP/1.1" URIEncoding="UTF-8"

disableUploadTimeout="true" connectionTimeout="20000"

acceptCount="100" redirectPort="8443" enableLookups="false"

maxSpareThreads="75" minSpareThreads="25"

maxThreads="150" maxHttpHeaderSize="8192"/>

The entry for Connector port= is where we change the port assignment for the SRM Profiler Website.Change the entry from 9000 to 80.

<Connector port="80" protocol="HTTP/1.1" URIEncoding="UTF-8"

disableUploadTimeout="true" connectionTimeout="20000"

acceptCount="100" redirectPort="8443" enableLookups="false"

maxSpareThreads="75" minSpareThreads="25"

maxThreads="150" maxHttpHeaderSize="8192"/>

Save your changes to the file. Finally we must restart the SRM Profiler Web service before the change willtake effect. To restart the SRM Profiler Web service do the following:

l Windows: Run services.msc and restart the SolarWinds SRM Profiler Web Services servicel Linux: From the Command Line Interface, type: /etc/init.d/storage_manager_serverrestart webserver

Open the SRM Profiler Web server in a web browser referencing your new port assignment.

page 202

Assign remote shares on virtual machinesBefore you can assign remote shares on Virtual Machines, you must first follow the following steps:

1. On your web console go to Settings > Discover vm targets.2. To assign one or more Virtual Machines to discover shares/filesystems do the following:

a. Select the VM(s) from Available.b. Select a resource.c. Click the down arrow.d. Click Discover Now.

3. Check for remote shares.

Configuring SRM Profiler agents to use a specific NIC(Network Interface Card) on servers with multiple NICsSRM Profiler agents use the first available Network Interface Card on a server with multiple NetworkInterface Cards. This can cause traps to get routed to the wrong network and cause connectivity issuesbetween the agent and SRM Profiler server.

If a SRM Profiler agent is installed on a server with 2 or more installed network cards, then the core.xml filemust be manually updated to define the IP address for the network card you want associated with sendingmessages to the SRM Profiler server. For example, if eth0 and eth1 are installed on your server, and eth1 isused to send traps, you must associate the eth1 IP address to the SRM Profiler agent by following theseinstructions:

1. Navigate to the agent directory For example: C:\Program Files\SolarWinds\StorageManager Agent\

2. Open core.xml in a text editor.3. Enter the IP address of the network card you want associated with sending traps.4. Save the file.5. Restart the SRM Profiler agent Service.

For Linux Servers, complete these additional steps:

1. Open /etc/hosts in a text editor.2. Keep the default options, and add the IP address, domain, and hostnames for the network card

you want associated with sending traps.3. Save the file.4. Make sure the core.xml file includes the IP address and hostname included in the /etc/hosts file.5. Restart the SRM Profiler agent Services.

By doing this you will allow the SRM Profiler agent to route traps to the correct network.


page 203

Hide report queries from being displayed in the HTML sourcecodeBy default, SRM Profiler displays the queries used to run reports in the HTML source code which can thenbe viewed from the browser.

Users can perform the following to disable these queries:

1. Go to \webapps\ROOT\bin and edit the server.properties file.2. Add the following line to the end of the file:

showQueryInReportSource = false

3. Restart the SRM Profiler Web Server service.

How to change the temporary directory when running amyisamchkWhen running a myisamchk, it uses the volume that SRM Profiler is installed on by default for its tempdirectory. If this volume is low on space, the myisamchk may not complete since it essentially replicateseach table when checking the index and repairing.

To change this, add --tmpdir = <path> to the myisamchk command in the parameters section.

The following example shows a temp directory on E: drive:

for %i in (*.MYI) do ..\..\bin\myisamchk --defaults-extra-file=..\..\my.cnf

-c -a -r -v --tmpdir = E:\temp\ %i

For more information see myisamchk.

Changing trap severities on the Event Monitor webpageWe can change the severity of traps and future traps by changing the trap definition in the event monitor.

Please review the following steps on changing the severity of traps on the Event Monitor Webpage. Thiswill also allow future traps assigned to the same rule to report with the same severity:

1. Push the policy associated with the rule to the agents. For more information on creating rules andpolicies, see Use Policies and Settings.

2. Allow the event monitor to receive one trap alert from the agent that has been assigned the rule.3. Find and select the trap rule on the Event Monitor Webpage. Click the Edit icon, which brings up the

"Edit Event" popup window.4. Change the severity of the trap via the "Severity" pull down option.

page 204

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

l If you would like to change the severity to only reflect traps that are triggered for aspecific rule then select "Override trap definition based on the rule Id" within the "TrapDefinition override action" option.

l If you would like to change the severity to all traps triggered for all the rules then select"Override default trap definition" within the "Trap Definition override action" option.

5. Click Save.

After you click Save, the current traps already listed on the Event Monitor Webpage along withany further traps matching the trap just edited will reflect the updated severity change.

Set up disaster recovery with SRM Profiler

1. If the DR (Disaster Recovery) server has a different IP or FQDN (Fully Qualified Domain Name)please review the following steps, otherwise skip to step 2:

a. Make sure the DR server has visibility to the agents. Can you ping the agents from the DRserver?

b. Verify you cannot ping the compromised server. If you can ping the compromised server,shut it down to make the IP address available.

c. If the compromised server's IP address is available, assign it to the DR server along with theFQDN.

d. Install the SRM Profiler server software on the DR server.e. Make sure all of the SRM Profiler services are running on the DR server.f. Log into the web console for the SRM Profiler DR server.g. Select Settings > Policies > Default OS Policy > Edit button (pencil icon) > Communications.h. Change the following options to match the compromised server:

HTTP Port Default (4319)

Server IP or Domain Name

Trap Port Defaults (162, 10162, 20162)

Community String Default (public)

Override Agent Values No

i. Click Save.

It is not necessary to push the values. You are only changing the Default OS Policy tomatch what is already configured on the agents.


page 205

j. If you have a backup copy of your database that is formatted to the same version of SRMProfiler that was running on the compromised server, proceed to step 2. If not, you will beforced to start with the blank database that is installed by default.

2. Stop the database service on the DR server. This will also stop all 5 (Event Receiver, Maintenance,Poller, and Web) SRM Profiler Services.

SRM Profiler versions 5.6 and newer use MariaDB. For versions prior to 5.6, substitute MySQLfor MariaDB.

3. If you have a backup copy of your database, rename or delete the default blank database andmigrate your backup database to the DR server.

The database backup must be formatted to the same version of SRM Profiler that is runningon the DR server. If you do not have a properly formatted backup of the database or nobackup database, you will be forced to start with the blank database that is installed bydefault.

The default location for the database is in the storage folder:

Windows: <installed drive>\Program Files\Solarwinds\Storage ManagerServer\mariadb\data\

Linux: /opt/Storage_Manager_Server/mariadb/data/

Place the entire folder into the subdirectory on the DR server.

4. Start the Database, Collector, Event Receiver, Maintenance, Poller, and Web Services.5. Log into the SRM Profiler website for the new server using your regular username, password and

insert the license key obtained from your customer portal into SRM Profiler. If there is no keypresent in your customer portal, call customer service to get it reset. SRM Profiler runs inevaluation mode for 30 days without a key.

6. Verify that SRM Profiler is communicating with the devices being monitored. This can be verified byviewing the main console website. If there are any communication issues, contact technical supportfor assistance.

Set up an alert for disk Failure on a SANThe following explains the process for creating a disk failure alert when one or more disk have failed on aSAN.

You must use a threshold rule when building a disk failure alert.

page 206

l Creating a Threshold Rule for Disk Failurel Creating a Policy for the Disk Failure rulel Alert Notifications

Create a threshold rule for disk failure

1. Select Settings > Threshold Rules > Add New Rule > Threshold Rules.2. For Rule Name, give the rule a unique name.3. For Section, select Storage Array.4. For Category, select Disk Drive Asset.5. For Choose Instances, you can select Any Instance or specific drives from Available and move them

to the Selected box.6. For Condition, select Operation Status, along with the desired operator (==, !=, <, >, >=, <=) and

status.7. Set the desired Duration time for the alert to be triggered before sending a trap.8. Select the option Send Trap.9. Click Save As New.

Create a policy for the disk failure rule

1. Click Settings > Policies > Add New Policy.2. For Policy Class, select SMI-S.3. For "Base Policy on," select Default SMI-S Policy.4. For Name, give the policy a unique name.5. Click Save.6. For Edit Policy, click Rules. On the next screen select the new Disk Failure rule and place it under

Selected Rules.7. Click Save.8. You should now be back to the Edit Policy page. Select Devices.9. For Choose Devices - <policy name>, look under Available Devices, select all of the SAN devices you

wish to be notified when a disk failure occurs and place them under Selected Devices by clickingthe down arrow.

10. Click Save.11. You should be back to the Edit Policy page. Click SMI-S Configuration.12. Verify the settings for SMI-S Configuration. If you select the Override Agent Values option, this

pushes the changes to all SRM Profiler Proxy agents. If you choose not to select this option, anynew proxy agents assigned to SRM Profiler are updated leaving the agents there prior to the policycreation unchanged.

13. Click Save.


page 207

14. You should be back to the Edit Policy page. Click Push. This will push the policy to the relevantagents.

Next you can verify the progress of the configuration push by clicking the Push List Report linkin the top right corner. This will show No Data if the push has worked for the resource. Youcan also verify if any trap events are being received (assuming the thresholds have beenmeet) by going to the web console > Monitors > Event Monitor.

These events are sent to the server from the SRM Profiler agents when a threshold is met. They can beedited to change any details of the trap going forward. For example, if you're seeing an event as Critical,you can edit this to reduce its priority.

Alert notificationsAfter you have confirmed SRM Profiler is receiving traps, you can define which users will receive alertnotifications via email. The following steps explain how to assign email alert notifications.

1. Configure the SMTP server by clicking Settings > Server Setup: E-mail in the SRM Profiler servertable.

2. Configure the User and email alerts in Settings > Manage Users in the Users table.3. Edit the user by clicking the edit icon.4. Define the Email Address via the E-mail Addresses table.5. Click Add beside Notifications.6. Define which resource or group to apply to.7. Define who the emails are sent to (subscribers) and determine the severity level (severity) of the

event being sent.8. Click Save.

l What is a SMI-S provider?l Configure storage arraysl General troubleshootingl Backup SRM Profiler requirementsl Upload modules

What is a SMI-S provider?The Storage Management Initiative Specification (SMI-S) is an interface standard enabling interoperabilitybetween storage hardware and software products. SMI-S Provider deployment is determined by thevendor. The three main deployment types are listed and illustrated below.

page 208

l Type 1: SMI-S Provider is installed as a component in the vendor-specific storage managementsoftware.

l Type 2: SMI-S Provider is a separate piece of software downloaded from the vendor's website.l Type 3: SMI-S Provider is built into the storage array.

SMI-S PROVIDER DEPLOYMENT TYPES

l The default ports for the Provider are 5988 for HTTP traffic and 5989 for HTTPS traffic.l Before installing the Provider, run netstat to make sure the default ports are not being used. Ifanother Cimom (ex: Solaris) or application (ex: IBM Director ) is using that port, you must changethe port the Provider uses. For information on changing the port, see the vendor documentation.

SMI-S FAQQ: What is SNIA?

A: SNIA is the Storage Networking Industry Association in-charge of SMI-S.

Q: What are the Default Ports used by the providers?

A: The default ports are 5988 for http traffic and 5989 for https traffic.

Before installing the Provider, run netstat to make sure the default ports are not being used. Ifanother Cimom or IBM Director is running on the machine, changing the port the Providerlistens on will be required for the Provider to run.

Q: How do I test the connection to the SMI-S provider for my storage array?

A: You can use Telnet to test the network connectivity to the SMI-S Provider. For example, on a Windowssystem:


page 209

1. Log onto the SRM Profiler agent or server where you are collecting the data for your storage array.2. Open a command prompt and type the command: telnet <SMI-S provider IP address>

<port>

Example: telnet 192.168.1.2 59883. If the connection is working, you will see a blank screen. If you get an error message, try the

following troubleshooting tips.Troubleshooting tips:

a. Check the SMIS-provider IP address and port number.b. Check if a firewall is blocking the connection to the IP address or the port number.c. Check if the SMI-S service is started.

Q: What is the default namespace for my array?

A: The following table provides array default name spaces:

Vendor Namespace

LSI root/lsissi11

3PAR root/tpd

EMC root/emc

HP root/eva

IBM root/ibm

HDS (versions after 5.8) root/smis/current

HDS (versions prior to 5.8) use /root/hitachi/dm<xx> where xx is version

Configure storage arrays for use with SRM ProfilerThe following links go to knowledge base articles containing third-party information about configurationthat may be required by some storage arrays to communication with SRM Profiler.

Please note, any content posted in these articles is provided as a suggestion or recommendation toyou for your internal use. This is not part of the SolarWinds software or documentation that youpurchased from SolarWinds, and the information set forth herein may come from third parties. Yourorganization should internally review and assess to what extent, if any, such custom scripts orrecommendations will be incorporated into your environment. You elect to use third party contentat your own risk, and you will be solely responsible for the incorporation of the same, if any.

page 210

l 3PAR Providerl Dell Compellent Providerl EMC Provider and Solutions Enabler Appliance (VNX/CLARiiON, Symmetrix, VMAX)l HDS (Hitachi Data Systems) Providerl HP EVA Providerl HP LeftHandl IBM DS 6000, 8000, or ESS Providerl IBM SVC, V7000 Providerl IBM XIVl NetApp E-Series LSI Providerl OS Embedded Providerl Pillar Providerl Sun StorageTEK 99xx Series Providerl Sun StorageTEK 2k, 6k, & FLX Provider

SMI-S PROVIDER TOOLSThe following tools can be used to log into a provider to view information regarding the arrays. This sectioncovers how to test a provider.

There is a special EMC test provider tool.

CIMWORKSHOP

Download from https://sourceforge.net/projects/wbemservices/files/

Installation:

1. Unzip the wbemservices-1.0.2.bin.zip.2. Open the wbemservices-1.0.2.bin directory.3. Edit cimworkshop.bat located in the bin directory.

a. Un-REM line 36, and change the path to the directory where the java jre is installed, if JAVA_HOME is not set as a global environment variableExample: set JAVA_HOME=C:\Progra~1\Java\jre1.6.0

Obtaining Array Identifier:


page 211


https://support.solarwinds.com/Success_Center/Storage_Manager_(STM)/SRM_Profiler/0300-Appendices/0030-Configuring_storage_arrays/0020-Dell_Compellent




https://support.solarwinds.com/Success_Center/Storage_Manager_(STM)/SRM_Profiler/0300-Appendices/0030-Configuring_storage_arrays/0060-HP_Lefthand





https://support.solarwinds.com/Success_Center/Storage_Manager_(STM)/SRM_Profiler/0300-Appendices/0030-Configuring_storage_arrays/0110-OS_Embedded_Provider

https://support.solarwinds.com/Success_Center/Storage_Manager_(STM)/SRM_Profiler/0300-Appendices/0030-Configuring_storage_arrays/0120-Pillar_Provider

https://support.solarwinds.com/Success_Center/Storage_Manager_(STM)/SRM_Profiler/0300-Appendices/0030-Configuring_storage_arrays/0130-Sun_StorageTEK_99xx_Series_Provider

https://support.solarwinds.com/Success_Center/Storage_Manager_(STM)/SRM_Profiler/0300-Appendices/0030-Configuring_storage_arrays/0140-Sun_StorageTEK_2K_6K__FLX_Provider

https://sourceforge.net/projects/wbemservices/files/

1. Run the cimworkshop.bat.

2. Enter the Host URL, User Name, and Password for the Array.Host URL Example: If you want to connect to the namespace root/cimv2 on the host named crawfishusing http on port 5988, you would specify the host as: http://crawfish:5988/root/cimv2

3. Click OK. The following screen is displayed:

page 212

4. Click the Magnifying Glass icon or Action > Find Class, and then search for cim_computersystem.

5. Click OK.6. Right-click cim_computersystem in the "class schema" tree menu.

7. Click Show Instances. You will find the Array Identifier / WWN under the "Name" field for theinstance containing "_StorageSystem" like below.

EMC TESTSMI PROVIDER

Follow the instructions in the EMC Provider > Installation section on where to download and how to installthis utility.

Obtaining Array Identifier

1. Log into the remote Array using the Host, Connection Type, Port, Username and Password.


page 213

2. Type "ens" to display a list of namespaces.

3. Type "ns" to change namespaces.Note: the default namespace for this utility is root/emc. If working with non-EMC arrays, use thedefault namespace for that array.

4. Type "ein" to enumerate instance names.Note: This action provides a list of all of the instances for a particular class.

5. Type "cim_computersystem" for the list of Arrays the Provider is monitoring.

page 214

In this example, there is only one instance, so it is easy to determine the correct identifier for theArray. For the instance containing "_StorageSystem", the string after the word "Name" contains theArray Identifier / WWN. In this case the Array Identifier is 50001FE15000A7E0.

Steps to reset the EMC Provider password for v4.1.x:

1. Shutdown ECOM.2. Go to <ECOM Install directory>/conf/cst/.3. Remove RoleData.xml, LocalDirectoryData.xml, csp.clb*.4. Restart ECOM.

General troubleshooting

l Device Diagnostic wizardl Troubleshooting resourcesl thwack! user communityl Instal local help filesl Upload modules

DEVICE DIAGNOSTIC WIZARDThe Devices Diagnostic wizard checks the status of all devices being monitored in SRM Profiler. If problemsare encountered, the wizard displays a message on the Main Console page and the device console pages.

1. From the main console, click Show Devices.2. Click the device name3. Use the Diagnose Problem link to help resolve the problem.

TROUBLESHOOTING RESOURCESFor more information about troubleshooting SRM Profiler issues, see the SolarWinds Knowledge Baselocated at:

https://support.solarwinds.com/Success_Center/Storage_Manager_(STM)

If you need further assistance, contact support (requires valid maintenance license):

https://customerportal.solarwinds.com/support/submit-a-ticket

THWACK! USER COMMUNITYthwack.com is a community site developed to provide users and the broader networking community withuseful information, tools and valuable devices related to SolarWinds network management solutions


page 215

https://support.solarwinds.com/Success_Center/Storage_Manager_(STM)

https://customerportal.solarwinds.com/support/submit-a-ticket

http://thwack.solarwinds.com/

PROVIDING FEEDBACKthwack! also offers the ability to submit product feedback and feature requests via the SRM ProfilerFeature Requests forum. You can navigate to that forum via the thwack! forums page.

INSTALL LOCAL HELP FILESSome users may need to host the Help files on their own web server. The following section details how toconfigure your SRM Profiler installation to use local help.

The web properties file contains the URL location of the server where online help for SolarWinds productsare stored. The default location ishttp://www.solarwinds.com/documentation/en/flarehelp/STM/default.htm.

If you are in an Internet-restricted network environment but require access to online help, download theentire online help, copy it to a web server, and then change the Help Server URL to that of the web server.To request a zipped copy of the SRM Profiler help files, please contact SolarWinds support.

1. Download and unzip the help to the required directory.2. Navigate to C:\Program Files\SolarWinds\Storage Manager

Server\webapps\ROOT\bin and open the file server.properties in a text editor such as Notepad.3. Edit the entry onlineHelpURL=top point at the location where you have upzipped the help files.4. Restart the webservice after the change.

Upload modulesThe Modules feature is used for delivering updates and patches and should only be used with theassistance of SolarWinds support. Modules define what information is gathered by the agents and whichproducts are installed on the SRM Profiler server.

Alert severity in SRM Profiler

Alert Severity

Informationall collection status

l Manual data collection for <x> startedl Manual data collection for <x> stoppedl Scheduled data collection for <x> startedl Scheduled data collection for <x> stopped

rules – asset change rule(default or user defined)

WARNINGl UnsupportedFirmwareException - (LSI drive perf via API for olderfirmware)

page 216

https://thwack.solarwinds.com/community/cloud-virtualization-storage_tht/storage-manager/storage-manager-feature-requests

https://thwack.solarwinds.com/community/cloud-virtualization-storage_tht/storage-manager/storage-manager-feature-requests

http://www.solarwinds.com/documentation/en/flarehelp/STM/default.htm

l Secure WBEMClient connection failedl Unsecure WBEMClient connection failedl Operational status set offlinel Data collection frequency is turned off for asset/storage/perf

Error Invalid Identifier: (can connect to the provider, but identifier not found)

Criticall Provider down/ SMI-S module going offlinel Rules – threshold rules(default or user defined)l Both secure/unsecure WBEMClient connection failedl Unable to create SYMbolclient - LSI drive perf via API for olderfirmware

l Null raw aggregated datal Monthly data is null

Operational status propertiesFollowing are the numbers and descriptions of the Operational Status properties:

Qualifier: 0 Unknown

Qualifier: 1 Other

Qualifier: 2 OK

Qualifier: 3 Degraded

Qualifier: 4 Stressed

Qualifier: 5 Predictive Failure

Qualifier: 6 Error

Qualifier: 7 Non-Recoverable Error

Qualifier: 8 Starting

Qualifier: 9 Stopping

Qualifier: 10 Stopped

Qualifier: 11 In Service

Qualifier: 12 No Contact

Qualifier: 13 Lost Communication


page 217

Qualifier: 14 Aborted

Qualifier: 15 Dormant

Qualifier: 16 Supporting Entity in Error

Qualifier: 17 Completed

Qualifier: 18 Power Mode

Qualifier: 19 Relocating

Qualifier: DMTF Reserved

Qualifier: 0x8000 Vendor Reserved

Performance chart time ranges and their corresponding unitsBelow are the SRM Profiler Performance chart time ranges and their corresponding units.

Time Ranges:

l Last Six Hours – Uses Raw datal Last 24 Hours – Uses Hourly summary datal Last 7 Days – Uses Hourly summary datal Last 30 Days – Uses Daily summary datal Last Twelve Weeks – Uses Weekly summary datal Last Six Months – Uses Weekly summary datal Last Twelve Months – Uses Monthly summary datal Between [enter times]

l If the difference between start and end time is less than 12 hours, the performance chartuses Raw data

l If the difference between start and end time is less than 14 days, the performance chart usesHourly data

l If the difference between start and end time is less than 40 days, the performance chart usesDaily data

l If the difference between start and end time is less than 40 weeks, the performance chartuses Weekly data

l If the difference between start and end time is more than 40 weeks, the performance chartuses Monthly data

Summary Units:

page 218

l Raw – The data polled from the configured device for a configured frequencyl Hourly – SRM Profiler calculates summary data on an hourly basisl Daily – SRM Profiler calculates summary data on an daily basisl Weekly – SRM Profiler calculates summary data on an weekly basisl Monthly – SRM Profiler calculates summary data on a monthly basis

Backup requirements for SRM Profiler

l CA ARCservel CommVaultl EMC/Legato NetWorkerl IBM TSMl Symantec Backup Execl Symantec Veritas NetBackup

CA ARCSERVE

Versions/Models 10,11,12 (Windows), ARCserve 11.x (Linux)

Features Activity

Supported Platforms Windows (thru 12.x) and Linux (thru 11.x)

Requires SRM Profiler agent? Yes – on ARCserve server

Prerequisites Location of ARCserve Install

Credentials Windows – Local System account/Domain Account

UNIX – run as root user


Ports Used SRM Profiler Agent Ports

Communication See the See the SRM Profiler Ports section below

Requires a SRM Profiler proxy agent? N/A

COMMVAULT

Versions/Models 7.x, 8.x

Features Activity


page 219

Configuration

Media

Exceptions/Errors

Supported Platforms Windows

Requires SRM Profiler agent? No – to collect Activity, Configuration, Media

Yes – on CommServ to collect exceptions/errors

Prerequisites Windows/ AD account to access CommServ (MS-SQL) database

Credentials Windows - Local System account/Domain Account




Requires a SRM Profiler proxyagent?

Yes – via SRM Profiler servertrfg xsd if not collectingexceptions/errors

EMC/LEGATO NETWORKER

Versions/Models 6.x thru 7.4.4

Features Activity

Configuration

Media

Exceptions/Errors

Supported Platforms Windows, Solaris, Linux, HP-UX, AIX, Tru64


Yes – on NetWorker Server

Prerequisitesl If Regional settings for date/time is not United States, a Domain Accountwith regional settings of United States to be defined (Windows)

l Location of Networker installl Date format of Daemon.raw (NetWorker 7.4)


page 220

UNIX – Run as root user


Ports Used SRM Profiler Data Agent Ports



N/A

IBM TSM

Versions/Models 5.x

Features Activity

Configuration

Storage Pool

Media

Exceptions/Errors

Supported Platforms Windows, AIX, Linux

Requires SRM Profiler agent? Yes – on Master Server or on server with DSMADMC

Prerequisitesl Account to access TSM database with operator privilegesl Location of TSM BA client install (on proxy agent/masterserver)

l TSM BA client options file (dsm.opt) configured for access to 1or master servers

l TSM Instance name


UNIX – Run as root user


Ports Usedl SRM Profiler Agent Ports


page 221

l TSM BA client communicates on port 1500(configurable) of theTSM Master Server


Requires a SRM Profiler proxyagent?

N/A

SYMANTEC BACKUP EXEC

Versions/Models 8.x, 9.x, 10.x, 11.x, 12.x

Features Activity

Supported Platforms Windows, NetWare

Requires SRM Profiler agent? Yes – on Master server


Prerequisitesl Location of Backup Exec installl Login to MS-SQL Server databasel Date Format of Set and Job (found in Backup Exec logs)

Credentialsl UNIX - Run as rootl Windows - Local System account/Domain Accountl Netware - Local adminl * Account and password are stored in SRM Profilerdatabase


Ports Used SRM Profiler Data Agent Ports


Requires a Storage

Manager Proxy Agent?

N/A

SYMANTEC VERITAS NETBACKUP

Versions/Models 4.5.x, 5.x.x thru 6.5.3.1

page 222

Features Activity

Configuration

Media

Exceptions/Errors

Tape Drive Utilization

Supported Platforms Windows, Solaris, Linux, HP-UX, AIX

Requires SRM Profiler agent? Yes – on Master Server

Prerequisites Location of NetBackup Install

Credentials UNIX - Run as root

Windows - Local System account/Domain Account






page 223

srm profiler administrator guide

Documents