Skip to main content

Script to update Dell Firmware

There are a few other scripts/tools out there to do this.. but they all seem to have some stupid dependencies (this one is no exception).

#!/bin/bash

# $Id: update_firmware.sh,v 1.9 2014/04/25 18:42:55 root Exp root $

# Author: James.Radtke@company.com
# Purpose:  Script to download and apply firmware updates
# Status:   Stable, but likely needs some work

# TODO:     I would like to require a flag to run the REBOOT REQUIRED updates
# Maintained at:   rhnsat01:/root/bin/update_firmware.sh
#        

#
#  VARIABLES
#
FIRMWARE_LOG=/var/log/dell_firmware.log

PRETTYDATE=`date +%Y%m%d-%H%M`
REBOOT_RECD=0

# PLEASE NOTE: EACH OF THE PACKAGES LISTED IN THE PKGS VARIABLES ARE THE
#   LEAST-COMMON-DENOMINATOR FOR EACH PACKAGE. (i.e. they only differ by version number).
NON_REBOOT_PKGS="ESM Lifecycle-Controller Power_Firmware"
REBOOT_PKGS="R[1-9][12]0_BIOS BIOS Network_Firmware SAS-RAID_Firmware Fibre-Channel_Firmware"
#
MYPWD=`pwd`

# #######################################################
# BEGIN
# #######################################################

# FIRST THINGS.. FIRST
if [ "`dmidecode -s system-manufacturer`" != 'Dell Inc.' ]
then 
  echo "Dude, This is not a Dell"
  exit 9
fi

echo "NOTE: You may find the output of this script in:"
echo "      cat /var/log/dell_firmware.log"
echo "      Updates log to /var/log/dell/updatepackage/log/support"

if [ ! -d /var/log/dell/updatepackage/log/support ]
then
  mkdir -p /var/log/dell/updatepackage/log/support
fi

echo "[`date +%Y%m%d-%H%M`] START"
echo "[`date +%Y%m%d-%H%M`] START" >> $FIRMWARE_LOG
/opt/dell/srvadmin/bin/omreport system version  >> /var/log/dell/updatepackage/log/support/omreport-`date +%Y%m%d-%H%M`.out

rm -f /var/tmp/Dell/`dmidecode -s system-product-name`/*
cd /var/tmp
wget -r -nH --cut-dirs=2 --no-parent --reject "index.html*" "http://rhnsat01.company.com/pub/sfw/Dell/`dmidecode -s system-product-name`/" > /dev/null 2>&1

cd "/var/tmp/Dell/`dmidecode -s system-product-name`/"
chmod 755 *

# IN CASE IT'S NOT OBVIOUS - THIS STANZA TRAVERSES THE NON_REBOOT UPDATES
for PKG in $NON_REBOOT_PKGS
do
  MYFW=`ls | grep ^${PKG} | sort | tail -1`
  if [ ! -z $MYFW ]
  then
    echo "[`date +%Y%m%d-%H%M`] Analysing ${PKG}"
    echo "[`date +%Y%m%d-%H%M`] Analysing ${PKG}" >> $FIRMWARE_LOG
    # CHECK IF UPDATE IS APPLICABLE
    sh ./${MYFW} -c -n -q
    if [ $? == 0 ]
    then
      echo "[`date +%Y%m%d-%H%M`] Updating ${PKG} with $MYFW"
      echo "[`date +%Y%m%d-%H%M`] Updating ${PKG} with $MYFW" >> $FIRMWARE_LOG
      sh ./${MYFW} -n -q
    else
      echo "[`date +%Y%m%d-%H%M`] Up-to-date $MYFW"
      echo "[`date +%Y%m%d-%H%M`] Up-to-date $MYFW" >> $FIRMWARE_LOG
    fi
  fi
done
# IN CASE IT'S NOT OBVIOUS - THIS STANZA TRAVERSES THE REBOOT UPDATES
for PKG in $REBOOT_PKGS
do
  MYFW=`ls | grep ^${PKG} | sort | tail -1`
  if [ ! -z $MYFW ]
  then
    echo "[`date +%Y%m%d-%H%M`] Analysing ${PKG}"
    echo "[`date +%Y%m%d-%H%M`] Analysing ${PKG}" >> $FIRMWARE_LOG
    # CHECK IF UPDATE IS APPLICABLE
    sh ./${MYFW} -c -n -q
    if [ $? == 0 ]
    then
      echo "[`date +%Y%m%d-%H%M`] Updating ${PKG} with $MYFW"
      echo "[`date +%Y%m%d-%H%M`] Updating ${PKG} with $MYFW" >> $FIRMWARE_LOG
      sh ./${MYFW} -n -q
    else
      echo "[`date +%Y%m%d-%H%M`] Up-to-date $MYFW"
      echo "[`date +%Y%m%d-%H%M`] Up-to-date $MYFW" >> $FIRMWARE_LOG
    fi
  fi
done

if [ ${REBOOT_RECD} != 0 ]
then
  echo "NOTE: Important - a reboot is required to complete updates"
  echo "      Since Dell produces low-quality patches, this process will"
  echo "      likely need to be repeated"
  echo " run the following after the reboot to view versions:"
  echo " # omreport system version"
fi

echo "[`date +%Y%m%d-%H%M`] END "
echo "[`date +%Y%m%d-%H%M`] END " >> $FIRMWARE_LOG
cd "$MYPWD"

exit 0

Comments

Popular posts from this blog

RHN Satellite Server (spacewalk) repomd.xml not found

"repomd.xml not found" If you add a channel, or if your RHN cache gets corrupted, and one of your guests complains that it cannot find repomd.xml for jb-ews-2-x86_64-server-5-rpm (for example) - you need to rebuild your repodata cache. Normally this is an automated job - which is exemplified by the fact that you have obviously built out your entire Satellite environment and never had to do any of the steps you are about to do. So - some prep work: Open 3 terminals to your Satellite Server and run: # Term 1 cd /var/cache/rhn watch "ls -l | wc -l" # Term 2 pwd cd /var/log/rhn tail -f rhn_taskomatic_daemon.log # Term 3 satellite-sync --channel=jb-ews-2-x86_64-server-5-rpm Once the satellite-sync has completed, you >should< see the count increment by one.  If you are unlucky (like me) you will not. You then need to login to the Satellite WebUI as the satellite admin user. Click on the Admin tab (at the top) Task Schedules (on the left) fin

Install RHEL 7 on old HP DL380 g5

Someone at work had been running RHEL on an HP DL380 G5 and blew it up.  After several attempts at doing an installation that made me conclude the hardware was actually bad... I kept digging for the answer. Attempt install and Anaconda could not find any disks - try a Drivers Disk (dd.img) both cciss and hpsa.   -- once we did that, when the system would reboot it would say it could not find a disk. hmmm. Boot from your installation media and interrupt the startup at grub. Add hpsa.hpsa_allow_any=1 hpsa.hpsa_simple_mode=1 to the line starting with linuxefi press CTRL-X to boot. Once the system restarts after the install, you need to once again interrupt the startup and add the line from above. After the system starts, edit /etc/default/grub and add those 2 parameters to the end of the line starting with GRUB_CMDLINE_LINUX (which likely has quiet at the end of the line currently). then run # cp /boot/grub2/grub.cfg /boot/grub2/grub.cfg.orig # grub2-mkconfig -o /boot/grub2

MOTD with colors! (also applies to shell profiles)

I'm not sure why I had never looked into this before, but this evening I became obsessed with discovering how to present different colored text in the /etc/motd. A person had suggested creating a shell script (rather than using special editing modes in vi, or something) and I agree that is the simplest way of getting this accomplished quickly. This most noteworthy portion of this script is the following: RESET="\033[0m" that puts the users shell back to the original color. I typically like a green text on black background. Also - a great reference for the different colors and font-type (underscore, etc...) https://wiki.archlinux.org/index.php/Color_Bash_Prompt I found this example on the web and I wish I could recall where so that I could provide credit to that person. #!/bin/bash #define the filename to use as output motd="/etc/motd" # Collect useful information about your system # $USER is automatically defined HOSTNAME=`uname -n` KERNEL=`un