<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Solutions Log &#187; Hardware</title>
	<atom:link href="http://solutions.unixsherpa.com/category/hardware/feed/" rel="self" type="application/rss+xml" />
	<link>http://solutions.unixsherpa.com</link>
	<description>by Dan Reiland</description>
	<lastBuildDate>Fri, 16 Apr 2010 20:28:57 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Reset HP Integrated Lights Out Board to Factory Defaults</title>
		<link>http://solutions.unixsherpa.com/2010/01/05/reset-hp-integrated-lights-out-board-to-factory-defaults/</link>
		<comments>http://solutions.unixsherpa.com/2010/01/05/reset-hp-integrated-lights-out-board-to-factory-defaults/#comments</comments>
		<pubDate>Tue, 05 Jan 2010 21:45:19 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Hardware]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[howto]]></category>
		<category><![CDATA[hp]]></category>
		<category><![CDATA[ilo]]></category>
		<category><![CDATA[recovery]]></category>
		<category><![CDATA[riloe]]></category>

		<guid isPermaLink="false">http://solutions.unixsherpa.com/?p=230</guid>
		<description><![CDATA[Issue: Cannot login to HP Integrated Lights Out Board (bad credentials). Cause: Someone failed to record the configuration. Solution: If an operating system supported by HP Proliant Essentials is installed along with a recent Proliant Support Pack, you may reset the Integrated Lights Out board to its factory defaults. Use the HP Lights-Out Online Configuration [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Issue:</strong><br />
Cannot login to HP Integrated Lights Out Board (bad credentials).</p>
<p><strong>Cause:</strong><br />
Someone failed to record the configuration.</p>
<p><strong>Solution:</strong><br />
If an operating system supported by HP Proliant Essentials is installed along with a recent Proliant Support Pack, you may reset the Integrated Lights Out board to its factory defaults. Use the HP Lights-Out Online Configuration utility.</p>
<div class="codecolorer-container bash twitlight" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;"><div class="bash codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap">C:\Program Files\HP\hponcfg\hponcfg.exe <span style="color: #000000; font-weight: bold;">/</span>reset</div></div>
]]></content:encoded>
			<wfw:commentRss>http://solutions.unixsherpa.com/2010/01/05/reset-hp-integrated-lights-out-board-to-factory-defaults/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Intel Matrix Storage Console Reports SATA Drives as Generation 1 not 2</title>
		<link>http://solutions.unixsherpa.com/2009/07/15/intel-matrix-storage-console-reports-sata-drives-as-generation-1-not-2/</link>
		<comments>http://solutions.unixsherpa.com/2009/07/15/intel-matrix-storage-console-reports-sata-drives-as-generation-1-not-2/#comments</comments>
		<pubDate>Wed, 15 Jul 2009 15:10:09 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Hardware]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[ICH10R]]></category>
		<category><![CDATA[intel]]></category>
		<category><![CDATA[sata]]></category>
		<category><![CDATA[seagate]]></category>
		<category><![CDATA[ST3500320AS]]></category>

		<guid isPermaLink="false">http://solutions.unixsherpa.com/?p=151</guid>
		<description><![CDATA[Issue: When launching the Intel Matrix Storage Console and reviewing the disposition of a mirrored pair of Seagate SATA 3.0Gb/s drives, I noted the Serial ATA transfer mode reported as Generation 1. Cause: SATA host adapters typically support autonegotiation, however, with the Intel ICH10R this does not seem to be the case with RAID enabled. [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Issue:</strong><br />
When launching the Intel Matrix Storage Console and reviewing the disposition of a mirrored pair of Seagate SATA 3.0Gb/s drives, I noted the Serial ATA transfer mode reported as Generation 1.</p>
<p><strong>Cause:</strong><br />
SATA host adapters typically support autonegotiation, however, with the Intel ICH10R this does not seem to be the case with RAID enabled. <em>Note: It does work with standard AHCI mode on this chipset.<br />
</em><br />
<strong>Resolution:</strong><br />
Seagate drives ship with a jumper enabled for 1.5GB/s mode. One must remove this jumper to force the drive in 3.0GB/s mode.</p>
<p><em>Attachment:</em> <a href="http://solutions.unixsherpa.com/wp-content/uploads/2009/07/100452348g.pdf">Seagate ST3500320AS product manual</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://solutions.unixsherpa.com/2009/07/15/intel-matrix-storage-console-reports-sata-drives-as-generation-1-not-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Cannot SSH into PIX/ASA firewall</title>
		<link>http://solutions.unixsherpa.com/2009/07/09/cannot-ssh-into-pixasa-firewall/</link>
		<comments>http://solutions.unixsherpa.com/2009/07/09/cannot-ssh-into-pixasa-firewall/#comments</comments>
		<pubDate>Fri, 10 Jul 2009 03:33:19 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[sysadmin]]></category>

		<guid isPermaLink="false">http://solutions.unixsherpa.com/?p=143</guid>
		<description><![CDATA[Issue: When attempting to SSH into a PIX/ASA firewall you receive the following error on the client ssh_exchange_identification: Connection closed by remote host Investigating the log on the PIX/ASA will yield a corresponding error: Fail to establish SSH session because RSA host key retrieval failed. Cause: The issue is the result of a corrupt or [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Issue:</strong><br />
When attempting to SSH into a PIX/ASA firewall you receive the following error on the client</p>
<div class="codecolorer-container text twitlight" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;"><div class="text codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap">ssh_exchange_identification: Connection closed by remote host</div></div>
<p>Investigating the log on the PIX/ASA will yield a corresponding error:</p>
<div class="codecolorer-container text twitlight" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;"><div class="text codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap">Fail to establish SSH session because RSA host key retrieval failed.</div></div>
<p>
<strong>Cause:</strong><br />
The issue is the result of a corrupt or missing RSA key on the firewall.<br />
<br />
<strong>Resolution:</strong><br />
You need to generate a new RSA key on the firewall.<br />
<br />
Magic juju (from either SDM or a prompt):</p>
<div class="codecolorer-container text twitlight" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;"><div class="text codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap">conf t<br />
ca generate rsa key 1024<br />
wr mem<br />
copy run start</div></div>
]]></content:encoded>
			<wfw:commentRss>http://solutions.unixsherpa.com/2009/07/09/cannot-ssh-into-pixasa-firewall/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
