This How To guide will take you through configuring Network Load Balancing and deploying MOSS 2007 in SharePoint Farm.

Transcription

1 Quick Brief This How To 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 Machine Roles Following table lists the role of server in the Lab and the products installed on them. Server Name Role Product Installed AXDC Domain Controller DNS Server Windows Server 2008 Enterprise SP1 (64 bit) AXSQL AXIIS1 AXIIS2 AXAOS AXClient Database Server for DynamicsAX and MOSS 2007 Web Server NLB - Not configured yet MOSS Not installed yet Web Server NLB - Not configured yet MOSS Not installed yet Microsoft Dynamics AX Application Object Server Microsoft Dynamics AX Client Windows Server 2008 Enterprise SP1 (64 bit).net 3.5 SP1 SQL Server 2008 Enterprise(64 bit) Windows Server 2008 Enterprise SP1 (64 bit).net 3.5 SP1 NLB Feature (Win2K8 Server Manager) IIS Role (Win2K8 Server Manager) Windows Server 2008 Enterprise SP1 (64 bit).net 3.5 SP1 NLB Feature (Win2K8 Server Manager) IIS Role (Win2K8 Server Manager) Windows Server 2008 Enterprise SP1 (64 bit).net 3.5 SP1 Windows Server 2008 Enterprise SP1 (64 bit).net 3.5 SP1 Network Configuration All the servers in the lab have two or three network adapters 1. AxNLBLab Used for isolated domain AXNLB communication 2. 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 cluster communication. 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 Following static IPs have been assigned to network adapter on these servers Server Name AxNLBLab VM-to-Host NLBHeartBeat AXDC AXSQL AXIIS AXIIS AXAOS AXClient Configuring Network Load balancing 1. Installing Network Load balancing tool a) On AXIIS1, open Server Manager from Administration tools b) Left click on Features and the Left click on Add Feature c) Select Network Load Balancing and click next and then Install to finish the wizard d) Repeat these steps on AXIIS2. 2. Launch Network Load balancing Manager from Program Administrative Tools a) In the manager Right Click on Network Load Balancer Cluster and Click New Cluster

4 b) Enter IP address of first server to be in the cluster. Click connect and choose the network card that is connected to AXNLB domain c) Leave defaults and click Next

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

6 f) Enter internet name. Choose Unicast if you have multiple network adapters or multicast if you have single network adapter on your webserver. If you are using Hyper-V you may have issues with unicast mode. See KB for workaround. g) On Port Rules page, delete existing rule can click add to create a new rule

7 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 j) Now we will add the second web server to the cluster. Right click on domain name and select Add host to cluster k) Enter IP address of second web server to be added to the cluster. Click connect and choose the network card that is connected to AXNLB domain

9 l) Accept defaults and click next. m) Click finish.

10 n) Wait while second webserver converges. o) After second webserver has converged and ready you will see two green boxes. You may have to refresh or restart NLB manager to get the final status.

11 Configuring DNS 1. 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 as the host s IP

12 4. After Host is added it will appear in DNS Manager as shown below. Verifying Network Load Balanced Servers 1. Trying ping 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 the clustered IP address 3. With network adapter AxNLBLab disabled on either AXIIS1 or AXIIS2, pinging host dynamics should 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 <H1>AXIIS1</H1> and save it as default.htm 6. On machine AXIIS2 navigate to default web server folder(c:\inetpub\wwwroot) 7. Create a new text file in this folder with text <H1>AXIIS2</H1> and save it as default.htm 8. Open internet explorer from a machine that is not one of the web servers. 9. Navigate to URL Depending upon NLB routing you may see AXIIS1 or AXIIS2 11. 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.

13 Installing MOSS 2007 on Web Servers and joining the Farm 1. On AXIIS1 machine, launch MOSS 2007 SP1 Setup 2. Enter your Key and click Next. 3. Click Advanced 4. Choose complete installation type and click Install Now

14 5. Wait for installation to complete 6. Click Close to start SharePoint Configuration Wizard.

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

16 9. Enter database Server name and account details for connecting to the DB server. If you are getting error connecting to Database, try opening port 1433 in database server firewall. 10. Click Next and proceed with default options

17 11. Verify details and click Next 12. Wait while SharePoint is being configured

18 13. After successful configuration, click Finish to close the wizard. 14. Launch SharePoint 3.0 Central Administration from Start > Administrative tools. Note that Farm topology web part shows AXIIS1 and AXSQL as part of the MOSS web farm.

19 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 the dropdown list. Enter DB user credentials and click next.

20 18. Launch SharePoint 3.0 Central Administration from Start > Administrative tools on AXIIS2. If you are 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. Conclusion We 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.