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

Storage Manager
69
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. Select the NetApp Filers from "Available" box. You can select more than one
by holding the control key while selecting.
3. Select the proxy agent.
4. Click the down arrow to move the NetApp Filers down to the Selected box.
5. Click Save. When you save the change, a push will be scheduled
immediately to update the agent(s) with the changes.
Monitoring Hitachi Data Systems
Hitachi Data Systems Sub-Agents can be defined and assigned to an OS Agent
when the agent is able to communicate to a SMI-S Provider (provided by the
SAN vendor). That SMI-S Provider must be able to communicate with the
Storage Array. A single agent device can monitor multiple Hitachi Data Systems
devices. The Hitachi Data Systems devices that the Hitachi Data Systems Agent
can monitor are:
Hitachi Data Systems (Windows and Solaris Agents only)
3Par, Pillar, IBM SVC
Some Providers are embedded in the device (3par, Pillar, IBM SVC). For these
devices, there is no separate Provider to install
3Par
The 3PAR Provider is embedded into the Storage Array.
• The 3PAR InformOS should be 2.3.1 or later
• Need the userid and password
• Need the array IP Address










