I was playing around with an older idrac 6 server Dell R210 ii and discovered this when I was trying to run a memtest remotely. It was a simple fix, although I wish the error was a little more obvious. The fix is to go to:
In the idrac 6 interface; go to system > console/media, then click configuration and enable virtual media, and click auto attach. Once you do that, click Apply.
I circled the options in the following image with handy dandy SNIP, ha ha.
I was working on something with an IP conflict, and then locked myself out of routing via the VPN, so the quickest way to do a fix, was to change the IP of my idrac via command line. Apparently, you can do almost everything through command line.
First step is to get onto your idrac, replacing root and IP with your own information. Note, default username and password is root – calvin. If you have a newer idrac, I think starting around idrac8, there is a tab on the server that has the default idrac username and password:
You should now have a print out of your current configuration for your NIC. To change it, you just do the following:
Give it a few seconds, and it should kick you out, and now have the new IP address.
If you want a full subset of the documentation go here: http://ftp.dell.com/Manuals/all-products/esuprt_electronics/esuprt_software/esuprt_remote_ent_sys_mgmt/integrated-dell-remote-access-cntrllr-7-v1.30.30_User%27s%20Guide_en-us.pdf
Otherwise here is a snippet:
% Get all iDRAC settings in a file
racadm get -f config.txt
If you like you can change the contents of config.txt and apply it back to iDRAC
racadm set -f config.txt
% Set password for root userracadm set iDRAC.Users.2.Password PASSWORD"
% List all ssh keys for root userracadm sshpkauth -i 2 -v -k all
% Add ssh key to root userracadm sshpkauth -i 2 -k 1 "CONTENTS OF PUBLIC KEY"
% Delete ssh key for root userracadm sshpkauth -i 2 -d -k 1
% Get iDRAC IP config
racadm getniccfg
racadm get iDRAC.NIC
% set iDRAC IP
Using config command:
racadm config -g cfgLanNetworking -o cfgNicEnable 1
racadm config -g cfgLanNetworking -o cfgNicIpAddress x.x.x.x
racadm config -g cfgLanNetworking -o cfgNicNetmask 255.255.255.0
racadm config -g cfgLanNetworking -o cfgNicGateway x.x.x.x
racadm config -g cfgLanNetworking -o cfgNicUseDHCP 0
racadm config -g cfgLanNetworking -o cfgDNSServersFromDHCP 0
racadm config -g cfgLanNetworking -o cfgDNSServer1 y.y.y.y
racadm config -g cfgLanNetworking -o cfgDNSServer2 y.y.y.y
• Using set command:
racadm set iDRAC.Nic.Enable 1
racadm set iDRAC.IPv4.Address x.x.x.x
racadm set iDRAC.IPv4.Netmask 255.255.255.0
racadm set iDRAC.IPv4.Gateway x.x.x.x
racadm set iDRAC.IPv4.DHCPEnable 0
racadm set iDRAC.IPv4.DNSFromDHCP 0
racadm set iDRAC.IPv4.DNS1 y.y.y.y
racadm set iDRAC.IPv4.DNS2 y.y.y.y
% Set iDRAC DNS Nameracadm set iDRAC.NIC.DNSRacName iDRACNAME
% Set iDRAC domain nameracadm set iDRAC.NIC.DNSDomainName DOMAIN.NAME
% Set iDRAC DNS Server
racadm config -g cfgLanNetworking -o cfgDNSServer1 x.x.x.x
racadm config -g cfgLanNetworking -o cfgDNSServer2 y.y.y.y
% Set Front LCD to hostnameracadm set System.LCD.Configuration 16
% Reset iDRAC to factory defaultsracadm racresetcfg
% Reset/Reboot iDRAC
racadm racreset OPTIONS
Options : soft, hard, cold
or
racadm serveraction powercycle
% Get Serial number (service tag)racadm getsvctag
% Get current system informationracadm getsysinfo
% Configure one-time-boot to PXE
racadm set BIOS.OneTimeBoot.OneTimeBootMode OneTimeBootSeq
racadm set BIOS.OneTimeBoot.OneTimeBootSeqDev NIC.Integrated.1-1-1
% Configure persistent Boot Device
racadm config -g cfgServerInfo -o cfgServerBootOnce 0
racadm config -g cfgServerInfo -i cfgServerFirstBootDevice HDD
% Check boot order listracadm get BIOS.BiosBootSettings.bootseq
% Disable HyperThreadingracadm set BIOS.ProcSettings.LogicalProc Disabled
% Disable OS to iDRAC pass-thru for iDRAC service module (automatically create a pseudo NIC in OS)racadm set iDRAC.OS-BMC.AdminState Disabled
% Change SNMP public community stringracadm set iDRAC.SNMP.AgentCommunity NEW STRING
% Disable ASRracadm config -g cfgRacTuning -o cfgRacTuneAsrEnable 0
% Configure Serial redirection
racadm config -g cfgSerial -o cfgSerialConsoleEnable 1
racadm config -g cfgSerial -o cfgSerialBaudRate 115200
racadm config -g cfgSerial -o cfgSerialCom2RedirEnable 1
racadm config -g cfgSerial -o cfgSerialTelnetEnable 0
racadm config -g cfgSerial -o cfgSerialSshEnable 1
to access console via ssh console com2
% Disable Serial On Lanracadm config -g cfgImpiSol -o cfgIpmiSolEnable 0
% Change Power Profileracadm set BIOS.SysProfileSettings PerfPerWattOptimizedOs
% Set AC Power Recovery
racadm set BIOS.SysSecurity.AcPwdRcvry Last
racadm set BIOS.SysSecurity.AcPwdRcvryDelay Immediate
% Get RAID physical Disk information
racadm raid get pdisks
racadm raid get pdisks -o (all information)
racadm raid get pdisks -o -p state,size (specific information)
% Get RAID Virtual Disk InformationRacadm raid get vdisks
I kept getting these errors when I would log into my older idrac 6 cards. You can fixing it by putting IE11 into compatability mode, but I also found it easier to update the idrac to the latest 2.91 version. These were the errors I was getting:
I updated one as far back as 1.43 to this version, no middle version required. Enjoy! I pulled these files right off of dells website. The only file you need to upload is the firming.d6. It was taken out of the ESM_Firmware_MXKG2_WN32_2.91_A00.EXE.
Dell iDRAC Monolithic Release 2.91
http://vivithemage.com/extra/Dell-11G/firmimg.d6
If you want to use the virutal console, you will probably have to switch from native to JAVA, as native was not working for me in my old firefox version, or IE11, even with compatibility enabled.
I had this issue updating my older R410, R610, and R710 servers the other day. You can still update idrac 6 via idrac, but they have since decomissioned ftp.dell.com as the repo for the lifecycle controller for some lame reason, see:
“Due to LC memory limitations only in 11G servers, Dell Engineering had to remove all 11G firmware and BIOS Dell Update Packages (DUPs) from the LC Catalog. The change was necessary due to the LC Catalog’s growing size, as it also added BIOS and firmware versions for 12G, 13G, and 14G servers being introduced.”
Luckily they made a work around that can be found here:
https://www.dell.com/support/article/us/en/04/sln310452/lifecycle-controller-lc-firmware-update-error-no-update-is-available-on-any-11g-server?lang=en
If that no longer works, here is a snippet of it:
Lifecycle Controller (LC) Firmware Update error “No update is available” on any 11G server
No update is available. Make sure that the Windows(R) catalog and Dell(TM) Update Packages for Windows(R) are used.
This is working as designed as of March 2018. Due to LC memory limitations only in 11G servers, Dell Engineering had to remove all 11G firmware and BIOS Dell Update Packages (DUPs) from the LC Catalog. The change was necessary due to the LC Catalog’s growing size, as it also added BIOS and firmware versions for 12G, 13G, and 14G servers being introduced.
Note that LC Firmware Update continues to work normally with all 12G – 14G servers. Catalog-based tools that can update 11G firmware such as OpenManage Essentials (OME) or System Center Updates Publisher (SCUP) will also still identify and push applicable 11G updates, since they can push and run DUPs “in-band” on the target host’s operating system, which has no memory limitations like LC.
To ensure the BIOS and firmware for your 11G servers are kept up-to-date, the suggested workaround is to use Dell Repository Manager (DRM) (I also got a copy of DRMInstaller_3.0.1.423.exe just in case that take it down, which you can get here: http://vivithemage.com/extra/Dell-11G/) to select the applicable 11G server models and then export a smaller custom Catalog that 11G LC can process. DRM can either:
Export both the custom Catalog.xml catalog and various DUP packages to an ISO image or directory intended to be stored on a file share that LC can access.
Export just the custom Catalog.xml file, which by default still points LC Update online to ftp.dell.com, making it unecessary to download all applicable DUPs to a local site.
Follow the steps below to export the custom Catalog in DRM:
In the main DRM homepage, click the “Add Repository” button.
Give the repository a name and choose the newest dated “Enterprise Server Catalog” in the “Base Catalog” menu.
Select the “Manual” tab and then click the “Custom” button under “Select Systems,” then click “Choose Systems.”
Only select “PowerEdge” in the “Line of Business” menu, and then click on each applicable 11G server model to move it into the “Selected Systems” list.
Click “Save” to return.
Click the “Custom” button under “Operating Systems,” then the “Choose” button.
Under the “Operating Systems” menu, choose only “Windows-32” and no other OSs.
IMPORTANT: A custom LC catalog can only list either Windows 32-bit or 64-bit DUPs, not both. All applicable 11G firmware and BIOS updates are still in the Windows 32-bit format, unlike newer server models. Do not choose Linux as 11G cannot process the Linux DUP format.
Click “Windows Server 2008 X64” to add to the “Selected Operating Systems” list, then click “Save.”
Under the “Components” section, simply choose “All component types” then click “Add.”
Once the new repository is added to the main DRM homepage, check its box and click the “Export” button.
There are several export formats available. Choosing “SUU ISO” exports the Catalog to an image file that LC Update can load via local or iDRAC virtual media. Otherwise, if you intend to mount the custom catalog in LC from a remote file share, choose the “Share” tab and then click “Browse” to specify a local directory path to save the Catalog.xml file and (optionally) all of the downloaded DUPs.
If the target hosts are intended to each connect online directly to ftp.dell.com, then check “Export only catalog.” Otherwise all Windows 32-bit DUPs applicable to the selected 11G server models will also be downloaded to the same local directory. This could make the directory large in size depending on how many DUPs are applicable.
Copy the directory containing the Catalog.xml file (and possible DUPs) to the intended file share server.
Once booted into LC Firmware Update, choose the appropriate file share protocol (FTP, CIFS, etc.) to connect to the remote file share containing Catalog.xml.
Quick Tips content is self-published by the Dell Support Professionals who resolve issues daily. In order to achieve a speedy publication, Quick Tips may represent only partial solutions or work-arounds that are still in development or pending further proof of successfully resolving an issue. As such Quick Tips have not been reviewed, validated or approved by Dell and should be used with appropriate caution. Dell shall not be liable for any loss, including but not limited to loss of data, loss of profit or loss of revenue, which customers may incur by following any procedure or advice set out in the Quick Tips.
Just because this took me a bit to find, and who knows if Dell will stop hosting it, but you can use this license to give yourself 30 days of enterprise features. You will then need to go purchase a license, because you will only get 30 days, and it will not let you re upload the licenses again for another 30, unless you do some effort, which I won’t get into here. I also had a hard time finding a place to purchase licenses, but as of this post, I was able to get them off ebay for about $47 each, which seems like a steal, considering what features you get.
http://vivithemage.com/extra/iDRAC7_Enterprise_30_day_Trial_license.zip
For keywords: Dell iDRAC7 Enterprise License PowerEdge R320 R420 R520 R620 R720xd R820 R920
Hi! So for whatever reason my R320 was throwing up HTTP 404 errors everywhere, like this:
I am using IE 11.248 to access, running version Version 1.45.45 of the idrac controller. What I had to do to resolve this was to open up IE, click the tool wheel on the top right, and go to compatibility view settings. Then add the IP address of my server here, and it allowed me to access it, and the HTTP 404 errors went away.
Hopefully this helps someone!