MOSS 2007 Deployment on NLB Web Servers[1]

7/31/2019 MOSS 2007 Deployment on NLB Web Servers[1]

1/20

Quick BriefThis HowTo guide will take you through configuring Network Load Balancing and deploying MOSS 2007

in SharePoint Farm.

This document will serve as prerequisite for Enterprise Portal deployment on NLB MOSS Web farm.

Network Setup


2/20

Machine RolesFollowing table lists the role of server in the Lab and the products installed on them.

Server Name Role Product Installed

AXDCDomain Controller

DNS Server

Windows Server 2008 Enterprise SP1 (64 bit)

AXSQL

Database Server for DynamicsAX

and MOSS 2007


.NET 3.5 SP1

SQL Server 2008 Enterprise(64 bit)

AXIIS1

Web Server

NLB - Not configured yet

MOSS 2007 - Not installed yet


.NET 3.5 SP1

NLB Feature (Win2K8 Server Manager)

IIS Role (Win2K8 Server Manager)

AXIIS2

Web ServerNLB - Not configured yet

MOSS 2007 - Not installed yet

Windows Server 2008 Enterprise SP1 (64 bit).NET 3.5 SP1

NLB Feature (Win2K8 Server Manager)

IIS Role (Win2K8 Server Manager)

AXAOSMicrosoft Dynamics AX

Application Object Server


.NET 3.5 SP1

AXClientMicrosoft Dynamics AX Client Windows Server 2008 Enterprise SP1 (64 bit)

.NET 3.5 SP1

Network ConfigurationAll the servers in the lab have two or three network adapters

1. AxNLBLab Used for isolated domain AXNLB communication2. VM-to-Host This lab was created in Hyper-V environment with each of the server hosted as a

VM. This network adapter allows communication between the Host OS with the VMs. This

network connection is primarily used for management of these servers using Remote Desktop

and copying setup files. If you are not hosting your servers as virtual machines, then this

network adapter is not required.

3. NLBHeartBeat This network is used by IIS machines for their private NLB clustercommunication. Only the IIS servers in the lab have this network adapter.

This adapter is required when NLB is being configured in Unicast cluster operation mode. In

Multicast mode, this network adapter is not required.


3/20

Following static IPs have been assigned to network adapter on these servers

Server Name AxNLBLab VM-to-Host NLBHeartBeat

AXDC 10.60.110.100 192.168.0.10

AXSQL 10.60.110.102 192.168.0.20

AXIIS1 10.60.110.103 192.168.0.30 10.0.0.3

AXIIS2 10.60.110.104 192.168.0.40 10.0.0.4

AXAOS 10.60.110.105 192.168.0.50

AXClient 10.60.110.106 192.168.0.60

Configuring Network Load balancing1. Installing Network Load balancing tool

a) On AXIIS1 , open Server Manager from Administration toolsb) Left click on Features and the Left click on Add Featurec) Select Network Load Balancing and click next and then Install to finish the wizardd) Repeat these steps on AXIIS2.

2. Launch Network Load balancing Manager from Program Administrative Toolsa) In the manager Right Click on Network Load Balancer Cluster and Click New Cluster


4/20

b) Enter IP address of first server to be in the cluster. Click connect and choose the networkcard that is connected to AXNLB domain

c) Leave defaults and click Next


5/20

d) Click Add. Enter Virtual IP address and subnet mask for your NLB Cluster

e) Click Next


6/20

f) Enter internet name. Choose Unicast if you have multiple network adapters or multicast ifyou have single network adapter on your webserver. If you are using Hyper-V you may have

issues with unicast mode. See KB 953828 for workaround.

g) On Port Rules page, delete existing rule can click add to create a new rule


7/20

h) Create new rule as shown below. Click OK. Click Finish.

i) Once complete, you will see a green background icon next to server name


8/20

j) Now we will add the second web server to the cluster. Right click on domain name andselect Add host to cluster

k) Enter IP address of second web server to be added to the cluster. Click connect and choosethe network card that is connected to AXNLB domain


9/20

l) Accept defaults and click next.

m) Click finish.


10/20

n) Wait while second webserver converges.

o) After second webserver has converged and ready you will see two green boxes. You mayhave to refresh or restart NLB manager to get the final status.


11/20

Configuring DNS1. Launch DNS Manager on AXDC machine. Expand Forward Lookup Zones and select

AXNLB.DYNAMICS.LAB domain

2. Right on this node and Select New Host

3. Create a new Host with name dynamics and use cluster IP 10.60.110.200 as the hosts IP


12/20

4. After Host is added it will appear in DNS Manager as shown below.

Verifying Network Load Balanced Servers1. Trying ping 10.60.110.200 from any of the Lab machine. You should get 4 replies from the

clustered IP address

2. Trying pinging host dynamics from any of the Lab machine. You should get 4 replies from theclustered IP address

3. With network adapter AxNLBLab disabled on either AXIIS1 or AXIIS2, pinging host dynamicsshould return replies.

4. On machine AXIIS1 navigate to default web server folder (C:\InetPub\wwwroot)5. Create a new text file in this folder with text AXIIS1 and save it as default.htm6. On machine AXIIS2 navigate to default web server folder(C:\InetPub\wwwroot)7. Create a new text file in this folder with text AXIIS2 and save it as default.htm8. Open internet explorer from a machine that is not one of the web servers.9. Navigate to URLhttp://dynamics10.Depending upon NLB routing you may see AXIIS1 or AXIIS211.You can now repeat the process of disabling your network adapter on webservers to see which

servers you are connecting to as well as you can verify that NLB is behaving as expected.
http://dynamics/http://dynamics/http://dynamics/http://dynamics/


13/20

Installing MOSS 2007 on Web Servers and joining the Farm1. On AXIIS1 machine, launch MOSS 2007 SP1 Setup2. Enter your Key and click Next.3. Click Advanced

4. Choose complete installation type and click Install Now


14/20

5. Wait for installation to complete

6. Click Close to start SharePoint Configuration Wizard.


15/20

7. Click Next.

8. Choose No, I want to create a new server farm and click Next


16/20

9. Enter database Server name and account details for connecting to the DB server. If you aregetting error connecting to Database, try opening port 1433 in database server firewall.

10.Click Next and proceed with default options


17/20

11.Verify details and click Next

12.Wait while SharePoint is being configured


18/20

13.After successful configuration, click Finish to close the wizard.

14.Launch SharePoint 3.0 Central Administration from Start > Administrative tools. Note that Farmtopology web part shows AXIIS1 and AXSQL as part of the MOSS web farm.


19/20

15.Repeat Steps 2- 13 on machine AXIIS2. Only steps 8 and 9 are different as shown below.16.On AXIIS2 choose option Yes, I want to connect to an existing server farm

17.Enter Database server name click Retrieve Database Name. Select correct DB from thedropdown list. Enter DB user credentials and click next.


20/20

18.Launch SharePoint 3.0 Central Administration from Start > Administrative tools on AXIIS2. If youare getting connection errors, try opening port on which Central Administration is running on

machine AXIIS1 (port 3996 in our case)

19.Verify that AXIIS1 and AXIIS2 show up in the Farm Topology web part.

ConclusionWe have successfully configured MOSS 2007 on a network load balancing web server. With Central

Administration running on AXIIS1, it is configured as Farm Admin machine. The Lab is now ready for

Enterprise Portal deployment.

Documents

MOSS 2007 Deployment on NLB Web Servers[1]