- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- FW upgrade on OpenVMS Blade cluster.
Operating System - OpenVMS
1753971
Members
8496
Online
108811
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-20-2009 11:12 AM
тАО03-20-2009 11:12 AM
The latest Itanium Blade F/W upgrade kit for systems running OpenVMS is released as a *.ZIPEXE, actually,
HP-I64VMS-OSIFM_BL860C-V0411.ZIPEXE
which can be installed as a normal VMS patch kit using "Product Install". This is very nice, (although the requirements are inconvenient, i.e. non-shadowed system disk, etc.).
I just ran the process on a stand-alone system without any issues, and it took ~30 mins from start to finish, including the additional boots required to unshadow, then reshadow the system disk.
So now the real question. I have to plan the firmware upgrade for my Production Blade cluster. I assume that I have to apply this F/W to all three of my production nodes individually, so I suspect I will have to boot each node standalone to do the firmware upgrade.
Has anyone outthere done this yet, and can offer any suggestions or advice?
thanks.
Dave
HP-I64VMS-OSIFM_BL860C-V0411.ZIPEXE
which can be installed as a normal VMS patch kit using "Product Install". This is very nice, (although the requirements are inconvenient, i.e. non-shadowed system disk, etc.).
I just ran the process on a stand-alone system without any issues, and it took ~30 mins from start to finish, including the additional boots required to unshadow, then reshadow the system disk.
So now the real question. I have to plan the firmware upgrade for my Production Blade cluster. I assume that I have to apply this F/W to all three of my production nodes individually, so I suspect I will have to boot each node standalone to do the firmware upgrade.
Has anyone outthere done this yet, and can offer any suggestions or advice?
thanks.
Dave
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-20-2009 02:07 PM
тАО03-20-2009 02:07 PM
Re: FW upgrade on OpenVMS Blade cluster.
OS Installable Firmware is a fine idea and I'm glad the kits have started to appear.
You have to install it for each system because it is the system that is being updated rather than the disk the system boots from.
You could do by hand what the kit does but that rather defeats the point of the kit doesn't it.
You have to install it for each system because it is the system that is being updated rather than the disk the system boots from.
You could do by hand what the kit does but that rather defeats the point of the kit doesn't it.
____________________
Purely Personal Opinion
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-22-2009 04:07 PM
тАО03-22-2009 04:07 PM
Solution
I had the same problem and have created an extra SAN based bootable system disk which I set via BOOT_OPTIONS and boot from that, one blade at a time. This system disk starts nothing, has VMSCLUSTER set to 0 and even has DECnet startup disabled. Very basic VMS system.
I then reinstall via PRODUCT INSTALL the relevant kit (BL860c or BL870c in my case) and let it roll through the shutdown and f/w upgrade process.
When the blade is re-powered it then re boots off the cluster disk again and it's done.
Then I move to the next node in the cluster.
The important thing seems to be you musy have a fully booted system to work from on a non-shadowed disk. Minimum boot will not do.
Hope this helps.
Malcolm
I then reinstall via PRODUCT INSTALL the relevant kit (BL860c or BL870c in my case) and let it roll through the shutdown and f/w upgrade process.
When the blade is re-powered it then re boots off the cluster disk again and it's done.
Then I move to the next node in the cluster.
The important thing seems to be you musy have a fully booted system to work from on a non-shadowed disk. Minimum boot will not do.
Hope this helps.
Malcolm
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP