"Debbie" <Debbie@discussions.microsoft.com> wrote in message
news:89B546EC-247D-464E-A149-6952D4AC5EC7@microsoft.com...
> There are three NICs, the heartbeat (crossover), private (for backups) and
> our intranet. All three have the exclamation mark.
>
> "Ayad" wrote:
>
> > Is the NIC you have exclamation mark on Public or Private network?
> >
> > Ayad
> >
> > "Debbie" <Debbie@discussions.microsoft.com> wrote in message
> > news:1CC9F5E6-46E3-482A-913C-B8C57692BDB2@microsoft.com...
> > > I am running a 2-node cluster for SQL Server. After powering down both
> > > servers (passive then active), one of the nodes did not successfully
join
> > the
> > > cluster. This node shows exclamation marks on the Network Interfaces
in
> > > Cluster Administrator. These nics are functioning correctly outside
of
> > the
> > > cluster. The cluster log on the failed node indicates that these
network
> > > interfaces are functioning each time it tries to join the cluster.
The
> > > active node's cluster log indicates that these resources are not
> > functioning
> > > and removes the other node from being active.
> > >
> > > If anyone has any ideas on how to solve this problem, your input would
be
> > > greatly appreciated.
> > > Thanks,
> > > Debbie
> > >
> >
> >
> >

"Debbie" <Debbie@discussions.microsoft.com> wrote in message
news:9AA7AFAC-5A77-4A71-B901-9CB4E99462ED@microsoft.com...
> Ayad,
>
> This is not a new install. It was working before. We had to power down
all
> of the servers for a generator hook-up to be installed. When bringing the
> cluster back up, this server failed and has failed ever since with these
NIC
> resource errors.
>
> The subnets look good on the NICs.
>
> Thanks,
> Debbie
>
> "Ayad" wrote:
>
> > Check your IP settings and make sure you are using the correct subnet
mask
> > address and network segment for each port and match each port with the
other
> > node's port.
> >
> > Was it working before or this is a new install?
> >
> > Ayad
> >
> > "Debbie" <Debbie@discussions.microsoft.com> wrote in message
> > news:89B546EC-247D-464E-A149-6952D4AC5EC7@microsoft.com...
> > > There are three NICs, the heartbeat (crossover), private (for backups)
and
> > > our intranet. All three have the exclamation mark.
> > >
> > > "Ayad" wrote:
> > >
> > > > Is the NIC you have exclamation mark on Public or Private network?
> > > >
> > > > Ayad
> > > >
> > > > "Debbie" <Debbie@discussions.microsoft.com> wrote in message
> > > > news:1CC9F5E6-46E3-482A-913C-B8C57692BDB2@microsoft.com...
> > > > > I am running a 2-node cluster for SQL Server. After powering down
both
> > > > > servers (passive then active), one of the nodes did not
successfully
> > join
> > > > the
> > > > > cluster. This node shows exclamation marks on the Network
Interfaces
> > in
> > > > > Cluster Administrator. These nics are functioning correctly
outside
> > of
> > > > the
> > > > > cluster. The cluster log on the failed node indicates that these
> > network
> > > > > interfaces are functioning each time it tries to join the cluster.
> > The
> > > > > active node's cluster log indicates that these resources are not
> > > > functioning
> > > > > and removes the other node from being active.
> > > > >
> > > > > If anyone has any ideas on how to solve this problem, your input
would
> > be
> > > > > greatly appreciated.
> > > > > Thanks,
> > > > > Debbie
> > > > >
> > > >
> > > >
> > > >
> >
> >
> >

"Ayad" wrote:

> Debbie,
>
> Try Shutdown that node (server hard reboot) and power it ON again and see if
> it clears your NIC issue.
>
> Ayad
>
> "Debbie" <Debbie@discussions.microsoft.com> wrote in message
> news:9AA7AFAC-5A77-4A71-B901-9CB4E99462ED@microsoft.com...
> > Ayad,
> >
> > This is not a new install. It was working before. We had to power down
> all
> > of the servers for a generator hook-up to be installed. When bringing the
> > cluster back up, this server failed and has failed ever since with these
> NIC
> > resource errors.
> >
> > The subnets look good on the NICs.
> >
> > Thanks,
> > Debbie
> >
> > "Ayad" wrote:
> >
> > > Check your IP settings and make sure you are using the correct subnet
> mask
> > > address and network segment for each port and match each port with the
> other
> > > node's port.
> > >
> > > Was it working before or this is a new install?
> > >
> > > Ayad
> > >
> > > "Debbie" <Debbie@discussions.microsoft.com> wrote in message
> > > news:89B546EC-247D-464E-A149-6952D4AC5EC7@microsoft.com...
> > > > There are three NICs, the heartbeat (crossover), private (for backups)
> and
> > > > our intranet. All three have the exclamation mark.
> > > >
> > > > "Ayad" wrote:
> > > >
> > > > > Is the NIC you have exclamation mark on Public or Private network?
> > > > >
> > > > > Ayad
> > > > >
> > > > > "Debbie" <Debbie@discussions.microsoft.com> wrote in message
> > > > > news:1CC9F5E6-46E3-482A-913C-B8C57692BDB2@microsoft.com...
> > > > > > I am running a 2-node cluster for SQL Server. After powering down
> both
> > > > > > servers (passive then active), one of the nodes did not
> successfully
> > > join
> > > > > the
> > > > > > cluster. This node shows exclamation marks on the Network
> Interfaces
> > > in
> > > > > > Cluster Administrator. These nics are functioning correctly
> outside
> > > of
> > > > > the
> > > > > > cluster. The cluster log on the failed node indicates that these
> > > network
> > > > > > interfaces are functioning each time it tries to join the cluster.
> > > The
> > > > > > active node's cluster log indicates that these resources are not
> > > > > functioning
> > > > > > and removes the other node from being active.
> > > > > >
> > > > > > If anyone has any ideas on how to solve this problem, your input
> would
> > > be
> > > > > > greatly appreciated.
> > > > > > Thanks,
> > > > > > Debbie
> > > > > >
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>