Unsolved
This post is more than 5 years old
5 Posts
0
3779
Multi vcenter with omivv 4.1 error
Hi,
Our environment uses several vcenters in linked mode, all vcenters belong to the same SSO site.
Because of compliancy each vcenter uses it's own omivv instance.
So our setup looks something like this:
vc01 <- omivv01
|
vc02 <- omivv02
|
vc03 <- omivv03
Now we have problems accessing omivv through the vcenter flash client.
We do see the plugin icon but upon clicking it we see the following error in the vsphere-web-client-log:
[2017-11-21T16:35:05.589+01:00] [INFO ] http-bio-9090-exec-25 org.springframework.flex.servlet.MessageBrokerHandlerAdapter Channel endpoint amf received request.
[2017-11-21T16:36:04.525+01:00] [INFO ] http-bio-9090-exec-24 70002639 100991 200101 com.dell.pg.spectre.business.ConsoleSDKServiceImpl Exception at ConsoleSDKServiceImpl: URL=omivv01.site.nl/.../ConsoleSDK
[2017-11-21T16:36:04.526+01:00] [INFO ] http-bio-9090-exec-24 70002639 100991 200101 com.dell.pg.spectre.business.ConsoleSDKServiceImpl Exception at ConsoleSDKServiceImpl: 2 counts of InaccessibleWSDLException.
The strange thing is that this error log is taken from vc03, so i would have expected the error to include the hostname from omivv03
But instead it lists omivv01, which is linked to vc01, not vc03.
So i get why omivv01 is throwing an error, i just can't explain why my vc03 is using the url of vc01.
Obviously i tried deleting/reregistering the appliance, rebooting, etc etc.
Anyone got any tips?
Regards,
Peter
DELL-Vijay B
183 Posts
0
December 5th, 2017 05:00
Hi,
Refer the below screenshots. In multi-VCenter/multi-OMIVV environment, at a given time, only one OMIVV instance can be active. One need to change/select the desired OMIVV instance to get the service from in such environment.
Let us know if this helps.
Thanks,
Vijay
DELL-Vijay B
183 Posts
0
December 6th, 2017 03:00
Also, additional information can be found in OMIVV's user guide's section "Managing Multiple Appliance"
Thanks,
Vijay.
pbosgraaf
5 Posts
0
December 8th, 2017 05:00
Hi,
Thanks for the followup, i understand that's how it's supposed to work, however i don't even get that far.
As soon as i click Home > Omivv icon i see that error from console.
To troubleshoot this i scaled back my config to:
vc01 <- omivv01
|
vc02 <- absent
|
vc03 <- absent
This seems to work OK, i am able to manage hosts in VC01 with omivv01.
So i continued, deployed omivv03 and entered the credentials of vc03, so my config looks like this:
vc01 <- omivv01
|
vc02 <- absent
|
vc03 <- omivv03
Now when i logged in to vc03 for the first time the webclient is supposed to download the plugin.
When i look at /var/log/vmware/vsphere-client/logs/vsphere_client_virgo.log on the vc03 i see:
[2017-12-08T14:34:49.201+01:00] [ERROR] vc-extensionmanager-pool-109 com.vmware.vise.vim.extension.VcExtensionManager Package com.dell.plugin.OpenManage_Integration_for_VMware_vCenter_WebClient was not installed!
Error downloading omivv01.x.x/.../DellManagementPluginWebClient.zip. Make sure that the URL is reachable then logout/login to force another download. java.net.SocketTimeoutException: connect timed out
I replaced the hostname with x.x, but the original showed the hostname of omivv01 and not omivv03.
How can this happen? omivv01 is not paired with vc03, so why is this url used?
What's the proper way to request support on omivv? I would love to do a webex and find out exactly what's going on.
Thanks,
Peter
pbosgraaf
5 Posts
0
December 22nd, 2017 02:00
Bump, noone able to help us out?