Skip to main content

rename DRAC from CLI OS

For some reason, a number of our physical hosts do not have their DRACs configured correctly, or according to our standard.

I wrote this script to clean them up.

#!/bin/bash
# Desc:  This horribly assembled bit of scripting is intended to configure the DRAC using
#        a few basic fundamental configuration variables.
#        The end result should be a host DRAC that is reachable via
#        <hostname>.mgmt.company.com

# A few helpful commands to review:
# /opt/dell/srvadmin/bin/idracadm7 getconfig -g cfgLanNetworking
# /opt/dell/srvadmin/bin/idracadm config -g cfgLanNetworking -o cfgDNSRacName `hostname -s`

yum -y install srvadmin-all srvadmin-idrac7
ls /opt/dell/srvadmin/bin/idracadm && myDRAC="/opt/dell/srvadmin/bin/idracadm"
ls /opt/dell/srvadmin/bin/idracadm7 && myDRAC="/opt/dell/srvadmin/bin/idracadm7"

if [ -z $myDRAC ]
then
  echo "ERROR: idracadm[7] was not found"
  echo "       yum -y install srvadmin-all srvadmin-idrac7 "
  exit 9
fi


# THIS >MAY< NEED TO BE UPDATED BASED ON LOCATION (GL vs PCW)
#/opt/dell/srvadmin/bin/idracadm7 getconfig -g cfgLanNetworking
cat << EOF > /tmp/iDRAC.cfg
cfgNicEnable=1
cfgNicIPv4Enable=1
cfgNicUseDhcp=1
cfgDNSServersFromDHCP=0
cfgDNSServer1=10.98.230.27
cfgDNSServer2=10.98.230.28
cfgDNSRacName=`hostname -s`
cfgDNSDomainName=mgmt.company.com
cfgDNSDomainNameFromDHCP=0
cfgDNSRegisterRac=1
EOF

cat /tmp/iDRAC.cfg | awk -F\= '{ print $1" "$2 }' | while read VAR VAL;
do
  $myDRAC config -g cfgLanNetworking -o $VAR $VAL
done

Comments

Popular posts from this blog

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things.  Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor.  (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb).  I'm not sure how to proceed.  This procedure worked for RHEVh, because it is quite a bit smaller.  Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.