Monday, June 1, 2009


Today, ISEE closes for non-CS customers. I don't think I'll blog much about RSP much from now on, since I've completed my migration and it now works. 

I'm scheduled to meet the Product Manager for RSP in a few weeks at the HPTF, and I'll give him some of my comments as there are still a few things in it that I would like to see to make RSP better.

I posted most of my experiences in the last few months, but here is recap.  A 100% successful RSP installation boils down to this:
  • If possible, start from scratch with a fresh CMS. SIM is easy to backup/restore so you won't loose any data. 
  • Don't be tempted to install anything else on the CMS.
  • Use RSP 5.20, as 5.10 has a dumbed-down Software Manager that doesn't tell you what it's doing.
  • If you have EVAs, reinstall the SMS from scratch too, with SmartStart or the Proliant Support Pack, and ensure that it has only the required software to manage the EVA and link it to RSP
  • Proliants running Windows and ESX are easy to configure, just use the SMH to send traps the the CMS.
  • As for HP-UX... well, while the CIM-related tools are not terrific, SFM itself is worse. I've had lots of problems with it. You've been warned.
Good luck


Mark Sense said...

I guess HP VSE would be one of those CIM host add-ons one should resist the temptation to install on an Insight RS server?

Olivier S. Masse said...

Well, HP-UX comes bundled in with a daemon named cimserverd whose job is to monitors cimserver in case it crashes. That kinda thing never sound good.

Anonymous said...

SIM is easy to backup/restore

Could you expand on that ??

Kurt Johannessen