MNS with FSW and Priviate Heartbeat Network

I have configured a two node MNS cluster with a file share witness. It all
works fine until I configure the networking as per a traditional cluser ie.
One nic connected to the switched n/w for public and one nic connected to the
other node via a crossover as private.

Now the cluster seems to hang when I fail over the quorum and I cannont
start the cluster service on either node. The cluster log has the following
entries:

000003a4.000003dc::2007/02/20-00:34:35.325 ERR Majority Node Set <Majority
Node Set>:
CreateTreeConnection(192.1.1.2\d8a922ed-3367-46a5-9c60-6b3038c6bae1$)
returned 0xc00000be hdl 0xffffffff

000003a4.00000fb8::2007/02/20-00:34:39.419 ERR Majority Node Set <Majority
Node Set>:
CreateTreeConnection(192.1.1.1\d8a922ed-3367-46a5-9c60-6b3038c6bae1$)
returned 0xc00000bc hdl 0xffffffff


My question is whether the cluster is trying to contact the fsw over the
private lan and if you need to configure the networking differently with the
fsw.

Any help would be appriciated.

Regards

Dave

FSW has nothing to do with the networking piece it only counts as a 'vote'
to help achieve 'Majority'. For an MNS cluster, please ensure you have File
and Print Sharing enabled.

Chuck Timon, Jr.
Microsoft Corporation
Longhorn Readiness Team
This posting is provided "AS IS" with no warranties, and confers no rights.



"David G" <> wrote in message
news:66A53722-925F-48EA-B96D-...
>I have configured a two node MNS cluster with a file share witness. It all
> works fine until I configure the networking as per a traditional cluser
> ie.
> One nic connected to the switched n/w for public and one nic connected to
> the
> other node via a crossover as private.
>
> Now the cluster seems to hang when I fail over the quorum and I cannont
> start the cluster service on either node. The cluster log has the
> following
> entries:
>
> 000003a4.000003dc::2007/02/20-00:34:35.325 ERR Majority Node Set
> <Majority
> Node Set>:
> CreateTreeConnection(192.1.1.2\d8a922ed-3367-46a5-9c60-6b3038c6bae1$)
> returned 0xc00000be hdl 0xffffffff
>
> 000003a4.00000fb8::2007/02/20-00:34:39.419 ERR Majority Node Set
> <Majority
> Node Set>:
> CreateTreeConnection(192.1.1.1\d8a922ed-3367-46a5-9c60-6b3038c6bae1$)
> returned 0xc00000bc hdl 0xffffffff
>
>
> My question is whether the cluster is trying to contact the fsw over the
> private lan and if you need to configure the networking differently with
> the
> fsw.
>
> Any help would be appriciated.
>
> Regards
>
> Dave

0xc00000be = The network path cannot be located. You might want to check on
your FSW configuration and make sure that it's set properly.

Regards,
John


"David G" <> wrote in message
news:66A53722-925F-48EA-B96D-...
> I have configured a two node MNS cluster with a file share witness. It
all
> works fine until I configure the networking as per a traditional cluser
ie.
> One nic connected to the switched n/w for public and one nic connected to
the
> other node via a crossover as private.
>
> Now the cluster seems to hang when I fail over the quorum and I cannont
> start the cluster service on either node. The cluster log has the
following
> entries:
>
> 000003a4.000003dc::2007/02/20-00:34:35.325 ERR Majority Node Set
<Majority
> Node Set>:
> CreateTreeConnection(192.1.1.2\d8a922ed-3367-46a5-9c60-6b3038c6bae1$)
> returned 0xc00000be hdl 0xffffffff
>
> 000003a4.00000fb8::2007/02/20-00:34:39.419 ERR Majority Node Set
<Majority
> Node Set>:
> CreateTreeConnection(192.1.1.1\d8a922ed-3367-46a5-9c60-6b3038c6bae1$)
> returned 0xc00000bc hdl 0xffffffff
>
>
> My question is whether the cluster is trying to contact the fsw over the
> private lan and if you need to configure the networking differently with
the
> fsw.
>
> Any help would be appriciated.
>
> Regards
>
> Dave

The 192.x.x.x is the private network consisting of a crossover cable between
the two nodes, clearly the FSW is not on this network. My question is
whether this configuration is appropriate for a FSW cluster.

"John Toner [MVP]" wrote:

> 0xc00000be = The network path cannot be located. You might want to check on
> your FSW configuration and make sure that it's set properly.
>
> Regards,
> John
>
>
> "David G" <> wrote in message
> news:66A53722-925F-48EA-B96D-...
> > I have configured a two node MNS cluster with a file share witness. It
> all
> > works fine until I configure the networking as per a traditional cluser
> ie.
> > One nic connected to the switched n/w for public and one nic connected to
> the
> > other node via a crossover as private.
> >
> > Now the cluster seems to hang when I fail over the quorum and I cannont
> > start the cluster service on either node. The cluster log has the
> following
> > entries:
> >
> > 000003a4.000003dc::2007/02/20-00:34:35.325 ERR Majority Node Set
> <Majority
> > Node Set>:
> > CreateTreeConnection(192.1.1.2\d8a922ed-3367-46a5-9c60-6b3038c6bae1$)
> > returned 0xc00000be hdl 0xffffffff
> >
> > 000003a4.00000fb8::2007/02/20-00:34:39.419 ERR Majority Node Set
> <Majority
> > Node Set>:
> > CreateTreeConnection(192.1.1.1\d8a922ed-3367-46a5-9c60-6b3038c6bae1$)
> > returned 0xc00000bc hdl 0xffffffff
> >
> >
> > My question is whether the cluster is trying to contact the fsw over the
> > private lan and if you need to configure the networking differently with
> the
> > fsw.
> >
> > Any help would be appriciated.
> >
> > Regards
> >
> > Dave
>
>
>

Sure, in a 2-Node MNS cluster, if one node goes down, the FSW will keep the
apps\services highly available with the one remaining node provided it can
get to the file share.

Chuck Timon, Jr.
Microsoft Corporation
Longhorn Readiness Team
This posting is provided "AS IS" with no warranties, and confers no rights.

"David G" <> wrote in message
news:B0E85447-CF62-4E22-BD57-...
> The 192.x.x.x is the private network consisting of a crossover cable
> between
> the two nodes, clearly the FSW is not on this network. My question is
> whether this configuration is appropriate for a FSW cluster.
>
> "John Toner [MVP]" wrote:
>
>> 0xc00000be = The network path cannot be located. You might want to check
>> on
>> your FSW configuration and make sure that it's set properly.
>>
>> Regards,
>> John
>>
>>
>> "David G" <> wrote in message
>> news:66A53722-925F-48EA-B96D-...
>> > I have configured a two node MNS cluster with a file share witness. It
>> all
>> > works fine until I configure the networking as per a traditional cluser
>> ie.
>> > One nic connected to the switched n/w for public and one nic connected
>> > to
>> the
>> > other node via a crossover as private.
>> >
>> > Now the cluster seems to hang when I fail over the quorum and I cannont
>> > start the cluster service on either node. The cluster log has the
>> following
>> > entries:
>> >
>> > 000003a4.000003dc::2007/02/20-00:34:35.325 ERR Majority Node Set
>> <Majority
>> > Node Set>:
>> > CreateTreeConnection(192.1.1.2\d8a922ed-3367-46a5-9c60-6b3038c6bae1$)
>> > returned 0xc00000be hdl 0xffffffff
>> >
>> > 000003a4.00000fb8::2007/02/20-00:34:39.419 ERR Majority Node Set
>> <Majority
>> > Node Set>:
>> > CreateTreeConnection(192.1.1.1\d8a922ed-3367-46a5-9c60-6b3038c6bae1$)
>> > returned 0xc00000bc hdl 0xffffffff
>> >
>> >
>> > My question is whether the cluster is trying to contact the fsw over
>> > the
>> > private lan and if you need to configure the networking differently
>> > with
>> the
>> > fsw.
>> >
>> > Any help would be appriciated.
>> >
>> > Regards
>> >
>> > Dave
>>
>>
>>

Had the same problem as described above.
Found that the Hosts had incorrect Network Priority for internal cluster communications. Public instead of the private. Also found that the hosts were using 2 multihomed NICs and for the public network which we had 2 of, they weren't matching up with the initially assigned networks that we had allocated to cluster.

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com