vcentre server is configured with vmware probe in UIM ,but the device model is showing as HOST ,not showing as Vcentre server .Kindly help.
your post is a bit short... So maybe attaching a picture might help us to help you...
This article may help - https://na4.salesforce.com/articles/Case_Summary/VC-only-show-as-a-Host?popup=true
In case you can't access it, here's the main points:
vCenter server only shows as a Host - not vCenter
This caused issues with the integration of Spectrum and CAUIM - fields were not populating as expected between the two products, which led to other issues with alarm management, device display, etc.
Error in discovery_server.log.5:
21 Apr 2015 09:34:22,071 [attach_clientsession] ERROR com.nimsoft.nimbus.NimSubscribe - Not able to callback for hubpost. Reason is: java.lang.reflect.InvocationTargetException
21 Apr 2015 09:34:22,072 [attach_clientsession] FATAL com.nimsoft.nimbus.NimSubscribe - pdsdata: md5sum=c‡ؓͰߦ���� nimts=1429626853, tz_offset=18000, , subject=probe_discovery, hop0=ftwcauimph01, origin=ftwcauimph01, charset=windows-1252, robot=ftwvc01, prid=vmware, qsize=1, pri=1, source=10.199.21.134, nimid=QL00413980-00132, domain=THR_PROD_Domain, hop=0 udata: graph=x۬ޛФȲ��Њ9y?ͬW c0cӧ^ƃ#㧓ɦؼG��іυK�6[��cuwEUղ#V��ė࠼i࠙࠹��߽��۟, mimeType=application/x-deflate 21 Apr 2015 09:34:22,072 [attach_clientsession] ERROR com.nimsoft.nimbus.NimSubscribe - java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor204.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.nimsoft.nimbus.NimSubscribe.callbackProxy(NimSubscribe.java:287) at sun.reflect.GeneratedMethodAccessor203.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.nimsoft.nimbus.NimServerSession$ThreadClient.run(NimServerSession.java:191) Caused by: java.lang.OutOfMemoryError: Java heap space ....
The above error led us to increase the max java size for the discovery_server (via raw config), which resolved the issue.
After changing the memory level and restarting the probe, the discovery queues had to drain and correlate the information.
Once these cleared up, the issues was resolved and the hosts were accurately shown/saved.
Hi Philip ,
I have tried the above steps earlier ,but still not resolved .
Retrieving data ...