Sign in
 
HomeProductsLibraryLearnDownloadsSupportForums
Microsoft Forefront TechCenter >
> 
> 
UAG 2010 NLB Array Creation

Unanswered UAG 2010 NLB Array Creation

  • Tuesday, January 08, 2013 11:42 AM
     
     
    Sign In to Vote
    0

    Hi,

    I currently have a single UAG 2010 server in production, I'm looking to create an array, but from past experience this has failed - basically I end up getting all sorts of weird networking issues with the activation failing at the end.

    I have the following in place

    UAG1 - internal ip 192.168.1.2, 192.168.1.3
    UAG1 ext ip - 182.67.23.112, 182.67.23.113, 182.67.23.114

    I'm by an online Ms test lab guide.

    The mentioned guide removes all the current IP addressing from the current UAG node, assigns new dips and assigns the ripped information as vips.

    I don't have that many free address on my network. I'm planning to do the following:

    1. Remove all secondary IPs (182.67.23.113, 182.67.23.114 & 192.168.1.3) from UAG1. These IPs are currently specified in the UAG activation wizard.
    2. Assign new IPs to UAG2.
    3. Create a NLB array between UAG1 & UAG2.
    4. Assign addresses 182.67.23.113, 182.67.23.114 & 192.168.1.3 as array vips
    5. Activate config

    Would this work or should I completely remove all the IP addressing information from UAG node1 and assign new details?

    Thanks 

     

All Replies

  • Thursday, January 10, 2013 8:31 PM
     
     
    Sign In to Vote
    0

    You should have enough IP addresses to do the cutover as specified in that document. When you move to an NLB scenario with VIPs, you end up with only 2 actual IP addresses on each server, one internal and one external. In the end you will have a total of 4 public IP addresses used, and 3 internal IP addresses.

    The reason the documentation takes you through the way it does is because they assume you are running DirectAccess actively on .112 and .113, and that you would most likely want to maintain those IP addresses as the active DirectAccess IPs. Otherwise, if your public VIPs turn out to be anything different than .112 and .113, all of your client computers will have to come back into the office to receive new settings before they will be able to connect.

    I would follow the document - assuming that I am correct about .112 and .113, remove those so that .114 is the only IP left on UAG1, and remove 192.168.1.2 also so that 192.168.1.3 is the remaining DIP on UAG1. Then setup UAG2 as 182.67.23.115 and 192.168.1.4, and then you can use the VIPs of 182.67.23.112 and 113, and an internal VIP of 192.168.1.2 - which if you are using ISATAP means you won't have to change anything in the ISATAP configuration either since it is most likely using 192.168.1.2 already.