Win2003 Cluster with multiple NICs

Hi,

The destination scenario should look like the image in
http://en.wikipedia.org/wiki/High-availability_cluster


Each node has 4 Nics

2 private and two public

Private Lan1 is using 172.17.1.x addresses mask: 255.255.255.0
Private Lan2 is using 172.17.2.x mask: 255.255.255.0
Public Lan1 is using 10.100.0.x mask: 255.255.255.0
At first I had Public lan2 in 10.100.1.x mask: 255.255.255.0

Since Windows 2003 Cluster can only use AND for resources I moved them to
10.100.0.x addresses (my SQL Server Group uses also a 10.100.0.x address).
After changing that, the network 'Public LAN 2' disappeared in Cluster
administrator.
How can I set up everything with redundancy without using trunking?


Regards,

Michael

Hi Michael,

as posted in german clustering group the only supported method which I'm
aware is - NIC teaming .
With teaming solutions you can utilize different approaches (switch / nic
redundancy) but this also depends on vendors capability of teaming
implementations.

Just be aware that teaming on heartbeat adapter is generally not supported.

Hope that helpds

Regards
Ramazan

"Michael Kugler" <> wrote in message
news:B63203F7-944E-49B6-BABE-...
> Hi,
>
> The destination scenario should look like the image in
> http://en.wikipedia.org/wiki/High-availability_cluster
>
>
> Each node has 4 Nics
>
> 2 private and two public
>
> Private Lan1 is using 172.17.1.x addresses mask: 255.255.255.0
> Private Lan2 is using 172.17.2.x mask: 255.255.255.0
> Public Lan1 is using 10.100.0.x mask: 255.255.255.0
> At first I had Public lan2 in 10.100.1.x mask: 255.255.255.0
>
> Since Windows 2003 Cluster can only use AND for resources I moved them to
> 10.100.0.x addresses (my SQL Server Group uses also a 10.100.0.x address).
> After changing that, the network 'Public LAN 2' disappeared in Cluster
> administrator.
> How can I set up everything with redundancy without using trunking?
>
>
> Regards,
>
> Michael