Capturing a DSET Report on a Lattus Controller Node in 3.6.6 and Later Versions (DRAFT) |
SR/Bug Information: Bugzilla – Bug 67002
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
|
Load the IPMI Drivers Manually
modprobe ipmi_si
modprobe ipmi_devintf
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."
update-rc.d -f dataeng defaults
update-rc.d -f instsvcdrv defaults
/etc/init.d/instsvcdrv start
/etc/init.d/dataeng start
Confirm Services are Running
service --status-all
Run DSET on a Lattus Controller Node
dellsysteminfo
Note: An example DSET is attached (DSET033117.zip). Password is "dell".
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 |
This page was generated by the BrainKeeper Enterprise Wiki, © 2018 |