New SQL CLUSTER was added recently in our environment. But that is not perfectly discovered. It is showing under Major Clusters Tab. When i try to re-discover them, for a while the nodes are showing under the SQL CLUSTER and then disappears. When i see the Discovery results, it says that " HP SIM cannot communicate with these systems using the WBEMprotocol.". I checked for the ports 5988/5989they doest show up.
Valueble information is appreciated.
Please read the following PDF, and use it to point your new installation to the old database:
https://community.hpe.com/hpeb/attachments/hpeb/itrc-455/59388/1/SIM-db-migration.pdf
Page 22 point to all files to be edited. The file hpsim-ds.xml is one that takes care of jobs an mutations in the database.
So you use WBEM to discover the servers. Can you run a identification for your server(s) and post the result here ?
Do you also have SNMP configured? You should only use SNMP or WBEM not both. The WBEM user should have enough rights on the servers ytou want to discover. You can use an admin account or use SIM to configure a non admin account for discovery.
Andrew, THANK YOU for taking the time to respond.
Just to clarify, you would not suggest the method as described, export and then full import. Correct?
Instead you would recommend basically what we did, adding the editing of some additional configuration files.
Correct?
Thanks again
when ILO crush, does it happen shut down server immediately? or it give some sort of warining?
and what was your solution solve this problem? (after upgrade the firmware abd so on?)
Hello again,
The fast way is to do a new install and point to the old database. But if you don't have a lot of different server(types) you can also do an mxnode -ln > c:\nodes.txt and use this list to fill the new database. Both work just fine, i prefer the new setup way as it will create a new and clean database. The previous upgrades gave me some issues in the reporting fields. But if you don't use the reporting features you are free to choose.
Do you see ASR events in the ILO Event Log log ?
Hello,
The VCA/VCRM set is a legacy way of updating your server. The HP preferred way to update your server is by using HP SUM. Did you try to update your server with this tool ? You can even do a remote or scripted (automated) update if you like.
Or do a bunch of servers is that is possible.
Andrew,
Thanks again for all your comments and insight.
We did the process as the original documented, basically a fresh install, mxexport of the old guy and mximport into the new guy followed by the appropriate collections, queries, tasks running.
This seems to have worked pretty well. Version control doesn't seem to be able to phone home, but it cannot phone home on the old server either and this isn't seen as a show stopper, at least right now.
Again, thanks for your suggestions and support.
Hi Andrew,
Thanks for your response. We have tried HP SUM but prefer the HP VCR reporting which shows a simple version comparison for each component on a server and a pie chart of the overall update status of a whole group of servers. I realise that VCR isn't getting much support now, but can HP SUM do the same?
Mark
Please!
Any help getting VCRM to work is greatly appreciated!
The server would boot up and would run for maybe 10 or 15 minutes before shutting off. If you put your hand on the cover of the server, it was so hot it was painful. We had to dump the server because we could not fix the iLO and it was out of warranty. I tried booting up to a bootable HPE firmware ISO to try to force the iLO firmware to be updated, but that did not work - the boot ISO acted really funny - it would hang at various points during the load/boot up...I think because it was overheating. I also tried using a large barn fan to keep the server cool long enough to fix - but that ended up not helping either.
I also tried flipping the iLO switch on the system board and pulling out CMOS battery. Nothing worked. And all this happened when we did a simple iLO firmware update. The update completed sucessfully with no errors. A short time later..bam! The server shut down on us.
I dont recall if there were any ASR errors....its been over a year since this happened. The main thing we saw (besides the overheating) was this during bootup:
iLO 4 not responding. System Health Monitoring has been disabled
1500 iLO 4 configuration is temporarily unavailable (5).
NK
Hello,
I am installing HP-SIM version 7.5. i am having sql server 2012 installed with sysadmin right on the same server where i want to install HP-SIM. i can confirm that i can use the database credentials on SQL management studio.
I am using service account(Non expiry account) to install HP-SIM and when HP-SIM wizards detects database and require a credential and then putting database account credentials are not working.it is giving me error that database credentials are not valid.(My service account and database account both are different).
Can someone please advise where i am doing wrong? or is there a bug in SIM?
Hi all,
I have 2 HP server (ProLiant DL380 Gen9), installed HPE Insight Management WBEM Providers, and showed warning log as below:
Windows Management Instrumentation has stopped WMIPRVSE.EXE because a quota reached a warning value. Quota: HandleCount Value: 4097 Maximum value: 4096 WMIPRVSE PID: 26908 Providers hosted in this process: C:\Program Files\HPWBEM\Server\dll\HPWmiDiskTEvt.dll, C:\Program Files\HPWBEM\Storage\dll\HPWMIFCA.dll, C:\Program Files\HPWBEM\Server\dll\HPWmiCpuTEvt.dll, C:\Program Files\HPWBEM\Server\dll\HPWmiSensorEvt.dll, C:\Program Files\HPWBEM\Storage\dll\HPWMISA.dll, C:\Program Files\HPWBEM\Server\dll\HPWmiTestEvt.dll
Anybody know the meaning of above message? What is the root casue of this? How to slove and how to avoid this message?
Thanks,
Stanley
+1 Same issue here
Central management server: Hostname: HP-Management Operating system: Windows Server 2012 R2 Version: Systems Insight Manager 7.6.0 - Windows Build version: C.07.06.00.00r76rc05 Build date: 2016-11-29 07:00 Patches:
Well i have configured the database using windows authentication. not sure why SQL authentication was not working. Thank you for your support.
can you please let me know exactly which HP or other web sites that IRS standard version 7.6 needs to have access to at port 443.
i alreday know that alias services.isee.hp.com need to be connected through firewall but my company policies require IP address and HP strongly recommends use only alias.
can you please let me know which else alias needs to be connected and what IP should be used?
Thanks in advance.