Return
-
Title
Federation setup causes the lost virtualization info -
Description
When setting up Federation between Diagnostic Servers, it doesn't allow duplicate connections and duplicate connections must be removed from either one of the Diagnostic Servers. In case of VCenter monitoring, removing the duplicate VCenter connection means that one of the Diagnostic will not get virtualization info.
-
Resolution
WORKAROUND:
The workaround is to first give each VMWare connection an alias name, that way Spotlight treats each connection differently even though they're actually the same.1. Create the VM connection on Diagnostic server 1 as one would normally do2. Remote to Diagnostic server 23. Edit C:\Windows\System32\drivers\etc\hosts file add an alias like:10.30.180.4 servername.prod.quest.corp*note: IP address is the IP address of VM server. servername.prod.quest.corp is an alias name, different than server name4. Create another VM connection in Spotlight with name of the alias servername.prod.quest.corp. Do not use the option to use the Diagnostic Server service owner account. Enter the same credentials mnaualy.5. Link VM to the windows connections on this Diagnostic server;6. Repeat 2-4 on the third Diagnostic server.