<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Hpe on Matt Allford</title><link>https://www.mattallford.com/tags/hpe/</link><description>Recent content in Hpe on Matt Allford</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 01 Apr 2020 20:40:43 +0000</lastBuildDate><atom:link href="https://www.mattallford.com/tags/hpe/index.xml" rel="self" type="application/rss+xml"/><item><title>Update Manager Initiated Reboot Doesn't Trigger Hardware Server Reset</title><link>https://www.mattallford.com/update-manager-initiated-reboot-doesnt-trigger-hardware-server-reset/</link><pubDate>Wed, 01 Apr 2020 20:40:43 +0000</pubDate><guid>https://www.mattallford.com/update-manager-initiated-reboot-doesnt-trigger-hardware-server-reset/</guid><description>&lt;p&gt;This might not be a new one to a lot of folk, but it certainly was to me!&lt;/p&gt;
&lt;p&gt;This week I was proactively updating some NIC driver and firmware for a customer to avoid a known issue where the FCoE driver could cause an ESXi Purple Screen of Death (PSOD). Both firmware and drivers needed to be upgraded to maintain interoperability. While I am very much looking forward to &lt;a href="https://www.youtube.com/watch?v=R4NGT12hvSM"&gt;vSphere Lifecycle Manager&lt;/a&gt; (finally!) to manage this in a single workflow, for this task I did what I normally would do:&lt;/p&gt;</description></item></channel></rss>