System information
Table Of Contents
- Introduction to SolarWinds Storage Manager powered by Profiler
- Installation
- Storage Manager System Requirements
- Storage Manager Server Installation for Windows
- Installing Storage Manager over an Existing Profiler Deployment
- Clean Install of Storage Manager for Windows
- Installing the Storage Manager Integration Module on your Orion Server
- License Activation
- STM Agent OS Device Configuration
- STM Orion NPM Integration
- Storage Manager Database
- Web Console Navigation
- Server Setup
- Monitoring Storage Arrays
- Backup Profiler
- Monitoring VMware
- VMware Device Requirements
- Configuring VMware
- Application Monitoring
- Gathering Exchange 2003/2007 Storage Data
- Exchange 2003 Clustering:
- Requirements for Gathering Exchange 2003/2007 Mailbox/Attachment Analysis Data
- Adding an Oracle Device
- Requirements
- Procedure:
- Windows:
- For example:
- Linux / Solaris installation:
- For example:
- Configuring an Oracle Device
- Editing an Oracle Configuration
- Reports and Schedules
- Rules & Policies
- Linux Installation
- STM Installation for LINUX
- New Install for Linux Server
- New Install for Linux Agent
- Uninstalling the Linux Server
- Uninstalling the Linux Agent
- Upgrading a Linux Server on an Existing Installation
- Upgrading the Linux Agent on an Existing Installation
- Backup Profiler Requirements
- Installing Agents on Windows Cluster (Windows 2008)
- Appendix
- SMI-S Provider Installation & Configuration
- General SMI-S Questions
- SMI-S Providers
- 3PAR Provider
- Troubleshooting 3PAR
- Dell MD3K Provider
- Dell Compellent
- Troubleshooting Compellent
- EMC Provider (Clariion, Symmetrix, Vmax)
- EMC Provider Version 4.0 and later
- Symmetrix
- CLARiiON Locally Attached
- CLARiiON out-of-band
- Provider Version Pre-4.0.0
- Adding A SAN
- Symmetrix & CLARiiON Out-of-Band
- CLARiiON Locally Attached
- Troubleshooting EMC (All Versions)
- Troubleshooting EMC Version 4.0.0 and later
- Troubleshooting EMC Version Pre-4.0.0
- Hitachi Data Systems (HDS) Provider
- Troubleshooting HDS
- HP Providers
- HP Provider Installation
- HP XP Provider
- HP EVA Provider (Command View)
- Adding Users to HP Groups
- Troubleshooting HP EVA
- Troubleshooting Using the CollectLogs tool
- HP LeftHand
- Finding a Management Node
- Enabling SNMP:
- IBM DS Provider
- IBM Provider Download:
- IBM CIM Agent:
- IBM Provider FAQ:
- Install guides:
- Troubleshooting IBM
- IBM SVC Provider
- Troubleshooting IBM SVC Provider
- LSI Provider
- New Provider (Eagle 2)
- Installation for Windows
- Adding A SAN
- Adding A SAN
- Installation on Linux
- Legacy Provider (Pre-Eagle 2)
- Installation on Windows
- Adding A SAN
- Windows
- Linux
- Obtaining Array Identifier
- SANtricity Storage Manager
- Troubleshooting LSI New Provider Eagle 2
- Troubleshooting LSI Legacy Provider (Pre-Eagle 2)
- OS Embedded Providers
- Solaris
- Pillar Provider
- Troubleshooting Pillar
- Using Support Tool to force a Pilot Failover.
- Sun Storage TEK 99xxSeries Provider
- Sun Storage TEK 2K, 6K & FLX Provider
- SMI-S Provider Tools
- Remote Agent Upgrade Utility
- Performing an Agent Upgrade:
- How to enable SSL login for the STM website
- Installing Local Help Files
- General Troubleshooting
- Index

264
Index
This button serves several purposes:
1. Verifies connectivity to provider by checking:
a. username/password
b. namespace
c. provider ip address
d. provider http/https ports
2) Default enumeration of CIM_ComputerSystem so identifier can be easily
obtained
3) Ability to enumerate on any cim class for verification (like
cim_blockstoragestatisticaldata to know what perf data is avail)
4) If LSI array automatically detect eagle provider and change namespace from
/root/lsissi11 to /root/lsiarray13
When new smi-s device created, you can specify the username, password, and
provider ip, then click the “Confirm Provider”. Once credentials, ip, port verified,
results of the enumeration of cim_computersystem are displayed. You can then
copy/paste the desired identifier in the configuration
TestProvider (CLI interface)
Starting with Profiler version 4.6.1, the Array Identifier can be found using
Profiler. This is also a good way to test connectivity to a provider.
Logging In:
1. Open command prompt.
2. Navigate to mod.sys.smis.Smis_1.0 directory in Profiler.
3. Run following command:
a. TestProvider.bat (for windows)
b. TestProvider.sh (for unix systems)
The scripts will run for both the Profiler Server and Profiler Agent.
For Unix systems, you will first have to make the script executable by issuing:
1. chmod 755 TestProvider.sh
If encountering issues try these steps:
1. Run the TestProvider manually
2. Pre-4.9.0 agent (uses wbemservices cim-client api)
<java bin dir>\java –classpath mod.sys.smis.Smis.jar;.\lib\wbem-
1.1.jar;..\..\lib\core.jar mod.sys.smis.util.TestProvider
3. Post-4.9.0 agent (uses sblim cim-client api)










