Prerequisites to add storage devices

The list of storage devices that are monitored by OpManager and their respective supported models, features supported and prerequisites for monitoring are listed below.

 

SAN Switches Storage Arrays Tape Libraries

 

 

 

Monitoring Brocade switches & directors

OpManager provides monitoring and management of Brocade silkworm switches and directors.

Models Supported

  • Brocade SilkWorm switches
    • SilkWorm 4100
    • SilkWorm 4102
  • All the rebranded models or OEM models are supported.

Features Supported

  • Inventory information for switch & switch ports
  • Switch ports monitoring
  • Reports:
    • Switch zoning configuration report
    • Availability reports for switch & switch ports
    • Performance reports for switch Ports
      • Bandwidth Utilization
      • Errors
      • Rx Traffic
      • Rx Utilization
      • Tx Traffic
      • Tx Utilization
    • Switch summary reports
  • Real time graphs for trouble shooting
  • SNMP trap based alarms
  • Launch of telnet/applet brocade client for configuration

Prerequisites for Monitoring

  • Ensure SNMP agent is running in the Brocade silkworm switch/director.
  • By default, OpManager uses SNMP port 161 and read community 'public' for discovery. If your settings are different , please provide the same in the OpManager web-client while adding Switch.
  • Ensure that the IP of the server running OpManager is included in the the SNMP access list of the Brocade Switch.
    • The following command can be used to know the snmp community & access list configurations in brocade silkworm switches.
      Run the command agtcfgdefault via CLI  console of the switch.
      Details: Refer the "Brocade Fabric OS Reference Manual"
  • Register OpManager server IP address as a trap destination for the Brocade Silkworm Switch.
    • Use agtcfgset command in the Brocade Fabric OS command line interface to specify the Trap Recipient.

Note: For more details refer the Brocade Fabric OS Reference Manual

Note: In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try re-adding the device.

 

Monitoring McData switches / directors

OpManager provides monitoring and management of McData switches and directors like Sphereon / Intrepid etc.

Models Supported

  •  Sphereon 4500 Fabric Switch
  •  Sphereon 3216 Fabric Switch
  •  Sphereon 3232 Fabric Switch
  •  ES-3016 switch
  •  ES-3032 switch
  •  ES-1000 switch
  •  Intrepid 6064 Director
  •  Intrepid 6140 Director
  •  ED-6064 director
  •  ED-5000 director

Features Supported

  • Complete inventory information for switch & switch ports
  • Switch ports monitoring
  • Reports:
    • Availability reports for switch & switch ports
    • Performance reports for switch Ports
      • Errors
      • Rx Traffic
      • Rx Throughput
      • Tx Traffic
      • TxThroughput
      • Total Throughput
    • Switch Port summary reports
  • Real time graphs for trouble shooting
  • SNMP trap based alarms
  • Launch of Telnet/web client for configuration

Prerequisites for Monitoring

  • Ensure SNMP agent is running in the McData switch / director. McData Switch SNMP information can be checked in the McData Switch's Web-based  interface -> Configure (option)  -> SNMP  (option).
  • By Default, OpManager uses SNMP port 161 and read community 'public' for discovery. If your settings are different , please provide the same in the OpManager web-client while adding Switch.
  • Register OpManager server IP address as trap destination.
  • For details refer Configure SNMP section in the McData Switch Product Manager user manual.

Note: In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try readding the device.

 

Monitoring EMC switches / directors

OpManager provides monitoring and management of EMC switches and directors.

Models Supported

  • EMC Connectrix switches
  • EMC Connectrix directors

Features Supported

  • Inventory information of switch & switch ports
  • Switch ports monitoring
  • Reports:
    • Availability reports for switch & switch ports
    • Performance reports for switch Ports
      • Errors
      • Rx Traffic
      • Rx Throughput
      • Tx Traffic
      • Tx Throughput
      • Total Throughput
    • Switch Port summary reports
  • Real time graphs for trouble shooting
  • SNMP trap based alarms
  • Launch of Telnet/Applet EMC client for configuration

Prerequisites for Monitoring

  • Ensure SNMP agent is running in the EMC Switch / director.
  • By default, OpManager uses SNMP port 161 and read community 'public' for discovery. If your settings are different, please provide the same in the OpManager web-client while adding Switch.
  • Register OpManager server IP address as a trap destination for the EMC Switch.

Note: In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try re-adding the device.

 

Monitoring Cisco MDS switches / directors

OpManager provides monitoring and management of Cisco MDS 9000 Series SAN Switches.

Models Supported

  • Cisco MDS 9000 Series Switches such as Cisco MDS9216i
  • Cisco SN 5428-K9 Storage Router

Features Supported

  • Inventory information of switch & switch ports
  • Cisco VSAN information
  • Switch ports monitoring
  • Reports:
    • Availability reports for switch & switch ports
    • Performance reports for switch Ports
      • Bandwidth Utilization
      • Port Frame Error Rate
      • Port In Drop Rate
      • Port Out Drop Rate
      • Rx Utilization
      • Rx Throughput
      • Tx Utilization
      • Rx Throughput
      • Total Throughput
    • Switch Port summary reports
  • Real time graphs for trouble shooting
  • SNMP trap based alarms
  • Remote launch of CLI to facilitate device configuration

Prerequisites for Monitoring

  • OpManager by default uses 'public' snmp community for discovery. This community should have read access right. In case your read community is different , please provide the same in the OpManager web-client while adding Switch.. You can check the community names (and their access rights) configured in your MDS switch by issuing the command "show snmp community" via telnet to switch
    • To set the access rights for a community in your cisco switch , you need to do the following ,
      • Go to config mode , by typing the command ,
        • config t
      • Set the snmp community by typing the command,
        • snmp-server community <community> <rw | ro>
          • For example, to set read-only access right to "public" community you can type ,
            • snmp-server community public ro
  • Register OpManager server IP address as a trap destination for the Cisco Switch.
    • Check if the server running OpManager is registered as a trap destination in the switch by issuing the command "show snmp host" via telnet to switch. This should have an entry with OpManager server IP and port 162
    • If entry is not available, use snmp-server host <host_address>traps command to specify Trap Recipient.

Note: For more details check Cisco MDS 9000 Family Command Reference Guide.

Note: In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try re-adding the device.

 

Monitoring QLogic switches

OpManager provides monitoring and management of QLogic SANbox switches.

Models Supported

  • SANbox2-64
  • SANbox 5600
  • SANbox 5200
  • SANbox 3050
  • SANbox Express 1400

Features Supported

  • Inventory information of switch & switch ports
  • Switch ports monitoring
  • Reports:
    • Availability reports for switch & switch ports
    • Performance reports for switch Ports
      • Errors
      • Tx Traffic
      • Rx Traffic
      • Tx Throughput
      • Rx Throughput
      • Total Throughput
    • Switch port summary reports
  • Real time graphs for trouble shooting
  • SNMP trap based alarms
  • Launch of telnet / QLogic client for configuration

Prerequisites for Monitoring

  • Ensure SNMP agent is running in the QLogic SANbox Switch. To view the SNMP settings, use the QLogic Switch telnet command "show setup snmp". For any changes use "set setup snmp". (Refer "QLogic Switch Management User’s Guide" for details.)
  • OpManager by default, uses snmp port 161 and read community 'public' for discovery. If your settings are different , please provide the same in the OpManager web-client while adding Switch.
  • Register OpManager server IP address as a snmp trap destination for the QLogic Switch.

Note: In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try readding the device.

 

Monitoring HP switches / directors

OpManager provides monitoring and management of HP Storageworks switches and directors.

Models Supported

  • HP storageworks switches
  • HP storageworks directors

Features Supported

  • Inventory information for switch & switch ports
  • Switch ports monitoring
  • Reports:
    • Switch zoning configuration report
    • Availability reports for switch & switch ports
    • Performance reports for switch Ports
      • Errors
      • Rx Traffic
      • Rx Throughput
      • Tx Traffic
      • Tx Throughput
      • Total Throughput
    • Switch Port summary reports
  • Real time graphs for trouble shooting
  • SNMP trap based alarms
  • Launch of telnet/applet HP client for configuration

Prerequisites for Monitoring

  • Ensure SNMP agent is running in the HP storageworks switch / director.
  • By default, OpManager uses snmp port 161 and read community 'public' for discovery. If your settings are different , please provide the same in the OpManager web-client while adding Switch.
  • Register OpManager server IP address as a trap destination for the HP StorageWorks Switch.

Note: In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try readding the device.

 

Monitoring IBM ESS Shark Storage Systems

OpManager provides monitoring and management of IBM ESS Shark series storage systems.

Models Supported

  • DS6000 Series
  • DS8000 Series
  • ESS 2105-800
  • ESS 2105-750
  • ESS 2105-F20

Features Supported

  • Inventory information of physical components
    • Array Controllers, Array controller Ports
    • Disk Drives
  • Logical configuration details
    • Storage Pools
    • Storage Volumes
    • Intercocnnects Info
  • Monitoring
    • Array system status
    • Array controller status
    • Disk drive status, Storage Pools Status, Storage Volumes status
  • Reports:
    • Availability reports for storage system, RAID controller & RAID controller ports

Prerequisites for Monitoring

  • OpManager uses the IBM Common Information Model (CIM) Agent for ESS to monitor the IBM ESS Shark Array
  • The IBM ESS CIM agent can be installed on any server that is pingable from the server where OpManager is installed.
  • IBM CIM agent install requires esscli utility is already installed in the server
  • Install the necessary software from the OEM website.
  • Disable DigestAuthentication by setting DigestAuthentication flag to false in cimom.properties file
    Note : Default directory is C:\Program Files\IBM\cimagent
  • Start the ESS Provider service CIM Object Manager - DS Open API from the Windows services menu
  • Ensure that, OpManager installed host and the Storage system has a Fibre Channel Connectivity.

Note: In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try re-adding the device.

 

Monitoring HP Modular Storage Arrays

OpManager provides monitoring and management of HP Modular Storage Arrays.

Models Supported

  • HP MSA 1000
  • HP MSA 1500

Features Supported

  • Inventory information of physical components ,
    • Array Controllers, Array controller Ports
    • Disk Drives
  • Logical configuration details
    • Storage Pools
    • Storage Volumes
    • Intercocnnects Info
  • Monitoring
    • Array system status
    • Array controller status
    • Disk drive status, Storage Pools Status, Storage Volumes status
  • Reports:
    • Availability reports for storage system, RAID controller & RAID controller ports

Prerequisites for Monitoring HP MSA Array

  • OpManager uses the HP SMI-S MSA Provider based on SNIA standard to monitor the HP MSA
  • The MSA provider can be installed on any server running Microsoft Windows 2000 or Windows 2003 Server.
  • This server must have a path through the SAN to the MSA devices that will be managed.
  • Also the server must be reachable from the server where OpManager is installed.
  • Install the necessary software from the OEM website.
  • Ensure that MSA firmware version is compatible with the installed SMI-S provider (latest download corresponds to SMI v1.0.3).
  • Start the MSA Provider service hp StorageWorks SMI-S CIMOM from the Windows services menu.

Note: In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try readding the device.

 

Monitoring HP StorageWorks Enterprise Virtual Array

OpManager provides monitoring and management of HP StorageWorks Enterprise Virtual Array.

Models Supported

  • HP StorageWorks EVA 3000,4000,5000,6000,8000

Features Supported

  • Inventory information of physical components
    • Raid Controllers
    • Raid Controller Ports
    • Disk Drives
  • Logical configuration details
    • Storage Volume
    • Storage Pool
    • Interconnects Info
  • Monitoring
    • Disk Drive status
    • Raid Controller status
    • Raid Controller Port status
  • Reports:
    • Performance reports for HP EVA arrays (via evaperfutil utility)
      • Array Statistics
        • Total Host Req/s, Total Host MB/s
      • Array Controller Statistics
        • CPU %, Data %
      • Virtual Disks
        • Read Hit MB/s, Read Hit Latency(ms), Read Hit Req/s, Read Miss Req/s, Read Miss MB/s, Read Miss Latency, Write Req/s, Write MB/s, Write Latency(ms), Flush MB/s, Mirror MB/s,
      • Host Port Statistics
        • Read Req/s, Read MB/s, Read Latency(ms), Write Req/s, Write MB/s, Write Latency (ms), Av. Queue Depth
      • Physical Disks
        • Disk Queue Depth, Drive Latency(ms), Read Req/s, Read MB/s, Read Latency (ms), Write Req/s, Write MB/s, Write Latency(ms)
      • Physical Disk Groups
        • Total Read Req/s, Total Read MB/s, Average Read Latency(ms), Total Write Req/s, Total Write MB/s, Average Write of Latency(ms), Total Flush Bytes, Total Mirror Bytes, Total Prefetch Bytes
    • Availability reports for Raid Controller & Raid Controller ports
  • Threshold monitoring for Disk Drive Temperature , Power Supply status

Prerequisites for Monitoring HP StorageWorks EVA

OpManager monitors HP EVA based on the Command View EVA(CV EVA) version installed in the your environment.

A) SSSU Installation Instructions

OpManager uses SSSU (Storage System Scripting Utility) available as part of HP StorageWorks Windows Kit for Enterprise Virtual Array installation.

  • This needs to be installed in the server where OpManager is installed and running
  • Ensure that "SSSU.exe" is included in the PATH environment variable in the server in which OpManager is installed. (You can check this by executing SSSU.exe in a command prompt which will print the version) .

Note: In case your current SSSU version is higher (say 5.0) , you need to download SSSU.exe (Version 4.0) and include it in the %PATH%. For this you may follow the steps below,

  1. Open the HP software download URL, HP Software Download Page
  2. Click on "HP StorageWorks Command View EVA V4.0 Media Kit". This will open a page which lists the supported Operating Systems
  3. Click on the operating system corresponding to the server running OpManager (Example: Windows 2003)
  4. Click on the "Download" button corresponding to the "HP StorageWorks Storage System Scripting Utility (SSSU) v4.0". This will download SSSU.exe

Steps to add the HP EVA into OpManager (using SSSU)

    • After including SSSU utility in the %PATH% environment variable, restart OpManager (shutdown & start). This is required for the Environment PATH settings to take effect.
    • In the OpManager browser client go to Admin tab --> Manage Storage Devices option.
    • In the "IP Address" field enter the Management_Appliance_IP_address (The IP address of the HP Management Appliance that is managing the HP EVA array)
    • Choose Device Type as Raid
    • Choose Vendor as HP
    • Choose Model as "EVA(Below 6.0)"
    • Provide the Administrator Username, Password and the Community String
    • Click on Add Device.

B) EVA SMI Provider Installation Instructions

  • OpManager uses the HP SMI-S EVA Provider (SNIA standard) to monitor the HP EVA (Command View EVA version 6.0.2 and above)
    The HP SMI-S EVA Provider is integrated with Command View EVA.
  • Install the necessary software from the OEM website.
  • Ensure that EVA firmware version is compatible with the installed SMI-S provider
  • Check the SMI service say like, HP StorageWorks SMI-S CIMOM or HP StorageWorks CIM Object Manager is listed in Windows Services of the Command View EVA Host.
  • Now start the service

    Steps to add HP EVA into OpManager (using SMI-S)

    • Ensure that SMI provider is properly started and is listed in Windows Services Panel
    • Restart OpManager (shutdown & start). This is required for the Environment PATH settings to take effect.
    • In the OpManager client go to Admin Tab -->Manage Storage Devices
    • Provide IP Address of the host  in which SMI-S Provider is running
    • Choose Device Type, Vendor and Model as RAID, HP and EVA(Above 6.0) respectively
    • In Username field enter the EVA Provider username
    • In the Password field enter the EVA Provider password
    • Provide the Port number at which the CIM Agent is running(5989 or 5988)
    • Choose whether the SSL should be Enabled(https) or Disabled(http)
    • Provied the name space (by default root/eva)
    • Change the Timeout if needed.
    • Click on Add Device

Note: If the Ping option is disabled for the device, then please uncheck 'Ping the given IP' field.
Note: In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try readding the device. 

C) evaperf Installation Instructions

For Performance monitoring, evaperf utility needs to be installed in the server running OpManager.

Ensure that, the evaperf utility installed host and the CommandView EVA running host are connected via Fibre Channel.

  1. Include evaperf in the PATH environment variable
  2. Ensure that the installed EvaPerf utility is compatible with EVA firmware version.
  3. Ensure that evapdcs (EVA Performance Data Collection Service) is installed along with evaperf by executing the command "evapdcs -v"
    • If it prints "evapdcs is currently installed" , you may check its startup status in the Windows "Services" menu . This service is registered with the name "HP EVA Performance Data Collector". (If the status is "disabled", it indicates that it is in an improper state and you will need to restart the host server once and then check the above again)
    • In case the above command prints "evapdcs not installed" , install evapdcs via the following command evapdcs -i -m
  4. The server running OpManager needs to be registered to the Command View EVA server via , "evaperf fnh [hostname] [username] [password]"
    hostname - CVE host name , username - CVE username , password - CVE password
  5. OpManager uses EVA name (known as friendly name in EVA terminology ) to issue evaperf commands. For this the EVA name - WWN mapping needs to be registered via "evaperf fn" command
  6. If the EVA is password protected, the EVA password needs to be registered for the respective EVA WWN via "evaperf spw array_WWN array_Password" command
  7. You can check if evaperf is able to fetch valid data by entering the following command in the OpManager/ directory ,
    • evaperf all -sz <EVA Name> -csv -nots (This will automatically start evapdcs service, if it is not started already) . This should print all the EVA performance statistics (for Array, VDisk , Disk etc). 
    • The sample output should look similar to the one given below : CPU %,Data %,Ctlr,Serial,Node
      82,81,A,V8398ADVBP2003,5065-1FD1-5021-8781
      94,99,B,V8398ADVHV200D,5060-1FF1-5031-8582

Note: Installation details for evaperf are available in the HP StorageWorks Command View EVA installation guide.

 

Monitoring EMC CLARiiON Networked Storage System

OpManager provides monitoring and management of EMC CLARiiON Networked Storage Systems.

Models Supported

  • CX Series like CX3-20, CX3-40, CX3-80, CX300, CX500, CX700 & CX800
  • FC Series like FC4700

Features Supported

  • Inventory information of physical components ,
    • Storage Processor (SP)
    • SP Ports
    • Disk Drives
  • Logical configuration details
    • LUNs
    • RaidGroups
    • Host-Port mapping
    • InterConnects Info
  • Monitoring
    • SP status
    • SP Port status
    • Free space of Disk Drives / Raid Groups /LUNs
  • Reports:
    • Performance
      • Storage Processors
        • Utilization, Total Bandwidth, Total throughput, Read Bandwidth, Read Size, Read throughput, Write Bandwidth, Write Size, Write throughput, Dirty Pages, Flush Ratio, Mbs Flushed, Idle Flush On, High Water Flush On, Low water Flush Off, Write Cache Flushes
      • Disk Drives
        • Total Bandwidth, Total throughput, Read Bandwidth, Read Size, Read throughput, Write Bandwidth, Write Size, Write throughput, Disk Service Time
      • LUNs
        • Read Bandwidth, Read Size, Read throughput, Write Bandwidth, Write Size, Write throughput, Read Cache Hits, Read Cache Hit Ratio, Write Cache Hits, Write Cache Hit Ratio, Forced Flushes.
    • Availability reports for SP & SP ports
  • SNMP trap based alarms

Prerequisites for Monitoring EMC CLARiiON

  • NaviCLI should be installed in the server in which OpManager is installed.
  • Include the directory containing NaviCLI.exe in the PATH environment variable. (This is normally C:\Program Files\EMC\Navisphere CLI\ ).
  • Ensure that OpManager is restarted (shutdown & started) after including NaviCLI in the path. This is required for the latest path changes to take effect for OpManager.
  • Now open a command prompt to execute the navicli command to check for the proper response from EMC CLARiiON RAID.
    • Command: navicli -h <array name> getall
  • For Performance monitoring, please ensure that setStats flag is enabled. You can enable the same using NaviCLI command
    • Command : NaviCLI -h <array-ip> setstats -on

Note: In case the device is not discovered, then the probable reasons for non-discovery are displayed in the client. Please go through the instructions and try re-adding the device.

 

Monitoring Infortrend EonStor Storage System

OpManager provides monitoring and management of Infortrend EonStor Storage System.

Models Supported

EonStor storage systems such as,

  • A16F-G2422
  • A24F-R2224
  • A24F-G2224
  • A16F-R2221
  • A16F-G2221
  • A16F-R/S1211
  • A12F-G2221
  • A08F-G2221
  • A16U-G2421
  • A12U-G2421
  • A08U-G2421
  • A08U-C2412
  • A08U-C2411
  • U12U-G4020
  • F16F-R/S2021
  • F12F-G2A2
  • FF-R/S2021-4/6
  • S16F-R1430
  • S16F-G1430
  • All the rebranded models or OEM models are supported.

Features Supported

  • Inventory information of physical components ,
    • RAID Controllers
    • RAID Controller  Ports
    • Channels
    • Disk Drives
  • Logical configuration details
    • LUNs
    • Raid Partitions
    • Logical Volumes
    • Logical Drives
  • Monitoring
    • RAID Controller status
    • RAID Controller port status
    • Fan, Power supply, UPS,  Battery, Temperature Sensor, Voltage status, Door status, Speaker status
  • Reports:
    • Performance
      • CurrentQueuedIOCount,CurrentLunNumber,CurrentAccessDelayTime
      • CurrentTagCount,CurrentIOTimeOut,CurrentDriveCheckPeriod
      • CurrentSAFTEPollingPeriod,CurrentAutoDetectPeriod
    • Availability reports for storage system, RAID Controller & RAID Controller ports

Prerequisites for Monitoring

  • Ensure SNMP agent is running.
  • Register OpManager server IP address as trap destination

Note : In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try re-adding the device.

 

Monitoring NetApp Primary Storage series

OpManager provides monitoring and management of NetApp Primary Storage series System.

Models Supported

  • FAS series like ,
    • FAS200
    • FAS250
    • FAS270
    • FAS270c
    • FAS3000
    • FAS 920
    • FAS920c
    • FAS940
    • FAS940c
    • FAS960
    • FAS960c
    • FAS980
    • FAS980c
    • FAS3000
    • FAS3020
  • F-500, F-600 & F-700 series like ,
    • F825c
    • F825
    • F210
    • F230
    • F520
    • F630
    • F720
    • F740
    • F760
  • C Series like ,
    • C1200
    • C2100
    • C6200

Features Supported

  • Discovers and displays NetApp Raid information including status parameters such as Global Status, Fan / Power supply status
  • Monitors Volume  usage  including snapshots
  • Monitors cluster status information when deployed in cluster configuration
  • Receives SNMP Traps covering over 75 system and threshhold alerts
  • Performance graphs
    • NFS/CIFS Ops/sec
    • NetRx/Tx Throughput
    • Disk Read Writes / sec  , Tape Read Writes  / sec
    • CacheAge

Prerequisites for Monitoring

  • Ensure SNMP agent is running.
  • Register OpManager server IP address as trap destination

Note: In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try re-adding the device.

 

Monitoring Hitachi HDS Lightning 9900V series storage systems

OpManager provides monitoring and management of HDS Lightning 9900V series storage System.


Models Supported

  • Hitachi HDS Lightning 9900V series storage systems such as HDS Lightning 9970V & HDS Lightning 9880V 
  • NSC55

Features Supported

  • Inventory information of physical components
    • Disk Controllers, Disk Units, Disk Processor
    • Port Details
  • Logical configuration details
    • LUNs
    • LUN Host Mapping
  • Monitoring
    • Disk Controller status
    • Disk Unit status
    • Port Status
  • Reports:
    • Availability reports
    • Capacity Summary
  • Monitoring and alarm generation for faulty conditions (via SNMP traps)

Prerequisites for Monitoring

  • Ensure SNMP agent is running.
  • Register OpManager server IP address as trap destination

Note : In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try re-adding the device.

 

Monitoring Hitachi HDS Thunder 9500V series storage systems

OpManager provides monitoring and management of HDS Thunder 9500V series storage system.

Models Supported

  • Hitachi HDS Thunder 9500V series storage systems such as HDS Thunder 9570V & HDS Thunder 9585V
  • Hitachi HDS TagmaStore

Features Supported

  • Inventory information of physical components ,
    • RAID Controller
    • RAID Controller Ports
  • Logical configuration details
    • LUNs
    • LUN Host Mapping
    • Interconnects Info
  • Monitoring
    • RAID Controller status
    • RAID Controller Port status
  • Reports:
    • Performance
      • LUNs
        • ReadCommandNumber,ReadHitNumber, ReadHitRate
        • WriteCommandNumber,WriteHitNumber,WriteHitRate
    • Availability reports for RAID, RAID Controller & RAID Controller ports
  • Monitoring and alarm generation for faulty conditions (via SNMP traps)
    • Controller blockade
    • Drive blockade
    • Internal FCAL Loop failure
    •  NAS server / path failures.
    • Battery/Fan alarms.
    • Other alarms defined in MIB

Prerequisites for Monitoring

  • Ensure SNMP agent is running.
  • Register OpManager server IP address as trap destination
  • Refer the SNMP Agent Support Function user guide of Hitachi Freedom Series Thunder 9500 V Series for agent installation and configuration detail.

Note: In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try re-adding the device.

 

Monitoring IBM FastT, DS4000 Storage Systems

OpManager provides monitoring and management of IBM FastT / DS4000 series storage systems

Models Supported

  • IBM FastT series
  • IBM DS4000 series

Features Supported

  • Inventory information of physical components
    • RAID, RAID Controller, RAID Controller Ports
    • Disk Drives
    • Tray/Enclosure Component Health Information
  • Logical configuration details
    • VolumeGroups
    • Volumes
    • VolumeLUN Mappings
    • Host Groups
    • Interconnects Info
  • Monitoring
    • RAID status
    • RAID  Port status
    • Status of Volume Groups, Volumes & Disk Drives
  • Reports:
    • Performance reports for DS4000 / IBM FastT Storage arrays
      • Includes reports for Controllers, Volumes and Array for the following stats (via SMcli utility),
        • Total IO Count
        • Read Percentage
        • Cache Hit Percentage
        • Current Data Transfer Rate
        • Maximum Data Transfer Rate
        • Current IO Count
        • Maximum IO Count
    • Availability reports for storage system, RAID controller & RAID controller ports
  • Alarms
    • SNMP trap based alarms
    • Status alerts for Disk Drives, Volume Groups & Volumes

Prerequisites for Monitoring

  • OpManager uses command line utility (SMcli.exe) available as part of IBM FastT / DS4000 Storage Manager installation
  • Ensure that SMcli is installed in the server in which OpManager is installed.
    • Include the directory containing SMcli.exe in the PATH environment variable.
      • By default for Windows Servers this is C:\Program Files\IBMFastT\client\
      • By default for UNIX Servers this is /opt/IBMFastT/client/
  • Ensure that OpManager is restarted (shutdown & started) after including SMcli in the path
  • Register OpManager server IP address as snmp trap destination.
  • Ensure that the OpManager installed server and the Storage system are connected via Fibre Channel.

Note: In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try readding the device.

 

Monitoring StorageTek Storage Systems

OpManager provides monitoring and management of StorageTek B-series & D-series storage systems.

Models Supported

  • D Series
  • B Series
  • Flexline 200 series
  • Flexline 300 series

Features Supported

  • Inventory information of physical components ,
    • RAID, RAID Controller, RAID Controller Ports
    • Disk Drives
    • Tray/Enclosure Component Health Information
  • Logical configuration details
    • VolumeGroups
    • Volumes
    • VolumeLUN Mappings
    • Host Groups
    • Intercocnnects Info
  • Monitoring
    • RAID status
    • RAID  Port status
    • Status of Volume Groups, Volumes & Disk Drives
  • Reports:
    • Performance reports for StorageTek /LSI Storage arrays
      • Includes reports for Controllers, Volumes and Array for the following stats (via SMcli utility),
        • Total IO Count
        • Read Percentage
        • Cache Hit Percentage
        • Current Data Transfer Rate
        • Maximum Data Transfer Rate
        • Current IO Count
        • Maximum IO Count
    • Availability reports for storage system, RAID controller & RAID controller ports
  • Alarms
    • SNMP trap based alarms
    • Status alerts for Disk Drives, Volume Groups & Volumes

Prerequisites for Monitoring

  • OpManager uses command line utility (SMcli.exe) available as part of SANtricity Storage Manager Client installation
  • Ensure that SMcli is installed in the server in which OpManager is installed.
    • Include the directory containing SMcli.exe in the PATH environment variable.
      • By default for Windows Servers this is C:\Program Files\SM8\client\
      • By default for UNIX Servers this is /opt/SM8/client/
  • Ensure that OpManager is restarted (shutdown & started) after including SMcli in the path
  • Register OpManager server IP address as SNMP trap destination.
  • Ensure that, OpManager installed host and the Storage system has a Fibre Channel Connectivity.

 

Monitoring SUNStorEdge Systems

OpManager provides monitoring and management of SUN StorEdge systems.

Models Supported

  • SUN StorEdge 6920
  • SUN StorEdge6120

Features Supported

  • Inventory information of physical components ,
    • Disk Drives
    • Storage Volumes, Storage Pools
    • Ports info
  • DSP information
    • Disk Drives
    • Volumes
    • Domains
    • SCSI info
    • Ports info
  • Monitoring
    • Drive status
    • Storage pool status, Storage volume status
    • Domain status
    • Port status
  • Reports:
    • Performance reports for StorageTek /LSI Storage arrays
      • Includes reports for Controllers, Volumes and Array for the following stats (via SMcli utility),
        • Total IO Count
        • Read Percentage
        • Cache Hit Percentage
        • Current Data Transfer Rate
        • Maximum Data Transfer Rate
        • Current IO Count
        • Maximum IO Count
    • Availability reports for storage system, RAID controller & RAID controller ports
  • Alarms
    • SNMP trap based alarms
    • Status alerts for Disk Drives, Volume Groups & Volumes

Prerequisites for Monitoring

  • OpManager uses command line utility (SMcli.exe) available as part of SANtricity Storage Manager Client installation
  • Ensure that SMcli is installed in the server in which OpManager is installed.
    • Include the directory containing SMcli.exe in the PATH environment variable.
      • By default for Windows Servers this is C:\Program Files\SM8\client\
      • By default for UNIX Servers this is /opt/SM8/client/
  • Ensure that OpManager is restarted (shutdown & started) after including SMcli in the path
  • Register OpManager server IP address as SNMP trap destination.
  • Ensure that, OpManager installed host and the Storage system has a Fibre Channel Connectivity.

Note : In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try readding the device.

 

Monitoring Areca ARC Storage System

 

OpManager provides monitoring and management of Areca ARC Storage System

Models Supported

  • ARC Series like ARC-5010, ARC-6010, ARC-6020.

Features Supported

  • Inventory information of physical components ,
    • RAID Controller
    • Disk Drives
  • Logical configuration details
    • Raid Set
    • Volume Set
  • Monitoring
    • Disk Drive state
    • Raid Set state
    • Volume Set state
    • Power Supply state
    • Disk Drive temperature
  • Reports:
    • Availability reports for RAID Controller.
  • SNMP trap based alarms

Prerequisites for Monitoring Areca ARC

  • Ensure SNMP agent is running.
  • Register OpManager server IP address as trap destination.

Note: In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try readding the device.

 

Monitoring EMC Centera Storage System


OpManager provides monitoring and management of EMC Centera Storage Systems.

Features Supported

  • Inventory information of physical components ,
    • Centera Clusters
    • Centera Nodes (Access & storage)
    • Centera Internal Switches
  • Logical configuration details
    • CenteraClusterPools
    • CenteraProfiles
  • Monitoring
    • Centera HeartBeat
    • Cluster status
    • Node status
    • Free space of Clusters / Nodes
  • Reports:
    • Availability reports for Cluster
  • SNMP trap based alarms

Prerequisites for Monitoring EMC Centera

  • OpManager uses CLI interface to monitor EMC Centera
  • Ensure that CenteraCLI software is installed in the server in which OpManager is installed (By default this is C:\Program Files\EMC\Centera\2_4\SystemOperator\lib)
  • Copy the following jars to {OpManager Install Dir/classes/ directory.
    • C:\Program Files\EMC\Centera\2_4\SystemOperator\lib\CenteraViewer.jar
    • C:\Program Files\EMC\Centera\2_4\SystemOperator\_jvm\lib\jsse.jar
  • Ensure that OpManager is restarted (shutdown & started) after copying these JAR files.

Note: In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try re-adding the device.

 

Monitoring HP EML and ESL Tapelibraries in SAN / NAS networks

OpManager provides monitoring and management of HP EML and ESL Tapelibraries.


Models Supported

  • HP EML E-Series
  • HP ESL E-Series

Features Supported

  • Inventory information
    • Tape library
    • Tape Drive status
    • Chassis Info
    • Fibre Channel ports
    • Storage Media details
    • Media Access Device
  • Monitoring
    • Tape library status
    • Tape drive status
    • Drive port status
    • Changer device status
  • Reports:
    • Availability reports for Tape library

Prerequisites for monitoring HP EML / ESL Tapelibrary

  • OpManager uses the HP SMI-S TL Provider to monitor the HP Tape Libraries
  • The TL provider can be installed on any server running Microsoft Windows 2000 / Windows 2003 / Windows XP / Windows Professional.
  • This server must have a path through the SAN to the TL devices that will be managed.
  • Also the TL Provider installed server must be pingable from the server where OpManager is installed.
  • Install the necessary software from the OEM website.
  • Start the TL Provider service hp StorageWorks SMI-S CIMServer from the Windows services menus

Note: In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try re-adding the device.

 

Monitoring Dell PV - PowerVault tape libraries

OpManager provides monitoring and management of Dell PV series tape libraries like DELL PV 132T & Dell PV 136T


Models supported

  • DELL PV132T
  • DELL PV136T

Features Supported

  • Inventory information of physical components ,
    • Tape Drives
  • Logical configuration details
    • Movers
  • Monitoring
    • Tape library status
    • Tape drive status
    • Mover status
  • Reports:
    • Availability reports for Tape library .
  • Monitoring and alarm generation for faulty conditions (via SNMP traps)
    • Tape library state
    • Door state
    • MailBox state
    • Error notification
    • Shutdown notification
    • Service Action Code (SAC) notification

Prerequisites for Monitoring

  • In the RemoteManagementUnit (RMU) ensure that the SNMP agent is running.
  • Register OpManager server IP address as trap destination
  • Check if the community name is configured as public
  • To ensure this check the value of Public Name under Configuration tab-->SNMP Configuration area. Note: If a different community is used, it needs to be specified when you add the device via OpManager
  • Details are available  in ADIC Scalar 100 User's Guide (Dell PV 136T is essentially a rebranded version of ADIC scalar 100 tape library)

Note : In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try readding the device.

 

Monitoring IBM 3584 / TS 3500 tape libraries

OpManager provides monitoring and management of IBM 3584 / TS 3500 Tape Libraries.


Models Supported

  • IBM 3584
  • TS 3500
  • IBM ULT3582

Features Supported

  • Inventory information of physical components
    • Chassis details
    • Changer Device details
    • Library Fibre Channel Port details
    • Library SCSI Controllerdetails
    • Storage Media details
    • Media Access Device
  • Monitoring
    • Tape Library status
    • SCSI Controller status
    • Changer Device status
    • Media Access Device status
  • Reports:
    • Availability reports for Tape library , Media Access Device
  • Monitoring and alarm generation for faulty conditions (via SNMP traps)

Prerequisites for monitoring IBM 3584 / TS 3500 Tapelibrary

  • Ensure that the SNMP agent is enabled in the tape library before adding the device via OpManager web-client .
    The details are available in the "IBM 3584 Planning & Operator Guide" in "Chapter 4 Advanced Operating Proceedures --> Selecting the Network Settings".
  • Register OpManager server IP address as trap destination.

Note : In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try readding the device.

 

Monitoring Overland Neo series tape libraries

OpManager provides monitoring and management of Overland Neo series tape libraries like Overland Neo 2000, Overland Neo 4000.


Models Supported

  • Overland Neo series tape libraries like 
    • Overland Neo 2000
    • Overland Neo 4000

Features Supported

  • Inventory information of physical components ,
    • Tape Drives
  • Logical configuration details
    • Library Modules (Master module / Slave module)
  • Monitoring
    • Tape library status
    • Tape drive status
    • Library Module status
  • Reports:
    • Availability reports for Tape library.
  • Monitoring and alarm generation for faulty conditions (via SNMP traps)
    • Tape library state
    • Door state
    • Mail Slot state
    • Power supply state
    • Tape drive state
    • Tape drive cleaning state
    • Library Module state

Prerequisites for monitoring Overland Neo series

  • Ensure that the SNMP agent is running.
  • Register OpManager server IP address as trap destination

Note: In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try re-adding the device.

 

Monitoring ADIC Scalar i2000 & 100 tape libraries

OpManager provides monitoring and management of ADIC Scalar i2000 & Scalar 100 tape libraries

 

Features Supported For ADIC Scalar i2000

  • Complete inventory information of physical components
    • Tape Library
    • Tape Drives
  • Monitoring
    • Tape library status
    • Tape drive status
  • Reports:
    • Availability reports for Tape library
  • Monitoring and alarm generation for faulty conditions (via SNMP traps)
    • Sensor state change (Voltage, Temperature, Cooling)
    • Tape library state change
    • Tape drive added/removed
    • Media mounted /unmounted

Features Supported For ADIC Scalar 100

  • Complete inventory information of physical components ,
    • Tape Library
    • Tape Drives
  • Logical configuration details
    • Library partitions
    • Movers
  • Monitoring
    • Tape library status
    • Tape drive status
    • Mover status
  • Reports:
    • Availability reports for Tape library
  • Monitoring and alarm generation for faulty conditions (via SNMP traps)
    • Tape library state
    • Door state
    • MailBox state
    • Error notification
    • Shutdown notification
    • Service Action Code (SAC) notification

Prerequisites for Monitoring ADIC Scalar 100

  • In the RemoteManagementUnit (RMU) ensure that the SNMP agent is running.
  • Register OpManager server IP address as trap destination.
  • Check if the snmp community name configured as public.
  • To ensure this check the value of Public Name under Configuration tab->SNMP Configuration area.
    Note: If a different community is used, it needs to be specified when you add the device via OpManager.
  • Details are available in ADIC Scalar 100 User's Guide.

Prerequisites for Monitoring ADIC Scalar i2000

  • Ensure that the SNMP agent is running.
  • Register OpManager server IP address as trap destination.
  • Details are available in ADIC Scalar i2000 User's Guide.

Note: In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try re-adding the device. 

 

Monitoring StorageTek L-series tape libraries

OpManager provides monitoring and management of STK - StorageTek L-series tape libraries like L20 , L40 & L80.

Models Supported

  • L20
  • L40
  • L80

Features Supported

  • Complete Inventory information
    • Tape library
    • Tape Drives
  • Monitoring
    • Tape library status
    • Tape drive status
  • Reports:
    • Availability reports for Tape library .
    • Performance reports
      • Get fails/Retries
      • Label fails/Retries
      • Num of cartidge moves
      • Num of door opens , IPLs , Mounts
      • Put fails/ retries
      • Target fails/retries
  • Alarm generation for faulty conditions (via SNMP traps)
    • Tape library state
    • Tape drive state
    • CAP state
    • PTP state

Prerequisites for Monitoring

  • Ensure that the SNMP agent is running.
  • Register OpManager server IP address as trap destination.

Note: In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try readding the device.

 

Monitoring QualStar TLS, QLS & RLS series tape libraries

OpManager provides monitoring and management of QualStar TLS, QLS & RLS series tape libraries like TLS-1210, QLS-SDX-220 & RLS 4445.


Models Supported

  • Qualstar TLS series tape libraries like TLS-1210 & TLS-1220
  • Qualstar QLS series tape libraries like QLS-SDX-220 , QLS-4G-236
  • Qualstar RLS series tape libraries like RLS-4221 & RLS-4445

Features Supported

  • Inventory information of physical components
    • Tape Drive
    • Fibre Channel details
    • Library SCSI details
    • Cartidge details
  • Logical configuration details
    • LUN information for library SCSI
  • Monitoring
    • Tape library status
    • Tape drive status
  • Reports:
    • Availability reports for Tape library
    • Tape Library status report
      • No of door opens
      • No of cartidge moves
      • No of picks
      • No of times placed
      • No of grips
  • Monitoring and alarm generation for faulty conditions (via SNMP traps)
    • Door Open
    • Unit Fault
    • Inventory Violation
    • Needs Maintenance

Prerequisites for Monitoring

  • Ensure that the SNMP agent is running.
  • Register OpManager server IP address as trap destination.
  • Refer the Q-Link (Qualstar's Remote Library Management software) user manual section "SNMP" under the chapter "Q-Link Remote Library Manager" for details.

Note: In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try readding the device.

 

Monitoring Quantum - ATL tape libraries

OpManager provides monitoring and management of Quantum - ATL tape libraries - PX, P, M and DX series.


Models Supported

  • P series
    • P7000
    • P4000
    • P3000
    • P2000
    • P1000
  • PX series
    • PX502
    • PX506
    • PX510
    • PX720
  • M Series
    • M1500
    • M1800
    • M2500
  • DX Series
    • DX3000
    • DX5000
    • DX100
    • DX30

Features Supported

  • Tape library Inventory information
  • Tape library status Monitoring
  • Reports:
    • Availability reports for Tape library.
  • Monitoring and alarm generation for faulty conditions (via SNMP traps)
    • Tape library state
    • Tape library availability state

Prerequisites for Monitoring

  • Ensure that the SNMP agent is running
  • Register OpManager server IP address as trap destination
  • Has the SNMP community name configured as  "public" ? (If a different community is used , it needs to be specified when you add the device via OpManager.)

Note: In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try re-adding the device.

 

Monitoring Tandberg tape libraries

OpManager provides monitoring and management of Tandberg M series tape libraries.


Models Supported

  • M Series
    • M1500
    • M2500

Features Supported

  • Tape library Inventory information
  • Tape library status Monitoring
  • Reports:
    • Availability reports for Tape library .
  • Monitoring and alarm generation for faulty conditions (via SNMP traps)
    • Tape library state
    • Tape library availability state

Prerequisites for Monitoring

  • Ensure that the SNMP agent is running
  • Register OpManager server IP address as trap destination
  • Has the SNMP community name configured as  "public" ?  (If a different community is used , it needs to be specified when you add the device via OpManager.)

Note: In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try re-adding the device.

 

Monitoring SUN StorEdge tape libraries

OpManager provides monitoring and management of SUN StorEdge L-series tape libraries.


Models Supported

  • L Series
    • 140
    • 400
    • 1000
    • 1800

Features Supported

  • Tape library Inventory information
  • Tape library status Monitoring
  • Reports:
    • Availability reports for Tape library .
  • Monitoring and alarm generation for faulty conditions (via SNMP traps)
    • Tape library state
    • Tape library availability state

Prerequisites for Monitoring

  • Ensure that the SNMP agent is running
  • Register OpManager server IP address as trap destination.
  • Have the snmp community name configured as  "public"?   (If a different community is used , it needs to be specified when you add the device via OpManager.)

Note : In case the device is not discovered, then the probable reasons for non discovery are displayed in the client. Please go through the instructions and try readding the device.