SolarWinds Storage Manager powered by Profiler Administrator Guide
Copyright © 1995-2012 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 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.
Administrator Guide SolarWinds Storage Manager powered by Profiler Storage Manager powered by Profiler Documentation The following documents are included in the SolarWinds Storage Manager powered by Profiler documentation library: Document Purpose Administrator Guide Provides detailed setup, configuration, and conceptual information. Evaluation Guide Provides an introduction to STM features and instructions for installation and initial configuration.
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 .
Discovering and Adding Devices .................................................................. 32 Editing Devices.............................................................................................. 34 Editing Devices.............................................................................................. 35 Agent Status ............................................................................................. 36 Data Retention Policies ...................................................
Application Monitoring ................................................................................... 96 Chapter 8 Reports and Schedules ............................................................................. 101 Creating a New Report ................................................................................ 105 Using Groups ............................................................................................... 112 Chapter 9 Rules & Policies .......................................
General Troubleshooting ............................................................................. 275 Index Index ...........................................................................................................
Chapter 1 Introduction to SolarWinds Storage Manager powered by Profiler SolarWinds Storage Manager (STM) is designed to give users greater control over their networked storage and server environments. Storage Manager supports event monitoring and reporting of the health, status, usage, and performance of critical storage and server devices.
• Oracle ® • SQL Server ® • Microsoft ® Exchange 2003 • Microsoft ® Exchange 2007 SAN and NAS: • 3Par • Dell™ EqualLogic™ • Dell PowerVault MD3000i • Dell Compellent • EMC Celerra ® • EMC CLARiiON ® , VNX • EMC Symmetrix DMX ,VMAX™ • EMC VNX • Hitachi Data Systems ™ • 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 V70
• QLogic switches • Host Bus Adapters (HBAs) (Emulex® and QLogic) Backup Profiler Backup Profiler requires purchase and is licensed into two tiers. Category 1: Backup Exec, Arcserve, Commvault Category 2: Legato, TSM, Netbackup Backup Profiler’s web-based backup console provides your entire team with a real-time, at-a-glance view of all backup operations. It automatically summarizes backup status, exceptions, and trending of backup size.
STM Server The STM server consists of a MySQL Database, Tomcat Web Server, Collector, Poller, Event Receiver, and a Maintenance process. STM uses a variety of methods to collect data, both local and remote. STM 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, backups and Exchange, agents are required on those servers.
• Maintenance • Webserver STM Agents OS Agents reside on operating systems and provide two functions. • • Agents gather asset, storage, performance and file information for that device. • • Agents provide a platform to monitor applications or other devices that reside on or are connected to that server.
Chapter 2 Installation Storage Manager is composed of two separate components that will need to be installed. The server install and OS agents. The following sections guide you through the various instalation scenarios for STM.
Storage Manager System Requirements Verify that you have downloaded the correct versions for your environment and that your system meets the minimum requirements.
Storage Manager Server STM Server Operating System Required Ports Production : Windows 2003, 2008 (32 & 64 bit) Linux Red Hat, SUSE (32 & 64 bit) Port 9000 as Web server port (HTTP) for the GUI. This port can be changed in the server.xml. Port 4319 as its communications port with STM Agents (HTTP). This port can be changed system wide, or on an agent by agent basis.
• 1 additional Agent per 200 VM • Poller/agent: Single/Dual Processor, 2GB of RAM Large Installation: Up to 30,000 disks Windows 64bit • 8-16 Processors, 16-64GB RAM • 1 additional Agent per 200 VM • Poller/agent: Single/Dual Processor, 4GB of RAM Other System Requirements: • Agent Requirements • Application Module Requirements • VMware Requirements • Fibre Channel Requirements • Port Requirements Storage Manager Agents The STM Data Collector/Agent can be installed on Windows, Linux, Sol
Primary Communication Ports: • HTTP Port 4319 (configurable) – handles requests from STM Server Collector • UDP Port 162 (configurable) – SNMP traps are sent to the STM Server Credentials Required: • Local System Account (Default) • Log On rights of Domain Account if WMI counters/Logical disks are not accessible to Local System Account. Domain Account must belong to Local Administrators group.
Versions/Models 2003, 2007: Mailbox Analysis Server and Application Performance Attachment Analysis (Ver. 2003 only) Requires Agent? Yes – on Exchange Server (Ver. 2003 only) Yes – on Mailbox Server (Ver. 2007 only) No – on Hub transport and Client Servers (Ver. 2007 only) No Requires a Proxy Agent? Prerequisites Ver. 2003 • Create Domain user with Exchange View Only Administrator role defined • Define MAPI Profile for Domain user on Exchange Server, set as default Profile Ver.
Communication SQL Queries over IP Oracle: Versions/Models 10G, 11G Requires Agent? No Requires a Proxy Agent? Yes – via STM Server Prerequisites Requires ID with Table name Permissions V$SGASTAT select v$version select v$statname select v$sesstat select v$session select v$sysstat select dba_rollback_segs select dba_indexes select dba_tables select dba_segments select sys.dba_extents select sys.dba_data_files select Credentials sys.dba_tablespaces select sys.
Other System Requirements: • VMware Requirements • Fibre Channel Requirements • Port Requirements STM Server Data Collector Ports Requirements SolarWinds Storage Manager requires the following ports: • HTTP Port 4319 (configurable) – handles requests from Profiler Server Collector. • UDP Port 162. By default if 162 is in use by Orion NPM for example, then Profiler will use 10162 or 20162 to register the agent, (also configurable) – SNMP traps are sent to the Profiler Server.
• EMC Symmetrix, DMX, VMAX: Configurable: 5988 (HTTP) or 5989 (HTTPS) used by EMC Solutions Enabler. • HP EVA: Configurable: 5988 (HTTP) or 5989 (HTTPS) used by HP CommandView. • HP MSA: Non-configurable: 5989 (HTTPS) used by HP SMI-S Provider. • IBM DS 3K, 4K, 5K: Configurable: 5988 (HTTP) or 5989 (HTTPS) used by the SMI-S provider .Non-Configurable: 2463 used to set RPC sessions to the storage controller from SMI-S provider.
Downloading the Installer To download the Storage Manager installer, you will need your SolarWinds ID (SWID) and password to login into the customer portal. Note: Existing customers received them in an email when Profiler was originally purchased. To obtain a SolarWinds ID (SWID) contact customer support. The following steps detail how to download Storage Manager Server. To Download the Storage Manager Server: 1. Login into the customer portal: http://www.solarwinds.com/customerportal/ 2.
For example: If you install the 32bit version of Profiler on a 64bit system, download the STM5.0 64bit version and run the installer - it will automatically migrate 32bit Profiler to 64bit Storage Manager. How come I only see Storage and/or Backup licenses in the Portal? The licenses for other Profiler devices (Servers, Agents, Pollers, Virtualization, Fibre Channel Switches and Applications) have been rolled into the disks licenses.
1. If you downloaded the product from the SolarWinds website, complete the following steps: a. Navigate to the location of your downloaded .zip file, and then extract the package to an appropriate location. b. Launch the SolarWinds STM Server executable. 2. Review the Welcome text, and then click Next. 3. Select setup type. Express Install is recommended for Evaluations. 4. Accept the terms of the license agreement, and then click Next.
Installing the Storage Manager Integration Module on your Orion Server If you are using an Orion product (NPM, APM, etc…) with Core 2011.1 or later, you can install the Storage Manager Integration Module and see storage data inside of your Orion product. To install the integration piece: 1. The integration module installer (OrionIntegrationModuleforStorgaeManager.msi) is included in the zip file you downloaded. Copy it to the Orion server (Core 2011.1 and later) and execute it. 2.
3. Click "Enter Registration Key" and then paste the string you copied from the customer portal. As long as the Storage Manager has internet access, it will activate the key and refresh the screen to show the newly activated key. If Storage Manager cannot reach the internet, there is a manual process to complete. Follow the onscreen instructions for offline activation.
4. Repeat the process for each key you want to activate (1 Storage and 2 Backup Categories). 5. Enter the Registration information and click Register. License Manager Page The License Manager page provides details about your main server license and any additional modules. This page also shows the service pack level which you are on. To access this page: 1. Click Settings > License Manager.
1. Verify the version of the agent in the Devices page. 2. If the agent version does not match the current version, then move on to upgrade the agent. 3. Click Settings > Updates & Upgrades. 4. Click Upgrade Agents. 5. Provide a name for your Agent Upgrade activity. Select all the required modules and the Agents. 6. Click Save to push the changes. 7. Click Module Push Report for details on the Modules/Agents upgrade pushed. Note: The Agent upgrade details are also available in Reports.
2. Complete or change the following info: a. 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 STM. HTTP Port : The port used by STM to collect data from the agent (default 4319). If you change this setting, STM will immediately try to connect to this agent and update its configuration. If STM is unsuccessful, then it will abort the changes.
• 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.
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.
3. Replace the data directory (see section above for paths) with the backed up directory 4. Restart MySQL 5. Restart STM services MySQL Performance Tuning: The MySQL Database Server should perform correctly under most situations and in most environments with the default configuration. If performance optimization is required, contact SolarWinds http://www.solarwinds.com/support/ticket/ for assistance on tuning MySQL.
Chapter 3 Web Console Navigation The STM Web Console provides a consolidation of information about your enterprise. The left navigation tree includes the following sections: Event Monitor The Event Monitor page summarizes the different events that are currently active (not cleared). Clicking the chart takes you to the Event Monitor screen. Reports: The SAN Group console aggregates information from both SAN devices and OS Devices that have file systems assigned to a SAN device.
Virtualization: Settings: Provides quick access to all the STM settings.
The Server Monitor page list the monitored servers and displays condition levels which are represented by various status icons. Backup Monitor Backup Dashboard shows the status of the client groups based on the status of all clients in that group. We can also drill down each client group to view the status of all the clients in that group along with details like Group, Start Time, End Time, Backed Up MB. At a glance it provides, 8 days view of backup client group and client backup statuses.
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. Getting Started Page When you login to the web console you will see the Getting Started with Storage Manager section. This device provides quick access to adding storage devices to monitor. The left navigation menu provides access to all the remaining components of STM.
Adding Users Managing Existing Users Adding Users To add a new user: 1. Click Settings > Manage Users 2. Click Add New User a. Then enter the Display Name, and Password. The password must be at least one character long; it is case sensitive. STM 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.
In addition, STM allows you to select the type of data a user can see. • Backup - Backup Servers and Clients • Device - 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 Administrator Administrators can see all data about all devices in all groups.
5. You may edit the email address of the user or add new email addresses. Multiple email addresses and aliases can be entered if necessary. Entered email addresses will receive notifications from all devices specified in the Notifications field. 6. To modify the list of devices that will send alert notifications to a user, click on the Edit icon in the Notifications frame. 7.
The Getting Started page allows you to add devices at any time. To begin Network Discovery 1. Click Discover 2. Add IP ranges to define the section of network for the discovery scan 3. Click Next 4. Add the necessary credentials for each type of device to be scanned. 5. Click Discover 6. Click Next to assign the discovered devices 7.
Note: When VC is assigned it will do an additional discovery in which additional ESX servers discovered will need to be configured on the Getting Started Page. a. Select from the dropdown b. Click Save Editing Devices The All Devices section allows you to add and edit applications and devices or edit existing devices. Devices are the storage devices that you want to monitor. To define, modify, or delete a device: 1. Click the Settings link under the left tree navigation. 2. Click All Devices.
After entering the necessary information, the device will appear in the device list for management Clicking the icons below allows you to edit, delete, configure Agents, and verify the current status for the selected device. Editing Devices To edit the information about a device, click the edit icon (pencil/paper) in the same row as the device's name.
Deleting Device To delete a device from STM, return to the device screen and click the trash can icon. A dialog box will appear requesting confirmation. Agent Status Agent Status displays the status of the modules installed on the client. When you click the Status icon, an Agent Status window will appear.
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 STM Collector 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.
Chapter 4 Server Setup Define the parameters of your Storage Manager server.
• Auto Assign OS License determines if STM 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.
• NetBackup: Treat job exit code 1 as lets the administrator determine whether or not an exit code 1 should be logged as a success or failure. • NetBackup: Treat job exit code 71 as lets the administrator determine whether or not an exit code 71 should be logged as a success or failure. • Backup Server Inactivity Threshold sets the inactivity threshold for backup servers.
• NetBackup:Exclude Exit Codes from Final Status summary Reports This parameter will exclude all the exit codes added in this option from the NetBackup Final Status Summary report. Valid IP addresses will be used to generate a list of Legato, TSM and NetBackup clients which are not being backed up by those servers respectively. The reports can be located under the "Reports" section for the specific backup server type. To turn off this feature select "no" and restart the Web Server.
• 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.
• 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. • 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.
Server Settings The Server settings control the overall behavior of the collector, the SNMP and DNS Poller, how the server sends email, and the global configuration of File Age Categories. • Delete Log files Older Than sets the duration server log files are retained on the server. • Delete Output files Older Than sets the duration temporary files are retained on the server. • SNMP Trap Port sets the port you want to receive traps on.
• Collector Frequency allows administrators to specify the maximum time between collection attempts, ranging from 30 minutes to daily. Every 15 minutes, STM 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.
• LDAP Server Display Domain name Provide display name for LDAP server • LDAP Server URL Provide URL for LDAP Server • LDAP Server Manager DN Provide Domain Name for LDAP Server Manager • LDAP Server Manager password Provide password for LDAP Server Manager • LDAP Search Base Specify LDAP search base • LDAP Search Filter Specify LDAP filter • LDAP Search Subtree Searches LDAP subtree when set to True • LDAP Dereference Flag LDAP Server performs dereferencing when set to True For example: 46
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 specifies as many categories needed, but the alignment may not look proper in the chart if the count goes more than 7. 1,2,3,4 will lead to 5 categories in the pie chart with (1CPU,2CPU,3CPU,4CPU,Other) colors .
48 Using STM
Chapter 5 Monitoring Storage Arrays STM monitors arrays in a variety of ways – SMI-S, SNMP, API, Telnet/SSH, and each method can have extra requirements to enable discovery and monitoring. Here is a summary of how each supported array is monitored and if there are extra requirements: Device Method Additional Software required 3PAR SMI-S No, SMI-S built into the array. Dell Compellent SMI-S No, SMI-S built into the array Dell Equalogic SNMP No. Yes, download and install the LSI SMI-S Provider.
Xiotech 3D 4000 and Emprise Web Services No Storage Array Requirments The follwing is a list of requirements needed to monitor your devices using STM.
Actions Ports Used Communication Installation Versions/Models Features Requires Agent? Requires a Proxy Agent? Prerequisites Credentials Read/Write Actions Ports Used Communication Data Classification Versions/Models Features Requires Agent? Requires a Proxy Agent? Prerequisites Configurable: 5988 (HTTP) or 5989 (HTTPS) used by 3PAR provider. • See the STM Ports section below. Can be HTTP/HTTPS between proxy agent and 3PAR SMI-S provider.
Credentials Read/Write Actions Ports Used Communication Data Classification available upon request. Usually provided just the root login • Add Proxy agent to list of trusted hosts on the NetApp storage system • ONTAP 7.3.
Prerequisites Credentials Read/Write Actions Ports Used Communication Versions/Models Features Requires Agent? Requires a Proxy 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 6.4.2 (Provider 3.2.
• • Credentials Read/Write Actions Ports Used Communication Versions/Models Features Requires Agent? Requires a Proxy Agent? Prerequisites Credentials Read/Write Actions Ports Used Communication Versions/Models Features Requires Agent? Requires a Proxy Agent? Prerequisites 54 Using STM 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.
Credentials Read/Write Actions Ports Used Communication Versions/Models Features Requires Agent? Requires a Proxy Agent? Prerequisites Credentials Read/Write Actions Ports Used Communication Versions/Models Features Requires Agent? Requires a Proxy Agent? Prerequisites Account and password stored in Profiler database and configuration files on proxy agent using custom encryption Read Only Configurable: 5988 (HTTP) or 5989 (HTTPS) used by SMIS provider Non-Configurable: 2463 used to set RPC sessions t
Credentials Read/Write Actions Ports Used Communication Versions/Models Features Requires Agent? Requires a Proxy Agent? Prerequisites Credentials Read/Write Actions Ports Used Windows/UNIX server that has IP connectivity to SVC Account and password stored in Profiler database and configuration files on proxy agent using custom encryption Read Only Configurable: 5988 (HTTP) or 5989 (HTTPS) used by SMIS provider • See the STM Ports section below.
Credentials Read/Write Actions Ports Used Communication Versions/Models Features Requires Agent? Requires a Proxy Agent? Prerequisites Credentials Read/Write Actions Ports Used a role with access to execute specific API calls. List available upon request. Usually provided just the root login • Add Proxy agent to list of trusted hosts on the NetApp storage system • ONTAP 7.3.
• IBM 3xxx,4xxx,5xxx Arrays • IBM SVC • EMC CLARiiON • Hitachi • HP 3PAR • NetAPP • NetAPP Flier • Pillar Monitoring IBM 3xxx,4xxx,5xxx Arrays The following section details how to add storage arrays from various vendors. Note: To add an IBM V7000, you need to select IBM SVC from the dropdown list. To add a LSI storage array: 1.
2. From the dropdown list select LSI and click OK. . 3. Click the Configure a LSI Array link. 4.
a. Server IP Address: Select the agent you want to monitor the Array b. Device Display Name: Type a descriptive name for the LSI array (ex: LSI NY) c. Storage Array Type: Select Storage Array LSI d. Active: Do not clear this check box, doing so will stop information collection from the array e. Device Groups: Optional - if you have configured groups, you can add this array to them by clicking the group name 5. Click Next> to continue to the next configuration screen.
6. Click Save to save the configuration and push it out to the agent to begin monitoring the array.
Note: Click Test to test the connectivity between the agent and provider, and if successful, display the identifiers from the arrays configured in the provider. Note you must have entered the username, password and provider IP address before pressing this . Monitoring EMC CLARiiON Arrays The following items are required before you begin: The EMC SMI-S Provider is installed, running and configured to monitor the Clariion(s) in the environment. Verify that you have: a. EMC SMI-S provider login credentials b.
2. Select the Array type from the dropdown, click OK 3.
• Server IP Address: Select the agent you want to monitor the Array - • Device Display Name: Type a descriptive name for the Clariion array (ex: Clariion NY1) • Active: Do not clear this check box; doing so will stop data collection from the array • Device Groups: Optional - if you have configured groups, you can add this array to them by clicking the group name 4. Click Next> to continue to the next configuration screen.
Provide the appropriate information about the array you want to monitor. If you are unsure about a value, do not change the value from the default.
• User Name: Type the user name used to access the provider • Password: Type the password used to access the provider • Provider IP Address: Type the IP address of the server where the provider is installed • Serial Number: Type the array identifier (the serial number of ClariiON Ex: ClariiON+APM#######) 5. Click Save to save the configuration and push it out to the agent to begin monitoring the array.
2. Select the Array type from the dropdown, click OK, then click Configure a NetApp Operations Manager. 3. On the New Device page, provide the appropriate values for the following fields: • Select Agent: Select the agent you want to monitor the Array - • Device Display Name: Type a descriptive name for the ClariiON array (ex: ClariiON NY1) • DFM Server IP Address: • Device Groups: Optional - if you have configured groups, you can add this array to them by clicking the group name 4.
Provide the appropriate information about the array you want to monitor. If you are unsure about a value, do not change the value from the default. • Status: Select On • User Name: Type the user name used to access the provider • Password: Type the password used to access the provider • Provider IP Address: Type the IP address of the server where the provider is installed • Serial Number: Type the array identifier (the serial number of ClariiON Ex: ClariiON+APM#######) 5.
Monitoring NetAPP Filer The process of adding NetApp is made easier in STM, using the DFM Operations Manager which discovers all NetApps. This functionality is very much similar to Adding ESX Hosts. Once NetApp has been discovered by the Operations Manager, the NetApp filers can be assigned to the desired Proxy Agent for data collection. To Assign NetApp filers to the proxy Agent, go to Settings -> NetApp Operations Manager > Assign NetApp Filers page. Assigning NetApp Filers: 1. Select the DFM Server 2.
Pillar The Pillar SMI Provider is embedded in the array, so there no separate installation required. Upgrades for the 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 Provider if the customer has the older 512 MB Pilots, but recommends upgrading to the 2 GB versions if you want to use the SMI Provider.
The following items are required before you begin: • Switch IP Address.
Credentials Read/Write Actions Ports Used Communication include proxy agent(s)'s IP address to the list SNMP community string for each FC Switch Zoning (v4.8+): Login and Password (telnet) for each FC Switch Read Only • • 161 UDP on the switch See the STM Ports section below 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 its implicitly for SNMP V3.
• McDATA Switch: Check this if the device uses the FIBRE-CHANNELMGMT MIB rather than the standard Fibre Alliance MIB (for example, McDATA switches use this MIB). Note: McData i10K series switches do not require the McData checkbox to be enabled. For more information see this KB article.
Chapter 6 Backup Profiler The Backup Console summarizes a backup cycle (24-hour period that begins at the start of the backup window) for a single backup server or a group of clients. To configure Backup Profiler to monitor devices, select your device from the list below: • CA Arcserve • CommVault Galaxy • IBM TSM • EMC Legato • Symantec Backup Exec • Symantec NetBackup Note: Backup Profiler requires purchase and is licensed into two categories.
• Equivalence can be set using the following command from the windows command line: (If you are logged in as a user who has no equivalence to any CA ARCServe Backup user, then you must be granted an equivalence before you can use ca_auth) • ca_auth -equiv add ntuser hostName ARCServeUser [caroot_username] [caroot_password] For ARCServe on Linux, create an equivalence of user on hostname to causer: ca_auth -equiv add UnixUser hostname BrightStorUser [Brightstor_username password] To execute the agent und
a. Server IP Address: Select the agent you want to monitor b. Device Display Name: Type a descriptive name for the ARCServe device (ex: ARCServe NY) c. Timezone: Select the timezone of the Backup Server d. Backup Start Window: Select the Backup start time. This should be the approximate time backup jobs start for the day. If backups run all day, define a 24 hour window. e. Backup Window End: Select the Backup end time f. Active: Do not clear this check box, doing so will stop information collection g.
No Job Job Id Type Job Status Job Owner Start Time 1 Finished Caroot 1/30/2009 1/30/2009 11:32:14 AM 11:34:34 AM 13 Backup N Jo Jo Job o b b Type Id No 1 8 8 Job Job Start Status Owne Time r End Time Backu Finish Caro 03/24/ 03/24/ 09 p ed ot 09 11:19 11:20 End Time Set Name Set Duration Comment Nam s (hh:mm: e ss) 00:00:38 JobFullBac kup If ARCServe is on Netware enter the date format as seen in the start of a line in the job log. It can be set to MM/dd/yy or dd/MM/yy.
1. On the New Device page, provide the appropriate values for the following fields: • Server IP Address: Select the agent you want to monitor • Device Display Name: Type a descriptive name for the CommVault Galaxy device (ex: Commvault NY) • Timezone: Select the timezone of the Backup Server • Backup Start Window: Select the Backup start time. This should be the approximate time backup jobs start for the day. If backups run all day, define a 24 hour window.
• CommVault Database Port: Database Port. This can be found by checking the Dynamic Port under the TCP IP properties in SQL Network Configuration Manager where the CommVault SQL database resides. • CommVault Database Username: Type the username to connect to this CommVault Database. This can be a local account or domain account • CommVault Database Password: Type the password for this UserName. • Domain: Type the domain associated with this UserName.
• Backup Start Window: Select the Backup start time. This should be the approximate time backup jobs start for the day. If backups run all day, define a 24 hour window. • Backup Window End: Select the Backup end time • Active: Do not clear this check box, doing so will stop information collection • Device Groups: Optional - if you have configured groups, you can add this backup server to them by clicking the group name • Licensing: Check this box if you want to assign a license to this device 2.
dsmadmc id = < username > -password = < password > q actlog the output looks like Date format will be MM/dd/yyyy and Time format will be HH:mm:ss • Time Format: Type the time format as seen in the actlog query output as shown in the above example. (Default HH:mm:ss) • Activity Frequency: Select the frequency to monitor the log file (default is 5 mins). • Media Frequency: Select the frequency to monitor the media information.
• DSM Directory path: Type the Directory path to dsm.opt file. • Has Oracle Clients: If the user wants to combine the RMAN pieces for the Oracle jobs. Then this should be set to true. The configuration settings will have to be saved once for Oracle Client Association Type to be visible.
• Enable Server Exception: You can turn off Server level exceptions messages by selecting False, which will ignore all the ANR messages with I, W, E, D and S severity. 4. Click Save to save the configuration and push it out to the agent to begin monitoring the device. Configuring EMC Legato 1.
4. • Log Directory : Type the directory where log files are written (default on Windows is "C:\Program Files\Legato\nsr\logs", Solaris is "/nsr/logs"). Modify the path if it is not correct. • MM Database Dir : Type the directory where the MM database resides (default on Windows is "C:\Program Files\Legato\nsr\mm", Solaris is "/nsr/mm"). Modify the path if it is not correct.
The following items are required before you begin: • Supported versions: Symantec Backup Exec 8.5, 9, 10, 11, 11.5, 12, 12.5 Servers (Windows and NetWare) • Configuring Symantec Backup Exec To begin, click this link Configure a Symantec Backup Exec Sub-Agent and follow the instructions below. 1.
• Version of Backup Exec: Select the Backup Exec version from the drop-down menu. • Prefix of the Backup Exec Logs: Type the prefix of the Backup Exec logs. • Job DateTime Format : Type the job date/time format as present in Backup Exec job logs. The job time can be got by searching for "Job started" line if Backup Exec is on Windows or "Backup operation started" on Netware. For example: • If Backup Exec is on Windows and the Backup Exec version is 9.
• If Backup Exec is on Windows and the Backup Exec version is 9.x Backup started on 1/7/2008 at 12:00:08 AM. • If Backup Exec is on Windows and the Backup Exec version is 8.x Backup started on 30/11/2006 at 20:01:07.
• Backup Exec Media polling Frequency : The frequency at which Backup Exec media would be polled. 4. Click Save to save the configuration and push it out to the agent to begin monitoring the device. Configuring Symantec NetBackup To configure, ensure you meet the appropriate requirements and complete the following tasks. Requirements: The following items are required before you begin: • Supported versions: Symantec NetBackup 4.5, 5.1.x, 6.1.x, 6.5.2, 6.5.3.x, 6.5.
Provide the appropriate information about the backup agent you want to monitor. If you are unsure about a value, do not change the value from the default. • Monitor Backup Server : Select On • Level of the Log : Select Info • Install Dir: Type the install directory of NetBackup (the default on Windows is "C:\Program Files\Symantec", on Solaris it is "/usr/openv"). Modify the path if it is not correct. The NetBackup subdirectory name automatically appended to the directory path entered here.
Chapter 7 Monitoring VMware This section covers the following topics: • VMware Configuration • VMware Requirements • Virtualization Dashboard VMware Device Requirements Versions/Models Features Requires Agent? Requires a Proxy Agent? Prerequisites Credentials Read/Write Actions Ports Used Communication VMware 3.0, 3.0i, 4.0, 4.0i, 4.1, 4.
The STM Virtualization Dashboard provides quick views into your current virtualized environment including: • Asset Summary (including Clusters) • Capacity Analysis • Storage by type • Data stores • VMDK Utilization • VMs by last boot time • Storage Utilization by VM • VMware snapshots • Overall performance of each device- CPU, Memory, Disk Capacity Analysis Capacity Analysis page will display the current usage of CPU, Memory, Storage, Disk and Network per VM as well as per ESX level.
4. Click Run Report. The capacity planning results display a "Before and After" chart similar to the below example. Thin Provisioning Thin provisioning is a system that applies to large scale, centralized computer disk storage systems, SANs, and storage virtualization systems. Thin provisioning allows for administrators to allocate storage space to multiple servers easily and allows distributed storage systems to be deployed as needed provisioning.
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. Configuring VMware VMware VC Instances can be monitored from any Storage Manager agent. A VMware VC Instance can discover the ESX Servers connected to virtual center.
• Poller: Select the poller you want to collector data. A poller is an agent that has been licensed to monitor the VMware infrastructure. • 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.
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.
Application Monitoring The following sections detail how to configure devices for application monitoring. MS Exchange 2003/2007 MS Exchange 2003 Clustering MS Exchange Requirements Oracle Device Gathering Exchange 2003/2007 Storage Data Note: Only roles on one server are supported. Clustering is only supported with Exchange 2003. STM gathers Storage Groups and Information Store sizes.
4. When Exchange data gathering occurs at the next scheduled time, exchange module will start collecting data from the server name entered in the Exchange Virtual Name field. 5. To verify that it is working correctly, run the following commands from the Exchange module directory - >> ExchangeDataGathering.
7. Click Finish. This will allow the exe to log in and collect storage data. Adding an Oracle Device The STM Server has the capability of monitoring database servers directly via an integrated database performance and usage poller. This function is done without the need of any agents. Requirements The following items are required before you begin: • The STM Server can monitor Oracle 7.
• param16 = ..\WEB-INF\lib\profiler-poller-4.9.2.jar;..\WEB-INF\lib\profilercommons-4.9.2.jar; [shortened for example ]..\..\..\common\lib\profiler-jni4.9.2.jar;..\WEB-INF\lib\ojdbc14.jar; Linux / Solaris installation: 1. Modify \bin\poller.sh and add this string to the end of the CLASSPATH: :..\WEB-INF\lib\ojdbc14.jar For example: Before: • CLASSPATH="../WEB-INF/lib/profiler-poller-4.9.3-SNAPSHOT.jar: [ shortened for example] :../../../common/lib/profiler-jni-4.9.3SNAPSHOT.
• Licensing: Check this box in order to assign a STM Right To Use (RTU) license to the Oracle device. If you don't check this box, the device will be ignored for data collection Click Save to save the configuration and push it out to the agent to begin monitoring the device. Editing an Oracle Configuration To edit an Oracle configuration: 1. Go to Settings> All Devices> Filter Oracle to display all added devices. 2. Click the wrench icon for the appropriate Oracle device.
Chapter 8 Reports and Schedules STM has the ability to email or print either the Main Console screen or individual device Console information. The printer and letter icons will appear in the upper right hand corner of the screen when this feature is available. • Click the printer icon to print the console. • Click the letter icon to email the console information.
• Quick Reports - Predefined reports STM uses a consistent format to display and manage reports regardless of which option is selected. Select an option and a table will appear listing the reports available under that option. If no reports are available an error message will be 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.
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 STM and cannot be edited or deleted by users or administrators.
• Publish: How you want to publish the report when it is executed. • Email Report - send the report in an email 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 • Email: Choose whether all reports should be sent in one email, or broken up into individual emails.
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'.
8. Click Continue. 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.
Select Enterprise > Storage > Volume Usage Forecast and then click Continue: Next, select the columns you want in the report and the order of those columns. Each template has defaults for the columns selected, the column order and the sort order. Remove the Eighty and Ninety percent columns by highlighting them and clicking the left arrow.
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 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. For the second filer, choose "AND", "% Used", " > " and enter "90" and click "Add Filter".
Now save the report and your page should look like this. 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%).
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.
Using Groups The Grouping functionality allows an administrator to define a logical organization and permission structure to the data that is gathered by STM. 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.
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 STM will sort them into categories and determine permissions.
• 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. Managing Groups To access the Groups function from the left navigation tree: 1.
• 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. • Database: This function allows you to group databases into logical groups for monitoring. • Email: This function allows you to group email servers into logical groups for monitoring.
4. To save the new group click the ‘Save’. The group list will reappear with the new group in the list. 5. To cancel creation of the new group, click the Cancel. The group list will reappear. 6. 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: 7. CTRL-click multiple objects in the Available box.
The File Type Groups Page displays the existing File Type Group Names. To edit a File Type Group click the edit icon from the File Type Group list. 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. Creating File Type Groups 1. Click Add to add a new Group. The 'Create New Group' console will appear. Group Name: Enter the name of the group.
• Snap Mirror Monitoring The following section details how to create new rules. 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: 5.
File Analysis Rule The File Analysis Rule lets you define rules that will provide detailed file information. STM 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.
• 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 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. 6. Click Save.
To assign shares for NetApp: 1. Go to Settings > Assign Remote Shares and choose the following (changes in selection will refresh the screen) 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. Share Type: CIFS or NFS. This will automatically change available agent to match the protocol. 3.
1. You can narrow it down the shares by using the regular expression filter. a. Select the shares you want. You can select multiple shares by using the CTRL or SHIFT key. b. Now you will select which agent is going to do the work c. Device: select which agent you want to do the work d. Share Depth: Leave this at zero for now - more on depth later e. Move: Press the down arrow to assign the share, up arrow to unassign shares. 2.
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.
• 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.
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.
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.
a. Rule Name: Enter the name of the rule. b. 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. c. Size of: If you leave the value set at 0, then all files will be evaluated, and considered potentially valid, regardless of size.
g. 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. h. 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 add it to the selected list. to 2.
• Send Trap: Send out SNMP trap. Using External Scripts The STM Server has the capability to manage external scripts and execute them via the STM Agent. The Scripts page shows the user the current scripts that have been uploaded to the STM Server. Scripts can be dispatched to STM Agents and executed when a threshold condition is met or on a schedule. See "Error! Reference source not found." page "Error! Bookmark not defined." for more information. To directly edit a script: 1.
IMPORTANT: 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. Policies allow you to configure sets of agents to behave similarly and to push configurations out to the agents. The server builds a list of configuration parameters to push for each agent then proceeds to push the parameters to each agent. When you push a policy out to its agents, all parameters are pushed.
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.
4. Define any necessary configurations and then click Push. 5. The Push List Report link displays a list of pushed agents/modules/policies. Editing a Policy To edit the Policy Setup menu: 1. Click on the Settings link in the left navigation tree. 2. Under Device Management select Policies. The Menu will show different sections of parameters that you can edit.
3. To edit a section click on the icon. Once you have completed setting all the parameters you can push one or more parameters to one or more agents via the Push screen. Interacting with the thwack User Community thwack.
Chapter 10 Linux Installation The following sections detail the installation steps for LINUX. Note: 32bit agent/server should only be installed on 32bit linux system 64bit agent/server should only be installed on 64bit linux system STM Installation for LINUX Supported Platforms - STM Server Operating System Supported Versions Linux (Intel-32) RedHat, SUSE Linux (x86-64) RedHat, SUSE Supported Platforms - STM Agent Operating System Supported Versions AIX (PPC 64) 5.
Note: In case of RHEL 5/OEL 5 install, certain libXP packages are not installed along with the default RPM Packages. These are needed for STM to work correctly on Linux. Hence they have to be installed manually. Packages details: libXp-1.0.0-8.1.e15 and libXp-devel-1.0.0-8.1.e15 (These packages are available on the RH5 distribution DVD) New Install for Linux Server The following provides steps for installing STM on a new Linux Server.
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 STM server Agent port: The agent server port to use. 4.
# ./Storage_Manager_Server-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. 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.
Backup Profiler Requirements • CA ARCserve • CommVault • EMC/Legato NetWorker • IBM TSM • Symantec Backup Exec • Symantec Veritas NetBackup CA ARCserve: Versions/Models 10,11,12 (Windows), ARCserve 11.x (Linux) Features Activity Supported Platforms Windows (thru 12.x) and Linux (thru 11.
Supported Platforms Requires Agent? Requires a Proxy Agent? Prerequisites Credentials Read/Write Actions Ports Used Communication Versions/Models Features Supported Platforms Requires Agent? Requires a Proxy Agent? Prerequisites Credentials Read/Write Actions Ports Used Communication Versions/Models Features Supported Platforms Requires Agent? Requires a Proxy 140 Index Windows No – to collect Activity, Configuration, Media Yes – on CommServ to collect exceptions/errors Yes – via STM servertrfg xsd if
Agent? Prerequisites Credentials Read/Write Actions Ports Used Communication Versions/Models Features Supported Platforms Requires Agent? Requires a Proxy Agent? Prerequisites Credentials Read/Write Actions Ports Used Communication Versions/Models Features • Account to access TSM database with operator privileges • Location of TSM BA client install (on proxy agent/master server) • TSM BA client options file (dsm.
Supported Platforms Requires Agent? Requires a Proxy Agent? Prerequisites Credentials Read/Write Actions Ports Used Communication Windows, Solaris, Linux, HP-UX, AIX Yes – on Master Server N/A Location of NetBackup Install UNIX - Run as root Windows - Local System account/Domain Account Read Only STM Data Collector/Agent Ports See the STM Ports section below Installing Agents on Windows Cluster (Windows 2008) The following steps detail the installation of STM agents onto a Windows Cluster. 1.
6. Right click the offline Server and select Add a Device > Generic Service. 7. Select SolarWinds Storage Manger Agent Service from the list and click Next. 8. Click Finish. 9. Right click and select Bring the service or application online.
10. Next you will need to login into Storage Manager web console, then click Settings > Device Management> All Devices > Choose Type> OS Windows > Add. 11. Enter the Virtual IP Address of the cluster and provide a Display Name.
12. Click Next and Save.
Appendix Appendix SMI-S Provider Installation & Configuration This section covers the installation and configuration of SMI-S Providers for your arrays. Each section is followed by troubleshooting steps and FAQs for each SMI-S Provider.
A: A provider is a CIMServer which handles CIM requests from a CIMClient. Using the vender’s API, the provider connects to the device and translates it into CIM. This enables CIMClients to make generic requests across a heterogeneous environment. Q: Which Storage Arrays have embedded providers? A: 3PAR, Pillar, Symmetrix V-Max Series Q: What are the Default Ports used by the providers? A: The default ports are 5988 for http traffic and 5989 for https traffic.
SMI-S Providers The following sections detail various vendors SMI-S Provider installation steps and troubleshooting FAQs. 3PAR Provider The 3PAR provider is embedded into the Storage Array, no need to install a Provider.
Login using the username and password setup on the Array. You should see the following after successfully logging in. Note: By default the Provider is disabled and must be enabled by an administrator. Troubleshooting 3PAR The following section list frequently asked questions for the provider.
A: Logon to provider as described above and call “help”. For help on a particular command, type “help ” where 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 exit the CLI? A: Logon to provider as described above and call “quit”.
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.
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 previoulsy 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.
a. Change directory to \Compellent Enterprise Manager\msaservice\Pegasus\bin b. Type: cimuser -a –u -w 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 - This will verify the user has been added successfully. h.
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: j.
Answer: Step through the configuration steps and make sure everything is configured correctly a. Check the Task Manager . Process list . Make sure the ‘cimserver’ is running. b. Verify that the cimserver is listening on port 5988. (netstat -ano| find "5988") Verify that SMI-S user is added correctly a. From command prompt, run \Compellent EnterpriseManager\msaservice\Pegasus\bin\cimuser -l b. Open Data Collector Manager . Click Properties . Choose Log Viewer c.
Release Notes: Home > Support > Technical Documentation and Advisories > Software ~ S ~ Documentation > SMI-S Provider > Release Notes Supported EMC Hardware and Firmware: The support matrix document is available from http://developer.emc.com/developer/devcenters/storage/snia/smis/downloads/EMC_Providers_SMI-S_Only.pdf EMC Provider Version 4.0 and later The following section detail installation steps for Windows and Linux.
Installation On Windows 1. Download the software from the Powerlink website. 2. Save all files and exit all Windows applications. Launch the self-extracting executable. For example: To install the EMC SMI-S Provider V4.0 software on a Windows platforms, launch the self-extracting executable, se7000WINDOWS-x86-SMI.exe. 3. The EMC Solutions Enabler with SMI X86 welcome page appears prompting you to install Solutions Enabler with SMI version x.x. Click Next. 4. Click Next to begin the installation.
01 EMC Solutions Enabler V7.0.0.0 SMI KIT V4.0.0.0 #---------------------------------------------------------------------------Logging In 6. Run the TestSmiProvider.exe (located at \ECIM\ECOM\bin). 7. Accept defaults for host, connection type and port. Username : LocalDir/admin Password : #1Password Symmetrix Symmetrix arrays are discovered automatically by the provider. So it is not required to add it to the provider using ‘addsys’ command.
CLARiiON out-of-band Note: out-of-band 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 In”. 2. Run the addsys command. 3. Type “y” at Add System prompt. 4. Chose the Array Type 1 for Clariion 5. Type in the IP address of Storage Processor A and Storage Processor B 6. Type the Address type 2 for both Storage Processors 7.
Installation on Windows 1. Double click the installer. 2. Click Next on the “Welcome” screen.
3. Choose a location to install to at the “Destination Folder” screen. 4.
5. Click Install at the “Ready to Install the Program” screen. 6.
Index 163
7. Click Finish at the “InstallShield Wizard Completed” screen. Installation on Linux 1. Untar the kit by typing: tar –xvf .tar 2. Execute the installer by typing: ./se6410_install.sh –install.
3. When the installer is finished, you will see the following: 4. Logging In 5. Run the TestSmiProvider.exe (located \SYMCLI\storbin).
6. Accept defaults for host, connection type, port, username and password. Adding A SAN Symmetrix & CLARiiON Out-of-Band Note: Out-of-Band 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).
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). 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.
8. Confirm the array to be added is locally attached. \SYMCLI\bin\syminq –cids There should be at least one LUN mapped to this host from the array. 9. Check the emcprovider.conf setting has ‘discover’set to ‘true’. It is located at \SYMCLI\storbin directory. OslProv/com.emc.se.osls.osl.StorApi.database.discover=true 10. List the authorization info. \SYMCLI\bin\symcfg list auth 11. If the list does not have entries for SPA and SPB of this array, 12.
The 6.4.2 SMI Kit and higher has an auto-synchronization mechanism, which by default is one hour after the last update (this option is configurable). Upgrading the Provider to 6.4.2 or higher is a must when Profiler does not recognize changes in the array configuration. Q: What EMC SMI Kit is needed for Flare Code 26? A: EMC’s SMIKit 6.4.2 (Provider 3.2.2) and higher. A Clariion with Flare Code 26 can only be monitored by an SMIKit 6.4.2 (Provider 3.2.2) or above.
3. Run EMC TestSMIProvider and run the command ‘dv’. Make sure all array are discovered without any errors. 4. Make sure Performance frequency is set to non-off value in Wrench Icon for Storage Array in Profiler (i.e. Performance is turned on). 5. Make sure there are instances for class name CIM_BlockStorageStatisticalData when enumerating instance names (ein). To do this, do the following: 6. Run Tek-Tools testProvider or EMCs testSMIProvider (Logging In instructions above in Tools section). 7.
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.
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.
The observed behavior is consistent with the way Clariion works. On Clariion, it is possible to see the primordial pool with RemainingManagedSpace having a nonzero 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 Clariion, with the capacities of 10 and 15 gigabytes.
‘SymDevMaskLoginHisto The VCMDB_RESTRICTED bit on symm 000187751584 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.
5. Change the port0 and port1 tag values to ports currently not in use. For Example: 15988 false true 15989 true true 6. Save port_settings.xml file. 7. Start the ECOM Service. 8. In the Profiler GUI: Go to Administration > Hosts. 9. Click the monkey wrench icon for the Array. 10. Change the HTTP port to the port set in the port_settings.
2. Start ECIM/ECOM/bin/sm_service start ecom.exe On Unix: 1. Stop Obtain the PID of the ECOM process and issue the kill command for that PID. ie kill –SIGTERM [PID] 2. Restart ECIM/ECOM/bin/ECOM –d Q: How do I prevent locally attached Clariion from automatically being discovered? A: Only provider version 4.0 and above. To remove a locally attached CLARiiON from auto discovery, write out a file with name ‘claravoid’ in the directory SYMAPI/config.
4. Run TestSMIProvider and add your arrays. Troubleshooting EMC Version Pre-4.0.0 Q: I want to monitor a Symmetrix V-Max Array. Which provider do I use? A: Version 4.0 of the provider has added support for V-Max series. The provider is embedded with the array. Q: What files are needed to send a bug to 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 \symapi\log symapi_db.
SYMCLI/storbin/stordaemon shutdown all 2. Start SYMCLI/storbin/cimserver -start emc_smi_provider Unix: 3. Stop /SYMCLI/storbin/cimserver –s 4. Start /SYMCLI/storbin/cimserver Note: For solaris you MUST be in the /SYMCLI directory and run ./storbin/cimserver command Q: Why does addsys time out when adding a CLARiiON, and how do I fix it? A: This error typically comes from the cimserver.
Hitachi Data Systems (HDS) Provider 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. 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.
Note: Disabling SNMP function has no effect on SMI-s provider.
5. Choose the Destination folder for HiCommand. Click Next.
6. Choose the destination for the HiCommand Suite Common Component database. Click Next.
7. Choose the destination for the HiCommand Device manager database. Click Next.
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.
9. Click Next at the adding to the windows firewall exceptions screen.
10. Select YES for enabling the SMI-s provider service after installation. Click Next.
11. Select NO for SSL, unless a secure connection is needed. Change port if needed. Click Next.
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.
13. Select YES for the SLP function to be enabled after installation. Click Next.
14. Select YES to start the HiCommand Suite to start after installation. Click Next.
15. Click Install at the Pre-Installation Summary page.
16. Click Next at the Secure Socket Certificates Note.
17. Click Finish. If you are using installing HDS 6.3 Device Manager Q: How do I enable the provider? A: 1. EditC:\ProgramFiles\HiCommand\DeviceManager\HiCommandServer\co nfig\server.properties 2. Edit following line and set server.cim.support to true # whether the server supports CIM interface or not server.cim.support=true Adding a Subsystem 1. Open HiCommand Device Manager GUI. 2. Click Subsystems.
3. Click Add Subsystem. 4. Select the Type of subsystem to be added. 5. Type in the IP Address of the Controllers. 6. Click OK.
7. Click OK when asked “Are you sure”.
You should see: Index 197
8. Click Close. 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? 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 Profiler. Q: What user permissions are required for the provider? A: All resources with view privileges.
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.
Q: Will disk or controller performance be available? 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, 9900v). 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.
WMS SMS AMS2100, AMS2300, AMS2500 WMS100 SMS100 Note: 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.
A: Steps to change the memory settings - from "Device Manager Server Installation and Configuration Guide" 3.1.2.3 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: 2.
Restart the Device Manager server as follows: Select Start, Programs, HiCommand, Device Manager, and then Stop Server. 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.
Select Language.
Click Next at the introduction screen. Accept the License agreement. Click Next.
Accept the license key agreement. Click Next. Choose Install Set. Check EVA PerfMon and SMI-S Cimom. Click Next.
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. Verify the Pre-Installation Summary. Click Install.
You will be presented with the following during the install. Click Done.
Adding Users to HP Groups The following section details how to add users to HP groups.. Right click “My Computer”. 1. Click Manage.
2. Click “Local users and Groups”. 3. Click Groups.
4. Double Click “HP Storage Admins”. 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. Troubleshooting HP EVA Q: What is the minimum Command View version I should be using for EVA? A: Command View 8.0.2 Q: What is the default user name password? A: The user must be a valid user for the Command View. The default username/password is administrator/administrator. Note: With Command View 8.x and 9.
A: For Command View version 7.0 or below: The user must be a valid local system user(domain user is not enough). User has to be added to the provider using the cimuser utility. Can choose a different password when adding using via ‘cimuser’ utility. - Note: User may get removed from the provider when the provider service gets restarted. Use the cimuser utility to list the users already added to the provider. For Command View version 8.0 and above: EVA provider users are valid Command View Users.
Performance data is not available if firmware is ‘6110’. This is due to a known issue where port WWN is zero. Solution is to upgrade to firmware version 6200 ‘HP EVA Perf’ template must be selected from profiler for the device. Check if the logs show ‘Duplicate host port address on EVA controller” exception when getting performance data. This is a known issue.
a. Stop the HP StorageWorks CIM Object Manager service (Services window) b. Change the parameters cxws.http.port and cxws.https.port in the cxws.properties(C:\Program Files\Hewlett-Packard\SMIS\CXWSCimom\config\cxws.properties) file. Q: How do I enable/collect logging? a. Set the Provider and CIMOM Log Level by executing the command, \Hewlettpackard\SMIS\CXWSCimom\bin\cscript Set_LogLevel.
2. Set the path to the specified directory as in the following example: Installed Path\Hewlettpackard\ SMIS\CXWSCimom\bin 3. Enter the Set_LogLevel command as displayed in the following example: cscript Set_LogLevel.vbsloglevel After you enter the CIMOM and HP SMI-S EVA Provider Set_LogLevel command, the log level is set to the desired log level. The following example message is displayed: Log Level Set to: log level.
Information collected successfully Location: C:\Program Files\HewlettPackard\SMI -S\support_ d200896_t105335.zip Note: Make sure the debug logging is turned off after the logs are being collected. HP does not recommend turning on DEBUG logs except for diagnosis. Command View logs are located at, C:\Program Files\Hewlett-Packard\Sanworks\Element Manager for StorageWorks HSV Q: Provider is not discovering the EVAs after a fresh install or provider is not able to synch with the EVA after running for a while.
If it is not found to the valid Command View EVA Server IP, add the correct IP using ‘discoverer.bat’ . Then remove the invalid IP. Refresh the smis provider cache using the command \Hewlett-Packard\SMI-S\CXWSCimom\bin> CLIRefreshTool.bat The result will show if the refresh was successful or not. You can also check on the status of the periodic refresh of the cache using the command, \Hewlett-Packard\SMIS\CXWSCimom\bin>GetArrayRefreshStatus.
Q: How do I install the trust certificate between provider and command view? A:Please select the "Server Options" in the CV EVA GUI. (Top right side) Please click on the "Other application trust relationships" option (check box). Remove the existing certificate using "Uninstall Certificates" option. Install the new certificate (HPSMISSSO.cert) using the "Install Certificate" option.You need to give the certificate location and the name (name can of your choice). HPSMISSSO.
- Command View version info - If it is an issue with performance, include the output of the following evaperf commands. • a. evaperf as • b. evaperf pd • c. evaperf vd • d. evaperf hps Note: evaperf.exe is located under folder 'Hewlett-Packard\EVA Performance Monitor'. Note: HP support requests log files in ALL level; however, the logs may be overwritten, or unable to reproduce issue after resetting log level. Be sure to explain thoroughly in email to support.
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.
Enabling SNMP: You need to have SNMP enabled and also allow the respective proxy agents 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.
Note: Community Strings are CASE sensitive and need to reflect their case sensitivity in Profiler as well. To check if proxy agent is in Access Control list: Check the Access Control list and see if the 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...
Add 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.
The 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...
Once you click copy the configuration is copied to all the nodes selected. You should now see the proxy agent IP in each node's Access Control list. 1. Management Group 2. Servers 3. Cluster 4. Node 5. SNMP Settings IBM DS Provider The following section details installation links to versions of IBM providers. The correct IBM Provider to install is based on Model and Firmware. For any DS 6000, 8000 or ESS, install the IBM Provider.
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: http://www947.ibm.com/support/entry/portal/Downloads/Hardware/System_Storage/ Storage_software/Other_software_products/CIM_Agent_for_DS_Open_( API)/ IBM CIM Agent: http://www01.ibm.com/support/docview.wss?rs=1118&context=STC4NKB&dc=DB500&uid= ssg1S1003070&loc=en_US&cs=utf-8&lang=en IBM Provider FAQ: http://www01.ibm.
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: \logs \pegasus\log \pegasus\logs Q: How do I add an array to the provider? A: \bin\dscimcli mkdev -type -user password Example: dscimcli mkdev 192.168.0.
Q: In what release did the CIM Agent become embedded in the HMC (Hardware Management Console)? A: Starting with Release 2.4 (Bundle 6.2.400.64) of the DS8000, the CIM agent was embedded into the HMC. Up to Release 4 (Bundle 62.0.175.0) 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.
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.
IBM SVC Provider The IBM SAN Volume Controller (SVC) SMI provider is embedded in each cluster. 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. Profiler must use the CIMOM on the cluster. SVC (SAN Volume Controller) CIM Agent Download: http://www304.ibm.com/jct01004c/systems/support/supportsite.
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.
New Provider (Eagle 5) downloads are located here: http://support.netapp.com/apbu/oemcp/protcd/ After logging in to the site, click the SMI-S Providers download link. New Provider (Eagle 2) 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.
2. Click Next at the “Introduction” screen.
3. Accept the License Agreement, Click Next.
4. Click Install. Add the IP addresses for the Array Controllers. Save and close Notepad.
Click Finish at the “Install Complete” screen. 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 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. 6. Type n to not set the storage array password. Adding A SAN Installation on Linux 1. Edit the /opt/lsi/sbma/data/ArrayHosts.
3. Stop the cimserver with /opt/lsi/pegasus/bin/cimserver-s 4. Start the cimserver with /opt/lsi/pegasus/bin/cimserver start Legacy Provider (Pre-Eagle 2) The following section details the installation on windows devices for pre-eagle 2 providers. Installation on Windows 1. Double click the installer. 2. You should see a status bar.
3. Click Next at the “Introduction” screen.
Accept the License Agreement, Click Next.
Choose the Install location, Click Next. Click Install at the “Pre-Installation Summary” screen if the summary is correct.
244 Index
Add the IP addresses for the Array Controllers. Click OK.
Click Done at the “Install Complete” screen.
Installation on Linux 1. Untar the Linux_Installer_xx.xx.xx.xx.tar file. 2. Execute the install executable. Adding A SAN The following section details the installation steps for adding SANs from windows and linux devices. Windows 1. Run the \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.
5. Type the array password. Obtaining Array Identifier 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.
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.
4. Scroll down to Storage array worldwide name (ID) under Summary for All tab. Common Array Manager 1.
2.
Troubleshooting LSI New 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. a. For a Windows operating system, the directory is C:\LSI\. b. For a UNIX-based operating system, the directory is /opt/lsi/sbma/data/. 2.
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 2463. The port 2463 is used to set RPC sessions to the storage controller. Q: How do I change the port the provider listens on? A: To change the port, do the following: On the machine running the Provider: Open the portInfo.
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 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 follow the below instructions to enable debug tracing and duplicate the issue so the SMISProvider.log file is created: 1.
Array Perf: smi-s Controller Perf: calculated by Profiler. Aggregate the performance values for all the luns that belong to specific controller. LUN Perf: smi-s Disk Perf: 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 10.10 version of the API was built against jdk 1.4, which matches with the jdk used in the Profiler agent at the time of the 4.8 release. The 10.
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 5988. 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 5989.
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: 1.
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. 1. To start: /etc/init.d/init.wbem start svcadm enable svc:/application/management/wbem 2. To stop: /etc/init.d/init.wbem stop svcadm disable svc:/application/management/wbem Note: other useful smf commands: (www.princeton.
A: Copy/paste following script to new file on system.
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.
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? The System information logs. See above on how to obtain logs 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.
Clone LUN Fibre Channel Protocol NDMP 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 Storage TEK 99xxSeries Provider Sun/StorageTek 99xx Series can be monitored from any OS agent by polling a HDS SMI-S Provider, typically the HiCommand Device Manager.
This button serves several purposes: 1. Verifies connectivity to provider by checking: a. username/password b. namespace c. provider ip address d.
\java -classpath .;mod.sys.smis.Smis.jar;.\lib\sblim-cim-client22.0.9-INTERNAL-r1.jar;..\..\lib\core.jar TestProvider Note: on Unix, use colons (: and /) instead of semi-colons (; and \) when separating the list jar files above 4. You should see a screen like the following: 5. Fill in the information below to log into the provider. (All defaults are in brackets. To accept default, simply leave field blank and hit return). a. Host – Hostname or IP of provider you wish to connect to. b.
6. Once connected, you should see the following. Obtaining Array Identifier (enumerating instances) 1. Type ein at command prompt. 2. Type CIM_ComputerSystem at Class Name prompt. 3. Select the Name field for the instance if _StorageSystem like below. CIMWorkshop Download: http://sourceforge.net/project/showfiles.
1. Unzip the wbemservices-1.0.2.bin.zip 2. Open the wbemservices-1.0.2.bin directory. 3. Edit cimworkshop.bat located in the bin directory. a. Un-REM line 36, and change the path to the directory where the java jre is installed, if JAVA_HOME is not set as a global environment variable Example: set JAVA_HOME=C:\Progra~1\Java\jre1.6.0. Obtaining Array Identifier 1. Run the cimworkshop.bat. 2. Enter the Host URL, User Name, and Password for the Array.
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: http://crawfish:5988/root/cimv2 268 Index
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. 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.
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.
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.
4. Restart ECOM Remote Agent Upgrade Utility Note: This section only applies if your agents are older than version 4.12. In the legacy product, Profiler 4.12, the improvements made to the application cannot be pushed via the upgrade module method used in previous releases. This means that all existing agents have to be upgraded in one of two ways: 1. Manually upgrade the agent via the software install. This means you will need to copy the install file to each server. 2.
The utility will provide a log directory to monitor the upgrade progress. Note: Before installing an agent you need to edit the Default Policy for Operating Systems on the server, as these settings will be pushed out to the agent when it self-registers. Once you have installed the agent, the agent will self-register and self-configure. The self-registration process will create an OS Device on the STM server. Devices can also be defined manually. How to enable SSL login for the STM website 1.
The web properties file contains the URL location of the server where online help for SolarWinds products are stored. The default location is http://www.solarwinds.com/support/storage/storagemanager/default.htm?context =StorageManager If you are in an Internet-restricted network environment but require access to online help, download the entire online help, copy it to a web server, and then change the Help Server URL to that of the web server. You can download the online help from http://www.solarwinds.
Index Index A N adding scripts 78 agent installation 15 upgrade utility 15 asset change rule 77 NetAPP file analysis 70 network devices adding 23 network discovery 23 non-windows installation requirements 81 C O configuring Profiler 19 OS device configuration 16 D P data retention policies 39 database backup 18 Profiler 18 deactivating polling 26 defining threshold rules 67 directory analysis rules 72 policy creating 28 editing 29 product feature requests 80 product feedback 80 Profiler architec
rules and alerting 66 creating 65 S T scheduling rules 77 server setup 30 SMI-S Provider Installation 42 CLariion arrays 47 LSI arrays 43 NetApp Ops Mgr 51 status agent 26 storage monitoring 42 sub-groups threshold rules 72 U user accounts adding 20 editing 22 managing 20 overview 20 W web console 41 windows event log rule 71 Index 277
