Skip to main content

hardware - HP plan to restrict access to ProLiant server firmware - consequences?




I've been a longtime advocate for HP ProLiant servers in my system environments. The platform has been the basis of my infrastructure designs across several industries for the past 12 years.



The main selling points of ProLiant hardware have been long-lasting product lines with predictable component options, easy-to-navigate product specifications (Quickspecs), robust support channels and an aggressive firmware release/update schedule for the duration of a product's lifecycle.



This benefits the use of HP gear in primary and secondary markets. Used and late-model equipment can be given a new life with additional parts or through swapping/upgrading as component costs decline.



One of the unique attributes of HP firmware is the tendency to introduce new functionality along with bugfixes in firmware releases. I've seen Smart Array RAID controllers gain new capabilities, server platforms acquire support for newer operating systems, serious performance issues resolved; all through firmware releases. Reading through a typical changelog history reveals how much testing and effort goes into creating a stable hardware platform. I appreciate that and have purchased accordingly.



Other manufacturers seem to ship product as-is and only focus on correcting bugs in subsequent firmware releases. I rarely run firmware updates on Supermicro and Dell gear. But I deem it irresponsible to deploy HP servers without an initial firmware maintenance pass.







Given this, the early reports of an upcoming policy change by HP regarding server firmware access were alarming...



The official breakdown:



enter image description here




Access to select server firmware updates and SPP for HP ProLiant

Servers will require entitlement and will only be available to HP
customers with an active contractual support agreement, HP Care Pack
service, or warranty linked to their HP Support Center User ID. As
always, customers must have a contract or warranty for the specific
product being updated.




Essentially, you must have active warranty and support on your servers in order to access firmware downloads (and presumably, the HP Service Pack for ProLiant DVD).



This will impact independent IT technicians, internal IT and customers who are running on older equipment the most, followed by people seeking deals on used HP equipment. I've provided many Server Fault answers that boil down to "updating this component's firmware will solve your problem". The recipients of that advice likely would not have active support and would be ineligible for firmware downloads under this policy.





  • Is this part of a growing trend of vendor lock-in? HP ProLiant Gen8 disk compatibility was a precursor.

  • Is HP overstepping bounds by restricting access to updates that some people have depended upon?

  • Will the result be something like the underground market for Cisco IOS downloads?

  • How does this sit with you, your organization or purchase decision makers? Will it impact future hardware decisions?

  • Is this any incentive to keep more systems under official warranty or extend Care Packs on older equipment?

  • What are other possible ill-effects of this policy change that I may not have accounted for?




Update:
A response on the HP Support Services Blog - Customers for Life



Update:



This is in effect now. I'm seeing the prompt when trying to download BIOS updates for my systems. A login using the HP Passport is not necessary to proceed with the download.



enter image description here


Answer



The simplest answer is, in this case, the correct answer: You will no longer be able to get firmware updates for HP equipment which is not (a) under its original factory warranty, or (b) covered by an active support contract with HP.




This has a number of implications, chief among them:




  • As a sysadmin you will have to ensure that you have an HP support contract to get continued firmware upgrades for machines that are beyond the factory warranty period.


  • As a business this alters the cost of continuing to operate equipment beyond its initial factory warranty period (as you now have to purchase support contracts, which adds to the cost of the equipment).







Ultimately what this means is the cost/benefit analysis of running HP hardware has just become more complex. How that analysis plays out for you, your company, or your clients will depends on your own internal requirements, constraints, and budgeting (and likely on your company's relationship with HP -- A company buying $500,000 of HP gear every quarter will likely get more favorable support contract terms than one that buys $50,000 every 5 years).



Comments

Popular posts from this blog

linux - iDRAC6 Virtual Media native library cannot be loaded

When attempting to mount Virtual Media on a iDRAC6 IP KVM session I get the following error: I'm using Ubuntu 9.04 and: $ javaws -version Java(TM) Web Start 1.6.0_16 $ uname -a Linux aud22419-linux 2.6.28-15-generic #51-Ubuntu SMP Mon Aug 31 13:39:06 UTC 2009 x86_64 GNU/Linux $ firefox -version Mozilla Firefox 3.0.14, Copyright (c) 1998 - 2009 mozilla.org On Windows + IE it (unsurprisingly) works. I've just gotten off the phone with the Dell tech support and I was told it is known to work on Linux + Firefox, albeit Ubuntu is not supported (by Dell, that is). Has anyone out there managed to mount virtual media in the same scenario?

hp proliant - Smart Array P822 with HBA Mode?

We get an HP DL360 G8 with an Smart Array P822 controller. On that controller will come a HP StorageWorks D2700 . Does anybody know, that it is possible to run the Smart Array P822 in HBA mode? I found only information about the P410i, who can run HBA. If this is not supported, what you think about the LSI 9207-8e controller? Will this fit good in that setup? The Hardware we get is used but all original from HP. The StorageWorks has 25 x 900 GB SAS 10K disks. Because the disks are not new I would like to use only 22 for raid6, and the rest for spare (I need to see if the disk count is optimal or not for zfs). It would be nice if I'm not stick to SAS in future. As OS I would like to install debian stretch with zfs 0.71 as file system and software raid. I have see that hp has an page for debian to. I would like to use hba mode because it is recommend, that zfs know at most as possible about the disk, and I'm independent from the raid controller. For us zfs have many benefits, ...

linux - Awstats - outputting stats for merged Access_logs only producing stats for one server's log

I've been attempting this for two weeks and I've accessed countless number of sites on this issue and it seems there is something I'm not getting here and I'm at a lost. I manged to figure out how to merge logs from two servers together. (Taking care to only merge the matching domains together) The logs from the first server span from 15 Dec 2012 to 8 April 2014 The logs from the second server span from 2 Mar 2014 to 9 April 2014 I was able to successfully merge them using the logresolvemerge.pl script simply enermerating each log and > out_putting_it_to_file Looking at the two logs from each server the format seems exactly the same. The problem I'm having is producing the stats page for the logs. The command I've boiled it down to is /usr/share/awstats/tools/awstats_buildstaticpages.pl -configdir=/home/User/Documents/conf/ -config=example.com awstatsprog=/usr/share/awstats/wwwroot/cgi-bin/awstats.pl dir=/home/User/Documents/parced -month=all -year=all...