Skip to main content

Update or Install DRAC license from OS

I had a motherboard replaced due a DRAC failure.  Once the system came back up, I noticed the DRAC was still offline... ugg...

After further digging and several reboots, I determined that the DRAC was not a viable option to configure.  More digging indicated that my Enterprise DRAC license was not present.  Unfortunately this was hours after my change window expired.  So - now that I have a DRAC license, how do I get it on my system without a reboot.

~~~
[root@server ~]# ls /opt/dell/srvadmin/bin/idracadm && myRACADM="/opt/dell/srvadmin/bin/idracadm"
[root@server ~]# ls /opt/dell/srvadmin/bin/idracadm7 && myRACADM="/opt/dell/srvadmin/bin/idracadm7"

[root@server ~]# $myRACADM config -g cfgLanNetworking -o cfgNicSelection 1
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 -- Dedicated NIC
~~~

After you acquire the zip file from Dell, pkunzip it and copy the xml file to your server.  Then:

~~~ 
[root@server ~]# $myRACADM license import -f /home/jradtke/FD0000000XXXXXX.xml -c idrac.embedded.1

[root@server ~]# $myRACADM license view
iDRAC.Embedded.1
    Status               = OK
    Device               = iDRAC.Embedded.1
    Device Description   = iDRAC7
    Unique Identifier    = XXXXXXX
        License #1
            Status               = OK
            Transaction ID       = 2
            License Description  = iDRAC7 Enterprise License
            License Type         = PERPETUAL
            Entitlement ID       = FD000000XXXXXXX
            License Bound        = XXXXXX
            Expiration           = Not Applicable

 ~~~


Labels:

Comments

Post a Comment

Popular posts from this blog

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...
1 comment
Read more

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 ...
1 comment
Read more

"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.
Post a Comment
Read more