-
-
Advertise on Bladewatch
You can easily reach influential IT professionals including decision makers. Talk to us about your products and services and we will do our best to make sure our viewers and readers find you.
-
subscribe to RSS
Get email updates every time we post!
Finding the serial number for a Compaq/HP server
I got an email from Mike about obtaining the serial number for his Compaq/HP DL360 running Windows 2000. You can do this easily but you will need the HP driver pack which you can get from here: http://h18023.www1.hp.com/support/files/server/us/locate/20_1123.html.
You can use either:
- HP Survey utility – this was a small downloadable application which creates a text file with complete system information, comprising serial number, components, firmware and operating system information. This was phased out in the newer drivers and therefore is not recommended for new servers.
- HP Insight diagnostic online utility – this in effect replaced the survey, it provides the same information in an XML file, but also allowed you to carry out online diagnostics.
- HP Insight Management agents – this is the web agent component of the driver pack which allows you to view the system health and all the firmware/configuration information, it’s accessed typically by typing http://servername:2301 – this re-directs you to the secure version of the url. In the later driver packs the login name is tied into active directory – otherwise the login information is controlled by an acl file on your system drive.
You should typically be using the latest driver pack for the specified operating system as that will contain the bug fixes/enhancements that you require – but do ensure that your firmware is up to date, particularly when you’re upgrading legacy systems (the Proliant R ranges), the firmware can affect the operating system and the drivers. I remember upgrading the driver pack on a Compaq 2500R running NT 4 to something like 5.5 or 6.1, and the server blue screening, and found after a few minutes testing that it was because the system firmware was ancient and needed to be upgraded.
Related posts:
- Check ILO version remotely Another tweet, can you check the ILO version remotely on...
- Writing about my obsession with firmware/drivers Writing about my obsession with firmware and drivers. The reason...
- How old is my Compaq/HP server – what should be virtualized? http://www.bladewatch.com/2009/09/04/how-old-is-my-server/ I’ve published the file which is in the previous...
- HP Proliant Support Pack 8.30 HP HP Proliant Support Pack for Microsoft Windows Server 2003...
Related posts brought to you by Yet Another Related Posts Plugin.
Leave a Reply
Recent Posts
Twitter Updates
- Talk to me about the benefits and importantly how it will work with my existing processes and infrastructure.
- The next confrontation in the virtual and the physical world is what features are included at that price point and not what isn't.
- As we add more layers to the IT infrastructure do we need more ITIL layers? How do we cope with an always on world development is like prod
- Is swapping a disk, adding a volume to an ESX host with development virtual machines a change?
- When we do integrated array controllers can they not be a daughter card, it's annoying having to swap a system board for controller failure
Categories
Recent Comments
- Cialis on Who will be the server world's Apple?
- Roger on How to reboot the HP ILO/kick off a hung session
- Martin on Tolly Group benchmark BladeSystem C7000 and Cisco UCS 5100
- Jose R on Tolly Group benchmark BladeSystem C7000 and Cisco UCS 5100
- Kevin Houston on HP Blades Day Analysis
- Pugalenthi on What's the equivalent of ILO in an IBM server?
- ST2 on Bladewatch drinks 14th October
- Adipex_Phentermine_Pill on How to reboot the HP ILO/kick off a hung session
- Adipex_Phentermine_Pill on IBM and Syracuse University data center
- console xbox 360 on Sun/Oracle continue the innovation
