[Linux-PowerEdge] PE T150/T350 and RHEL7

[Giulio]

Here (page 10, small table in lower right)
  https://linux.dell.com/files/supportmatrix/RHEL_Support_Matrix.pdf
only T550 is certified for RHEL7, T150/T350 are not.

T150/T350 are certified for RHEL8 only, on page 6.

Is this definitive? Will T150/T350 never be supported on RHEL7?

We need to know this for planning purposes.

I'd swear I had seen RHEL7 as supported a few weeks ago on this page:
https://www.dell.com/support/home/en-us/product-support/product/poweredge-t350/drivers
but now it's gone, and only RHEL8 is available.


Thanks

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] Dell tech support: DSET -> iDrac/SupportAssist Collection

[Giulio]

> Ssh the DRAC, not the OS

We have vpn  access to the server, not iDrac.
I tried ssh from server itself to iDrac but it doesn't work, no
answer, even telnetting the http port gives no answer when originating
from the server itself.
We have basic iDrac with no dedicated NIC, it seems the iDrac will
recognize outside traffic to its IP and take it, but not traffic
coming from the server itself.

=
So, in the end,  because of a change in Dell Tech support (they cannot
read DSET output anymore), the level of support they can provide us
decreased substantially.

1) We have to produce the support bundle from another PC, because
racamd won't work due to license issue

2) Also, we have to update firmware/bios from Linux command line (as
we always did) because if we try to do that from the iDrac web
interface (the same used to produce the support bundle) we get
System Alert : LIC501: A required license is missing or expired.
Obtain an appropriate license then try again. If the problem persists,
contact technical support. Refer to your product documentation to
choose the contact method that is convenient for you

So, there's no way to use a single channel to do what Dell support
will ask us to do, we have to use command line for updating, and web
for support bundle.
Really not user friendly.

Thanks for your suggestions.

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] Dell tech support: DSET -> iDrac/SupportAssist Collection

[Giulio]

> Try
> racadm help techsupreport
Same message as previous post

> If that' doesn't work, install:
> srvadmin-idracadm7

Done.

> then do
> idracadm7 help techsupreport

# idracadm7 help techsupreport

Techsupreport -- Tech Support Report operations.

Techsupreport has multiple subcommands, view the help
as shown below.

Usage:

racadm techsupreport help collect
...
...


# idracadm7  techsupreport help collect
ERROR: SWC0242 : A required license is missing or expired.
   Obtain an appropriate license and try again, or contact your service
   provider for additional details.
Required License -- RACADM

# idracadm7  techsupreport
ERROR: SWC0242 : A required license is missing or expired.
   Obtain an appropriate license and try again, or contact your service
   provider for additional details.
Required License -- RACADM

# racadm supportassist
ERROR: SWC0242 : A required license is missing or expired.
   Obtain an appropriate license and try again, or contact your service
   provider for additional details.
Required License -- RACADM

# racadm techsupreport
ERROR: SWC0242 : A required license is missing or expired.
   Obtain an appropriate license and try again, or contact your service
   provider for additional details.
Required License -- RACADM
=

I imagine this is because we have basic iDrac (no upsell options)?


Thanks

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] Dell tech support: DSET -> iDrac/SupportAssist Collection

[Giulio]

> racadm supportassist ?

Thanks.

I tried and got this:

# racadm supportassist

NOTE:
This Integrated Dell Remote Access Controller does not support RACADM commands.
Please contact Dell Customer Service to upgrade your version of iDRAC.
The executed RACADM commands are not supported by the current version of
Integrated Dell Remote Access Controller (iDRAC) in the system.
To upgrade to latest version of iDRAC, contact Dell customer service.

=
# idracadm supportassist
is the same

=
The system is a  PE-T320, with basic/minimum iDrac
Lifecycle Controller = 2.50.50.50
12G iDRAC7 BASE V1.00 = 2.50.50

rpm -qa|grep srvadmin|grep rac

srvadmin-idrac-vmcli-7.3.0-4.12.1.el5
srvadmin-racdrsc-7.3.0-4.29.4.el5
srvadmin-racadm5-7.3.0-4.1.110.el5
srvadmin-idrac-snmp-7.3.0-4.29.4.el5
srvadmin-racsvc-7.3.0-4.1.110.el5
srvadmin-idrac-7.3.0-4.29.4.el5
srvadmin-racadm4-7.3.0-4.1.110.el5
srvadmin-idrac-ivmcli-7.3.0-4.15.4.el5
srvadmin-rac-components-7.3.0-4.29.4.el5
srvadmin-rac4-populator-7.3.0-4.1.110.el5
srvadmin-rac4-7.3.0-4.1.110.el5
srvadmin-idracadm-7.3.0-4.29.4.el5
srvadmin-rac5-7.3.0-4.1.110.el5

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] RAID failure

[Giulio Bottazzi]

Hi guys,
I'm her to ask for some help and knowledgeable advice. It seems my
RAID 1 has got some problem:

# mpt-status -v
ioc0 vol_id 0 type IM, 2 phy, 465 GB, state DEGRADED, flags ENABLED
ioc0 phy 1 scsi_id 9 SEAGATE  ST3500620SS  MS04, 465 GB, state
ONLINE, flags NONE
ioc0 phy 0 scsi_id 1 SEAGATE  ST3500620SS  MS04, 465 GB, state
FAILED, flags OUT_OF_SYNC

I suppose I should replace the driver and my question is: should I
replace it with an identical driver or are there alternatives?

Thanks in advance for any feedback.

Giulio.

-- 
Giulio Bottazzi <giulio.botta...@gmail.com>

PGP Key ID:BAB0A33F

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

[Linux-PowerEdge] racadm not working on CentOS 7.2 + idrac8

[Giulio]

PE-T330 with iDRAC8 Express

= PROBLEM
# /opt/dell/srvadmin/sbin/racadm getsysinfo
 
NOTE:
The current version of Integrated Dell Remote Access Controller (iDRAC)
that do not support the execution of RACADM commands.
Contact Dell customer service to upgrade to iDRAC Express or iDRAC Enterprise
The installed version of RACADM client executable that do not match the
generation of the server.
=

I would have expected some kind of output from the racadm command.
Instead, it's telling me to upgrade to iDRAC Express, but I have iDRAC Express,
see below.

Any help?


= SYSTEM CONFIG
# cat /etc/redhat-release
CentOS Linux release 7.2.1511 (Core)

# omreport licenses
Licenses information
 
Device Index   : 0
Device Status  : Ok
Device : iDRAC
Device Description : iDRAC8
Device ID  : XXX
License Index  : 0
Description: iDRAC8 Express License
Status : OK
Recommended Action : N/A
License Type   : Perpetual
Entitlement ID : FD000NNN
Expiry Date: N/A

# rpm -qa|grep idrac|sort
srvadmin-idrac-8.3.0-1908.9058.el7.x86_64
srvadmin-idrac-ivmcli-8.3.0-1908.9058.el7.x86_64
srvadmin-idrac-snmp-8.3.0-1908.9058.el7.x86_64
srvadmin-idrac-vmcli-8.3.0-1908.9058.el7.x86_64
srvadmin-idracadm-8.3.0-1908.9058.el7.x86_64


# dsu --inventory
1. OpenManage Server Administrator  ( Version : 8.3.0 )
2. BIOS  ( Version : 1.1.4 )
3. Lifecycle Controller  ( Version : 2.22.22.22 )
4. Dell 64 Bit uEFI Diagnostics, version 4239, 4239A27, 4239.35  ( Version :
4239A27 )
5. OS COLLECTOR 1.1, OSC_1.1, A00  ( Version : OSC_1.1 )
6. Power Supply  ( Version : 00.1B.71 )
7. PERC H730 Adapter Controller 0 Firmware  ( Version : 25.3.0.0016 )
8. Firmware for  - Disk 0 in Backplane 1 of PERC H730 Adapter Controller 0 in
Slot 2   ( Version : TT31 )
9.  iDRAC  ( Version : 2.22.22.22 )
10. 13G SEP Firmware, BayID: 1  ( Version : 2.23 )

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: [Linux-PowerEdge] dsu performs a 'yum upgrade -y' when upgrading firmware

[Giulio]

On Mon, Mar 7, 2016 at 5:02 PM,   wrote:

> DSU only facilitates the system updates using the packages provided by
> various teams.

Can you explain this:

# strings /usr/sbin/dsu | grep "yum.*upgrade"
yum upgrade -y
#

what's the purpose of dsu using "yum upgrade -y"?


# rpm -q dell-system-update
dell-system-update-1.2-16.02.00.x86_64
#

Thanks

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Setting Service Tag only allowed with old libsmbios?

[Giulio Orsero]

After a motherboard swap performed by a Dell tech on a PE840 we were left
with a Service Tag set to 1.

We are using CentOS 5.x / libsmbios-2.2.19-10.1.el5, so I tried
smbios-sys-info --service-tag --set=123456
but I got
Setting new tag value: 123456
Traceback (most recent call last):
...
...
raise Exception(set service tag not yet supported.)

I saw in the archives of this list a reference to the serviceTag binary from
libsmbios-0.13.5, so I downloaded this old version, compiled it and I
managed to update the ServiceTag using the serviceTag utility.

Is there a way to update the Service Tag using the current
libsmbios-2.2.19-10.1.el5 that gets automatically installed from the Dell
online repo?

Thanks
-- 
giul...@pobox.com

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq

Re: Issues with OpenManage + CentOs 5.4

[Giulio Orsero]

On Thu, Sep 30, 2010 at 15:08, Chris Szilagyi ch...@apex-internet.com wrote:
 Thanks... so from that I can see that since I have a PE2400, that the script
 is complaining about the hardware.  Does anybody know how to get the script
 to accept the PE2400 (or any other unsupported hardware)?  Or am I pretty
 much out of luck?  I don't know how to find and modify that script, or if

Some time ago I managed to install 5.x and 6.1 on a VMware image (no
Dell hardware) using:

export OMIIGNORESYSID=1

before running rpm -Uvh ...

-- 
giul...@pobox.com

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq

Re: raidcfg not finding controller on Dell PE M610 blade, PE T310 too

[Giulio Orsero]

On Tue, Dec 1, 2009 at 17:13, Jaco Engelbrecht b...@serendipity.org.za wrote:

 I have a Dell PE M610 and PE1955 blade, which is failing to detect their
 RAID controllers when using the Dell Deployment Toolkit (DTK)'s raidcfg
...
 However, raidcfg does not find any RCs:
 [r...@bob ~]# /opt/dell/toolkit/bin/raidcfg -ctrl
 Controller does not exist

I have a similar problem with a PERC H200 in a PET310.
I installed dell-toolkit.rpm v.3.2.0 in our custom boot/diag cd (based
on CENTOS5.4 kernel/libs/binaries).

syscfg --pci sees it
...
PCI Bus: 3, Device: 0, Function: 0
  Vendor:1000 - LSI Logic / Symbios Logic
  Device:0072 - SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon]
  Sub Vendor:1028 - Dell
  Sub Device:1F1D - PERC H200 Adapter
  Slot:  01
  Class: 01 - Storage
  SubClass:  07 - N/A

but raidcfg -ctrl does not: raidcfg -ctrl - Controller does not exist

Our boot image is very minimal. Maybe raidcfg needs some particular
kernel module loaded to work correctly?

I put Debug=On in stsvc.ini and got this output:

RAIDCFG - Start Debug
RAIDCFG - Walking through all the command line args.
RAIDCFG - RAIDCFG compiled at 15:15:25 Oct 27 2009
command run on Tue Mar 23 14:25:34 2010
RAIDCFG - RAIDCFG Command Line Options: -ctrl
RAIDCFG - Calling ValInit
RAIDCFG - Begin: CMain::get_controllers_in_system()
RAIDCFG - Inside alloc_build_pci_cfg_list
RAIDCFG - Begin: CMain::check_PCI_BIOS
RAIDCFG - Begin: CMain::intInstallCheck
RAIDCFG - intInstallCheck - after setting SMBIOSReq params.
RAIDCFG - intInstallCheck - DCHBASSMBIOSCommand has passed
RAIDCFG - End: CMain::check_PCI_BIOS
RAIDCFG - PCI Identification Procedure:
RAIDCFG - Number of PCI Buses: 4.
RAIDCFG - Adding to PCICfg: Bus=0 Device:0 Func:0
RAIDCFG - Adding to PCICfg: Bus=0 Device:3 Func:0
RAIDCFG - Adding to PCICfg: Bus=0 Device:5 Func:0
RAIDCFG - Adding to PCICfg: Bus=0 Device:8 Func:0
RAIDCFG - Adding to PCICfg: Bus=0 Device:8 Func:1
RAIDCFG - Adding to PCICfg: Bus=0 Device:8 Func:2
RAIDCFG - Adding to PCICfg: Bus=0 Device:8 Func:3
RAIDCFG - Adding to PCICfg: Bus=0 Device:10 Func:0
RAIDCFG - Adding to PCICfg: Bus=0 Device:10 Func:1
RAIDCFG - Adding to PCICfg: Bus=0 Device:1a Func:0
RAIDCFG - Adding to PCICfg: Bus=0 Device:1c Func:0
RAIDCFG - Adding to PCICfg: Bus=0 Device:1c Func:2
RAIDCFG - Adding to PCICfg: Bus=0 Device:1c Func:3
RAIDCFG - Adding to PCICfg: Bus=0 Device:1c Func:4
RAIDCFG - Adding to PCICfg: Bus=0 Device:1d Func:0
RAIDCFG - Adding to PCICfg: Bus=0 Device:1e Func:0
RAIDCFG - Adding to PCICfg: Bus=0 Device:1f Func:0
RAIDCFG - Adding to PCICfg: Bus=0 Device:1f Func:2
RAIDCFG - Adding to PCICfg: Bus=0 Device:1f Func:5
RAIDCFG - Adding to PCICfg: Bus=1 Device:3 Func:0
RAIDCFG - Adding to PCICfg: Bus=2 Device:0 Func:0
RAIDCFG - Adding to PCICfg: Bus=2 Device:0 Func:1
RAIDCFG - Adding to PCICfg: Bus=3 Device:0 Func:0
RAIDCFG - Inside assign_pci_slot_numbers
+-+--+--+
| Bus |Device| Slot |
+-+--+--+
|0| 0| 0|
|0| 3| 0|
|0| 5| 0|
|0|16| 0|
|0|1a| 0|
|0|1c| 0|
|0|1d| 0|
|0|1f| 0|
|3| 0| 1|
|4| 0| 2|
|5| 0| 3|
|6| 0| 4|
|7| 0| 5|
|2| 0| 0|
|1| 3| 0|
+-+--+--+
RAIDCFG - Begin: CVALTalker::getVALControllers()
RAIDCFG - Calling ValGetControllers()
RAIDCFG - getVALControllers(): numCtrls is 0
RAIDCFG - End: CVALTalker::getVALControllers()
RAIDCFG - After enumeration
RAIDCFG - End: CMain::get_controllers_in_system()
RAIDCFG - Get All Controllers
RAIDCFG - End Debug

Controller does not exist
RAIDCFG - In ~CVALTalker()

I tried stracing raidcfg, but I got some kind of infinite loop
(command would not terminate when straced , data kept scrolling and
scrolling, I waited for 20/30 secs)

Thanks

-- 
giul...@pobox.com

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq

Re: omreport storage: are all possible output values documented?

[Giulio Orsero]

On Mon, Mar 22, 2010 at 06:20,  mohan_g_mur...@dell.com wrote:

 e.g., to find the possible states and properties of an Virtual Disk you
 can find under the Virtual Disk Properties section
 (http://support.dell.com/support/edocs/software/svradmin/6.2/en/OMSS/vdm
 gmt.htm#wp1424964 )of the user guide.

Unfortunately this is more geared towards the GUI front-end.

For instance, for the status the table says Warning/non-critical,
but I think in the omreport output I might see either Warning or
non-critical but not Warning/non-critical, right?

I downloaded the script Ben pointed to, and that contains a reference
of possible values.

The problem now is that I tested OMSA 5.5.0, 6.1.0, 6.2.0 and the
position of the columns using -fmt ssv keeps changing, the names of
the columns do the same (ie: Type - Bus Protocol); ideally this
could be documented too, but this I can easily test by running
omreport once for every OMSA version and checking the differences.

Thanks

-- 
giul...@pobox.com

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq

omreport storage: are all possible output values documented?

[Giulio]

OMSA 6.2

I'm interested in finding docs which will explain in detail all the possible
output values of the omreport storage controller and related commands.

For instance, on one of my systems omreport storage vdisk will output
...
...
State   : Ready
Progress: Not Applicable
..

Which other values can State: show? Progress:?

The reason is to be able to use omreport's output in scripts.

I looked here 
http://support.dell.com/support/edocs/software/svradmin/6.2/en/CLI/html/storage.htm#wp1077100
but coulnd't find a definitive reference.

Thanks
-- 
giul...@pobox.com

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq

PERC H200: anyone that can share sas2ircu cmd line util?

[Giulio]

PET310, CentOS5.4, mpt2sas 02.00.02.00

For previous MPT controllers we used LSI's lsiutil utility as a light weight
alternative to OMSA's omreport storage controller.

Now with the new SAS2 controllers, such as the PERC H200, lsiutil won't work
anymore (tried with v1.62), and you need the new sas2ircu utility, whose
syntax is documented here:
http://www.lsi.com/DistributionSystem/AssetDocument/SAS2_IR_User_Guide.pdf

I asked LSI for the utility, but they won't give it to me, because they only
distribute it to LSI resellers (not Dell's).

Is there anyone who somehow got this util and can make it available?

Thanks
-- 
giul...@pobox.com

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq

Re: PERC H700 and linux 2.6.33

[Giulio Orsero]

On Wed, Mar 10, 2010 at 16:08, cosmih cos...@gmail.com wrote:

 So, no one has yet tried the new H700 controller with 2.6.33 kernel ?

Maybe not.
Have you tried looking for the pci ids?

1) Download http://pciids.sourceforge.net/v2.2/pci.ids.gz

2) See that H700 has device id 0079

3) Check kernel.org log for the megaraid_sas driver
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6-stable.git;a=history;f=drivers/scsi/megaraid/megaraid_sas.c;h=409648f5845f06c6ff3d0c435164efc060e561ba;hb=HEAD

4) Check this commit
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6-stable.git;a=commitdiff;h=6610a6b354d6c3377a1e79cd1d760ffe4358245c

It would appear the answer to your question is yes.

-- 
giul...@pobox.com

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq

OMSA 6.2 + DSET 1.8.1: bad mix?

[Giulio]

PET300, CENTOS 5.4, OMSA 6.2.

I downloaded DSET 1.8.1 from here
http://support.dell.com/support/topics/global.aspx/support/en/dell_system_tool
and chose to install it permanently on hard disk into /opt/dell/dset

Then I issued

# time /usr/bin/clearesm
Dell System E-Support Tool
@Copyright Dell Inc. 2004-2009  Version 1.8.1 build 100
* Collecting Dell OpenManage information ... [Please wait]
There was a problem loading the OMSA driver/service
 
real5m1.722s
user0m1.466s
sys 0m0.056s
#

After this I could see these 2 processes still active (ps ax):
S 0:00 /bin/bash ./omsaliteinstall.sh
D 0:00 rmmod ipmi_devintf --wait

I was connected remotely via telnet.
I issued
# reboot
the system would not reboot correctly, I went to the console and saw it was
stuck at stopping IPMI drivers.

I wanted to simulate a situation in which I could not go to the console, so
I tried resetting it remotely.

Many network services had been shut down, luckily OMSA web service was still
active, so I used 
OMSA - shutdown - no os shutdown + power cycle
and the system came back up.

Then I retried the very same thing, but this time in OMSA I chose
OMSA - shutdown - OS shutdown first  (default setting in OMSA)
this didn't succeed, and after that OMSA wouldn't let me power cycle
anymore, because when going to the shutdown page I got
Operating system shutdown is disabled.  
Remote Shutdown Action is disabled  
I could only press shutdown which wouldn't work.
So I had to walk to the system and manually power cycle it.


The DSET README says

* This Hotfix is for supporting Dell Systems having OM6.1 on
  * PER710, PER610, PEM610, PER905, PE6950, PE1950
  * Red Hat Enterprise Linux (AS, ES) 4 update 6 for i386 and x86_64
  * Red Hat Enterprise Linux (AS, ES) 4 update 7 for i386 and x86_64
  * Red Hat Enterprise Linux (AS, ES) 5 update 3 for i386 and x86_64
  
NOTE: It is certified only for the above mentioned Dell Systems  operating
systems having OM6.1 on System Under Test(SUT)


Does the above mean I cannot use DSET 1.8.1 with OMSA 6.2?
If so, where do I get a DSET which will work with OMSA 6.2?

I downloaded the DSET from the default link on the offical DSET page, so I
thought I was ok.

Since unloading kernel modules is not always a good thing, should I just
edit the /etc/rc.d/init.d/ipmi and make stop() a noop?


Thanks
-- 
giul...@pobox.com

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq

Re: OMSA 6.2 + DSET 1.8.1: bad mix?

[Giulio]

Problem is the following:

- /usr/bin/clearesm at some point runs /opt/dell/dset/bin/omsaliteinstall.sh

- that in turns sources /opt/dell/dset/bin/dsetfunctions, and then executes
the functionGet_OMSA_Versions from dsetfunctions. This function fails to
correctly set the variable $OMSAversion, this causes omsaliteinstall.sh to
fail.

Reason is that dsetfunctions does:
export OMSApath=`grep -i openmanage.omacore.installpath 
/etc/omreg.cfg | awk -F = '{print $2}'`
this will set OMSApath to /opt/dell/srvadmin, then
if [ -e $OMSApath/OMIVER.DB ]; then
export OMSAversion=`grep -i OMI_OM_VERSION $OMSApath/OMIVER.DB
 | awk -F = '{print $2}'`
else
if [ -e $OMSApath/omil ]; then
echo OMSA installed is very old. Strongly recommend to ...
OMSAversion=2.0
OMSAomssversion=2.0
fi
fi
the file OMIVER.DB does not exist at that location, and where it actually
exists
/opt/dell/srvadmin/var/lib/srvadmin-omilcore/OMIVER.DB
it has just
OMI_OM_VERSION=%{PACKAGE_VERSION}
so it would fail regardless.

I edited omsaliteinstall.sh and manually forced the OMSA version
Get_OMSA_Versions
OMSAversion=6.2.0 === brute force method

and now I can use clearesm and it runs in a few seconds

# time /usr/bin/clearesm
Dell System E-Support Tool
@Copyright Dell Inc. 2004-2009  Version 1.8.1 build 100
* Collecting Dell OpenManage information ... [Please wait]
* Clearing Hardware Log ...
 
real0m7.526s
user0m3.105s
sys 0m0.232s
#




On Tue, 26 Jan 2010 09:10:54 +0100, Giulio giul...@gmail.com wrote:

PET300, CENTOS 5.4, OMSA 6.2.

I downloaded DSET 1.8.1 from here
http://support.dell.com/support/topics/global.aspx/support/en/dell_system_tool
and chose to install it permanently on hard disk into /opt/dell/dset

Then I issued

   # time /usr/bin/clearesm
   Dell System E-Support Tool
   @Copyright Dell Inc. 2004-2009  Version 1.8.1 build 100
   * Collecting Dell OpenManage information ... [Please wait]
   There was a problem loading the OMSA driver/service
 
   real5m1.722s
   user0m1.466s
   sys 0m0.056s
   #

After this I could see these 2 processes still active (ps ax):
   S 0:00 /bin/bash ./omsaliteinstall.sh
   D 0:00 rmmod ipmi_devintf --wait

I was connected remotely via telnet.
I issued
   # reboot
the system would not reboot correctly, I went to the console and saw it was
stuck at stopping IPMI drivers.

I wanted to simulate a situation in which I could not go to the console, so
I tried resetting it remotely.

Many network services had been shut down, luckily OMSA web service was still
active, so I used 
   OMSA - shutdown - no os shutdown + power cycle
and the system came back up.

Then I retried the very same thing, but this time in OMSA I chose
   OMSA - shutdown - OS shutdown first  (default setting in OMSA)
this didn't succeed, and after that OMSA wouldn't let me power cycle
anymore, because when going to the shutdown page I got
   Operating system shutdown is disabled.  
   Remote Shutdown Action is disabled  
I could only press shutdown which wouldn't work.
So I had to walk to the system and manually power cycle it.


The DSET README says

* This Hotfix is for supporting Dell Systems having OM6.1 on
  * PER710, PER610, PEM610, PER905, PE6950, PE1950
  * Red Hat Enterprise Linux (AS, ES) 4 update 6 for i386 and x86_64
  * Red Hat Enterprise Linux (AS, ES) 4 update 7 for i386 and x86_64
  * Red Hat Enterprise Linux (AS, ES) 5 update 3 for i386 and x86_64
  
NOTE: It is certified only for the above mentioned Dell Systems  operating
systems having OM6.1 on System Under Test(SUT)


Does the above mean I cannot use DSET 1.8.1 with OMSA 6.2?
If so, where do I get a DSET which will work with OMSA 6.2?

I downloaded the DSET from the default link on the offical DSET page, so I
thought I was ok.

Since unloading kernel modules is not always a good thing, should I just
edit the /etc/rc.d/init.d/ipmi and make stop() a noop?


Thanks
-- 
giul...@pobox.com

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq

hardware repo question: notable links

[Giulio]

The main page of the repo 
http://linux.dell.com/repo/hardware/
says

If you wish to install a particular version of OMSA and *not* be
automatically updated to the latest version when it comes out, follow the
links below to one of the OMSA versions in this repository. All links in the
Notable Links column are automatically updated, so if you use the link,
your installation will be automatically updated. Other links are static,
which allow you to remain on a specific release if that is your site
policy.

If I choose the fixed link for 6.2 I understand the svradmin-* packages will
remain 6.2, but what happens to the other packages available from the repo
(firmware update tools, smbios, bios/fw payloads)? 
Are they also never updated?

Is there a way to configure yum in such a way that the srvadmin-* packages
will remain NOT updated and fixed at 6.2, while everything else is updated?

Maybe using latest notable link and putting
exclude = srvadmin-*  (will the -* wildcard work?)
in /etc/yum.conf?

Thanks.
-- 
giul...@pobox.com

___
Linux-PowerEdge mailing list
Linux-PowerEdge@dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq