• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 993
  • Last Modified:

NLB for hub & CAS -exchange 2007

hi
we have two mail box servers in ccr on exchange 2007. Now i am configuring an NLB for my two hub/cas servers. I noticed in some documentations that they are giving public and nlb on the same network. For example my public network is in Class C, 192.168.1.0 is it suggested to give the same subnet for the NLB as well
0
mishalk
Asked:
mishalk
1 Solution
 
kyodaiCommented:
You can also put them in different networks - in my eyes this would also be the cleaner solution. This however requires you to also have a routing strategy between the networks making implementation maybe harder if you only administrate the servers not the network. I can only assume the made this recommendation to keep implementation easier.
0
 
KaffiendCommented:
Nothing wrong with the cluster's IP address being on the same subnet.

It's a "Best Practice" that the heartbeat be on a separate subnet.
0
 
gupnitCommented:
Hi,
It all depends upon you scenario and what availability you want. It is always recommended to have both networks seperate. If you have some resource crunch, then go ahead and use the same network
Cheers
Nitin Gupta (gupnit)
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
mishalkAuthor Commented:
hi nitin
i did complete the nlb configuration
 and this is my config
"      Hub-Cas1
--------------
Public
NIC IP : 192.168.1.104/255.255.255.0
DNS   :  192.168.1.20
 
NLB
NIC IP  : 192.168.1.109 / 255.255.255.0
No DNS and No GW
 
Hub-Cas2
----------------
Public
Nic IP : 192.168.1.105/255.255.255.0
DNS   : 10.0.0.2
 
NLB
NIC IP : 192.168.1.110 /255.255.255.0
No DNS and NO GW
 
NLB Virtual name : webmail.domain.local
NLB Virtual  IP     : 192.168.1.111


now i am able to access : webmail.domain.local/owa , but only from the 192.168.1.0/255.255.255.0 network. If i ping from any other internal network i am getting time out. I have selected multicast while configuring NLB.

my nlb network card cables are also coming from the same switch of my public nic card. Instead of that do i need to do a card to card cross over or ? please help us
0
 
mishalkAuthor Commented:
sorry , on hub-cas02, i typed the dns wrong..i kept the correct dns entry in my configuration
0
 
gupnitCommented:
Hi,
If other subnets are unable to connect to your CAS server, then first you got to look at Network Routing and whether routing is enabled or not. Check your DNS too.
I have not looked at your NLB feasibility yet, if you can confirm above, then we can look at the NLB, as first the internal routing needs to be in place.
Cheers
Nitin
0
 
mishalkAuthor Commented:
hi nitin
when i changed from multicast to unicast, it is able to reach from any vlan we have configured in the switch. And now we are able to resolve the name and ip as well
0
 
mishalkAuthor Commented:
nitin
i was able to reach the cas server from any vlan, the problem was reaching the virtual host name and the virtual ip
0
 
gupnitCommented:
Hi,
You mean to say that even pinging by IP is not working. Are you sure you are able to ping from same LAN subnet
Thanks
Nitin
0
 
mishalkAuthor Commented:
yes, i can ping from same lan, but as  i mentioned earlier i am able to ping from any vlan after changing to multicast to unicast
0

Featured Post

Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now