Oracle's future for Sun's hardware and OS business is now clear

May 6, 2010

The alternate title for this entry is 'how to persuade us to never buy your hardware again'.

The old Sun had both a general server business and a general OS business, and people used both; they bought Sun servers to run lots of operating systems and they ran Solaris on lots of non-Sun hardware. It is now clear that Oracle is nothing like this. Solaris now exists only to run on Oracle hardware, and Oracle hardware exists only to run Solaris and a few other Oracle-supported operating systems.

Why do I say this? Well, it's due to the latest bit of Oracle news, to wit that Oracle has restricted access to firmware updates (via Slashdot). In order to get firmware updates, your hardware either has to be under its one-year warranty or you have to have an Oracle support contract for it. Older than a year and without a support contract? You lose. This policy change was introduced abruptly and with no advance warning; it appears that even (ex-)Sun and Oracle support people may not understand it yet.

(Note that you must have a support contract that includes hardware support. A Solaris software support contract is not good enough, as I have verified.)

This is much more important than it looks from the outside. For most systems, server firmware updates are relatively unimportant; few people ever apply BIOS updates. But Sun servers have integrated lights out management processors, which are network accessible under some circumstances, and they have had security vulnerabilities. These security vulnerabilities are fixed with, you guessed it, firmware updates.

As far as I am concerned, this makes access to firmware updates somewhere between very important and vital for running production Sun servers, especially since their excellent ILOMs were much of the reason to prefer them in the first place.

But wait, it gets better: you cannot buy hardware support without buying Oracle software support (at least for new support contracts), and software support is twice as expensive as the hardware support. Software support costs 8% of the net hardware purchase cost per year, and adding hardware support costs an additional 4% per year (per here, found via Hacker News). Oracle very explicitly won't sell hardware support by itself, and have said so clearly.

This makes it very clear that Oracle intends their hardware almost exclusively for running Oracle-supported operating systems, since if you run a non-supported OS on Oracle hardware, you are completely wasting the 8% a year Oracle software support fee.

(If you do not get hardware support, you are gambling on there not ever being an ILOM security vulnerability that affects you. Since the ILOM is accessible from the server itself under some circumstances, this is not a bet that I would want to take.)

There are two immediate corollaries to this firmware access policy change. First, if you still have systems under hardware warranty (or hardware support contract), get the latest firmware updates now while you still can, even if you don't plan to apply them. Second, smart people buying second-hand Sun servers are likely to either demand that they be at the latest firmware version or require a potentially significant price discount, or both.

(Hence one reason to get the latest firmware updates even if you never plan on applying them yourself.)


Comments on this page:

From 174.112.198.41 at 2010-05-06 22:29:44:

Yeah, I learned that today too: http://wiki.xdroop.com/space/Seriously,+Oracle%3F

I can't think of a better way to drive the low- and mid-end market away from your hardware.

- David Mackintosh

From 171.192.0.10 at 2010-05-07 08:11:55:

I've been reading previous entry in your blog, like the one saying Solaris can only be install on Sun hardware, but the day after, Sun announced a partnership with HP. Now you are talking about crazy licencing policy...

It's really nice of you to try to find the lastest news but before spreading faulse news it would be great if you could double check the information or least don't be so sure about yourself.

Cheers,

rno

By rdump at 2010-05-07 10:18:10:

I'm most used to seeing "raise doubts" comments like that misspelled second one there on sites like resellerratings.com. It's passing strange to see what looks like loyalty team activity here.

By cks at 2010-05-07 11:48:43:

In reply to 171.192.0.10/rno:

This 'crazy licensing policy' is verifiable current fact; as I mentioned, I tried to get firmware updates myself and failed before posting this, and we have a formal Sun support contract (not just a SunSolve login). Plus, you know, the comment above yours that reports the same thing.

As far as I know and has ever been reported here, everything I've written here and in the previous entry is true and correct and has been confirmed from multiple sources; in addition, I have gone to some effort to check and verify things myself and have delayed writing entries (both this one and previous ones) until I could do so. I am obviously quite annoyed by your suggestion that I don't do this and that I am carelessly spreading false news.

From 216.110.78.56 at 2010-05-07 13:35:05:

We recently has a Solaris 10 OS patch cluster that caused the machine to kernel panic on boot. The fix was a BIOS patch.

I don't see how you avoid the 12% per annum at this point.

I guess we should just make our peace with it.

- pel
From 173.26.164.245 at 2010-05-08 22:32:36:

It appears that there's still a relationship for Oracle Solaris on HP hardware: http://h18000.www1.hp.com/products/quickspecs/13239_div/13239_div.pdf

Looks like Oracle hardware is now only for those who can pay for a premium hardware contract - too bad.

From 203.206.45.176 at 2010-05-09 06:06:57:

173.26.164.245 at 2010-05-08 22:32:36:

That's dated March 19, 2010, which is before the latest news about HP dropping Solaris support for Proliant servers.

James

Written on 06 May 2010.
« The right way and the wrong way to disable init.d services
SSL certificate vendors are selling a commodity »

Page tools: View Source, View Normal.
Search:
Login: Password:

Last modified: Thu May 6 21:20:07 2010
This dinky wiki is brought to you by the Insane Hackers Guild, Python sub-branch.