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
53
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.2) and higher
• Install EMC Solutions Enabler with SMI-S on a
Windows/Linux server with IP connectivity to the
array controllers.
• User account on Navisphere with admin/manager
privileges on the CX array
• For each CX, enable "Statistics Logging" for all
storage processors via Navisphere
• If SMI-S provider is on a server connected to the
SAN being monitored see FAQ-92.
• Note: CX600 arrays – require a Flare code higher
than 16 (2.16.x.x.x) for data to be gathered using
SMI-S
Credentials
Account and password stored in Profiler database and
configuration files on proxy agent using custom encryption
Read/Write
Actions
Read Only
Ports Used
• Configurable: 5988 (HTTP) or 5989 (HTTPS) used
by EMC Solutions Enabler
• Non-configurable: TCP Port 443 bi-direction
between provider and Clariion.
Communication
• See the STM Ports section below.
• Can be HTTP/HTTPS between proxy agent and
EMC Solutions Enabler
HP EVA
Versions/Models
4000, 5000, 6000, 8000
Features
Asset
Storage
Performance
Requires Agent?
No
Requires a Proxy
Agent?
Yes – Windows or UNIX
Prerequisites
• CommandView 8.02 with SMI-S CIMOM installed
is recommended by HP, but CommandView 7.x
will provide asset and storage info.
• EVA8000 requires CommandView 8.0.2 and
Firmware 6200 for Profiler to be able to show array
Performance.