000035947 - Direct Attached Storage monitoring instructions for RSA NetWitness appliances

Document created by RSA Customer Support Employee on Mar 7, 2018Last modified by RSA Customer Support Employee on Mar 10, 2018
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000035947
Applies ToRSA Product Set: NetWitness Logs & Packets, Security Analytics
RSA Product/Service Type: Packet Decoder, Log Decoder, Concentrator, Archiver, Direct Attached Capacity (DAC)
RSA Version/Condition: 10.6.x,
Platform: CentOS 6
IssueThere is no way to remotely monitor the RSA Direct Attached Capacity (DAC) storage devices. You must look for the flashing amber lights on the physical DAC storage device to notice a fan or power supply failure.
Resolution

Solution


Install the Server Hardware Manager software on the RSA NetWitness Suite host attached to your 15-Drive DAC. This software enables you to monitor the DACs for fan and power supply failures without having to go to the physical DAC storage device.
 
To monitor your DACs, 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.



Procedure



Follow this procedure to install the Server Hardware Manager software on the RSA NetWitness Suite host attached to your 15-Drive DAC. For additional 15-Drive DACs, repeat this procedure for each connected RSA NetWitness Suite host.



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

    unzip ServerHWMgr-2.1.0.10977-CentOS6.zip

  4. Locate the ServerHardwareManager-2.1.0.10977-CentOS6-installer.tar.gz file in the directory and run gunzip for this file.

    gunzip ServerHardwareManager-2.1.0.10977-CentOS6-installer.tar.gz

  5. Unpackage the ServerHardwareManager-2.1.0.10977-CentOS6-installer.tar file using the tar command.

    tar -xvf ServerHardwareManager-2.1.0.10977-CentOS6-installer.tar

  6. Execute the ServerHardwareManager-2.1.0.10977-CentOS6-installer file and follow the instructions to install the Server Hardware Manager:

    ./ServerHardwareManager-2.1.0.10977-CentOS6-installer


    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 127.0.0.1:162.


       
    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:
       

      192.168.0.10:8012

       
    7. Enter y (yes) to install Server Hardware Manager.
  7. Make sure that the servicestartup.sh script has permissions set to be able to run.

    chmod 755 servicestartup.sh

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

    ./servicestartup.sh

  9. 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/drives

    For Example:


    http://192.168.0.10:8012/api/SEM/1.0/adapters
    http://192.168.0.10:8012/api/SEM/1.0/enclosures
    http://192.168.0.10:8012/api/SEM/1.0/drives

  10. The above three addresses in Step 9 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, in order 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
    a. Edit the iptables file

    # vi /etc/sysconfig/iptables

    b. 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 6.


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

    c. Save the file with :qw! and restart the iptables service


    service iptables restart

    d. Try to access the REST API again via browser
  11. Step 10 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 3 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 http://192.168.0.10:8012/api/SEM/1.0/adapters

      > {"Adapters":{"Adapter":[{"Name":"PERC H710P Mini","SAS_WWID":"500056b37789abff",
      "FW_Version":"21.3.0-0009"},{"Name":"PERC H810 Adapter","SAS_WWID":"50060480702e5d3f",
      "FW_Version":"21.2.0-0007","Enclosures":{"Enclosure":[{"EnclosureWWID":"50060480702e5d3e",
      "ServiceTag":"PMCSIERA","ProductName":"ESES Enclosure","EmmSlotCount":"2","DrawerCount":"1",
      "DriveSlotCount":"15","FanCount":"4","PowerSupplyCount":"2","VoltageSensorCount":"0",
      "CurrentSensorCount":"0","TemperatureSensorCount":"7","AlarmCount":"0","OverallStatus":"OK"}]}}]}}

       

    •  

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

        For Example:

       

      > curl http://192.168.0.10:8012/api/SEM/1.0/enclosures

      > {"Enclosures":{"Enclosure":[{"EnclosureWWID":"50060480702e5d3e","ServiceTag":"PMCSIERA",
      "ProductName":"ESES Enclosure","EmmSlotCount":"2","DrawerCount":"1","DriveSlotCount":"15",
      "FanCount":"4","PowerSupplyCount":"2","VoltageSensorCount":"0","CurrentSensorCount":"0",
      "TemperatureSensorCount":"7","AlarmCount":"0","OverallStatus":"OK"}]}}[

       

    •  

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

        For Example:

       

      > curl http://192.168.0.10:8012/api/SEM/1.0/drives

      > OUTPUT: {"Drives":{"Drive":[{"DeviceTypeString":"Direct-access block device","FirmwareRevision":"AS09",
      "SerialNumber":"9XG5AJQ4","VendorId":"SEAGATE","ProductId":"ST91000640SS","TargetPortWwn":"5000c500571d1355",
      "TargetPortWwn2":"5000c500571d1356", "sd_path1":"n.a.","sd_path2":"n.a.","mpath":null, "DeviceIds":
      {"Descriptor":[{"@value":"5000c500571d1357", "@association":"ADDRESSED_LOGICAL_UNIT",
      "@designator_type":"NAA"},
      {"@value":"5000c500571d1355","@association":"TARGET_PORT",
      "@designator_type":"NAA"}, 
      {"@value":"5000c500571d1354","@association":"SCSI_TARGET_DEVICE","@designator_type":"NAA"},
      {"@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"}, 

       
  12. For detailed DAC monitoring information, refer to the "SHM CLI" reference in the Dell Storage PowerTools Server Hardware Manager Administrator's Guide.
  13. 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.
Notes

Prerequisites


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:

  • RSA NetWitness Suite S4s (Dell R620)
    • BIOS: 1.1.2
    • iDRAC: 1.23.23
    • PERC 21.1.0-0007
  • RSA NetWitness Suite S5 (Dell R630)
    • BIOS: 2.4.3
    • iDRAC:  2.50.50.50
    • PERC 25.3.005
 

Common DAC Monitoring Commands


The following table lists common SHM CLI commands used to monitor the DAC.
 
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> -enc=<enclosure-index>List Drives
./shmcli lds –a=<adapter-index> -enc=<enclosure-index>List Drive Slots
./shmcli lf –a=<adapter-index> -enc=<enclosure-index>List Fans
./shmcli lps –a=<adapter-index> -enc=<enclosure-index>List Power Supplies
./shmcli lts –a=<adapter-index> -enc=<enclosure-index>List Temperature Sensors

Attachments

    Outcomes