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
Index
147
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.
Note: Before installing the Provider, run netstat to make sure the default ports
are not being used. If another Cimom or IBM Director
(
http://publib.boulder.ibm.com/infocenter/eserver/v1r2/index.jsp?topic=/diricinfo/fq
m0_r_tbs_cimserver_openwbem_port_conflict.html) is running on the machine,
changing the port the Provider listens on will be required for the Provider to run.
Default Namespaces
Vendor Namespace
LSI root/lsissi11
3PAR root/tpd
EMC root/emc
HP root/eva
IBM root/ibm
HDS (versions after 5.8)
root/smis/current
HDS (versions prior to 5.8)
use /root/hitachi/dm<xx> where xx is
version