|
Question : IIS load Balancing/win 2003 with two NIC ..
|
|
Hi
I am trying to do IIS Load Balancing on windows 2003 Server and with TWO NIC card.
My Configuration Details :
OS : windows 2003 Std Edition
NIC : RealTek 8139
1 Switch 10/100
I have created small Network with Two Servers and 1 Switch with 4 NIC Card.
I had given 192.168.10.190 as CLUSTER IP address,
IISLOAD 1
NIC 1 : 192.168.10.191
NIC 2 : 192.168.10.193
IISLOAD 2
NIC 1 : 192.168.10.192
NIC2 : 192.168.10.194
I have created First Server on IISLOAD1 but after that when I am adding second server to host it has added but message is "NLB NOT BOUND",
Second,
after applied LOAD BALANCE I am unable to PING Primary Ip address : 192.168.10.192.
but both machine can PING Cluster IP address 192.168.10.190..
Please help me !
soumenb
|
Answer : IIS load Balancing/win 2003 with two NIC ..
|
|
Hi,
If you still facxe the problem then use the following steps i change the ip address you can use your ip there. This is configure which we use.
How-To: Configure Network Load Balancing (NLB) with Two Network Adapters
1.. Assign appropriate IP addresses to each NIC, placing them in separate
subnets.
· Node1 -
o "Public" NIC
§ IP address: 10.10.2.17 /as primary ip address
§ Subnet: 255.255.255.0
§ Gateway: 10.10.2.1 / as gateway
§ DNS: as appropriate
o "NLB" NIC
§ IP address: 192.168.1.1
§ Subnet: 255.255.255.0
§ Gateway: N/A
§ DNS: N/A
· Node2 -
o "Public" NIC
§ IP address: 10.10.2.18
§ Subnet: 255.255.255.0
§ Gateway: 10.10.2.1
§ DNS: as appropriate
o "NLB" NIC
§ IP address: 192.168.1.2
§ Subnet: 255.255.255.0
§ Gateway: N/A
§ DNS: N/A
2.. On the "Public" NICs, click "Advanced" and add an additional IP
address as the Virtual IP Address which clients will connect to from the
Public network (i.e. - 10.10.2.177)
3.. Install "Network Load Balancing" as an additional service from the
"Public" adapter properties.
a.. Click "Install.." and then select "Service" in the upper-window and
click "Add."
b.. Select "Network Load Balancing" in the upper-window and click "OK"
c.. Answer any prompts and provide the correct path to installation
media.
4.. Once NLB is installed, return to the Properties page for the "Public"
NIC and select the check-box next to "Network Load Balancing." This enables
the service globally.
5.. Next, select the item "Network Load Balancing" and click "Properties"
6.. Configure the NLB Cluster properties according to your parameters,
using the following example steps as a guide.
· Node1 -
o "Public" NLB Cluster Parameters tab
§ Primary IP address: 10.10.2.177
§ Subnet: 255.255.255.0
§ Full Internet Name mail.domain.com
o "Public" NLB Host Parameters tab
§ Priority: 1
§ Dedicated IP address: 10.10.2.17
§ Subnet: 255.255.255.0
· Node2 -
o "Public" NLB Cluster Parameters tab
§ Primary IP address: 10.10.2.177
§ Subnet: 255.255.255.0
§ Full Internet Name mail.domain.com
o "Public" NLB Host Parameters tab
§ Priority: 2
§ Dedicated IP address: 10.10.2.18
§ Subnet: 255.255.255.0
7.. MultiCast support can be optional in this configuration.
8.. You can also now take time to create a static Host record (A record) in your scenario's DNS infrastructure to provide appropriate name resolution to the NLB cluster name (i.e. - mail.domain.com or just mail).
9.. Your NLB cluster should be up and running.
10.. An external client should now be able to ping the IP address of the NLB cluster (i.e. - 10.10.2.177) as well as each of the individual node addresses (i.e. - 10.10.2.17 & -.18).
11.. Many good diagnostic commands can be found by typing "wlbs /?" in a command window. For example, "wlbs query" shows the status and convergence state of the cluster.
12.. IMPORTANT NOTE: In this configuration, each individual node is NOT able to ping the other node's Public physical IP address (i.e - 10.10.2.17 cannot ping 10.10.2.18 and vice-versa). I believe this is expected behavior, as the NLB cluster is now responding to requests on the Virtual Cluster address (i.e. - 10.10.2.177).
|
|
|
|
|
