GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: HP Software update: how to proceed and is ther...
Server Management - Systems Insight Manager
1850627
Members
2620
Online
104054
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
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
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
05-04-2005 12:18 AM
05-04-2005 12:18 AM
HP Software update: how to proceed and is there a big impact
Dear All,
I've a question question about the way to update HP software on ours > 200 servers.
Today we have a mix of Compaq , HP software with agents having different names, different version, different terminology and so on...
Furthermore, I'm completely lost with all these agents, versions, also what is part of PSP or not...
Is it possible to upgrade to latest version of HP management software with lowest possible impact, given that we have W2k and W2k3 systems with hardware from Proliant ML370 to Proliant DL580 (DL 360, 380,...) ?
Moreover, what is the best methodology ? We have HP SIM 4.2 SP2 we our systems configured to update from VC Repository manager.
Thanks and regards
Angelo
I've a question question about the way to update HP software on ours > 200 servers.
Today we have a mix of Compaq , HP software with agents having different names, different version, different terminology and so on...
Furthermore, I'm completely lost with all these agents, versions, also what is part of PSP or not...
Is it possible to upgrade to latest version of HP management software with lowest possible impact, given that we have W2k and W2k3 systems with hardware from Proliant ML370 to Proliant DL580 (DL 360, 380,...) ?
Moreover, what is the best methodology ? We have HP SIM 4.2 SP2 we our systems configured to update from VC Repository manager.
Thanks and regards
Angelo
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-04-2005 08:20 AM
05-04-2005 08:20 AM
Re: HP Software update: how to proceed and is there a big impact
You got potential risks for a number of areas, including Firmware Revision levels.
Installing the complete Support Pack is the safest option as it is a tested bundle.
Saying that, Support Pack 7.20A caused us a few problems.
I've not extensively tested 7.30 but so far it has none of the issues the previous version has.
These upgrades will need a reboot to complete, so it depeds on what you mean by impact.
Note that you configure the Agents in the VCRM before deploying, this means you do not need to configure the agents on the clients.
The best methodology?
Here we target Development and Test boxes first. I also schedule remote updates out of hours to our Remote DR Site.
Then we need to liaise with Business Units.
Start with small chunks and then work up.
You'll want to keep your action plan as you'll reuse it.
Installing the complete Support Pack is the safest option as it is a tested bundle.
Saying that, Support Pack 7.20A caused us a few problems.
I've not extensively tested 7.30 but so far it has none of the issues the previous version has.
These upgrades will need a reboot to complete, so it depeds on what you mean by impact.
Note that you configure the Agents in the VCRM before deploying, this means you do not need to configure the agents on the clients.
The best methodology?
Here we target Development and Test boxes first. I also schedule remote updates out of hours to our Remote DR Site.
Then we need to liaise with Business Units.
Start with small chunks and then work up.
You'll want to keep your action plan as you'll reuse it.
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.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP