000037726 - Direct Attached Storage Monitoring Instructions for RSA NetWitness Hosts on CentOS7

Document created by RSA Customer Support Employee on Jul 19, 2019Last modified by RSA Customer Support Employee on Aug 21, 2019
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000037726
Applies ToRSA Product Set: NetWitness Logs & Network
RSA Product/Service Type: Packet Decoder, Log Decoder, Concentrator, Archiver, 15-Drive Direct-Attached Capacity (DAC), 60-Drive DAC, and PowerVault
RSA Version/Condition: 11.3.x.x and later
Platform: CentOS 7
If CentOS6 needed, see 000035947 - Direct Attached Storage monitoring instructions for RSA NetWitness appliances.
IssueThere is no way to remotely monitor the RSA Direct-Attached Capacity (DAC) and PowerVault storage devices. You must look for the flashing amber lights on the physical storage device to notice a fan or power supply failure.
Note: For Series 6 hosts only, you can use the Dell iDRAC9 Storage Overview as an alternative to monitoring PowerVaults as shown in the following figure:
User-added image


Install the Server Hardware Manager software on the RSA NetWitness® Platform host attached to your DAC or PowerVault. This software enables you to monitor the DACs and PowerVaults for fan and power supply failures without having to go to the physical storage device.
To monitor your DACs and PowerVaults, refer to the "SHM CLI" reference in the Dell Storage PowerTools Server Hardware Manager Administrator's Guide.
Note: All guides referenced within this article can be found within the attached zip file.
Note: If there are any issues experienced during installation or running of the services from the installed software, please go to /var/log/dell/ServerHardwareManager and provide those logs to RSA Netwitness Support.


This tool was qualified on the following hardware platforms with the listed BIOS, IDRAC, and PERC Firmware versions. These are the minimum required versions for the installation script to run:

  • NetWitness Platform S4s (Dell R620)
    • BIOS: 2.7.0
    • iDRAC:
    • PERC 21.3.0-0009
  • NetWitness Platform S5 (Dell R630)
    • BIOS: 2.9.1
    • iDRAC:
    • PERC 25.5.3-0005
  • NetWitness Platform S6 (Dell R640)
    • BIOS: 2.1.8
    • iDRAC:
    • PERC 50.5.0-1750
Please follow RSA NetWitness Availability of BIOS & iDRAC Firmware Updates to update the firmware if the installed version is lower than the listed.


Follow this procedure to install the Server Hardware Manager software on the RSA NetWitness® Platform host attached to your DAC or PowerVault. For additional DACs and PowerVaults, repeat this procedure for each connected RSA NetWitness® Platform host.

  1. Click here to download the ServerHWMgr- file from this article.
  2. Log in to the RSA NetWitness host connected to the DAC or PowerVault as the root user and copy the ZIP file to the NetWitness host into the /root directory.
  3. Unzip the ServerHWMgr- archive.

    unzip ServerHWMgr-

  4. Unpackage the ServerHardwareManager- file using the tar command.

    tar -xvf ServerHardwareManager-

  5. Execute the ServerHardwareManager- file and follow the instructions to install the Server Hardware Manager.
    ./ ServerHardwareManager-
    1. Enter y (yes) to accept the license agreement.
    2. Specify the directory where Server Hardware Manager will be installed.
        If no directory is specified, and the Enter button is pressed, the default directory that the Server Hardware Manager will be installed in is /opt.
    3. Enter y (yes) to enable the SNMP service after installation.
        To send SNMP messages to an external SNMP monitor, enter the IP address and port for the SNMP Trap receivers in the format ip:port.
        If the enter button is pressed with no ip:port entered, it will use the default of
    4. Otherwise, proceed with SNMP disabled.
    5. Enter Y (yes) to enable the REST service after installation.
    6. Enter the IP address and port of the REST service of the Server Hardware Management Service (8012) in the format ip:port.
        Use the IP address of the server on which the Server Hardware Manager is being installed.
        For example:
    7. Enter Y (yes) to install Server Hardware Manager.

  1. Rename servicestartup.sh.txt, convert it to Unix format, and make sure that the script has permissions set to be able to run:

    mv servicestartup.sh.txt servicestartup.sh

    vi servicestartup.sh
    :set ff=unix

    chmod 755 servicestartup.sh


  2. Run the shell script servicestartup.sh to copy the libstorelib.so file to the /opt/dell/ServerHardwareManager/ServerHardwareManagerCLI/bin and /opt/dell/ServerHardwareManager/ServerHardwareManagerMonitor/bin directories. You will most likely need to modify firewall services in order to access the REST server from remote servers.


    Verify that the libstorelib.so file is also located in the /opt/lsi/lib directory. If it is not there, then copy it manually to the /opt/lsi/lib directory.               

ls /opt/lsi/lib
(If missing)mkdir /opt/lsi/lib
cp libstorelib.so /opt/lsi/lib/


  1. Test the REST output by opening a web browser (Chrome supports REST output) and navigating to the URLs below.

        http://<IP ADDRESS>:<PORT>/api/SEM/1.0/adapters
    http://<IP ADDRESS>:<PORT>/api/SEM/1.0/enclosures
    http://<IP ADDRESS>:<PORT>/api/SEM/1.0/drive

    For example:

  2. The above three addresses in Step 8 may cause the browser to time out. A firewall rule would need to be added to the server that the software is being executed on to be able to access the port above from outside of the server. To do this you will need to modify the iptables rule listing and restart the iptables service. Use the following commands to allow access to port 8012.
    1. Edit the iptables file.

      # vi /etc/sysconfig/iptables

    2. Add the following line above this REJECT line (-A INPUT -j REJECT --reject-with icmp-host-prohibited). The port designated in --dport should be the same as selected during step 5.

      -A INPUT -p tcp --dport 8012 -J ACCEPT

    3. Save the file with :qw! and restart the iptables service.
        service iptables restart
    4. Try to access the REST API again via browser.
  3. Step 9 may also cause the web browser to time out. Network firewalls in the customer's environment may not allow them to access port 8012 to use the Web UI of the Server Hardware Manager software. If this is the case, run the following three commands with information about the adapters, enclosures, and drives.
    Note: It may take a few seconds for these commands to return data.

curl http://<DEVICE_INTERFACE_IP>:8012/api/SEM/1.0/adapters

For example:

> curl
> {"Adapters":{"Adapter":[{"Name":"PERC H710P Mini","SAS_WWID":"500056b37789abff",
"FW_Version":"21.3.0-0009"},{"Name":"PERC H810 Adapter","SAS_WWID":"50060480702e5d3f",
"ServiceTag":"PMCSIERA","ProductName":"ESES Enclosure","EmmSlotCount":"2","DrawerCount":"1",


curl http://<DEVICE_INTERFACE_IP>:8012/api/SEM/1.0/enclosures For example:
> curl
> {"Enclosures":{"Enclosure":[{"EnclosureWWID":"50060480702e5d3e","ServiceTag":"PMCSIERA",
"ProductName":"ESES Enclosure","EmmSlotCount":"2","DrawerCount":"1","DriveSlotCount":"15",

curl http://<DEVICE_INTERFACE_IP>:8012/api/SEM/1.0/drives

For example:

> curl
> OUTPUT: {"Drives":{"Drive":[{"DeviceTypeString":"Direct-access block device","FirmwareRevision":"AS09",
"TargetPortWwn2":"5000c500571d1356", "sd_path1":"n.a.","sd_path2":"n.a.","mpath":null, "DeviceIds":
{"Descriptor":[{"@value":"5000c500571d1357", "@association":"ADDRESSED_LOGICAL_UNIT",
{"@value":"5000c500571d1354","@association":"SCSI_TARGET_DEVICE","@designator_type":"SCSI_NAME_STRING"}]},"WWID":"5000c500571d1357","Slot":"3","Size":"931.51GB","OSPath":"\\controller0\\device3","DellPPID":"TH09W5WV212333840205A06","Bus":"SCSI","Type":"HDD","FormFactorWidth":{"@units":"hundredths of mm","@value":"2500"},"FormFactorHeight":{"@units":"hundredths of mm","@value":"1500"},"YearOfMfr":"2013","SizeInBytes":"1000204885504","SupportedDrive":"TRUE","EnclosureSlot":"-1","Drawer":"-1","DrawerSlot":"-1","RPM":"7200","PredictedFail":"NO","Status":"OK"},

  1. For detailed DAC and PowerVault monitoring information, refer to the "SHM CLI" reference in the Dell Storage PowerTools Server Hardware Manager Administrator's Guide.
  2. If any issues are encountered, please reach out to RSA Netwitness Support with reference to this guide and any error messages/screenshots that can be provided.
NotesCommon DAC Monitoring Commands
The following table lists common SHM CLI commands used to monitor the DAC and PowerVault.
SHN CLI commandUse to Monitor:
./shmcli laList Adapters
   (Make a note of the adapter-index.)
./shmcli lpeList Physical Enclosures
   (Make a note of the enclosure-index.)
./shmcli ld –a=<adapter-index>
List Drives
./shmcli lds –a=<adapter-index>
List Drive Slots
./shmcli lf –a=<adapter-index>
List Fans
./shmcli lps –a=<adapter-index>
List Power Supplies
./shmcli lts –a=<adapter-index>
List Temperature Sensors