Insight Manager on Non-HP Boxes

[Jeremy Dixon]

Hi all, weird problem perhaps. The only server I have available to put Insight Manager on at my location is a Dell PowerEdge 2600. I didn't see anything saying it won't work so I installed it last night. It is up and running and seems to be working ok and can monitor servers fine. I can perform tasks from their against my Proliants without problem, except for the Version Control Repository. It shows up ok, but is empty. How do I go about getting it populated with Proliant Support Packs, Firmware, etc?

I wasn't sure if this was because it was not loaded on a Proliant server w/ the Support Pack installed. I'm guessing the Support Pack would blow up if I tried to install it on a Dell. :)

Thanks!

[Aravindh Rajaram · Accepted solution]

Browse to https://:2381/cgi-bin/vcrepository/cgi

Login and then click on the "Upload support pack". It then will prompt for a ActiveX control installation. On successful intallation of that, you can start populating your VCRM using the SmartStart CD(s).

There is also an option to download the softwares and firmwares from hp.com. Use the "Configure the repository and automatic update settings" link to do the same

[TechGuru]

Dixon,

VCRM will work fine in Dell system, and No need of installing any other HP agents in that VCRM System

as AMicSys said, if you have Smart Start CD, you can use "upload a Support Pack" option in VCRM and browse to folder "compaq\csp\" in Smart Start CD and upload the PSPs

if you need more PSPs,
1) you should have at least one VCA in your network pointed to VCRM (Browse VCA and click "change agent settings" and configure VCA to use VCRM)
2) VCRM system should have access to ftp://ftp.hp.com and ftp://ftp.compaq.com to get the Updates online

If the above 2 points are fine, then you can Click on "Update from hp.com now" option in VCRM's "Catalog" tab, or you can schedule the VCRM to Download automatically by using "configure the repository and automatic update settings" in VCRM's "Home" tab.

[Jeremy Dixon]

Thanks guys, that fixed it. I must have missed that somewhere in the Install Guide.

Much appreciated!