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

174
Index
‘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. EMC did not provide instructions on how to change
this value and per EMC’s instructions ‘let the customer take care of it, he will
know what to do or the storage administrator at that customer site will, it's not
something you should attempt,you don't know the full story with regards to the
san setup.’
Q: Can we use the EMC provider to monitor the CLARiiON behind the
Celerra NS-20 device?
A: Yes, it works the same way as a regular Clariion
Troubleshooting EMC Version 4.0.0 and later
Q: LocalDir/admin no longer works in 4.1.1 provider, did the user name
change?
A: Yes, username for 4.1.1 provider is now admin
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 <install_dir>\symapi\log
• All log files from <install_dir>\ECIM\ECOM\log
• symapi_db.bin file, located <install_dir>\symapi\db
• Output of the ‘dv’ command from the TestSmiProvider utility
• Output of the ‘tms’ command from the TestSmiProvider utility
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:
1. Stop the ECOM Service
2. Navigate to <Install_dir>\ ECIM\ECOM\conf
3. Edit the properties of the file and uncheck “Read-only”, click ok
4. Open the file named port_settings.xml.










