Pre-requisites for storage devices

This page discusses the pre-requisites/ basic requirements for storage devices that are monitored by OpManager. The supported storage devices are classified broadly into 3 categories and as you drill you will find the detailed pre-requisites of each individual device.

Storage Device Classification

RAID TAPE Libraries FC Swtiches
Accordance

ADIC

Cisco

Areca

HPE

SNIA FCMGMT

Dell

IBM

 

Dell EMC

OverLand Tape Library

 

Fibrenetix

Qualstar TapeLibrary  

Hitachi

SpectraLogic

 

HPE

StorageTek TapeLibrary  

Huawei

SUN SL8500  

IBM

 ATL Quantum  

INFINIBOX Storage

   

Infortrend

   

Kaminario Storage

   

NetApp

   

Promise VTrak

   

PureStorage

   

StorageTek/LSI Logic

   

SUN StorEdge6920

   

Synology DSM

   

Fujitsu

   

QNAP

   

Specific details on Storage Devices

You can find additional specific information on supported models, features and pre-requisites for each device here below.

RAID Devices

Accordance

General Information

Credential Privelege - Read Community

Device Template - Accordance

Pre-requisites

  • Ensure storage device is pingable from OpManager.
  • The SNMP port should be allowed through the firewall.

Areca

General Information

Credential Privelege - Read Community

Device Template - Areca

Pre-requisites

  • Ensure storage device is pingable from OpManager.
  • The SNMP port should be allowed through the firewall.

Dell Compellent

General Information

  • Credential Privilege - Admin
  • Device Template - Dell Compellent

Pre-requisites

  • The storage device should be pingable from OpManager installed server.
  • If the device does not have SMI server, then compatible third part SMI server must be installed.

EqualLogic

General Information

  • Credential Privilege - Read Community
  • Device Template - EqualLogic

Pre-requisites

  • Ensure storage device is pingable from OpManager.
  • The SNMP port should be allowed through the firewall.

Dell EMC VNX-BLOCK

General Information

  • Credential Privilege - Admin
  • Device Template - EMC VNX-BLOCK

Pre-requisites

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

Dell EMC VNXe 3 Series

General Information

  • Credential Privilege - Admin
  • Device Template - EMC VNXe 3 Series

Pre-requisites

  • Ensure storage device is pingable from OpManager.

Dell EMC Centera

General Information

  • Credential Privilege - Admin
  • Device Template - EMC Centera

Pre-requisites

  • OpManager uses CLI interface to monitor EMC Centera
  • Ensure that CenteraCLI software is installed on the server on 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 OpManager is restarted (shutdown & started) after copying these JAR files.

Dell EMC Symmetrix

General Information

  • Credential Privilege - Admin
  • Device Template - EMC Symmetrix

Pre-requisites

  • Ensure storage device is pingable from OpManager installed server.
  • If the device does not have an SMI server then a compatible third party SMI server should be installed.

Dell EMC VNXe 3200

General Information

  • Credential Privilege - Admin
  • Device Template - EMC VNXe 3200

Pre-requisites

  • Ensure storage device is pingable from OpManager installed server.

Dell EMC Isilon Storage

General Information

  • Credential Privilege - Admin
  • Device Template - EMC Isilon Storage

Pre-requisites

  • Ensure storage device is pingable from OpManager.
  • The API port should be allowed through Firewall.

Dell EMC Clariion

General Information

  • Credential Privilege - Admin
  • Device Template - EMC Clariion

Pre-requisites

  • Ensure storage device is pingable from OpManager.
  • NaviCLI/NaciSecCLI should be installed in the server in which OpManager is installed (Download from the official vendor site).
  • Include the directory containing NaviCLI.exe/NaviSecCLI.exe in the PATH environment variable. (This is normally C:\Program Files\ EMC\ Navisphere CLI\).
  • Ensure that OpManager is restarted (shutdown and 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.
    • navicli -h <array name> getall
    • naviseccli -h <array name> getall
  • For Performance monitoring, please ensure that setStats flag is enabled. You can enable the same using NaviCLI command
    • NaviCLI -h <array-ip> setstats -on
    • NavisecCLI -h <array-ip> setstats -on.

Dell Unity Storage

General Information

  • Credential Privilege - Admin
  • Device Template - EMC Unity Storage

Pre-requisites

  • Ensure storage device is pingable from OpManager.
  • The API port should be allowed through Firewall.

Dell EMC VNX-FILE

General Information

  • Credential Privilege - CLI
  • Device Template - EMC VNX-FILE

Pre-requisites

  • Ensure storage device is pingable from OpManager.

Dell EMC Celerra

General Information

  • Credential Privilege - CLI
  • Device Template - EMC Celerra

Pre-requisites

  • Ensure storage device is pingable from OpManager.

Fibrenetix

General Information

  • Credential Privilege - Read Community
  • Device Template - Fibrenetix

Pre-requisites

  • Ensure SNMP agent is running.
  • Ensure storage device is pingable from OpManager.
  • The SNMP port should be allowed through Firewall.

Fujitsu

General Information

Credential Privilege - Admin

Device Template - Fujitsu Storage

Pre-requisites

  • Ensure storage device is pingable from OpManager installed server.
  • If the device does not have an SMI server then a compatible third party SMI server should be installed.

Hitachi Lightning

General Information

Credential Privilege - Admin

Device Template - Hitachi Lightning

Pre-requisites

  • Ensure SNMP agent is running.
  • Ensure storage device is pingable from OpManager.
  • The SNMP port should be allowed through Firewall.

Hitachi Thunder

General Information

Credential Privilege - Read Community

Device Template - Hitachi Thunder

Pre-requisites

  • Ensure storage device is pingable from OpManager.
  • The SNMP port should be allowed through Firewall.

Hitachi Storage

General Information

Credential Privilege - Admin

Device Template - Hitachi Storage

Pre-requisites

  • Ensure storage device is pingable from OpManager.
  • If the device doesn't have SMI server then compatible 3rd party SMI server should have been installed.

HPE Nimble

General Information

Credential Privilege - Admin

Device Template - HPE Nimble

Pre-requisites

  • Ensure storage device is pingable from OpManager.
  • The API port should be allowed through firewall.

HP EVA (SSSU)

General Information

Credential Privilege - Admin

Device Template - HP EVA (SSSU)

Pre-requisites

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

A) SSSU Installation Instructions

  • OpManager uses SSSU (Storage System Scriptin 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.

  • Open the HP software download URL, HP Software Download Page.
  • Click on "HP StorageWorks Command View EVA V4.0 Media Kit". This will open a page which lists the supported Operating Systems.
  • Click on the operation system corresponding to the server running OpManager (Example: Windows 2003)
  • Click on the "Download" button corresponding to the HP StorageWorks Storage System Scripting Utility (SSSU) v4.0". This will donwload SSSU.exe.
  • After including SSSU utility in the %PATH% environment variable, restart OpManager (shutdown & start). This is required for the Environment PATH settings to take effect.

evaperf Installation Instructions

For Performance monitoring, evaperfutility 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.

HP EVA(SMI-S)

General Information

Credential Privilege - Admin

Device Template - HP EVA(SMI-S)

Pre-requisites

  • 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

HP MSA 2312

General Information

Credential Privilege - Admin

Device Template - HP MSA 2312

Pre-requisites

  • 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.
  • 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.
  • Start the MSA Provider service hp StorageWorks SMI-S CIMOM from the Windows services menu.

HP MSA Storage

General Information

Credential Privilege - Admin

Device Template - HP MSA Storage

Pre-requisites

  • The Storage device should be pingable from OpManager installed server.
  • 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.
  • Start the MSA Provider service hp StorageWorks SMI-S CIMOM from the Windows services menu.

HPE StoreOnce

General Information

Credential Privilege - Admin

Device Template - HPE StoreOnce

Pre-requisites

  • The Storage device should be pingable from OpManager.
  • The model that supports StoreOnce appliance must have the software version 4.1.x and newer. It is not compatible with models having software versions 3.x or older.

HPE Storage Device (WSAPI)

General Information

Credential Privilege - Admin

Device Template - HPE Storage Device (WSAPI)

Pre-requisites

  • Ensure the storage device is pingable from OpManager.
  • Ensure that the device to be added supports API.
  • The WSAPI server does not start automatically. Log in to the CLI as Super, Service, or any role granted the wsapi_set right. Start the WSAPI server using the following command, cli% startwsapi.
  • WSAPI version 1.6.4 or higher is required.
  • To access WSAPI version, log in to CLI as Super, Service or any other role granted to wsapi_set right and use the command: cli% showwsapi 

Huawei 18800 Series

General Information

Credential Privilege - Admin

Device Template - Huawei 18800 Series

Pre-requisites

  1. The Storage device should be pingable from OpManager installed server.
  2. If the device doesn't have SMI server then compatible 3rd party SMI Server should have been installed

Huawei 9000 Cluster

General Information

Credential Privilege - Admin

Device Template - Huawei 9000 Cluster

Pre-requisites

  1. Ensure storage device is pingable from OpManager.
  2. The API port should be allowed through firewall.

Huawei Fusion Storage

General Information

Credential Privilege - Admin

Device Template - Huawei Fusion Storage

Pre-requisites

  1. Ensure storage device is pingable from OpManager.
  2. The API port should be allowed through firewall.

Huawei Storage

General Information

Credential Privilege - Admin

Device Template - Huawei Storage

Pre-requisites

  1. Ensure storage device is pingable from OpManager.
  2. The API port should be allowed through firewall.

IBM DS Series

General Information

Credential Privilege - Admin

Device Template - IBM DS Series

Pre-requisites

  • The Storage device should be pingable from OpManager installed server.

IBM ESS

General Information

Credential Privilege - Admin

Device Template - IBM ESS

Pre-requisites

  • 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 to be 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.

IBM XIV

General Information

Credential Privilege - Admin

Device Template - IBM XIV

Pre-requisites

  • The Storage device should be pingable from OpManager installed server.
  • If the device doesn't have SMI server then compatible 3rd party SMI Server should have been installed.

IBM Spectrum Virtualize

General Information

Credential Privilege - Admin

Device Template - IBM Spectrum Virtualize

Pre-requisites

  • Ensure storage device is pingable from OpManager.
  • The API port should be allowed through firewall.

IBM FS 840/900 Storage


General Information

Credential Privilege - Admin

Device Template - IBM FS 840/900 Storage

Pre-requisites

  • Ensure storage device is pingable from OpManager.
  • Port 9443 should be allowed through the firewall.

INFINIBOX Storage

General Information

Credential Privilege - Admin

Device Template - INFINIBOX Storage

Pre-requisites

  • Ensure storage device is pingable from OpManager.
  • The API port should be allowed through firewall.

Infortrend

General Information

Credential Privilege - Read Community

Device Template - Infortrend

Pre-requisites

  1. Make sure storage device is pingable from OpManager.
  2. The SNMP port should be allowed through firewall.

KAMINARIO Storage

General Information

Credential Privilege - Admin

Device Template - KAMINARIO Storage

Pre-requisites

  • Ensure storage device is pingable from OpManager.
  • The API port should be allowed through firewall.

NetApp ONTAP(Cluster)

General Information

Credential Privilege - Admin

Device Template - NetApp ONTAP (Cluster)

Pre-requisites

  • Ensure storage device is pingable from OpManager.
  • The API port should be allowed through firewall.

NetApp E2X00/E5X00/EF5X0

General Information

Credential Privilege - Admin

Device Template - NetApp E2X00/E5X00/EF5X0

Pre-requisites

  • The Storage device should be pingable from OpManager installed server.
  • If the device doesn't have SMI server then compatible 3rd party SMI Server should have been installed.

Promise VTrak

General Information

Credential Privilege - Read Community

Device Template - Promise VTrak

Pre-requisites

  • Ensure SNMP agent is running.
  • Ensure storage device is pingable from OpManager.
  • The SNMP port should be allowed through firewall.

Pure Storage(API)

General Information

Credential Privilege - Admin

Device Template - Pure Storage(API)

Pre-requisites

  • Ensure storage device is pingable from OpManager.
  • The API port should be allowed through firewall.

PureStorage

General Information

Credential Privilege - Admin

Device Template - PureStorage

Pre-requisites

  • Ensure storage device is pingable from OpManager.

StorageTek LSI (SSCS)

General Information

Credential Privilege - Admin

Device Template - LSI(SSCS)

Pre-requisites

  • Make sure storage device is pingable from OpManager.

SUN StorEdge6920

General Information

Credential Privilege - Admin

Device Template - SUN StorEdge 6920

Pre-requisites

  • 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

Synology DSM

General Information

Credential Privilege - Read Community

Device Template - Synology DSM

Pre-requisites

  • Ensure storage device is pingable from OpManager.
  • The SNMP port should be allowed through firewall.

FCSwitch

Cisco MDS

General Information

Credential Privilege - Read Community

Device Template - Cisco MDS

Pre-requisites

  • The Read community should have read access right. Please provide the Community 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

SNIA FCMGMT

General Information

Credential Privilege - Read Only

Device Template - SNIA FCMGMT

Pre-requisites

  • 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

QNAP

General Information

Credential Privilege - Admin

Device Template - QNAP QTS Storage

Pre-requisites

  • Ensure storage device supports API.

Tape Library

ADIC 100

General Information

Credential Privilege - Read Community

Device Template - ADIC 100

Pre-requisites

  • 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.

ADIC i2000

General Information

Credential Privilege - Read Community

Device Template - ADIC i2000

Pre-requisites

  • 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.

ATL Quantum

General Information

Credential Privilege - Read Community

Device Template - ATL Quantum

Pre-requisites

  • 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.)

HP EML/ESL

General Information

Credential Privilege - Admin

Device Template - HP EML/ESL

Pre-requisites

  • 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 menu.

IBM 3584

General Information

Credential Privilege - Read Community

Device Template - IBM 3584

Pre-requisites

  • 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".
  • Ensure storage device is pingable from OpManager.
  • The SNMP port should be allowed through firewall.

IBM TS3100

General Information

Credential Privilege - Read Community

Device Template - IBM TS3100

Pre-requisites

  • Ensure SNMP agent is running.
  • Ensure storage device is pingable from OpManager.
  • The SNMP port should be allowed through firewall.

IBM TS3200

General Information

Credential Privilege - Read Community

Device Template - IBM TS3200

Pre-requisites

  • Ensure SNMP agent is running.
  • Ensure storage device is pingable from OpManager.
  • The SNMP port should be allowed through firewall.

TapeLibrary

Overland TapeLibrary

General Information

Credential Privilege - Read Community

Device Template - Overland TapeLibrary

Pre-requisites

  • Ensure SNMP agent is running.
  • Ensure storage device is pingable from OpManager.
  • The SNMP port should be allowed through firewall.

Qualstar TapeLibrary

General Information

Credential Privilege - Read Community

Device Template - Qualstar TapeLibrary

Pre-requisites

  1. Ensure SNMP agent is running.
  2. Ensure storage device is pingable from OpManager.
  3. The SNMP port should be allowed through firewall.
  4. Refer the Q-Link (Qualstar's Remote Library Management software) user manual section "SNMP" under the chapter "Q-Link Remote Library Manager" for details.

SpectraLogic T120

General Information

Credential Privilege - Read Community

Device Template - SpectraLogic T120

Pre-requisites

  1. Ensure SNMP agent is running.
  2. Ensure storage device is pingable from OpManager.
  3. The SNMP port should be allowed through firewall.

SpectraLogic T950

General Information

Credential Privilege - Read Community

Device Template - SpectraLogic T950

Pre-requisites

  1. Ensure SNMP agent is running.
  2. Ensure storage device is pingable from OpManager.
  3. The SNMP port should be allowed through firewall.

StorageTek TapeLibrary

General Information

Credential Privilege - Read Community

Device Template - StorageTek TapeLibrary

Pre-requisites

  1. Ensure SNMP agent is running.
  2. Ensure storage device is pingable from OpManager.
  3. The SNMP port should be allowed through firewall.

SUN SL8500

General Information

Credential Privilege - Read Community

Device Template - SUN SL8500

Pre-requisites

  1. Ensure SNMP agent is running.
  2. Ensure storage device is pingable from OpManager.
  3. The SNMP port should be allowed through firewall.