Free SAN and storage performance and capacity monitoring

HPE storage installation

Back to storage installation home.


In case of usage of Virtual Appliance
  • Use local account lpar2rrd for hosting of STOR2RRD on the virtual appliance
  • Use /home/stor2rrd/stor2rrd as the product home
  • Use lpar2rrd account on storages as it is configured in /home/stor2rrd/stor2rrd/etc/stor2rrd.cfg (STORAGE_USER)
Configure storage access in one of following ways:
  • 3PAR CLI commands via SSH protocol, no need any HPE SW installation, just exachange ssh keys and that's it
  • Using 3PAR CLI calls, it is necessary for 3PAR storages with firmware 3.2.2 MU4 and higher. Read why.

Configuration

  • Do all actions below under stor2rrd account (lpar2rrd on the Virtual Appliance) unless is explicitly specified root in the procedure.

  • Create user stor2rrd on the storage with browse role and allow it for all domains.
    $ ssh 3paradm@3par_storage
      3paradm's password: ******
    cli% createuser -c testpw stor2rrd all browse 
    cli% exit
    
    $ ssh stor2rrd@3par_storage
    cli% showuser
         Username Domain    Role   Default
         stor2rrd    all    browse N
    
  • Under stor2rrd account create config entry. Uncomment (remove the hash) example line and adjust it:
    $ vi /home/stor2rrd/stor2rrd/etc/storage-list.cfg
    
    #
    # HP 3PAR
    #
    # Storage name alias:3PAR:storage IP/hostname:ssh_key_file:VOLUME_AGG_DATA_LIM:VOLUME_AGG_IO_LIM:SAMPLE_RATE_MINS
    #
    #3PAR01-alias:3PAR:3par_host.example.com:/home/stor2rrd/.ssh/id_rsa:2048:512:5
    #3PAR02-alias:3PAR:3par_host.example.com:/home/stor2rrd/.ssh/id_rsa
    #3PAR02-alias:3PAR:storage_IP:
    3par01:3PAR:192.168.1.1:
    
    Above shows 3PAR storage with IP 192.168.1.1 which will be visible in the GUI as 3par01

  • Use 1 of these connection methods:
    • 3PAR CLI via SSH
      Use that for HPE 3PAR firmwares up to 3.2.2 MU4, read why
      No need to install anythig, standard ssh is used as the transport layer.
      • Open port 22 to the storage (you can use this test cmd since version 2.00)
        $ perl /home/stor2rrd/stor2rrd/bin/conntest.pl 192.168.1.1 22
          Connection to "192.168.1.1" on port "22" is ok
        
      • Create a key pair using the ssh-keygen utility in case you do not have a one in /home/stor2rrd/.ssh
        Type enter instead of passphrase.
        # su - stor2rrd # (use lpar2rrd user on the Appliance)
        $ ssh-keygen -t rsa
          Generating public/private rsa key pair.
          Enter file in which to save the key (/home/stor2rrd/.ssh/id_rsa):
          ...
        $ cat ~/.ssh/id_rsa.pub
        
      • Exchange the ssh public key (import it on the storage under stor2rrd account)
        $ ssh stor2rrd@3par_storage
          stor2rrd@3par_storage password: testpw
        cli% setsshkey
        
        Enter the SSH public key below. When finished, press enter twice. The key is usually long.
        It's better to copy it from inside an editor and paste it here. (make sure there is no extra blanks)
         sshrsa AF5afPdciUTJ0PYzB6msRxFrCuDSqDwPshqWS5tGCFSoSZdE= stor2rrd pubic key
         SSH public key successfully set!
        
      • Check the storage connection, you should log in without password prompt
        $ ssh stor2rrd@3par_storage
        
    • 3PAR CLI calls (it is supported since STOR2RRD v2.00)
      Use this method for 3PAR 3.2.2 MU4 and higher although ssh access might work for couple of hours
      • Open ports 5783,5782,22 to the storage
        Test if ports are open:
        $ perl /home/stor2rrd/stor2rrd/bin/conntest.pl 192.168.1.1 22
          Connection to "192.168.1.1" on port "22" is ok
        
      • Download HPE 3PAR CLI. You need software support contract (SAID) at HPE
        Under root:
        # mount -o loop,ro ./3PAR_INFORMOS_3.2.2_MU4_CLI_SNMP_QR482-11192.iso /cdrom
        # cd /cdrom/cli/linux/
        # ./setup.bin
          Default Install Folder: /opt/hp_3par_cli
          Congratulations. HP 3PAR CLI 3.2.2 has been successfully installed to:
          /opt/hp_3par_cli
        
        When you select not default installation directory then update appropriately:
        HPE3PAR_CLIDIR=/opt/hp_3par_cli/bin in etc/stor2rrd.cfg

      • Run configuration script under stor2rrd user for credential save:
        $ ./bin/3par-credential-save.sh
          Script will go through all configured 3PARs in etc/storage-list.cfg
          Provide for each 3PAR system username and password
          You might run it for specific 3PAR: ./bin/3par-credential-save.sh <3PAR alias>
        
          STORAGE: 3PAR01-phys IP/hostanme: 192.168.1.60 username:stor2rrd
          /opt/hp_3par_cli/bin/cli setpassword -saveonly -file /home/lpar2rrd/stor2rrd/etc/.3par-192.168.1.60.pwf -sys 192.168.1.60
          user: stor2rrd
          password: 
        
  • Assure you have enough of disk space on the filesystem where is STOR2RRD installed
    Roughly you might count 2 - 30 GB per a storage (it depends on number of volumes, 30GB for 5000 volumes)
    $ df -g /home   # AIX
    $ df -h /home   # Linux
    
  • Check storage connectivity
    $ cd /home/stor2rrd/stor2rrd
    $ ./bin/config_check.sh 
      =====================
      STORAGE: 3par01: 3PAR
      =====================
      ssh -o ConnectTimeout=15 -i /home/stor2rrd/.ssh/id_rsa  stor2rrd@192.168.1.1  "showuser"
      connection ok
    
  • Schedule to run storage agent from stor2rrd crontab (lpar2rrd on Virtual Appliance, it might already exist there)
    $ crontab -e
    
    # HPE 3PAR storage agent
    0,5,10,15,20,25,30,35,40,45,50,55 * * * * /home/stor2rrd/stor2rrd/load_3parperf.sh > /home/stor2rrd/stor2rrd/load_3parperf.out
    
    Assure there is already an entry with the GUI creation running once an hour in crontab
    $ crontab -e
    
    # STOR2RRD GUI (just ONE entry of load.sh must be there)
    5 * * * * /home/stor2rrd/stor2rrd/load.sh > /home/stor2rrd/stor2rrd/load.out 2>&1
    
  • Let run the storage agent for 15 - 20 minutes to get data, then:
    $ cd /home/stor2rrd/stor2rrd
    $ ./load.sh
    
  • Go to the web GUI: http://<your web server>/stor2rrd/
    Use Ctrl-F5 to refresh the web browser cache.

HPE XP7 is re-branded Hitachi VSP-G therefore install procedure is same as for it.

In case of usage of Virtual Appliance
  • Use local account lpar2rrd for hosting of STOR2RRD on the virtual appliance
  • Use /home/stor2rrd/stor2rrd as the product home
The program uses two Hitachi (HPE) APIs. You have to install both of them.
  • Command Control Interface (CCI)
  • Hitachi (HPE) Export Tool
You might also look into very detaily described installation procedure on www.sysaix.com.
Note that Virtual Storage Machines (VSM) feature is not supported by the tool.

Installation of CCI

  • Allow communication from STOR2RRD host to all storages on TCP ports 1099, 51100, and UDP 31001, 31002
    Test open ports for TCP protocols (UDP ports cannot be tested via that):
    $ perl /home/stor2rrd/stor2rrd/bin/conntest.pl 192.168.1.1 1099
      Connection to "192.168.1.1" on port "1099" is ok
    $ perl /home/stor2rrd/stor2rrd/bin/conntest.pl 192.168.1.1 51100
      Connection to "192.168.1.1" on port "51100" is ok
    
  • Create user stor2rrd on the storage, read only access

  • Obtain CCI installation package from your HPE representatives.
    • Install it from .iso
      # loopmount -i HS042_77.iso -o "-V cdrfs -o ro" -m /mnt
      # mkdir /etc/HORCM
      # cd /mnt
      # ./RMinstsh
      
    • Install from CD
      # mkdir /opt
      # cpio -idmu < /dev/XXXX    # where XXXX = I/O device with install media
      # ln -s /opt/HORCM /HORCM
      
    • Execute the CCI installation command:
      # /HORCM/horcminstall.sh
      
    • Verify installation of the proper version using the raidqry command:
      # raidqry -h
        Model: RAID-Manager/HP-UX
        Ver&Rev: 01-29-03/05
        Usage: raidqry [options]
      
    • Assure that everything is executable and writeable by stor2rrd user (it will be started under stor2rrd).
      This is a must! Under root identification execute this:
      # touch /HORCM/etc/USE_OLD_IOCT
      # chown stor2rrd /HORCM
      # chown -R stor2rrd /HORCM/log* /HORCM/.uds /HORCM/usr
      # chmod 755 /HORCM /HORCM/usr/bin /HORCM/usr/bin/* /HORCM/log /HORCM/etc/horcmgr /HORCM/etc/*conf /HORCM/.uds/ /HORCM/.uds/*
      

Configuration of CCI

  • CCI communication with storage can be done either via LAN (it is something described below) or via command device (SAN attached volume from the storage).
    When you have many storages in place 40+ then use rather command device as LAN communication might not be reliable enough. CCI command device configuration procedure

  • Each storage must have its own config file /etc/horcmXX.conf

  • Check if local ports 10001 and 10002 are not used (nothing is listening there)
    # netstat -an|grep -i listen| egrep "11001|11002"
    
  • storage with IP 192.168.1.1, conf file /etc/horcm1.conf will use local port 11001 (UDP)
    Use storage node IP. SVP IP must be used in etc/storage-list.cfg further.
    # vi /etc/horcm1.conf
    
    HORCM_MON
    # ip_address service poll(10ms) timeout(10ms)
    localhost    11001   1000       3000
    HORCM_CMD
    # dev_name dev_name dev_name
    \\.\IPCMD-192.168.1.1-31001
    
  • storage with IP 192.168.1.10, conf file /etc/horcm2.conf
    change localhost port to 11002 (from 11001 which is used above)
    # vi /etc/horcm2.conf
    
    HORCM_MON
    # ip_address service poll(10ms) timeout(10ms)
    localhost    11002   1000       3000
    HORCM_CMD
    # dev_name dev_name dev_name
    \\.\IPCMD-192.168.1.10-31001
    
  • Start it under stor2rrd account (definitelly not under root!). Use lpar2rrd account on the Virtual Appliance
    This starts HORM instance 1 (/etc/horcm1.conf)
    # su - stor2rrd
    $ /HORCM/usr/bin/horcmstart.sh 1
    
  • Start HORM instance 1 & 2 (/etc/horcm1.conf & /etc/horcm2.conf)
    # su - stor2rrd
    $ /HORCM/usr/bin/horcmstart.sh 1 2
    
  • Check if they are running
    $ ps -ef | grep horcm
      stor2rrd 19660912 1 0 Feb 26 - 0:03 horcmd_02
      stor2rrd 27590770 1 0 Feb 26 - 0:09 horcmd_01
    
  • Place it into operating system start/stop scripts
    # su - stor2rrd -c "/HORCM/usr/bin/horcmstart.sh 1 2"
    # su - stor2rrd -c "/HORCM/usr/bin/horcmshutdown.sh 1 2"
    

Installation of Export Tool

    It is typically located on a CD that comes packaged with the Service Processor on the HPE XP7 Array. The Export Tool can also be obtained by contacting HPE support. (CD location: /ToolsPack/ExportTool)
    There is a new Export Tool build for each release of the firmware. Unless you make sure all of the storages are running on the same firmware version then you will need to obtain the appropriate version of the Export Tool to meet the firmware version you are running at the site.

    Find our firmware release of your storage (83-01-28/00) identified by /etc/horcm1.conf (-I1):
    Export Tool version must match the SVP firmware version.
    Under stor2rrd account!
    # su - stor2rrd
    $ raidcom -login stor2rrd <password> -I1
    $ raidqry -l -I1 
      No  Group    Hostname     HORCM_ver   Uid   Serial#   Micro_ver     Cache(MB)
       1    ---   localhost   01-35-03-08     0   471234    83-01-28/00      320000
    $ raidcom -logout -I1
    
    Install each version of the Export Tool into separate directory named as firmware of your storage (just 6 numbers like in this example firmware 83-01-28) under root user:
    # mkdir /opt/hds
    # mkdir /opt/hds/83-01-28
    # cd /opt/hds/83-01-28
    # tar xvf export-tool.tar
    # chown -R stor2rrd /opt/hds
    
    Might work that higher Export Tool version works even with lower storage firmware like in that example (Export Tool 83-01-28 and storage firmware 73-03-57).
    In this case you do not need to install older Export Tool, just make a symlink.
    # cd /opt/hds/
    # ls 
      83-01-28
    # ln -s 83-01-28 73-03-57
    

    Directory /opt/hds is optional, it is configurable in /home/stor2rrd/stor2rrd/etc/sto2rrd.cfg : VSP_CLIDIR=/opt/hds
    The HPE Performance Monitor License must exist for each array and monitoring must be enabled.
    Storage configuration example

Allow monitoring of CU and WWN

  • CU
    Hitachi CU menu

    Hitachi CU selection

  • WWN
    Hitachi WWN menu

    Hitachi WWN selection

STOR2RRD storage configuration

  • All actions below under stor2rrd user (lpar2rrd on Virtual Appliance)

  • Configure Export Tool installation directory in /home/stor2rrd/stor2rrd/etc/stor2rrd.cfg
     VSP_CLIDIR=/opt/hds
    
  • Create user stor2rrd on the storage, read only access
  • Configure storages in etc/storage-list.cfg
    Uncomment (remove the hash) example line and adjust it.
    Use storage SVP IP here (CCI above uses storage node IP).
    $ vi /home/stor2rrd/stor2rrd/etc/storage-list.cfg
    
    #
    # Hitachi VSP-G & HPE XP7
    #
    # Storage Alias:VSPG:IP address/hostname:storage user:password:/etc/horcm.conf:VOLUME_AGG_DATA_LIM:VOLUME_AGG_IO_LIM:SAMPLE_RATE_MINS
    # to encrypt password use: perl ./bin/spasswd.pl
    #XP7-alias:VSPG:192.168.1.2:stor2rrd:KT4mXVI9N0BUPjZdVQo=:/etc/horcm1.conf:1024:10:0
    
    XP7-01:VSPG:192.168.1.1:stor2rrd:KT4mXVI9N0BUPjZdVQo=:/etc/horcm2.conf
    
    Above shows storage with IP 192.168.1.1 which will be visible in the GUI as XP7-01

    Use encrypted password in storage line above:
    $ perl bin/spasswd.pl
    
      Encode password for storage authentication:
      -------------------------------------------
      Enter password:
      Re-enter password:
    
      Copy the following string to the password field of the corresponding line in etc/storage-list.cfg:
    
      KT4mXVI9N0BUPjZdVQo=
    
  • Assure you have enough of disk space on the filesystem where is STOR2RRD installed
    Roughly you might count 2 - 30 GB per a storage (it depends on number of volumes, 30GB for 5000 volumes)
    $ df -g /home   # AIX
    $ df -h /home   # Linux
    
  • Test the storage connectivity under stor2rrd user:
    $ cd /home/stor2rrd/stor2rrd
    $ ./bin/config_check.sh 
      ======================
      STORAGE: XP7-01 : VSPG
      =======================
      connection ok
    
  • Schedule to run storage agent from stor2rrd crontab (lpar2rrd on Virtual Appliance, it might already exist there)
    $ crontab -e
    
    # HPE XP7 (use Hitachi VSPG scipt load_vspgperf.sh)
    0,5,10,15,20,25,30,35,40,45,50,55 * * * * /home/stor2rrd/stor2rrd/load_vspgperf.sh > /home/stor2rrd/stor2rrd/load_vspgperf.out
    
    Assure there is already an entry with the GUI creation running once an hour in crontab
    $ crontab -e
    
    # STOR2RRD GUI (just ONE entry of load.sh must be there)
    5 * * * * /home/stor2rrd/stor2rrd/load.sh > /home/stor2rrd/stor2rrd/load.out 2>&1
    
  • Let run the storage agent for 15 - 20 minutes to get data, then:
    $ cd /home/stor2rrd/stor2rrd
    $ ./load.sh
    
  • Go to the web GUI: http://<your web server>/stor2rrd/
    Use Ctrl-F5 to refresh the web browser cache.

In case of usage of Virtual Appliance
  • Use local account lpar2rrd for hosting of STOR2RRD on the virtual appliance
  • Use /home/stor2rrd/stor2rrd as the product home
The product uses SMI-S and XML API interfaces natively provided by the storage.
We do not support G2 and older models which do not have SMI-S and XML API interfaces.

Storage connectivity

  • Allow access from the STOR2RRD host to the storage on ports 80 (HTTP) and 5988 (SMI-S) and optionally 22 (ssh) if you use cmd line configuration as in examples below (you can use the storage GUI instead).
    Test if ports are open:
    $ perl /home/stor2rrd/stor2rrd/bin/conntest.pl 192.168.1.1 80
      Connection to "192.168.1.1" on port "80" is ok
    
  • Assure that SMI-S 5988 and HTTP protocols are enabled on the storage
    $ ssh -l manage <storage_hostname>
    # show protocols
      Service and Security Protocols
      ------------------------------
      Web Browser Interface (HTTP): Enabled
      Secure Web Browser Interface (HTTPS): Enabled
      Command Line Interface (Telnet): Disabled
      Secure Command Line Interface (SSH): Enabled
      Storage Management Initiative Specification (SMI-S): Disabled
      Unsecure Storage Management Initiative Specification (SMI-S 5988): Enabled
      ...
    
    If SMI-S 5988 or HTTP is not enabled:
    # set protocols usmis enabled
    # set protocols http enabled
    
  • Create user stor2rrd on the storage with monitor role and allow SMI-S and XML API.
    Adjust password to your prefered one from used Test1234.
    $ ssh -l manage <storage_hostname>
    # create user interfaces smis,wbi locale English password Test1234 roles monitor stor2rrd
    
  • In case you want to use SSL access to the storage
    enable ports 5989 and 443 and start up SSL services on the storage instead of non SSL ones
    # set protocols smis enabled
    # set protocols https enabled
    
    Use this fix to enable SSL communication if you run STOR2RRD v2.00 or v2.01: dothill-ssl.tar.gz.
    $ gunzip dothill-ssl.tar.gz
    $ ls -l dothill-ssl.tar
      -rw-rw-r-- 1 lpar2rrd lpar2rrd 92160 Jun  5 14:41 dothill-ssl.tar
    $ cd /home/stor2rrd/stor2rrd
    $ tar xvf dothill-ssl.tar
      -rwxr-xr-x lpar2rrd/lpar2rrd 4081  2017-06-01 13:34 bin/dothill_apitest.pl
      -rwxr-xr-x lpar2rrd/lpar2rrd 81664 2017-06-05 11:59 bin/dothillperf.pl
    
    kill all running  dothillperf.pl processes
    

Install prerequisites

Skip that in case of Virtual Appliance
  • Linux:
    Install sblim-wbemcli package:
    # yum list |grep sblim-wbemcli
      sblim-wbemcli.x86_64                       1.6.2-9.el7                 base
    # yum install sblim-wbemcli     # RedHat
    # apt-get install sblim-wbemcli # Debian based (Ubuntu etc)
    # /usr/bin/wbemcli -noverify -nl ei https://<storage_hostname>:5988/root/dsh:cim_computersystem
      *
      * ./wbemcli: Http Exception: Username/password required.
      *
    
    If you prefere to use https on port 5989 then you must use wbemcli with this patch 0002742
    Download the package from:
    Test the package:
    # rpm -q sblim-wbemcli
      sblim-wbemcli-1.6.3-31.1.x86_64
    # /usr/bin/wbemcli -v
      * wbemcli Version 1.6.3
    # /usr/bin/wbemcli -noverify -nl ei http://<storage_hostname>:5988/root/dsh:cim_computersystem
      *
      * ./wbemcli: Http Exception: Username/password required.
      *
    
  • AIX:
    Download and install
    # rpm -Uvh libffi-3.1-1.aix5.1.ppc.rpm --nodeps
    # rpm -Uvh libiconv-1.14-2.aix5.1.ppc.rpm --nodeps
    # rpm -Uvh libidn-1.29-1.aix5.1.ppc.rpm --nodeps
    # rpm -Uvh libssh2-1.4.3-2.aix5.1.ppc.rpm --nodeps
    # rpm -Uvh openssl-1.0.1j-1.aix5.1.ppc.rpm
    # rpm -Uvh openldap-2.4.23-0.3.aix5.1.ppc.rpm
    # rpm -Uvh curl-7.27.0-1.aix5.1.ppc.rpm
    # rpm -Uvh wbemcli-1.6.3-1.aix5.1.ppc.rpm
    
    # LIBPATH=/opt/freeware/lib; export LIBPATH
    # /opt/freeware/bin/wbemcli -noverify -nl ei http://<storage_hostname>:5988/root/dsh:cim_computersystem
      *
      * ./wbemcli: Http Exception: Username/password required.
      *
    

STOR2RRD storage configuration

  • All actions below under stor2rrd user (lpar2rrd on Virtual Appliance)

  • Uncomment (remove the hash) example line and adjust it:
    $ vi /home/stor2rrd/stor2rrd/etc/storage-list.cfg
    
    #
    # Dot Hill AssuredSAN and its rebrands like Lenovo S2200 or HPE MSA P2000
    #
    # Storage Alias:DOTHILL:Controller_A IP address or hostname:Controller_B IP address or hostname:[http|https]:storage user:encrypted password:VOLUME_AGG_DATA_LIM:VOLUME_AGG_IO_LIM:SAMPLE_RATE_MINS
    # to encrypt password use: perl ./bin/spasswd.pl
    #DOTHILL_AssuredSAN-alias01:DOTHILL:ctla_host.example.com:ctlb_host.example.com:http:stor2rrd:KT4mXVI9N0BUPjZdVQo=:1024:10:
    #LENOVO_S2000-alias01:DOTHILL:ctla_host.example.com:ctlb_host.example.com:http:stor2rrd:KT4mXVI9N0BUPjZdVQo=
    #HPE_MSA2000-alias01:DOTHILL:ctla_host.example.com:ctlb_host.example.com:http:stor2rrd:KT4mXVI9N0BUPjZdVQo=
    
    MSA2000-alias01:DOTHILL:192.168.1.1:192.168.1.2:http:stor2rrd:KT4mXVI9N0BUPjZdVQo=
    
    Above shows storage with IP 192.168.1.1 which will be visible in the GUI as MSA2000-alias01

    Use encrypted password in storage line above, encrypt it like this:
    (Note: do not use characters like "@" or "!" in password string as wbemcli does not cope with them)
    $ perl bin/spasswd.pl
    
      Encode password for storage authentication:
      -------------------------------------------
      Enter password:
      Re-enter password:
    
      Copy the following string to the password field of the corresponding line in etc/storage-list.cfg:
    
      KT4mXVI9N0BUPjZdVQo=
    
  • Assure you have enough of disk space on the filesystem where is STOR2RRD installed
    Roughly you might count 2 - 30 GB per a storage (it depends on number of volumes, 30GB for 5000 volumes)
    $ df -g /home   # AIX
    $ df -h /home   # Linux
    
  • Check storage connectivity
    $ cd /home/stor2rrd/stor2rrd
    $ ./bin/config_check.sh 
      =====================
      STORAGE: MSA2000-alias01 : HPE MSA
      =====================
      connection ok
    
    If you use HTTPS and do not have installed Perl SSL support then you get an error:
    "Missing LWP::Protocol::https", "Connection reset by peer" or "500 SSL negotiation failed"
    Follow this or switch to HTTP on the storage line in etc/storage-list.cfg.

  • Schedule to run storage agent from stor2rrd crontab (lpar2rrd on Virtual Appliance, it might already exist there)
    $ crontab -e
    
    # DotHill AssuredSAN and its rebrands like Lenovo S2200 or HPE MSA P2000
    0,5,10,15,20,25,30,35,40,45,50,55 * * * * /home/stor2rrd/stor2rrd/load_dothillperf.sh > /home/stor2rrd/stor2rrd/load_dothillperf.out
    
    Assure there is already an entry with the GUI creation running once an hour in crontab
    $ crontab -e
    
    # STOR2RRD GUI (just ONE entry of load.sh must be there)
    5 * * * * /home/stor2rrd/stor2rrd/load.sh > /home/stor2rrd/stor2rrd/load.out 2>&1
    
  • Let run the storage agent for 15 - 20 minutes to get data, then:
    $ cd /home/stor2rrd/stor2rrd
    $ ./load.sh
    
  • Go to the web GUI: http://<your web server>/stor2rrd/
    Use Ctrl-F5 to refresh the web browser cache.

Troubleshooting

  • Assure SMI-S is working for user stor2rrd. Adjust password and storage_hostname in example below:
    $ /usr/bin/wbemcli -nl -t -noverify ein 'http://stor2rrd:<password>@<storage_hostnamew>:5988/root/hpq:SMI_Controller'
      192.168.1.1:5988/root/smis:SMI_Controller.Name="208000c0ff261f53:A",CreationClassName="SMI_Controller"
      192.168.1.2:5988/root/smis:SMI_Controller.Name="208000c0ff261f53:B",CreationClassName="SMI_Controller"
    
    When it does not work then check user rights of stor2rrd user (must have "smis"), network visibility (firewall), user/password combination.

 

Links

Download

Others

Contact