|
|
|
date: Tue, 1 Jul 2008 01:47:00 -0700,
group: microsoft.public.exchange.clustering
back
Re: CCR on Windows Server 2008 - Private Network Question
Hi Edwin, thanks for your response.
So are you saying when configuring the private network, we can add a default
gateway? I thought this wasn't best practice since the Public NICs have a
default gateway.
For example, would the following be acceptable?
Private NIC 01 - 10.0.31.70, Subnet 255.255.255.0, Default Gateway 10.0.31.1
Private NIC 02 - 10.29.81.70, Subnet 255.255.255.0, Default Gateway
10.29.81.70
Sorry if I'm missing something. It's just from everything I have read states
that you should configure the Private NICs with just an IP and subnet mask
ONLY.
Thanks again in advance,
Peter
"Edwin vMierlo [MVP]" wrote:
> With windows 2008 you can be on seperate subnets (eg routed networking)
>
> rgds,
> Edwin.
>
>
> "Don Pedro" wrote in message
> news:7042D216-541C-46F0-9A73-09FA4E3CAEBA@microsoft.com...
> > Hi,
> >
> > I am deploying a CCR on Windows Server 2008 using Exchange 2007 SP1.
> >
> > Each node is in a separate physical location and therefore on different
> > switches.
> >
> > I am happy with my Public network config. I now need to configure the
> > Private one.
> >
> > If I am supposed to configure the Private network with non-routable IPs
> and
> > no default gateway, how are they expected to communicate? I asked my
> Network
> > guys and they are at a loss of how to set this up.
> >
> > Has someone done this and how was it achieved?
> >
> > Thanks,
> > Peter
> >
> >
>
>
>
date: Tue, 1 Jul 2008 04:07:00 -0700
author: Don Pedro
Re: CCR on Windows Server 2008 - Private Network Question
- Windows Server 2008 Failover Clustering there are no Public or Private
networks.
- Failover Clustering automatically controls and configures network
configuration. If a NIC has a default gateway, it will be used for
public/client communications, unless you change the configuration (uncheck
"Allow clients to connect through the network").
- On Windows Server 2008 when both nodes sit on different IP subnets, you
cannot *not have* a default gateway for network traffic (including cluster
communications/heartbeat) to get to the other IP subnet.
- The nature of heartbeat/cluster communications has changed from a UDP
broadcast on port 3343 to a UDP unicast on the same port. Amongst other
benefits, it allows cluster communication to cross routers.
References:
Core setup team blog:
Multi-Site Failover Cluster Communications Connectivity
http://blogs.technet.com/askcore/archive/2008/06/02/multi-site-failover-cluster-communications-connectivity.aspx
Windows Server 2008 Failover Clustering White Papers:
http://www.microsoft.com/downloads/details.aspx?familyid=75566F16-627D-4DD3-97CB-83909D3C722B&displaylang=en
(Take a look at the white papers on multi-site cluster and WS08 Failover
Clustering Architecture).
--
Bharat Suneja
Microsoft Corporation
blog: exchangepedia.com/blog
This posting is provided "AS IS" with no warranties, and confers no
rights. Please do not send email directly to this alias. This alias is for
newsgroup purposes only.
----------------------------
"Don Pedro" wrote in message
news:25CC1FE7-BEA2-4C5B-A577-359675B7C31F@microsoft.com...
> Hi Edwin, thanks for your response.
>
> So are you saying when configuring the private network, we can add a
> default
> gateway? I thought this wasn't best practice since the Public NICs have a
> default gateway.
>
> For example, would the following be acceptable?
>
> Private NIC 01 - 10.0.31.70, Subnet 255.255.255.0, Default Gateway
> 10.0.31.1
> Private NIC 02 - 10.29.81.70, Subnet 255.255.255.0, Default Gateway
> 10.29.81.70
>
> Sorry if I'm missing something. It's just from everything I have read
> states
> that you should configure the Private NICs with just an IP and subnet mask
> ONLY.
>
> Thanks again in advance,
> Peter
>
> "Edwin vMierlo [MVP]" wrote:
>
>> With windows 2008 you can be on seperate subnets (eg routed networking)
>>
>> rgds,
>> Edwin.
>>
>>
>> "Don Pedro" wrote in message
>> news:7042D216-541C-46F0-9A73-09FA4E3CAEBA@microsoft.com...
>> > Hi,
>> >
>> > I am deploying a CCR on Windows Server 2008 using Exchange 2007 SP1.
>> >
>> > Each node is in a separate physical location and therefore on different
>> > switches.
>> >
>> > I am happy with my Public network config. I now need to configure the
>> > Private one.
>> >
>> > If I am supposed to configure the Private network with non-routable IPs
>> and
>> > no default gateway, how are they expected to communicate? I asked my
>> Network
>> > guys and they are at a loss of how to set this up.
>> >
>> > Has someone done this and how was it achieved?
>> >
>> > Thanks,
>> > Peter
>> >
>> >
>>
>>
>>
date: Tue, 1 Jul 2008 06:43:23 -0700
author: Bharat Suneja [MSFT]
Re: CCR on Windows Server 2008 - Private Network Question
OK, so I do need to add a default gateway to the heartbeat IPs for routing
purposes. I can then untick the "Allow clients to connect through the network"
Then I will have 2 NICs per node configured, since a single NIC cluster node
violates a 'best practice', that being a single point of failure for cluster
communications...and therefore, is not a supported configuration.
Am I correct in this assumption?
"Bharat Suneja [MSFT]" wrote:
> - Windows Server 2008 Failover Clustering there are no Public or Private
> networks.
> - Failover Clustering automatically controls and configures network
> configuration. If a NIC has a default gateway, it will be used for
> public/client communications, unless you change the configuration (uncheck
> "Allow clients to connect through the network").
> - On Windows Server 2008 when both nodes sit on different IP subnets, you
> cannot *not have* a default gateway for network traffic (including cluster
> communications/heartbeat) to get to the other IP subnet.
> - The nature of heartbeat/cluster communications has changed from a UDP
> broadcast on port 3343 to a UDP unicast on the same port. Amongst other
> benefits, it allows cluster communication to cross routers.
>
> References:
> Core setup team blog:
> Multi-Site Failover Cluster Communications Connectivity
> http://blogs.technet.com/askcore/archive/2008/06/02/multi-site-failover-cluster-communications-connectivity.aspx
>
> Windows Server 2008 Failover Clustering White Papers:
> http://www.microsoft.com/downloads/details.aspx?familyid=75566F16-627D-4DD3-97CB-83909D3C722B&displaylang=en
>
> (Take a look at the white papers on multi-site cluster and WS08 Failover
> Clustering Architecture).
> --
> Bharat Suneja
> Microsoft Corporation
> blog: exchangepedia.com/blog
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights. Please do not send email directly to this alias. This alias is for
> newsgroup purposes only.
> ----------------------------
>
>
>
>
> "Don Pedro" wrote in message
> news:25CC1FE7-BEA2-4C5B-A577-359675B7C31F@microsoft.com...
> > Hi Edwin, thanks for your response.
> >
> > So are you saying when configuring the private network, we can add a
> > default
> > gateway? I thought this wasn't best practice since the Public NICs have a
> > default gateway.
> >
> > For example, would the following be acceptable?
> >
> > Private NIC 01 - 10.0.31.70, Subnet 255.255.255.0, Default Gateway
> > 10.0.31.1
> > Private NIC 02 - 10.29.81.70, Subnet 255.255.255.0, Default Gateway
> > 10.29.81.70
> >
> > Sorry if I'm missing something. It's just from everything I have read
> > states
> > that you should configure the Private NICs with just an IP and subnet mask
> > ONLY.
> >
> > Thanks again in advance,
> > Peter
> >
> > "Edwin vMierlo [MVP]" wrote:
> >
> >> With windows 2008 you can be on seperate subnets (eg routed networking)
> >>
> >> rgds,
> >> Edwin.
> >>
> >>
> >> "Don Pedro" wrote in message
> >> news:7042D216-541C-46F0-9A73-09FA4E3CAEBA@microsoft.com...
> >> > Hi,
> >> >
> >> > I am deploying a CCR on Windows Server 2008 using Exchange 2007 SP1.
> >> >
> >> > Each node is in a separate physical location and therefore on different
> >> > switches.
> >> >
> >> > I am happy with my Public network config. I now need to configure the
> >> > Private one.
> >> >
> >> > If I am supposed to configure the Private network with non-routable IPs
> >> and
> >> > no default gateway, how are they expected to communicate? I asked my
> >> Network
> >> > guys and they are at a loss of how to set this up.
> >> >
> >> > Has someone done this and how was it achieved?
> >> >
> >> > Thanks,
> >> > Peter
> >> >
> >> >
> >>
> >>
> >>
>
>
date: Tue, 1 Jul 2008 07:21:01 -0700
author: Don Pedro
Re: CCR on Windows Server 2008 - Private Network Question
Correct.
Additionally, Windows Server 2008 Failover Clustering *requires* two NICs.
--
Bharat Suneja
Microsoft Corporation
blog: exchangepedia.com/blog
This posting is provided "AS IS" with no warranties, and confers no
rights. Please do not send email directly to this alias. This alias is for
newsgroup purposes only.
----------------------------
"Don Pedro" wrote in message
news:EA98F40E-E0F0-43D1-993F-E619A288453E@microsoft.com...
> OK, so I do need to add a default gateway to the heartbeat IPs for routing
> purposes. I can then untick the "Allow clients to connect through the
> network"
>
> Then I will have 2 NICs per node configured, since a single NIC cluster
> node
> violates a 'best practice', that being a single point of failure for
> cluster
> communications...and therefore, is not a supported configuration.
>
> Am I correct in this assumption?
>
>
>
> "Bharat Suneja [MSFT]" wrote:
>
>> - Windows Server 2008 Failover Clustering there are no Public or Private
>> networks.
>> - Failover Clustering automatically controls and configures network
>> configuration. If a NIC has a default gateway, it will be used for
>> public/client communications, unless you change the configuration
>> (uncheck
>> "Allow clients to connect through the network").
>> - On Windows Server 2008 when both nodes sit on different IP subnets, you
>> cannot *not have* a default gateway for network traffic (including
>> cluster
>> communications/heartbeat) to get to the other IP subnet.
>> - The nature of heartbeat/cluster communications has changed from a UDP
>> broadcast on port 3343 to a UDP unicast on the same port. Amongst other
>> benefits, it allows cluster communication to cross routers.
>>
>> References:
>> Core setup team blog:
>> Multi-Site Failover Cluster Communications Connectivity
>> http://blogs.technet.com/askcore/archive/2008/06/02/multi-site-failover-cluster-communications-connectivity.aspx
>>
>> Windows Server 2008 Failover Clustering White Papers:
>> http://www.microsoft.com/downloads/details.aspx?familyid=75566F16-627D-4DD3-97CB-83909D3C722B&displaylang=en
>>
>> (Take a look at the white papers on multi-site cluster and WS08 Failover
>> Clustering Architecture).
>> --
>> Bharat Suneja
>> Microsoft Corporation
>> blog: exchangepedia.com/blog
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights. Please do not send email directly to this alias. This alias is
>> for
>> newsgroup purposes only.
>> ----------------------------
>>
>>
>>
>>
>> "Don Pedro" wrote in message
>> news:25CC1FE7-BEA2-4C5B-A577-359675B7C31F@microsoft.com...
>> > Hi Edwin, thanks for your response.
>> >
>> > So are you saying when configuring the private network, we can add a
>> > default
>> > gateway? I thought this wasn't best practice since the Public NICs have
>> > a
>> > default gateway.
>> >
>> > For example, would the following be acceptable?
>> >
>> > Private NIC 01 - 10.0.31.70, Subnet 255.255.255.0, Default Gateway
>> > 10.0.31.1
>> > Private NIC 02 - 10.29.81.70, Subnet 255.255.255.0, Default Gateway
>> > 10.29.81.70
>> >
>> > Sorry if I'm missing something. It's just from everything I have read
>> > states
>> > that you should configure the Private NICs with just an IP and subnet
>> > mask
>> > ONLY.
>> >
>> > Thanks again in advance,
>> > Peter
>> >
>> > "Edwin vMierlo [MVP]" wrote:
>> >
>> >> With windows 2008 you can be on seperate subnets (eg routed
>> >> networking)
>> >>
>> >> rgds,
>> >> Edwin.
>> >>
>> >>
>> >> "Don Pedro" wrote in message
>> >> news:7042D216-541C-46F0-9A73-09FA4E3CAEBA@microsoft.com...
>> >> > Hi,
>> >> >
>> >> > I am deploying a CCR on Windows Server 2008 using Exchange 2007 SP1.
>> >> >
>> >> > Each node is in a separate physical location and therefore on
>> >> > different
>> >> > switches.
>> >> >
>> >> > I am happy with my Public network config. I now need to configure
>> >> > the
>> >> > Private one.
>> >> >
>> >> > If I am supposed to configure the Private network with non-routable
>> >> > IPs
>> >> and
>> >> > no default gateway, how are they expected to communicate? I asked my
>> >> Network
>> >> > guys and they are at a loss of how to set this up.
>> >> >
>> >> > Has someone done this and how was it achieved?
>> >> >
>> >> > Thanks,
>> >> > Peter
>> >> >
>> >> >
>> >>
>> >>
>> >>
>>
>>
date: Tue, 1 Jul 2008 07:48:56 -0700
author: Bharat Suneja [MSFT]
Re: CCR on Windows Server 2008 - Private Network Question
Thanks Bharat for your professional advice.
I hope this discussion proves as useful to others as it has been for me.
Peter
"Bharat Suneja [MSFT]" wrote:
> Correct.
>
> Additionally, Windows Server 2008 Failover Clustering *requires* two NICs.
> --
> Bharat Suneja
> Microsoft Corporation
> blog: exchangepedia.com/blog
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights. Please do not send email directly to this alias. This alias is for
> newsgroup purposes only.
> ----------------------------
>
>
>
>
> "Don Pedro" wrote in message
> news:EA98F40E-E0F0-43D1-993F-E619A288453E@microsoft.com...
> > OK, so I do need to add a default gateway to the heartbeat IPs for routing
> > purposes. I can then untick the "Allow clients to connect through the
> > network"
> >
> > Then I will have 2 NICs per node configured, since a single NIC cluster
> > node
> > violates a 'best practice', that being a single point of failure for
> > cluster
> > communications...and therefore, is not a supported configuration.
> >
> > Am I correct in this assumption?
> >
> >
> >
> > "Bharat Suneja [MSFT]" wrote:
> >
> >> - Windows Server 2008 Failover Clustering there are no Public or Private
> >> networks.
> >> - Failover Clustering automatically controls and configures network
> >> configuration. If a NIC has a default gateway, it will be used for
> >> public/client communications, unless you change the configuration
> >> (uncheck
> >> "Allow clients to connect through the network").
> >> - On Windows Server 2008 when both nodes sit on different IP subnets, you
> >> cannot *not have* a default gateway for network traffic (including
> >> cluster
> >> communications/heartbeat) to get to the other IP subnet.
> >> - The nature of heartbeat/cluster communications has changed from a UDP
> >> broadcast on port 3343 to a UDP unicast on the same port. Amongst other
> >> benefits, it allows cluster communication to cross routers.
> >>
> >> References:
> >> Core setup team blog:
> >> Multi-Site Failover Cluster Communications Connectivity
> >> http://blogs.technet.com/askcore/archive/2008/06/02/multi-site-failover-cluster-communications-connectivity.aspx
> >>
> >> Windows Server 2008 Failover Clustering White Papers:
> >> http://www.microsoft.com/downloads/details.aspx?familyid=75566F16-627D-4DD3-97CB-83909D3C722B&displaylang=en
> >>
> >> (Take a look at the white papers on multi-site cluster and WS08 Failover
> >> Clustering Architecture).
> >> --
> >> Bharat Suneja
> >> Microsoft Corporation
> >> blog: exchangepedia.com/blog
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights. Please do not send email directly to this alias. This alias is
> >> for
> >> newsgroup purposes only.
> >> ----------------------------
> >>
> >>
> >>
> >>
> >> "Don Pedro" wrote in message
> >> news:25CC1FE7-BEA2-4C5B-A577-359675B7C31F@microsoft.com...
> >> > Hi Edwin, thanks for your response.
> >> >
> >> > So are you saying when configuring the private network, we can add a
> >> > default
> >> > gateway? I thought this wasn't best practice since the Public NICs have
> >> > a
> >> > default gateway.
> >> >
> >> > For example, would the following be acceptable?
> >> >
> >> > Private NIC 01 - 10.0.31.70, Subnet 255.255.255.0, Default Gateway
> >> > 10.0.31.1
> >> > Private NIC 02 - 10.29.81.70, Subnet 255.255.255.0, Default Gateway
> >> > 10.29.81.70
> >> >
> >> > Sorry if I'm missing something. It's just from everything I have read
> >> > states
> >> > that you should configure the Private NICs with just an IP and subnet
> >> > mask
> >> > ONLY.
> >> >
> >> > Thanks again in advance,
> >> > Peter
> >> >
> >> > "Edwin vMierlo [MVP]" wrote:
> >> >
> >> >> With windows 2008 you can be on seperate subnets (eg routed
> >> >> networking)
> >> >>
> >> >> rgds,
> >> >> Edwin.
> >> >>
> >> >>
> >> >> "Don Pedro" wrote in message
> >> >> news:7042D216-541C-46F0-9A73-09FA4E3CAEBA@microsoft.com...
> >> >> > Hi,
> >> >> >
> >> >> > I am deploying a CCR on Windows Server 2008 using Exchange 2007 SP1.
> >> >> >
> >> >> > Each node is in a separate physical location and therefore on
> >> >> > different
> >> >> > switches.
> >> >> >
> >> >> > I am happy with my Public network config. I now need to configure
> >> >> > the
> >> >> > Private one.
> >> >> >
> >> >> > If I am supposed to configure the Private network with non-routable
> >> >> > IPs
> >> >> and
> >> >> > no default gateway, how are they expected to communicate? I asked my
> >> >> Network
> >> >> > guys and they are at a loss of how to set this up.
> >> >> >
> >> >> > Has someone done this and how was it achieved?
> >> >> >
> >> >> > Thanks,
> >> >> > Peter
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >>
> >>
> >>
>
>
date: Tue, 1 Jul 2008 08:25:00 -0700
author: Don Pedro
Re: CCR on Windows Server 2008 - Private Network Question
Oh, one last question.
Can the second NIC of each node be on the same network as the first NIC.
i.e. - NODE01 - NIC 1 (10.0.31.60), NIC 2 (10.0.31.65)
NODE02 - NIC 1 (10.29.81.60), NIC 2 (10.29.81.65)
Thanks again.
"Bharat Suneja [MSFT]" wrote:
> Correct.
>
> Additionally, Windows Server 2008 Failover Clustering *requires* two NICs.
> --
> Bharat Suneja
> Microsoft Corporation
> blog: exchangepedia.com/blog
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights. Please do not send email directly to this alias. This alias is for
> newsgroup purposes only.
> ----------------------------
>
>
>
>
> "Don Pedro" wrote in message
> news:EA98F40E-E0F0-43D1-993F-E619A288453E@microsoft.com...
> > OK, so I do need to add a default gateway to the heartbeat IPs for routing
> > purposes. I can then untick the "Allow clients to connect through the
> > network"
> >
> > Then I will have 2 NICs per node configured, since a single NIC cluster
> > node
> > violates a 'best practice', that being a single point of failure for
> > cluster
> > communications...and therefore, is not a supported configuration.
> >
> > Am I correct in this assumption?
> >
> >
> >
> > "Bharat Suneja [MSFT]" wrote:
> >
> >> - Windows Server 2008 Failover Clustering there are no Public or Private
> >> networks.
> >> - Failover Clustering automatically controls and configures network
> >> configuration. If a NIC has a default gateway, it will be used for
> >> public/client communications, unless you change the configuration
> >> (uncheck
> >> "Allow clients to connect through the network").
> >> - On Windows Server 2008 when both nodes sit on different IP subnets, you
> >> cannot *not have* a default gateway for network traffic (including
> >> cluster
> >> communications/heartbeat) to get to the other IP subnet.
> >> - The nature of heartbeat/cluster communications has changed from a UDP
> >> broadcast on port 3343 to a UDP unicast on the same port. Amongst other
> >> benefits, it allows cluster communication to cross routers.
> >>
> >> References:
> >> Core setup team blog:
> >> Multi-Site Failover Cluster Communications Connectivity
> >> http://blogs.technet.com/askcore/archive/2008/06/02/multi-site-failover-cluster-communications-connectivity.aspx
> >>
> >> Windows Server 2008 Failover Clustering White Papers:
> >> http://www.microsoft.com/downloads/details.aspx?familyid=75566F16-627D-4DD3-97CB-83909D3C722B&displaylang=en
> >>
> >> (Take a look at the white papers on multi-site cluster and WS08 Failover
> >> Clustering Architecture).
> >> --
> >> Bharat Suneja
> >> Microsoft Corporation
> >> blog: exchangepedia.com/blog
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights. Please do not send email directly to this alias. This alias is
> >> for
> >> newsgroup purposes only.
> >> ----------------------------
> >>
> >>
> >>
> >>
> >> "Don Pedro" wrote in message
> >> news:25CC1FE7-BEA2-4C5B-A577-359675B7C31F@microsoft.com...
> >> > Hi Edwin, thanks for your response.
> >> >
> >> > So are you saying when configuring the private network, we can add a
> >> > default
> >> > gateway? I thought this wasn't best practice since the Public NICs have
> >> > a
> >> > default gateway.
> >> >
> >> > For example, would the following be acceptable?
> >> >
> >> > Private NIC 01 - 10.0.31.70, Subnet 255.255.255.0, Default Gateway
> >> > 10.0.31.1
> >> > Private NIC 02 - 10.29.81.70, Subnet 255.255.255.0, Default Gateway
> >> > 10.29.81.70
> >> >
> >> > Sorry if I'm missing something. It's just from everything I have read
> >> > states
> >> > that you should configure the Private NICs with just an IP and subnet
> >> > mask
> >> > ONLY.
> >> >
> >> > Thanks again in advance,
> >> > Peter
> >> >
> >> > "Edwin vMierlo [MVP]" wrote:
> >> >
> >> >> With windows 2008 you can be on seperate subnets (eg routed
> >> >> networking)
> >> >>
> >> >> rgds,
> >> >> Edwin.
> >> >>
> >> >>
> >> >> "Don Pedro" wrote in message
> >> >> news:7042D216-541C-46F0-9A73-09FA4E3CAEBA@microsoft.com...
> >> >> > Hi,
> >> >> >
> >> >> > I am deploying a CCR on Windows Server 2008 using Exchange 2007 SP1.
> >> >> >
> >> >> > Each node is in a separate physical location and therefore on
> >> >> > different
> >> >> > switches.
> >> >> >
> >> >> > I am happy with my Public network config. I now need to configure
> >> >> > the
> >> >> > Private one.
> >> >> >
> >> >> > If I am supposed to configure the Private network with non-routable
> >> >> > IPs
> >> >> and
> >> >> > no default gateway, how are they expected to communicate? I asked my
> >> >> Network
> >> >> > guys and they are at a loss of how to set this up.
> >> >> >
> >> >> > Has someone done this and how was it achieved?
> >> >> >
> >> >> > Thanks,
> >> >> > Peter
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >>
> >>
> >>
>
>
date: Tue, 1 Jul 2008 08:40:01 -0700
author: Don Pedro
Re: CCR on Windows Server 2008 - Private Network Question
- Afaik, there's nothing to prevent it from being so.
- Additionally, if the traffic is going to cross that router to get to the
other node (on the second subnet), you'll need access to the same default
gateway - unless you're willing to make your network configuration a lot
more complicated. :)
- Finally, forget what you've learnt as far a Public and Private networks
go - these no longer exist. Really. Think of them as NICs over which both
cluster and client communication is enabled by default (if they have a
default gateway), but you can change the config to prevent client
connectivity (and allow only cluster communication).
Thanks for some good questions...
Windows Server 2008 Failover Clustering: No Public and Private networks?
http://exchangepedia.com/blog/2008/07/windows-server-2008-failover-clustering.html
--
Bharat Suneja
Microsoft Corporation
blog: exchangepedia.com/blog
This posting is provided "AS IS" with no warranties, and confers no
rights. Please do not send email directly to this alias. This alias is for
newsgroup purposes only.
----------------------------
"Don Pedro" wrote in message
news:DC87D11A-7AED-47F8-B34B-576C31332B67@microsoft.com...
> Oh, one last question.
>
> Can the second NIC of each node be on the same network as the first NIC.
>
> i.e. - NODE01 - NIC 1 (10.0.31.60), NIC 2 (10.0.31.65)
> NODE02 - NIC 1 (10.29.81.60), NIC 2 (10.29.81.65)
>
> Thanks again.
>
>
>
>
> "Bharat Suneja [MSFT]" wrote:
>
>> Correct.
>>
>> Additionally, Windows Server 2008 Failover Clustering *requires* two
>> NICs.
>> --
>> Bharat Suneja
>> Microsoft Corporation
>> blog: exchangepedia.com/blog
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights. Please do not send email directly to this alias. This alias is
>> for
>> newsgroup purposes only.
>> ----------------------------
>>
>>
>>
>>
>> "Don Pedro" wrote in message
>> news:EA98F40E-E0F0-43D1-993F-E619A288453E@microsoft.com...
>> > OK, so I do need to add a default gateway to the heartbeat IPs for
>> > routing
>> > purposes. I can then untick the "Allow clients to connect through the
>> > network"
>> >
>> > Then I will have 2 NICs per node configured, since a single NIC cluster
>> > node
>> > violates a 'best practice', that being a single point of failure for
>> > cluster
>> > communications...and therefore, is not a supported configuration.
>> >
>> > Am I correct in this assumption?
>> >
>> >
>> >
>> > "Bharat Suneja [MSFT]" wrote:
>> >
>> >> - Windows Server 2008 Failover Clustering there are no Public or
>> >> Private
>> >> networks.
>> >> - Failover Clustering automatically controls and configures network
>> >> configuration. If a NIC has a default gateway, it will be used for
>> >> public/client communications, unless you change the configuration
>> >> (uncheck
>> >> "Allow clients to connect through the network").
>> >> - On Windows Server 2008 when both nodes sit on different IP subnets,
>> >> you
>> >> cannot *not have* a default gateway for network traffic (including
>> >> cluster
>> >> communications/heartbeat) to get to the other IP subnet.
>> >> - The nature of heartbeat/cluster communications has changed from a
>> >> UDP
>> >> broadcast on port 3343 to a UDP unicast on the same port. Amongst
>> >> other
>> >> benefits, it allows cluster communication to cross routers.
>> >>
>> >> References:
>> >> Core setup team blog:
>> >> Multi-Site Failover Cluster Communications Connectivity
>> >> http://blogs.technet.com/askcore/archive/2008/06/02/multi-site-failover-cluster-communications-connectivity.aspx
>> >>
>> >> Windows Server 2008 Failover Clustering White Papers:
>> >> http://www.microsoft.com/downloads/details.aspx?familyid=75566F16-627D-4DD3-97CB-83909D3C722B&displaylang=en
>> >>
>> >> (Take a look at the white papers on multi-site cluster and WS08
>> >> Failover
>> >> Clustering Architecture).
>> >> --
>> >> Bharat Suneja
>> >> Microsoft Corporation
>> >> blog: exchangepedia.com/blog
>> >>
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights. Please do not send email directly to this alias. This alias is
>> >> for
>> >> newsgroup purposes only.
>> >> ----------------------------
>> >>
>> >>
>> >>
>> >>
>> >> "Don Pedro" wrote in message
>> >> news:25CC1FE7-BEA2-4C5B-A577-359675B7C31F@microsoft.com...
>> >> > Hi Edwin, thanks for your response.
>> >> >
>> >> > So are you saying when configuring the private network, we can add a
>> >> > default
>> >> > gateway? I thought this wasn't best practice since the Public NICs
>> >> > have
>> >> > a
>> >> > default gateway.
>> >> >
>> >> > For example, would the following be acceptable?
>> >> >
>> >> > Private NIC 01 - 10.0.31.70, Subnet 255.255.255.0, Default Gateway
>> >> > 10.0.31.1
>> >> > Private NIC 02 - 10.29.81.70, Subnet 255.255.255.0, Default Gateway
>> >> > 10.29.81.70
>> >> >
>> >> > Sorry if I'm missing something. It's just from everything I have
>> >> > read
>> >> > states
>> >> > that you should configure the Private NICs with just an IP and
>> >> > subnet
>> >> > mask
>> >> > ONLY.
>> >> >
>> >> > Thanks again in advance,
>> >> > Peter
>> >> >
>> >> > "Edwin vMierlo [MVP]" wrote:
>> >> >
>> >> >> With windows 2008 you can be on seperate subnets (eg routed
>> >> >> networking)
>> >> >>
>> >> >> rgds,
>> >> >> Edwin.
>> >> >>
>> >> >>
>> >> >> "Don Pedro" wrote in message
>> >> >> news:7042D216-541C-46F0-9A73-09FA4E3CAEBA@microsoft.com...
>> >> >> > Hi,
>> >> >> >
>> >> >> > I am deploying a CCR on Windows Server 2008 using Exchange 2007
>> >> >> > SP1.
>> >> >> >
>> >> >> > Each node is in a separate physical location and therefore on
>> >> >> > different
>> >> >> > switches.
>> >> >> >
>> >> >> > I am happy with my Public network config. I now need to configure
>> >> >> > the
>> >> >> > Private one.
>> >> >> >
>> >> >> > If I am supposed to configure the Private network with
>> >> >> > non-routable
>> >> >> > IPs
>> >> >> and
>> >> >> > no default gateway, how are they expected to communicate? I asked
>> >> >> > my
>> >> >> Network
>> >> >> > guys and they are at a loss of how to set this up.
>> >> >> >
>> >> >> > Has someone done this and how was it achieved?
>> >> >> >
>> >> >> > Thanks,
>> >> >> > Peter
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>>
>>
date: Tue, 1 Jul 2008 08:57:09 -0700
author: Bharat Suneja [MSFT]
Re: CCR on Windows Server 2008 - Private Network Question
Let me take that back. Both NICs do need to be on different networks.
My apologies for the confusion.
--
Bharat Suneja
Microsoft Corporation
blog: exchangepedia.com/blog
This posting is provided "AS IS" with no warranties, and confers no
rights. Please do not send email directly to this alias. This alias is for
newsgroup purposes only.
----------------------------
"Bharat Suneja [MSFT]" wrote in message
news:unmTfM52IHA.4500@TK2MSFTNGP06.phx.gbl...
>- Afaik, there's nothing to prevent it from being so.
> - Additionally, if the traffic is going to cross that router to get to the
> other node (on the second subnet), you'll need access to the same default
> gateway - unless you're willing to make your network configuration a lot
> more complicated. :)
> - Finally, forget what you've learnt as far a Public and Private networks
> go - these no longer exist. Really. Think of them as NICs over which both
> cluster and client communication is enabled by default (if they have a
> default gateway), but you can change the config to prevent client
> connectivity (and allow only cluster communication).
>
> Thanks for some good questions...
>
> Windows Server 2008 Failover Clustering: No Public and Private networks?
> http://exchangepedia.com/blog/2008/07/windows-server-2008-failover-clustering.html
>
> --
> Bharat Suneja
> Microsoft Corporation
> blog: exchangepedia.com/blog
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights. Please do not send email directly to this alias. This alias is for
> newsgroup purposes only.
> ----------------------------
>
>
>
>
> "Don Pedro" wrote in message
> news:DC87D11A-7AED-47F8-B34B-576C31332B67@microsoft.com...
>> Oh, one last question.
>>
>> Can the second NIC of each node be on the same network as the first NIC.
>>
>> i.e. - NODE01 - NIC 1 (10.0.31.60), NIC 2 (10.0.31.65)
>> NODE02 - NIC 1 (10.29.81.60), NIC 2 (10.29.81.65)
>>
>> Thanks again.
>>
>>
>>
>>
>> "Bharat Suneja [MSFT]" wrote:
>>
>>> Correct.
>>>
>>> Additionally, Windows Server 2008 Failover Clustering *requires* two
>>> NICs.
>>> --
>>> Bharat Suneja
>>> Microsoft Corporation
>>> blog: exchangepedia.com/blog
>>>
>>> This posting is provided "AS IS" with no warranties, and confers no
>>> rights. Please do not send email directly to this alias. This alias is
>>> for
>>> newsgroup purposes only.
>>> ----------------------------
>>>
>>>
>>>
>>>
>>> "Don Pedro" wrote in message
>>> news:EA98F40E-E0F0-43D1-993F-E619A288453E@microsoft.com...
>>> > OK, so I do need to add a default gateway to the heartbeat IPs for
>>> > routing
>>> > purposes. I can then untick the "Allow clients to connect through the
>>> > network"
>>> >
>>> > Then I will have 2 NICs per node configured, since a single NIC
>>> > cluster
>>> > node
>>> > violates a 'best practice', that being a single point of failure for
>>> > cluster
>>> > communications...and therefore, is not a supported configuration.
>>> >
>>> > Am I correct in this assumption?
>>> >
>>> >
>>> >
>>> > "Bharat Suneja [MSFT]" wrote:
>>> >
>>> >> - Windows Server 2008 Failover Clustering there are no Public or
>>> >> Private
>>> >> networks.
>>> >> - Failover Clustering automatically controls and configures network
>>> >> configuration. If a NIC has a default gateway, it will be used for
>>> >> public/client communications, unless you change the configuration
>>> >> (uncheck
>>> >> "Allow clients to connect through the network").
>>> >> - On Windows Server 2008 when both nodes sit on different IP subnets,
>>> >> you
>>> >> cannot *not have* a default gateway for network traffic (including
>>> >> cluster
>>> >> communications/heartbeat) to get to the other IP subnet.
>>> >> - The nature of heartbeat/cluster communications has changed from a
>>> >> UDP
>>> >> broadcast on port 3343 to a UDP unicast on the same port. Amongst
>>> >> other
>>> >> benefits, it allows cluster communication to cross routers.
>>> >>
>>> >> References:
>>> >> Core setup team blog:
>>> >> Multi-Site Failover Cluster Communications Connectivity
>>> >> http://blogs.technet.com/askcore/archive/2008/06/02/multi-site-failover-cluster-communications-connectivity.aspx
>>> >>
>>> >> Windows Server 2008 Failover Clustering White Papers:
>>> >> http://www.microsoft.com/downloads/details.aspx?familyid=75566F16-627D-4DD3-97CB-83909D3C722B&displaylang=en
>>> >>
>>> >> (Take a look at the white papers on multi-site cluster and WS08
>>> >> Failover
>>> >> Clustering Architecture).
>>> >> --
>>> >> Bharat Suneja
>>> >> Microsoft Corporation
>>> >> blog: exchangepedia.com/blog
>>> >>
>>> >> This posting is provided "AS IS" with no warranties, and confers no
>>> >> rights. Please do not send email directly to this alias. This alias
>>> >> is
>>> >> for
>>> >> newsgroup purposes only.
>>> >> ----------------------------
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> "Don Pedro" wrote in message
>>> >> news:25CC1FE7-BEA2-4C5B-A577-359675B7C31F@microsoft.com...
>>> >> > Hi Edwin, thanks for your response.
>>> >> >
>>> >> > So are you saying when configuring the private network, we can add
>>> >> > a
>>> >> > default
>>> >> > gateway? I thought this wasn't best practice since the Public NICs
>>> >> > have
>>> >> > a
>>> >> > default gateway.
>>> >> >
>>> >> > For example, would the following be acceptable?
>>> >> >
>>> >> > Private NIC 01 - 10.0.31.70, Subnet 255.255.255.0, Default Gateway
>>> >> > 10.0.31.1
>>> >> > Private NIC 02 - 10.29.81.70, Subnet 255.255.255.0, Default Gateway
>>> >> > 10.29.81.70
>>> >> >
>>> >> > Sorry if I'm missing something. It's just from everything I have
>>> >> > read
>>> >> > states
>>> >> > that you should configure the Private NICs with just an IP and
>>> >> > subnet
>>> >> > mask
>>> >> > ONLY.
>>> >> >
>>> >> > Thanks again in advance,
>>> >> > Peter
>>> >> >
>>> >> > "Edwin vMierlo [MVP]" wrote:
>>> >> >
>>> >> >> With windows 2008 you can be on seperate subnets (eg routed
>>> >> >> networking)
>>> >> >>
>>> >> >> rgds,
>>> >> >> Edwin.
>>> >> >>
>>> >> >>
>>> >> >> "Don Pedro" wrote in message
>>> >> >> news:7042D216-541C-46F0-9A73-09FA4E3CAEBA@microsoft.com...
>>> >> >> > Hi,
>>> >> >> >
>>> >> >> > I am deploying a CCR on Windows Server 2008 using Exchange 2007
>>> >> >> > SP1.
>>> >> >> >
>>> >> >> > Each node is in a separate physical location and therefore on
>>> >> >> > different
>>> >> >> > switches.
>>> >> >> >
>>> >> >> > I am happy with my Public network config. I now need to
>>> >> >> > configure
>>> >> >> > the
>>> >> >> > Private one.
>>> >> >> >
>>> >> >> > If I am supposed to configure the Private network with
>>> >> >> > non-routable
>>> >> >> > IPs
>>> >> >> and
>>> >> >> > no default gateway, how are they expected to communicate? I
>>> >> >> > asked my
>>> >> >> Network
>>> >> >> > guys and they are at a loss of how to set this up.
>>> >> >> >
>>> >> >> > Has someone done this and how was it achieved?
>>> >> >> >
>>> >> >> > Thanks,
>>> >> >> > Peter
>>> >> >> >
>>> >> >> >
>>> >> >>
>>> >> >>
>>> >> >>
>>> >>
>>> >>
>>>
>>>
>
date: Tue, 1 Jul 2008 09:48:05 -0700
author: Bharat Suneja [MSFT]
Re: CCR on Windows Server 2008 - Private Network Question
Thats great Bharat, thanks a million for all your help and time, you have
really helped me out a lot.
Peter
"Bharat Suneja [MSFT]" wrote:
> Let me take that back. Both NICs do need to be on different networks.
>
> My apologies for the confusion.
> --
> Bharat Suneja
> Microsoft Corporation
> blog: exchangepedia.com/blog
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights. Please do not send email directly to this alias. This alias is for
> newsgroup purposes only.
> ----------------------------
>
>
>
>
> "Bharat Suneja [MSFT]" wrote in message
> news:unmTfM52IHA.4500@TK2MSFTNGP06.phx.gbl...
> >- Afaik, there's nothing to prevent it from being so.
> > - Additionally, if the traffic is going to cross that router to get to the
> > other node (on the second subnet), you'll need access to the same default
> > gateway - unless you're willing to make your network configuration a lot
> > more complicated. :)
> > - Finally, forget what you've learnt as far a Public and Private networks
> > go - these no longer exist. Really. Think of them as NICs over which both
> > cluster and client communication is enabled by default (if they have a
> > default gateway), but you can change the config to prevent client
> > connectivity (and allow only cluster communication).
> >
> > Thanks for some good questions...
> >
> > Windows Server 2008 Failover Clustering: No Public and Private networks?
> > http://exchangepedia.com/blog/2008/07/windows-server-2008-failover-clustering.html
> >
> > --
> > Bharat Suneja
> > Microsoft Corporation
> > blog: exchangepedia.com/blog
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> > rights. Please do not send email directly to this alias. This alias is for
> > newsgroup purposes only.
> > ----------------------------
> >
> >
> >
> >
> > "Don Pedro" wrote in message
> > news:DC87D11A-7AED-47F8-B34B-576C31332B67@microsoft.com...
> >> Oh, one last question.
> >>
> >> Can the second NIC of each node be on the same network as the first NIC.
> >>
> >> i.e. - NODE01 - NIC 1 (10.0.31.60), NIC 2 (10.0.31.65)
> >> NODE02 - NIC 1 (10.29.81.60), NIC 2 (10.29.81.65)
> >>
> >> Thanks again.
> >>
> >>
> >>
> >>
> >> "Bharat Suneja [MSFT]" wrote:
> >>
> >>> Correct.
> >>>
> >>> Additionally, Windows Server 2008 Failover Clustering *requires* two
> >>> NICs.
> >>> --
> >>> Bharat Suneja
> >>> Microsoft Corporation
> >>> blog: exchangepedia.com/blog
> >>>
> >>> This posting is provided "AS IS" with no warranties, and confers no
> >>> rights. Please do not send email directly to this alias. This alias is
> >>> for
> >>> newsgroup purposes only.
> >>> ----------------------------
> >>>
> >>>
> >>>
> >>>
> >>> "Don Pedro" wrote in message
> >>> news:EA98F40E-E0F0-43D1-993F-E619A288453E@microsoft.com...
> >>> > OK, so I do need to add a default gateway to the heartbeat IPs for
> >>> > routing
> >>> > purposes. I can then untick the "Allow clients to connect through the
> >>> > network"
> >>> >
> >>> > Then I will have 2 NICs per node configured, since a single NIC
> >>> > cluster
> >>> > node
> >>> > violates a 'best practice', that being a single point of failure for
> >>> > cluster
> >>> > communications...and therefore, is not a supported configuration.
> >>> >
> >>> > Am I correct in this assumption?
> >>> >
> >>> >
> >>> >
> >>> > "Bharat Suneja [MSFT]" wrote:
> >>> >
> >>> >> - Windows Server 2008 Failover Clustering there are no Public or
> >>> >> Private
> >>> >> networks.
> >>> >> - Failover Clustering automatically controls and configures network
> >>> >> configuration. If a NIC has a default gateway, it will be used for
> >>> >> public/client communications, unless you change the configuration
> >>> >> (uncheck
> >>> >> "Allow clients to connect through the network").
> >>> >> - On Windows Server 2008 when both nodes sit on different IP subnets,
> >>> >> you
> >>> >> cannot *not have* a default gateway for network traffic (including
> >>> >> cluster
> >>> >> communications/heartbeat) to get to the other IP subnet.
> >>> >> - The nature of heartbeat/cluster communications has changed from a
> >>> >> UDP
> >>> >> broadcast on port 3343 to a UDP unicast on the same port. Amongst
> >>> >> other
> >>> >> benefits, it allows cluster communication to cross routers.
> >>> >>
> >>> >> References:
> >>> >> Core setup team blog:
> >>> >> Multi-Site Failover Cluster Communications Connectivity
> >>> >> http://blogs.technet.com/askcore/archive/2008/06/02/multi-site-failover-cluster-communications-connectivity.aspx
> >>> >>
> >>> >> Windows Server 2008 Failover Clustering White Papers:
> >>> >> http://www.microsoft.com/downloads/details.aspx?familyid=75566F16-627D-4DD3-97CB-83909D3C722B&displaylang=en
> >>> >>
> >>> >> (Take a look at the white papers on multi-site cluster and WS08
> >>> >> Failover
> >>> >> Clustering Architecture).
> >>> >> --
> >>> >> Bharat Suneja
> >>> >> Microsoft Corporation
> >>> >> blog: exchangepedia.com/blog
> >>> >>
> >>> >> This posting is provided "AS IS" with no warranties, and confers no
> >>> >> rights. Please do not send email directly to this alias. This alias
> >>> >> is
> >>> >> for
> >>> >> newsgroup purposes only.
> >>> >> ----------------------------
> >>> >>
> >>> >>
> >>> >>
> >>> >>
> >>> >> "Don Pedro" wrote in message
> >>> >> news:25CC1FE7-BEA2-4C5B-A577-359675B7C31F@microsoft.com...
> >>> >> > Hi Edwin, thanks for your response.
> >>> >> >
> >>> >> > So are you saying when configuring the private network, we can add
> >>> >> > a
> >>> >> > default
> >>> >> > gateway? I thought this wasn't best practice since the Public NICs
> >>> >> > have
> >>> >> > a
> >>> >> > default gateway.
> >>> >> >
> >>> >> > For example, would the following be acceptable?
> >>> >> >
> >>> >> > Private NIC 01 - 10.0.31.70, Subnet 255.255.255.0, Default Gateway
> >>> >> > 10.0.31.1
> >>> >> > Private NIC 02 - 10.29.81.70, Subnet 255.255.255.0, Default Gateway
> >>> >> > 10.29.81.70
> >>> >> >
> >>> >> > Sorry if I'm missing something. It's just from everything I have
> >>> >> > read
> >>> >> > states
> >>> >> > that you should configure the Private NICs with just an IP and
> >>> >> > subnet
> >>> >> > mask
> >>> >> > ONLY.
> >>> >> >
> >>> >> > Thanks again in advance,
> >>> >> > Peter
> >>> >> >
> >>> >> > "Edwin vMierlo [MVP]" wrote:
> >>> >> >
> >>> >> >> With windows 2008 you can be on seperate subnets (eg routed
> >>> >> >> networking)
> >>> >> >>
> >>> >> >> rgds,
> >>> >> >> Edwin.
> >>> >> >>
> >>> >> >>
> >>> >> >> "Don Pedro" wrote in message
> >>> >> >> news:7042D216-541C-46F0-9A73-09FA4E3CAEBA@microsoft.com...
> >>> >> >> > Hi,
> >>> >> >> >
> >>> >> >> > I am deploying a CCR on Windows Server 2008 using Exchange 2007
> >>> >> >> > SP1.
> >>> >> >> >
> >>> >> >> > Each node is in a separate physical location and therefore on
> >>> >> >> > different
> >>> >> >> > switches.
> >>> >> >> >
> >>> >> >> > I am happy with my Public network config. I now need to
> >>> >> >> > configure
> >>> >> >> > the
> >>> >> >> > Private one.
> >>> >> >> >
> >>> >> >> > If I am supposed to configure the Private network with
> >>> >> >> > non-routable
> >>> >> >> > IPs
> >>> >> >> and
> >>> >> >> > no default gateway, how are they expected to communicate? I
> >>> >> >> > asked my
> >>> >> >> Network
> >>> >> >> > guys and they are at a loss of how to set this up.
> >>> >> >> >
> >>> >> >> > Has someone done this and how was it achieved?
> >>> >> >> >
> >>> >> >> > Thanks,
> >>> >> >> > Peter
> >>> >> >> >
> >>> >> >> >
> >>> >> >>
> >>> >> >>
> >>> >> >>
> >>> >>
> >>> >>
> >>>
> >>>
> >
>
>
date: Wed, 2 Jul 2008 00:34:06 -0700
author: Don Pedro
|
|
