locked
Adding Load Balancer RRS feed

  • Question

  • Question about Enterprise Edition (Consolidated) deployment:

    I have a working Front End pool consisting of only 1 server and also a mediation server and clients. I am inclined to think that it should be possible to

    1. add the load balancer and

    2. add the 2nd front end server

    without tearing apart my existing configuration/network. There isn't a procedure outlined in the deployment guide for such expansion. Could some one confirm before I proceed?

     

    Thanks.

    Thursday, October 9, 2008 4:27 PM

Answers

  • The reason you won't find a procedure for this documented in the deployment guides is that a single front-end server without a Hardware Load Balancer is not actually a supported configuration.

     

    But assuming that you have created a virtual IP for the the poolname FQDN and assigned it to the current Front-End server as an additional IP address, then you can simply deploy the HLB in your network, move that virtual IP over to it and then configure the HLB to work with the single Front-End.  Once that is completed you can deploy a second Front-End server and update the HLB to use both servers.

     

    If you currently are using your Front-End server's FQDN as the pool name (and thus is used in the certificates) then you have a little bit different scenario as you'll have to fix that to use a dedicated poolname FQDN first.

    Thursday, October 9, 2008 7:43 PM
    Moderator

All replies

  • The reason you won't find a procedure for this documented in the deployment guides is that a single front-end server without a Hardware Load Balancer is not actually a supported configuration.

     

    But assuming that you have created a virtual IP for the the poolname FQDN and assigned it to the current Front-End server as an additional IP address, then you can simply deploy the HLB in your network, move that virtual IP over to it and then configure the HLB to work with the single Front-End.  Once that is completed you can deploy a second Front-End server and update the HLB to use both servers.

     

    If you currently are using your Front-End server's FQDN as the pool name (and thus is used in the certificates) then you have a little bit different scenario as you'll have to fix that to use a dedicated poolname FQDN first.

    Thursday, October 9, 2008 7:43 PM
    Moderator
  • Are you sure a single Front-End in a Consolidated pool is not supported?  I have seen it done successfully several times, and I have never read an explicit statement in the OCS docs that says it is NOT supported.

     

    On Pg 14 of the Microsoft Office Communications Server 2007 Supportability Guide:

     

    "In Office Communications Server 2007, two types of Enterprise Pool topologies are supported:

    Enterprise pool in the consolidated topology. One or more Enterprise Edition servers in a pool, each running all server roles: Front-End, A/V Conferencing, and Web Conferencing, as well as IIS for the Web Components. 

     

    ** A single Enterprise Edition server, configured as an Enterprise pool, without a hardware load balancer and with a separate Back-End Database server, is supported.  ** 

     

    A hardware load balancer is required if two or more Enterprise Edition servers make up the pool. The consolidated topology can support up to 30,000 active, concurrent users."

     

    Akshai, I don't see why you couldn't add a second server to the pool and an HLB.  Just install the second server to the pool, add an HLB, and re-point your pool FQDN to the HLB virtual IP.  Caveat:  I have never tried this myself.

    Friday, October 10, 2008 2:26 PM
  • Curtis you are correct; I should state 'not recommended'.  It's interesting that the Supportibilty Guide has that statement, yet the Enterprise Deployment Guide has no mention of how to configure a Consolidated Enterprise Front-End without a HLB.

     

     

    Friday, October 10, 2008 3:33 PM
    Moderator
  • Actually a single frontend server in a consolidated pool is supported. Just configure your pool ip address with the same ip address of the front-end server in your DNS setting. We have tested this in a lab environment.  

    We are able to log on using the Web Access Server and the OC client using the pool address.

    /Thomas
    Friday, October 10, 2008 4:27 PM
  • Thomas,

     

    I know that works, but shouldn't the recommended/supported solution be to use unique IP address for the poolname (which is NOT the Front-End server's FQDN) and then assign that secondary IP address to the server's NIC?  Then when adding a second consolidated front-end server the virtual IP can easily be moved over to the HLB without reconfiguring.

     

    Friday, October 10, 2008 8:51 PM
    Moderator
  • Of course that should be the recommended configuration for a production environment. But if you have no load balancer available, and would like to try out the entrerprise install of OCS, this could be a workaround. Nothing more then that.

     

    /Thomas

     

    Tuesday, October 14, 2008 10:08 PM