We have 2 connection servers, one for internal access, one for external access with an associated security server. I have created a manual pool and assigned VMs to the pool and made the entitlements. I can see the pool if I connect via the security server from an external source. When I connect via the internal connection server, the pool is not available (not visible at all). This is the second time I've had this issue. Previously after creating some other test pools, the problem pool suddenly appeared and could be accessed as expected. Is there some sync process that is failing here? All other pools on the internal connection server are functioning as expected.
Are you using tags in your environment? If so I would check to make sure that is set correctly on the pool having issues.
No tags are in use.
If you logon to the admin portal of the internal connection broker do you see the pool listed? That would verify whether you had some type of sync issue in the replica group.
Yes, it is listed. I've also run the PowerCLI command: get-pool and they are all listed on both connection servers.
I'm not sure then. The tags are the only thing I have seen that allows you to hide pools from certain brokers.
So, it does seem as though there is a sync or replication issue going on. Digging a little deeper on the connection server where the pool is not visible, there were no entitlements present for the pool at issue, even though there are on the other connection server. I added the entitlement (again) and I can see it now. Also, I had manually added a VM to the pool but it only showed on one connection server and not the other.
Here is one KB discussing replication. http://kb.vmware.com/kb/2014488
