SolarWinds Storage Manager powered by. Profiler Administrator Guide

(1)

SolarWinds

Storage Manager

powered by

(2)

Copyright © 1995-2015 SolarWinds Worldwide, LLC. All rights reserved worldwide. No part of this document may be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the written consent of SolarWinds. All right, title, and interest in and to the software and documentation are and shall remain the exclusive property of

SolarWinds and its respective licensors.

SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON SOFTWARE AND

DOCUMENTATION FURNISHED HEREUNDER INCLUDING WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. IN NO EVENT SHALL SOLARWINDS, ITS

SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The SOLARWINDS and 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 or pending registration in other countries. All other SolarWinds trademarks, service marks, and logos may be common law marks, registered or pending registration in the United States or in other countries. All other trademarks mentioned herein are used for identification purposes only and may be or are trademarks or registered trademarks of their respective companies.

(3)

SolarWinds Storage Manager powered by Profiler  Administrator Guide

About SolarWinds

 iii

About SolarWinds

SolarWinds, Inc. develops and markets an array of network management, monitoring, and discovery tools to meet the diverse requirements of today’s network management and consulting professionals. SolarWinds products continue to set benchmarks for quality and performance and have positioned the company as the leader in network management and discovery technology. The SolarWinds customer base includes over 45 percent of the Fortune 500 and customers from over 90 countries. Our global business partner distributor network exceeds 100 distributors and resellers.

Contacting SolarWinds

You can contact SolarWinds in a number of ways, including the following: Team Contact Information

Sales

[email protected] www.solarwinds.com 1.866.530.8100 +353.21.5002900

Technical Support www.solarwinds.com/support User Forums www.thwack.com

Conventions

The documentation uses consistent conventions to help you identify items throughout the printed and online library.

Convention Specifying

Bold Window items, including buttons and fields.

Italics Book and CD titles, variable names, new terms

Fixed font File and directory names, commands and code examples,

text typed by you Straight brackets, as in

[value] Optional command parameters Curly braces, as in

{value} Required command parameters Logical OR, as in

value1|value2

Exclusive command parameters where only one of the options can be specified

(4)

Administrator Guide  SolarWinds Storage Manager powered by Profiler

Storage Manager

powered by Profiler

Documentation

The following documents are included in the SolarWinds Storage Manager powered by Profiler documentation library:

Document Purpose

Administrator Guide Provides detailed setup, configuration, and conceptual information.

Evaluation Guide

Provides an introduction to STORAGE MANAGER features and instructions for installation and initial configuration.

Page Help Provides help for every window in the Storage _{Manager powered by Profiler user interface}

Release Notes

Provides the latest information about known issues, and updates. The latest Release Notes can be found at www.solarwinds.com.

(5)

Contents  v

Chapter 1

Introduction to SolarWinds Storage Manager

powered by Profiler

Storage Manager provides accurate, critical classification and performance information for SAN, NAS, Fibre Channel switches and HBA's, enabling IT managers and administrators to monitor, alert, forecast, and act on storage performance, utilization, and storage provisioning.

 Supported Devices

 Common Uses for Storage Manager

Supported Devices

Storage Manager currently supports the following platforms, applications, and devices:

OS:

 Linux

 Windows ®

 Unix (IBM AIX, HP-UX, Sun Solaris)

Virtualization:

 VMware ®

Applications:

 Oracle ®

 SQL Server ®

SAN and NAS:

 Dell™ EqualLogic™

 Dell PowerVault MD3000i

 Dell Compellent

 EMC Celerra ®

(14)

 EMC Isilon™

 EMC Symmetrix DMX ,VMAX™

 Hitachi Data Systems ™

 HP 3PAR

 HP StorageWorks EVA

 HP LeftHand P4000

 HP StorageWorks XP

 IBM® System Storage DS® 3xxx, 4xxx, 5xxx, 6xxx, 8xxx

 IBM System Storage™ N series

 IBMSystem Storage™ SANVolume Controller (SVC)

 IBM V7000  NetApp®  LSI™  ONStor™  Pillar  SGI

Fibre Channel Switches andFabric

 Brocade Switches

 Cisco Switches

 McData

 QLogic switches

 Host Bus Adapters (HBAs) (Emulex® and QLogic)

Common Uses for Storage Manager

The following are some examples of how Storage Manager can help you.

Increased Efficiency

 Reclaiming system administrator time through automation.

 Resource Optimization

(15)

Storage Manager  15 Strategic Planning

 Forecasting & trending for business continuity & capital expenditure planning.

 Risk Mitigation

 Reducing the human error associated with managing backup & storage environments.

(16)

(17)

Chapter 2

Installing Storage Manager

Storage Manager is composed of two separate components that need to be installed. The server installation and agent installation.

The following sections guide you through the various installation scenarios for Storage Manager.

 System Requirements  Downloading the Installer

 Installing Storage Manager Server on Windows  Installing Storage Manager Server on Linux  Licensing STM or SRM

 Installing an Agent  Integrating Orion NPM

 Integrating Virtualization Manager

 Upgrading Storage Manager

After Storage Manager is installed, you can add devices you want to monitor. Some devices require the installation or configuration of an SMI-S Provider. To determine if your device requires additional installations see the Adding Storage Arrays section.

(18)

Storage Manager System Requirements

Verify that you have downloaded the correct versions for your environment and that your system meets the minimum requirements.

 Server Requirements  Agent Requirements

 Application Module Requirements  Port Requirements

 VMware Requirements  Fibre Channel Requirements

Storage Manager Server Requirements

Storage Manager Server Minimum 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: See Ports requirements section for full list.

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

(19)

Port 4319 Communications port with Storage Manager 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.

Port 3306 Used by the Storage Manager database.

Port 8443 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

Note: The installation does NOT require a reboot.

Sizing Suggestions for Storage Manager Server

Below are sizing suggestions for installing Storage Manager Server for small, medium, and large storage environments.

(20)

 Windows/Linux 64-bit

 2 Cores, 8 GB RAM

 40 GB of Free Disk Space

 1 additional Agent per 200 VM's

 Agent: 2 Cores, 4 GB of RAM, 20 GB of Free Disk Space

Medium Installation: Up to 3000 Disks  Windows/Linux 64-bit

 4 Cores, 16 - 32 GB RAM

 100 - 300 GB of Free Disk Space

 1 additional Agent per 200 VM’s

 Agent: 2 - 4 Cores, 6 GB of RAM, 20 GB of Free Disk Space

Large Installation: Greater than 3,000 disks  Linux 64-bit

 8 + Cores, 32-64 GB RAM

 500 GB of Free Disk Space

 1 additional Agent per 200 VM

 Agent: 4 Cores, 8 GB of RAM, 20 GB of Free Disk Space For more information see the “Storage Manager Deployment Guide.”

Agent Requirements

Operating System requirements are listed in the table below.

Operating System Supported versions

Windows (32 or 64 bit) Windows Server 2003 R2, Windows

Server 2008 R1/R2, Windows Server 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, Windows Server 2012 R1/R2

(21)

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

Note: When monitoring Solaris servers it is important to have the Storage

Manager Agent installed in a global zone. This prevents issues with executing native OS commands such as ptrconf.

Application Module Requirements

The following requirements apply to any application modules you may want to monitor.  Microsoft SQL Server  Oracle Microsoft SQL Server Versions/Models 2000, 2005, 2008 Requires Storage Manager Agent? No

Prerequisites Domain or Local DB user with:

• Read-only access to ALL tables in the MASTER database

• Permission to execute Stored Procedures • Permission to execute DBCC commands

(22)

Credentials Account and password stored in Storage Manager database and configuration files on Storage Manager 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 Storage Manager Proxy Agent?

Yes –via Storage Manager Server

Oracle

Versions/Models 10G, 11G

Requires Storage Manager Agent?

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

Credentials Account and password stored in Storage Manager

database and configuration files on Storage Manager Proxy Agent using custom encryption

(23)

Read/Write Actions Read Only

Ports Used Depends on Oracle configuration

Communication SQL Queries over IP

Requires a Storage Manager Proxy Agent?

Yes – via Storage Manager Server

Port Requirements

This graphic shows the SRM Profiler Module (STM) with supported storage devices and the ports required for communications.

(24)

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

(25)

This graphic shows the SRM Orion Module (SRM) main poller, additional poller, supported storage devices, and the ports required for communications.

The following tables list the ports required by the SRM Profiler Module (STM) and the SRM Orion Module (SRM)

Ports required by the SRM Profiler Module (STM)

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 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 Storage Manager Server

when information is available to be retrieved from the agent.

If port 162 is in use by Orion NPM, then Storage

Manager will use 10162 or 20162 when SNMP traps are sent to the Storage Manager Server.

443 TCP Storage Manager uses this port to communicate with

(26)

Used on the NetApp head/cluster node and any available CIFS/NFS.

1094 TCP Used by MS SQL application module.

1433 TCP Used by MS SQL application module.

2463 TCP Used to set RPC sessions to the storage controller from

the SMI-S provider for LSI and SUN StorageTek storage devices.

3306 TCP Used by the Storage Manager Database.

4319 TCP Handles the collection from Storage Manager Agents

and also acts as a local data collector/agent. Storage Manager communicates with data collectors/agents.

5988 TCP HTTP port used by SMI-S providers.

5989 TCP HTTPS port used by SMI-S providers.

8443 TCP HTTPS port used to communicate with the Storage

Profiler Module

9000 TCP Storage Manager Web Console

17778 TCP Required for access to the SRM Orion module

(SRM)SWIS API

43501 TCP Java Management Extensions (JMX) if blocked can also

use 43052, 43503, and 43504. Allows web server to obtain memory from STM services (collector, event receiver, maintenance, and poller).

(27)

Ports required by the SRM Orion Module (SRM)

Port Type Description

25 TCP SSL/TLS for email alert actions should be

enabled

80 TCP Default web port. If you specify any port

other than 80, you must include that port in the URL used to access the web console. For example, if you specify an IP address of 192.168.0.3 and port 8080, the URL used to access the web console

is http://192.168.0.3:8080 . Open the port to enable communication from your computers to the Orion Web Console.

161 UDP Used for polling storage arrays through

SNMP.

Used on the EqualLogic Group IP

443 TCP (HTTPS) Used on the NetApp head/cluster

node and any available CIFS/NFS. Used by EMC VNX/Clariion for file side performance.

1433 TCP Used for communication between the SRM

and the SQL Server

1434 UDP Used for communication with the SQL

Server Browser Service to determine how to communicate with certain non-standard SQL Server installations.

1801 UDP MSMQ WCF binding (for more information

see this

KB: http://support.microsoft.com/kb/183293).

5988 TCP (HTTP) Used by SMI-S providers.

5989 TCP (HTTPS) Used by SMI-S providers.

8088 TCP (HTTP) Backup port used for NetApp DFM

(28)

8443 TCP (HTTPS) Used by Storage Profiler SWIS

8488 TCP (HTTPS) Used for NetApp DFM

management servers for 7-mode arrays

17777 TCP Orion module traffic. Open the port to enable

communication from your poller to the SRM Web Console, and from the SRM Web Console to your poller.

The port used for communication between the Orion Web Console and the poller

17778 TCP (HTTPS) Required for access to the SWIS

API

17779 TCP (HTTP/HTTPS) SolarWinds Toolset

Integration

Downloading the Installer

To download the Storage Manager installer, you will need your SolarWinds ID (SWID) and password to login into the customer portal.

The following steps detail how to download Storage Manager Server.

To Download the Storage Manager Server:

1. Login into the customer portal:

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

2. Enter your SWID and password and click the Log In button.

3. Under downloads select the Storage Manager Server installer that is

appropriate for your OS and then click .

4. Click View All to list all available activation keys.

5. Copy the long string of characters under "Activation Key". Copy it to clipboard for later use.

(29)

Note: Before exiting the customer portal, download any Agent installers that are relevant to your deployment if needed.

Installing Storage Manager Server on Windows

 Downloading the Installer  Clean Install

 Uninstalling Storage Manager on Windows

Before Installing: Close any service window(s). Installation will not work

properly if you leave this window open during install.

 Stop your antivirus software. Some antivirus software packages can interfere with the product installation.

 Backup the Storage Manager database: SolarWinds recommends backing

up the Storage Manager database before performing any upgrades. See

Backing up the Storage Manager database for more information.

Storage Manager database Notes:

 Uninstall any previous instances of the MariaDB or MySQL. Only one instance of the MariaDB is supported on the Storage Manager server.

 Storage Manager versions 5.6 and newer use MariaDB. For previous versions, MySQL is used. For versions prior to 5.6, substitute MySQL for MariaDB

Installation Path: All Storage Manager binary and data files are located under

the installation directory. When installing, select a directory located on a partition with enough space (we suggest 40 GB) to accommodate the Storage Manager database over time.

(30)

SolarWinds Virtualization Manager cannot be installed on the same server

as Storage Manager.

Windows Clean Install

The following section guides you through a clean install on a Windows Server. After downloading the product from the SolarWinds website, complete the

following steps:

1. Navigate to the location of your downloaded .zip file, and then extract the package to an appropriate location.

2. Launch the SolarWinds Storage Manager 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 then click Next.

Note:

License: The built-in 30 day evaluation license will be used during install.

After installing you can enter your activation key.

Path: The default install path is: C:\Program

Files\SolarWinds\Storage Manager Server\

Database Password: The default database password is 'solarwinds'.

Storage Manager Server installs these services:

 MariaDB: the database for all data collected by Storage Manager.

Note: Storage Manager versions 5.6 and newer use MariaDB.

For previous versions, MySQL is used. For versions prior to 5.6, substitute MySQL for MariaDB

 SolarWinds Storage Manager Collector: collects data from agents.

 SolarWinds Storage Manager Event Receiver: receives traps.

 SolarWinds Storage Manager Maintenance: runs maintenance

routines in the background.

 SolarWinds Storage Manager Poller: remotely polls devices or

applications by a variety of methods.

 SolarWinds Storage Manager Web Services: the tomcat web server.

6. Click Finish to exit the Setup Wizard.

7. Click the Storage Manager icon on your desktop or point your web browser at http://localhost:9000. You should see a Login Screen.

(31)

Note: The default Web ServerPort can be changed in the server.xml file in the configuration folder C:\Program Files\SolarWinds\Storage Manager

Server\conf. After changing, you need to restart the Tomcat web service.

8. Login 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 Storage Manager Agents on the devices you want to

monitor.

Uninstalling Storage Manager on Windows

Use Add or Remove Programs for Windows Server 2003 R2 or Programs and

Features for Windows Server 2008 R1/R2 and Windows Server 2012 R1/R2.

Installing Storage Manager Server on Linux

The following sections detail the installation steps for LINUX.

 Supported Platforms  New Install for Linux Server  Uninstalling Linux Server

Note: 32-bit agent/server should only be installed on 32-bit Linux system

64-bit agent/server should only be installed on 64-bit Linux system

Supported Platforms - Storage Manager Server

Operating

System

Supported Versions

Linux (x86-64) RedHat, CentOS, SUSE

Linux Clean Install

The following provides steps for installing Storage Manager on a new Linux Server.

Notes:

 Storage Manager versions 5.6 and newer use MariaDB. For previous versions, MySQL is used. For versions prior to 5.6, substitute

(32)

 Before installing Storage Manager, verify there are no current instances of mariadb running on the server. If there are, you must uninstall it before installing Storage Manager. You must also rename or delete my.cnf if present before installing Storage Manager. This file is generally found in the path, /etc/my.cnf.

To install on a Linux server:

1. Login as root.

2. Execute the install binary:

# ./Storage_Manager_Agent-linux-x86_64.bin

3. Installation may take several minutes. You will be prompted for the following:

 Destination Path: The path where you want to install the agent.

A directory will be created underneath this path if it does not already exist.

 Agent Port: Correlates to the web services port that is used by

the server to communicate with the agent. The default port '4319' is recommended.

 Server Trap Port: Also related to the agent setup, the 'Server

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

 Storage Manager Database password: The password needed

to access the Storage Manager database. It is important to write it down and keep it in a safe place. This password is used by the Storage Manager services to access the Storage Manager database. This is NOT the password used to login to the GUI.

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

Note: To stop the server:

#/usr/bin/storage_manager_server stop

Uninstalling Storage Manager on Linux

The following section details how to uninstall a Linux server.

To uninstall a Linux agent:

1. Login as root.

2. Go to install path: # cd /opt/Storage_Manager_Server 3. Execute the Uninstall folder: # ./uninstall -mode silent

(33)

4. This will uninstall the Storage Manager Server.

Licensing Storage Manager or the SRM Orion Module

If you install the SRM Profiler Module or the SRM Orion Module, the license key in your customer portal will license the appropriate product version installed, the SRM Profiler Module or the SRM Orion Module.

Notes:

 When running a version of Storage Manager prior to release 6.0 that is licensed with a Storage Profiler or Backup Profiler license, you must first deactivate your license before upgrading to Storage Manager 6.0. For more information on upgrading to STM 6.0 when a Storage Profiler or Backup Profiler license is installed, see “Upgrading to Storage Manager 6.0 with a Profiler License.”

 If you are running Storage Manager with a Backup Profiler Evaluation

license, contact SolarWinds support for assistance before upgrading.

 The SRM Profiler Module can be integrated to run with the SRM Orion Module. When integrated, both products share the same license and users can see the functionality of both the SRM Orion Module and SRM Profiler Module. For more information, see “Key Scenarios when the SRM Profiler Module and the SRM Orion Module are integrated.”

 If your license is assigned to the SRM Orion Module and you wish

to share your license with the SRM Profiler Module (integrate), you must first reclaim the license from the SRM Orion Module and apply

it to the SRM Profiler Module. When the license is shared between the

two, the SRM Profiler Module is responsible monitoring the license. For more information on reclaiming you license from the SRM Orion Module, see “Reclaiming your License.” For more information on sharing your

license between the SRM Orion Module and the SRM Profiler Module, see “Integrating the SRM Orion Module and the SRM Profiler Module.”

Once the install has completed for the SRM Profiler Module or SRM Orion Module, you can license your installed product provided you have a STM license available in your customer portal. If you are installing for the first time and decide not to license your product, it will run in evaluation mode for 30 days. If you do not apply your license immediately after installation, the following topics explain how to add your license later:

 Licensing the SRM Profiler Module - This configuration is for users who want to do either one of the following options:

(34)

o Run the SRM Profiler Module and SRM Orion Module with a single license (integrated)

 Licensing the SRM Orion Module - This configuration is for users who want to use the SRM Orion Module only. In this scenario, the SRM Orion Module will use the license key and it will show active in the SRM Orion Module Licensor.

For more information on sharing the license between the SRM Orion Module and the SRM Profiler Module (integrating), see “Integrating the SRM Orion Module and the SRM Profiler Module.”

Upgrading to Storage Manager 6.0 with a Profiler License

Please note that if you are running a version of Storage Manager prior to release 6.0 that is licensed with a Storage Profiler or Backup Profiler license, you must first deactivate your license before upgrading to Storage Manager 6.0.

Note: If you wish to upgrade to Storage Manager 6.0 and still use Backup

Profiler, SolarWinds recommends that you clone or migrate your current Backup Profiler install to a different server. Once Backup Profiler is on a different server, proceed to deactivate the Backup Profiler license on the original server and then upgrade to Storage Manager 6.0.

If you try to upgrade Storage Manager when it is licensed with a Storage Profiler or Backup Profiler license, you will 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 Storage Manager 6.0 and follow the steps stated in “Licensing the SRM Profiler Module” to license Storage Manager 6.0.

Licensing the SRM Profiler Module

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

 Running the SRM Profiler Module only

 Running the SRM Profiler Module and SRM Orion Module with a single license (integrated)

(35)

Note: If your license is currently applied to the SRM Orion Module and you wish to use the two products (SRM Profiler Module and SRM Orion Module)

integrated with a single license, you must reclaim the license from the SRM Orion Module and apply it to the SRM Profiler Module. For more information, see "Reclaiming your License from the SRM Orion Module."

If you have a license available in your customer portal, perform the following task to activate your SRM Profiler Module:

1. Log into the SRM Profiler Module web console. 2. Click Settings > License Manager

3. Click Enter Registration Key and paste the string you copied from the customer portal. If the SRM Profiler Module server has internet access, the key will activate. If your server does not have internet access, there is a manual process to complete. Follow the onscreen instructions for offline activation.

Licensing the SRM Orion Module

If you are using the SRM Orion Module only, this section explains how to apply your license. The SRM Orion Module uses the SolarWinds License Manager. This is a free utility that manages your SolarWinds licenses.

This section explains the following task:

(36)

 Using License Manager

Installing License Manager

Note: The server hosting the License Manager software must have the correct

local time. If the time is incorrect on the server, License Manager will not function properly and a call to SolarWinds Customer Service will be necessary to resolve the issue. Time zone settings neither affect nor cause this issue.

The following explains the tasks for installing License Manager:

Click Start > All Programs > SolarWinds > SolarWinds License Manager Setup.

Click I Accept to accept the SolarWinds EULA.

If you are prompted to install the SolarWinds License Manager application, click Install.

Using License Manager

You must run License Manager on the computer where the SRM Orion Module is installed.

To activate your license, perform the following tasks:

Click Start > All Programs > SolarWinds > SolarWinds License Manager

Find the product you want to activate and click Upgrade under the action column Follow all steps in the wizard to complete your product activation.

Reclaiming your License

This section explains the tasks of reclaiming your license from the SRM Orion Module. This task is useful if you want to do the following:

 Run the SRM Profiler Module only

 Run the SRM Profiler Module and SRM Orion Module with a single license (integrated)

Note: If you choose to integrate the SRM Profiler Module with the SRM Orion

Module, the license must be shared between the two applications and the license

must be applied to the SRM Profiler Module. If the license is currently applied to

the SRM Orion Module, you must use this procedure to reclaim the license before applying it to the SRM Profiler Module.

(37)

The following task explain how to reclaim your license:

Reclaiming your License from the SRM Orion Module:

1. Reclaiming your license from the SRM Orion Module using the license manager: Click Start > All Programs > SolarWinds > SolarWinds

License Manager.

2. Check the products you want to deactivate on this computer, and click

Deactivate.

3. Specify your SolarWinds Customer ID and password when prompted, and click Deactivate.

Reclaiming your License from the SRM Orion Module via the

SRM Profiler Module:

1. Click SETTINGS > License Manager > Reclaim Licenses to open the Reclaim License pop-up window. If you are sure that you want to proceed with reclaiming your SRM Orion Module license, click Yes. If you wish 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 the SRM Orion Module license. If you disagree, click Cancel. For more information on what happens when you reclaim your licenses from the SRM Orion Module, see "Disabling Integration between SRM and STM."

(38)

3. Click Finish

Your reclaimed license will be available in your customer portal and ready for activation. For more information on licensing the SRM Orion Module, see "Licensing the SRM Orion Module." For more information on licensing the SRM Profiler Module, see "Licensing the SRM Profiler Module."

Integrating the SRM Orion Module and the SRM

Profiler Module

As stated earlier, you can run the SRM Orion Module and the SRM Profiler Module using a single license (integrated).

The following prerequisites must be met before product integration can happen:

 If your license is applied to the SRM Orion Module, you must reclaim the license from the SRM Orion Module and apply it to the SRM Profiler Module install before integrating the two products. For more information, see "Reclaiming your License from the SRM Orion Module." When the two products are integrated, the SRM Profiler Module is responsible for maintaining the license even though the SRM Orion Module and the SRM Profiler Module are sharing the license.

(39)

 The Storage Manager Integration Module for Orion is an integration module specific to earlier releases of Storage Manager. Installing the Storage Manager integration module for Orion after the SRM Orion Module and the SRM Profiler Module are integrated will cause the appearance of two storage tabs on the Orion web page. The two tabs will have different content one being for the SRM Orion Module and the other for the SRM Profiler Module. If you are running the Storage Manager integration module for Orion prior to integrating the SRM Profiler Module and the SRM Orion Module we recommend that you first uninstall the Storage Manager integration module for Orion before integrating the SRM Orion Module and the SRM Profiler Module. It is also recommend that you do not install the Storage Manager Integration Module for Orion once the SRM Orion Module and the SRM Profiler Module are

integrated.

This section explains the following task:

 Enabling Integration between the SRM Orion Module and the SRM Profiler Module

 Disabling Integration between the SRM Orion Module and the SRM Profiler Module

 Verifying your License Count with the SRM Profiler Module  Verifying your License Count with the SRM Orion Module

 Authentication between the SRM Orion Module and the SRM Profiler Module

 Key Scenarios when the SRM Profiler Module and the SRM Orion Module are Integrated

Enabling Integrating between the SRM Orion Module and

the SRM Profiler Module

The following tasks will integrate the SRM Orion Module and the SRM Profiler Module:

Log into the Orion web console and Click Settings > SRM Settings > Manage

SRM Profiler Module. This opens the setup web page for the SRM Orion

Module integration

Provide the following information for the SRM Profiler Module integration website: 1. Server name or IP address - Location of the SRM Profiler Module

(40)

2. Port assignment, the default port is 8443

3. User Name - A valid username or account of the server you wish to integrate

4. Password - A valid password of the server you wish to integrate Perform the following tasks:

1. Click Test Connection to verify your settings

2. Click Submit if the results from clicking Test Connection are successful. If the test fails, verify your credentials and connectivity to the SRM Profiler Module server.

Disabling Integration between the SRM Orion Module and

the SRM Profiler Module

You can disable integration between the SRM Orion Module and the SRM Profiler Module. If integration is disabled between the SRM Orion Module and the SRM Profiler Module the following happens:

 The SRM Profiler Module will remain licensed and polling continues for storage devices assigned to it

 If the 30 day evaluation period has not expired for the SRM Orion Module, polling continues for devices assigned to it

 If the 30 day evaluation period has expired for the SRM Orion Module, polling stops for devices assigned to it.

The following task explains how to disable integration between the SRM Orion Module and the SRM Profiler Module:

1. Log into the Orion web console

2. Click Settings > SRM Settings > Manage the SRM Profiler Module

Integration. This opens the setup website for the SRM Profiler Module

integration

3. Click the Disable Integration button on the Setup the SRM Profiler Module Integration website.

Verifying your License Count with the SRM Profiler Module

To view your licensing information in the SRM Profiler Module, log into the SRM Profiler Module web console and click Settings > License Manager. This will open a window showing your license count summary. The following explains the content of the license manager when the SRM Profiler Module is configured as follows:

(41)

 Running the SRM Profiler Module only

 Running the SRM Profiler Module and SRM Orion Module with a Single License (integrated)

Running the SRM Profiler Module only

The following information is displayed:

 The SRM Profiler Module version and maximum number of disks that can be monitored with your license

 License Key - The key used to activate your license

 License Size – Number of disks being monitored and the maximum number of disks that can be monitored

 Maintenance Expiration – Date your maintenance expires

Running the SRM Profiler Module and SRM Orion Module with a Single License (integrated)

 The SRM Profiler Module version and maximum number of disks that can be monitored with your license

 License Key - The key used to activate your license

 License Size – Number of disks monitored and the maximum number of disks that can be monitored

 SRM Profiler Module – Total number of disks monitored in the SRM Profiler Module

 SRM Orion Module – Total number of disks monitored in the SRM Orion Module

 Shared – Total number of disks monitored in both the SRM Orion Module and the SRM Profiler Module

 Available – Remaining number of disks that can be monitored with your license

 Maintenance Expiration – Date your maintenance expires

Verifying your License Count with the SRM Orion Module

To view licensing information in the SRM Orion Module, log into the SRM Orion Module web console and click Settings > Licensing Details. The following explains the content of the license manager for the SRM Orion Module:

(42)

 Running the SRM Orion Module and SRM Profiler Module with a Single License (integrated)

 Running the SRM Orion Module only

Running the SRM Orion Module only

 Module Name – The name of the module installed

 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 Disks - Number of licensed disks being monitored

 Unlicensed Number of Disks - Number of disks that have exceeded the license count and are not being monitored

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

Running the SRM Orion Module and SRM Profiler Module with a Single License (integrated)

 Module Name - The name of the module installed

 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

(43)

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

 Licensed Number of STM Disks - Number of licensed disks being monitored by STM

 Licensed Number of Shared Disks - Number of disks being monitored in SRM and STM using the shared license

 Unlicensed Number of Disks - Number of disks that have exceeded the license count and are not being monitored

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

Authentication between the SRM Orion Module and the

SRM Profiler Module

When the SRM Profiler Module and the SRM Orion Module are integrated, the SRM Orion Module generates a hidden service account username and password and passes this information to the SRM Profiler Module. The SRM Profiler Module also generates a hidden service account username and password passing this to the SRM Orion Module. Once integration is complete, all requests to the SRM Orion Module and the SRM Profiler Module are authenticated based on the service account information. Information transferred between the SRM Orion Module and the SRM Profiler Module is encrypted and passed via HTTPS over TCP port 8443.

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

When integrated, the SRM Profiler Module is the primary owner for holding license keys and is responsible for handling any license related queries. When integrated, the products will try to sync every 5 minutes. The following describes what happens when the SRM Orion Module and the SRM Profiler Module cannot sync.

When the SRM Profiler Module goes offline, the following happens:

 The SRM Orion Module continues connection attempts to the SRM Profiler Module until connectivity is re established

 The SRM Orion Module will not add any arrays when the SRM Profiler Module is unreachable

 If the SRM Profiler Module is unreachable for more than 24 hours, the SRM Orion Module will mark all arrays as unlicensed and polling will stop When the SRM Orion Module goes offline the following happens:

(44)

 The SRM Profiler Module continues working

 The SRM Profiler Module will use the last retrieved license validation from the SRM Orion Module for 30 days

 After 30 days the last retrieved license validation from the SRM Orion Module is discarded and the SRM Profiler Module reclaims the licenses from the SRM Orion Module and continues working

 The SRM Profiler Module continues connection attempts to the SRM Orion Module until connectivity is re established. When the SRM Orion Module goes offline, if desired, you can reclaim the licenses from the SRM Orion Module immediately. For more information on reclaiming the license from the SRM Orion Module, see “Reclaiming your License.”

Key Scenarios when the SRM Profiler Module and the SRM

Orion Module are Integrated

This section discusses the possible scenarios for the SRM Profiler Module and the SRM Orion Module when they are integrated. The following topics are discussed:

 The SRM Orion Module on Startup

 Adding an Array to the SRM Orion Module

 Adding an Array to the SRM Profiler Module

The SRM Orion Module on Startup

The SRM Orion Module performs the following tasks on startup:

1. The SRM Orion Module retrieves licensing information from the SRM Profiler Module. This information is kept in the SRM Orion Module license cache

2. The SRM Orion Module retrieves a list of licensed arrays for both the SRM Orion Module and the SRM Profiler Module. This information is kept in the SRM Orion Module license cache

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

(45)

When an array is added to the SRM Orion Module, a check is performed to verify whether or not the array is being monitored in the SRM Profiler Module. This is done by a validation process to the SRM Orion Module license cache. If the array is licensed in the SRM Profiler Module, then the SRM Orion Module adds the array to its inventory. If the array is not licensed in the SRM Profiler Module, a calculation is performed by the SRM Orion Module to verify whether or not adding the array will exceed the total licensed disk count. If the total license disk count is not exceeded, the SRM Orion Module adds the array, updates the license cache for the SRM Orion Module and sends notification to the SRM Profiler Module about the inventory change. If the total license disk count is exceeded, the user will receive a warning message and the array will not be added.

Adding an Array to the SRM Profiler Module

When an array is added to the SRM Profiler Module, a check is performed to verify whether or not the array is being monitored in the SRM Orion Module. This is done by a validation process to the SRM Profiler Module license cache. If the array is licensed in the SRM Orion Module, then the SRM Profiler Module adds the array to its inventory. If the array is not licensed in the SRM Orion Module, a calculation is performed by the SRM Profiler Module to verify whether or not adding the array will exceed the total licensed disk count. If the total license disk count is not exceeded, the SRM Profiler Module adds the array, updates the license cache for the SRM Profiler Module and sends notification to the SRM Orion Module about the inventory change. If the total license disk count is exceeded, the user will receive a warning message and the array will not be added.

Installing Storage Manager Agents

You can download agents for multiple platforms and quickly install them. Once installed, they will self-register with the Storage Manager Server and

automatically start monitoring the server they are installed on.

Before installing an agent, edit the Default Policy for Operating Systems on the server, as these settings will be pushed out to the agent when it self-registers. The self-registration process will create an OS Resource on the Storage Manager Server. Resources can also be defined manually.

Note: if there is a firewall between your Storage Manager Agent and your

Storage Manager Server, you must open Port 4319 so the agent can send data back to the server.

This chapter covers installation of the Storage Manager Agent on the following platforms:

(46)

 Installing an Agent on Windows Cluster (Windows 2008)  Installing an Agent on Linux

This Chapter will also cover the following:

 Configuring an Agent

 Turning Off Performance Reporting  Turning Off Real Time Status

Installing an Agent on Windows

Note: If you are installing an agent on a Windows 2008 Clusters, see this

section.

To install the Agent:

1. Execute the install file, typically Storage_Manager_Agent-Windows-xxx-nnn.exe (where xxx is the architecture and nnn represents the version). 2. You will be prompted for the install directory. Accept the default

(recommended) or select a different one. 3. Accept the license agreement.

4. You will then be prompted for the following (fresh install only):

 Server Address: Type the IP Address of the server where the

Storage Manager Server is running

 Server Trap Port: Type the port the Storage Manager Server is

listening for incoming traps. The default port '162' is recommended.

 Agent Web Port: Type the port to be used for communication

between the server and the agent. The default port '4319' is recommended.

Note: If you plan to use the Storage Manager Agent as a proxy for NAS

(Network Attached Storage) file analysis, you will need to manually configure the login account of the Agent service. Use an account with the right privileges to view/read the NAS shares. If you are upgrading and have configured the login previously, you will have to configure the login again after the install.

5. Leave the Start Services for Storage Manager Agent checkbox activated, if you want to start the agent service immediately. If you choose not to start the service, then you will have to manually start it later.

(47)

6. For a fresh install, the agent should self-register and self-configure on the Storage Manager Server

7. Configure your agent from the Storage Manager Server's console by clicking on the Device Configuration icon that will lead you to the configuration page for that resource

Installing an Agent on Windows Cluster (Windows 2008)

The following steps detail the installation of Storage Manager agents onto a Windows Cluster.

1. Login 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. Next, Enter the Server IP Address of the Storage Manager 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 follow the steps above.

Note: When prompted, select the same destination path previously selected.

To create a new cluster device:

1. Remotely login 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 save it.

5. Next Right click on the service and Take this service or Application Offline.

(48)

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

7. Select SolarWinds Storage Manager Agent Service from the list and click Next.

8. Click Finish.

(49)

10. Next you will need to login into Storage Manager web console, then click Settings > All Devices-> Choose Type-> OS Windows > Add.

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

(50)

12. Click Next and Save.

Installing an Agent on Linux

Find instructions for installing and uninstalling Storage Manager Agents on Linux. Check the Agent Requirements before you begin.

Notes: 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 RPM Packages. These are needed for Storage Manager to work correctly on Linux. Hence they must be installed manually. Packages details: libXp-1.0.0-8.1.e15 and libXp-devel-1.0.0-8.1.e15 (These packages are available on the RH5 distribution DVD).

Steps to install Storage Manager Agent on Linux

The following provides steps for installing Storage Manager agents on a Linux Server.

Note: 32bit agents should only be installed on 32bit Linux systems and

(51)

To install on a Linux agent:

1. Login as root.

2. Execute the install binary:

# ./Storage_Manager_Agent-linux-x86_32.bin

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

 Destination Path: The path where you want to install the agent.

A directory will be created underneath this path if it does not already exist.

 Server IP Address: The IP address of the device running the

Storage Manager Server

 Agent port: The agent server port to use.

 Web Services Port: The 'Web Services Port' correlates to the

web services port that is used by the server to communicate with the agent. The default port '4319' is recommended.

 Trap Destination Port: The 'Trap Destination Port' must be set

to the port listening on the server for incoming trap events. The default port '162' is recommended.

3. To start the agent, execute the following: #/usr/bin/storage_manager_agent start

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

Uninstalling the Linux Agent

The following section details how to uninstall a Linux agent.

To uninstall a Linux Agent:

1. Login as root.

2. Go to install path: # cd /opt/ Storage_Manager_Agent 3. Execute the Uninstall folder: # ./uninstall -mode silent 4. This will uninstall the Storage Manager Agent.

Configuring an Agent

In most cases, an Agent will self-register with the Storage Manager Server as a device. However, you can also define OS Policies manually. This allows you to push the configuration parameters out to your devices configured in the policy

(52)

1. Click > Settings > Policies > Default OS Policy

2. Complete or change the following info:

 Server IP Address: The Server IP Address of the server where

the agent resides. Note: This is not configurable once the agent is created.

 Device Display Name: The name you want to display for this

device throughout Storage Manager.

 HTTP Port : The port used by Storage Manager to collect data

from the agent (default 4319). If you change this setting, Storage Manager will immediately try to connect to this agent and update its configuration. If Storage Manager is unsuccessful, then it will abort the changes. Otherwise, you might lose communication with the agent.

 Active: The active agent. Uncheck this box if you want Storage

Manager to stop collecting data from the agent.

Note: Even though you make a Device inactive, the agent will

continue to run and you will still receive traps and be able to configure the agent.

(53)

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

 To assign a device to a group, simply click the group name in the Available field. The selected group name will automatically move to the Selected field.

 To remove a device from a group, simply click the group name in the Selected field and it will move to the Available

field.

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

 Monitor Agent: Check this box if you want the server to monitor

the agent and send a trap if the agent has not been collected from. The inactivity threshold can be configured on the server setup page.

3. To save this device definition, click Save

Turning Off Performance Reporting

If you do not need Performance Reports for Storage Manager Agents, and you are trying to limit the load on the Storage Manager Server, follow these steps to turn off Performance Reporting for Storage Manager Agents.

Follow these steps to turn of Performance Reporting for you Storage Manager Agents.

1. From the Web Console, navigate to Settings .

2. Under Device Management, click on Policies .

3. Click on the Default OS Policy Edit icon.

(54)

5. Choose Off for all Stats, check Override Agent Values, and click Save.

6. Click Push on the Edit Default OS Policy page.

NOTE: Agents are included in the Default OS Policy. Repeat steps 3-5 for each

OS Policy with agents included in the policy. It might take a few minutes for the policy revisions to get pushed out to all agents. Check that the agent

performance reports are empty to assure the configuration is pushed to all agents.

Turning Off Real Time Status

If you do not need Real Time Status for Storage Manager Agents and you are trying to limit the load on the Storage Manager Server, follow these steps to turn off Real Time Status for Storage Manager Agents.

Follow these steps to turn off Real Time Status for your Storage Manager Agents.

1. From the Web Console, navigate to Settings .

2. Under Device Management, click on Policies .

(55)

4. Click the Real Time Status link.

5. In the Enabled menu, select Off, Check the Override Agent Values, and click Save.

6. Click Push on the Edit Default OS Policy page.

What to expect after turning off Real Time Status

The Server Status in the Server Monitor and Device Console tab will show a warning.

(56)

See the screen shots below for an example of how these messages will appear.

Integrating Orion NPM

You are the website administrator for your company. You have users that desire to have the Storage Manager website and the Orion Network Performance Monitor website integrated into one browser vs. using multiple browser tabs. The Storage Manager Installer package includes an integration module that can be installed on your Orion NPM server. This light integration provides a Storage tab in your NPM web console which provides a quick view of your storage metrics.

Requires Orion core 2012.2.2 or later

To install the Storage Manager /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) and execute it.

2. Go to the NPM Settings > Storage Manager Settings and enter the IP address and login credentials you want to use.

(57)

Note: On some browsers, if you press the Test button, it will erase the password.

If you are using HTTPS the Test button will report an error.

3. Click on the storage tab, to see the Storage Manager main console.

Note: When Storage Manager is configured to use LDAP authentication, then the

domain is assumed by Storage Manager based on those settings. Therefore, when you configure the Orion Storag

SolarWinds Storage Manager powered by. Profiler Administrator Guide

SolarWinds

SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON SOFTWARE AND

About SolarWinds

Conventions

Convention Specifying

Storage Manager

Document Purpose

Contents

Chapter 1 Introduction to SolarWinds Storage Manager powered by Profiler ... 13

Chapter 3

Chapter 4 Getting Started with Storage Manager ... 65

Chapter 6 Managing User Accounts ... 103

Chapter 8 Adding and Configuring Devices ... 125

IBM SVC, V7000 ... 172

Chapter 9 Using Reports and Schedules ... 217

Chapter 11 Using Rules ... 237

Chapter 13 Common Tasks with Storage Manager ... 263

Appendix Appendix ... 273

Chapter 1

Supported Devices

Virtualization:

Fibre Channel Switches andFabric

Common Uses for Storage Manager

Increased Efficiency

Chapter 2

Storage Manager System Requirements

Operating System Requirements Windows

Minimum Hardware Requirements

Sizing Suggestions for Storage Manager Server

Agent Requirements

Operating System Supported versions

Application Module Requirements

Requires a Storage Manager Proxy Agent?

Requires a Storage Manager Proxy Agent?

Port Requirements

Ports required by the SRM Profiler Module (STM)

Port Type Description

(SRM)SWIS API

Ports required by the SRM Orion Module (SRM)

Port Type Description

Downloading the Installer

To Download the Storage Manager Server:

Installing Storage Manager Server on Windows

Storage Manager database Notes:

Windows Clean Install

Uninstalling Storage Manager on Windows

Supported Platforms - Storage Manager Server

System

Linux Clean Install

Notes:

Uninstalling Storage Manager on Linux

To uninstall a Linux agent:

Licensing Storage Manager or the SRM Orion Module

Notes:

to share your license with the SRM Profiler Module (integrate), you must first reclaim the license from the SRM Orion Module and apply

Upgrading to Storage Manager 6.0 with a Profiler License

Licensing the SRM Profiler Module

Licensing the SRM Orion Module

Using License Manager

Reclaiming your License

Reclaiming your License from the SRM Orion Module:

Reclaiming your License from the SRM Orion Module via the

Integrating the SRM Orion Module and the SRM

Enabling Integrating between the SRM Orion Module and

Disabling Integration between the SRM Orion Module and

Verifying your License Count with the SRM Profiler Module

Running the SRM Profiler Module only

Running the SRM Profiler Module and SRM Orion Module with a Single License (integrated)

Verifying your License Count with the SRM Orion Module

Running the SRM Orion Module only

Running the SRM Orion Module and SRM Profiler Module with a Single License (integrated)

Authentication between the SRM Orion Module and the

Key Scenarios when the SRM Profiler Module and the SRM

The SRM Orion Module on Startup

Adding an Array to the SRM Profiler Module

Installing Storage Manager Agents

Installing an Agent on Windows

To install the Agent:

Installing an Agent on Windows Cluster (Windows 2008)