HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
BladeSystem Virtual Connect
cancel
Showing results for 
Search instead for 
Did you mean: 

VCEM server installed with incorrect mode.

 
cls.co.za
Occasional Visitor

VCEM server installed with incorrect mode.

Hi I have run into an issue on one of my sites. The VCEM was installed originally in "Stand-Alone" mode. The problem is that the client wants to use HP SIM and ALL of it's add-on licensed features. When VCEM is installed in "Stand-Alone" mode one cannot add any of these other plug-in features i.e. Performance Management Pack. The VC's are active and configured into a single domain. My problem worsens... The HP SIM / VCEM server was renamed. I now cannot get HP SIM nor VCEM open. I have taken the precaution of backing up the SQL database but.... I have primarily 2 major concerns 1) If I trash (format / re-install) the VCEM (HP SIM) server will the Domain remain active and fully functional? 2) In the same breath I need to ask when I have a correctly configured VCEM (HP SIM) server installed what is the correct process to get the current domain "imported" into this new VCEM (HP SIM) server? Thanks for taking the time to read this and any advice would be appreciated.
3 REPLIES
Adrian Clint
Honored Contributor

VCEM server installed with incorrect mode.

For (1) Yes it will remain active - you just cant manage it (no changes) till the VCEM is back up and running and the VCEM database restored.
cls.co.za
Occasional Visitor

VCEM server installed with incorrect mode.

Hi when I run the command remove external-manager UserName="what ever" Does the VC stay up and active? And during the import the VC into the new VCEM does the VC stay up? Thanks
dchmax
Frequent Advisor

VCEM server installed with incorrect mode.

I've run into the problem of when a server was renamed and SQL was running on it. SQL needs to be renamed. I think this link refereneces that. http://msdn.microsoft.com/en-us/library/ms143799%28SQL.90%29.aspx