Why Unicast NLB server needs to have 2 NIC connected to different IP VLAN ?
Hi All,
Is there any reason as to why Windows Server 2003 Unicast NLB clustered server (running Terminal Server 2003) is configured with 2x vNIC and each of them connected to two different IP address class or VLANs ?
The server is deployed as Vmware Virtual Machine and I wonder if the IP address can be on the same VLAN for the simplicity of migration sake ?
Any thoughts and comments would be greatly appreciated,
Thanks
Is there any reason as to why Windows Server 2003 Unicast NLB clustered server (running Terminal Server 2003) is configured with 2x vNIC and each of them connected to two different IP address class or VLANs ?
The server is deployed as Vmware Virtual Machine and I wonder if the IP address can be on the same VLAN for the simplicity of migration sake ?
Any thoughts and comments would be greatly appreciated,
Thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I agree with you it makes no sense in a VMware environment
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes, you are right guys.
the current configuration is as follows:
So is it possible to maintain it as Unicast NLB and change all of the IP address VLAN into the same VLAN 5 just for the sake of migrating it into the different data center with different IP address class ?
the current configuration is as follows:
VM1 - vNIC1
IP: 192.168.1.14
VLAN 1
VM1 - vNIC2
IP1: 10.1.1.10
IP2: 10.1.1.100 --> The Virtual IP of Clustered Terminal Server Service
VLAN: 5
VM2 - vNIC1
IP: 192.168.1.15
VLAN 1
VM2 - vNIC2
IP1: 10.1.1.11
IP2: 10.1.1.100 --> The Virtual IP of Clustered Terminal Server Service
VLAN 5
So is it possible to maintain it as Unicast NLB and change all of the IP address VLAN into the same VLAN 5 just for the sake of migrating it into the different data center with different IP address class ?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
ok, so in this case both of the NIC can still be used with the same VLAN for the Unicast NLB to work successfully ?
I'm not in the position to change the mode from Unicast into Multicast since I don't know the behaviour and how it is going to work with the Clustered Terminal Server.
Proposed changes to IP address
VM1 - vNIC1
IP: 192.168.1.14
VLAN 1
VM1 - vNIC2
IP1: 192.168.1.50
IP2: 192.168.1.100 --> The Virtual IP of Clustered Terminal Server Service
VLAN: 1
VM2 - vNIC1
IP: 192.168.1.15
VLAN 1
VM2 - vNIC2
IP1: 192.168.1.51
IP2: 192.168.1.100 --> The Virtual IP of Clustered Terminal Server Service
VLAN 1
I'm not in the position to change the mode from Unicast into Multicast since I don't know the behaviour and how it is going to work with the Clustered Terminal Server.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
my understanding is that both vNIC will have the same default gateway because the IP address are in the same IP class / VLAN. Do I still need to add the static route ?
Do you mean by using the "route add –p ...."
Do you mean by using the "route add –p ...."
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks !
ASKER
I can understand the configuration of IGMP multicast NLB for exchange server 2007 Hub Transport server on Windows Server 2008, but I don't know if this can be applied to the Terminal Server 2003.