<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Do not update firmware/BIOS from within ESX console</title>
	<atom:link href="http://www.modelcar.hk/?feed=rss2&#038;p=2780" rel="self" type="application/rss+xml" />
	<link>http://www.modelcar.hk/?p=2780</link>
	<description>My Die-Cast Collection &#38; Interests</description>
	<lastBuildDate>Thu, 08 Jan 2026 15:35:11 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: admin</title>
		<link>http://www.modelcar.hk/?p=2780&#038;cpage=1#comment-797</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Thu, 30 Dec 2010 04:28:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.modelcar.hk/?p=2780#comment-797</guid>
		<description>Just received an update from Virtualization Buster, which is the proper way to update firmware using an USB method via F10 Unified Server Configuration (USC). 

Updating Dell R-Series aka 11-th Generation Servers via USB and Repository Manager

http://www.virtualizationbuster.com/?p=1301</description>
		<content:encoded><![CDATA[<p>Just received an update from Virtualization Buster, which is the proper way to update firmware using an USB method via F10 Unified Server Configuration (USC). </p>
<p>Updating Dell R-Series aka 11-th Generation Servers via USB and Repository Manager</p>
<p><a href="http://www.virtualizationbuster.com/?p=1301" rel="nofollow">http://www.virtualizationbuster.com/?p=1301</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.modelcar.hk/?p=2780&#038;cpage=1#comment-794</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Wed, 29 Dec 2010 08:11:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.modelcar.hk/?p=2780#comment-794</guid>
		<description>AH,

Thanks for pointing out it&#039;s an ESX memory limitation.

Honestly, I never really read the instruction when performing the BIOS action. I thought it would be the same as updating firmware from within Windows environment while the OS is running, obviously I was wrong.

Btw, are you Antti? :)</description>
		<content:encoded><![CDATA[<p>AH,</p>
<p>Thanks for pointing out it&#8217;s an ESX memory limitation.</p>
<p>Honestly, I never really read the instruction when performing the BIOS action. I thought it would be the same as updating firmware from within Windows environment while the OS is running, obviously I was wrong.</p>
<p>Btw, are you Antti? <img src='http://www.modelcar.hk/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AH</title>
		<link>http://www.modelcar.hk/?p=2780&#038;cpage=1#comment-790</link>
		<dc:creator>AH</dc:creator>
		<pubDate>Wed, 29 Dec 2010 06:04:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.modelcar.hk/?p=2780#comment-790</guid>
		<description>Hello Admin,

I don&#039;t whether you saw the instruction when you run the bin file of updating file.
As I know, it will show you below message.

============
If you run into the above memory limitation on VMWare ESX, the problem is because the console OS available memory is only 272M by default. Please increase the console OS memory to 800M temporarily and perform the FW update. During ESX server boot up please perform the below steps to increase the memory available.
1. While booting, press &#039;e&#039; on the VMware ESX line (Grub option display screen).
2. Press &#039;e&#039; again on the &#039;uppermem=&#039; line and edit uppermem=819200. Press Enter.
3. Press &#039;e&#039; on the kernel line (Just below the uppermem line). Edit the kernel line with mem=800M and press Enter.
4. Press &#039;b&#039; to boot with these options.
5. Perform the FW update.</description>
		<content:encoded><![CDATA[<p>Hello Admin,</p>
<p>I don&#8217;t whether you saw the instruction when you run the bin file of updating file.<br />
As I know, it will show you below message.</p>
<p>============<br />
If you run into the above memory limitation on VMWare ESX, the problem is because the console OS available memory is only 272M by default. Please increase the console OS memory to 800M temporarily and perform the FW update. During ESX server boot up please perform the below steps to increase the memory available.<br />
1. While booting, press &#8216;e&#8217; on the VMware ESX line (Grub option display screen).<br />
2. Press &#8216;e&#8217; again on the &#8216;uppermem=&#8217; line and edit uppermem=819200. Press Enter.<br />
3. Press &#8216;e&#8217; on the kernel line (Just below the uppermem line). Edit the kernel line with mem=800M and press Enter.<br />
4. Press &#8216;b&#8217; to boot with these options.<br />
5. Perform the FW update.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: greg</title>
		<link>http://www.modelcar.hk/?p=2780&#038;cpage=1#comment-682</link>
		<dc:creator>greg</dc:creator>
		<pubDate>Tue, 02 Nov 2010 21:00:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.modelcar.hk/?p=2780#comment-682</guid>
		<description>You should use the Dell Repo Manager tool (read more about Repo Manager @ http://www.delltechcenter.com/page/Repository+Manager)

Repo manager will allow you to create a &quot;Linux Deployment Media&quot; disk. This is a bootable ISO you can custom tailor to contain only the updates you need (usually under 100mb). You can mount this as virtual media and run the updates over the idrac... keep in mind the risks of running updates over virtual media... if your connection drops in the middle of an update..

You could also boot OMSA live and run the RHEL update package formats of the updates.

The FTP catalog is only updated about once a quarter... I don&#039;t see why it couldn&#039;t be scripted.</description>
		<content:encoded><![CDATA[<p>You should use the Dell Repo Manager tool (read more about Repo Manager @ <a href="http://www.delltechcenter.com/page/Repository+Manager)" rel="nofollow">http://www.delltechcenter.com/page/Repository+Manager)</a></p>
<p>Repo manager will allow you to create a &#8220;Linux Deployment Media&#8221; disk. This is a bootable ISO you can custom tailor to contain only the updates you need (usually under 100mb). You can mount this as virtual media and run the updates over the idrac&#8230; keep in mind the risks of running updates over virtual media&#8230; if your connection drops in the middle of an update..</p>
<p>You could also boot OMSA live and run the RHEL update package formats of the updates.</p>
<p>The FTP catalog is only updated about once a quarter&#8230; I don&#8217;t see why it couldn&#8217;t be scripted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.modelcar.hk/?p=2780&#038;cpage=1#comment-562</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Thu, 07 Oct 2010 16:06:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.modelcar.hk/?p=2780#comment-562</guid>
		<description>Thanks for leaving reply to me, could you kindly email me the iso of DOS-Image (I&#039;ve sent you a mail from my gmail account, please check), so I can boot R710 using this .iso and then execute the update BIOS.exe. (I found iDRAC6 does not support remote boot from USB or Floppy, then why Dell made a DOS update BIOS available? Huh?)

Btw, even I am able to boot into DOS, I still haven&#039;t figured out how do you run the update bios image from? Do you make another iso or combined the updated BIOS 2.1.15 into the bootable DOS image .iso?

Any detail would be greatly apprecaited.

Thanks in advance.</description>
		<content:encoded><![CDATA[<p>Thanks for leaving reply to me, could you kindly email me the iso of DOS-Image (I&#8217;ve sent you a mail from my gmail account, please check), so I can boot R710 using this .iso and then execute the update BIOS.exe. (I found iDRAC6 does not support remote boot from USB or Floppy, then why Dell made a DOS update BIOS available? Huh?)</p>
<p>Btw, even I am able to boot into DOS, I still haven&#8217;t figured out how do you run the update bios image from? Do you make another iso or combined the updated BIOS 2.1.15 into the bootable DOS image .iso?</p>
<p>Any detail would be greatly apprecaited.</p>
<p>Thanks in advance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yps</title>
		<link>http://www.modelcar.hk/?p=2780&#038;cpage=1#comment-553</link>
		<dc:creator>Yps</dc:creator>
		<pubDate>Wed, 06 Oct 2010 12:59:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.modelcar.hk/?p=2780#comment-553</guid>
		<description>I got the same problem, my IDRAC card doesn´t got access to Internet. 
I have got an flp image from my Dell contact with a DOS-image, and Winimage to change bios.exe on it. 

Works for me.</description>
		<content:encoded><![CDATA[<p>I got the same problem, my IDRAC card doesn´t got access to Internet.<br />
I have got an flp image from my Dell contact with a DOS-image, and Winimage to change bios.exe on it. </p>
<p>Works for me.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
