HP SIM storage info from multiple EVA's through one instance CV

[WishfulThinking]

Hi All,

I have SIM 5.3 correctly connected using WEBEM / SMI-S and talking to a CV 8.02 instance on the same server. (CV & SIM WEBEM ports changed and talking)

CV manages 2x EVA 4400s.

In SIM I can only ever get capacity information on just one EVA.

I've seen this before on other sites - but wanted to know, is this a limitation of SIM / CV or in theory should both EVA's through the CV to SIM SMI-S integration be able to report on more than one at a time?

Regards,

Tim

[Rob Buxton]

HPSIM usually sees the EVAs via CV. So if CV can see both EVAs you should see them both in HPSIM.
Just setting up 5.3 now, but on our old 5.2.2 HPSIM, both the local and DR based EVAs were visible in HPSIM.

[WishfulThinking]

Thanks Rob, just as I thought.

CV can see both and has on other sites but has never brought it through to SIM - have you had luck with your 5.3 install?

[Rob Buxton]

Yep, 5.3 installed, and it's reporting the EVAs successfully in HPSIM. Our CV is still at 8.0.1 but that shouldn't matter.

Under the System credentials for the server hosting CV I've added a new credential that specifies WBEM on 5989 and uses a local server account that is in the HP Storage Group.

Our CV is on a different server so I know that you need to do a few tweaks if you're running CV and SIM on the same server.

But now we've run a data collection both EVAs show and all of the additional info (capacity etc.) is listed.

[WishfulThinking]

Thanks again for the confirmation on 5.3 Rob, much aprpeciated.

Seems it's possibly localised to a CMS with both SIM & CV running with the required port changes.

I wonder if it's directly related to the single instance of the CIM Object Manager on the CMS and whether as its a single instance it limits things?

Anyone out there experiecning the same issue or the opposite working) on a single CMS (SIM + CV) monitoring multiple EVAs?

[WishfulThinking]

bump

[WishfulThinking]

UPDATE:
Seems this might be related to EVA 4400's.

Have now had 2 personal instances and a further 3rd instance from a colleague where SIM will display capacity information for only one of the 2 EVAs managed by CV on the same CMS as SIM.

The 2nd EVA won't complete a data collection - quoting

"An unexpected error was encountered in the middle of communication with the CIMOM."


Both EVA's have the following version details:

Type: HSV300
Version: 09006000
Software: CR1276lep-09006000


Any further thoughts out there?

[Micke_Ch_1]

Hi!

I have seen the same problem, but I have not the same CMS as CV.
In fact I have 2 cust with the same problem.
On the first place there is two EVA 8000 which only the first will show everything.

On the other place there are two EVA 5000 and only one have all info.

If I try run the command WBEMDISCO and WBEMCAP from the CMS against the CV all info is displayed correctly in the command window.

It seems that HP SIM is not able to interpret the information.

Thanks
/Mikael Christenson

[WishfulThinking]

Hmm - Have had a successful environment with an 8000 and a 5000 where both feed through - same versions.

So it's not just limited to EVA 4400's.

Still could be firmware or most likely - SIM

[WishfulThinking]

Hit submit too soon.

I'm leaning towards it being that SIM/SMI-S/WEBEM doesn't like talking to two EVAs of the same model (2x 4400 / 2x 8000)

[Micke_Ch_1]

Hi!

Dont think it is firmware on the EVA, because there is both 2x8000 and 2x5000 and 2x4400.

It must be some limitation in SIM.

I am running SIM 5.3 on one place (2x5000) and SIM 5.2.0 on the other (2x8000)

It must be larger installation with multiple EVA somewhere. I wonder if all info is coming up there?

/Micke

[WishfulThinking]

Upgraded CV 9.0 on one of the systems in question and it now seems to successfully catpure data from both EVA's.

Would be good if someone else could confirm in their environment.

[Micke_Ch_1]

Hi!!

I have just installed CVEVA 9.0 in customers environment. It work as it should be.
Both EVA show all info in SIM.

It seems that the problem was inside SMI-S or maybe SIM have trouble to interpret the information provided by the earlier SMI-S.

Thanks
/Micke Ch

[WishfulThinking]

My guess is SMI-S as well - thanks for the confirmation Mike :)

[WishfulThinking]

See above