SolarWinds Storage Manager powered by. Profiler Administrator Guide

Transcription

1 SolarWinds Storage Manager powered by Profiler Administrator Guide

2 Copyright 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. SolarWinds Storage Manager powered by Profiler, Page Help, 23 February 15 Version 6.0.

3 SolarWinds Storage Manager powered by Profiler Administrator Guide 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 Technical Support User Forums sales@solarwinds.com Conventions The documentation uses consistent conventions to help you identify items throughout the printed and online library. Convention Bold Italics Fixed font Straight brackets, as in [value] Curly braces, as in {value} Logical OR, as in value1 value2 Specifying Window items, including buttons and fields. Book and CD titles, variable names, new terms File and directory names, commands and code examples, text typed by you Optional command parameters Required command parameters Exclusive command parameters where only one of the options can be specified About SolarWinds iii

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 Administrator Guide Evaluation Guide Page Help Release Notes Purpose Provides detailed setup, configuration, and conceptual information. Provides an introduction to STORAGE MANAGER features and instructions for installation and initial configuration. Provides help for every window in the Storage Manager powered by Profiler user interface Provides the latest information about known issues, and updates. The latest Release Notes can be found at iv SolarWinds Orion IP Address Manager Documentation

5 Contents About SolarWinds... iii Contacting SolarWinds... iii Conventions... iii Storage Manager powered by Profiler Documentation... iv Chapter 1 Introduction to SolarWinds Storage Manager powered by Profiler Supported Devices Common Uses for Storage Manager Chapter 2 Installing Storage Manager Storage Manager System Requirements Storage Manager Server Requirements Agent Requirements Application Module Requirements Port Requirements Downloading the Installer Installing Storage Manager Server on Windows Installing Storage Manager Server on Linux Licensing Storage Manager or the SRM Orion Module Upgrading to Storage Manager 6.0 with a Profiler License Licensing the SRM Profiler Module Licensing the SRM Orion Module Reclaiming your License Integrating the SRM Orion Module and the SRM Profiler Module Installing Storage Manager Agents Installing an Agent on Windows Installing an Agent on Windows Cluster (Windows 2008) Installing an Agent on Linux Configuring an Agent Integrating Orion NPM Integrating Virtualization Manager Contents v

6 Chapter 3 Upgrading Storage Manager Verifying there is sufficient disk space Back up your Storage Manager database Upgrading the Storage Manager Server Upgrading Storage Manager Server on Linux Upgrading your License Verification of Software Version Upgrading Storage Manager Agents Chapter 4 Getting Started with Storage Manager Getting Started with Storage Manager Page Settings Navigating the Web Console Settings Chapter 5 Storage Manager Deployment Guide Storage Manager Architecture Storage Manager Server Storage Manager Agents Storage Manager Proxy Agents Architecture Diagram Deploying Storage Manager Minimum Recommendations for Small, Medium and Large Environments Storage Manager Proxy Agent Deployment Number of Storage Manager Agents and Proxy Agents per Storage Manager Server Sample Deployment File Analysis Storage Manager Health Status Overview Page Storage Manager Server Performance Metrics Services Database Status Device Types vi Contents

7 Storage Manager (STM) Proxy Agents Collection Jobs Queue Help and Support Advanced Configuration of Storage Manager Increasing Memory for Storage Manager Services Modifying Database Memory Settings Antivirus and Intrusion Detection Library and Support via Thwack Chapter 6 Managing User Accounts Adding Users Editing User Profiles Managing User Notifications Setting up Notifications Chapter 7 Setting Up the Storage Manager Server Agent Settings Array Settings Database Settings Settings File Analysis Settings GUI Settings Real Time Settings Reporter Settings Server Settings Trap Forwarding Settings User Authentication Settings (LDAP Settings) Virtualization Settings Enabling SSL login for the website Manage Agent Assignments Storage Manager Database Backing up the Storage Manager Database Database Maintenance using Dbutil Chapter 8 Adding and Configuring Devices Contents vii

8 Configuring Devices Adding Storage Arrays Using the Add A Device Wizard Troubleshooting with the Add a Device Wizard PAR Dell Compellent Dell Equalogic Dell MD3xxx EMC Celerra EMC Isilon EMC Symmetrix, Symmetrix DMX, Symmetrix VMAX, VNX/CLARiiON 147 EMC VNX/CLARiiON Hitachi Data Systems (HDS) HP EVA HP Lefthand P HP XP IBM DS3xxx, DS4xxx, DS5xxx IBM DS6xxx and DS8xxx IBM ESS IBM N-Series Operations Manager IBM N-Series IBM SVC, V IBM XIV NetApp E-Series LSI NetApp Filer NetApp Operations Manager ONStor Pillar Sun StorageTek 2xxx, 6xxx, and FLX Series Sun StorageTek 99xx Series Xiotech Emprise Xiotech Magnitude 3D 3xxx Xiotech Magnitude 3D Adding Fibre Channel Devices Fibre Channel Switches Requirements Configuring a McData Fibre Channel Switch Device Adding VMware Monitoring VMware Device Requirements Adding VMware Storage Manager and vcenter Asset Collection Virtualization Dashboard Discover VM Targets viii Contents

9 SnapMirror Monitor Setting Up File Analysis Assigning Remote Shares Assign Local Shares Enabling File Analysis Summary for configuring File Analysis Chapter 9 Using Reports and Schedules Administrator Reports User Reports Enterprise Storage Reports Managing Reports Running a Report Scheduling a Report Creating a New Report Deleting a Report Example Report File Repository Chapter 10 Using Groups Group Examples Creating, Editing, and Deleting Groups Creating, Editing, and Deleting File Type Groups Chapter 11 Using Rules Creating a new rule File Analysis Rule Threshold Rules Windows Event Log Rule Directory Analysis Rule Managing Rules Scheduling Rules Contents ix

10 Asset Change Rule Using External Scripts Adding a Script Editing a Script Using Scripts Chapter 12 Using Policies and Setting Alerts in Storage Manager Data Retention Policies Policy List Page Creating a Policy Editing a Policy Selecting Rules Setting Alerts in Storage Manager Chapter 13 Common Tasks with Storage Manager Using LDAP to Add a New User Deleting an Administrator Account with Root Privileges Changing the Default Web Console Port from How to Assign Remote Shares on Virtual Machines Configuring STM Agents to Use a Specific NIC (Network Interface Card) on Servers with Multiple NICs Hiding Report Queries from Displaying in the HTML Source Code How to Change the Temporary Directory when running a myisamchk Changing Trap Severities on the Event Monitor Webpage Setting up Disaster Recovery with Storage Manager Setting up an Alert for Disk Failure on a SAN Creating a Threshold Rule for Disk Failure Creating a Policy for the Disk Failure rule Alert Notifications: Appendix Appendix What is a SMI-S Provider? SMI-S FAQ x Contents

11 Configuring Storage Arrays PAR Provider Dell Compellent Dell Compellent Provider Enterprise Manager Version Dell Compellent Provider Enterprise Manager Version EMC Provider and Solutions Enabler Appliance (VNX/CLARiiON, Symmetrix, VMAX) Hitachi Data Systems (HDS) Provider HP EVA Provider (Command View) Enabling SNMP HP XP IBM DS 6000, 8000 or ESS Provider IBM SVC, V7000 Provider IBM XIV Provider NetApp E-Series LSI Provider OS Embedded Provider Pillar Provider Sun StorageTEK 99xxSeries Provider Sun StorageTEK 2K, 6K & FLX Provider Other SMI-S Provider Tools General Troubleshooting Device Diagnostic Wizard Troubleshooting Resources Thwack User Community Providing Feedback Installing Local Help Files Backup Storage Manager Requirements Upload Modules Alert Severity Operational Status Properties Performance Chart Time Ranges and their Corresponding Units Index Contents xi

12

13 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 EMC VNX/CLARiiON Storage Manager 13

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 SLA metrics & storage reallocation cost savings. 14 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. Historical trending Storage Manager 15

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 in the server.xml. 18 Storage Manager

19 Port 4319 Port 162 Port 3306 Port 8443 Communications port with Storage Manager Agents (HTTP). This port can be changed system wide, or on an agent by agent basis. Default SNMP port. Must be changed if using Orion NPM. Used by the Storage Manager database. Used by SolarWinds Information Service (SWIS) Minimum Hardware Requirements CPU Memory Storage 2 CPUs 8 GB 40 GB Browser Requirements Internet Explorer FireFox Chrome IE8, IE9, IE and above 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. Small Installation: Up to 500 Disks

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, GB RAM 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, 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 Windows (32 or 64 bit) Windows 64 bit Supported versions 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 Server 2003 R2, Windows Server 2008 R1/R2, Windows Server 2012 R1/R2 Unix (x86-32 and x86-64) Solaris Sparc 9, Storage Manager

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? Prerequisites No 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 Read/Write Actions Ports Used Communication Requires a Storage Manager Proxy Agent? Account and password stored in Storage Manager database and configuration files on Storage Manager Proxy Agent using custom encryption Read Only 1433 or 1094 on MS SQL Server (depends on SQL configuration) SQL Queries over IP Yes via Storage Manager Server Oracle Versions/Models Requires Storage Manager Agent? Prerequisites 10G, 11G No 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 Credentials sys.dba_tablespaces select sys.dba_free_space select V$OSSTAT select V$SYSMETRIC_HISTORY select Account and password stored in Storage Manager database and configuration files on Storage Manager Proxy Agent using custom encryption 22 Storage Manager

23 Read/Write Actions Ports Used Communication Requires a Storage Manager Proxy Agent? Read Only Depends on Oracle configuration SQL Queries over IP 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. 24 Storage Manager

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 or when SNMP traps are sent to the Storage Manager Server. 443 TCP Storage Manager uses this port to communicate with VMware Virtual Center or ESX server.

26 Used on the NetApp head/cluster node and any available CIFS/NFS TCP Used by MS SQL application module TCP Used by MS SQL application module TCP Used to set RPC sessions to the storage controller from the SMI-S provider for LSI and SUN StorageTek storage devices TCP Used by the Storage Manager Database TCP Handles the collection from Storage Manager Agents and also acts as a local data collector/agent. Storage Manager communicates with data collectors/agents TCP HTTP port used by SMI-S providers TCP HTTPS port used by SMI-S providers TCP HTTPS port used to communicate with the Storage Profiler Module 9000 TCP Storage Manager Web Console TCP Required for access to the SRM Orion module (SRM)SWIS API TCP Java Management Extensions (JMX) if blocked can also use 43052, 43503, and Allows web server to obtain memory from STM services (collector, event receiver, maintenance, and poller). 26 Storage Manager

27 Ports required by the SRM Orion Module (SRM) Port Type Description 25 TCP SSL/TLS for 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 and port 8080, the URL used to access the web console is 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 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 UDP MSMQ WCF binding (for more information see this KB: TCP (HTTP) Used by SMI-S providers TCP (HTTPS) Used by SMI-S providers TCP (HTTP) Backup port used for NetApp DFM management servers for 7-mode arrays

28 8443 TCP (HTTPS) Used by Storage Profiler SWIS 8488 TCP (HTTPS) Used for NetApp DFM management servers for 7-mode arrays 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 TCP (HTTPS) Required for access to the SWIS API 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: 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. 28 Storage Manager

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 You should see a Login Screen. 30 Storage Manager

31 Note: The default Web Server Port 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 MySQL for MariaDB

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

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: o Run the SRM Profiler Module only

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) 34 Storage Manager

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: Installing License Manager

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. 36 Storage Manager

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. 38 Storage Manager

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 (Storage Manager) server

40 2. Port assignment, the default port is 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: 40 Storage Manager

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 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 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 The following information is displayed: 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) The following information is displayed: 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 42 Storage Manager

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 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. Adding an Array to the SRM Orion Module 44 Storage Manager

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: Installing an Agent on Windows

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-xxxnnn.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. 46 Storage Manager

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 configuration page for that resource icon that will lead you to the 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. 9. Right click and select Bring the service or application online. 48 Storage Manager

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 Name.

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 e15 and libxp-devel 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 64bit agent should only be installed on 64bit Linux systems. 50 Storage Manager

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 To change the default OS 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. 52 Storage Manager

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. 4. Click the Performance link.

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. 3. Click on the Default OS Policy Edit icon. 54 Storage Manager

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 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 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. 56 Storage Manager

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 Storage Manager Settings, they should not specify the domain when filling in the Login Name field. If you have configured LDAP authentication in Storage Manager, and configured a domain of foodev, they will not include this in the Orion Storage Manager Settings page, For Example: Instead of foodev\john.doe, just use john.doe. The user can also configure the credentials for the admin user, as that user will be authenticated against the local Storage Manager user database, not LDAP, regardless of whether or not LDAP authentication is enabled. Integrating Virtualization Manager If you have SolarWinds Virtualization Manager, you can link data stores on the details page to open in their corresponding VMan web pages. For more information see the Virtualization Manager Administration Guide. Backing up and Scanning the Storage Manager database Using external software to scan or backup the Storage Manager database is not recommended. Use the dbutil tool provided by the Storage Manager team to backup and maintain the Storage Manager database.

58

59 Chapter 3 Upgrading Storage Manager The basic topics for upgrading Storage Manager are: Verifying there is sufficient disk space Back up the Storage Manager database Upgrading the Storage Manager Server Upgrading Storage Manager Server on Linux Upgrading your License Upgrading Storage Manager Agents Verifying there is sufficient disk space Verify there is sufficient free disk space on the Storage Manager Server before upgrading. There must be TWICE as much free space as the largest table in your database. 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 The database can be found at the following location: Windows - <installed drive>\program Files\SolarWinds\Storage Manager Server\mariadb\data\storage directory Linux -<installed path>/storage_manager_server/mariadb/data/storage directory Note: 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 and remember there must be TWICE as much free space as the largest table in your database. Storage Manager will build temporary database tables from the actual database. If you have insufficient disk space you will need to point the temporary database tables to a drive that has sufficient disk space.

60 To change the location of where the temporary database tables are stored, go to the following location: Windows - <installed drive>:\program Files\SolarWinds\Storage Manager Server\mariadb Linux <installed path>/storage_manager_server/mariadb Using a text editor open the file called my.cnf. Once 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. Windows- Restart the mariadb service via services.msc Linux Run the command /etc/init.d/storage_manager_server restart database Back up your Storage Manager database SolarWinds recommends backing up your Storage Manager database before running the Storage Manager installer. See Backing Up the Storage Manager database. 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 Note: The time it takes to complete the upgrade depends on the size of the database. Large database can take more than 6 hours. Upgrading the Storage Manager Server The Storage Manager installer upgrades your current Storage Manager Server in place. Simply execute the installer on the Storage Manager Server, and it will find the current installation and migrate the configuration and history into the upgrade. SolarWinds recommends Backing Up the Storage Manager database before upgrading the Storage Manager server. Start the MariaDB service before running the installer. Close all folders before running the installer. 60 Storage Manager

61 Run the installer. Upgrade Storage Manager Agents after the Storage Manager Server is upgraded. Note: The time it takes to complete the upgrade depends on the size of the database. Large database sizes can take more than 6 hours. See Upgrading Storage Manager Agents after the Storage Manager Server is upgraded. Upgrading Storage Manager Server on Linux The following section details to upgrade Storage Manager Server on a Linux OS. To upgrade a Linux server: 1. Login as root. 2. Execute the install binary: #./Storage_Manager_Server-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. It is NOT the password used to login to the GUI. 4. To start the server, execute the following: #/usr/bin/storage_manager_server start Note: To stop the server: #/usr/bin/storage_manager_server stop

62 Upgrading your License You can license Storage Manager by navigating to Web Console > Settings > License Manager. Your license activation key is available on your customer portal: Verification of Software Version You can see what version of Storage Manager is currently installed by navigating to Web Console > Settings > Storage Manager Server > About. Once there, you will see the following information: Server Database Version Tomcat Version MariaDB Version Patch History Version Applied 62 Storage Manager

63 Upgrading Storage Manager Agents Upgrading Agents from the Web Console After upgrading Storage Manager, you must update the agents: 1. Navigate to Web Console -> Settings -> Upgrade Agents 2. Set a name for the upgrade 3. Select all modules. 4. Select all agents. 5. Click Save. Upgrading Agents Manually The above upgrade mechanism is done from the Server side. Agent Upgrades can also be done manually by executing the Agent build for that version on the Agent side itself. SolarWinds recommends upgrades to be done from the Server side to avoid data loss. Upgrading Agents on Linux The following section details how to upgrade an agent on an existing Linux server. To upgrade an agent: 1. Login as root. 2. Execute the install binary: #./Storage_Manager_Agent-linux-x86_32.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. Server IP Address: The IP address of the device running the Storage Manager Server Agent port: The agent server port to use. 4. To start the agent, execute the following: #/usr/bin/storage_manager_agent start Note: To stop the agent: #/usr/bin/storage_manager_agent stop

64

65 Chapter 4 Getting Started with Storage Manager Getting Started Page provides quick access to adding storage devices so you can get started with your storage monitoring. Explore each section of the Storage Manager Web Console in Navigating the Web Console. The Settings page provides documentation links to the settings you can configure in Storage Manager. Getting Started with Storage Manager Page Getting Started with Storage Manager is loaded in the Main View when you first log into Storage Manager. Use this page for quick access to adding and configuring the devices you want to monitor. You can navigate to Getting Started with Storage Manager from Home in the Left Navigation Pane. Servers Add servers to be monitored by Storage Manager. Follow the onscreen instructions for adding the OS agent. Virtualization Add VC Instances and stand-alone VMware Hosts by following the onscreen configuration instructions. See Adding VMware Monitoring for details on adding your VMware to Storage Manager. Storage Arrays Use Add to select the type of storage array and follow the onscreen instructions. The Adding Storage Arrays section provides details on adding and configuring your arrays in Storage Manager. FC Switches Select the type of fibre channel switches to add and follow the onscreen instructions for configuration. See the Adding Fibre Channel Devices for more information and adding and configuring your Fibre Channel Switches in Storage Manager.

66 Viewing Data from your Devices and Applications Main Console - Summary of storage, servers and virtualization infrastructure. Server Monitor - Health and status of all your servers, physical and virtual. Virtualization Dashboard - Enterprise summary of the virtualization infrastructure. Configuration Settings Server Setup - Configure system-wide settings, including server. Devices - Manage all devices and applications. Groups - Define groups of devices for reports and chargeback. Rules - Set up thresholds and triggers on storage, performance and asset data. Quick Reports - Configure, run and publish reports on demand and by schedule. The Storage Settings page provides links to the tasks you can perform in Storage Manager. To get to the settings page, click the settings icon in the upper right of the Storage Manager website. Navigating the Web Console Storage Manager provides a web console consisting of a title bar, a help bar, left navigation pane, and a main view. The Settings section provides links to documentation for commonly performed tasks. Title bar Profile Log Out Settings Help bar Left-navigation pane Home 66 Storage Manager

67 Storage Manager Health Status Monitors Reports Server and NAS Groups SAN Groups LUN Groups Virtualization When you login to the web console for the first time, Getting Started with Storage Manager is loaded in the main view and provides quick access to adding storage devices so you can get started with your storage monitoring. The main view changes as you navigate Storage Manager. 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 profile page allows users to edit their profile and to add and edit addresses Log Out Click the Log Out button to log out of the Storage Manage web console. Settings The Settings page provides links to the tasks you can perform in Storage Manager. Documentation for these tasks is available in the Settings section. Help Bar Hide or Show the Left Navigation Pane with the Hide/Show Menu link. Access the Thwack Storage User Community.

68 The Help link opens a new browser window and loads the Storage Manager Administrator s Guide. In general, help topics relating to the Main View are accessed from the Help link. 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 Storage Manager dashboards and reports. Home Links to Getting Started with Storage Manager. Storage Manager Health Status Storage Manager (versions 5.7 and above) provides a web console consisting of a central place to view the overall health and status of the Storage Manager software. This includes the Storage Manager Server (STM), Storage Manager Database, and Storage Manager Proxy Agents. For more information, see Health Status Overview. Monitors Main Console summarizes the storage, servers, and virtualization infrastructure you are monitoring. Event Monitor summarizes the different events that are currently active. o Note: Storage Manager will show the trap values as a number for asset change conditions. For a description of what those numerical values mean, see OperationalStatus. Server Monitor shows information on the servers you are monitoring. Click the Legend link for details about the symbols used to convey server status. SnapMirror Monitor shows the current transfer between the source and the destination for all the filers in the group or a particular filer based on the filter selection. Reports Below are links to documentation for the types of reports in the Reports section of the Left-Navigation Pane. 68 Storage Manager

69 My Reports Shared Reports Quick Reports Report Schedules Management Reports Enterprise Reports Server and NAS Groups Server and NAS Groups includes information about Servers or Network Attached Storage devices you are monitoring. SAN Groups The San Groups aggregates information from both SAN devices and OS Devices that have file systems assigned to a SAN device The SAN Storage Status is an overview of the OS device file systems that have been mapped to the SAN. The SAN File System Trends and Forecast are the trends and forecast for the file systems that have been assigned to that SAN group. LUN Groups User Defined Logical Unit Number (LUN) Grouping for NetApp, SMI-S, and SNMP enabled arrays. Users can group LUNs based on their own requirements. Once the LUNs are grouped users can view details about capacity and performance for those LUN groups. For more information on grouping LUNs, see Chapter 10 Using Groups. The LUN Group Summary link provides the following information about all LUN groups: Usable Storage and RAW Storage. 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 to the LUNS assigned to that group: LUN Group - Console o o Usable and RAW Storage. Top 10 LUN Performance by Total IOPs, Latency, Read, and Write.

70 LUN Group Performance o o o o o Virtual Machine (VM) Disk Metrics per LUN - Shows performance metrics of VMs in a single LUN. Users can select appropriate LUN from the Group and verify the VM Disk Performance. LUN Metrics per VM - Shows performance metrics of the LUN for a single VM. Users can select appropriate VM and verify LUN Performance. LUN Performance - Displays performance for all of the LUNs assigned to the group. Comparisons can be made against other LUNS in the group. LUN Performance Comparison Shows LUN Performance and users can compare them with the LUN s additional metrics. LUN Group Summary Provides summary information about the group. LUN Group Servers o o o o o Allocated Volume Usage - Reports volume usage for servers and virtual machines that use storage array LUNs belonging to user defined LUN groups. This report also provides volume usage for servers and virtual machines with local storage and includes growth rates with forecast information. LUN Details - Explains the RAID group, associated disks, and information of each LUN for a given LUN Group. ESX Logical Mapping Shows the VMDK, VM, Datastore, and ESX Host of each LUN for a given LUN Group. RDM Mapping - Showing RDM Mapping from VirtualDisk to Storage Array LUNs. Logical Mapping - Shows the mapping of Server volumes and logical drives to an array LUN. Virtualization Virtualization includes any VMware devices you are monitoring. Settings The Settings page provides links to the tasks you can perform in Storage Manager. Below are links to the documentation for each of these tasks 70 Storage Manager

71 Device Management Getting Started All Devices Policies Device Groups Server Setup: Arrays NetApp Operations Manager Server Setup: Databases Virtualization (Assign ESX Hosts) Managing Agent Assignments Rules and Alerting All Rules Threshold Rules Windows Event Log Rules Asset Change Rules Scheduled Rules Sever Setup: Real Time Scripts Files File Analysis Rules Directory Analysis Rules File Type Groups Assign Remote Shares Assign Local Shares Server Setup: File Analysis Discover VM Targets File Repository

72 Users Manage Users Server Setup: User Authentication (LDAP) Storage Manager Server Server Setup: All Server Setup: Data Retention About Updates and Upgrades Upload Modules Upgrade Agents GUI and Reporting Server Setup: Reporter Server Setup: GUI License Summary License Manager thwack Community Storage Manager in the thwack community 72 Storage Manager

73 Chapter 5 Storage Manager Deployment Guide This chapter provides information on deploying and configuring Storage Manager. The Storage Manager Server works with Storage Manager Agents and Storage Manager Proxy Agents. Depending on how many devices Storage Manager is monitoring, Storage Manager Agents can help improve overall performance with Storage Manager through load balancing across multiple servers. 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. For more information on installing agents see Installing Storage Manager Agents. This chapter covers the following: Storage Manager Architecture Deploying Storage Manager Storage Manager Health Status Overview Page Advanced Configuration of Storage Manager

74 Storage Manager Architecture Storage Manager is comprised of a Server /Agent architecture: Storage Manager Server collects data from agents, traps, pollers, and saves the data to a central database and distributes information to users via the web interface. Storage Manager Server also allows the user to manage the Storage Manager Agents and Storage Manager Proxy Agents remotely. Note: The Storage Manager Server can also serve as a Storage Manager Agent or Storage Manager Proxy Agent. Storage Manager Agents provides the framework to gather storage, server performance and file analysis information from the local device and transmit it to the Storage Manager Server. Storage Manager Proxy Agents provides the framework to gather storage, server performance and file analysis information from local devices and collect Storage, Application, Virtual and Server information from external devices. Architecture Diagram illustrates the relationship between the proxy agents and the STM server. Storage Manager Server The Storage Manager Server consists of a Database, Web Server, Collector, Poller, Event Receiver, and a Maintenance process. Storage Manager uses a variety of methods to collect data, both local and remote. Storage Manager can collect most data remotely, including storage arrays (NAS and SAN), VMware hosts and virtual machines, Fibre Channel switches, databases (SQL and Oracle ) and file analysis. For physical servers, agents are required on those servers. Some of the methods that Storage Manager uses to collect data includes: SMI-S, Telnet/SSH, SNMP, CIFS/NFS, API, WMI, SQL queries, Web Services, command line, and log parsing. Primary communication between the Storage Manager Server and Agents occurs on ports 4319 TCP (HTTP) and 162 UDP (SNMP). Storage Manager Agents Storage Manager Agents reside on operating systems and monitors statistics about the operating system they are installed on The Storage Manager Agent will pull CPU, Memory, Disk (storage and speed), Network Values and File Analysis from the server it is installed on. The Storage Manager Agent can also alert on events generated from the server. 74 Storage Manager

75 Storage Manager Proxy Agents Storage Manager Proxy Agents perform the same task as the Storage Manager Agent yet also include collecting Storage, Application, Virtual and Server information from external devices. Note: To use the Storage Manager Agent as a Storage Manager Proxy Agent, you must install the Agent software on either a Windows or Linux platform. Also note that the Storage Manager Agent and Proxy agent uses the same installer software. In summary the Storage Manager Agent and Storage Manager Proxy agent are the same software. The naming convention comes from how the customer decides to deploy the agent software in their environment. If you want the agent software to just monitor the server it is installed on, this will be considered an agent. If you want the agent software to monitor external devices such as SAN, NAS, Fibre Channel Switches, etc., then we consider this a proxy agent. The following illustration shows, Storage Manager Proxy Agents collecting information from two VMware Virtual Centers and one EMC VNX/Clariion via its SMI-S Provider. Once the Storage Manager Proxy Agent has collected enough data it will send a SNMP trap (UDP port 162, or 20162) to the Storage Manager Server notifying it of data waiting to be received. After receiving the trap, Storage Manager Server, will establish a connection via HTTP or HTTPS Port 4319 to the Storage Manager Proxy Agent and retrieve the data. Once all information has been retrieved, the Storage Manager Proxy Agent deletes the information from its temporary data sub directories and the process starts over again.

76 The Storage Manager Server will take all retrieved information and store it in the Storage Manager database. Note: Click here to see the ports required by Storage Manager Proxy Agents for collecting information. The following tables summarize the differences between Storage Manager Agents and Storage Manager Proxy Agents. Operating Systems Windows 32/64 bit Linux 32/64 bit AIX (PPC 32/64) HP_UX (Itanium) Solaris (SPARC or Intel 32/64 bit) Agent Yes Yes Yes Yes Yes Proxy Agent 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 Diagram The Storage Manager Architecture Diagram illustrates the relationship between sources, the Storage Manager Proxy Agent, and the Storage Manager Server. 76 Storage Manager

77 We will cover the following in this chapter: Deploying Storage Manager Advanced Configuration of Storage Manager

78

79 Deploying Storage Manager This section covers Small, Medium, Large Environments, and Minimum Recommendations for Server Hardware and Memory for Storage Manager Services. We will cover the following in this section: Minimum Recommendations for Small, Medium, and Large Environments Storage Manager Proxy Agent Deployment Number of Storage Manager Agents and Proxy Agent per Storage Manager Server Sample Deployment File Analysis Minimum Recommendations for Small, Medium and Large Environments This chart explains the minimal hardware and memory requirements for Storage Manager Server and Services based on your environment size. Environment Size Resource Monitored Disks/LUNs Total Small Medium Large Up to 500 Up to 3000 Greater than 3000 Physical Servers Up to 100 Up to to 500 Virtual Machines Fibre Channel Switches Minimum Recommendations for Server Hardware Environment Size Small Medium Large

80 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 GB 500GB Proxy Agents Required No **Yes **Yes Minimum Memory Recommendations for Storage Manager Services Environment Size Collector Service Event Receiver Service Maintenance Service Small Medium Large 1024MB (1 GB) 4096MB (4 GB) 8192MB (8 GB) 1024MB (1 GB) 4096MB (4 GB) 4096MB (4 GB) 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) Storage Manager Proxy Agents are required for collecting information from external resources across multiple servers thus reducing workload to the Storage Manager Server. Resources Monitored should be interpreted as XX Virtual Machines and XX Fibre Channel Switches and XX Disk/LUNs before adding proxy agents. See Sample Deployment. 80 Storage Manager

81 It is recommended that you perform maintenance on the Storage Manager database using the dbutil tool. This tool will allow users to run maintenance routines keeping the database running smoothly and make backups of the database. For more information on using this tool see dbutil. Storage Manager Proxy Agent Deployment This chart explains the Recommended Server and Resources for Storage Manager Proxy Agents based on your environment size. Minimum Recommendations for Agent Hardware Environment Size Small Medium Large Server Platform N/A Windows or Linux Architecture N/A x32 or x64 Linux 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 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 Number of Disks/LUNs per Proxy Agent N/A `Resources Monitored should be interpreted as XX Virtual Machines and XX Fibre Channel Switches and XX Disk/LUNs before adding additional proxy agents. See Sample Deployment

82 If you are running VMware VMotion, Storage VMotion or anything that can cause ESX host to dynamically switch to another ESX server be aware of how VMware distributes the load dynamically from one ESX server to another. You should allow for additional room for the switch over. For example, if you are currently running 300 virtual machines on one proxy agent and a switchover occurs, this could allow monitoring of 300 plus virtual machines on your Storage Manager Proxy Agent. Note: It is recommended to have no more than 500 Disk/LUNs PER SMI-S Provider. The Storage Manager 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-S Providers see Architecture. Number of Storage Manager Agents and Proxy Agents per Storage Manager Server The maximum recommended number of Storage Manager Agents and Proxy Agents per Storage Manager Server is 500. If you choose to go beyond 500 Storage Manager Agents then we recommend that you consider multiple Storage Manager Servers. Sample Deployment This example shows how to load balance external devices using Storage Manager Proxy Agents. The following diagram shows one way of assigning resources to proxy agents. Note the three proxy agents at the bottom are monitoring both ESX servers and Fibre Channel switches. Storage Manager Agents are comprised of modules. Each module is responsible for monitoring a different resource on the external device being monitored. Because of this feature, we are able to monitor multiple functions from different devices via one agent. 82 Storage Manager

83

84 The table below gives a breakdown of the devices being monitored in our example and the number of agents needed to monitor those devices. Type of Device Number of Devices Proxy Agent to Device Ratio Number of Proxy Agents Needed Symmetrix/VMAX Array VNX/Clariion Array 2 1: :5 3 NetApp Filers 24 1:10 3 Virtual Machines 600 1:300 3 Fibre Channel Switches 30 1:10 3 All calculations are done using Linux x64 bit agents Since Storage Manager Agents are capable of monitoring multiple resources from different devices, we can go a step further and optimize our setup by spreading the workload out even further thus reducing the number of Proxy Agents needed. Example: The table above can be divided out even further using the Proxy Agent to Device Ratio column in the table above: Agent 1 2 ESX hosts with 200 Virtual Machines, 10 Fibre Channel Switches, 5 Clarrion/VNX arrays Agent 2 2 ESX hosts with 200 Virtual Machines, 10 Fibre Channel Switches, 5 Clarrion/VNX arrays Agent 3 2 ESX hosts with 200 Virtual Machines, 10 Fibre Channel Switches, 2 Clarrion/VNX arrays Agent 4 One Symmetrix/VMAX array Agent 5 - One Symmetrix/VMAX array Agent 6 8 NetApp Filers Agent 7 8 NetApp Filers 84 Storage Manager

85 Agent 8 8 NetApp Filers Note: If you are running VMware VMotion, Storage VMotion or anything that can cause ESX host to dynamically switch to another ESX server be aware of how VMware distributes the load dynamically from one ESX server to another. You should allow for additional room for the switch over. For example, if you are currently running 300 virtual machines on one proxy agent and a switchover occurs, this could allow monitoring of 300 plus virtual machines on your Storage Manager Proxy Agent. In summary we can monitor all of the devices in this example with 8 Proxy Agents. File Analysis It is recommended not to use Storage Manager Server for File Analysis. You should instead use a Storage Manager Proxy Agent. The proxy agent should be dedicated to only running File Analysis and nothing else. This is because of heavy workloads that can be placed on the Storage Manager Proxy Agent due to large file scans. Determining how much File Analysis the Storage Manager Proxy Agent can do is dependent on three things: The number of files being scanned. The rate at which the Storage Manager Proxy Agent can process them. It is best for you to run test in your environment to determine your files per minute (Files/Min). This result can be viewed in the File Analysis Stats Report located in Quick Reports. The time window that you have to process the files. This is generally a few hours to overnight if daily, or weekend if weekly. Ideally, File Analysis should not run on a single target for more than 24 hours. The following formula will help determine if your current deployment of Storage Manager can collect File Analysis 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 Storage Manager Proxy Agent. If it is greater, you need to deploy another Storage Manager Proxy Agent (and so on). For more information on File Analysis see Setting Up File Analysis.

86 Storage Manager Health Status Overview Page Storage Manager (versions 5.7 and above) provides a web console consisting of a central place to view the overall health and status of the Storage Manager software. This includes the Storage Manager Server (STM), Storage Manager Database, and Storage Manager Proxy Agents. The Storage Manager Health Status page provides the following resources: Storage Manager Server Performance Metrics Services Database Status Device Types Storage Manager (STM) Proxy Agents Collection Jobs Queue Help and Support Storage Manager Server Performance Metrics The Storage Manager Server Performance Metrics resource displays the health status of the Storage Manager Server. The following information is provided: CPU utilization Amount of CPU resources being used. Physical Memory (RAM) consumption Amount of RAM being used. Disk Usage Disk space being consumed. Collection List Shows all agents that are waiting for collection. An explanation of warnings that are generated. When the CPU, Memory (RAM) or Disk Usage threshold reaches 70%, the indicator bar will turn yellow meaning warning and when the threshold reaches 90%, it will turn red meaning critical. If the server has less than 8GB of memory (RAM) a warning message will be displayed. 86 Storage Manager

87 Services The Services resource shows Java Heap memory consumption and Java Heap memory allocation of the Storage Manager Services excluding the database service. Note: 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 allocated memory while processed memory is considered used memory. User can learn more about allocating physical memory to the Storage Manager services by clicking the Learn how to allocate physical memory for services link. Users can also learn more about allocating memory to the database by clicking the Learn how to allocate memory to the database link. When a threshold reaches 70%, the indicator bar will turn yellow meaning warning. When a threshold reaches 90%, the indicator bar will turn red meaning critical. If a service is stopped or in a stopped state, it will be labeled as offline. Database Status The Database Status resource provides the current state of the Storage Manager Database. The user will be provided the following information: Displays the size of the database. Displays the largest table and the size. Displays the date of the last dbutil/index rebuild. Database Status also provides the following information and help links: Show Process List - Shows all processes in the MariaDB database. Show Crashed Tables - Shows a list of crashed tables if there are any. Learn to maintain your database Provides information about performing maintenance and fixing crashed tables within the Storage Manager database.

88 Note: If there are any crashed table in the database, a display message will appear notifying the user. The user can 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 Storage Manager. This view provides the following: View Device Collection Status Shows device collection status values. View All Devices Shows a list all devices being monitored by Storage Manager. Devices The type of device being monitored. Total Total number of devices being monitored by Storage Manager. Up The number of devices responding to polling. Down The number of devices up at one time yet are not currently responding to polling. Offline The devices that have never been up and are not responding to polling. Storage Manager (STM) Proxy Agents The STM Proxy Agents resource displays the health status of the proxy agents that have devices assigned to them. The following information is provided: View all agents Displays a full list of proxy agents assigned to Storage Manager. 88 Storage Manager

89 Monitored Devices The number of devices being monitored by the proxy agent. Device Name of the server hosting a Storage Manager Proxy Agent and its current status. CPU utilization Amount of CPU resources being used by the proxy agent. Physical Memory (RAM) consumption Amount of RAM being used by the proxy agent. Disk Usage Amount of disk space being used by the proxy agent. 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 of when the disk will run out of space. When the CPU, RAM or Disk threshold reaches 70%, the indicator bar will turn yellow meaning warning and when the threshold reaches 90%, it will turn red meaning critical. Collection Jobs Queue The Collection Jobs Queue resource provides users with a list of the last 10 devices that were either successful or failed when data collection occurred with a proxy agent. The users will be provided the following: Device Device name. Last Run The last time Storage Manager polled the device to retrieve information. Last run duration - How long it took Storage Manager to retrieve information from the device. Frequency How often Storage Manager polls the device for information.

90 Job type The information Storage Manager requested from the device. Note: The Diagnose link within the Last 10 Failed Jobs provides users with additional information as to why data collection could be failing. Help and Support The Help and Support resource provides users with the following information: Storage Manager Video Resources Thwack Storage Community Storage Manager Help 90 Storage Manager

91 Advanced Configuration of Storage Manager NOTE: This section is only for advanced users. If you are uncomfortable with performing any of the steps below, please contact SolarWinds Support. We will cover the following in this section: Increasing Memory for Storage Manager Services Modifying Database Memory Settings Antivirus and Intrusion Detection Library and Support via Thwack Increasing Memory for Storage Manager Services To increase the memory for your Storage Manager Server services, Storage Manager Agents or Storage Manager Proxy Agents, 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 memory allocation used by the Java Virtual Machine and Xmx defines the maximum amount of memory that Java can use for that service. We will discuss adjusting memory setting for the following Storage Manager Services in this section: Storage Manager Collector Storage Manager Agent or Proxy Agent Storage Manager Event Receiver Storage Manager Poller Storage Manager Maintenance Web Server Memory Database Memory Settings Adjusting memory settings for Storage Manager Collector If you are running a large amount of Storage Manager Proxy Agents, or if your environment switches from small to medium or large, it may be necessary to adjust the memory settings for the Storage Manager Collector Service.

92 The Storage Manager Collector Service is responsible for handling the collection of data from Storage Manager Proxy Agents. The Storage Manager Collector service also acts s a local data collector/agent. The default maximum memory value in a small environment for the Storage Manager Collector service is 1024m. If you need to adjust this value due to a larger polling environment, this section explains how. 1. Stop the collector service for Storage Manager Server. a. For Windows run the Windows application services.msc and look for a service called SolarWinds Storage Manager Collector and stop the service. b. For Linux, SSH to the Storage Manager Server using an account that has root privileges and run the following command /etc/init.d/storage_manager_server stop collector. 2. Locate the collector configuration file. The Java memory settings are located in this file. a. For Windows the file will be located in the <installed drive>\program Files\SolarWinds\Storage Manager Server\webapps\ROOT\bin sub directory. File name is SolarWinds.Storage.Collector.ini. b. 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 per the Sizing Chart below. Example: o -Xmx4096m for a medium environment 4. Save the file and start the collector service. a. For Windows run the Windows application services.msc and look for a service called SolarWinds Storage Manager Collector and start the service. b. For Linux, SSH to the Storage Manager Server using an account that has root privileges and run the following command /etc/init.d/storage_manager_server start collector. Sizing Chart for Storage Manager Collector Service: Environment Size Medium Large 92 Storage Manager

93 Memory 4096m 8192m Note: Linux is the recommended platform for Storage Manager Server when monitoring large environments. ** For environment size specifications see Small, Medium, Large Environments Adjusting memory settings for Storage Manager Agent or Storage Manager Proxy Agent 1. Stop the agent service for Storage Manager Agent or Proxy Agent. a. For Windows run the Windows application services.msc and look for a service called SolarWinds Storage Manager Agent Service. Stop the service. b. For Linux, SSH to the Storage Manager server using an account that has root privileges and run the following command /etc/init.d/storage_manager_agent stop. 2. We must now find the location of the file that contains the memory settings. a. For Windows the file will be located in the <installed drive>\program Files\SolarWinds\Storage Manager Agent sub directory. The file name will be SolarWindsStorage.Agent.ini. b. For Linux, migrate to the /etc/init.d sub directory and using a text editor, open the file called storage_manager_agent. 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 per the Storage Manager Proxy Agent Deployment table. Example: o -Xmx4096M for a medium environment 4. Save the file and start the agent service. a. For Windows run the Windows application services.msc and look for a service called SolarWinds Storage Manager Agent Service. Start the service. b. For Linux, SSH to the Storage Manager Server using an account that has root privileges and run the following command /etc/init.d/storage_manager_agent start. Note: You can turn off Performance Reporting and Real Time Status for improved performance of Storage Manager Proxy Agents.

94 Adjusting Memory Settings for Storage Manager Event Receiver If you are running a large amount of Storage Manager Agents, it may be necessary to adjust the memory settings for the Storage Manager Event Receiver Service. The Storage Manager Event Receiver Service is responsible for receiving traps being sent from Storage Manager Agents. The default maximum memory value in a small environment for the Storage Manager Event receiver is 1GB. Most of the time this value is sufficient for the Storage Manager Server yet if you need to adjust 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 Manager Server\webapps\ROOT\bin. 2. Using a text editor, open the file SolarWinds.Storage.EventReceiver.ini 3. Look for param02=-xmx1024m and modify it to a value that fits your environment per the Sizing Chart below. Example: o 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 per the Sizing Chart below. Example: o -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: 94 Storage Manager

95 Environment Size Medium Large Memory 4096m 4096m For environment size specifications see Small, Medium, Large Environments Adjusting Memory Settings for Storage Manager Poller If you are monitoring a large amount of Fibre Channel Switches or other devices that are polled using SNMP or devices such as EMC Celerra, MS-SQL, or Oracle which do not use SNMP, it may be necessary to adjust 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 EMC Celerra, MS-SQL, and Oracle which do not use SNMP. The default maximum memory value in a small environment for the Storage Manager Poller is 512MB. Most of the time this value is sufficient for the Storage Manager Server yet if you need to adjust this value, this section explains how. The Storage Manager Poller configuration file can be found in the following locations: Storage Manager Server Windows: 1. Go to the <installed drive>\program Files\SolarWinds\Storage Manager Server\webapps\ROOT\bin. 2. Using a text editor, open the file SolarWinds.Storage.Poller.ini 3. Look for param02=-xmx512m and modify it to a value that fits your environment per the Sizing Chart below. Example: o Medium environment will be param02=-xmx2048m 4. Save the file and restart the SolarWinds Storage Manager Poller service via services.msc. Storage Manager 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 per the Sizing Chart below. Example:

96 o 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 Storage Manager Poller Service: Environment Size Medium Large Memory 2048m 4096m For environment size specifications see Small, Medium, Large Environments Adjusting Memory Settings for Storage Manager Maintenance If you have a large database, it may be necessary to adjust the memory settings for the Storage Manager Maintenance Service. The Storage Manager Maintenance Service is responsible for performing maintenance on the database by running the rollup and cleanup scripts. The default maximum memory value in a small environment for the Storage Manager Maintenance is 512MB. Most of the time this value is sufficient for the Storage Manager Server 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: Storage Manager Server Windows: 1. Go to the <installed drive>\program Files\SolarWinds\Storage Manager Server\webapps\ROOT\bin. 2. Using a text editor, open the file SolarWinds.Storage.Maintenance.ini 3. Look for param02=-xmx512m and modify it to a value that fits your environment per the Sizing Chart below.. Example: o Medium environment will be param02=-xmx2048m 4. Save the file and restart the SolarWinds Storage Manager Maintenance service via services.msc. Storage Manager Server Linux: 1. Go to the <installed path>/storage_manager_server/bin directory. 96 Storage Manager

97 2. Using a text editor open the file Maintenance.sh. 3. Look for Xmx and modify it to a value that fits your environment per the Sizing Chart below. Example: o 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: Environment Size Medium Large Memory 2048m 4096m For environment size specifications see Small, Medium, Large Environments Increasing Web Server Memory Most of the time, Web Server memory will not need adjusting. When Storage Manager is initially installed it will check the specifications of the server and adjust itself given the resources provided. If you must adjust the memory settings for the Web Server Service, this section will explain how. 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 //ES//SWStmWebServerSvc. 3. This will open a Web Services Properties GUI. On the Java tab increase the Max Memory Pool to a higher value that fits your environment per the Sizing Chart below.

98 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 called webserver.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 script is JAVA_OPTS="-XX:MaxPermSize=256M -Xmx512M" Increase the Xmx value and modify it to a value that fits your environment per the Sizing Chart below. Example: o Xmx4096m for a medium environment This will increase the maximum memory allocated to the Web Server Service. Next save the file and restart the Storage Manager Web Service by typing the command /usr/bin/storage_manager_server restart webserver. Sizing Chart for Storage Manager Web Server: Environment Size Medium Large Memory 4096m 8192m 98 Storage Manager

99 For environment size specifications see Small, Medium, Large Environments Modifying Database Memory Settings Note: This is an advanced topic and if you feel uncomfortable performing any of the following steps please contact SolarWinds Support. Most of the time, the database memory settings will not need adjusting. When Storage Manager is initially installed it will check the specifications of the server and adjust itself given the resources provided. If you must adjust the memory settings for the database, this section will explain how. Note: Storage Manager versions 5.6 and newer use MariaDB. For versions prior to 5.6, substitute MySQL for MariaDB. Using a text editor, the my.cnf file can be modified to increase various memory settings for the database. File Locations: Windows: <installed drive>:\program Files\SolarWinds\Storage Manager Server\mariadb\my.cnf Linux: <installed path>/storage_manager_server/mariadb/my.cnf The values you may want to consider changing are: key_buffer_size (size of the index buffers held in memory) sort_buffer_size read_buffer_size myisam_sort_buffer_size thread_concurreny max_connections (be careful with this number, it should not exceed 700) tmp_table_size (On a server with a lot of RAM this can dramatically help SQL performance. This should be set to the largest table size in the database) An explanation of what these values mean can be found at

100 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 max_heap_table_size 292 MB 585 MB 1170 MB thread_concurrency max_connections Note: 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 the Storage Manager Collector, Event Receiver, Web, Maintenance and Poller services. Note: After performing changes to database memory it is recommended to run Dbutil. Dbutil is a script that ships with Storage Manager that allows you to run maintenance routines to keep the database running smoothly. It also allows users to perform backups of the database. For more information, see Dbutil. 100 Storage Manager

101 Antivirus and Intrusion Detection Any external software that scans the Storage Manager Database and module files can cause locks and potential corruption. Blockage of ports used by Storage Manager can also cause problems. It is highly recommended that you add the following exclusions to your antivirus and intrusion detections software. 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 Storage Manager Server Exclusions Windows <Install Directory>\Storage Manager Server\agent\systemic <install Directory>\Storage Manager Server\agent\administrative <install Directory>\Storage Manager Server\mariadb C:\Windows\Temp If you are unable to exclude C:\Windows\Temp please perform the following steps. 1. Open my.cnf in C:\Program Files\SolarWinds\Storage Manager Server\mysql 2. Search for "tmpdir". By default it is commented out. Please uncomment and add your desired subdirectory. This example uses a sub directory called MyTemp. (tmpdir=c:/mytemp). Ensure MyTemp folder is created in C drive. It should be forward slash ("/") 3. Add "C:\MyTemp" in Antivirus exclusion list 4. Restart mysql Storage Manager Server Exclusions Linux <Install Directory>/Storage_Manager_Server/agent/systemic <install Directory>/Storage_Manager_Server/agent/administrative <install Directory>/Storage_Manager_Server/mariadb Storage Manager Agent Exclusions Windows <install Directory>\Storage Manager Agent\systemic <install Directory>\Storage Manager Agent\administrative

102 Storage Manager Agent Exclusions Non Windows <install Directory>Storage_Manager_Agent/systemic <install Directory>Storage_Manager_Agent/administrative Port Exclusions for Storage Manager Server and Agents Your Antivirus and Intrusion Detection software must allow access to the following ports. TCP 4319, 8443, 43501, 43502, 43503, UDP 162, 10162, Note: Storage Manager uses UDP 162 by default. If this port is being used by another application, it will use either UDP or Library and Support via Thwack More information about Storage Manager can be found on Thwack at Users are provided the following topics of discussion: Start Using STM Latest Blogs Making the most of STM Most Recent / Popular KB s STM How To Articles STM Video Zone STM Documentation STM Releases Troubleshooting STM What Are We Working On STM Request Pre-Sales Support Submit A Sales Engineering Ticket 102 Storage Manager

103 Chapter 6 Managing User Accounts The User account feature allows you to add, edit, and delete users from Storage Manager. Users' privileges are categorized into several levels, allowing administrators to create filtered views of information based on the user's responsibilities. These filters are created according to groupings of managed devices. This function allows administrators to assign users to the appropriate group or groups of monitored systems for which they are responsible. Adding Users Editing User Profiles Managing User Notifications Setting Up Notifications Adding Users To perform the following you must be logged into the Storage Manager website with an account that has Administrative privileges. The following steps detail how to add a user. Note: The Add User button will be missing when LDAP is enabled. To disable LDAP go to Settings > Server Setup > User Authentication To add a new user: 1. Click Settings > Manage Users 2. Click Add New User then enter the Display Name, and Password. Note: The password must be at least one character long and is case sensitive. Storage Manager will require you to retype the password again in the Confirm Password field. 3. Click Save. There are several user account options to choose from. Root administrator Read Only Administrator- User has read- access only

104 Group Administrator- User access is defined by the root administrator User User access is defined by the root administrator Backup Monitor only Select the levels of user privileges Login Users with login privileges can access event screens as well as device inventory usage and performance reports for all devices in their assigned groups. To grant login privileges, check the Login screen. 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 selected column. Once the groups are selected, click Add to activate the privilege. The user will then have access to those defined group(s). For example, if only the NT Group was selected, then the user would only be able to access Event Lists, Event Histories, Usage Reports and other information about Windows NT systems assigned to the NT group. Users with login privileges can access the Storage Manager application, but the view of the Storage Manager main menu will be filtered. For example: Login users will not see the Administration portion of the menu that contains folders for defining Groups, Devices, Server Setup and Users. In addition, Storage Manager allows you to select the type of data a user can see. Backup - Backup Servers and Clients Server and NAS - All DAS and NAS devices SAN - All SAN devices (Fibre Channel and EMC) Application - Application devices Storage Group - Logical groupings of File systems Management Reports - Can run management reports 104 Storage Manager

105 Administrator Administrators can see all data about all devices in all groups. Administrators also have access to all Storage Manager menus, screens, and reports, including the Administration menu. To grant administrator privileges to a user, check the Administrator field and then click Add. Editing User Profiles To edit a user 1. Click on the Settings icon and find Users in the lower left corner of the Settings website. 2. Options to Add, edit and remove user accounts are available here. Click the link Manager Users 1. Click the Manage icon in the row where that user's name appears on the Users screen. The User's Profile screen is displayed. 2. To edit any User Info fields, click the Edit icon in the User Info frame. Note: If you edit the password, Storage Manager will require you to retype the password again in the Confirm Password field. 3. To change user privileges, check /uncheck the Login and/or Administrator boxes. Startup Screen: Choose the user's startup screen. Managing User Notifications The user Profile page also allows you to enter addresses and configure alert notifications for users. 1. To edit addresses and/or notifications, return to the Profile page of the user you wish to modify. 2. To manager Address click the Edit icon for settings already configured or click the Add account. button to add a new 3. To manager Notifications click the Edit icon for settings already configured or click the Add notification. button to add a new type of

106 Setting up Notifications Users have the option of setting notification policy on either a device-by-device or group basis. For example, if the user knows that a manager in a given department would like to be notified if a critical server is running out of disk space, but does not want to receive about non-critical servers in that group, then the user can specify a notification policy for that server alone. Specifying notification policies by groups can save time, for example, if there are multiple devices in a group, a user can use a single command to specify notification destinations for all of those devices concurrently. To create notification policies, click Edit on the Notifications section at the bottom of the User Profile screen. A screen appears containing a drop-down menu field, allowing you to choose a type from the following options: Devices Groups Selecting either Devices (or Groups) will expand the screen, including a dropdown menu that lists all of the devices (or groups) for which the User has access privileges. Administrators will see all device devices (or groups). 1. You may edit the address of the user or add new addresses. Multiple addresses and aliases can be entered if necessary. Entered addresses will receive notifications from all devices specified in the Notifications field. 2. To modify the list of devices that will send alert notifications to a user, click on the Edit icon in the Notifications frame. 3. Click on the drop-down menu for Choose a Type to select either a group of devices or a specific device to be added to the notifications list. You may also choose the severity of Notifications to be sent: critical, error, warning, information and debug. For more information see Alert Severity. The event receiver is the service which is responsible for receiving alerts, traps events and sending notification to users via . The following explains the actual behavior of the event receiver: When an incoming trap is received, the event receiver checks to see if it already exist in the database 106 Storage Manager

107 If the trap does not exist in the database, (new trap) the event receiver will send notification via to the users assigned to the notification list. If the trap already exist, by default it will increment the counter for that trap and no notification is sent. This prevents the users account from being flooded with trap messages. If you wish to be notified via for each trap received, log into the Storage Manager website and go to Settings > Server Setup:All > GUI and for the option Notification for SNMP Alerts, change First Occurrence only to Every Occurrence. Finally, restart the Storage Manager Event Receiver service to allow the changes to be registered to Storage Manager.

108 Chapter 7 Setting Up the Storage Manager Server The following steps detail the parameters for your Sever Setup. To access the Server Setup function: 1. Click Settings > Server Setup All. Define the parameters of your Storage Manager Server. These parameters control server behavior and are separated into the following functions: Agent Settings Array Settings Database Settings Settings File Analysis Settings GUI Settings Real Time Settings Reporter Settings Server Settings Trap Forwarding Settings User Authentication (LDAP) Virtualization Settings Enabling SSL login for the website Storage Manager database Poller Agent Assignment Agent Settings The Agent Settings define the behavior of the Storage Manager Server when it receives a registration trap from an agent trying to register. Enabling these allows you to receive real time alerts when an agent status changes from yellow to red or from green to yellow. This will send out a trap. 108 Storage Manager

109 Allow Self-Register defines what Storage Manager does when it receives a trap from an agent that is not in the devices table. If set to true, Storage Manager adds the agent to the device table, using the IP address as the device name. Default is yes. Auto Assign OS License determines if Storage Manager automatically assigns an OS RTU License when it registers an agent. Default is yes. Agent Inactivity Threshold Choose the threshold for agent inactivity. If there has been no collection from an agent for the period specified, then an 'Agent not collecting' trap is sent. This trap is only sent for the agents to which the monitor agent check box is selected in the edit page. Agent Status Alert sets Alert status to TRUE/FALSE. Any change made to this parameter should be followed by the restart of the Storage Manager Event Receiver service. Always alert when Agent status is Critical or Warning sets status to TRUE/FALSE. The 'Agent Status Alert' parameter should be set to 'TRUE'. Agent Status Alert Frequency sets Alert Frequency levels. Default is five minutes. The 'Agent Status Alert' parameter should be set to 'TRUE'. Any change made to this parameter should be followed by the restart of the Storage Manager Event Receiver Service. Array Settings The Array Settings control the behavior of the NAS and the Xiotech Magnitude poller. 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 is gathered. C-Level Data Collection Frequency sets the frequency to Daily / Always / Never. Database Settings The Database Settings control the behavior of the Oracle and the SQL-Server Poller.

110 Oracle Performance Polling Frequency allows administrators to specify how often Storage Manager gathers performance data from server-attached Oracle RDBMS. Oracle Usage Polling Frequency allows administrators to specify how often Storage Manager gathers usage data from server-attached Oracle RDBMS. SQL Server Performance Polling Frequency allows administrators to specify how often Storage Manager gathers performance data from serverattached SQL Server RDBMSs. SQL Server Usage Polling Frequency allows administrators to specify how often Storage Manager gathers usage data from server-attached SQL Server RDBMSs. SQL Server Table Fragmentation Hour sets the start time to run the DBCC ms-sql command to collect table fragmentation stats. Settings Server and From specifies the account that Storage Manager will use to send notifications and reports. The defaults should be changed immediately. Server Port: Specify the port to be used for systems that requires authentication. When using secure SMTPS protocol. Server Username & Server Password: Provide valid Username and Password for systems that requires authentication. For example: When using secure SMTPS protocol. Use SMTPS: Select 'Yes' if using systems that requires authentication. Else select 'No'. File Analysis Settings All settings that control the behavior of file analysis and data classification. File Age Categories sets the coding thresholds for File Age reporting values in reports. Always Pre-Select All NAS Shares determines if all shares are selected to be available to assignment to an agent automatically (Yes) or if you have to manually select the shares before you can assign them to an agent (No). Ungrouped File Type Details determines whether to store detailed information on ungrouped file types in database. 110 Storage Manager

111 GUI Settings All settings that control how the GUI behaves at the enterprise level. Server Monitor Refresh Frequency sets the frequency at which you want to refresh the Server monitor. Max Data Points for Storage Trending and Forecasting sets the maximum number of data points that Storage Manager will trend for storage usage. For example, 30 means Storage Manager will go back 30 days (assuming one point per day) while doing analysis. The minimum is 15 points. Server Monitor Filter filters the list of Servers in the Server Monitor and Server Status bar by last collect time. Enable IPAddress Change allows the IP addresses of servers to be changed on the Device Page. Enable Storage -Share Group Assignment by 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 invalid log in attempts in Window Event Log 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. Notifications for SNMP Alerts Select 'First Occurrence' to receive an notification 'once' for the first time when a trap comes in (or) select 'Every Occurrence' to receive an notification 'for every repeated occurrence of the trap. In case of iservice, this sends out an notification every minute, whenever the iservice is down. Real Time Settings Each of the following parameters allows you to set the minimum threshold for the HIGH warning and error conditions 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 an error, Storage Manager will adjust those settings higher to meet the minimums set here (15% and 40% respectively). CPU Error Minimum sets the minimum CPU Busy for a HIGH Error threshold. CPU Warning Minimum sets the minimum CPU Busy for a HIGH Warning threshold. Disk Error Minimum sets the minimum Disk I/O for a HIGH Error threshold.

112 Disk Warning Minimum sets the minimum Disk I/O for a HIGH Warning threshold. Memory Error Minimum sets the minimum Memory for a HIGH Error threshold. Memory Warning Minimum sets the minimum Memory for a HIGH Warning threshold. Network Error Minimum sets the minimum Network I/O for a HIGH Error threshold. Network Warning Minimum sets the minimum Network I/O for a HIGH Warning threshold. Reporter Settings The Reporter settings allow administrators to specify Server parameters. Maximum Report Rows sets 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 files Older Than sets the number of hours or days that published reports are retained. Date Format sets the way dates will be displayed in reports and consoles. Report Charset sets charset encoding for reports. Percent Usage Color Coding sets the color coding thresholds for Percent Usage values in reports and on Device Consoles. Enter "70,80,90" to show 0-70% as Green, 70-80% as Yellow, 80-90% as Orange and % as Red. You can enter from one to three threshold values. Enter "off" to turn off this feature. Server Name sets the name of the Server Server Port sets the port of the Server Chart Font determines the font used in charts. Chart Top X Series determines the value for the Top X series for charts. Server Settings The Server settings control the overall behavior of the Storage Manager Server, the SNMP and DNS Poller. This setting also defines how the server sends and the global configuration of File Age Categories. 112 Storage Manager

113 Delete Log files Older Than sets the duration server log files are retained on the server. SNMP Trap Port sets the port you want to receive traps on. Note: If you change this setting, you should restart the event receiver. Data Retention policy Start Time sets the time you want Data Retention policies to be executed. Data Retention Policies 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 Monitor Enable default is YES. If set to NO, then the functionality of 'Host Not Responding to Ping' trap is disabled. Any change to this parameter either (YES / NO) should be followed by the restart of the Storage Manager Event Receiver service. Web Server Log Level sets the level of Storage Manager Reporter Web Server log messages. Maintenance Log Level sets the level of Storage Manager Reporter Maintenance log messages. Poller Log Level sets the level of Storage Manager Reporter Poller log messages. Event Receiver Log Level sets the level of Storage Manager Reporter Event Receiver log messages. SNMP Table Poll Timeout sets maximum time allowed for polling an SNMP table. Automatic Clearing of Traps Frequency sets frequency to clear traps older than trap age threshold. Automatic Clearing of Traps 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 have defined. Chart Image Format sets the chart image format to either PNG or JPG default format is PNG. Collector Frequency allows administrators to specify the maximum time between collection attempts, ranging from 30 minutes to daily. Every 15 minutes, Storage Manager checks every device and if the time since the last successful data collection is greater than the time specified in this field, the server adds the device to the collection list and attempts to collect data from the agent on that device. SNMP Frequency sets the interval (30 min. to daily) the server uses for SNMP-standard GET commands to collect MIB II data from SNMP-enabled monitored devices.

114 Note: The Storage Manager Event Receiver continues to receive SNMP traps as they arrive regardless of the setting in this field. Trap Forwarding Settings The Storage Manager server and its agents generate traps that are sent to the Storage Manager Trap Receiver. We can also have these traps forwarded to a network operations center. In this sections we will discuss the following: Forwarding Traps for Storage Manager Server Forwarding Traps for Storage Manager Agent Forwarding Traps for Storage Manager Server To forward Storage Manager Server traps to a network operations center, you must configure the trap forwarding features of Storage Manager. You may also setup Alerts based on traps. Storage Manager only forwards Storage Manager traps. To configure Trap Forwarding, navigate to Settings -> Server Setup: All ->Trap Forwarding and configure the following fields. Forward Traps enables the forwarding of traps when set to true. Destination IP sets the IP address of the server to which you want to forward traps. Destination Port sets the port of the server to which you want to forward traps. Community String sets the community string of the server to which you want to forward traps. Disk Usage Warning Limit sets the threshold for a file system, volume or drive that you want to forward as a Warning trap. Disk Usage Critical Limit sets the threshold for a file system, volume or drive that you want to forward as a Critical trap. Disk Usage Error Limit sets the threshold for a file system, volume or drive that you want to forward as an Error trap. In general, you want the Warning Limit to be less than the Critical Limit, which will be less than the Error Limit (ex., 70 < 80 < 90). Persist Trap determines if trap is persisted in database. 114 Storage Manager

115 Forwarding Traps for Storage Manager Agent To forward Storage Manager Agent traps to a network operations center, you must do the following: 1. Click on the Settings button on the Storage Manager website. 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 wish to forward the traps to. 6. Configure the port and community string to your desired settings. 7. Select the Override Agent Values option and click Save. 8. Push your changes to the external agents by clicking the Push button. Note: Storage Manager Agents will not filter any traps being forwarded to a remote host and you will see a lot of traps being logged to the destination server. Filtering of these traps must be done by the destination. The following kb shows how Orion Network Performance Monitor Trap Viewer filters these traps: een+storage+manager+and+orion User Authentication Settings (LDAP Settings) Enabling the following permissions is recommended: Read All Properties Read All Permissions Allowed to Authenticate Change Password Enable LDAP Authentication Enables LDAP Authentication when set to True LDAP Server Display Domain name Provide display name for LDAP server LDAP Server URL Provide URL for LDAP Server LDAP Server Manager DN Provide Distinguished Name (DN) for LDAP Server Manager LDAP Server Manager password Provide password for LDAP Server Manager

116 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 For example: Note: The LDAP Server Manager DN (Distinguished Name) cannot contain forward / or backward \ slashes. Virtualization Settings VM Age Categories by Boot Time sets the coding thresholds for VM Age Categories by Boot Time reporting values in reports. Capacity Forecasting Target Utilization sets the utilization range from 50% to 100% CPU Distribution Category Distribution of the number of CPU cores in the VM. For example, if you set this to 1,2,5, VMs with similar CPU core setups are categorized in the CPU pie chart under the Asset Distribution section. Memory Distribution Category (MB) Distribution of RAM allocated to the VMs. For example, if you set this to 1024,512, VMs with similar RAM capacity are categorized in the Memory pie chart under the Asset Distribution section. Storage Distribution Category (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 Asset Distribution section. 116 Storage Manager

117 Heatmap Percentage Category VM 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 values less than 70 percent report as green, report as yellow and greater than 90 report as red. Values are reported to the VM Group page under the VM Heatmap section. Note: The following table represents the parameters which require a restart of some of the Storage Manager Services for the effect to take place. For all others, the Services do not need to be restarted, but they will take into effect only going forward. No changes will be done to historical data. Server Setup Parameter - Function Name of the parameter Name of the service to be restarted Server Server Server Agent Status Alert Agent Status Alert Frequency Agent Status Alert Frequency SolarWinds Storage Manager Event Receiver SolarWinds Storage Manager Event Receiver SolarWinds Storage Manager Event Receiver Enabling SSL login for the website Some users may want to utilize SSL logins for their website. Enabling SSL Login describes how to set up SSL on the Storage Manager 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. STM already has a self-signed certificate in the <STM Server installation path> /webapps/root/bin directory called "jswis-keystore." If you want to use this keystore, proceed to step 4, otherwise proceed to step 2.

118 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 keystore password. 3. The certificate file is called.keystore and it can be found in the home directory of the user creating it. Save this file to a location outside of the Storage Manager installation directory, for example: C:\STM_Certificate. 4. Using a text editor, open the server.xml file. This file is located in "C:\Program Files\SolarWinds\Storage Manager Server\conf\server.xml" directory. Perform the following changes: Using the self-signed certificate you just created: o <Connector port="8443" protocol="org.apache.coyote.http11.http11niopro tocol" 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_DH E_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"/> Using your own self-signed certificate: o <Connector port="8443" protocol="org.apache.coyote.http11.http11niopro tocol" URIEncoding="UTF-8" disableuploadtimeout="true" connectiontimeout="20000" acceptcount="100" redirectport="8443" enablelookups="false" maxsparethreads="75" minsparethreads="25" keystorefile="c:\stm_certificate\.keystore" keystorepass="solarwinds" SSLEnabled="true" maxthreads="150" scheme="https" secure="true" 118 Storage Manager

119 Notes: 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_DH E_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"/> The port numbers can be modified to whatever port you wish to use for HTTP or HTTPS communication. In the HTTPS connector, the 'keystorefile=' points to the location of the keystore file. In the HTTPS connector, the 'keystorepass=' contains the password for the keystore file. If you update the HTTPS port you must also update the 'redirectport= ' in the HTTP and HTTPS connectors. Save your changes to the server.xml file. 5. Using a text editor, open the web.xml file located in the C:\Program Files\SolarWinds\Storage Manager Server\conf\web.xml directory. 6. Remove the <url-pattern> line and modify it by copying the following lines in the same </web-app> tag location: <url-pattern>/*</url-pattern> <http-method>get</http-method> <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</transportguarantee> </user-data-constraint> </security-constraint> 7. Save the web.xml file. 8. Restart the SolarWinds Storage Manager Web Services service.

120 Manage Agent Assignments Allows you to select devices and assign agents. Select the edit icon for the device you want to assign the agent to. Click Select Agent. Select an agent from the dropdown list and click Save. Note: You can also unassign Agents during this process if the device is a Cluster/ESX host. Storage Manager Database Storage Manager is bundled with its own database. The Storage Manager database is flexible, making the database backup, external access (via ODBC) and handling easy tasks. Note: Using the Storage Manager database s server for applications other than Storage Manager can slow down performance and consume additional CPU devices. Storage Manager Database Port: Storage Manager Database runs its server on port SolarWinds strongly recommends not changing this setting. Contact for assistance if you need to change it The Storage Manager database performs correctly under most situations and in most environments with the default configuration. If performance optimization is required, contact SolarWinds for assistance. Warning: If you installed MariaDB before installing Storage Manager Server, the install will terminate. Only one instance of the MariaDB is supported on the Storage Manager Server. Before installing the Storage Manager Server, stop the MariaDB Windows service (if any) and then uninstall MariaDB. DO NOT manually delete any MariaDB directories even after uninstall is completed! Old database data is located under the MariaDB install directory. 120 Storage Manager

121 Any external utility that scans or backs up the Storage Manager database is NOT recommended instead use Dbutil for backup and maintenance. In this section we will cover: Backing Up Storage Manager Database Database Maintenance using Dbutil Backing up the Storage Manager Database Backing up the Storage Manager Database and data recovery are simple processes. 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 in the following instructions. To back the Storage Manager database: 1. Stop Storage Manager services. 2. Stop MariaDB services. 3. Make a copy of the entire data directory, and put it in a different location: The default path in Windows - <installed drive>:\program Files\SolarWinds\Storage Manager Server\mariadb\data\storage directory. The default path in Linux - <installed path> /Storage_Manager_Server/mariadb/data/storage directory. Note: Versions prior to Storage Manager version 5.6 use either \mysql\data\storage directory for Windows. \mysql\data\storage_manager path for Linux. Data Recovery: Follow these instructions to recover the Storage Manager database. 1. Stop Storage Manager services. 2. Stop MariaDB service. 3. Replace the data directory (see section above for paths) with the backed up directory. 4. Restart MariaDB service. 5. Restart Storage Manager services.

122 Database Maintenance using Dbutil Dbutil is a script that ships with Storage Manager that allows you to make backups of your database and run maintenance routines to keep the database running smoothly. Note: All Storage Manager Services will be halted when this runs. Depending on which platform you are running, directions are below explaining how to run dbutil in your environment. Windows Instructions Linux instructions Running dbutil in Windows The dbutil.bat file will be 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: Set BackupStage=C:\temp\mariadb_backup. 2. Change the path C:\temp\mariadb_backup to the directory where you would like to backup your profiler database. Note: It is recommended that you do not use a directory within the Storage Manager install directory and you need to verify that the location selected has sufficient free disk space for your database. Usage dbutil.bat [backup maintenance] Options Scheduling backup: Copy database to backup directory maintenance: Run database repair/analysis/optimization procedures default (no options specified): Executes maintenance and backup To run this using Windows task scheduler. 1. Open Windows Task Scheduler and Create a Basic Task with your desired schedule (Weekly for example). 2. Set the Action as Start a Program. 122 Storage Manager

123 3. Program/script = \bin\dbutil.bat 4. Set the arguments to "backup" to only do a backup if desired. Running dbutil in Linux The dbutil.bat file will be 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 your profiler database. Note: It is recommended that you do not use a directory within the Storage Manager install directory and you need to verify that the location selected has sufficient free disk space for your database. Usage dbutil.sh [backup maintenance] Options Scheduling backup: Copy database to backup directory maintenance: Run database repair/analysis/optimization procedures default (no options specified): Executes maintenance and backup Create a cron job to run the dbutil.sh on a schedule. For more information on creating cron jobs, see

124

125 Chapter 8 Adding and Configuring Devices The All Devices page displays all the OS and NAS devices that are added to Storage Manager monitoring. See the Configuring Devices for details on adding, editing, and deleting devices as well as details on activating and deactivating polling. Find more details on adding and configuring your devices in the following sections: Adding Storage Arrays Adding Fibre Channel Devices Adding VMware Monitoring Virtualization Dashboard Adding Application Monitoring SnapMirror Monitor Setting Up File Analysis Configuring Devices Use the All Devices section to add, edit, or delete applications and devices. Adding a Device 1. Click the Settings link under the left tree navigation.

126 2. Click All Devices. 3. The All Devices page displays a listing of all devices currently defined in Storage Manager. There are several actions you can take on this page. 4. You can add a device by selecting the device and clicking Add. 5. After entering the necessary information, the device will appear in the device list for management 6. Clicking the icons below allows you to edit, delete, configure Agents, verify the agent health, and download support bundles for the selected device. 126 Storage Manager

127 Editing a Device 1. Click the Edit icon. 2. Enter new information in the desired fields. 3. Click Save. To 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 Storage Manager server. 4. Set the self-register option as 'yes' in Server setup page. Deleting a Device To delete a device from Storage Manager, return to the device screen and click the trash can icon. A dialog box will appear requesting confirmation. Activating/Deactivating Polling Important: From the Edit screen verify that the Active checkbox is checked. For Storage Manager to poll and collect data from a device; the Active checkbox should be checked. Similarly, to stop Storage Manager from collecting or polling data from a device, uncheck the active box. The change will take effect at the next scheduled collection time. Note: Even when a device is marked inactive, you can still change the agent's configuration, the agent will continue to send traps, and you can still view data about that device. Adding Storage Arrays Storage Manager can monitor arrays from different vendors. Find vendor-specific instructions for adding your array to Storage Manager. Note: if there is a firewall between your Storage Manager Agent and your SMI-S provider, you must open HTTP Port 5988 or HTTPS Port 5989 so Storage Manager can collect data from your configured devices. For a complete listing of SMI-S vendors supported see SMI-S Vendor Support Matrix.

128 Using the Add a Device Wizard provides guidance on adding arrays that use SMI-S providers Troubleshooting with the Add a Device Wizard provides details on error messages you might encounter when using the Add a Device Wizard. Storage Manager can monitor these Storage Array types. 3PAR Dell Compellent Dell Equalogic Dell MD3xxx EMC Celera EMC Isilon EMC Symmetrix, DMX, VMAX EMC VNX/CLARiiON Hitachi Data Systems (HDS) HP EVA HP Lefthand P4000 HP XP IBM DS3xxx, DS4xxx, and DS5xxx IBM DS6xxx, DS8xxx IBM ESS IBM N-Series Operations Manager IBM N-Series IBM SVC, V7000 IBM XIV NetApp E-Series LSI NetApp filer NetAPP Operations Manager 128 Storage Manager

129 OnStor Pillar Sun StorageTek 2xxx, 6xxx and FLX Series Sun StorageTek 99xx Series Xiotech Emprise 7000 Xiotech Magnitude 3D 3xxx Xiotech Magnitude 3D 4000 Using the Add A Device Wizard Storage Manager makes adding storage devices easy. Enter the IP address of the array provider, and the wizard will walk you through adding your array. Note: if there is a firewall between your Storage Manager Agent and your SMI-S provider, you must open HTTP Port 5988 or HTTPS Port 5989 so Storage Manager can collect data from your configured devices. 1. From the Getting Started with Storage Manager page, click Add More in the Storage Arrays section, and choose your array from the drop down menu. 2. Add the Provider IP Address, Provider Admin Username, and Provider Password, and click Test Connection or choose an existing provider and click

130 Test Connection. 3. Click Next. 130 Storage Manager

131 4. The Assign Storage Arrays window lists all arrays found on the provider. Each array is listed with the array name configured in the provider, the array type, the number of disks in the array, and the agent to which the array is assigned. The overall License Usage for all arrays is provided 5. Check the box next to each array you want to add, then click Assign to Agent. You can choose multiple arrays. From the drop down menu, choose the agent to which you want to assign the array then click Assign to Agent. 6. Each agent in the Select Agent list displays the number of disks the agent is monitoring. 7. Arrays with disks falling within the allowed license count can be assigned. 8. The total of all disks in the selected arrays needs to be within the allowed license count. 9. In the Node(s) assigned successfully window, click OK. 10. When all your agents are assigned, click Finish.

132 11. Confirm your arrays are added by checking the SAN Groups section in the left-hand navigation: Troubleshooting with the Add a Device Wizard The Add a Device Wizard provides error messages for common problems encountered when adding an array to Storage Manager. 132 Storage Manager

133 The provider for this array is not responding. Make sure you are using the correct Provider IP address and you have the correct credentials. Make sure the network connection between the Storage Manager Server and provider is good. See article, Make sure the network connection between the Agent and Provider on port x or y is good for details on testing the connection. The article, Restarting the SMI-S Provider on Storage Array., provides details on how to restart your array provider. Manual Configuration The provider rejected your login credentials. This message indicates a problem with the provider username or password and password. These are the SMI-S provider username and password. The provider is responding with a namespace different than the array you are trying to configure. Another provider is listening on the IP address and port you entered for your array. Validate that you are using the correct provider IP address.

134 Validate that your array provider is listening on the default ports 5988 or If not, use the manual device creation to add your array. 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. For assistance adding your array to the provider, check your array documentation or refer to you array administrator. Arrays with no Assigned Agents The Arrays with no Assigned Agents message will appear when arrays are found on the provider but are not assigned to an agent. Storage Manager can only report on arrays that are assigned to an agent. Click Cancel and follow the Assign to Agent instructions. Note: if there is a firewall between your Storage Manager Server and your SMI-S provider you will need to open Ports 5988 and 5989 so Storage Manager s discovery can locate the SAN devices configured in the SMI-S provider. 3PAR Find the information you need to add a 3PAR array to Storage Manager. This section includes what you need before you begin, instructions on using the Add a Device Wizard, and guidance for resolving the troubleshooting messages you might encounter. 134 Storage Manager

135 Before you begin The SMI-S provider is embedded in the 3PAR array. There is no need to install a 3 PAR Provider. Note: By default the 3PAR SMI-S Provider is disabled and must be enabled by an administrator before Storage Manager can monitor your 3PAR array. For more information, see the Enabling the 3PAR SMI-S Provider or contact your 3PAR vendor for support. The 3PAR InformOS should be or later Before adding your 3PAR array to Storage Manager, you must collect the information listed in the table below. Provider IP Address IP address of the SMI-S provider Provider Admin Username The Administrator Username for the array you want to monitor Provider Admin Password The Administrator Password for the array you want to monitor Adding the array Use the Add a Device Wizard to add your 3PAR array to Storage Manager Troubleshooting with the Add a Device Wizard Troubleshooting with the Add a Device Wizard provides details and guidance about the error messages you might encounter. Manual configuration Use the manual configuration if you must specify parameters that are not available from the Add a Device Wizard. In Step 1 of the Add a Device Wizard, choose 3PAR.

136 From the Add a Device 3PAR window, click the Manual Configuration link. In the Create New Device for Agent: Storage Array window provide the following information:: Server IP Address: From the drop down menu, select the Storage Manager Agent you want to monitor your array. Device Display Name: Enter a meaningful name for your array. Storage Array Type: Set to Storage Array 3PAR. Active: Keep this box checked. Clearing this check box stops data collection for your array. Click Next. In the Configure Device window, provide the values for the following fields. Status : Select On. User Name : Enter the user name used to access the provider Password : Enter the password used to access the provider. Provider IP Address : Enter the IP address of the provider Node WWN : Enter the 3PAR identifier. Note: Other parameters are editable from this window. Make changes only if you are sure of the parameter value, otherwise leave the default value. Click Test to test the connectivity between the agent and the array s SMI-S provider. You must enter the username, password, and provider IP before you can test the connection. Click Save to save the configuration and push it to the agent to begin monitoring the array. Additional information: 3PAR Versions/Models Features All F Class and T Class InForm OS and higher Asset Storage Performance 136 Storage Manager

137 Requires Storage Yes Manager Agent? Prerequisites IP Address of the 3PAR storage array SMI-S provider is embedded on the storage array. The provider must be started prior to connecting to it. Login to the CLI on the array and run startcim. Type: showcim to confirm Inform OS version Identifier Type: showport, Node_wwn is the identifier Username and Password to the array Credentials Account and password are stored in Storage Manager database and configuration files on Storage Manager Proxy Agent using custom encryption Read/Write Actions Read Only Ports Used Configurable: 5988 (HTTP) or 5989 (HTTPS) used by 3PAR provider. Communication See the STM Ports section below. Can be HTTP/HTTPS between Storage Manager Proxy Agent and 3PAR SMI-S provider. Installation Configuring a 3PAR device Requires a Storage Yes Windows or Linux Manager Proxy Agent? Dell Compellent Find the information you need to add your EMC array to Storage Manager. 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: The SMI-S provider for the Dell Compellent array is contained in the Enterprise Manager as illustrated in the diagram below. Before Storage Manager can monitor you Dell Compellent array, the SMI-S provider must be set up either during the Enterprise Manager installation or at a later time through the Enterprise Manager interface.

138 The Troubleshooting the Dell Compellent Enterprise Manager section contains frequently asked questions and guidance on configuring the Dell Compellent provider. Or contact your Dell Compellent vendor for SMI-S provider support. The Create a local user account section provides guidance on creating a user account in the Enterprise Manager. Before adding your Dell Compellent array to Storage Manager, you must collect the information listed in 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. Note: Dell Compellent does not allow special characters in the password. Adding the array Use the Add a Device Wizard to add your Dell Compellent array to Storage Manager Note: Storage Manager provides no mapping between block storage and file systems. Troubleshooting with the Add a Device Wizard Troubleshooting with the Add a Device Wizard provides details and guidance about the error messages you might encounter. Manual configuration Use the manual configuration if you must specify parameters that are not available from the Add a Device Wizard. In step 1 of the Add a Device Wizard,choose Dell Compellent. From the Add a Device Dell Compellent window, click the Manual Configuration link. 138 Storage Manager

139 In the Create New Device for Agent: Storage Array window, provide the following information: Server IP Address:, From the drop down menu, select the Storage Manager Agent you want to monitor your array. Device Display Name: Enter a meaningful name for your array. Storage Array Type: Set to Storage Array Dell Compellent. Active: Keep this box checked. Clearing this check box stops data collection for your array. Click Next. In the Configure Device window, provide the values for the following fields. Status: Select On. User Name: Enter the user name used to access the provider. Password: Enter the password used to access the provider. Provider IP Address: Enter the IP address of the provider. Storage Center: Enter the IP address of the Dell Compellent. Note: Other parameters are editable from this window. Make changes only if you are sure of the parameter value, otherwise leave the default value. Click Test to test the connectivity between the agent and the array s SMI-S provider. You must enter the username, password, and provider IP before you can test the connection. Click Save to save the configuration and push it to the agent to begin monitoring the array. Additional information Dell Compellent Versions/Mod els Features Requires Storage Storage Center 6.0 Asset Storage Performance No agent installed on array

140 Manager Agent? Prerequisites IP Address/Hostname of the Dell Compellent Storage Center Username and Password of Provider IP Provider CIMOM Name space & Vendor Name space (e.g)/root/pg_interop All these info automatically obtained using s Add a Device option. Credentials Account and passwords are stored in STM database and configuration files on Storage Manager Proxy Agent using custom encryption Read/Write Actions Ports Used Read Only Configurable: 5988 (HTTP) or 5989 (HTTPS) used by Dell Compellent provider. See the STM Ports section below. Can be HTTP/HTTPS between Storage Manager Proxy Agent and Dell Compellent provider. Communicatio n We can verify the connection of provider through our TestProvider Tool[Administrator mode] and execute below command and get the testprovideroutput file. 1)Command:ein / ClassName:CIM_StatisticsCollection 2)Command:ein / ClassName:CIM_HostedCollection 3)Command:ein / ClassName:CIM_StoragePool 4)Command:ein / ClassName:CIM_StorageVolume Requires a Storage Manager Proxy Agent? Yes Windows or Linux Dell Equalogic Find details about adding a Dell Equalogic array to Storage Manager. This section includes what you need before you begin, details about adding your array, and guidance for configuring your array. 140 Storage Manager

141 Before you begin Your array must be installed and running before it can be added to Storage Manager. Contact your array vendor for additional support on installing and troubleshooting your array. Get the IP address of the array. Refer to your array administrator or your array documentation with questions about obtaining this information. Adding 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. Select Agent Select the Storage Manager agent you want to monitor your array. IP Address - Enter the IP address of your array. Active: Keep this box checked. Clearing this check box stops data collection for your array. Click Next>. Configuring the array Click Test to confirm the default values are working. The test can take up to 90 seconds. Click Show Advanced Fields to customize your array configuration. Click Test to confirm the connection. The test can take up to 90 seconds. When the Test Results show successfully connected, save your configuration. Additional information Dell EqualLogic Versions/Models 4.x Features Asset Storage Performance Requires Storage No agent installed on array Manager Agent? Prerequisites IP Address of the storage array

142 Read-only SNMP version 1 community string for the EqualLogic group Credentials UNIX - Run as root Windows - Local System account/domain Account Read/Write Actions Read Only Ports Used 161 (UDP) on the EqualLogic Group IP Communication Requires a Storage Manager Proxy agent? See the Storage Manager Ports section below. Yes Windows or Linux Dell MD3xxx Find the information you need to add your Dell MD3xxx array to Storage Manager. 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 An SMI-S Provider must be installed and configured before Storage Manager can monitor your Dell MD3xxx array. The Dell MD3xxx array requires the installation of a separate SMI-S provider as illustrated in the diagram below. See the Provider section for details on downloading and installing the provider for you Dell MD3xxx array. Or contact your Dell MD3xxx vendor for additional SMI-S provider support. Before adding your Dell MD3xxx array to Storage Manager, you must collect the information listed in the table below. Provider IP address IP address of the SMI-S provider 142 Storage Manager

143 Provider Admin Username The Administrator Username for the SMI-S provider Provider Admin Password The Administrator Password for the SMI-S provider Adding the array Use the Add a Device Wizard to add your Dell MD3xxx array to Storage Manager Troubleshooting with the Add a Device Wizard Troubleshooting with the Add a Device Wizard provides details and guidance about the error messages you might encounter. Manual configuration Use the manual configuration if you must specify parameters that are not available from the Add a Device Wizard. In step 1 of the Add a Device Wizard choose Dell MD3xxx. From the Add a Device Dell MDxxx window, click the Manual Configuration link. In the Create New Device for Agent: Storage Array window, provide the following information: Server IP Address: From the drop down menu, select the Storage Manager Agent you want to monitor your array. Device Display Name: Enter a meaningful name for your array. Storage Array Type: Set to Storage Array Dell MD3K series.. Active: Keep this box checked. Clearing this check box stops data collection for your array. Click Next. In the Configure Device window, provide the values for the following fields. Status: Select On. User Name: Enter the user name used to access the provider. Password: Enter the password used to access the provider. Provider IP Address: Enter the IP address of the provider.

144 Identifier: Enter the array identifier (the WWN of the MD3K array). Note: Other parameters are editable from this window. Make changes only if you are sure of the parameter value, otherwise leave the default value. Click Test to test the connectivity between the agent and the array s SMI-S provider. You must enter the username, password, and provider IP before you can test the connection. Click Save to save the configuration and push it to the agent to begin monitoring the array. EMC Celerra Find details about adding an EMC Celerra array to Storage Manager. This section includes what you need before you 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 Storage Manager. Contact your array vendor for additional support on installing and troubleshooting your array. You need the IP address of your array. Refer to your array administrator or your array documentation for questions about obtaining this IP address. Adding 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 UNIX Device List: Select a UNIX or Linux server to retrieve the NFS shares exposed by the NAS device. Control Station IP Address: Enter the IP Address of the Celerra control station. Device Display Name: Enter a display name for this resource. Control Station Username: Enter name of the user with permissions to log into the control station. Control Station Password: Enter the password for the user with permissions to log into the control station. 144 Storage Manager

145 TCP Dump: Control Station Root Password: Enter the password of the root user with permissions to log into the control station TCP Dump Data Mover IP Address: Enter the IP Address of a data mover that is chosen to store temporary files. The user defined above must have access to this file system. TCP Dump: Data Mover File system: Enter the name of the file system chosen to store temporary files. The user defined above must have access to this file system. 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. Active: Keep this box checked. Clearing this check box stops data collection for your array. Configuring the array In the Configure Device window, click Test to confirm the default values are working. Click the Show Advanced Fields to customize your array configuration. Click Test to confirm the configuration is working. When the Test Results show Successfully connected, save your configuration to begin monitoring the array. Additional information EMC Celerra Versions/Models NS Series Features Asset Storage Performance VDMs Data Classification (File Analysis) Requires Storage No Manager Agent? Prerequisites nasadmin login or equivalent Same login for all Control Stations; passwords can be different SSH connectivity between Storage Manager Server and EMC Control Station

146 Credentials Read/Write Actions Ports Used Communication Data Classification Requires a Storage Manager Proxy Agent? Account and password are stored in Storage Manager database and configuration files on Storage Manager Proxy Agent using custom encryption Read Only Non-Configurable: 22 on the Control station SSH between Storage Manager Server and each EMC Control Station Occurs via Storage Manager Proxy Agent. CIFS Shares require a Storage Manager Windows Agent and domain account to access the shares being analyzed NFS Shares require a Storage Manager UNIX Agent and root access to shares being analyzed. Yes via Storage Manager Server EMC Isilon Find details about adding an EMC Isilon array to Storage Manager. This section includes what you need before you 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 Storage Manager. Contact your array vendor for additional support on installing and troubleshooting your array. Collect the information in the table below.ip Address SNMP community string IP address of the EMC Isilon cluster. The SNMP community string is configured on the EMC Isilon array. Refer to your array administrator or your array documentation with questions about obtaining this information. Adding 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. 146 Storage Manager

147 Select Agent Select the Storage Manager agent you want to monitor your array. Windows Device List Select a Windows server to retrieve the CIFS shares exposed by the NAS devise. UNIX Device List - Select a Unix or Linux server to retrieve the NFS shares exposed by the NAS devise. IP Address Enter the IP address of your EMC Isilon array. Device Display Name Enter a descriptive name for your device. This will be displayed within Storage Manager. Active: Keep this box checked. Clearing this check box stops data collection for your array. Configuring the array Click Test to confirm the default values are working. The test can take up to 90 seconds. Click Show Advanced Fields to customize your array configuration. Click Test to confirm the connection. The test can take up to 90 seconds. When the Test Results show Successfully connected, save your configuration to begin monitoring the array. EMC Symmetrix, Symmetrix DMX, Symmetrix VMAX, VNX/CLARiiON Find the information you need to add your EMC array to Storage Manager. This section provides 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: Use these instructions for these EMC arrays:

148 VNX/CLARiiON array EMC Symmetrix array Symmetrix DMX array Symmetrix VMAX array Before you begin An SMI-S provider must be installed and configured before Storage Manager can monitor your VNX/CLARiiON, Symmetrix, DMX, and VMAX arrays. The EMC provider is a separate piece of software as illustrated in the diagram below. See the EMC Provider section for information on downloading, installing, and configuring the software for this provider. Or contact your EMC vendor for additional SMI-S provider support. Collect the information listed in the table below before adding your array to Storage Manager. Provider IP address IP address of the SMI-S provider Provider Admin Username The Administrator Username for the EMC provider Provider Admin Password The Administrator Password for the EMC provider Adding the array Use the Add a Device Wizard to add your array to Storage Manager Note: Storage Manager provides no mapping between block storage and file systems. 148 Storage Manager

149 Troubleshooting with the Add a Device Wizard Troubleshooting with the Add a Device Wizard provides details and guidance about the error messages you might encounter Manual configuration Use the manual configuration if you must specify parameters that are not available from the Add a Device Wizard. In step 1 of the Add a Device Wizard,choose EMC Symmetrix, DMX, VMAX. From the Add a Device EMC Symmetrix, DMX, VMAX window, click the Manual Configuration link. In the Create New Device for Agent: Storage Array window, provide the following information: Server IP Address: From the drop down menu, select the Storage Manager Agent you want to monitor your array. Device Display Name: Enter a meaningful name for your array. Storage Array Type: Set to Storage Array EMC Symmetrix.. Active: Keep this box checked. Clearing this check box stops data collection for your array. Click Next. In the Configure Device window, provide the values for the following fields. Status: Select On. User Name: Enter the user name used to access the provider. Password: Enter the password used to access the provider. Provider IP Address: Enter the IP address of the provider. Serial No: Enter the array identifier (the serial number of the Symmetrix/DMX array). Note: Other parameters are editable from this window. Make changes only if you are sure of the parameter value, otherwise leave the default value. Click Test to test the connectivity between the agent and the array s SMI-S provider. You must enter the username, password, and provider IP before you can test the connection.

150 Click Save to save the configuration and push it to the agent to begin monitoring the array. EMC VNX/CLARiiON Find details about adding an EMC VNX/CLARiiON array to Storage Manager. This section includes what you need before you begin, details about adding your array, and guidance for configuring your array. Before you begin An SMI-S provider must be installed and configured before Storage Manager can monitor your VNX/CLARiiON array. The EMC provider is a separate piece of software as illustrated in the diagram below. See the EMC Provider section for information on downloading and installing the software for this provider. Or contact your EMC vendor for additional SMI-S provider support. Collect the information listed in the table below before adding your array to Storage Manager. Provider IP address IP address of the SMI-S provider Provider Admin Username The Administrator Username for the EMC provider Provider Admin Password The Administrator Password for the EMC provider Adding the array Use the Add a Device Wizard to add your array to Storage Manager Note: Storage Manager provides no mapping between block storage and file systems. 150 Storage Manager

151 Troubleshooting with the Add a Device Wizard Troubleshooting with the Add a Device Wizard provides details and guidance about the error messages you might encounter Manual configuration Use the manual configuration if you must specify parameters that are not available from the Add a Device Wizard. In step 1 of the Add a Device Wizard,choose EMC VNX/CLARiiON. From the Add a Device EMC VNX/CLARiiON window, click the Manual Configuration link. In the Create New Device for Agent: Storage Array window, provide the following information: Server IP Address: From the drop down menu, select the Storage Manager Agent you want to monitor your array. Device Display Name: Enter a meaningful name for your array. Storage Array Type: Set to Storage Array EMC VNX/CLARiiON.. Active: Keep this box checked. Clearing this check box stops data collection for your array. Click Next. In the Configure Device window, provide the values for the following fields. Status: Select On. User Name: Enter the user name used to access the provider. Password: Enter the password used to access the provider. Provider IP Address: Enter the IP address of the provider. Serial No: Enter the array identifier (the serial number of the VNX/CLARiiON array). Note: Other parameters are editable from this window. Make changes only if you are sure of a parameter value, otherwise leave the default value. Click Test to test the connectivity between the agent and the array s SMI-S provider. You must enter the username, password, and provider IP before you can test the connection.

152 Click Save to save the configuration and push it to the agent to begin monitoring the array. Additional information EMC VNX/CLARiiON Series Versions/Models All Features Asset Storage Performance Requires Storage No agent installed on array. Manager Agent? Prerequisites IP Addresses of Controller A (SPA) and Controller B (SPB) Identify firmware/flare code of array and confirm it is compatible with latest SMI-S provider. *Some older firmware is only compatible with older SMI-S provider versions. If the array has Flare Code 26 it requires EMC SMIKit (Provider 3.2.2) and higher Install EMC Solutions Enabler with SMI-S on a Windows/Linux server with IP connectivity to the array controllers. User account on Unisphere with admin/manager privileges on the CX array For each CX, enable "Statistics Logging" for all storage processors via Unisphere If SMI-S provider is on a server connected to the SAN being monitored see FAQ-92. Note: CX600 arrays require a Flare code higher than 16 (2.16.x.x.x) for data to be gathered using SMI-S Credentials Account and password are stored in Storage Manager database and configuration files on Storage Manager Proxy Agent using custom encryption Read/Write Actions Read Only Ports Used Configurable: 5988 (HTTP) or 5989 (HTTPS) used by EMC Solutions Enabler Non-configurable: TCP Port 443 bi-direction between provider and VNX/Clariion. Communication See the Storage Manager Ports section below. Can be HTTP/HTTPS between Storage Manager Proxy Agent and EMC Solutions Enabler 152 Storage Manager

153 Requires a Storage Manager Proxy Agent? Yes Windows or Linux Hitachi Data Systems (HDS) Find the information you need to add your Hitachi Data Systems (HDS) array to Storage Manager. This section provides 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 The SMI-S provider for your HDS array is part of the HiCommand Device Manager as illustrated in the diagram below. See the Hitachi Data Systems (HDS) Provider section for details on installing the HDS provider in the HiCommand Device Manager. Or contact your HDS vendor for additional SMI-S provider support. Before adding your HDS array to Storage Manager, you must collect the information listed in the table below. Provider IP address IP address of the SMI-S provider Provider Admin Username Provider Admin Password The Administrator Username set up when adding a subsystem to the HiCommand Device Manager The Administrator Password set when adding a subsystem to the HiCommand Device Manager See, How do I Add a Subsystem?, for more information about adding subsystems to the HiCommand Device Manager. Adding the array Use the Add a Device Wizard to add your HDS array to Storage Manager

154 Troubleshooting with the Add a Device Wizard Troubleshooting with the Add a Device Wizard provides details and guidance about the error messages you might encounter. Manual configuration Use the manual configuration if you must specify parameters that are not available from the Add a Device Wizard. In step 1 of the Add a Device Wizard, choose HDS. From the Add a Device HDS window, click the Manual Configuration link. In the Create New Device for Agent: Storage Array window, provide the following information: Server IP Address: From the drop down menu, select the Storage Manager Agent you want to monitor your array. Device Display Name: Enter a meaningful name for your array. Storage Array Type: Set to Storage Array HDS.. Active: Keep this box checked. Clearing this check box stops data collection for your array. Click Next. In the Configure Device window, provide the values for the following fields. Status: Select On. User Name: Enter the user name used to access the provider. Typically it is the HiCommand Device Manager login. Password: Enter the password used to access the provider. Provider IP Address: Enter the IP address of the provider. Serial No: Enter the array serial number. Note: Other parameters are editable from this window. Make changes only if you are sure of a parameter value, otherwise leave the default value. Click Test to test the connectivity between the agent and the array s SMI-S provider. You must enter the username, password, and provider IP before you can test the connection. 154 Storage Manager

155 Click Save to save the configuration and push it to the agent to begin monitoring the array. HP EVA Find the information you need to add your HP EVA array to Storage Manager. This section provides 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 The SMI-S provider is part of your HP EVA Command View as illustrated in the diagram below. The HP provider must be installed and configured before you can add your HP EVA array to Storage manager. The HP Provider can be installed through Command View or can be downloaded and installed separately. See the HP Eva Provider section for details on installing and configuring this provider. Or contact your HP EVA vendor for more HP EVA SMI-S provider support. Before adding your HP EVA array to Storage Manager, you must collect the information listed in the table below. Provider IP address IP address of the SMI-S provider 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 See the Adding Users to HP Groups for more information on the HP Storage Admin Group Adding the array Use the Add a Device Wizard to add your array to Storage Manager

156 Note: Storage Manager provides no mapping between block storage and file systems. Troubleshooting with the Add a Device Wizard Troubleshooting with the Add a Device Wizard provides details and guidance about the error messages you might encounter. Manual configuration Use the manual configuration if you must specify parameters that are not available from the Add a Device Wizard. In step 1 of the Add a Device Wizard,choose HP EVA. From the Add a Device EVA window, click the Manual Configuration link. In the Create New Device for Agent: Storage Array window, provide the following information: Server IP Address: From the drop down menu, select the Storage Manager Agent you want to monitor your array. Device Display Name: Enter a meaningful name for your array. Storage Array Type: Set to Storage Array HP EVA. Active: Keep this box checked. Clearing this check box stops data collection for your array. Click Next. In the Configure Device window, provide the values for the following fields. Status: Select On. User Name: Enter the user name used to access the provider. Typically this is the Command View EVA login in the formant DomanName\userName. For a local user, this is <MachineName\UserName>. Password: Enter the password used to access the provider. Provider IP Address: Enter the IP address of the provider. Node WWN: Enter the array identifier (the Node WWN of the HP EVA array). Specify the Node WWN without the dashes. 156 Storage Manager

157 Note: Other parameters are editable from this window. Make changes only if you are sure of a parameter value, otherwise leave the default value. Click Test to test the connectivity between the agent and the array s SMI-S provider. You must enter the username, password, and provider IP before you can test the connection. Click Save to save the configuration and push it to the agent to begin monitoring the array. Additional information HP EVA Versions/Models 4000, 5000, 6000, 8000 Features Asset Storage Performance Requires Storage No Manager Agent? Prerequisites CommandView 8.02 with SMI-S CIMOM installed is recommended by HP, but CommandView 7.x will provide asset and storage info. EVA8000 requires CommandView and Firmware 6200 for Storage Manager to be able to show array Performance. CommandView ID and Password for the provider. Define user account on Command View EVA managing EVAs. Local user for CV-EVA v7.x; Domain/Local user for CV-EVA v8.x Credentials Account and password are stored in Storage Manager database and configuration files on Storage Manager Proxy Agent using custom encryption Read/Write Actions Read Only Ports Used Configurable: 5988 (HTTP) or 5989 (HTTPS) used by HP CommandView Communication See the Storage Manager Ports section below. Can be HTTP/HTTPS between Storage Manager Proxy Agent and HP CommandView Requires a Storage Manager Proxy Agent? Yes Windows or Linux

158 HP Lefthand P4000 Find details about adding an HP LeftHand P4000 array to Storage Manager. This section includes what you need before you 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 Storage Manager. Contact your array vendor for additional support on installing and troubleshooting your array. Get the IP address of your array. Refer to your array administrator or your array documentation with questions about obtaining this information. Adding the array When adding a device, choose HP LeftHand P4000 from the Choose your Array Type menu. Click OK. Fill in the fields In the Create New Device for Agent: HP P4000 Series window. Select Agent: Select an Agent for this device. IP Address: Enter the IP address of your array that you obtained in the Before you begin section. Device Display Name: Enter the name you want displayed for this resource. Active: Keep this box checked box. Clearing this check box stops data collection for your array. Click Next. Configuring the array Test your array In the Configure Device window. Click Test to confirm the default values are working. The test can take up to 90 seconds. Click Show Advanced Fields to customize your array configuration. Click Test to confirm the connection. The test can take up to 90 seconds When the Test Results show Successfully connected, save your configuration For details on enabling SNMP polling, see Enabling SNMP for HP LeftHand. 158 Storage Manager

159 Additional information HP P Series (LeftHand) Versions/Models P4000 Features Asset Configuration Storage Requires Storage No Manager Agent? Prerequisites SNMP enabled IP address of management node and each node Storage Manager Proxy Agent in Access Control List Credentials Account and password are stored in Storage Manager database and configuration files on Storage Manager Proxy Agent using custom encryption Read/Write Actions Read Only Ports Used 161 on management node and each node Communication See the Storage Manager Ports section below. SNMP from Storage Manager Proxy Agent to management node and each node Requires a Storage Yes Windows or Linux Manager Proxy Agent? HP XP Find details on how to add your HP XP array to Storage Manager. 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 The HP XP array requires an SMI-S provider before it can be monitored by Storage Manager. The HDS provider is part of the HiCommand Device Manager as illustrated in the diagram below.

160 See the Hitachi Data Systems (HDS) Provider section for details on installing the HDS provider in the HiCommand Device Manager. Or contact your HP XP vendor for HDS SMI-S provider support. Before adding your HP XP array to Storage Manager, you must collect the information listed in the table below. Provider IP address IP address of the SMI-S provider Provider Admin Username Provider Admin Password The Administrator Username set up when adding a subsystem to the HiCommand Device Manager The Administrator Password set when adding a subsystem to the HiCommand Device Manager See How do I Add a Subsystem? For more information about adding subsystems to the HiCommand Device Manager. Adding the array Use the Add a Device Wizard to add your HP XP array to Storage Manager Troubleshooting with the Add a Device Wizard Troubleshooting with the Add a Device Wizard provides details and guidance about the error messages you might encounter. Manual configuration Use the manual configuration if you must specify parameters that are not available from the Add a Device Wizard. In step 1 of the Add a Device Wizard,choose HP XP. From the Add a Device HP XP window, click the Manual Configuration link. In the Create New Device for Agent: Storage Array window, provide the following information: Server IP Address: From the drop down menu, select the Storage Manager Agent you want to monitor your array. Device Display Name: Enter a meaningful name for your array. 160 Storage Manager

161 Storage Array Type: Set to Storage Array HP XP. Active: Keep this box checked. Clearing this check box stops data collection for your array. Click Next. In the Configure Device window, provide the values for the following fields. Status: Select On. User Name: Enter the user name used to access the provider. Typically this is the HiCommand Device Manager. Password: Enter the password used to access the provider. Provider IP Address: Enter the IP address of the provider. Identifier: Enter the serial number for the array. Note: Other parameters are editable from this window. Make changes only if you are sure of a parameter value, otherwise leave the default value. Click Test to test the connectivity between the agent and the array s SMI-S provider. You must enter the username, password, and provider IP before you can test the connection. Click Save to save the configuration and push it to the agent to begin monitoring the array. IBM DS3xxx, DS4xxx, DS5xxx Find the information you need to add your IBM DS 3xxx, IBM DS4xxx, and DS5xxx arrays to Storage Manager. 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 An SMI-S provider must be installed and configured before you can add the IBM DS3xxx, DS4xxx, or DS5xxx array to Storage Manager. The SMI-S provider is a separate piece of software as illustrated in the diagram below.

162 See the Provider section for more information on downloading and installing the provider software or contact IBM for support. Before adding your IBM DS3xxx, DS4xxx, IBM DS5xxx array to Storage Manager, you must collect the information listed in the table below. Provider IP address IP address of the SMI-S provider Provider Admin Username The Administrator Username is assigned when the SMI-S provider is installed. Provider Admin Password The Administrator Password is assigned when the SMI-S provider is installed. Adding the array Use the Add a Device Wizard to add your array to Storage Manager Troubleshooting with the Add a Device Wizard Troubleshooting with the Add a Device Wizard provides details and guidance about the error messages you might encounter. Manual configuration Use the manual configuration if you must specify parameters that are not available from the Add a Device Wizard. In step 1 of the Add a Device Wizard,choose IBM DS3xxx, DS4xxx, DS5xxx. From the Add a Device IBM DS3xxx, DS4xxx, DS5xxx window, click the Manual Configuration link. In the Create New Device for Agent: Storage Array window, provide the following information: Server IP Address: From the drop down menu, select the Storage Manager Agent you want to monitor your array. Device Display Name: Enter a meaningful name for your array. 162 Storage Manager

163 Storage Array Type: Set to Storage Array IBM DS 3k, 4k, 5k series. Active: Keep this box checked. Clearing this check box stops data collection for your array. Click Next. In the Configure Device window, provide the values for the following fields. Status: Select On. User Name: Enter the user name used to access the provider. Password: Enter the password used to access the provider. Provider IP Address: Enter the IP address of the provider. Storage Array WWN: Enter the array identifier (WWN of the IBM DS3xxx, DS4xxx, and DS5xxx array). Note: Other parameters are editable from this window. Make changes only if you are sure of a parameter value, otherwise leave the default value. Click Test to test the connectivity between the agent and the array s SMI-S provider. You must enter the username, password, and provider IP before you can test the connection. Click Save to save the configuration and push it to the agent to begin monitoring the array. Additional information IBM DS 3K, 4K, 5K Versions/Models 3000, 4000, 5000 Features Asset Storage Performance - Disk Performance Requires Storage No Manager Agent? Prerequisites IP Address of Storage Processors Latest LSI Engenio SMI-S Provider installed on a 32 bit Windows/Linux server that has IP connectivity to the storage processors

164 Credentials Account and password are stored in Storage Manager database and configuration files on Storage Manager Proxy Agent using custom encryption Read/Write Actions Read Only 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 from SMI-S provider. Communication See the Storage Manager Ports section below.. Can be HTTP/HTTPS between Storage Manager Requires Storage Manager Proxy Agent? IBM DS6xxx and DS8xxx Proxy Agent and the LSI Engenio SMI-S provider. Yes Windows or Linux Find details on how to add your IBM DS6xxx or DS8xxx arrays to Storage Manager. 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 An SMI-S Provider must be installed and configured before you can add IBM DS6xxx or DS8xxx arrays to Storage Manager. The IBM Provider is a separate piece of software as illustrated in the diagram below. For more information about downloading and installing an IBM Provider, see the IBM Provider FAQ or contact IBM for support. Before adding your IBM DS6xxx or IBM DS8xxx arrays to Storage Manager, you must collect the information listed in the table below. Provider IP address IP address of the SMI-S provider 164 Storage Manager

165 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. Adding the array Use the Add a Device Wizard to add your array to Storage Manager Troubleshooting with the Add a Device Wizard Troubleshooting with the Add a Device Wizard provides details and guidance about the error messages you might encounter. Manual configuration Use the manual configuration if you must specify parameters that are not available from the Add a Device Wizard. In step 1 of the Add a Device Wizard,choose IBM DS6xxx, DS8xxx From the Add a Device IBM DS6xxx, DS8xxx window, click the Manual Configuration link. In the Create New Device for Agent: Storage Array window, provide the following information: Server IP Address: From the drop down menu, select the Storage Manager Agent you want to monitor your array. Device Display Name: Enter a meaningful name for your array. Storage Array Type: Set to Storage Array IBM DS 6k/8k series. Active: Keep this box checked. Clearing this check box stops data collection for your array. Click Next. In the Configure Device window, provide the values for the following fields. Status: Select On. User Name: Enter the user name used to access the provider. Password: Enter the password used to access the provider. Provider IP Address: Enter the IP address of the provider.

166 Storage Array WWN: Enter the array identifier (WWN of the IBM DS6xxx or DS8xxx array). Note: Other parameters are editable from this window. Make changes only if you are sure of a parameter value, otherwise leave the default value. Click Test to test the connectivity between the Storage Manager Proxy Agent and the array s SMI-S provider. You must enter the username, password, and provider IP before you can test the connection. Click Save to save the configuration and push it to the Storage Manager Proxy Agent to begin monitoring the array. Additional information IBM DS 6K, 8K Versions/Models 6000, 8000 Features Asset Storage Performance Requires Storage No Manager Agent? Prerequisites IP Address of the Storage Manager ID and Password to Storage Manager Latest IBM SMI-S Provider installed on a Windows/Linux server that has IP connectivity to the Storage Manager server. Can also monitor these via the HMC. Needs to be enabled via IBM. Credentials Read/Write Actions Ports Used Account and password stored in Storage Manager database and configuration files on Storage Manager Proxy Agent using custom encryption Read Only Configurable: 5988 (HTTP) or 5989 (HTTPS) used by SMI-S provider Communication See the Storage Manager Ports section below. Can be HTTP/HTTPS between Storage Manager Proxy Agent and the IBM SMI-S provider. Requires a Storage Yes Windows or Linux Manager Proxy Agent? 166 Storage Manager

167 IBM ESS Find details on how to add your IBM ESS array to Storage Manager. 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 An SMI-S Provider must be installed and configured before you can add a IBM ESS array to Storage Manager. The IBM Provider is a separate piece of software as illustrated in the diagram below. For more information about downloading and installing an IBM Provider, see the IBM Provider FAQ or contact IBM for support. Before adding your IBM ESS array to Storage Manager, you must collect the information listed in the table below. Provider IP address IP address of the SMI-S provider 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. Adding the array Use the Add a Device Wizard to add your array to Storage Manager Troubleshooting with the Add a Device Wizard Troubleshooting with the Add a Device Wizard provides details and guidance about the error messages you might encounter.

168 Manual configuration Use the manual configuration if you must specify parameters that are not available from the Add a Device Wizard. In step 1 of the Add a Device Wizard,choose ESS. From the Add a Device ESS window, click the Manual Configuration link. In the Create New Device for Agent: Storage Array window, provide the following information: Server IP Address: From the drop down menu, select the Storage Manager Agent you want to monitor your array. Device Display Name: Enter a meaningful name for your array. Storage Array Type: Set to Storage Array IBM ESS. Active: Keep this box checked. Clearing this check box stops data collection for your array. Click Next. In the Configure Device window, provide the values for the following fields. Status: Select On. User Name: Enter the user name used to access the provider. Password: Enter the password used to access the provider. Provider IP Address: Enter the IP address of the provider. Storage Array WWN: Enter the array identifier (WWN of the IBM ESS array). Note: Other parameters are editable from this window. Make changes only if you are sure of a parameter value, otherwise leave the default value. Click Test to test the connectivity between the Storage Manager Proxy Agent and the array s SMI-S provider. You must enter the username, password, and provider IP before you can test the connection. Click Save to save the configuration and push it to the Storage Manager Proxy Agent to begin monitoring the array. 168 Storage Manager

169 IBM N-Series Operations Manager Find details about adding an IBM N Series Operations Manager array to Storage Manager. This section includes what you need before you 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 Storage Manager. Contact your array vendor for additional support on installing and troubleshooting your array. You must obtain the following information: o o o o DFM Server IP Address Username Password Contact your array administrator or refer to your array documentation for questions about obtaining this information. Note: One or more Storage Manager Proxy Agents for Windows/Unix/Linux must be used to perform File Analysis on an IBM N-Series. Use Windows Proxy Agents to perform analysis on CIFS shares, and Unix/Linux Proxy Agents to perform analysis on NFS mounts. Adding 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. Select Agent Select the Storage Manager Proxy Agent you want to monitor your array. DFM Server IP Address - Enter the IP address of the DFM Server. Click Next>. Configuring the array Enter the username and password you obtained in the Before you begin section. For the other values, you can use the default values or you can click Show Advanced Fields to enter your custom values.

170 Click Save. IBM N-Series Find details about adding an IBM N-Series array to Storage Manager. This section includes what you need to know before beginning. Before you begin Your array must be installed and running before it can be added to Storage Manager. Contact your array vendor for additional support on installing and troubleshooting your array. IP address of the IBM N-Series to be monitored. IBM N-Series login credentials, typically root or equivalent. The selected Storage Manager Proxy Agent is in the list of IBM N-Series trusted hosts. Windows Security Context: Please ensure that the Storage Manager Proxy Agent service is running with the "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 Storage Manager Proxy Agents, then the following items are required to collect data via a DFM Server: Ensure that a Storage Manager Proxy Agent is running on the server to be used to monitor this IBM N-Series DFM Server IP address IBM N-Series IP address used by DFM Server Ensure that the IBM N-Series IP address is accessible to DFM Server via http/https DFM Server login with GlobalFullControl privileges Note: One or more Storage Manager Proxy Agents for Windows/Unix/Linux must be used to perform File Analysis on an IBM N-Series. Use Windows Proxy Agents to perform analysis on CIFS shares, and Unix/Linux Proxy Agents to perform analysis on NFS mounts. Adding the array When adding a device, choose IBM N-Series from the Choose your Array Type menu then Click OK. Complete the fields in the Create New device for Agent: IBM N Series window. 170 Storage Manager

171 Select Agent: Select the Storage Manager Proxy Agent you want to monitor the IBM N-Series. IBM N Series IP Address: enter the IP Address of the IBM N-Series / IBM N-Series's head Device Display Name: Enter a descriptive name for the IBM N-Series device (ex:ibmn NY) Active: Keep this box checked. Clearing this check box stops data collection for your array. Cost Per GB: Optional - the cost per GB of storage on this IBM N-Series to be used for chargeback purposes Click Next>. Configuring the array Status : Select On Username: Enter the username used to access the IBM N-Series Password: Enter the password used to access the IBM N-Series DFM Server IP Address: Enter the IP address of the DFM server if the IBM N-Series is to be monitored via a DFM Server. Leave as blank otherwise. Click Save. Additional Information Versions/Models Features Requires Storage Manager Agent? NetApp and IBM N-Series All Asset Storage Performance No Prerequisites IP Address of NetApp head/cluster node Define user account on NetApp. Minimum access - a role with access to execute specific API calls. List available upon request. Usually provided just the root login

172 Add the Storage Manager Proxy Agent to list of trusted hosts on the NetApp storage system ONTAP 7.3.x: Turn off API XML validation on each filer (FAQ-132) Credentials Account and password are stored in Storage Manager database and configuration files on Storage Manager Proxy Agent using custom encryption Read/Write Read Only Actions Ports Used 80 (HTTP)/443 (HTTPS) on NetApp head/cluster node Any available for CIFS/NFS Communication See the Storage Manager Ports section below. Can be HTTP/HTTPS between Storage Manager Proxy Agent and the NetApp head/cluster node Data Classification Occurs via Storage Manager Proxy Agent. CIFS Shares require a Storage Manager Windows Agent and domain account to access the shares being analyzed NFS Shares require a Storage Manager UNIX Agent and root access to shares being analyzed. Requires Storage Manager Proxy Agent? Yes IBM SVC, V7000 Find the information you need to add IBM SVC and IBM Storwize V7000 arrays to Storage Manager. This section includes what you need before you begin, instructions on using the Add a Device Wizard, and guidance for resolving the troubleshooting messages you might encounter. Note: IBM SVC and IBM V700 are used interchangeably in this document. 172 Storage Manager

173 Before you begin An SMI-S provider is embedded in the Management Console of the array as illustrated in the diagram below. There is no need to install additional software. See the IBM SVC Provider section for additional information or contact IBM for IBM SVC Provider support. Before adding your IBM SVC array to Storage Manager, you must collect the information listed in the table below. 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. See the IBM SVC Provider troubleshooting section for information about the default username and password, or contact your array vendor for additional support. Adding the array Use the Add a Device Wizard to add your IBM SVC array to Storage Manager Troubleshooting with the Add a Device Wizard Troubleshooting with the Add a Device Wizard provides details and guidance about the error messages you might encounter. Manual configuration Use the manual configuration if you must specify parameters that are not available from the Add a Device Wizard.

174 In step 1 of the Add a Device Wizard,choose IBM SVC, V7000. From the Add a Device IBM SVC, V7000 window, click the Manual Configuration link. In the Create New Device for Agent: Storage Array window, provide the following information: Server IP Address: From the drop down menu, select the Storage Manager Proxy Agent you want to monitor your array. Device Display Name: Enter a meaningful name for your array. Storage Array Type: Set to Storage Virtualization IBM SVC. Active: Keep this box checked. Clearing this check box stops data collection for your array. Click Next. In the Configure Device window, provide the values for the following fields. Status: Select On. User Name: Enter the user name used to access the provider. Password: Enter the password used to access the provider. Provider IP Address: Enter the IP address of the provider. Identifier: Enter the array identifier (WWN of the array). Note: Other parameters are editable from this window. Make changes only if you are sure of a parameter value, otherwise leave the default value. Click Test to test the connectivity between the Storage Manager Proxy Agent and the array s SMI-S provider. You must enter the username, password, and provider IP before you can test the connection. Click Save to save the configuration and push it to the Storage Manager Proxy Agent to begin monitoring the array. Additional information IBM SVC, V7000 Versions/Models Features SVC Asset Storage 174 Storage Manager

175 Requires Storage No Manager Agent? Prerequisites IP Address of IBM SVC Latest IBM SMI-S Provider installed on a Windows/Linux server that has IP connectivity to SVC Credentials Account and password are stored in Storage Manager database and configuration files on Storage Manager Proxy Agent using custom encryption Read/Write Actions Read Only Ports Used Configurable: 5988 (HTTP) or 5989 (HTTPS) used by SMI-S provider Communication See the Storage Manager Ports section below. Can be HTTP/HTTPS between Storage Manager Proxy Agent and the IBM SMI-S provider. Requires a Storage Yes Windows or Linux Manager Proxy Agent? IBM XIV Find the information you need to add an IBM XIV array to Storage Manager. This section includes 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 The SMI-S provider for the IBM XIV array is embedded in the administrative modules of the array as illustrated in the diagram below. There is no need to install additional software. The provider is enabled and running by default in all administrative modules. Additional information is available in the IBM XIV Provider section. Or contact IBM for additional support. The IBM XIV must be version or higher. Before adding your IBM SVC array to Storage Manager, you must collect the information listed in the table below.

176 Provider IP address IP address of the SMI-S provider 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. Adding the array Use the Add a Device Wizard to add your IBM XIV array to Storage Manager Troubleshooting with the Add a Device Wizard Troubleshooting with the Add a Device Wizard provides details and guidance about the error messages you might encounter. Manual configuration Use the manual configuration if you must specify parameters that are not available from the Add a Device Wizard. In step 1 of the Add a Device Wizard,choose IBM XIV. From the Add a Device IBM XIV window, click the Manual Configuration link. In the Create New Device for Agent: Storage Array window, provide the following information: Server IP Address: From the drop down menu, select the Storage Manager Agent you want to monitor your array. Device Display Name: Enter a meaningful name for your array. Storage Array Type: Set to Storage Array IBM XIV. Active: Keep this box checked. Clearing this check box stops data collection for your array. Click Next. In the Configure Device window, provide the values for the following fields. Status: Select On. 176 Storage Manager

177 User Name: Enter the user name used to access the provider. Password: Enter the password used to access the provider. Provider IP Address: Enter the IP address of the provider. Identifier: Enter the array identifier (WWN of the IBM SVC array). Note: Other parameters are editable from this window. Make changes only if you are sure of a parameter value, otherwise leave the default value. Click Test to test the connectivity between the Storage Manager Proxy Agent and the array s SMI-S provider. You must enter the username, password, and provider IP before you can test the connection. Click Save to save the configuration and push it to the Storage Manager Proxy Agent to begin monitoring the array. NetApp E-Series LSI Find the information you need to add your NetApp E-Series LSI array to Storage Manager. 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. Note: NetApp acquired LSI and their arrays are now referred to as E-Series. If you are working with Eagle 5.0 or 5.1 providers and firmware at version or higher, you can claim E-Series support. NetApp E-Series LSI Arrays include: Dell MD3xxx IBM DS3xxx, DS4xxx, and DS5xxx Sun StorageTek x222, 6xxx, and FLX Series Before you begin An SMI-S Provider must be installed and configured before you can add your array to Storage Manager. Your array requires the installation of a separate SMI-S provider as illustrated in the diagram below.

178 See the Provider section for more details on downloading and installing this provider. Or contact your array vendor for additional SMI-S provider support. Before adding your NetApp E-Series LSI array to Storage Manager, you must collect the information listed in the table below. Provider IP address IP address of the SMI-S provider Provider Admin Username The Administrator Username of the SMI-S provider Provider Admin Password The Administrator password of the SMI-S provider Adding the array Use the Add a Device Wizard to add your NetApp E-Series LSI array to Storage Manager Troubleshooting with the Add a Device Wizard Troubleshooting with the Add a Device Wizard provides details and guidance about the error messages you might encounter. Manual configuration Use the manual configuration if you must specify parameters that are not available from the Add a Device Wizard. In step 1 of the Add a Device Wizard, choose LSI. From the Add a Device LSI window, click the Manual Configuration link. In the Create New Device for Agent: Storage Array window, provide the following information: 178 Storage Manager

179 Server IP Address: From the drop down menu, select the Storage Manager Proxy Agent you want to monitor your array. Device Display Name: Enter a meaningful name for your array. Storage Array Type: Set to Storage Array LSI. Active: Keep this box checked. Clearing this check box stops data collection for your array. Click Next. In the Configure Device window, provide the values for the following fields. Status: Select On. User Name: Enter the user name used to access the provider. Password: Enter the password used to access the provider. Provider IP Address: Enter the IP address of the provider. Storage Array WWN: Enter the array identifier (WWN of the NetApp E-Series LSI array). Note: Other parameters are editable from this window. Make changes only if you are sure of a parameter value, otherwise leave the default value. Click Test to test the connectivity between the Storage Manager Proxy Agent and the array s SMI-S provider. You must enter the username, password, and provider IP before you can test the connection. Click Save to save the configuration and push it to the Storage Manager Proxy Agent to begin monitoring the array. Additional information NetApp E-Series formerly LSI Versions/Models All Features Asset Storage Performance Disk Performance Requires Storage No Manager Agent? Prerequisites IP Address of Storage Processors

180 Latest LSI Engenio SMI-S Provider installed on a 32 bit Windows/Linux server that has IP connectivity to the storage processors Credentials Account and password are stored in Storage Manager database and configuration files on Storage Manager Proxy Agent using custom encryption Read/Write Actions Read Only 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 from SMI-S provider. Communication See the Storage Manager Ports section below. Can be HTTP/HTTPS between Storage Manager Requires Storage Manager Proxy Agent? NetApp Filer Proxy Agent and the LSI Engenio SMI-S provider. Yes Windows or Linux Add your NetApp filer so Storage Manager can query it directly. Find the information you need before you begin and steps for adding and configuring your NetApp filer. Review the NetApp Operations Manager section if you have many Filers to add to Storage Manager. Before you begin Ensure that a Storage Manager Proxy Agent is running on the server to be used to monitor your NetApp filer. One or more Storage Manager Proxy Agents for Windows/Unix/Linux must be used to perform File Analysis on a NetApp filer. Use Windows agents to perform analysis on CIFS shares and Unix/Linux agents to perform analysis on NFS mounts. NetApp filer IP address. NetApp filer login credentials, typically root or equivalent. The selected Storage Manager Proxy Agent is in the list of the filer's trusted hosts. Windows Security Context: Please ensure that the Storage Manager Proxy Agent service is running with the "Log On" rights of a Domain Account that has read access on the shares assigned to it via the 'Assign Shares' page. Note: Operations Manager and DFM are used synonymously in Storage Manager. 180 Storage Manager

181 Adding NetApp filer When adding a device, choose NetApp filer from the Choose your Array Type menu. Click OK. Select Agent: Select a Storage Manager Proxy Agent to monitor the device. NetApp IP Address: Enter the NetApp filer IP address obtained in Before you begin. Device Display Name: Enter a descriptive name to identify the device. Active: Uncheck this box if you want to stop collecting data for the device. Cost Per GB: Optional - Enter the cost per gigabyte. 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. Status: Select On.

182 User Name: Enter the User Name obtained in Before you begin. Password: Enter the Password obtained in Before you begin. Transport Type: Choose HTTP or HTTPS. Use Operations Manager: This field is set to False by default. When the flag is set to True, and a valid DFM Server IP Address is provided, Storage Manager requests data from the NetApp Operations Manager. If the value is set to false, Storage Manager queries the NetApp filer directly. Note: DFM Server and Operations Manager are used synonymously in Storage Manager. DFM Server IP Address: If you enter True for Use Operations Manager, enter the Operations Manager (DFM) IP address. Advanced Fields: The Operations Manager Port and Data Window Size are advanced configuration fields. Click Save to save the configuration and push it to the Storage Manager Proxy Agent to begin monitoring the array. Additional information NetApp Versions/Models Features Requires Storage Manager Agent? All Asset Storage Performance No Prerequisites IP Address of NetApp head/cluster node Define user account on NetApp. Minimum access - a role with access to execute specific API calls. List available upon request. Usually provided just the root login Add the Storage Manager Proxy Agent to list of trusted hosts on the NetApp storage system 182 Storage Manager

183 ONTAP 7.3.x: Turn off API XML validation on each NetApp filer (FAQ-132) For ONTAP 8.1 o o 7 Mode is required Clustered Mode is not supported Credentials Read/Write Actions Account and password are stored in Storage Manager database and configuration files on Storage Manager Proxy Agent using custom encryption Read Only Ports Used 80 (HTTP)/443 (HTTPS) on NetApp head/cluster node Any available for CIFS/NFS Communication See the Storage Manager Ports section. Data Classification Can be HTTP/HTTPS between Storage Manager Proxy Agent and the NetApp head/cluster node CIFS Shares require a Storage Manager Windows Agent and domain account to access the shares being analyzed NFS Shares require a Storage Manager Linux Agent and root access to shares being analyzed. Occurs via Storage Manager Proxy Agent Requires Storage Manager Proxy Agent? Yes Windows or Linux NetApp Operations Manager If you have many NetApp filers in your environment, using NetApp Operations Manager can be a convenient way to add the Filers to Storage Manager. Operations Manager can discover NetApp filers and collect data on the Filers it manages.

184 After the NetApp filers are added, you can easily configure Storage Manager to query the NetApp filers directly through the All Devices page or through the NetApp filer Policy Configuration page. See Configuring NetApp 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 Storage Manager. Step 2: Selecting which NetApp filers to monitor and assign them to a Storage Manager Proxy Agent for data collection. Note: Discovery can take a few minutes in large environments. Note: Operations Manager and DFM Server are used synonymously in Storage Manager. Before you begin Obtain the following information before you begin adding NetApp Operations Manager to Storage Manager. DFM Server IP address DFM Server User Name and Password with GlobalFullControl privileges Ensure that the NetApp filers are accessible to DFM Server via http or https Adding NetApp Operations Manager 1. When adding a device, choose NetApp Operations Manager from the Choose your Array Type menu. Click OK. 2. Fill in the fields In the Create New Device for Agent: NetApp Operations Manager window. 3. Select Agent: Select a Storage Manager 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 that you obtained in the Before you begin section. 6. Click Next>. 184 Storage Manager

185 Configuring NetApp Operations Manager Provide the appropriate information about the array you want to monitor. If you are unsure about a value, do not change the default value. Status: Select On User Name: Enter the DFM User Name obtained in Before you begin. Password: Enter the DFM Password obtained in Before you begin. Transport Type: Choose HTTP or HTTPS. Discovery Frequency: Choose the discovery frequency. Advanced Fields: The Operations Manager Port and Data Window Size are advanced configuration fields. Click Save to save the configuration and push it to the Storage Manager Proxy Agent to begin monitoring the array. Assigning NetApp filers To Assign NetApp filers to the Storage Manager Proxy Agent, go to Settings -> NetApp Operations Manager -> Assign NetApp Filers page. Select the DFM Server Select the NetApp filers from "Available" box. You can select more than one by holding the Control Key while making your selections. Select the Storage Manager Proxy Agent. Click on the down arrow; this will move the NetApp filers down to the "Selected" box. Click the SAVE button. When you save the change, a push will be scheduled immediately to update the Storage Manager Proxy Agent(s) with the changes. Removing NetApp filers Select the NetApp filers from the "Selected" box. You can select more than one by holding the Control Key while making your selections. Click on the up arrow; this will move the NetApp filers up to the "Available" box. Click the SAVE button. When you save the change, a push will be scheduled immediately to update the Storage Manager Proxy Agent(s) with the changes.

186 Additional information NetApp Versions/Models Features Requires Storage Manager Agent? All Asset Storage Performance No Prerequisites IP Address of NetApp head/cluster node Define user account on NetApp. Minimum access - a role with access to execute specific API calls. List available upon request. Usually provided just the root login Add Storage Manager Proxy Agent to list of trusted hosts on the NetApp storage system ONTAP 7.3.x: Turn off API XML validation on each NetApp filer (FAQ-132) For ONTAP 8.1 o o 7 Mode is required Clustered Mode is not supported Credentials Read/Write Actions Account and password are stored in Storage Manager database and configuration files on Storage Manager Proxy Agent using custom encryption Read Only Ports Used 80 (HTTP)/443 (HTTPS) on NetApp head/cluster node Any available for CIFS/NFS Communication See the Storage Manager Ports section. 186 Storage Manager

187 Data Classification Can be HTTP/HTTPS between Storage Manager and the NetApp head/cluster node CIFS Shares require a Storage Manager Windows Agent and domain account to access the shares being analyzed NFS Shares require a Storage Manager UNIX Agent and root access to shares being analyzed. Occurs via Storage Manager Proxy Agent Requires Storage Manager Proxy Agent? Yes Windows or Linux ONStor Find details about adding an ONStor array to Storage Manager. This section includes what you need before you 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 Storage Manager. Contact your array vendor for additional support on installing and troubleshooting your array. You will need the IP address of the array you want to monitor. Contact your array administrator or refer to your array documentation for assistance obtaining this IP address. Adding 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. Select Agent: Select the Storage Manager Proxy Agent for this device. Windows Device List: Select a Windows server to retrieve the CIFS shares exposed by the NAS device. Unix Device List: Select a Unix or Linux server to retrieve the NFS shares exposed by the NAS device. IP Address: Enter the IP address of the device to be monitored.

188 Device Display Name: Enter the display name for this resource. Active: Keep this box checked box. Clearing this check box stops data collection for your array Click Next>. Configuring the array Status: Select On. SNMP Community String: Enter the community string of the Array (default is public). In the Configure Device window, click Test to confirm the default values are working. Click the Show Advanced Fields to customize your array configuration. Click Test to test SNMP communication between the Storage Manager Proxy Agent and the ONStor device. Note: You must select a Storage Manager Proxy Agent, enter an SNMP community string, and enter a device IP address before you click Test. When the Test Results show Successfully connected, save your configuration. Pillar Find details on how to add your Pillar array to Storage Manager. 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 The SMI-S Provider is embedded in the Pillar array as illustrated in the diagram below. No installation is required The SMI Provider is enabled by default on systems with 2 GB Pilots. 188 Storage Manager

189 Upgrades for the Pillar SMI-S Provider are bundled with system software upgrades. 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. If you want to use the SMI-S provider, upgrade to the 2 GB versions. See the Pillar Provider section for additional information or contact your Pillar vendor for SMI-S provider support. Before adding your Pillar array, collect the information in the table below. Provider IP address IP address of the SMI-S provider Provider Admin Username The Administrator Username of the Pillar provider Provider Admin Password The Administrator password of the Pillar provider Adding the array Use the Add a Device Wizard to add your Pillar array to Storage Manager Troubleshooting with the Add a Device Wizard Troubleshooting with the Add a Device Wizard provides details and guidance about the error messages you might encounter. Manual configuration Use the manual configuration if you must specify parameters that are not available from the Add a Device Wizard. In step 1 of the Add a Device Wizard, choose Pillar. From the Add a Device Pillar window, click the Manual Configuration link. In the Create New Device for Agent: Storage Array window, provide the following information: Server IP Address: From the drop down menu, select the Storage Manager Proxy Agent you want to monitor your array.

190 Device Display Name: Enter a meaningful name for your array. Storage Array Type: Set to Storage Array Pillar. Active: Keep this box checked. Clearing this check box stops data collection for your array. Click Next. In the Configure Device window, provide the values for the following fields. Status: Select On. User Name : Enter the user name used to access the Pillar provider Password: Enter the password used to access the Pillar provider. Provider IP Address: Enter the IP address of the Pillar provider. Identifier: Enter the array identifier (the WWN of the Pillar array). Note: Other parameters are editable from this window. Make changes only if you are sure of a parameter value, otherwise leave the default value. Click Test to test the connectivity between the Storage Manager Proxy Agent and the array s SMI-S provider. You must enter the username, password, and provider IP before you can test the connection. Click Save to save the configuration and push it to the Storage Manager Proxy Agent to begin monitoring the array. Sun StorageTek 2xxx, 6xxx, and FLX Series Find the information you need to add your Sun StorageTek 2xxx or 6xxx Series array to Storage Manager. 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 An SMI-S Provider must be installed and configured before you can add your Sun/StorageTek 2xxx or 6xxx Series array to Storage Manager. The SMI-S Provider is a separate installation as illustrated in the diagram below. 190 Storage Manager

191 See the Provider section for more details on downloading and installing this provider. Contact your Sun StorageTek vendor for additional SMI-S provider support. Before adding your Sun/StorageTek 2xxx or 6xxx Series array to Storage Manager, you must collect the information listed in the table below. Provider IP address IP address of the SMI-S provider 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. Adding the array Use the Add a Device Wizard to add your array to Storage Manager Troubleshooting with the Add a Device Wizard Troubleshooting with the Add a Device Wizard provides details and guidance about the error messages you might encounter. Manual configuration Use the manual configuration if you must specify parameters that are not available from the Add a Device Wizard. In step 1 of the Add a Device Wizard,choose Sun Storage Tek 2xxx, 6xxx Series or Sun Storage Tek FLX Series. From the Add a Device Sun Storage Tek window, click the Manual Configuration link. In the Create New Device for Agent: Storage Array window, provide the following information:

192 Server IP Address: From the drop down menu, select the Storage Manager Proxy Agent you want to monitor your array. Device Display Name: Enter a meaningful name for your array. Storage Array Type: Set to Sun Storage Tek 2xxx, 6xxx Series or Sun Storage Tek FLX Series. Active: Keep this box checked. Clearing this check box stops data collection for your array. Click Next. In the Configure Device window, provide the values for the following fields. Status: Select On. User Name: Enter the user name used to access the provider. Password: Enter the password used to access the provider. Provider IP Address: Enter the IP address of the provider. Storage Array WWN: Enter the array identifier (WWN of the array). Note: Other parameters are editable from this window. Make changes only if you are sure of a parameter value, otherwise leave the default value. Click Test to test the connectivity between the Storage Manager Proxy Agent and the array s SMI-S provider. You must enter the username, password, and provider IP before you can test the connection. Click Save to save the configuration and push it to the Storage Manager Proxy Agent to begin monitoring the array. Additional information SUN/StorageTek Versions/Models All Features Asset Storage Performance Disk Performance Requires Storage No Manager Agent? Prerequisites IP Address of Storage Processors 192 Storage Manager

193 Latest LSI Engenio SMI-S Provider installed on a 32 bit Windows/Linux server that has IP connectivity to the storage processors Credentials Account and password are stored in Storage Manager database and configuration files on Storage Manager Proxy Agent using custom encryption Read/Write Actions Read Only 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 from SMI-S provider. Communication See the Storage Manager Ports section below. Can be HTTP/HTTPS between Storage Manager Requires Storage Manager Proxy Agent? Sun StorageTek 99xx Series Proxy Agent and the LSI Engenio SMI-S provider. Yes Windows or Linux Find details on how to add your Sun StorageTek 99xx Series array to Storage Manager. 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 An SMI-S Provider must be installed and configured before you can add your Sun StorageTek 99xx Series array to Storage Manager. The HDS provider is part of the HiCommand Device Manager as illustrated in the diagram below. See the Hitachi Data Systems (HDS) Provider section for details on installing the HDS provider in the HiCommand Device Manager. Or contact your Sun StorageTek 99xx vendor for additional SMI-S provider support. Before adding your Sun StorageTek 99xx Series array to Storage Manager, you must collect the information listed in the table below.

194 Provider IP address The IP address of the HiCommand Device manager. Provider Admin Username Provider Admin Password The Administrator Username set up when adding a subsystem to the HiCommand Device Manager The Administrator Password set when adding a subsystem to the HiCommand Device Manager See, How do I Add a Subsystem?, for more information about adding subsystems to the HiCommand Device Manager. Or contact your StorageTek 99xx vendor for additional HiCommand support. Adding the array Use the Add a Device Wizard to add your array to Storage Manager Troubleshooting with the Add a Device Wizard Troubleshooting with the Add a Device Wizard provides details and guidance about the error messages you might encounter. Manual configuration Use the manual configuration if you must specify parameters that are not available from the Add a Device Wizard. In step 1 of the Add a Device Wizard,choose Sun Storage Tek 99xxSeries. From the Add a Device Sun Storage Tek 99xxSeries window, click the Manual Configuration link. In the Create New Device for Agent: Storage Array window, provide the following information: Server IP Address: From the drop down menu, select the Storage Manager Proxy Agent you want to monitor your array. Device Display Name: Enter a meaningful name for your array. Storage Array Type: Set to Storage Array HDS. Active: Keep this box checked. Clearing this check box stops data collection for your array. Click Next. 194 Storage Manager

195 In the Configure Device window, provide the values for the following fields. Status: Select On. User Name: Enter the user name used to access the provider. Typically this is the username used to access the HiCommand Device Manager. Password: Enter the password used to access the provider. Typically this is the password used to access the HiCommand Device Manager. Provider IP Address: Enter the IP address of the HiCommand Device Manager. Serial No: Enter the serial number of the array. Note: Other parameters are editable from this window. Make changes only if you are sure of a parameter value, otherwise leave the default value. Click Test to test the connectivity between the Storage Manager Proxy Agent and the array s SMI-S provider. You must enter the username, password, and provider IP before you can test the connection. Click Save to save the configuration and push it to the Storage Manager Proxy Agent to begin monitoring the array. Xiotech Emprise 7000 Find details about adding a Xiotech Emprise 7000 array to Storage Manager. This section includes what you need before you 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 Storage Manager. Contact your array vendor for additional support on installing and troubleshooting your array. You will need to obtain the following information. o o o o The Serial Number for the Xiotech device you want to monitor. The IP address of the XWS that manages the array. The Client / User Name used to log into the ICON. By default, this is set to Administrator. The ICON password for the Client / User Name.

196 Refer to your array administrator or your array documentation for assistance obtaining this information. Adding the array When adding a device, choose Xiotech Emprise 7000 from the Choose your Array Type menu. Click OK. Complete the fields in the Create New Device for Agent: Emprise 7000 window. Select Agent: Select a Storage Manager Proxy Agent for this device. Serial Number: Add the Serial number you obtained in the Before you begin section. Device Display Name: Enter the display name for this resource. Click Next>. Configuring the array From the Configure Device window, enter the information you collected in the Before you begin section. Poll Status: Select On. XWS IP Address: The IP address of the XWS that manages the array. Client /User Name: The client / User Name used to log into the ICON. By default, this is set to Administrator. Password: The password for the ICON server. ICON: Select the ICON managing the Magnitude. The default values can be used for the remaining configuration fields. Or you can click the Show Advanced Fields and enter your custom configuration values. Click Save. Xiotech Magnitude 3D 3xxx Find details about adding a Xiotech Magnitude 3D 3xxx array to Storage Manager. This section includes what you need before you begin, details about adding your array, and guidance for configuring your array. 196 Storage Manager

197 Before you begin Your array must be installed and running before it can be added to Storage Manager. Contact your array vendor for additional support on installing and troubleshooting your array. You will need to obtain the following information. o o o o The Serial Number for the Xiotech device you want to monitor. The IP address of the XWS that manages the array. The Client / User Name used to log into the ICON. By default, this is set to Administrator. The ICON password for the Client / User Name. Contact your array administrator or refer to your array documentation for assistance obtaining this information. Adding the array When adding a device, choose Xiotech Magnitude 3D 3xxx from the Choose your Array Type menu. Click OK. Select Agent: Select a Storage Manager Proxy Agent for this device. Serial Number: Add the Serial number you obtained in the Before you begin section. Device Display Name: Enter the display name for this resource. Click Next>. Configuring the array From the Configure Device window, enter the information you collected in the Before you begin section. Poll Status: Select On. XWS IP Address: The IP address of the XWS that manages the array. Client /User Name: The client / User Name used to log into the ICON. By default, this is set to Administrator. Password: The password for the ICON server. ICON: Select the ICON managing the Magnitude.

198 The default values can be used for the remaining configuration fields. Or you can click the Show Advanced Fields and enter your custom configuration values. Click Save. Xiotech Magnitude 3D 4000 Find details about adding a Xiotech Magnitude 3D 4000 array to Storage Manager. This section includes what you need before you 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 Storage Manager. Contact your array vendor for additional support on installing and troubleshooting your array. You will need to obtain the following information. o o o o The Serial Number for the Xiotech device you want to monitor. The IP address of the XWS that manages the array. The Client / User Name used to log into the ICON. By default, this is set to Administrator. The ICON password for the Client / User Name. Contact your array administrator or refer to your array documentation for assistance obtaining this information. Adding the array When adding a device, choose Xiotech Magnitude 3D 4000 from the Choose your Array Type menu. Click OK. Complete the fields in the Create New Device for Agent: Magnitude 3D 4000 window. Select Agent: Select a Storage Manager Proxy Agent for this device. Serial Number: Add the Serial number you obtained in the Before you begin section. Device Display Name: Enter the display name for this resource. Click Next>. 198 Storage Manager

199 Configuring the array From the Configure Device window, enter the information you collected in the Before you begin section. Poll Status: Select On. XWS IP Address: The IP address of the XWS that manages the array. Client /User Name: The client / User Name used to log into the ICON. By default, this is set to Administrator. Password: The password for the ICON server. ICON: Select the ICON managing the Magnitude. The default values can be used for the remaining configuration fields. Or you can click the Show Advanced Fields and enter your custom configuration values. Click Save. Adding Fibre Channel Devices The following section details how to add Fibre Channel Switches to Storage Manager. To add and configure a FibreChannel switch for vendors like Brocade, Cisco, McDATA,and Qlogic, obtain the required information before you begin, ensure you meet the requirements, and follow the example in the Configuring a McData Fibre Channel Switch Device section.. Fibre Channel Switches Requirements Configuring a McData Fibre Channel Switch Device Fibre Channel Switches Requirements The following items are required before you begin: Switch IP Address. This IP must be accessible via telnet from the selected Storage Manager Proxy Agent to collect Zoning information from Brocade Switches An SNMP v1 read-only community string Cisco MDS Switches Brocade, McData, and QLogic Switches

200 Cisco MDS Versions/Models Any Features Asset Storage Performance Topology (Tabular) Requires Storage No Manager Agent? Prerequisites Create SNMP version 1 community string from command line If there is an access list for SNMP on the switch, include the Storage Manager Proxy Agent(s) s IP address to the list Credentials SNMP community string for each FC Switch Read/Write Read Only Actions Ports Used 161 UDP on the switch Communication See the Storage Manager Ports section below Requires Storage Manager Proxy Agent? Yes Window or Linux Topology requires Windows agent on SAN attached host to any switch in the fabric Brocade, McData, and QLogic Switches Versions/Models Any Features Asset Storage Performance Topology (Tabular) Zoning Requires Storage No Manager Agent? Prerequisites Enable FA-MIB on switches (on Brocade, command to run is snmpmibcapset) If there is an access list for SNMP on the switch, include The Storage Manager Proxy Agents(s)'s IP address to the list Credentials SNMP community string for each FC Switch Zoning (v4.8+): Login and Password (telnet) for each FC Switch Read/Write Read Only Actions Ports Used 161 UDP on the switch 200 Storage Manager

201 Communication Requires Storage Manager Proxy Agent? See the Storage Manager Ports section below Yes Windows or Linux Topology requires Windows agent on SAN attached host to any switch in the fabric Community String SNMP V1 needs to be enabled to collect data from a CISCO switch. If the community string is defined from any CISCO Device/Fabric Manager, then it's implicitly set for SNMP V3. The community string MUST be defined from the command line. Storage Manager can monitor any switch (or device) that supports the Fibre Alliance MIB. Some switches (for example, McDATA) use an alternate MIB, called the Fibre Channel Management MIB, which provides the same information. For those switches using this MIB, you must check the McDATA box when creating the device. If you are unsure, create the device without checking the box first. If you do not see data after minutes, try checking the box and see if data begins to be collected. Note: To set up Brocade switches, one has to execute the following commands to change the SNMP configuration: To enable FA MIB: snmpconfig --set snmpv1 For access control: snmpconfig --set accesscontrol To check: snmpconfig: snmpconfig --show Configuring a McData Fibre Channel Switch Device 1. On the new device page enter the appropriate values. Select Agent: Select the Storage Manager Proxy Agent you want to monitor the Fibre Channel Switch IP Address: Type the IP address of the switch Device Display Name: Type a descriptive name for the Fibre Channel (ex: FC NY1) Active: Do not clear this check box, doing so will stop information collection from the Fibre Channel McDATA Switch: Check this if the device uses the FIBRE-CHANNEL- MGMT MIB rather than the standard Fibre Alliance MIB (for example, McDATA switches use this MIB).

202 Note: McData i10k series switches do not require the McData checkbox to be enabled. For more information see this KB article. Device Groups: Optional - if you have configured groups, you can add this Fibre Channel Switch to them by clicking the group name Zoning: Check this box and provide credentials, which will generate the Zoning reports. Note: Zoning option is supported via a Windows Agent only. 2. Click Next> to continue to the next configuration screen. 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 On b. SNMP Community String: An SNMP v1 read-only community string 4. Click Save to save the configuration and push it out to the Storage Manager Proxy Agent to begin monitoring the Fibre Channel. Note: Click Test to test SNMP communication between the Storage Manager Proxy Agent and the Fibre Channel Switch device. You must select a Storage Manager Proxy Agent; enter a SNMP community string and device IP address, before you press this button. 202 Storage Manager

203 Adding VMware Monitoring Storage Manager Proxy Agents can monitor the VMware infrastructure remotely (VC, ESX and VM). Installed agents will discover the ESX Servers connected to virtual center. Select from the following topics: VMware Requirements Adding VMware Storage Manager and vcenter Asset Collection VMware Device Requirements Note: For Storage Manager to reliably collect data from VMs, it is recommended not to exceed 300 VMs per 64 bit Storage Manager Proxy Agents and 200 VMs per 32 bit Storage Manager Proxy Agents. To accommodate failover situations, allow a margin of safety when calculating your VM per Storage Manager Proxy Agent limits. If you are monitoring a cluster with more than 300 VMs, consider assigning Storage Manager Proxy Agents to monitor specific hosts. VMware Versions/Models 4.0, 4.0i, 4.1, 4.1i, 5.0, 5.1, 5.5 Features Asset - (VC, Cluster, ESX, and VM levels) Storage - (VC, Cluster, ESX, and VM levels) Performance - (VC, Cluster, ESX, and VM levels) Capacity Planning Requires Storage No Manager Agent? Prerequisites Create user on Virtual Center with a role containing the following privileges Datastore.browse Global.Licenses System.view System.Anonymous System.Read Credentials Run as root user on Unix/Linux Local System account/domain Account (Windows) Account and password are stored in Storage Manager database and configuration files on Storage Manager Proxy Agent using custom encryption

204 Read/Write Read Only Actions Ports Used Virtual Center: HTTPS Port 443 Storage Manager Agent Ports Requires Storage Yes Windows or Linux Manager Proxy Agent? Storage Manager Proxy Agent must not be installed on the Virtual Center server Adding VMware Configuring Storage Manager to monitor your virtual infrastructure is a two step process. First step, Storage Manager must connect to the VC instance and discover all the ESX hosts it is managing. Second step, you must select which ESX hosts to monitor. Discovery can take a few minutes in large environments. NOTE: For Storage Manager to reliably collect data from VMs, it is recommended to not exceed 300 VMs per 64 bit Storage Manager Proxy Agents and 200 VMs per 32 bit Storage Manager Proxy Agents. To accommodate failover situations, allow a margin of safety when calculating your VM per Storage Manager Proxy Agent limits. If you are monitoring a cluster with more than 300 VMs, consider assigning agents to monitor specific hosts. Requirements: The following items are required before you begin: A Storage Manager Proxy Agent located on the same network as the VC instance Login credentials to the VC Instance. Step 1: Configuring a VMware VC Instance To begin follow the instructions below.. 1. Click Settings > Getting Started>Virtualization> Add More, and provide the appropriate values for the following fields: 204 Storage Manager

205 Select Agent: Select the Storage Manager Proxy Agent you want to collector data. Device Display Name: Type a descriptive name for the VMware VC Instance (ex: VMwareVC NY) 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. Status: Select ON UserName: Virtual Centre login [Do not include Windows domain even if this is a domain account] Password: Virtual Centre password Collect Orphaned VMDK: Select Yes unless you do not need reports on orphan VMDK Files Collect Device Pools: Select Yes 4. Click Save to save the configuration and push it out to the poller to begin monitoring the VC instance. Note: You can also configure a VMware VC Instance at any time from the Devices page (Settings > All Devices). Step 2: Assigning VMware ESX Hosts Once Storage Manager 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 problem with vcenter. Verify your credentials and try again or contact SolarWinds for support. You can always test the authentication yourself from this machine by manually connecting to the vcenter using a web browser: IP Address>/ui 1. On the Assign ESX Hosts page:

206 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 will push the configuration out the selected poller(s) and begin data collection. A VMware VC Instance will now appear in the Storage Manager Devices list. Wait for about minutes after completion 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 on 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 to the Available list b. Click Save. A push will be scheduled immediately to update the Storage Manager Proxy Agent(s) with the changes. Clusters can also be assigned in the same manner by selecting 'Cluster' instead of ESX in the ESX Host Assignment page If after selecting the Assign by 'Cluster' option, the user clicks on the Save button without actually making any changes, then the ESX hosts which are assigned to a different poller will be re-assigned under the cluster 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 been installed and registered with the Storage Manager Server. VMware vcenter can discover the ESX Servers connected to Virtual Center. Important Note: To create a VMware vcenter, make sure that a Storage Manager Proxy Agent is running on the IP Address you want to use to gather data from. 206 Storage Manager

207 Storage Manager and vcenter Asset Collection Customers with very large virtual environments might encounter an issue where asset data is not being reported for virtual devices. This issue can be caused by timeout issues due to an influx of too much data to Storage Manager. Storage Manager versions 6.0 and above have resolved this issue by adding a feature allowing customers to throttle the amount of data being polled by STM. The new feature can be seen when clicking the "Show Advanced Fields" button in the device configuration window for the virtual device. The fields are: Number of Connection to VC for Asset Number of connection to VC for Storage 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 modify the time for when Configuration, Performance, Storage and Discovery Frequency is collected thus avoiding any scheduled overlap with data collection from the virtual device.

208 When customers set the values and click the "Save" button, the changes are automatically cascaded to any additional proxy agents that are monitoring ESX servers associated with the vcenter, thus saving the customer time from having to manually duplicate the settings for each proxy agent. Virtualization Dashboard The Storage Manager Virtualization Dashboard provides quick views into your current virtualized environment including: Asset Summary (including Clusters) Capacity Analysis Storage by type Data stores VMDK Utilization 208 Storage Manager

209 VMs by last boot time Storage Utilization by VM VMware snapshots Overall performance of each device- CPU, Memory, Disk Discover VM Targets This feature allows you to assign one or more VM(s) for Storage Manager to discover shares/file systems on. Select the VMs from the available section to be moved to the selected box and click Discover Now. Note: Works with Windows Guest OS Only P2V Simulator P2V (physical to virtual) is the migration of operating systems and their associated applications from physical, dedicated hardware into virtualized environments. The P2V migration can be handled through specialized 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 below example.

210 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 to multiple servers easily and allows distributed storage systems to be deployed as needed provisioning. The Virtualization Dashboard provides a graphical display of your datastore Thin Provisioning. Displays thin 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: Used Space is the actual amount of space used. Free is the physical amount of storage still available. Overcommitted is how much storage is committed above the physical storage available. Thin provisioning percent is the percentage of over commitment above the physical storage. 210 Storage Manager

211 SnapMirror Monitor The SnapMirror Monitor shows the current transfer between the source and the destination for all the filers in the group or a particular filer based on the filter selection. Filtering the view: Groups - All Groups assigned to the logged in user with NetApp or IBM N Series Filers devices will be displayed Source Filer - Filers in all the Groups will be displayed. On selection of a particular group, source filer drop down box will be loaded with filers in that groups Status - Displays the possible statuses that can happen during snap mirror transfer, user can filter based on the selected status by selecting the desired status and clicking on 'GO' button Sorting the view: Groups - All Groups assigned to the logged in user with NetApp or IBM N Series Filers devices will be displayed Source Filer - Filers in all the Groups will be displayed. On selection of a particular group, source filer drop down box will be loaded with filers in that groups Status - Displays the possible statuses that can happen during snap mirror transfer, user can filter based on the selected status by selecting the desired status and clicking on 'GO' button Setting Up File Analysis The following section describes how to setup file analysis and is based on the scenario of determining who has files, what kind of files and how old the files are. This will allow you to: Obtain size and details on each share Used for quota enforcement Compliance reporting Storage recovery You can also group shares into logical collections for chargeback. STM 211

212 Requirements First, we need a list of shares from the device. For NetApp, this is done automatically through the API. For Celerra, Virtual Machines, and other NAS devices, you assign this work to an agent. An agent that is assigned the work must be able to access the share. For Windows, this means changing the Service Account to a domain user that has access to those CIFS shares. For Unix/Linux, it means the root user should have access to the NFS shares. All CIFS scanning is done by agents on Windows servers, and all NFS scanning by agents on Unix/Linux servers. You must enable File Analysis on the agent doing the work. Note: 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 permission to see all the files you wish to perform File Analysis against. We will cover the following in this section: Assigning Remote Shares Assigning Local Shares Enabling File Analysis Summary for configuring File Analysis Assigning Remote Shares The following example shows how to assign remote shares to a NetApp device. 1. Go to Settings > Assign Remote Shares. See the following screen shot. 2. Assign By: NAS or VM - lets you choose if you want to see NAS devices or Virtual Machines [NAS/VM] Device: Select one device or all devices. 212 STM

213 Share Type: CIFS or NFS. This will automatically change available agent to match the protocol. 3. Once 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. STM 213

214 Select the shares you want. You can select multiple shares by using the CTRL or SHIFT key. Device: select which agent you want to do the work Share Depth: Used to move the start point of file analysis further down the share. Storage Manager will treat each folder at that level as its own root directory. Note: Increasing Share Depth will increase the amount of work File Analysis must do. It should only be set greater than 0 if required. Using the default Share Depth of 0 will still gather data on all files in all sub folders. Move: Press the down arrow to assign the share, up arrow to unassign shares. 5. Once you have assigned the shares to the agents you want, press Save at the bottom. This will immediately assign out the shares to that agent, and file analysis will be performed at the next scheduled file analysis start time for that agent. If you want to change the start time, click on the Device Configuration icon for the agent doing the scanning and under File Analysis you will see the option to change the start time. Assign Local Shares We can also perform File Analysis on local shares. The process is pretty much automatic when enabling File Analysis on the agent. In the screen shot below we can see the server has a local c:\ drive. When File Analysis 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. 214 STM

215 Enabling File Analysis To turn on file analysis for a specific server: 1. Go to the Devices page (Settings> Devices) and click the Device Configuration icon for the server you 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. Summary for configuring File Analysis The agent which is monitoring the shares should have proper privileges to access shares. When enabling File Analysis for that agent, you should see the shares under the Assign Remote Shares page in Storage Manager. STM 215

216 Select those shares accordingly and assign to the respective agent When File Analysis run next time for that agent, it will do the scan the shares and on the device console, 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 File Analysis scan. For more information on building File Analysis rules see FA Rules. For more information on File Analysis see the following Thwack post: STM

217 Chapter 9 Using Reports and Schedules Storage Manager supports a versatile reporting tool that provides summary, inventory and historical information about network performance, storage and devices. The reports provide information about servers, databases, backup operations, NAS and SAN devices. Storage Manager provides two levels of reports and an Enterprise Report.: Administrator Reports User Reports Enterprise Report For details on running reports see Manage Reports. Administrator Reports Storage Manager is configured with two report options available to administrators and those users with specific permissions only. These options provide instantaneous access to assets, operating systems, storage, and backup statistics across the entire network. When an administrator logs in to Storage Manager, two additional selections are available under the Reports menu option. Management Reports: Provides a quick high-level summary of the current network assets, storage and backup. Enterprise Storage Reports: Present high-level summary views of network performance, while allowing the administrator to drill down to see underlying data. 1. Click the Reports folders to expand the report options. The Storage Manager user report options are listed below. My Reports - Reports you have created Shared Reports - Reports other users have created and shared with you Quick Reports - Predefined reports STM 217

218 Storage Manager uses a consistent format to display and manage reports regardless of which option is selected. Select an option and a table appears listing the reports available under that option. If no reports are available an error message is displayed. Within each section, managing reports works the same. You create, run, schedule, modify and delete reports the same way. Note: You cannot modify or delete quick reports. User Reports Storage Manager allows each user to run preformatted and user-defined reports. Both types of reports may be scheduled to run periodically at specific times. The Reports menu selection has several options: My Reports: This option is for building user-defined reports. These reports will always be accessible to the individual user or the administrator. The user has the option to set the permission level of a report so that the report can be shared with other users. Shared Reports: Reports created by any user in My Reports may be shared with other users in the same 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. Quick Reports: This is a selection of reports preformatted by Storage Manager. These reports cover a broad spectrum of file, device, and network parameters. Parameters include: disk usage, disk performance, disk and file system inventory, CPU/Memory performance statistics, network statistics and virtual memory performance statistics. Ability to "Star" a report as favorite, is added to 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. Enterprise Storage Reports Enterprise Reports present high-level summary views of network performance, while allowing the administrator to drill down to see underlying data. The administrator can look across the enterprise and see a summary view of how much storage space each 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 storage tier, business unit, data center, location, or other logical group using flexible grouping of volumes, qtrees, LUNs, and directories. 218 STM

219 Managing Reports The following steps detail how to run, schedule, create or modify a report. Running a Report Scheduling a Report Creating a New Report Deleting a Report Example Report To Begin: 1. Click the Reports 2. Select My Reports, Shared Reports or Quick Reports. Running a Report The Action column contains icons indicating the action the user has permission to perform. Possible Action selections include: Selecting the My Reports option will allow the user to Edit, Delete, Schedule and Run any reports created by that user. A user may also Schedule or Run any report available when the Shared Reports or Quick Reports options are selected. (Note: Administrators always have full access to user-defined reports.) Reports listed under the Quick Reports option are preformatted by Storage Manager and cannot be edited or deleted by users or administrators. To take an action, click the icon next to the report you want to run, schedule, modify or delete. To run a report, simply click the arrow. A Run Report screen will appear with multiple drop-down menus for selecting the scope and output format. Note: You can only see devices that are in the same groups as you. The Groups drop-down is limited to the groups that you are a member of, and the Devices drop-down is limited to the devices within those groups. Scheduling a Report Use the Report Scheduler to schedule a report: STM 219

220 1. Click the Schedule icon in the Report List. 2. This action will show a list of available schedules and the reports assigned to each schedule. You can also 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 you to the Create Schedule page. 4. To assign this report to an existing schedule, click the Add icon for that schedule. This brings up the Create 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: Frequency: Daily, Weekly (pick one or more days), or Monthly (choose the 1st, 15th or the Last Day of the Month) Time To Run: The time at which to execute the Report Recipients: Select the users who will be notified when this report is run. The users listed are Storage Manager users. You can add external addresses as well. Reports: Scheduled Reports assigned to this Schedule Publish: How you want to publish the report when it is executed. Report - send the report in an to all recipients Publish Report (Overwrite) - outputs to the same file name every time report is executed Publish Report (Do Not Overwrite) - outputs to a file name plus a time stamp each time the report is executed Choose whether all reports should be sent in one , or broken up into individual s. Name: The name of the schedule Note: 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 to which the reports are to be redirected to. You must provide an address to publish to a share. 220 STM

221 Report Schedule List Clicking on the Report Schedules icon under the Reports folder in the Tree Menu brings up the Report Schedules List page. Here you can see a list of all schedules, what reports are assigned to each schedule, the schedule frequency and the next run time. Exporting Report Data You can export the data from the report in several ways. the report in HTML format. CSV output, with the following additional choices. When the second browser window opens, the report has the following features: Click a column header to sort Click a chart icon to chart that column The header will scroll up and down with you Totals at the bottom for that page Pagination for multiple pages of data The ability to the report The ability to close the report Note: Remember, users can only see devices that are in the same groups as the user. If a user is restricted to just Windows devices then the Enterprise reports visible to the user will contain information about Windows only, not Solaris. If there is no data for the report or the user does not have the permissions to see available data, the report will show: There is no data for this report'. Creating a New Report To create a new report, click through the menu tree down to My Reports. If you have not previously built a custom report, the message 'There are no reports available' will appear on the screen. To build a new custom report: 1. Click the New Report. Note: To edit an existing custom report, click the edit icon. 2. Choose the Scope of your report. STM 221

222 Example: If you choose Enterprise, you will be able to run reports that apply to all devices across the enterprise. 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 the Continue. 7. Select the sorting, filtering and permission structures for this report. Structure Scenarios to consider: 8. Click Continue. You may sort according to any chosen statistic in ascending or descending order. Once the report is executed, you can dynamically change the sort. 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. Rows per page set the default rows per page for this report. Permissions options include myself (only I can run the report), Group (all users in the groups I am a member of), or All (all users). 9. Enter a name for the report. 10. Click Save. The report will appear on the My Reports list. Deleting a Report To 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 will appear asking you to confirm your selection. To delete the report, click the OK. Note: You will neither be able to delete a Shared Report that you have access to, nor a Quick Report. Example Report When you build a custom report, you are simply selecting the fields you want to see, in the order you want to see them, and adding filters to narrow the results. 222 STM

223 When the report is run you can narrow the results by selecting a particular set of devices, time period, and other variables. For example, assume you wanted to find all the servers in your environment where the C:\ drive was greater 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. 1. Go to Reports > My Reports and click the New Report button, and then select the template you want to use. 2. Select Enterprise > Storage > Volume Usage Forecast and then click Continue: 3. Next, select the columns you want in the report and the order of those columns. STM 223

224 4. Each template has defaults for the columns selected, the column order and the sort order. 5. Remove the Eighty and Ninety percent columns by highlighting them and clicking the left arrow. 6. Next, select the sorts and filters for the report, allowing us to narrow the output to exactly what we want. Enter the name of the report "C Drives Over 90 Percent" and in this case, you will leave the default sort (server, volume) in place. If you wanted to change the sort order, you can remove current sorts by highlighting them in the text box and clicking Delete Sort, and add new sorts by selecting the Sort By field and order by clicking "Add Sort". The order of the fields in text box is the order the sort will be applied to the report. 7. Next, select the filters. In general, you can filter by any column in the report, and the options of the filter will match the data type: 224 STM Text Fields: like, not like, <, >, =, <=, >=, <>, in, not in Numeric Fields: like, not like, <, >, =, <=, >=, <>, in, not in Date Fields: <, >, =, <=, >=, <>, before, within

225 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 appear in the text box. For "like" filters, make sure you add the "%" before and after the text. Note: Since this is the first filter, you can ignore AND/OR drop down. 8. For the second filer, choose "AND", "% Used", " > " and enter "90" and click "Add Filter". 9. Finally, there are few additional items to select: Time Zone: The default time zone of the report, which can be changed at run time. Row per Page: The default rows per page. Permissions: What users can see this report: Myself, Group (All users in my groups), All (everyone). STM 225

226 10. Now save the report and your page should look like this below. Available actions: Save Report - saves the report and returns to My Reports. Save and Run - saves the report and takes you to the Run Report page 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 you have some C:\ drives over 90%). 226 STM

227 You have the ability to group filters, so you can do "Find all (C: OR D:) drives that are over 90%". So that is how you build a custom report - it is quite flexible and lets you get to your data exactly how you want it. Here are some ways users can leverage the reporter functionality: Identify problem areas before they become "problems" - busiest LUNs, fullest drives, busiest VM or ESX, etc. Chargeback - charge users, departments, customers, etc. for the storage, backups or servers they are using. Backup Compliance - identify full backups that have not been successful for more than 7 days. User Quotas - identify users exceeding their storage quota STM 227

228 File Repository The File Repository or Central Repository is a location to publish and store reports. Users can or publish their reports. The published reports can either be published to a default path or a defined target location. The user defined target location can be defined from the Reports Schedule window or from the File Repository window. To 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: a. Display Name: Enter a meaningful name for your File Repository. b. Device name or IP: Enter the device name or IP address where you shared directory resides c. CIFS Share Name or NFS Export Name: Choose the appropriate field for your environment, and enter name of your mapped drive d. Path: Enter the Path for your shared directory. 228 STM

229 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: STM 229

230 Restrictions for the target file share include: Mapped directories require write access enabled. The mapped drives must be within the same domain as the Storage Manager Server. See the KB article, Publishing Storage Manager Reports, for more information on publishing reports. 230 STM

231 Chapter 10 Using Groups The Grouping functionality allows an administrator to define a logical organization and permission structure to the data that is gathered by Storage Manager. A Group console can quickly show an overview of its devices 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 the same 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 specific organization. When you are assigning devices, objects and users to groups, it affects Storage Manager s interface in the following ways: Tree Menu: (The structure of the tree menu) Users will only see groups and devices in the tree menu that their permissions allow. Reports: The groups available when a report is executed or scheduled: Only the groups and devices the user has access will be available. Consoles: Console can quickly show an overview of its devices as a whole, and serve as a quick link to those devices. When you define a group, you can put different types of objects in them, which include: Backup Clients Server and NAS SAN Storage Volume User Storage Qtree Storage LUN SAN Switch ports VMware VM STM 231

232 VMware ESX In this chapter, we will discuss: Group Examples Creating, Editing, and Deleting Groups Creating, Editing, and Deleting File Type Groups Group Examples One way to think of a group is as a bucket. You place all the objects that logically belong together into a single bucket and Storage Manager will sort them into categories and determine permissions. The default categories that Storage Manager sorts these objects into are: Devices (all OS and NAS Devices) SAN devices (all supported Storage Arrays, Generic SAN Arrays, and Fibre Channel Devices) Storage Groups (File Systems and Shares) Fibre Channel Ports LUNs & Qtrees 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 accounting code in some management reports. Notes: 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." 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. 232 STM

233 When creating a device, if you do not associate it with a group you have defined, and then it will be associated with the default group Unassigned. Once you have associated a device with at least one group, the association with the unassigned group is dropped. Only a user with administrator privileges can see the "Unassigned" group. Creating, Editing, and Deleting Groups Create a New Group To create a new group: 1. Click the Settings button on the Storage Manager website and select the Device Groups link under Device Management. 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. Summary of Categories: Backup Client: All backup clients, including monitored and unmonitored devices (a monitored device has an agent, an unmonitored device does not), not assigned to another group. Backup Clients can belong to multiple groups. SAN: This function allows you to group SAN into logical groups for monitoring. Servers & NAS: All OS and NAS devices defined on the Devices page. A device can belong to one or more groups. Storage - Volume: All volumes (file systems) from all OS and NAS devices not assigned to another group. This allows you to associate volumes into logical collections of storage independent of the device it resides (Note each volume in the assignment window shows the device name and volume name). This allows for easy chargeback reports as they show storage allocation and usage summaries per group. These groups are also used in the Management reports to show allocated and used space per group. Volumes & file systems can be assigned to more than one group. STM 233

234 234 STM User: All the users defined in Storage Manager. Administrators are always a member of every group. This function is done in the background automatically. If you remove an administrator from a group and then save it, Storage Manager will add it back automatically. Users can belong to one or more groups. Storage - Qtree This function allows you to group Storage Qtrees into logical groups for monitoring and chargeback. SAN Switch - Ports: This function allows you to group SAN Switch Ports into logical groups for monitoring. Storage - LUN This function allows you to group Storage LUNs into logical groups for monitoring and chargeback. VMware VM This function allows you to group VMware VMs into logical groups for monitoring. VMware ESX This function allows you to group VMware ESX into logical groups for monitoring. Note: User will have access only to the file system/shares/qtrees in the group assigned to him. 11. To save the new group click Save. The group list will reappear with the new group in the list. 12. To cancel creation of the new group, click the Cancel. The group list will reappear. 13. 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). To assign multiple objects: 14. 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 Regular Expression box. You can filter by the beginning letter by clicking it, or you can enter you own regular expression to find the object you are looking for. Create a New Subgroup Note: There are only two levels of groups for backup clients. To create a new subgroup: 1. Click Add Sub Groups on the Groups screen. 2. Choose the super group for this subgroup.

235 Note: 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 it will move to the Selected box. To remove a backup client from a group, select backup clients on Selected box and click Users section. it will move to the Available box. Same applies for the 4. To save the new subgroup click Save. The group list will reappear with the new group added. 5. To cancel creation of the new subgroup, click Cancel. The group list will reappear. Edit and Delete a Group The following options are available for editing groups: Group Name Name of group ChargeBack Customer charges for resources used. Group Description Give description of the group 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. Creating, Editing, and Deleting File Type Groups The File Type Grouping functionality allows an administrator to define a logical organized structure to the data that is gathered by Storage Manager. The File Type Groups Page displays the existing File Type Group Names. Creating a File Type Group 1. Click the Settings button on the Storage Manager website and select the File Type Groups link under Device Management. 2. Click Add Group to add a new Group. The 'Add Group' console will appear. Group Name: Enter the name of the group. Case-sensitive: Define whether the file names will be case-sensitive. If the box is checked, file names with capital letters will be different than names with lower case letters. STM 235

236 File Types: A list of file types (extensions) returned by the console. The files can be selected by using filters based on starting letters, expression, or by adding a new file type. 3. Once the file types have been selected from the available area, click to add them to the selected list. 4. Click Save. The File Type Group list will reappear 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 and functions as in 'Add File Type Group' will appear. To delete a File Type Group click the Delete icon from the File Type Group list. 236 STM

237 Chapter 11 Using Rules The Rules section details the various rules you can create to achieve certain actions. Once you have created 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: File Analysis Rules Threshold Rules Windows Event Logs Rules Directory Analysis Rules Managing Rules Scheduled Rules Asset Change Rule Using External Scripts SnapMirror Monitoring Creating a new rule To create a new rule: 1. Click Settings in the left navigation menu. 2. Click Rules. 3. Click Add New Rule. 4. Select from one of the following: STM 237

238 5. Enter the necessary information and then click Save File Analysis Rule The File Analysis Rule lets you define rules that will provide detailed file information. Storage Manager currently limits the number of files returned to 5000 per target. You can subdivide the current target by doing local or remote shares, leveraging the depth function, which automatically subdivides the target per subdirectory. What is File Analysis? Analyzes how you are using your file storage 238 STM

239 Works on any formatted storage: Server, VM or NAS device For more information on File Analysis see Setting up File Analysis. What does it report? Summary Information By Owner, Age and Type Find specific files via File Rules File Information - Size, owner, access, creation, modification These rules are applied to devices via the Policies menu under Settings. NOTE: A new Rule must be specified under a policy before it can be used to run a report. Rule Name: Enter the name of the rule. Find the X Y files with: X represents the max number of files reported on. It is on a per file system/share basis. Y represents the limit type to be used in cases where more than max(x) number of files are found. 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 potentially valid, regardless of size. Otherwise, only files that are at least the selected size (specified in megabytes) will be evaluated and considered potentially valid. Accessed Age: If you leave the value set at 0, then all files will be evaluated, and considered potentially valid, regardless of access time. Otherwise, only files that are at least this age, in regards to 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 potentially valid, regardless of modified time. Otherwise, only files that are at least this age, in regards 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 potentially valid, regardless of created time. Otherwise, only files that are at least this age, in regards to created time, will be evaluated and considered potentially valid. File Path Regular Expression: You can specify a regular expression (based on the Java implementation of regular expressions) that all files must match, in regards to file name and path, in order to be evaluated and considered potentially valid. If nothing is specified, then all files are evaluated, and considered potentially valid. Regex Examples: STM 239

240 o To Find files that have a date in their extension, e.g : Create a Rule with the File Path Regular Expression.*[\d]{4}-[\d]{2}- [\d]{2}.* This returns files like "Localdevice_log txt" as well as files like "bookmarks html". o 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. o 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}.* o 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}.* o To Find files that start with the numbers 118: Create a Rule with the File Path Regular Expression.*118[\d]{7}.* o o Regular expression to exclude all ZIP Files: Create a Rule with the File Path Regular Expression.*(?i:(?<!\.zip))$ Regular expression to exclude PST and OST files: Create a Rule with the File Path Regular Expression.*(?i:(?<!\.[op]st))$ For documentation on Regular Expressions in Java, refer to html File Types: A list of file types (extensions) returned by the rule. The files can be selected by using filters 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 names with capital letters will be different than names with lower case letters. Click Save. Threshold Rules The Threshold Rules page allows you to add thresholds for conditions and determine if scripts need to be run or SNMP traps sent. 240 STM

241 To add or edit a Threshold Rule, navigate to Settings > Threshold Rules -> Add New Rule -> Threshold Rule The following descriptions detail the available options. Rule Name: The name you would like to give this rule. Section: The section of the devices that you would like to monitor. This can be done across the Enterprise or by system type. The Section defines the scope of resources to which the rule applies. Category: The category you would like to monitor. The Category defines the metrics that can be applied to the Section. Choose Instances: If applicable, the Choose Instances allows you to choose specific instances on which you can run the rule. Click on add an instance to the selected list. 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. Duration: The duration that the condition must be true for the action to be taken. This is the length of time the condition must be met before the threshold is triggered. STM 241

242 Choose Action: Allows you to assign an action to be taken if the threshold condition and duration occur. Run Client Script: Enter the path and file name of your script. (clientside based). Run Server Script: Choose from the scripts uploaded to the Storage Manager Server. (server-side based). Send Trap: Send out SNMP trap. Once the rule is created, it must be added to the Storage Manager Policies. Windows Event Log Rule Windows Event Log Rules allow you to receive alerts whenever an event takes place. Once created, you must 'Push' the policy to begin receiving alerts. To enable a Windows Event Log Rule: 1. Ensure that Event log monitoring is enabled. 2. Go to Settings > Rules and add a new Windows Event Log rule. 3. Next, go to Settings > Policies and add the rule to the policy that the Windows host(s) belongs to. Rule Name: The name of the Windows Event Logs rule. Event Log: The log file you wish to monitor (Application, System). Event Source: The type of event in the event log you wish to monitor. Event ID: The event ID you wish to monitor. Record and Notify: The types of events you would like to either record or be notified on. Directory Analysis Rule The Directory Analysis Rules allows you to specify certain criteria for identifying directories. Limit Size which 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. 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 result set will be trimmed based on one of the following criteria, depending on which one you select: 242 STM

243 Total directory count, including sub-directories (lowest values will be trimmed) Total file count, including sub-directories (lowest values will be trimmed) Total file size, including sub-directories (lowest values will be trimmed) Access age, including sub-directories (latest values will be trimmed, i.e. oldest directories kept) Modified age, including sub-directories (latest values will be trimmed, i.e. oldest directories kept) Files percentage, including sub-directories (lowest values will be trimmed) Total file count, current directory ONLY (lowest values will be trimmed) Total file size, current directory ONLY (lowest values will be trimmed) Access age, current directory ONLY (latest values will be trimmed, i.e. oldest directories kept) Modified age, current directory ONLY (latest values will be trimmed, i.e. oldest directories kept) 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 the following limit sizes: 10 / 20 / 50 / 100 / 250 / 500. This will be the limit size per file system/share. Minimum Directory Count: numeric values that you would like to set in order to filter out directories that do not contain at least X number of directories. This count includes sub-directories. Minimum File Count: numeric values that you would like to set in order to filter out directories that do not contain at least X number of files. This count includes sub-directories. Minimum Total File Size in MB: A numeric value that you would like to set in order to filter out directories that do not contain at least X number of megabytes of files. This count includes sub-directories. Minimum Access Age in Days: Numeric values that you would like to set in order to filter out directories that do not contain files that are at least X number of days old in terms of access time. This can be used to find high level directories that have not been accessed in a very long time. This count includes subdirectories. STM 243

244 Minimum Modified Age in Days: A numeric value that you would like to set in order to filter out directories that do not contain files that are at least X number of days old in terms of modified time. This can be used to find high level directories that have not been accessed in a very long time. This count includes subdirectories. Minimum Total File Size Percentage: Numeric values that you would like to set in order to filter out directories that do not contain files totaling X percent of the parent directory, in terms of size. This count includes sub-directories. Minimum File Count: Numeric values that you would like to set in order to filter out directories that do not contain at least X number of files. This count is for the current directory only. Minimum Total File Size in MB: A numeric value that you would like to set in order to filter out directories that do not contain at least X number of megabytes of files. This count is for the current directory only. Minimum Access Age in Days: Numeric values that you would like to set in order to filter out directories that do not contain files that are at least X number of days old in terms of access time. This can be used to find the exact directories that have not been accessed in a very long time, based on the files they contain. This count is for the current directory only. Minimum Modified Age in Days: A numeric value that you would like to set in order to filter out directories that do not contain files that are at least X number of days old in terms of modified time. This can be used to find the exact directories that have not been accessed in a very long time, based on the files they contain. This count is for the current directory only. Minimum Total File Size Percentage: Numeric values that you would like to set in order to filter out directories that do not contain files totaling X percent of the parent directory, in terms of size. This count is for the current directory only. Directory Path Regular Expression: A regular expression that you can set in order to restrict the directories considered to a subset. 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, to be within C:\winnt\, ignoring all others. If this option is left blank, all directories will be considered valid. Report: Generate a report that matches the rule. Schedule the selected Action: Schedule the action you selected above. 244 STM

245 Managing Rules Scheduling Rules Asset Change Rule The Storage Manager 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: Windows Event Logs Rules Threshold Rules Directory Analysis Rules Scheduled Rules To define a File Analysis Rule provide the following: Rule Name: Enter the name of the rule. Find the X Y files with: X represents the max number of files reported on. It is on a per file system/share basis. Y represents the limit type to be used in cases where more than max(x) number of files are found. The choices are largest, oldest accessed and oldest modified. Size of: If you leave the value set at 0, then all files will be evaluated, and considered potentially valid, regardless of size. Otherwise, only files that are at least the selected size (specified in megabytes) will be evaluated and considered potentially valid. Accessed Age: If you leave the value set at 0, then all files will be evaluated, and considered potentially valid, regardless of access time. Otherwise, only files that are at least this age, in regards to 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 potentially valid, regardless of modified time. Otherwise, only files that are at least this age, in regards to modified time, will be evaluated and considered potentially valid. File Path Regular Expression: You can specify a regular expression (based on the Java implementation of regular expressions) that all files must match, in regards to file name and path, in order to be evaluated and considered potentially valid. If nothing is specified, then all files are evaluated, and considered potentially valid. Regex Examples: STM 245

246 o To find files that has a date in their extension, e.g : Create a Rule with the File Path Regular Expression.*[\d]{4}-[\d]{2}- [\d]{2}.* this returns files like Localdevice_log txt as well as files like bookmarks html. o o o 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 give just the log files with a date in the file name. 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}.* 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}.* o 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 filters 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 names with capital letters will be different than names with lower case letters. 1. Once the file types have been selected from the available area, click to add it to the selected list. 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. Scheduling Rules The Schedule Rules page lets you execute a script on the device machines at a given schedule. 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 new script, go to Administration-> Scripts page. 246 STM

247 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 will be executed on the device machines according to this schedule. Asset Change Rule The Asset Change Rule page lets you execute a script on the device machines when any asset change occurs. 1. Provide the following a. Rule Name: The name you would like to give this rule. b. Section: The section of the devices that you would like to monitor. c. Category: The category you would like to monitor. d. Property: The property you would like to select. 2. Select one of the following: Run Client Script: Enter the path and file name of your script. (clientside based). Run Server Script: Choose from the scripts uploaded to the Storage Manager Server. (server-side based). Send Trap: Send out SNMP trap. Using External Scripts Storage Manager can execute external scripts. The Scripts window lists scripts that are uploaded to the Storage Manager Server. 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 an asset change occurs. Note: Storage Manager requires scripts with the.bat or.sh file extensions. Note: Storage Manager does not support scripts containing double quotes. Adding a Script Editing a Script STM 247

248 Using Scripts Adding a Script To add a script: 1. Go to Settings > Scripts 2. Click Add and enter the information below. Script Name: Enter a name for the script Description: Enter a description for the script. Upload: Click browse to select a script from the local machine to upload to the Storage Manager server. Scripts added to Storage Manager will be available from the Run Server Script menu when adding or editing certain Rules. Editing a Script The Scripts Window offers two editing options. Clicking the Edit option allows you to modify the Script Name and the Description. Clicking the File Name allows you to edit the content of the script. 248 STM

249 You can also download and delete the script from this window. Note: Storage Manager does not support scripts containing double quotes. Using Scripts Scripts 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. Choose 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. Choose Run a Client Script or Run a Server Script. For more 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 each parameter. STM 249

250 Using Run Client Script Choose Run Client Script to execute a script on the Storage Manager Agent. Add the path to the script when choosing this option. The script must reside on the same network as the Storage Manager Agent where the script will be executed. Using Run Server Script Choose Run Server Script if your script is uploaded to the Storage Manager Server. Server scripts are invoked on the agents that call the script. Parameters are added in the Set the Static Parameter for the script field. If you have more than one parameter, enter a space after each parameter. 250 STM

251 STM 251

252

253 Chapter 12 Using Policies and Setting Alerts in Storage Manager The Storage Manager server has the capability of configuring multiple agents at once using policies. Polices consists of Rules that contain configuration parameters for the devices Polices are intended for advanced users. Typically the default policies will not need to be changed. You can make changes by clicking on the pencil icon Note: 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. Protection: You can protect an agent from being updated by the policy setup push to preserve special setups on a specific agent. For example: On a critical server you may want the performance interval to be 1 minute, but on other servers you want the interval to be 5 minutes. To accomplish this configuration, you would define the policy setup performance frequency at 5 minutes and then use the Device Config icon to configure the critical server to 1 minute. The configuration for the one agent is automatically "protected" and will be unaffected by changes to the policy. This setting will only be overwritten in two cases: When you configure a policy, you check the "override protection" box. If you move the agent from one policy to another. Override Protection: You can also override protection when you need to. When choosing the agents to push parameter(s) to you can choose to override any protection on the agent. Note: This override is for all parameters you select on a push, not parameter by parameter (unless you push them one at a time). So for the above example, if you want to change a parameter (for example: Disk Usage threshold) on the protected agent, you could do so by selecting Yes for the Override Protection on the Push screen. Self-Configure: When a new agent registers it automatically adds itself to the configuration push list (for all parameters). This function allows you to quickly set up all your agents during installation. As soon as the Storage Manager Server is running you should configure Policy Setup parameters so any agents that selfregister subsequently will have the configuration you want. STM 253

254 Monitoring: You can also monitor the push list to see the progress of your configuration. From the push report, 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 for twenty-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 in the links below. Data Retention Policy Policy List Page Creating a Policy Editing a Policy Selecting Rules Data Retention Policies Data Retention Policies allow Administrators to define the duration that they wish to keep each kind of data. The policies are executed once every twenty-four hours by the Storage Manager Maintenance service. Data Retention Policies are divided into the following categories: Backup Database Events Operating Systems SMI-S SNMP/FC/HBA System Virtualization These categories are subdivided into types of data. Each type of data has a retention policy for raw and hourly data. Raw data is collected in defined time intervals. For example, raw data for storage arrays is collected every 15 minutes. Hourly data is the average of the raw data over an hourly interval. 254 STM

255 The Data Retention Policy is responsible for maintaining the minimum data needed for data roll-up. Data roll-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 performance data is collected, data roll-up calculates the average of the last 30 data points (the last hour of data) and inserts it into a summary table of HOURLY data. Once the device collects 24 hours of data, data roll-up calculates the average of the last 24 HOURLY data points from the summary table and inserts it into a summary table of DAILY data. Once the device collects 31 days of data, data roll-up calculates the average of last 31 DAILY data points (last one month of data) from the summary table and inserts it into the summary 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 1 day 1 day + x 7 days 7 days + x 1 month 1 month + x 2 months 2 months + x 3 months 3 months + x 6 months 6 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. See the example below. For example: If you configured Settings > Storage Manager Server > Data Retention > Operating Systems > Disk Usage > Raw Data for one month, and if the Data Retention Policy is run on the 15 th of December, then the Data Retention Policy retains data for the month of November + 15 days of December. In this example, 45 days of data are kept in the Performance table. STM 255

256 Policy List Page The Policy List page allows you to add, edit, delete, or push all configuration parameters out to devices configured in the policy. To create a new policy: Click New Policy and follow the onscreen instructions. To export policies: Click Export. The rules and policies will be saved as a SQL file. A simple execute this SQL file against the database is done to import the settings back when needed. To edit the policy: Click the Edit icon. Once the policy has been edited you will need to push the policy out. To push the policy to the configured devices: Click on the Policy icon. You can get a push list report by selecting Push List Report. Creating a Policy To create a new policy: 1. Click New Policy. 2. Enter the necessary information Policy Class: The type of policy that you are creating (OS, Magnitude, etc.) Base Policy on: Use a predefined policy as a template for the design of the new policy. 3. Click Save. Name: The name that is assigned to the policy. 4. Define any necessary configurations and then click Push. 5. The Push List Report link displays a list of pushed agents/modules/policies. 256 STM

257 Editing a Policy To 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. STM 257

258 3. Click on the edit policy icon for the policy you want to edit. Once you select the desired report it will display a menu with all of the option available for modification. The following example shows the Default SMI-S Policy (SMI-S). Rules Choose which rules to include in this policy Devices Choose which devices to include in this policy SMI-S Configuration Set the configuration parameters for a Storage Array Device 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. Note: After clicking Push, the user will be returned to the Policy web page. In the upper right corner is a link called Push List Report. When clicked, this link will show users any pending reports waiting to be pushed to proxy agents. 258 STM

259 Selecting Rules Choose from the available rules for your policy, and then push the policy to a group of devices. The rules will be activated for those devices, and when the condition of the rule is met, a trap or script will be 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 Storage Manager. Setting Alerts in Storage Manager The following explains the process for creating alerts in Storage Manager: 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. If the rule condition is met, the agent will send a trap to the Storage Manager Server. STM 259

260 Once the trap has been received by the Storage Manager server, the resource or group and severity will be checked and if there is a match, an is sent to the designated user. The following example shows how to create a Threshold Rule in Storage Manager and configuring of notification. To 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 then click Save. For more information see Rules Assigning 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 will be in the OS Policy. 3. Edit the Policy and then click Rules. 4. Move the new rule from Available to Selected and click Save. 5. Verify the Resources are assigned to this policy by clicking Devices. 6. Once done click Push. This will push the policy to the relevant agents. This will update the configuration files for that resource (NetApp in this example). For more information see Policies Note: Next you can verify the progress of the configuration push by clicking the Push List Report link in the top right corner. This will show No Data if the push has worked for the resource. You can also verify if any trap events are being received (assuming the thresholds have been meet) by going to the web console > Monitors > Event Monitor. These events are sent to the server from the Storage Manager agents when a threshold is met. They can be edited 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: Once you have confirmed Storage Manager is receiving traps, you can define which users will receive alert notification s. To assign Alert Notifications: 260 STM

261 1. Configure the SMTP server by clicking Settings > 2. Configure the User and alerts in Settings > Manage Users. 3. Edit the user. 4. Define the Address. 5. Click Add beside Notifications. 6. Define which resource or group to apply to. 7. Define who the s are sent to and determine the severity level of the event being sent. STM 261

262

263 Chapter 13 Common Tasks with Storage Manager This chapter provides a number of common scenarios for which Storage Manager provides solutions. Using LDAP to Add a New User Deleting an Administrator Account with Root Privileges Changing the Default Web Console Port from 9000 How to Assign Remote Shares on Virtual Machines Configuring STM Agents to Use Specific NIC (Network Interface Card) on Servers with Multiple NICs Hiding Report Queries from Displaying in the HTML Source Code How to Change the Temporary Directory when Running a myisamchk Changing Trap Severities on the Event Monitor Webpage Setting up Disaster Recovery with Storage Manager Setting up an Alert for Disk Failure on a SAN Using LDAP to Add a New User Note: The Add User button will be missing when LDAP is enabled. To add a new user to Storage Manager while LDAP is enabled, do the following: 1. Have the user log into Storage Manager using their domain credentials. 2. Once the new user has successfully logged into the Storage Manager website, a second user with Administrative rights must log into the Storage Manager website and go to Settings > Manage Users and click the Manage icon for the new user. 3. By default the new user will not have any privileges to the Storage Manager website. By clicking the Manage icon and the Edit button, login rights can be provided to the new user. STM 263

264 Deleting an Administrator Account with Root Privileges If you wish to delete an account with Root Privileges, you must first change the account to another User Type. By design Storage Manager does not allow users to delete accounts with Root Administrator access. To change and then delete an account that currently has Root Administrator privileges do the following: 1. Click the Settings button and then select Manage Users 2. Click the Manage Icon for the account you wish to delete 3. You will now be on the Profile page for the account. Click the Edit button. 4. For User Type, select the pull down and choose a user type that is different from Root Administrator and then click the Save button. When you go back to the Manage Users page, you will now see an option to delete the account. Changing the Default Web Console Port from 9000 By default the Storage Manager Website uses port Some customer may wish to change this to another port due to port availability or firewall issues. There is a configuration file within the install subdirectory of Storage Manager that will allow users to change from default port 9000 to another port. In this example we will change the Storage Manager Website port to 80. This example will also show you how to change the port assignment for Storage Manager running on Windows or Linux. The file we must modify is called server.xml and it can be found in the following locations: Windows - <installed drive>:\program Files\SolarWinds\Storage Manager Server\conf Linux - /opt/storage_manager_server/conf Open the file with a text editor and do a search for You will see a section that looks like the following 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" 264 STM

265 maxthreads="150" maxhttpheadersize="8192"/> The entry for Connector port= is where we change the port assignment for the Storage Manager Website. I 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 Storage Manager Web service before the change will take effect. To restart the Storage Manager Web service do the following: Windows - Run services.msc and restart the SolarWinds Storage Manager Web Services service Linux From the Command Line Interface, type: /etc/init.d/storage_manager_server restart webserver Open the Storage Manager Web server in a web browser referencing your new port assignment. How to Assign Remote Shares on Virtual Machines Before 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. Press the down arrow d. Press the Discover Now button 3. Once completed check for remote shares STM 265

266 Configuring STM Agents to Use a Specific NIC (Network Interface Card) on Servers with Multiple NICs Storage Manager Agents will use the first available Network Interface Card on a server with multiple Network Interface Cards. This can cause traps to get routed to the wrong network and cause connectivity issues between the agent and Storage Manager Server. If a Storage Manager agent is installed on a server with 2 or more installed network cards, then the core.xml file must be manually updated to define the IP address for the network card you want associated with sending messages to the Storage Manager Server. For example, if eth0 and eth1 are installed on your server, and eth1 is used to send traps, you must associate the eth1 IP address to the Storage Manager agent by following these instructions: 1. Navigate to \Storage Manager Agent\. Example: C:\Program Files\SolarWinds\Storage Manager 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 Storage Manager 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 Storage Manager Agent Services. By doing this you will allow the Storage Manager agent to route traps to the correct network. 266 STM

267 Hiding Report Queries from Displaying in the HTML Source Code By default, STM displays the queries used to run reports in the HTML source code which can then be 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 Storage Manager Web Server service How to Change the Temporary Directory when running a myisamchk When running a myisamchk, it uses the volume that Storage Manager is installed on by default for its temp directory. If this volume is low on space, the myisamchk may not complete since it essentially replicates each table when checking the index and repairing. To change this, add --tmpdir = <path> to the myisamchk command in the parameters section. In the following example, we use a temp directory on E: drive: for %i in (*.MYI) do..\..\bin\myisamchk --defaults-extrafile=..\..\my.cnf -c -a -r -v --tmpdir = E:\temp\ %i For more information see myisamchk. Changing Trap Severities on the Event Monitor Webpage We 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. This will 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 and policies, see Chapter 12. STM 267

268 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. Notes: If you would like to change the severity to only reflect traps that are triggered for a specific rule then select "Override trap definition based on the rule Id" within the "Trap Definition override action" option. 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. Note: Once you click Save, the current traps already listed on the Event Monitor Webpage along with any further traps matching the trap just edited will reflect the updated severity change. Setting up Disaster Recovery with Storage Manager 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 DR server? 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 the FQDN. d. Install the Storage Manager Server software on the DR server. e. Make sure all of the Storage Manager services are running on the DR server. f. Log into the web console for the Storage Manager DR server. g. Select Settings > Policies > Default OS Policy > Edit button (pencil icon) > Communications. 268 STM

269 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. Press SAVE. Note: It is not necessary to push the values. We are only changing the Default OS Policy to match what is already configured on the agents. j. If you have a backup copy of your database that is formatted to the same version of Storage Manager that was running on the compromised server, proceed to step 2. If not, you will be forced 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) Storage Manager Services. Note: Storage Manager versions 5.6 and newer use MariaDB. For versions prior to 5.6, substitute MySQL for MariaDB. 3. If you have a backup copy of your database, rename or delete the default blank database and migrate your backup database to the DR server. Note: The database backup must be formatted to the same version of Storage Manager that is running on the DR server. If you do not have a properly formatted backup of the database or no backup database, you will be forced to start with the blank database that is installed by default. The default location for the database will be: Windows: <installed drive>\program Files\Solarwinds\Storage Manager Server\mariadb\data\ Database is the storage folder Linux: /opt/storage_manager_server/mariadb/data/ Database is the storage folder STM 269

270 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 Storage Manager website for the new server using your regular username, password and insert the license key obtained from your customer portal into Storage Manager. If there is no key present in your customer portal, call customer service to get it reset. Storage Manager will run in evaluation mode for 30 days without a key. 6. Verify that Storage Manager is communicating with the devices being monitored. This can be verified by viewing the main console website. If there are any communication issues, contact technical support for assistance. Setting up an Alert for Disk Failure on a SAN The following explains the process for creating a disk failure alert when one or more disk have failed on a SAN. Note: We must use a threshold rule when building a disk failure alert. Creating a Threshold Rule for Disk Failure 1. Click 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 270 STM

271 Creating 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 clicking the 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 will push the changes to all Storage Manager Proxy agents. If you choose not to select this option, any new proxy agents assigned to Storage Manager will be updated leaving the agents there prior to the policy creation unchanged. 13. Click Save 14. You should once again be back to the Edit Policy page. Click Push. This will push the policy to the relevant agents. Note: Next you can verify the progress of the configuration push by clicking the Push List Report link in the top right corner. This will show No Data if the push has worked for the resource. You can also verify if any trap events are being received (assuming the thresholds have been meet) by going to the web console > Monitors > Event Monitor. These events are sent to the server from the Storage Manager agents when a threshold is met. They can be edited 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. STM 271

272 Alert Notifications: Once you have confirmed Storage Manager is receiving traps, you can define which users will receive alert notifications via . The following steps explain how to assign alert notifications. 1. Configure the SMTP server by clicking Settings > Server Setup: in the Storage Manager Server table 2. Configure the User and alerts in Settings > Manage Users in the Users table 3. Edit the user by clicking the edit icon 4. Define the Address via the Addresses table 5. Click Add beside Notifications 6. Define which resource or group to apply to 7. Define who the s are sent to (subscribers) and determine the severity level (severity) of the event being sent 8. Click Save 272 STM

273 Appendix Appendix What is a SMI-S Provider? Configuring Storage Arrays General Troubleshooting Backup Storage Manager Requirements Upload Modules What is a SMI-S Provider? The Storage Management Initiative Specification (SMI-S) is an interface standard enabling interoperability between storage hardware and software products. SMI- S Provider deployment is determined by the vendor. The three main deployment types are listed and illustrated below. Type 1: SMI-S Provider is installed as a component in the vendor-specific storage management software. Type2: SMI-S Provider is a separate piece of software downloaded from the vendor s website. Type 3: SMI-S Provider is built into the storage array. STM 273

274 SMI-S Provider deployment types The default ports for the Provider 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. If another Cimom (ex: Solaris) or application (ex: IBM Director ) is using that port, you will need to change the port the Provider uses. Please review the vendor documentation for changing the port. SMI-S FAQ Q: 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. Note: Before installing the Provider, run netstat to make sure the default ports are not being used. If another Cimom or IBM Director ( m0_r_tbs_cimserver_openwbem_port_conflict.html) is running on the machine, changing the port the Provider listens 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? 274 STM

275 A: You can use Telnet to test the network connectivity to the SMI-S Provider. For example, on a Windows system: 1. Log onto the Storage Manager 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 If the connection is working, you will see a blank screen. If you get an error message, try the following troubleshooting tips. Troubleshooting tips: 1. Check the SMIS-provider IP address and port number. 2. Check if a firewall is blocking the connection to the IP address or the port number. 3. 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 LSI 3PAR EMC HP IBM HDS (versions after 5.8) HDS (versions prior to 5.8) Namespace root/lsissi11 root/tpd root/emc root/eva root/ibm root/smis/current use /root/hitachi/dm<xx> where xx is version STM 275

276 Configuring Storage Arrays Note: This information is provided as-is as a reference for our customers. SolarWinds provides no guarantees as to the accuracy of this information as the software is built and distributed by 3rd party vendors who may make changes at any time. SolarWinds does not provide official support for problems related to vendor s SMI-S Providers, but customers can seek support via Thwack. Our product team and other knowledgeable customers regularly use these forums and may be able to assist you. Storage Monitoring can monitor arrays from different vendors. Several of these vendors use SMI-S Providers to provide an interface between the storage hardware and software. Additional installation and configuration information is available for the following arrays.. 3PAR Provider Dell Compellent Provider EMC Provider and Solutions Enabler Appliance (VNX/CLARiiON, Symmetrix, VMAX) HDS (Hitachi Data Systems) Provider HP EVA Provider Enabling SNMP for HP LeftHand IBM DS 6000, 8000, or ESS Provider IBM SVC, V7000 Provider IBM XIV NetApp E-Series LSI Provider OS Embedded Provider Pillar Provider Sun StorageTEK 99xx Series Provider Sun StorageTEK 2k, 6k, & FLX Provider 276 STM

277 3PAR Provider Note: This information is provided as-is as a reference for our customers. SolarWinds provides no guarantees as to the accuracy of this information as the software is built and distributed by 3rd party vendors who may make changes at any time. SolarWinds does not provide official support for problems related to vendor s SMI-S Providers, but customers can seek support via Thwack. Our product team and other knowledgeable customers regularly use these forums and may be able to assist you. The 3PAR provider must be enabled before it can be monitored. The following example uses PuTTY to access and configure a 3PAR SMI-S provider. Enabling the 3PAR SMI-S Provider Log into the 3PAR Command Line Interface (CLI) STM 277

278 Using SSH, enter the IP address of the 3PAR array Login using the username and password setup on the Array. 278 STM

279 You should see the following after successfully logging in.. Troubleshooting 3PAR Provider The following section list frequently asked questions for the provider. Q: What is the default username and password? A: 3paradm / 3pardata Q: How do I enable the Provider? A: Logon to provider as described above and call setcim command. This command can be used to enable or disable certain services on the Provider. Q: How do I know if the Provider is running? A: InForm OS version 2.2.3, logon to provider as described above and call type showcim. Note: In previous versions, from a remote machine, telnet to the Array on port Example: telnet Q: How do I get the version of InForm OS? A: Logon to provider as described above and call show version. Q: How do I get an explanation on the commands I am running? A: Logon to provider as described above and call help. For help on a particular command, type help <command> where <command> is the command for help needed. Example: help show. Q: How do I start the Provider? A: Logon to provider as described above and call startcim.. Q: How do I stop the Provider? A: Logon to provider as described above and call stopcim. Q: How do I restart the Provider? A: Log onto the provider as described above. 1. Call cim stopcim f x STM 279

280 2. Call startcim Q: How do I exit the CLI? A: Logon to provider as described above and call quit. Q: What is the minimum InformOS firmware supported version for the 3PAR array? A: Dell Compellent Note: This information is provided as-is as a reference for our customers. SolarWinds provides no guarantees as to the accuracy of this information as the software is built and distributed by 3rd party vendors who may make changes at any time. SolarWinds does not provide official support for problems related to vendor s SMI-S Providers, but customers can seek support via Thwack. Our product team and other knowledgeable customers regularly use these forums and may be able to assist you. The Dell Compellent SMI-S Provider is part of Enterprise Manager. This section covers configuring Dell Compellent Version 6.2 and Dell Compellent Version Dell Compellent Provider Enterprise Manager Version 6.2 This sections shows how to add a user account in Enterprise Manager 6.2 Refer to the Dell Compellent Storage Center s Best Practices for Configuring the Dell Compellent SMI-S Provider for Microsoft SCVMM 2012 for information on installing, configuring, and troubleshooting the Dell Compellent SMI-S provider. This guide includes instructions for creating user accounts with the PowerShell SMI-S configuration script. The complete manual from Dell on configuring Enterprise Manager Version 6.2 can be found at pdf Creating a local user account Enterprise Manager Version 6.2 Add a user for SMI-S to Enterprise Manager, then Use the SMIS User Configuration Script to add a matching user to the Dell Compellent SMI-S Provider. The name and password of both accounts must match. 280 STM

281 1. Add a user to Enterprise Manager that has the Administrator privilege and has a password that is no longer than eight characters. Users with the Data Collector Manager. The user that you add to the Dell Compellent SMI-S Provider must match this user. To avoid confusion, Dell Compellent recommends naming the user smis. 2. Make sure the Windows PowerShell execution policy allows scripts to run. a. Start Windows PowerShell. b. To view the current execution policy, run the command Get- ExecutionPolicy. c. If the execution policy is currently set to Restricted, run the command Set-ExecutionPolicy AllSigned to allow signed scripts to run. After you are done using the script, you can change the execution policy back to Restricted if needed. 3. From the Start menu, select All Programs Dell Compellent Enterprise Manager Launch SMIS User Configuration Script via PowerShell. Windows PowerShell appears. 4. (Conditional) If PowerShell prompts you to run the script, press R or A, then press Enter. The script runs and displays a welcome message. 5. Add a user that matches the user name and password of an Enterprise Manager user. a. Press U to manage users, then press Enter. The Manage Users menu appears. b. Press A to add a user, then press Enter. The Please choose an EM user menu appears. c. Type the number that corresponds to the Enterprise Manager user you added, then press Enter. A password prompt appears. d. Type and confirm the password for the Enterprise Manager user that you selected in the previous step. After you confirm the password, the script prompts you to create a matching local Windows administrator account if it does not already exist. e. Press O to create a corresponding local Windows user, then press Enter. The script prompts you about the password for the local Windows user. STM 281

282 To use the same password, press Y, then press Enter. To specify a different password, press N, then press Enter. If the local Windows administrator user does not have rights to log in as a service, it prompts you to add them. a. Press O to allow the local Windows administrator user to log in as a service, then press Enter. The script prompts you to set the Password Never Expires option for the local Windows administrator user. b. Choose whether you want to allow the password for the local Windows administrator user to expire. To prevent the password from expiring, press Y, then press Enter. To allow the password to expire, press N, then press Enter. When the user setup is complete, the script displays the text User added successfully and returns to the Mange Users menu. 6. To confirm that the user has been added at the Manage Users menu, press L to list users, then press Enter. 7. Adding the Compellent to SolarWinds Storage Manager software. a. Login to SolarWinds Storage Manage. b. Click Home on the upper left or go to Settings on the upper right and Click Getting Started. 282 STM

283 c. Click Add next to Storage Arrays. d. Click the dropdown. e. Select Dell Compellent. f. Enter the Compellent Enterprise Manager username and password. This is the same username and password created through the CLI (cimuser) command. g. Example User: cmuser h. Example Password: STM1234 i. Provider IP: <IP of the server running the Compellent Data Manager Collector> j. Click Test. k. Copy the bolded IP from the results screen. l. Paste the copied IP into the Storage Center IP section. m. Click Save. Dell Compellent Provider Enterprise Manager Version Refer to the Dell Compellent Storage Center s Best Practices for Configuring the Dell Compellent SMI-S Provider for Microsoft SCVMM 2012 for information on installing, configuring, and troubleshooting the Dell Compellent SMI-S provider. This guide includes instructions for creating user accounts with the PowerShell SMI-S configuration script. Dell support offers a video on how to configure the SMI-S collection for Dell Compellent arrays. Creating a local user account Enterprise Manager Version To add the Dell Compellent Array, you must first create a local user on the server where the Compellent Data Collector Manager is installed. For version only. You will first need to create a local user on the server where Compellent Data Collector Manager is installed. 1. Login to the Windows server where the Compellent Data Collector Manager is installed. STM 283

284 2. Create a Windows Local User account with 8 characters or less - DO NOT USE Special Characters. a. User Example: cmuser b. Use any Alphanumeric password c. Password Example: storage Add the Windows local user account to the Administrators Group. 4. Give the User Account rights to logon as a Service. a. All Programs > Administrative Tools > Local Policies > User Rights Management. b. Double click on Log on as a service Policy. 5. Add the user and then apply the changes. 6. Important: Log off and Login to the server with the new Windows Local User account you ve just created. Example User: cmuser 7. Create a New User for Compellent Enterprise Manager. Note: If open security is used, the user can be added from the Enterprise Manager Client. a. Login to Compellent Enterprise Manager. b. Type the username you used for the Local Windows Account that was created. c. User Example: cmuser. d. Click the Check box Create New User. e. Type an alphanumeric password with LESS than 8 characters and NO Special Characters. f. Password Example: STM1234. g. Click Login. 8. Once the New User has been created click the Add Storage Center button to add it to the user or click the Management menu item at the top left of the screen. Use the Admin credentials to add the Storage center to the user. Note: If an Advanced security policy is used, add the user from the Data Collector Manager Interface. 9. Open the Compellent Data Collector Manager GUI. 284 STM

285 a. Click > All Programs > Compellent Technologies > Compellent Enterprise Manager > Compellent Enterprise Data Collection Manager. b. Click Properties. c. From the User Viewer, confirm that the new user is now visible. 10. Set the Service Type and User in Data Collector Manager. a. Click Service from the left pane. b. Click Change at the bottom right in the Data Collector Service Properties. This allows you to edit the configuration. c. Click the Service User Type dropdown and change it to Local User Account. d. Add the Service User Name and Password. e. Use the Windows Local User Account and Password that was previously created. f. User Example: cmuser. g. Password Example: storage123. h. Click Apply Changes on the bottom right. 11. Configure SMI-S in Data Collector Manager. a. Click SMI-S from the Left Pane The SMI-S Server configuration will show in the right pane. b. Click Change at the bottom right in the SMI-S Server Configuration. c. Select Enable SMI-S Server. d. Uncheck Use Https for SMI-S server connections. e. Check Manually Manage Users. f. Click Apply Changes on the bottom right. 12. To add SMI-S users from the CLI, run the Command Prompt as Administrator. STM 285

286 286 STM a. Change directory to <Compellent install folder >\Compellent Enterprise Manager\msaservice\Pegasus\bin. b. Type: cimuser -a u <username> -w <password>. c. User is the Compellent Enterprise Manager user created. d. User Example: cmuser. e. Password is the Compellent Enterprise Manager password. The less than 8 character password used when creating the Enterprise Manager account. f. Password Example: STM1234. g. Type: cimuser -l <enter> - This will verify the user has been added successfully. h. Restart the Compellent Data Collector Manager service. 13. Adding the Compellent to SolarWinds Storage Manager software. a. Login to SolarWinds Storage Manage. b. Click Home on the upper left or go to Settings on the upper right and Click Getting Started. c. Click Add next to Storage Arrays. d. Click the dropdown. e. Select Dell Compellent. f. Enter the Compellent Enterprise Manager username and password. This is the same username and password created through the CLI (cimuser) command. g. Example User: cmuser. h. Example Password: STM1234. i. Provider IP: <IP of the server running the Compellent Data Manager Collector>. j. Click Test. k. Copy the bolded IP from the results screen. l. Paste the copied IP into the Storage Center IP section. m. Click Save. Troubleshooting the Dell Compellent Enterprise Manager Note: Dell Compellent does not allow special characters in the Enterprise Manager password. Q: What is the minimum version of Enterprise Manager supported?

287 A: v Q: Where can I find the version of Enterprise Manager running? A: Open the Data Collector Manager GUI. If the service is running, there will be a shortcut in the system tray. Right click show. Version is displayed on the screen Q: How to stop/start the SMI-S provider? A: The SMI-S provider is NOT running as a separate service. It is running as a process under the Data Collector Manager Service. The service name is Compellent Enterprise Manager Data Collector. The process name of the smis provider is cimserver. Q: Unable to connect or get data from the SMI-S Provider. How do I debug? STM 287

288 A: a. Step through the configuration steps and make sure everything is configured correctly b. Check the Task Manager Process list. Make sure the cimserver is running. c. Verify that the cimserver is listening on port (netstat -ano find "5988") d. Verify that SMI-S user is added correctly e. From command prompt, run <Compellent install folder >\Compellent Enterprise Manager\msaservice\Pegasus\bin\cimuser -l f. Open Data Collector Manager Click Properties Choose Log Viewer g. Enable debug Logging h. Open Data Collector Manager Click Properties Choose Debug Loggers i. Check SMI-S, Compellent API, API XML Web Services j. Apply the changes. Debug Logs are located in <Compellent install folder>\compellent Enterprise Manager\msaservice\etc\compservices\debuglogs Note: Turn the debug logging off after collecting the logs. Q: Is there any info on the SMI-S provider available in the Data Collector Manager help? A: Yes. Detailed instruction on setting up the SMI-S for the specific version installed is available in the help. Click HELP on Data Collector Manager startup screen. See the section under Using Dell Compellent SMI-S provider. 288 STM

289 EMC Provider and Solutions Enabler Appliance (VNX/CLARiiON, Symmetrix, VMAX) Note: This information is provided as-is as a reference for our customers. SolarWinds provides no guarantees as to the accuracy of this information as the software is built and distributed by 3rd party vendors who may make changes at any time. SolarWinds does not provide official support for problems related to vendor s SMI-S Providers, but customers can seek support via Thwack. Our product team and other knowledgeable customers regularly use these forums and may be able to assist you. SolarWinds provides some guidance on installing the EMC SMI-S provider and Solutions Enabler Appliance software. For more information on what a provider is see SMI-S provider. The Solutions Enabler Appliance is an alternative to installing the Windows/Linux SMI-S provider software. This section explains the process of downloading, installing and configuring your software. This section also explains the task of adding a SAN to your provider, troubleshooting and provides additional resources. The following is included in this section: Downloading Software and Documentation from EMC Installing EMC Provider Version 4.0 and Later Logging into Your Provider Adding a SAN to the Provider Installing EMC Solutions Enabler Appliance Troubleshooting EMC (All Versions) Troubleshooting EMC Versions and Later Additional Resources Downloading Software and Documentation from EMC The following information provides instruction on how to download software and documentation from EMC. The SMI-S provider, Solutions Enabler Appliance, and documentation can be downloaded from the following website: STM 289

290 If you choose to download the SMI-S provider software, log into the website, click Support and do a search for SMI-S Provider Download and download the latest version. You can download a copy of the release notes by searching for smi-s provider release notes, sort by relevance, and download the version that matches your SMI-S software version. The release notes contain detailed instructions on installing and configuring your SMI-S software. 290 STM

291 If you choose to download the Solutions Enabler Appliance software, log into the website, click Support and search for Solutions Enabler. STM 291

292 Installing EMC Provider Version 4.0 and Later Before you configure the Provider, please make sure you have the following information: Controller IP Addresses Unisphere ID and Password with at least manager privileges Notes: The default ports for the Provider are 5988 for HTTP traffic and 5989 for HTTPS traffic. Do not install your EMC Provider where ECC is installed, if possible. Before installing the Provider, run netstat to make sure the default ports are not being used. If another Cimom (ex: Solaris) or application (ex: IBM Director) is 292 STM

293 using that port, you must change the port the Provider uses. Please review the vendor documentation for changing the port. This section provide installation steps for the following operating systems: Windows Linux The following steps explains the installation process for Windows: 1. Download your software from the EMC website. 2. Save all files and exit all Windows applications. Launch the selfextracting executable. For example: To install the EMC SMI-S Provider V4.6 software on a Windows platforms, launch the self-extracting executable, se76226-windows-x86-smi.exe. The EMC Solutions Enabler with SMI X86 welcome page appears prompting you to install Solutions Enabler with SMI version x.x. click Next. 3. The Destination Folder dialog box opens and prompts you to select an install directory for the Solutions Enabler and EMC SMI-S Provider. It is recommended that you choose the default directory. Choose a location for the install and click Next. 4. The Provider List dialog box appears. Select Array Provider and click Next. 5. You are prompted with the Service List. Accept the default settings and click Next. 6. The Installation dialog box appears. Click Install. 7. When the installation completes, click Finish. The following steps explains the installation process for Linux: 1. Download the software from the EMC website. 2. Extract the TAR image to a temporary directory. 3. Change the directory to the location of the EMC SMI-S Provider kit and run the install script by using the following commands: cd /<location of extracted files or CD>/UNIX./se<xxxx>_install.sh -install 4. The installation program will begin copying the files. When complete, the installation program will automatically start the storapid daemon and the cimserver, which may take a few minutes. 5. When complete, the installation program will return the following confirmation message, which lists EMC Solutions Enabler with SMI-S Provider in the HAS BEEN INSTALLED list: STM 293

294 # # The following HAS BEEN INSTALLED in /opt/emc via the rpm utility. # ITEM PRODUCT VERSION 01 EMC Solutions Enabler V7.6.2 SMI KIT V4.6.2 # Logging into Your Provider To log into the provider software, run the TestSmiProvider executable located at the <install_dir>\ecim\ecom\bin directory and accept the defaults for hosts, connection type, and port, for example: Connection Type (ssl,no_ssl) [no_ssl]: Host [localhost]: Port [5988]: Username [admin]: Password [#1Password]: Log output to console [y n (default y)]: Log output to file [y n (default y)]: Logfile path [Testsmiprovider.log]: Symmetrix Symmetrix arrays are discovered automatically by the provider. So it is not required to add it to the provider using addsys command. The host where the provider is installed must have at least one LUN presented to it from the array. EMC recommends having at least 6 gatekeepers for getting better performance. 294 STM

295 VNX/CLARiiON Locally Attached A locally attached storage array is one in which at least one VNX/CLARiiON LUN is visible to the host on which the provider is running. The locally attached VNX/CLARiiONS are discovered automatically. But it requires the authorization information for each VNX/CLARiiON storage processor already added. 1. Confirm the array to be added is locally attached: <install_dir>\symcli\bin\syminq cids There should be at least one LUN mapped to this host from the array. 2. Check the OSLSProvider.conf setting has discover set to true : OSLSProvider.conf is located at <install_dir>\ecim\ecom\providers folder. OslProv/com.emc.se.osls.osl.StorApi.database.discover=true 3. List the authorization info: <install_dir>\symcli\bin\symcfg list auth 4. If the list does not have entries for SPA and SPB of this array, stop the provider service(ecom) 5. Add the authorization for SPA and SPB using: <install_dir>\symcli\bin\symcfg authorization add host <host> username <user> -password <pass> where <host> is the IP Address of the storage processor. 6. Start the provider service. VNX/CLARiiON out-of-band Note: Out-of-band VNX/CLARiiON are arrays which do not have any LUNs presented to the host where the provider is running. 1. Log into the Provider by following the steps from Logging into the Provider. 2. Type y at Add System prompt. 3. Chose the Array Type 1 for VNX/Clariion 4. Type in the IP address of Storage Processor A and Storage Processor B 5. Type the Address type 2 for both Storage Processors STM 295

296 6. Type the Username and Password for a user with either Admin or Manager privileges on the Array. Note: If the addition of the Array is successful, you will get an output of 0 when the Array is discovered. The output should look like ++++ EMCAddSystem ++++ OUTPUT : 0 Legend:0=Success, 1=Not Supported, 2=Unknown, 3=Timeout, 4=Failed 5=Invalid Parameter 4096=Job Queued, 4097=Size Not Supported System : // /root/emc:Clar_StorageSystem.CreationClassName="Clar _StorageSystem",Name="CLARiiON+CK " Make a note of the Identifier (CLARiiON+CK in the sample output shown above), which is required for configuring the Array in Storage Manager Adding a Symmetrix & VNX/CLARiiON Out-of-Band Note: Out-of-Band VNX/CLARiiON are arrays which do not have any LUNs presented to the host where the provider is running. 1. Log into the Provider by following the steps from Logging into the Provider. 2. Run the addsys command. 3. Type y at Add System prompt. 4. Chose the Array Type to be monitored (1 for Clariion, 2 for Symmetrix). Note: If choosing EMC Symmetrix, a LUN needs to be presented to the host where the EMC Provider is installed. 5. Type in the IP address of Storage Processor A and Storage Processor B if Clariion. Type the array id for Storage Processor A and Storage Processor B if Symmetrix 6. Type the Address type from step 5 above for both Storage Processors (2 if IP Address, 3 if Array ID). 296 STM

297 7. Type the Username and Password for a user with admin or manager privileges on the Array. Note: If the addition of the Array is successful, you will get an output of 0 when the Array is discovered. The output should look like: ++++ EMCAddSystem ++++ OUTPUT : 0 Legend:0=Success, 1=Not Supported, 2=Unknown, 3=Timeout, 4=Failed 5=Invalid Parameter 4096=Job Queued, 4097=Size Not Supported System : // /root/emc:Clar_StorageSystem.CreationClassName="Clar_Stor agesystem",name="clariion+ck " Make a note of the Identifier (CLARiiON+CK in the sample output shown above), which is required for configuring the Array in Storage Manager. Installing EMC Solutions Enabler Appliance You can download instructions for installing and configuring your software from the EMC website. Log into your EMC account, click the Support tab, and do a search for Solutions Enabler Installation Guide. STM 297

298 Note: It is also recommended that you download the latest OVA and ISO files for your Solutions Enabler Appliance software. Troubleshooting EMC (All Versions) The following section details FAQs regarding troubleshooting issues. Q: How do I find the version of the provider? A: To find the provider version, do the following: OR <install_dir>\symcli\bin\symcfg version Login to <install_dir>\symcli\storbin\testsmiprovider Execute the dv command. Q: What port is used between the EMC Provider and VNX/Clariion? A: Port 443 is used for bidirectional communication between the EMC Provider and VNX/Clariion. Q: Why is my VNX/Clariion not reporting performance data? A: Statistics logging must be turned on. 298 STM

299 To enable Statistics Logging, do the following: 1. Open Unisphere. 2. Right click the icon for the storage system. 3. Click Properties. 4. Be sure SP A and SP B are in the System Level setting section. 5. Click the box for Statistics Logging under the Configuration section. Q: What is the minimum flare code level that EMC recommends for the VNX/CLARiiON arrays to work with the EMC SMI Provider? A: For release R26 R for CX3 arrays and R for CX arrays For release 28 For release 29 R for all arrays R for all arrays Q: What are some steps I can follow to get VNX/Clariion Performance data? A: The following are some steps that can be followed: 1. Make sure Statistics are enabled for the array on SP A and SP B in Unisphere (Follow instructions in the section: Why is my VNX/Clariion not reporting performance data?). 2. For locally attached VNX/CLARiiONs, check if authorization info is present. See section: Adding Authorization Info for Locally Attached VNX/CLARiiON. 3. Run EMC TestSMIProvider and run the command dv. Make sure all array are discovered without any errors. 4. Make sure there are instances for class name CIM_BlockStorageStatisticalData when enumerating instance names (ein). To do this, do the following: 5. Run Tek-Tools testprovider or EMCs testsmiprovider (Logging In instructions above in Tools section). 6. Type ein for command. 7. Type CIM_BlockStorageStatisticalData for Class Name. If no instances are returned, follow the instructions on resetting EMC provider (How do I reset EMC provider?). Once complete, repeat steps 1-3 again. Q: How do I get data for a CX600? STM 299

300 A: Per EMC, they do not support flare code 16 (2.16.x.x.x). The array must be upgraded to 19, 22, or 24 with all the latest patches for that release Q: I get the following DEP error from windows for the SMI-s provider, how do I fix it? A: To enable DEP for the SMI-s provider, do the following: 1. Click Start. Click Run. Type sysdm.cpl, and then click OK. 2. On the Advanced tab, under Performance, click Settings. 3. On the Data Execution Prevention tab, use one of the following procedures: 4. Click Turn on DEP for essential Windows programs and services only to select the OptIn policy. 5. Click Turn on DEP for all programs and services except those I select to select the OptOut policy, and then click Add to add the programs that you do not want to use the DEP feature. 6. Click OK twice. The following link below gives a detailed description of hardware and software based DEP: Q: What permissions are required when configuring a user in Unisphere? A: You have to have an Admin or Manager privileges in order to discover. Note: Monitor privileges are not enough. Q: Why does the addsys command fail when trying to add an array to be monitored by the EMC Provider? A: When running addsys, make sure of the following: 300 STM

301 Make sure the user used has at least manager privileges. Make sure that spa and spb are in correct order. To get the correct IP address for the storage processors, follow the instructions in the question How do I get the IP address for the storage processors from Unisphere. NOTE: Array ID 0 refers to spa, and Array ID 1 refers to spb. Q: Why do commands like addsys and dv fails with Error: CIM_ERR_FAILED: A general error occurred that is not covered by a more specific error code: provider initialization failed? A: Check whether the provider is installed on a 64-bit OS, if then check that provider installed supports 64 bit OS (Check in Provider Release Notes- Supported Host Operating System). Provider installs including version 3.3 supports only 32 bit OS. Q: How do I get the IP address for the storage processors from Unisphere? A: To get the correct IP address from Unisphere, do the following: 1. Go to Unisphere 2. Right click on spa for the array you wish to add. 3. Click Properties. 4. Click Network. (This will show the IP address for spa). 5. Do steps 2 4 for spb. Q: The server where we planning to install have a version of Solutions Enabler installed. How do I determine which version of the provider to use in this case? A: Solutions Enabler is used by the provider as well as EMC management applications like ECC. It is better to install the provider on another server if possible. Otherwise, follow these steps to find out the correct version. Check the version of the solutions enabler: <install_dir>\symcli\bin\symcfg version The output show the version of the solutions enabler installed. Check the solutions enabler version of the installer. It can be found from the name of the installer. Example: se76226-windows-x86-smi.exe is packed with Solutions Enabler version STM 301

302 Install only if the versions match. If the versions do not match, check to see if the solutions enabler can be upgraded to the required version without affecting ECC or other management applications currently installed. Q: Array Capacity (Raw) on the console screen shows non-zero value for Free capacity even though the Physical Disk Report shows that all disks are assigned to raid-groups. Isn t the free capacity representing the total capacity of the disks which are not assigned to any raid-groups? A: This following response is from EMC. The observed behavior is consistent with the way VNX/Clariion works. On VNX/Clariion, it is possible to see the primordial pool with RemainingManagedSpace having a non-zero value even though all disk drives are in use. In this situation, the value in the RemainingManagedSpace represents a collection of "left-over", unusable, disk capacities after the raid groups are created (i.e. concrete pools). For example, let's assume there are two disk drives available in a VNX/Clariion, with the capacities of 10 and 15 gigabytes. The client wishes to create a raid 1, raid group from these two disk drives. Because both disk drives should have the same size, the array uses the first disk drive with the capacity of 10 gigabytes and the first 10 gigabytes of the second disk drive. The remaining 5 gigabytes of the second disk drive will remain unused and is reported as a part of the RemainingManagedSpace capacity of the primordial pool. One way to determine if all disk drives are in use is to examine the primordial pool's "EMCRemainingRawCapacity" property. If this property contains 0, it means all disk drives are in use by various concrete pools. Q: EMC posted and End of Service Life for the Solutions Enabler and SMI-S provider, what are the versions affected and the end of life dates? A: Product Version EOSL Date SMI-S Provider /2008 SMI-S Provider /2009 SMI-S Provider /2010 Solutions Enabler /30/2008 Solutions Enabler 5.4 9/30/2008 Solutions Enabler 5.5 9/30/ STM

303 Note: Solutions Enabler customers who choose to upgrade their environments to SMI-S Provider version must uninstall their existing versions of Solutions Enabler before the installation. The SMI-S Provider V4.6.2 installation is bundled with the required Solutions Enabler libraries. For more information see the SMI-S provider release notes for version Q: Why is Symmetrix not showing correct number hosts masked into array? A: Look at the symapi log file and look for following message: SymDevMaskLoginHisto The VCMDB_RESTRICTED bit on symm is set, only records for this host will be returned This message means that the host the provider is running on needs to be able to obtain all the vcmdb info. EMC does not provide instructions on how to change this value and EMC should be consulted for any additional steps. Q: Can we use the EMC provider to monitor the VNX/CLARiiON behind the Celerra NS-20 device? A: Yes, it works the same way as a regular VNX/Clariion Troubleshooting EMC Versions and later Q: LocalDir/admin no longer works in provider, did the user name change? A: Yes, username for provider is now admin Q: What files are needed before opening a trouble ticket with EMC? A: Any issues related to the EMC provider, EMC requires the following info before they ll look into the problem: All log files from <install_dir>\symapi\log All log files from <install_dir>\ecim\ecom\log symapi_db.bin file, located <install_dir>\symapi\db Output of the dv command from the TestSmiProvider utility Output of the tms command from the TestSmiProvider utility Q: How do I change the provider port? A: To change the port, do the following: On the machine running the Provider: STM 303

304 1. Stop the ECOM Service 2. Navigate to <Install_dir>\ ECIM\ECOM\conf 3. Edit the properties of the file and uncheck Read-only, click ok 4. Open the file named port_settings.xml. 5. Change the port0 and port1 tag values to ports currently not in use. Example: <ECOMSetting Name="Port0"> <port>15988</port> <secure>false</secure> <slp>true</slp> </ECOMSetting> <ECOMSetting Name="Port1"> <port>15989</port> <secure>true</secure> <slp>true</slp> </ECOMSetting> 6. Save port_settings.xml file. 7. Start the ECOM Service. Q: How do I add a new user to the provider? A: Login to the provider GUI. 1. Go to the URL and log in using the username LocalDir/admin and the password #1Password. 2. Click Add User and create a user with the role of Administrator. This newly created username can now be used to obtain access to the Array Provider. Note: LocalDir/ will prepended to the username whenever a new user is created. Example: The new user name will be LocalDir/<the user name that you have given> Q: How do I start/stop the provider from command prompt? A: Windows: 304 STM

305 UNIX: Stop <install_dir>ecim/ecom/bin/sm_service stop ecom.exe Start <install_dir> ECIM/ECOM/bin/sm_service start ecom.exe Stop Obtain the PID of the ECOM process and issue the kill command for that PID. ie kill SIGTERM [PID] Restart <install_dir>ecim/ecom/bin/ecom d Q: How do I prevent locally attached VNX/Clariion from being discovered automatically? A: To remove a locally attached VNX/CLARiiON from auto discovery, write out a file with name claravoid in the directory SYMAPI/config. The file must have the name of the VNX/CLARiiON. Q: How do I prevent Symmetrix arrays from being discovered automatically? A: DO NOT use this method if the host where the provider is installed also has ECC running. Write out a file with name symavoid in the directory SYMAPI/config. The file must have the SymmID of the Symmetrix arrays that should not be auto-discovered. Use the command SYMCLI\bin>symcfg list to get the SymmID. Note: Make sure that the provider is not running when you make the change. Delete the symapi_db.bin file and re-discover for the changes to take effect. Q: Will the LocalDir/admin password expire? A: Yes, it will expire after 90 days. EMC was not aware of this, and are looking into making it tunable in a future release. So as of 4.1 release, it will expire. If user resets password, it again expire in 90 days after resetting. If user creates new user, it will password expire in 90 days. You can change password from Additional Resources This section provides additional resources for installing EMC software: Provider installation video o SolarWinds provides a step-by-step EMC VNX/CLARiiON provider installation tutorial hosted on Thwack. EMC support portal STM 305

306 o Visit the EMC 2 support portal for more information on installing the EMC SMI-S Provider. 306 STM

307 Hitachi Data Systems (HDS) Provider Notes: This information is provided as-is as a reference for our customers. SolarWinds provides no guarantees as to the accuracy of this information as the software is built and distributed by 3rd party vendors who may make changes at any time. SolarWinds does not provide official support for problems related to vendor s SMI-S Providers, but customers can seek support via Thwack. Our product team and other knowledgeable customers regularly use these forums and may be able to assist you. Pre Configuration Requirements Before beginning the host agent installation, you must create and assign command devices so that connectivity can be established between the host agent and the disk arrays. For more information on configuring the Hitachi Data Systems (HDS) Provider, see the following link: Refer to your product s HDS documentation for the most up to date information. Some guidance for installing the HDvM and HiCommand is provided below. Installing and configuring the Hitachi Device Manager (HDvM) 1. Install HDvM Agent on a host that can communicate to the HDvM Server. You can install HDvM agent in HDvM Server itself (recommended) or you can use any Windows, Solaris and Linux machines. 2. Map the HDvM Agent. During the Agent installation, you will get a message to configure the agent now or later. If you configure it during the installation you have to setup the IP/HOSTNAME of HDvM Server along with Credentials to access it. If you choose to do it later, you can do it via command line with the hdvmagt_setting command under <HDvM Agent Install Dir>\Hitachi\HDVM\HBaseAgent\bin\ directory. 3. Navigate to the directory, <HDvM Agent Install Dir>\Hitachi\HDVM\HBaseAgent\bin\ Manually run the HiScan command to verify the connectivity: STM 307

308 HiScan s IP/HOSTNAME of HDvM Server by navigating to <HDvM Agent Install Dir>\Hitachi\HDVM\HBaseAgent\bin\ directory. 4. Configure the HDvM agent to collect the performance files. Navigate to the directory, <HDvM Agent Install Dir>\Hitachi\HDVM\HBaseAgent\bin\ Run the command to write a new perf_cmddev.properties file. perf_findcmddev write You can also view and verify the results by perf_findcmddev view and perf_findcmddev verify commands. 308 STM

309 5. Restart the HDvM Agent. 6. To collect performance data, configure HDvM Server to use your HDvM agent. Edit the server.properties files and specify the exact hostname of the HDvM Agent under server.cim.agent. You must use the exact name of the server that is listed in the hosts tree of HDvM Server. STM 309

310 7. After steps 1-6 are performed, restart the HDvM Server service then restart the HDvM Agent service. Installing the HiCommand Device Manager on Windows The following section detail installation steps for Windows. The HDS provider is part of the HiCommand Device Manager and is a purchased product. Installation Steps: 1. Double click the HiCommand Device Manager Install package. 310 STM

311 2. Click Next at the welcome screen. 3. Accept the license agreement. Click Next. 4. Select Disable SNMP trap function if port 162 is in use. Otherwise, skip this step. Click Next. STM 311

312 Note: Disabling SNMP function has no effect on SMI-s provider. 5. Choose the Destination folder for HiCommand. Click Next. 312 STM

313 6. Choose the destination for the HiCommand Suite Common Component database. Click Next. STM 313

314 7. Choose the destination for the HiCommand Device manager database. Click Next. 314 STM

315 8. Specify the IP address of the machine HiCommand Device Manager is being installed on and Port for HBase Storage Management Web Service. Click Next. STM 315

316 9. Click Next at the adding to the windows firewall exceptions screen. 316 STM

317 10. Select YES for enabling the SMI-s provider service after installation. Click Next. STM 317

318 11. Select NO for SSL, unless a secure connection is needed. Change port if needed. Click Next. 318 STM

319 12. Depending on the Array type, a Device Manager agent may be needed. If it is needed, select yes and specify an IP address. Refer to the Which HDS arrays need a Device manager agent for performance metrics to be gathered from question in the Troubleshooting section. STM 319

320 13. Select YES for the SLP function to be enabled after installation. Click Next. 320 STM

321 14. Select YES to start the HiCommand Suite to start after installation. Click Next. STM 321

322 15. Click Install at the Pre-Installation Summary page. 322 STM

323 16. Click Next at the Secure Socket Certificates Note. STM 323

324 17. Click Finish. Troubleshooting HDS The following section details troubleshooting steps for HDS. Q: Which HDS arrays need a Device manager agent for performance metrics to be gathered from? 324 STM

325 A: Refer to the following image (USP V/VM, and TagmaStor USP). Q: What is the default username/password for the provider? A: The username and password for the Provider is the same for the DataCenter (not administrator/administrator). If need be, they can create a new one for Storage Manager. Q: What user permissions are required for the provider? A: All resources with view privileges. STM 325

326 Q: What should I do if the test results window returns blank and I am using an admin ID to access the device manager? A: Save the resource and check the SMI-S module log. If you see an Access denied error this means that the ID you are using doesn t have the proper permissions. Use the ID: System and Password: manager (both are case sensitive). This should solve your problem. Q. How do I enable performance statistics? A: To enable performance on a USP/USP-v/USP-vm series storage system: There are two pieces of software that have to be installed on the command view (in case of HP XP)/device manager server. 1. Hitachi/XP Raid Manager software which is only needed to create the device library. 2. Device Manager agent which can access the command device to transfer the performance data. Device Manager agent requires the Hitachi/XP Raid Manager device library to function. The system that Device Manager/Command View is running on must have SAN access to the command device. Follow the instructions to install the XP Raid Manager, but you do not need to actually have the HORCM process running. For further information see the XP Command View Advanced Edition software server Administrator Guide for Device Manager and Provisioning Manager ( in case HP XP) or Hitachi Storage Command Suite Software Server Installation and Configuration Guide for Hitachi Device Manager and Provisioning Manager To enable performance on an AMS/WMS/Thunder 9500v/Thunder 9200 series storage system: See the XP Command View Advanced Edition software server Administrator Guide for Device Manager and Provisioning Manager ( in case HP XP) or Hitachi Storage Command Suite Software Server Installation and Configuration Guide for Hitachi Device Manager and Provisioning Manager Q: What is the minimum provider version to get performance statistics? A: Provider version must be High Command Device Manager 5.9 or later. Q: What performance metrics are available? A: Volume, port, and overall array performance metrics. Q: Will disk or controller performance be available? 326 STM

327 A: No. HDS does not plan to support those metrics via smi-s. Q: Is performance supported on all arrays? A: No. Performance is not available on the Lightning series arrays (9900, v). NOTE: The Lightning series is obsolete and replaced by AMS/WMS. Q: How do I enable performance on 9580? A: Perform following steps: 1. Start Storage Navigator 2. Change the operation mode to Management Mode 3. Selected Performance tab from Settings-->Configuration Settings menu. 4. Select the Performance Statistics tab. 5. Check all performance choices Q: What is the difference between Tagma Store and USP? A: Tagma Store is an outdated name, and has since been replaced with USP naming convention. Storage System HDS Models Rebranded HP Models Rebranded SUN Models Lightning 9900 Lightning 9900-V 9910, 9960 XP48, XP V, 9980V XP128, XP1024 USP-V R600, R601 XP20000, XP V USP Thunder 9500-V USP100, USP600, USP1100, NSC V, 9530V, 9570V, 9580V XP10000, XP12000, SVS , 9200L STM 327

328 AMS WMS SMS AMS200, AMS500, AMS1000, AMS2100, AMS2300, AMS2500 WMS100 SMS100 Notes: Midrange arrays: 9200 (thunder) 9500 (thunder) 9900, 9900-v (Lightning obsolete and replaced by AMS, WMS) AMS, WMS (replacement for above 9900 series) Enterprise: USP 100, USP 600, USP 1100, NSC (1st generation arrays) USP-V, USP-VM (2nd generation) Q: What is the command for getting the Hdvm data base and logs dump? A: 1. Go to the High Command installation directory from a command prompt. Example: Windows: C:\Program Files\HiCommand\Base\bin Solaris/Linux: /opt/hicommand/base/bin 2. Run the command below: hcmdsgetlogs /dir <empty-directory-where-to-keep-the-dump> /arc <archive-file-name> Example: hcmdsgetlogs /dir C:\logs_work /arc hicmd_log In this case the dump will be in the directory C:\logs_work. Note: User needs administrator privilege on the system to run this command. Q: How do I change the memory settings for Device Manager? A: Steps to change the memory settings - from "Device Manager Server Installation and Configuration Guide" 328 STM

329 Setting Memory Heap Size When Using CIM/WBEM If CIM/WBEM functions are being used, you might have to increase the memory heap size of the Device Manager server, depending on the conditions. Note: that the required memory heap size differs depending on the CIM client you are using. To change the memory heap size: 1. Use a text editor to open the following file: installation-folder-for-the-device-managerserver\hicommandserver\server.ini 2. Change the value of JVM_XOPT_HEAP_MAX to new-setting-value (units: MB), which is calculated by using the two formulas below: JVM_XOPT_HEAP_MAX = -Xmxnew-setting-valuem calculation-value-for-smi-s-provider = 30,000 x number-of- LDEVs x number-ofpaths-per-ldev / If the value of number-of-paths-per-ldev becomes less than 1, assume that this value is equal to 1 for the calculation. The value of calculation-value-for-smi-s-provider is expressed in megabytes. Round this value up to the nearest whole number. If this value is less than 256 (MB), assume that it is equal to 256 for the calculation: new-setting-value = current-setting-value + calculation-value-for- SMI-S-Provider All of the values in the above formula are expressed in megabytes. The value of new-setting-value obtained from the above formula is the memory heap size required for obtaining the class information that belongs to the bottom layer in a CIM class. When an upper-layer class is specified, some SMI-S clients might obtain information of all the classes below that class at the same time. In this instance, the required capacity will be larger than the value of newsetting-value obtained from this formula. 3. Restart the Device Manager server as follows: a. Select Start, Programs, HiCommand, Device Manager, and then Stop Server. STM 329

330 b. After the Device Manager server has stopped, select Start, Programs, HiCommand, Device Manager, and then Start Server. Q: How do I enable SMI-S on Device Manager if I didn t enable during installation? A: Edit the file Program Files\HiCommand\DeviceManager\HiCommandServer\config and change from server.cim.support=false to server.cim.support=true. Restart HiCommand Device Manager service. Q: How do I enable? A: Perform the following steps: a. Edit C:\ProgramFiles\HiCommand\DeviceManager\HiCommandServe r\config\server.properties b. Edit following line and set server.cim.support to true # whether the server supports CIM interface or not server.cim.support=true Q: How do I Add a Subsystem? A: Perform the following steps: 1. Open HiCommand Device Manager GUI. 2. Click Subsystems. 3. Click Add Subsystem. 330 STM

331 18. Select the Type of subsystem to be added. 19. Type in the IP Address of the Controllers. 20. Click OK. STM 331

332 21. Click OK when asked Are you sure. You should see: 332 STM

333 22. Click Close. HP EVA Provider (Command View) The HP Provider is an installable option with Command View. If it is not selected during install, you can either run the Command View install again from CD (the install will detect that SMI-S was not selected) or Download and install the SMI-S provider from the HP website. Download: Compatibility Matrix: Reference Guides: n&cc=us&taskid=101&prodclassid=- 1&contentType=SupportManual&docIndexId=64180&prodTypeId=18964&prodSe riesid= STM 333

334 Note: The SMI-S provider for HP EVA should not have more than one Storage Manager Proxy Agent polling it. Being the SMI-S provider for HP EVA is single threaded, this will cause latency issues with polling. Windows install: Double click the setup for Command View 8. Select Language. 334 STM

335 Click Next at the introduction screen. Accept the License agreement. Click Next. STM 335

336 Accept the license key agreement. Click Next. Choose Install Set. Check EVA PerfMon and SMI-S Cimom. Click Next. 336 STM

337 Keep in mind the Security Groups Configuration for post installation. Click Next. Note: Post install, follow the steps in the Adding Users to HP Groups section. STM 337

338 Verify the Pre-Installation Summary. Click Install. You will be presented with the following during the install. 338 STM

339 Click Done. STM 339

340 Adding Users to HP Groups The following section details how to add users to HP groups.. Right click My Computer. 1. Click Manage. 340 STM

341 2. Click Local users and Groups. 3. Click Groups. 4. Double Click HP Storage Admins. STM 341

342 5. Click Add. Enter the names to be added. 6. Click OK. 7. Click OK. This will return you to the Computer Management screen. Double click HP Storage Users. Follow the steps for adding the same user to the HP Storage Users group. HP LeftHand Enabling SNMP Note: This information is provided as-is as a reference for our customers. SolarWinds provides no guarantees as to the accuracy of this information as the software is built and distributed by 3rd party vendors who may make changes at any time. SolarWinds does not provide official support for problems related to vendor s SMI-S Providers, but customers can seek support via Thwack. Our product team and other knowledgeable customers regularly use these forums and may be able to assist you. This section details enabling SNMP polling on the management nodes from the poller agent assigned to poll LeftHand devices. Once enabled, the SNMP data will appear within the LeftHand device console screen. Centralized Management Console (CMC) structure To begin you need to drill down in the cluster to locate a management node. 342 STM

343 Finding a Management Node To find a management node for a specific cluster 1. Click on the node and check the Status on the Details tab. 2. If the status reads Manager Normal then it is a management node. STM 343

344 Enabling SNMP: You need to have SNMP enabled and also allow the respective Storage Manager Proxy Agent to access the information. After adding permissions to one node you will then need to copy these permissions to the rest of the nodes. To check if SNMP is enabled: 1. Click the SNMP icon below one of the nodes. 2. Check that Agent Status is enabled on the SNMP General tab. 3. If SNMP is not enabled, Edit SNMP Settings below will include how to enable it. To Find Community String: 1. Click the SNMP icon below one of the nodes. 2. Check the Community String, if it is different than public make sure this is reflected within Storage Manager. 3. If the Community String needs to be changed see Edit SNMP Settings below for steps. 344 STM

345 Note: Community Strings are CASE sensitive and need to reflect their case sensitivity in Storage Manager as well. To check if Storage Manager Proxy Agent is in Access Control list: Check the Access Control list and see if the Storage Manager Proxy Agent s IP address is in the list. If not, it will need to be added. To do so, see Edit SNMP Settings below. Edit SNMP Settings: Near the bottom of the CMC screen there is a SNMP General Tasks drop down. From here click Edit SNMP Settings... From this page you can set SNMP to enabled, change the Community String and add the Storage Manager Proxy Agent to the Access Control list. STM 345

346 Add the Storage Manager Proxy Agent IP to Access Control list: From the Edit SNMP Settings page, click Add. This will bring you to the Add SNMP Client page. From here, click the By Address radio button and add the IP address of the Storage Manager Proxy Agent and then click OK 346 STM

347 The Storage Manager Proxy Agent IP should now be in the Access Control list. The last step is to copy these SNMP settings to the rest of the nodes within the cluster. To do this return back to the node page. From the Node page you can click on the Storage Node Tasks drop down at the bottom of the page and select Copy Configuration... This will bring up the Copy Configuration box, and from here you can select the SNMP Settings and select the nodes you want to copy the configuration to by checking the checkbox for SNMP Settings (General, Traps) and by selecting the nodes you wish to copy the selected configuration to. STM 347

348 Once you click copy the configuration is copied to all the nodes selected. You should now see the Storage Manager Proxy Agent IP in each node's Access Control list. Management Group Servers Cluster Node SNMP Settings HP XP Note: This information is provided as-is as a reference for our customers. SolarWinds provides no guarantees as to the accuracy of this information as the software is built and distributed by 3rd party vendors who may make changes at any time. SolarWinds does not provide official support for problems related to vendor s SMI-S Providers, but customers can seek support via Thwack. Our product team and other knowledgeable customers regularly use these forums and may be able to assist you. For information on configuring HP XP, please click the following link: pdf. 348 STM

349 IBM DS 6000, 8000 or ESS Provider Note: This information is provided as-is as a reference for our customers. SolarWinds provides no guarantees as to the accuracy of this information as the software is built and distributed by 3rd party vendors who may make changes at any time. SolarWinds does not provide official support for problems related to vendor s SMI-S Providers, but customers can seek support via Thwack. Our product team and other knowledgeable customers regularly use these forums and may be able to assist you. The following section details installation links to versions of IBM providers. The correct IBM Provider to install is based on Model and Firmware. Notes: For any DS 6000, 8000 or ESS, install the IBM Provider. For any DS 3k, 4k, or 5k array, install the LSI Provider Compatibility Matrix: 1.ibm.com/support/docview.wss?rs=1118&context=STC4NKB&dc=DB500&u id=ssg1s &loc=en_us&cs=utf-8&lang=en Note: The Bundle and LIC are firmware versions for the array. The compatibility matrix shows the minimum and maximum for the specific arrays and their providers. IBM Provider Download: ibm.com/support/entry/portal/Downloads/Hardware/System_Storage/ Storage_software/Other_software_products/CIM_Agent_for_DS_Open_( API)/ IBM CIM Agent: 01.ibm.com/support/docview.wss?rs=1118&context=STC4NKB&dc=DB500&uid= ssg1s &loc=en_us&cs=utf-8&lang=en IBM Provider FAQ: 01.ibm.com/support/docview.wss?rs=1118&context=STC4NKB&dc=DB500&uid= ssg1s &loc=en_us&cs=utf-8&lang=en Install guides: Search results link showing all documents for DS Open API STM 349

350 1.ibm.com/support/search.wss?rs=1118&tc=STC4NKB&dc=DA400+DB300+DA1 00+DA110+DA120+DB100+DA700+DA450+DA300&dtm DS Open Application Programming Interface and Installation and Reference 01.ibm.com/support/docview.wss?rs=1118&context=STC4NKB&dc=DA400&uid= ssg1s &loc=en_us&cs=utf-8&lang=en Troubleshooting IBM The following section details FAQs for the IBM SMI-S Provider. Q: Is IBM Shark supported? A: Yes. Add it as an IBM DS 6K/8K Series device Q: What is the default username/password for the IBM provider? A: superuser / passw0rd Q: What is service name for the IBM provider in windows? A: IBM System Storage CIM Agent for DS Open API x.y Pegasus Server, where x.y is the version. Q: Where are the logs located? A: <install path>\logs <install path>\pegasus\log <install path>\pegasus\logs Q: How do I add an array to the provider? A: <install path>\bin\dscimcli mkdev <ip> -type <ds ess> -user <username> - password <password> Example: dscimcli mkdev type ds -user superuser - password passw0rd Note: the user and password combination are that of the Control Station Q: How do I remove an array from the provider? 350 STM

351 A: <install path>\bin\dscimcli rmdev <ip> -type <ds ess> Example: dscimcli rmdev type ds Q: I try to add an array, but it fails with error Array is already added? A: The password for the Control Station user may be expired, which can be verified in the <install path>\pegasus\log\providerdebug.log. If expired, the password can be reset in the Control Station. Q: Where can I find more usage details on the dscimcli command? A: Follow the link above for Reference Install guides. There are install/ref guides for 5.2, 5.3, 5.4 versions of the provider Q: What user/password do I use when configuring the array in Storage Manager (in the monkey wrench page)? A: Use the default username/password (superuser/passw0rd). Other user-ids/passwords can be created using the dscimcli command. You can list what users are configured by doing lsuser Q: What username/password do I use when adding array to the provider? A: The username/password used for the Control Station (similar to how there is username/password to Unisphere). The user should know this information Q: In what release did the CIM Agent become embedded in the HMC (Hardware Management Console)? A: Starting with Release 2.4 (Bundle ) of the DS8000, the CIM agent was embedded into the HMC. Up to Release 4 (Bundle ) by default, it comes disabled Q: How does the embedded CIM Agent get Enabled? A: In order to use the CIM agent, the customer must contact IBM support to have the CIM agent enabled. Q: How does the embedded CIM Agent get configured? A: The Customer must download the dscimcli tool and install it on a separate server, i.e. the TPC server or laptop, to configure the CIM agent. dscimcli is a small utility that runs on the same platforms that the proxy CIM agent runs on, but does not consume a lot of CPU or memory, so it should be able to run on any reasonable server or laptop. You can download the dscimcli tool at the download site for the version of CIM agent that is running on the HMC. Please refer to the install documentation for more details. STM 351

352 Install Document Link: 01.ibm.com/support/docview.wss?uid=ssg1S &aid=1 Q: How do I enable the embedded CIM agent on the HMC? A: For releases prior to DS8000 release 4.1, the CIM agent is NOT automatically enabled. You must enable the CIM agent on the HMC before you can use it. For DS8000 release 4.1 and later, the CIM agent is enabled by default. You do not have to enable the CIM agent unless it has been disabled. Note: Enabling DS8000 CIM Agent on DS8000 bundles , , , and requires assistance from IBM Technical Support. Perform the following steps to enable the HMC CIM agent: 1. From the HMC Welcome page, click HMC Management. The HMC Management window is displayed. 2. Click Start/Stop CIM Agent. The HMC CIM Agent window is displayed with the current state of the CIM agent. 3. Select Start CIM Agent and click Apply. The CIM agent is started and the state is updated. Q: How do I configure the embedded CIM agent for HMC? A: For DS8000 release 4.0 and earlier, the CIM agent administrator and storage administrator are required to create and maintain user passwords for both the CIM agent and the DS8000 management applications. For DS8000 release 4.1 and later, the embedded CIM agent does not require configuration changes to manage DS8000 devices. The DS8000 device user names and passwords are used to authenticate CIM client requests. The DS8000 administrator must create user names and passwords that CIM clients can use to attach to the CIM agent. Each user that is created must be in the administrator group. Users that are created in any group other than the administrator group cannot function with DS8000 release 4.1 and 4.2 CIM agents. The DS8000 administrator can use the DSCLI or the HMC console GUI to create the user names and passwords Q: How do I verify the CIM agent connection to the HMC outside of Storage Manager? A: You must verify that the CIM agent software connects to the storage unit that you identified during configuration by issuing the following commands: dscimcli -s -u <DS8000user> -p <DS8000password> lsdev STM

353 <hmc ip> is the IP address of the HMC, <DS8000user> is the user name that is used to log into the DS8000 Storage Manager, and <DS8000password> is the password that is used to log into the DS8000 Storage Manager. Q: How do I setup Storage Manager to connect to the embedded HMC CIM agent? A: Storage Manager should be configured with the same ports and credentials that were used to verify the HMC connection with the dscimcli: HTTP Port: This is the typical default port HTTPS Port: This is the typical default port Provider IP: Use the HMC IP Address Username An administrator user, preferably the one used to verify the connection to the CIM agent Password The corresponding password to the user with administrator privileges used to connect to the CIM agent. Identifier Example: ibm z This can be found in the Storage Manager SMI-S logs or by using the Confirm Provider button in the Array configuration page of Storage Manager. IBM SVC, V7000 Provider Note: This information is provided as-is as a reference for our customers. SolarWinds provides no guarantees as to the accuracy of this information as the software is built and distributed by 3rd party vendors who may make changes at any time. SolarWinds does not provide official support for problems related to vendor s SMI-S Providers, but customers can seek support via Thwack. Our product team and other knowledgeable customers regularly use these forums and may be able to assist you. The IBM SAN Volume Controller (SVC) SMI Provider is embedded in the Management Console software. Note: Older versions of SVC have another CIMOM embedded on the Management Console which is named as the proxy provider. IBM recommends not using this proxy CIMOM due to various performance considerations. Storage Manager must use the CIMOM on the cluster. All SVC's are sold with a Management Console in the rack on which the SVC GUI is installed to run the proxy server along with a number of other management tools. The Management Console itself is a CIM Client. SVC CIM Agent Support Matrix: 1.ibm.com/support/docview.wss?rs=591&uid=ssg1S #_SVC_and_SVC STM 353

354 a. The user can stop it and run it once again, and the profile the user has just created will be selected, then check the default profile check box that will make it a default profile. b. If the MAPI Profile is created successfully, then the executable will continue to run and output mailbox information to the command line. c. Wait for a few seconds to make sure it is collecting data, then the press Ctrl-C to stop the exe. d. Next, start the agent. SVC (SAN Volume Controller) CIM Agent Information: SVC CIM Agent Support Matrix: 1.ibm.com/support/docview.wss?rs=591&uid=ssg1S #_SVC_and_SVC Troubleshooting IBM SVC Provider Q: What is the minimum version of the provider supported? A: Minimum version supported is Q: What is the default login and password the cim agent on the cluster? A: Login is either administrator or superuser Password is either passw0rd or l0destone Q: What is the default port used by the cim agent? A: By default the install uses HTTPS. If the user doesn't remember the ports/protocol used at install, the install directory contains a config file which will tell you: svcconsole\cimom\pegasus\cimserver_current.conf. Q: Is it possible to upgrade the provider part alone? 354 STM

355 A: No. The CIMOM is a core part of the SVC Console so you have to upgrade it as a part of your Console upgrade. The supported upgrade path is that you can run an SVC Console one rev up of the cluster code for migration purposes only. So you can upgrade the SVC Console to one rev up in order to upgrade the cluster, but IBM doesn't support long term management of mismatched SVC Console to Cluster versions. SVC upgrade for cluster and console is a customer capable task; however, they should contact their IBM support representative to make sure they won't hit any of the known issues. Q: For SVC or above, provider exists on the cluster as well as on the host. Which one do I use? A: From release and above, there are multiple CIMOMs available; a) embedded CIMOMs in each cluster b) CIMOM on the management console (on the host where the SAN Volume Controller Console is running). Use the CIMOM on the cluster. There are chances that the use of CIMOM on the management console slows down the SVC GUI operations. CIMOM on the cluster gives better performance than the other since it is embedded in the cluster itself. Q: How do I find the IP for cluster? A: a. From the SVC GUI. b. From TestProvider utility or from Confirm Provider in the Storage Manager GUI config page(only from Storage Manager version or greater) c. Connect to the CIMOM on the management Console. d. Enumerate CIM_ComputerSystem class. IP of the cluster is part of the identifier for the cluster instance. Q: How do I monitor multiple clusters? A: Each cluster has to be configured in Storage Manager as a SVC device with the correct CIMOM IP and identifier. STM 355

356 IBM XIV Provider Note: This information is provided as-is as a reference for our customers. SolarWinds provides no guarantees as to the accuracy of this information as the software is built and distributed by 3rd party vendors who may make changes at any time. SolarWinds does not provide official support for problems related to vendor s SMI-S Providers, but customers can seek support via Thwack. Our product team and other knowledgeable customers regularly use these forums and may be able to assist you. Namespace The namespace used by the XIV provider is /root/ibm. Configuring XIV in Storage Manager CIM Agent is enabled by default. There is no option to start or stop it. Port: XIV uses Secure port 5989 by default. Provider IP: IP address of the administrative module. You can use any administrative module if more than management nodes exist. Credentials Version and above use the XIV system user name and password. Users created in technicians group may not have sufficient privileges to get all data. Version requires a SMI-S agent user to be created. This can be done from XIV CLI interface. o Command: smis_add_user user=<username> password=<password> password_verify=<password> Version 11.0 and above does not use the smis_add_user command. There is no separate SMIS access control. Any read-only user can access the SMI_S provider. Troubleshooting IBM XIV Q: Is there a way to manually start/stop the provider? A: There are no options to start or stop the provider process through the XCLI or IBM XIV Storage System GUI. The Provider is running by default and monitored by a watchdog process. Q. What is the minimum supported version? 356 STM

357 A. IBM XIV has two versions of hardware active in the field, Gen2 and Gen3. They both have minimum required versions to work with Storage Manager because of memory leaks on the CIM server side (IBM-side) that have been fixed. For Gen 2, firmware version e-5 is recommended f is also applicable, but will not be placed in general availability at any point so the e version is a better recommendation. For Gen3, firmware version or higher is recommended. Note: Storage Manager version 5.7 will enable performance collection by default for all XIV arrays regardless of firmware version. Q: What is the default port used by the CIM agent? A: By default the CIM agent uses HTTPS on port Q: What is the user name/password for the XIV provider? A: XIV system user name and password. Minimum privilege required is ReadOnly ( category = readonly ). Q: How do I collect diagnostic files from XIV? A: CIM Agent log files are located in /local/cim/log folder. You can manually logon to xiv to collect them. They can also collected by running XCLI command system_logs_collect Note: Users that are created in the 'technicians' user group' may not have sufficient privileges to get the data. NetApp E-Series LSI Provider Notes: This information is provided as-is as a reference for our customers. SolarWinds provides no guarantees as to the accuracy of this information as the software is built and distributed by 3rd party vendors who may make changes at any time. SolarWinds does not provide official support for problems related to vendor s SMI-S Providers, but customers can seek support via Thwack. Our product team and other knowledgeable customers regularly use these forums and may be able to assist you. NetApp acquired LSI and their arrays are now referred to as E-Series. If you are working with Eagle 5.0 or 5.1 providers and firmware at version or higher, you can claim E-Series support. STM 357

358 The following is covered in this section: Before you begin Registering with NetApp Downloading a LSI Provider Installing the Provider (Eagle2) in Windows or Linux Adding a SAN (Eagle 2) in Windows or Linux Installing a Legacy Provider (Pre-Eagle 2) in Windows or Linux Adding a SAN (Pre-Eagle 2) in Windows or Linux Troubleshooting LSI Provider Eagle 2 Troubleshooting LSI Provider (Pre-Eagle 2) CIMWorkshop SANtricity Storage Manager Common Array Manager 358 STM

359 Before you begin Before you configure the LSI provider, obtain the following pieces of information about your array. Controller IP Addresses Array/Storage Subsystem Identifier: WWN Note: For information on how to obtain the WWN, see Obtaining Array Identifier NetApp user account. See Registering with NetApp below. Registering with NetApp NetApp requires registration and logon before you can access and download the provider. NetApp provides guest access so you do not have to be a NetApp customer. NetApp registration link: Notes: If you do not want to register as a NetApp customer, choose the Guest option in Step 2. Serial # is not required. Downloading a LSI Provider The download links are located on the NetApp support site. You will need an account to access the download link. See Registering with NetApp for more information. Provider (Eagle 5) downloads are located at: After logging in to the site, click the SMI-S Providers download link. STM 359

360 Installing the Provider (Eagle 2) in Windows or Linux The following section details the steps for installing LSI on a windows server for the Eagle 2 Legacy version. Installation for Windows: 1. Double click the installer. 360 STM

361 2. Click Next at the Introduction screen. STM 361

362 3. Accept the License Agreement, Click Next. 362 STM

363 4. Click Install. 5. Add the IP addresses for the Array Controllers. Save and close Notepad. STM 363

364 6. Click Finish at the Install Complete screen. 364 STM

365 Installation for Linux: The following section details the installation steps on a Linux server. 1. Untar the lsi_array_xx.xx.xx.xx.tar file. 2. Execute rpm -i lsi_array_xx.xx.xx.xx.rpm. Adding a SAN (Eagle 2) in Windows or Linux These following steps are taken for the arrays added during installation. Installation on Windows: 1. Run the ArrayManagementUtility.exe that came with the SMI-S installation file. 2. Use the IP where the SMI-S provider is installed. 3. Use the defaults for the CIMOM Username, Password, and Port. 4. Type 1 for Add Array. 5. Type the array IP or DNS name. STM 365

366 6. Type n to not set the storage array password. Installing on Linux 1. Edit the /opt/lsi/sbma/data/arrayhosts.txt file. 2. Enter the IP address of each array, one per line. 3. Stop the cimserver with /opt/lsi/pegasus/bin/cimserver-s 4. Start the cimserver with /opt/lsi/pegasus/bin/cimserver start Installing a Legacy Provider (Pre-Eagle 2) in Windows or Linux The following section details the installation on windows devices for pre-eagle 2 providers. Installation on Windows: 366 STM

367 1. Double click the installer. 2. You should see a status bar. STM 367

368 3. Click Next at the Introduction screen. 368 STM

369 4. Accept the License Agreement, Click Next. STM 369

370 5. Choose the Install location, Click Next. 6. Click Install at the Pre-Installation Summary screen if the summary is correct. 7. You should see the following screenshot: 370 STM

371 STM 371

372 8. Add the IP addresses for the Array Controllers. Click OK. 372 STM

373 9. Click Done at the Install Complete screen. STM 373

374 Installation on Linux: 1. Untar the Linux_Installer_xx.xx.xx.xx.tar file. 2. Execute the install executable. 374 STM

375 Adding a SAN (Pre-Eagle 2) in Windows, Linux The following section details the installation steps for adding SANs from windows and Linux devices. Windows: 1. Run the <install directory>\smi_sprovider\bin\providerutil.bat script. 2. Use the defaults for the CIMOM Username, Password, and Port. 3. Type 1 for adddevice. 4. Type the array IP or DNS name. 5. Type the Array Password. Linux: 1. Run the /usr/engenio/smi_sprovider/bin/providerutil script. 2. Type the default username, password and Port. Note: username - must be a valid user on the local system. 3. Type add for adding a device. 4. Type the IP or DNS name. STM 375

376 5. Type the array password. Troubleshooting LSI Provider Eagle 2 Q: What is the default username/password? A: admin/admin Q: What is the default namespace? A: /root/lsiarray13 Q: Where are the log files located? A: To enable logging, do the following: Note: Changes to the tracing level requires a restart of the provider to take effect. 1. Go to the directory where SMI-S Provider is stored: For a Windows operating system, the directory is C:\LSI\. For a UNIX-based operating system, the directory is /opt/lsi/sbma/data/. 376 STM

377 2. Edit the providertracelog.properties file. Remove the pound sign (#) from the lines containing FILE, LEVEL, and EVENTS. 3. Save the file, and exit the text editor. 4. Stop and start the CIM server by using the specific location and name. Q: How do I change the ports that the provider binds to? A: 1. Go to the <installpath>\bin directory. For a Windows operating system, the directory is c:\lsi\pegasus28\pegasus\bin For a UNIX-based operating system, the directory is /opt/pegasus28/pegasus/bin/ 2. Run the following commands: cimconfig s httpport=<newhttpport> -p cimconfig s httpsport=<newhttpsport> -p Q: I keep getting a Storage array added successfully, but instead of returning the UUID, it returns a index string out of bounds. A: Double check the IP address. This is the provider s way of saying, this host is pingable, but it s not a storage array. Q: Array does not appear to be added to the provider when editing the arrayhosts.txt file, what should I do? A: See section above Adding a SAN under the Provider Version Eagle 2 and above section. Troubleshooting LSI Legacy Provider (Pre-Eagle 2) Q: What are the ports that LSI provider listens on? A: 5988, 5989 and The port 2463 is used to set RPC sessions to the storage controller. Q: How do I change the port the provider listens on? STM 377

378 A: On the machine running the Provider do the following: 1. Open the portinfo.properties located (by default): C:\Program Files\EngenioProvider\SMI_SProvider\bin. 2. Change the entry CIM-XML=5988 to the desired port which has no conflicts. 3. Save the changes. 4. Restart the Engenio SMI-S Provider Server service. Q: How do I enable logging for debugging the provider, and where is the log located? A: To enable logging, do the following: Note: Changes to the tracing level requires a restart of the provider to take effect. The SMISProvider.log file is created if you have debug tracing enabled. The file could be located in any of the following locations: \Program Files\EngenioProvider\SMI_SProvider\bin\ \Windows\System32\ \EngenioProvider\SMI_SProvider\bin\ If you are not able to find the SMISProvider.log file then perform the following to enable debug tracing and duplicate the issue so the SMISProvider.log file is created: 1. Stop the Provider 2. Edit the providertracelog.properties file located in [Installation Drive]\Program Files\EngenioProvider\SMI_SProvider\bin\ 3. Remove the # symbol from the last line of the code, which looks like: #log4j.logger.providerlog=debug, File 4. The line of code should now look like: log4j.logger.providerlog=debug, File 5. Save the file 6. Restart the Provider 378 STM

379 On UNIX: the trace log is in the {install location}/smi_sprovider/bin directory. Q: Why, on a minute by minute basis, am I seeing some perf stats as 0.0? A: Because LSI only polls their arrays on a 10 minute basis. It is too taxing on the array to gather more frequently than that. Q: How many arrays can be monitored at one time? A: LSI recommends no more than 4 arrays at once. The following is an excerpt from their release notes: The maximum configuration recommended for the SMI provider is either 3 storage systems or a total of 512 volumes, whichever is reached first. If the limits are exceeded, the provider may not be able to generate performance statistics. Q: What performance information is available from the LSI array and how is it obtained? A: Array Performance: smi-s Controller Performance: calculated by Storage Manager. Aggregate the performance values for all the LUNs that belong to specific controller. LUN Performance: smi-s Disk Performance: API. Currently using the Crystal (10.10) version API. In order to ascertain disk performance from an array, the controller firmware minimum version must also be Crystal release (7.10). The version of the API was built against jdk 1.4, which matches with the jdk used in the Storage Manager agent at the time of the 4.8 release. The (Crystal maintenance) and (Emerald) release was compiled against jdk 1.5, and is the reason it is not used. Volume Group Performance: calculated by Storage Manager. Aggregate the performance values for all the LUNs that belong to specific raid group. Q: Why is disk performance not showing up? A: The controller firmware must be version 7.10 or greater. We use the API to gather the data, and there is a dependency on the controller firmware to be greater than A trap is sent to Storage Manager if the minimum version is not met. STM 379

380 You might hear the controller versions referred to by name, which are: o o o o o - Chromium (no disk perf avail, only in this list to show firmware name) - Crystal - Crystal maintenance - Emerald (which is the xbb2) - Crystal/Emerald 4Q08 Maintenance o - Aurora (2009) o Allegheny (2009) o - Flint (2009) Q: Is any configuration required to get disk performance to show up? A: No configuration required on the agent nor from Storage Manager gui. The disk performance uses LSI s API (symsdk.jar) in conjunction with the smi-s provider to ascertain the disk performance. The API requires the IP addresses of the controllers. The IP addresses are obtained from the smi-s provider; therefore, you must have the smi-s settings configured correctly. Q: How do I get the LSI provider to work on Solaris? A: For Solaris 10, you will probably need to change the port the lsi provider listens on, as solaris 10 ships w/ a cimom enabled by default that is already bound to For solaris 10 do the following: 1. Install provider following instructions 2. Stop the provider (/opt/engenio/smi_sprovider/bin/launch stop) 3. Change the ports in /opt/engenio/smi_sprovider/bin/portinfo.properties to something other than 5988 and CIM-XML is listed twice, so be sure to change both 4. Check that slp is running (ps eaf grep slp) a. should see /usr/java/jre/bin/java -Xmx128m -classpath /usr/share/lib/slp/slpd.jar 380 STM

381 b. can also check the slp port is bound to by doing netstat an grep 427. Should see port 427 in a listen state 5. Start slp if not running (/etc/init.d/slpd start) Note: slp requires that the /etc/inet/slp.conf file exists. If the file does not exist, then copy the slp.conf.example file (cp /etc/inet/slp.conf.example /etc/inet/slp.conf) 6. Start the provider (/opt/engenio/smi_sprovider/bin/launch start) For solaris 8 or 9, there should be no need to change provider ports. No cimmon should be running on port Users should still verify the port is not in use by using netstat command netstat an grep Q: Provider still doesn t work on Solaris, what logs can I look at? A: You can edit the /opt/engenio/smi_sprovider/bin/launch script and change the PROVIDER_OUT=/dev/null to PROVIDER_OUT=$PROVIDER_HOME/SMI_SProvider/bin/provider_launch.log You can then view the provider_launch.log and SMISProvider.log (found in /opt/engenio/smi_sprovider/bin) to further diagnose issue PROVIDER_OUT=$PROVIDER_HOME/SMI_SProvider/bin/provider_launch.log Q: What is the default username/password for provider running on Solaris? A: You must use a valid username/password that is used to login to the system Q: How do I add an array to the provider on Solaris? A: Run /opt/engenio/smi_sprovider/bin/providerutil You must provide ip address of the controller, and also a valid username/password that is used to login to the system Q: Can you use the Windows installer on a 64-bit Windows OS? A: No. According to the LSI Representative, this will be supported in the next generation of the provider (information is as of 2/6/2009) Q: How do I obtain the Support Bundle Data from LSI array? A: To obtain the Support Bundle Data from Santricity/Storage Manager: a. From the array management window (AMW), select the Advance drop down menu STM 381

382 b. Choose Troubleshooting and then Collect All Support Data. c. From this screen, specify the location to save. d. Click Start Q: What files are needed to send a bug to LSI? A: Any issues related to LSI provider, get the following: Provider logs (See How do I enable logging for debugging the provider, and where is the log located for log file location) ArrayHosts.txt (located in C:\Program Files\EngenioProvider) Support Data (See question How do I obtain the Support Bundle Data from LSI array ) LSI provider version info CIMWorkshop The LSI Provider has CIMWorkshop enabled, located: C:\Program Files\EngenioProvider\wbemservices (by default). Refer to Tools > CIMWorkshop for instructions on how to obtain the Array Identifier in CIMWorkshop. SANtricity Storage Manager 1. Log into SANtricity. 382 STM

383 2. Double click on the Storage Array name (You should be taken to the Logical / Physical View, like below). 3. Right Click on the Storage Array name. Select View > Profile. STM 383

384 4. Scroll down to Storage array worldwide name (ID) under Summary for All tab. Common Array Manager 1. Login to Common Array Manager and click on the Administration Licensing section and note down the Array WWN as shown below 384 STM

385 2. Remove the colons for providing the identifier within Storage Manager as shown below STM 385

386 OS Embedded Provider Note: This information is provided as-is as a reference for our customers. SolarWinds provides no guarantees as to the accuracy of this information as the software is built and distributed by 3rd party vendors who may make changes at any time. SolarWinds does not provide official support for problems related to vendor s SMI-S Providers, but customers can seek support via Thwack. Our product team and other knowledgeable customers regularly use these forums and may be able to assist you. Some of the OS platforms come with a cimom already installed, running, and bound to the default ports of 5988 and This section is used to describe those providers and possible ways to work around them. Solaris Q: What is the default cimom service on Solaris? A: For Solaris 9 and 10, /etc/init.d/init.wbem launches the scm (Solaris Management Console), which is a bootloader for the embedded cimom smcboot (/usr/sadm/lib/smc/bin/smcboot) Q: How do I start/stop the smcboot cimom service? A: Solaris changed the default way services can be started/stopped in Solaris 10 (via service management facility: smf). SMF avail in Solaris 9, but became default way to handle services in Solaris 10. Below are couple methods to start/stop service using smf and not using smf. To start: 1. /etc/init.d/init.wbem start 2. svcadm enable svc:/application/management/wbem To stop: 1. /etc/init.d/init.wbem stop 2. svcadm disable svc:/application/management/wbem Note: other useful smf commands: ( List all services svcs a Check status of service 386 STM

387 svcs -l <service name> example: svcs l svc:/application/management/wbem List properties of service svccfg -s <service> then at the <service name> prompt: listprop example: svcfg s svc:/application/management/wbem svc:/application/management/wbem> listprop Q: I see port 5988/5989 is bound to, but smcboot is not running, how do I determine the process that is bound to those ports? A: Copy/paste following script to new file on system. Script from unknown source#!/bin/ksh line=' ' pids=$(/usr/bin/ps -ef sed 1d awk '{print $2}') if [ $# -eq 0 ]; then read ans?"enter port you would like to know pid for: " else ans=$1 fi for f in $pids do /usr/proc/bin/pfiles $f 2>/dev/null /usr/xpg4/bin/grep -q "port: $ans" if [ $? -eq 0 ]; then echo $line echo "Port: $ans is being used by PID:\c" /usr/bin/ps -ef -o pid -o args egrep -v "grep pfiles" grep $f fi done exit 0 STM 387

388 Pillar Provider Note: This information is provided as-is as a reference for our customers. SolarWinds provides no guarantees as to the accuracy of this information as the software is built and distributed by 3rd party vendors who may make changes at any time. SolarWinds does not provide official support for problems related to vendor s SMI-S Providers, but customers can seek support via Thwack. Our product team and other knowledgeable customers regularly use these forums and may be able to assist you. The Pillar SMI provider is embedded in the array itself, so there is nothing a customer needs to do to install it. If a customer is running an older Pillar Axiom system that has the 512Meg Pilot hardware, the provider is by default disabled. Provider is enabled by default on systems with 2 Gig Pilots. Pillar doesn t recommend enabling the SMI provider if the customer has the older 512 Meg Pilots and recommends that they have it upgraded to the 2 Gig versions. Customers can contact Pillar s customer support to have their systems upgraded to the 2 Gig Pilots. The provider uses the same username/passwords that the customer has set up for their Axiom systems. Standard SLP discovery mechanism is used. The interop namespace for the provider is /root/pg_interop, and the namespace is /root/pillar. Upgrades for the provider are bundled with system software upgrades. Currently Pillar is SMI 1.1 certified with the 2.3 Axiom software release. Troubleshooting Pillar The following section list FAQs for troubleshooting a Pillar provider. Q: Since provider is embedded in the controller, is there a way to manually start/stop the provider? If so, how? A: You can restart the provider two different ways (force a Pilot failover, or issue disable/enable startup command for smi provider) both of which require that the Support Tool be licensed and the supporttool software be locally installed. You can get a list of the support tool commands with supporttool.exe help listrequests > requests.txt For a quick syntax of any command, use supporttool.exe template d [command name] Restart smi provider using one of two avail methods 388 STM

389 Using Support Tool to force a Pilot Failover. This is completely non-disruptive to the data path, it issues a Linux reboot to the active Pilot, which does a failover to the passive, and in the process starts the web service and SMI-S Provider service on the standby pilot. Warning:Do not do this if there is a storage resource modifying task in progress. $ supporttool.exe sub -u pillar -p a1s2d3f$ -H [your pilot hostname or shared IP] ForcePilotFailure You should get a response that looks like this: Header ProtocolVersion: 0.1 SessionKey: 7cc aac74cda7d19a1d3f250fc Time: T15:40:50-07:00 ClientData: supporttool RequestStatus: Succeeded FAQ Error List ForcePilotFailureResponse Within a minute or two, you should be able to get back into the GUI as the standby pilot begins coming up. Using Support Tool to disable/enable the provider suporttool.exe PerformDisableSMIStartup supporttool.exe PerformEnableSMIStartup Q: Are there log files for the provider? If so, where are they located? A: They are located on the pilot (if you can ssh to it) under /var/log. They can be obtained via "Collect System Information" under the "Support" tab. The tar you download will have the cimserver logs. Q: When encountering smi-s issues, what information should we collect from customer s environment? A: The System information logs. See above on how to obtain logs STM 389

390 Q: Where can one find exact array model info? A: On the GUI, the System -> Summary page will provide you with the Model Number as AX300 or AX500 etc. Q: When getting version of the smi-s, is that the slammer, pilo, or brick version when going to Axiom One web gui under support? A: Pilot OS is the version to use. For example, if you're asked to be on version 3.3, it should show up as XX Q: What's the minimum version of the provider we should attempt to ascertain data from? A: Q: Is performance information available? If so, what metrics? A: Yes. Only LUN performance is available as of the Pilot release Note: Per from Shaq from Pillar on 09/14/09: For the statistics - we're probably going to be limited to LUN and file system statistics for the near future. We have plans to incorporate the remaining statistics in the release 5.x timeframe but that is a ways off Q: What Pillar licenses are required to collect valid set of smi-s data? A: At a minimum need either Fibre Channel Protocol or iscsi Protocol Q: What is the default username and password for AxiomONE Storage Services Manager web gui? A: administrator / pillar - for admin level privileges pillar / a1s2d3f$ - for support level privileges Q: What license are available for the Pillar array? A: Licensed Features: 1MB Stripe CIFS Clone FS Clone LUN Fibre Channel Protocol NDMP 390 STM

391 NFS Pilot SSH Access [for support use] Pooled RAID10 SNMP SecureWORMfs Snap FS Support Tool [for support use] Thin Provisioning: FS Thin Provisioning: LUN Virtual Tape Library Volume Backup Volume Copy and Backup iscsi Protocol Sun StorageTEK 99xxSeries Provider Note: This information is provided as-is as a reference for our customers. SolarWinds provides no guarantees as to the accuracy of this information as the software is built and distributed by 3rd party vendors who may make changes at any time. SolarWinds does not provide official support for problems related to vendor s SMI-S Providers, but customers can seek support via Thwack. Our product team and other knowledgeable customers regularly use these forums and may be able to assist you. Sun/StorageTek 99xx Series can be monitored from any OS agent by polling a HDS SMI-S Provider, typically the HiCommand Device Manager. For more information refer to the Hitachi Data Systems (HDS) Provider section. Sun StorageTEK 2K, 6K & FLX Provider Note: This information is provided as-is as a reference for our customers. SolarWinds provides no guarantees as to the accuracy of this information as the software is built and distributed by 3rd party vendors who may make changes at any time. SolarWinds does not provide official support for problems related to vendor s SMI-S Providers, but customers can seek support via Thwack. Our product team and other knowledgeable customers regularly use these forums and may be able to assist you. The Sun Storage Tek 2K, 6K and FLX Series providers use the NetApp E-Series LSI Provider. For more information see the Provider section. Note: NetApp acquired LSI and their arrays are now referred to as E-Series. If you are working with Eagle 5.0 or 5.1 providers and firmware at version or higher, you can claim E-Series support. STM 391

392 Other SMI-S Provider Tools The following tools can be used to log into a Provider to view information regarding the arrays. This section covers how to test a provider. There is a special EMC test provider tool. CIMWorkshop Download: Installation: 1. Unzip the wbemservices bin.zip 2. Open the wbemservices 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 variable Example: set JAVA_HOME=C:\Progra~1\Java\jre Obtaining Array Identifier 1. Run the cimworkshop.bat. 2. Enter the Host URL, User Name, and Password for the Array. Host URL Example: 392 STM

393 If you wanted to connect to the namespace root/cimv2 on the host named crawfish using http on port 5988, you would specify the host as: 3. Click OK. You will be taken to screen below: 4. Click the Magnifying Glass looking icon or Action > Find Class. Search for cim_computersystem. STM 393

394 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 the instance containing _StorageSystem like below. 394 STM

395 EMC TestSMI provider Installation Follow the instructions in the EMC Provider > Installation section on where to download and how to install this utility. Obtaining Array Identifier 1. Log into the remote Array using the Host, Connection Type, Port, Username and Password. STM 395

396 2. Type ens to get 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 the default namespace for that array. 4. Type ein to enumerate instance names. Note: This will give us a list of all of the instances for a particular class. 5. Type cim_computersystem for the list of Arrays the Provider is monitoring. Note: In this particular example, there is only one instance, so it is easy to determine the correct identifier for the Array. For the instance containing _StorageSystem, the string after the word Name contains the Array Identifier / WWN. In this case the Array Identifier is 50001FE15000A7E0. Steps to reset EMC Provider password for v4.1.x: a. Shutdown ECOM b. Go to <ECOM Install directory>/conf/cst/ c. Remove RoleData.xml, LocalDirectoryData.xml, csp.clb* d. Restart ECOM General Troubleshooting Device Diagnostic Wizard Troubleshooting Resources Thwack User Community 396 STM

397 Installing Local Help Files Upload Modules Device Diagnostic Wizard The Devices Diagnostic wizard checks the status of all devices being monitored in Storage Manager. If problems are encountered, the wizard displays a message on the Main Console page and the device console pages. From the main console, click Show Devices. Click the device name Use the Diagnose Problem link to help resolve the problem. Troubleshooting Resources For more information about troubleshooting Storage Manager issues, reference the SolarWinds Knowledge Base located at er/troubleshooting+(storage+manager)/ If you need further assistance, contact support (requires valid maintenance license). STM 397