Capturing a DSET Report on a Lattus Controller Node in 3.6.6 and Later Versions (DRAFT)

Overview

SR/Bug Information: Bugzilla – Bug 67002 Link will open in new window. and HGST QUANTUM-1481 Link will open in new window.

 

 

Product / Software Version: Lattus Controller Nodes with Lattus 3.6.6 or later version installed

 

 

Problem Description: The process for remotely collecting hardware information for a Lattus Controller Node using DSET was broken in the Lattus 3.6.6 release. See Bugzilla – Bug 67002 Link will open in new window. for details. Two workarounds are available.

 

 

 


Workaround 1

Load the IPMI Drivers Manually

 

  1. Load the ipmi drivers manually so you can do a full DSET collection without having to reboot / interrupt data traffic.

modprobe ipmi_si
modprobe ipmi_devintf

 

  1. Add the drivers to /etc/modules so they will be automatically started on subsequent reboots.

echo ipmi_si >> /etc/modules
echo ipmi_devintf >> /etc/modules

 

Enable DSET

 

The following steps are available in the Lattus Service Reference Guide in the "Enabling DSET" procedure in the "Collecting Hardware Information Using DSET" section of "Chapter 4: Tools and Utilities for Lattus."
 

 

  1. To run DSET and gather all relevant data, you must enable the following services on a Dell system. To enable the services on startup, enter the following code:

update-rc.d -f dataeng defaults
update-rc.d -f instsvcdrv defaults

 

  1. To start the services manually, enter the following code:

/etc/init.d/instsvcdrv start
/etc/init.d/dataeng start

 

 

Confirm Services are Running

 

  1. Confirm that the two above services are running and have a [+] next to them.

service --status-all

 

Run DSET on a Lattus Controller Node  

 

 

 

  1. Open a shell on the appropriate Lattus Controller Node.
  1. Run the following command:

 

dellsysteminfo

 

 

  1. When prompted, enter the root password.
  1. A summary of the available system information will be returned.

 

Note: An example DSET is attached (DSET033117.zip). Password is "dell".

 


Workaround 2

If the above Workaround 1 procedure is not successful, use the following . Note that this procedure requires someone to be on-site to reboot a Controller Node and use a USB drive to gather the report details.

 

Use the attached procedure (DSET_Procedure using OMSA for Ubuntu OS Dec 2013 V2.docx) to capture a DSET report for a Lattus Controller Node using OMSA for Ubunto OS.

 

Do not use the "Collecting Hardware Information Using DSET" procedure in "Chapter 4: Tools and Utilities for Lattus" in the Lattus Service Reference Guide for systems with Lattus 3.6.6 or later software installed.

 


 

 

The following steps are available in the Lattus Service Reference Guide in the "Running DSET on a Lattus Controller Node (Pre Lattus 3.6.6)" procedure in the "Collecting Hardware Information Using DSET" section of "Chapter 4: Tools and Utilities for Lattus."

 

Attachments
Title Last Updated Updated By
Dell DSET Example (DSET033117.zip)
04/03/2017 04:18 PM Tom Sajbel
DSET Procedure Using OMSA for Ubuntu OS Dec 2013 V2
03/08/2017 01:23 PM Tom Sajbel


This page was generated by the BrainKeeper Enterprise Wiki, © 2018