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

72
Using STM
include proxy agent(s)'s IP address to the list
Credentials
• SNMP community string for each FC Switch
• Zoning (v4.8+): Login and Password (telnet) for each
FC Switch
Read/Write
Actions
Read Only
Ports Used
161 UDP on the switch
Communication
See the STM Ports section below
Community String
• SNMP V1 needs to be enabled to collect data from a CISCO switch.
• If the community string is defined from any CISCO Device/Fabric
Manager, then its implicitly for SNMP V3.
•
The community string MUST be defined from the command line.
Storage Manager can monitor any switch (or device) that supports the Fibre
Alliance MIB. Some switches (for example, McDATA) use an alternate MIB,
called the Fibre Channel Management MIB, that provides the same information.
For those switches using this MIB, you must check the McDATA box when
creating the device. If you are unsure, create the device without checking the box
first. If you do not see data after 15-30 minutes, try checking the box and see if
data begins to be collected.
Note: To set up Brocade switches, one has to execute the following
commands to change the SNMP configuration:
• To enable FA MIB:
snmpConfig --set snmpv1
• For access control:
snmpConfig --set accessControl
• To check:
snmpconfig: snmpConfig --show
To configure a McData Fibre Channel Switch Device:
1. On the new device page enter the appropriate values.
• Select Agent: Select the agent you want to monitor the Fibre Channel
• Switch IP Address: Type the IP address of the switch
• Device Display Name: Type a descriptive name for the Fibre Channel
(ex: FC NY1)
• Active: Do not clear this check box, doing so will stop information
collection from the Fibre Channel










