There are different IP address between Connection server and Relica server.
When Connection server is crashed down, how Replica server works? How can clients connect to broker?
thanks a lot.
You will need some type of loadbalancing that will direct clients to the replica instead of the connection broker. We are in the midst of pricing out some hardware load balancing but for the time being we use DNS round robin and if the connection server has to go or there is problem we remove it from DNS.
If you found this or any other post helpful please consider the use of the Helpful/Correct buttons to award points
As already mentioned you need a load balancer (HW or SW) for that. Every View environment starts with the first connection server, which creates a new View LDAP directory during installation. The View LDAP is based on Microsoft ADAM (Active Directory Application Mode) with W2K3 and Windows LDS (Lightweight Directory Services) with W2K8 which is actually the same. In case of Windows Server 2003 View installs ADAM, using Windows Server 2008 it comes out of the box from Microsoft. The replica servers are full copies of the first connection server. If you install an replica, you have to connect that server with the connection server to copy the View LDAP. After doinf that the servers are all added to a View Server group which replicates the directories from all servers. You can have 7 servers in one View Server group max.
Don't forget to award the points if this answer was helpful for you.