I've got an answer from the support. It work connecting with the ip address of the log insight server. After it worked a first time with ip address it work also with fqdn. It solved my issue.
I've found a site with some instruction on how to connect to the various nodes. From the vio for kubernetes management machine: vkube login --insecure vkube cluster list --insecure Make a...
See more...
I've found a site with some instruction on how to connect to the various nodes. From the vio for kubernetes management machine: vkube login --insecure vkube cluster list --insecure Make a note of the Cluster ID of the cluster you want to access vkube cluster show <Cluster ID> --insecure Make a note of the IP of the Master and Worker Nodes. docker exec -it app-api /bin/bash cd /var/lib/vrc/terraform/<ClusterID> ssh -i private.key -F ssh-bastion.conf ubuntu@Kubernetes_Host_IP_Address
You license the CPU of hosts you're monitoring or VM/Objects you're monitoring not how many vrops server you install. To rebalance login to one the vrops server. Go on the configuration/Cluste...
See more...
You license the CPU of hosts you're monitoring or VM/Objects you're monitoring not how many vrops server you install. To rebalance login to one the vrops server. Go on the configuration/Cluster Management Page. You'll find in the action the rebalance option. Here you can rebalance the adapter, the gemfire (in memory data) and disk space (in my case this did not work too well, my data are mostly on one of the node of the cluster).
Uplink group are used by vmware to connect the "logical" port-group used by Virtual Machines/VMkernel Interface/Service console to the real network. When you add an host and its interface...
See more...
Uplink group are used by vmware to connect the "logical" port-group used by Virtual Machines/VMkernel Interface/Service console to the real network. When you add an host and its interfaces to a dvswitch you're adding them to the dvuplink group. If you go on the configuration/networkin/distributed virtual switch of an host, you will see the virtual switch in the middle of the screen, the portgroup on the left and the dvuplinks on the right. The number seems just a random number so that every dvuplink is called differently (for example we have renamed all the dvuplink/dvswitch to domething more readable).
Here you can find all information on vmware network adapter: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001805 VMXNET 3 is suppor...
See more...
Here you can find all information on vmware network adapter: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001805 VMXNET 3 is supported only for virtual machines version 7 and later, with a limited set of guest operating systems: 32- and 64-bit versions of Microsoft Windows XP and later 32- and 64-bit versions of Red Hat Enterprise Linux 5.0 and later 32- and 64-bit versions of SUSE Linux Enterprise Server 10 and later 32- and 64-bit versions of Asianux 3 and later 32- and 64-bit versions of Debian 4/Ubuntu and later 32/64-bit versions of Sun Solaris 10 U4 and later
If you use Windows Authentication to login to the database you've to change the user with which the Update Manager service start on the virtual center. You've to put the username/password of the ...
See more...
If you use Windows Authentication to login to the database you've to change the user with which the Update Manager service start on the virtual center. You've to put the username/password of the user that can connect to the database (by default Update Manager start with Local System account. When installing if the vCenter Server is on Windows 2008 I think you should also use the FQDN of the vCenter server (or the ip address) to be sure it get the right address (something to do with IPv6 on Windows 2008) . At least this worked for me.