OMSA on PowerEdge 1600SC

[Baird, Josh]

A quicker "fix" is to edit srvadmin-install a bit:

if [ -n "${SYSID}" ]; then
     if [ "${SYSID}" = "0134" ] ||  [ "${SYSID}" = "0135" ]  || [
"${SYSID}" = "0141" ]; then
        echo "  Unsupported system (sysid=${SYSID})"
        SetErrorAndInterrupt 1
     fi
  fi

Change that to..


  if [ -n "${SYSID}" ]; then
     if [ "${SYSID}" = "0134" ] ||  [ "${SYSID}" = "0141" ]; then
        echo "  Unsupported system (sysid=${SYSID})"
        SetErrorAndInterrupt 1
     fi
  fi


Josh

-----Original Message-----
From: Robert Terzi [mailto:rct at r-t.org] 
Sent: Wednesday, February 13, 2008 1:55 PM
To: Baird, Josh
Subject: Re: OMSA on PowerEdge 1600SC

Baird, Josh wrote:
> I am getting an unsupport system error on 5.2 and 5.3:
> 
>   Unsupported system (sysid=0135)
> 
> Any ideas?

Yes, I remember getting that.  I believe what I did was
to just install the rpms directly instead of using the
install script.  I had to do that for Mandriva install
anyway since it wasn't RHEL.  I forget if I had to
do that for CentOS too.

I wrote this for mandriva:
http://wiki.mandriva.com/en/Docs/SysAdmin/Dell_OpenManage

It should be pretty close for most similar RPM based systems.

Note:  I also got this reply after I posted my note
about mandriva.  Didn't have enough context to make sense and
I already had things working so I didn't pursue it.
It may be a fixed version of setup.sh.

http://lists.us.dell.com/pipermail/linux-poweredge/2007-November/033686.
html