Groups | Search | Server Info | Login | Register
Groups > comp.sys.hp.hpux > #525
| Subject | HP-UX 11i v3 in 2026 After End of Standard Support: What It Means in Practice |
|---|---|
| From | mummycullen@gmail-dot-com.no-spam.invalid (MummyChunk) |
| Date | 2026-02-27 12:59 -0500 |
| Newsgroups | comp.sys.hp.hpux |
| Message-ID | <UoudnVhJtss8ZTz0nZ2dnZfqnPWdnZ2d@giganews.com> (permalink) |
For anyone still running HP UX 11i v3 on Integrity, we're now in the new reality where standard support is over as of the end of 2025 and the last big "operating environment update" drop was the 2025 release. In plain terms, that means you should not expect the usual sustaining engineering style fixes going forward, and you should assume security and defect coverage is not going to look like it used to, even if you still have some form of contract or assistance option on paper. What I'm seeing people do right now falls into a few familiar camps. Some are freezing the environment and treating it like an appliance, locking the stack, tightening network exposure, and focusing on reliability rather than change. Others are finally using this as the forcing function to migrate, because the real risk is not that the box stops booting tomorrow, it's that one day you need a fix you cannot get, or a compliance question you cannot answer cleanly, or a hardware failure turns into a scramble. And then there's the group that's planning to keep the workload but move the hardware risk off the table, either by consolidating what's left onto the most stable remaining machines or by going down the emulation route so the OS can live on without depending on aging Integrity parts. None of this means your systems instantly become unusable. HP UX is still HP UX, it will keep doing what it's been doing if you leave it alone. The change is mostly in what happens when you cannot leave it alone anymore. If you have any dependency on new certificates, updated crypto requirements, changing network policies, or audits that expect current vendor patching, that's where the pain tends to show up first. The other obvious pressure point is hardware. The older these platforms get, the more your survival plan starts looking like spare parts management. If you're still in the "we have to run this for years" camp, I'd be interested in what your strategy is. Are you locking it down and riding it out, paying for third party support, actively migrating apps off, or trying to preserve the environment through virtualization or emulation. The details matter a lot, and what works for one shop can be totally wrong for another depending on whether the box is doing something simple and stable or something business critical with lots of moving parts.
Back to comp.sys.hp.hpux | Previous | Find similar
HP-UX 11i v3 in 2026 After End of Standard Support: What It Means in Practice mummycullen@gmail-dot-com.no-spam.invalid (MummyChunk) - 2026-02-27 12:59 -0500
csiph-web