It is important to note, that, since all the Exchange web apps live on the same server and the same TCP port, all five Virtual Servers and all five Service Groups are nearly identical to each other. Finally, there is a Service Group bound to each Virtual Server. Content Switch directs user’s request to the appropriate LB Virtual Server based on the URL. The general diagram is presented in Figure 2.Īs you can see, user connects to the Content Switch first. Finally, we need a catchall default entity for cases when URL does not match anything. In addition, we are not implementing MAPI at this point. Also, our testing indicates that Outlook Anywhere (RPC) and EWS need to be grouped together in order to avoid transient Outlook errors. Now, let us see how this general architecture can be translated into NetScaler configuration.įirst thing that comes to mind is that some web apps can be grouped together to avoid excessive complexity. The basic idea is that Layer 7 proxy allows us to have independent logical entry point for each Exchange web app which in turn allows us to independently switch them on and off based on their individual health rather than overall health of the server. Path: HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parametersīack to top General Architecture of the SSL Content Switchīelow is the load-balancing architecture as seen by the Microsoft: By default, this parameter in the registry does not exist so we need to add it: The only thing to do is to configure TCP/IP idle timeout. In Exchange 2013, there are no CAS arrays anymore, so no need to create one. However, we are only interested in the parts connected to load balancing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |