Running Command View EVA / HPSIM - RSSWM on same server

[Ervinck Kevin]

I've been reading following comment in one of the setup PDF's from the HP Documentation site:

IMPORTANT: Windows servers running HP Command View EVA Software cannot be utilized as
a Central Management Server. Please do not install HP Command View EVA Software and HP
Systems Insight Manager on the same server. Please see the Important Notice: Implementing
Remote Support for EVAs available at:
http://docs.hp.com/en/netsys.html#Service%20Essentials%20Remote%20Support%20Pack

A.05.05 HP Service Essentials Remote Support Pack Important Information: Implementing Remote Support for EVAs

URL: http://docs.hp.com/en/5992-4039/5992-4039.pdf

We would like to offer our customers all-in-one Management server and would like to install Command View EVA / HPSIM / RSWMM on the same physical server.

Is this possible and what are the things we should keep in mind?

[Rob Buxton · Accepted solution]

Before I was aware of the documentation above I did try and install CV EVA and HPSIM on the same server.
It didn't work.
The documentation says don't do it.
I don't think you should offer your customers that.

[tr10385]

Running Command view on SMS (storage management system) communicating to WEBES configured on HP-SIM (CMS) with RSP client A.05.05.00.

Scheduled collections (storage collections) from the managed entities are processed and reaching the CMS without any issue.

WEBES SEA test event on WEBES/CMS working fine. But when a real hardware incident is triggered by a managed entity (EVA) device, this is reported in Command view, but this is not reaching the WEBES GUI for that managed entity.

What could be the issue. I would send the WEBES, CV and HP-SIM version shortly. Do yu need any further logs to analyse this.

[cmoberly]

I have run into issues myself with both of thewse products on the same server.

Specifically, HP SIM does not pull the relevant data from the EVA. This is with CV 8.01 and HP SIM 5.2. I have set up many installations of HP SIM on a separate server and have not encountered this issue.

Has anyone else seen this? SMI-S appears to be working properly and wbemdisco returns valid data with them name of the EVA.

I realize that the two apps should be separated, but I have one customer who insisted on keeping them combined.

[Jov]

Hi,

It might also be due to resource contention and given the two are separate products, the donâ t and can't share. e.g. Listening to incoming traps.

And for customers wanting them on the same box, just get them sign document stating the implementation will not be supported by HP or the provider. That should change their minds of saving a few dollars on hardware.

Jov

[Ervinck Kevin]

Would it be a solution to change the Pegasus WMI Mapper port configuration, change the http/https port to 5991 and 5992 respectively?

[cmoberly]

I think ultimately it is best to keep the products separate. I convinced my customer, so I am set. Thanks guys.

[Timothy Cusson]

It is now supported to have HP SIM 5.2 SP2, RSP 5.10 and Command View 8.01 on the same server. You must manually change the HTTP port 5988 and HTTPS 5989 port that the HP Storage Works cxws CIMOM listen on to unused ports such as 6988 and 6989.

You would need to log an HP support case to obtain a document with detailed instructions. This solution is working at one site so far.

[Ervinck Kevin]

Hi Tim!

Thanks for following up this thread. Any chance of posting the detailed document here?
I prepared this very same thing at a customer of ours and want to be sure I did it right.

It's good to have a second opinion that this should be working.

cheers,
kevin

[Ervinck Kevin]

Should there also be changed made to WEBES?

[Ervinck Kevin]

OK, found it already.
You need to alter these files:

cxws.properties:
change the ports to 6988 and 6989 (be sure to check these ports aren't in use).

wbemportlist.xml:
change the ports to 6988 and 6989

Stop the Hewlett Packard storage works CIMOM service

Restart the Pegasus WMI Mapper service.

Start the Hewlett Packard storage works CIMOM service

To verify SMI-S can communicate with the storage on the new port, open a command prompt and change directories to where SIM is installed.

Type wbemdisco
Specify the new port number 6989.