Re: Checking that all nodes have access to the quorum resource!

I'll doubt check to see if the system fails over when our user go to lunch.
However, is there a way to fix this issue? Is there a problem with either
machines registry?

Scott

"Jeff Hughes [MSFT]" wrote:

The reason it's happening is that the target ID and LUN may not necessarily
match from one node to another so the cluster thinks it's a different disk.
As long as the join succeeds and failover of that disk(s) work, you are good
to go.

We've documented this in:

331801 Cluster setup may not work when you add nodes
http://support.microsoft.com/default.aspx?scid=kb;EN-US;331801

--
Jeff Hughes, MCSE
Support Escalation Engineer
Microsoft Enterprise Platforms Support (Server Core/Cluster)

"scott" <scott@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5704C71F-B8DB-4C88-89D5-66D2113268B9@xxxxxxxxxxxxxxxx
Hi... thanks for the fast reply


I tried that, and for the most part it joins the cluster fine. The errors
still show up in the log file, but it joins! But, why is it happening?
When
the system was installed, several months ago, we have an small problem
that
required us to remove a node from the cluster. When we brought the node
back
in, it didn't have any errors.

Scott





"Jeff Hughes [MSFT]" wrote:

When you do the install, at the point you sepcify the node to join,
select
the [Advanced] option and bypass the storage check. I think it's
something
like 'Advanced minimum'.
--
Jeff Hughes, MCSE
Support Escalation Engineer
Microsoft Enterprise Platforms Support (Server Core/Cluster)

"scott" <scott@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3C56F7BD-DC56-44CF-8590-CFE5EC49AE77@xxxxxxxxxxxxxxxx
Hi,

I have two machines that were apart of a cluster (simply named NODE1
and
NODE2). Node1 had a operating system problem that brought the machine
down,
in a non-graceful manner, and needed to be reloaded. Both machines
have
2003
enterprise with service pack 2 installed and we are using MS ISCSI. At
this
point NODE1 is back up and running, but is unable to join the cluster
(see
log file). NODE1 seems to be having a problem seeing the quorum
drive.
Also, if we attempt to join the cluster from NODE1 or NODE2 (which is
the
only member) we get the same results.

Tests: Both machines have NIC cards up and running correctly and are
able
to ping each other the remote storage, which contains the quorum drive.

TAIL END OF THE LOG FILE WITH THE PROBLEM
*
* 2006-12-12 18:23:39.062 (HSMC\administrator)
*
2007-05-18 07:40:49.437 [INFO] CLUSTER: The quorum resource is
"Disk:X".
(hr=00000000, {102439CC-67FA-48A6-AB0D-31DF047FC5E6},
{88407BE5-26A3-46F6-9636-A26BDAECC5D6}, 1, 1, 1), (null)
2007-05-18 07:40:49.437 [INFO] [MT] The cluster managed resource has no
support for IClusCfgManagedResourceData.
2007-05-18 07:40:49.453 [INFO] [MT] Matched resource 'Local Quorum'
('Local
Quorum') from node 'NODE1.hsmc.local' with 'Local Quorum' ('Local
Quorum')
on
cluster node 'node2.hsmc.local'.
2007-05-18 07:40:49.453 [INFO] [MT] Matched resource 'Majority Node
Set'
('Majority Node Set') from node 'NODE1.hsmc.local' with 'Majority Node
Set'
('Majority Node Set') on cluster node 'node2.hsmc.local'.
2007-05-18 07:40:49.453 [INFO] [MT] The cluster managed resource has no
support for IClusCfgManagedResourceData.
2007-05-18 07:40:49.453 [INFO] [MT] Matched resource 'Unknown Quorum'
('Unknown Quorum') from node 'NODE1.hsmc.local' with 'Unknown Quorum'
('Unknown Quorum') on cluster node 'node2.hsmc.local'.
2007-05-18 07:40:49.453 [INFO] CLUSTER: Comparing the resources between
the
cluster and the nodes being added... (hr=00000000,
{EBC8AEFF-10C3-4D5B-AC17-FC0F4C3871B7},
{102439CC-67FA-48A6-AB0D-31DF047FC5E6}, 0, 1, 1), (null)
2007-05-18 07:40:49.453 [INFO] CLUSTER: (null) (hr=00000000,
{FDC75680-7DBB-42CA-8003-E4CDB01FF062},
{EBC8AEFF-10C3-4D5B-AC17-FC0F4C3871B7}, 0, 8, 6), (null)
2007-05-18 07:40:49.468 [INFO] CLUSTER: Comparing the networks in the
cluster with the networks on the nodes... (hr=00000000,
{EBC8AEFF-10C3-4D5B-AC17-FC0F4C3871B7},
{A209EF1D-7C2F-451C-99D9-42A5E00F3028}, 0, 1, 0), (null)
2007-05-18 07:40:49.468 [INFO] [OM] Found an existing cookie for object
'10.0.0.0'
2007-05-18 07:40:49.468 [INFO] [OM] Found an existing cookie for object
'192.168.1.0'
2007-05-18 07:40:49.468 [INFO] [OM] Found an existing cookie for object
'192.168.0.0'
2007-05-18 07:40:49.468 [INFO] [OM] Found an existing cookie for object
'192.168.21.0'
2007-05-18 07:40:49.468 [INFO] CLUSTER: Comparing the networks in the
cluster with the networks on the nodes... (hr=00000000,
{EBC8AEFF-10C3-4D5B-AC17-FC0F4C3871B7},
{A209EF1D-7C2F-451C-99D9-42A5E00F3028}, 0, 1, 1), (null)
2007-05-18 07:40:49.484 [INFO] CLUSTER: (null) (hr=00000000,
{FDC75680-7DBB-42CA-8003-E4CDB01FF062},
{EBC8AEFF-10C3-4D5B-AC17-FC0F4C3871B7}, 0, 8, 7), (null)
2007-05-18 07:40:49.484 [INFO] CLUSTER: Checking that all nodes have
access
to the quorum resource... (hr=00000000,
{EBC8AEFF-10C3-4D5B-AC17-FC0F4C3871B7},
{B8C4066E-0246-4358-9DE5-25603EDD0CA0}, 0, 3, 0), (null)
2007-05-18 07:40:49.484 [INFO] CLUSTER: Checking that all nodes have
access
to the quorum resource... (hr=00000000,
{EBC8AEFF-10C3-4D5B-AC17-FC0F4C3871B7},
{B8C4066E-0246-4358-9DE5-25603EDD0CA0}, 0, 3, 1), (null)
2007-05-18 07:40:49.484 [INFO] CLUSTER: The following nodes cannot not
verify that they can host the quorum resource... (hr=00000000,
{B8C4066E-0246-4358-9DE5-25603EDD0CA0},
{A976DC09-0108-410A-AF57-68C05F9A42F7}, 1, 1, 1), (null)
2007-05-18 07:40:49.500 [ERR ] CLUSTER: Could not verify that node
"NODE1.hsmc.local" can host the quorum resource. (hr=0x800713de,
{A976DC09-0108-410A-AF57-68C05F9A42F7},
{DAD63EA8-7B7D-4771-9E27-AA763775F6BD}, 1, 1, 1), Ensure that your
hardware
is properly configured and that all nodes have access to a
quorum-capable
resource.
2007-05-18 07:40:49.531 [INFO] CLUSTER: Checking that all nodes have
access
to the quorum resource... (hr=00000000,
{EBC8AEFF-10C3-4D5B-AC17-FC0F4C3871B7},
{B8C4066E-0246-4358-9DE5-25603EDD0CA0}, 0, 3, 2), (null)
2007-05-18 07:40:49.562 [ERR ] CLUSTER: A multi-node cluster cannot be
created because there is not a quorum-capable resource common to all
nodes.
(hr=0x800713de, {B8C4066E-0246-4358-9DE5-25603EDD0CA0},
{3BB53C9E-E14A-4196-9066-5400FB8860C9}, 0, 1, 1), In some complex
storage
solutions, such as a fiber channel switched fabric, a particular
storage
unit
might have a different identity (Target ID and/or LUN) on each computer
in
the cluster. Although this is a valid storage configuration, it
violates
the
storage validation heuristics in the Add Nodes Wizard when using the
default
Typical (full) configuration option, resulting in an error.

To avoid this error, first verify that your storage configuration is
set
up
correctly. Next, disable the storage validation heuristics by using the
Back
button to return to the Select Computer page. Then, on the Select
Computer
page, click the Advanced button, and select the Advanced (minimum)
configuration option.

For more information on the Advanced and Typical configuration options,
see
"Storage config
2007-05-18 07:40:49.578 [INFO] [WIZ] Ignoring invalid progress -- min,
max
or current are invalid. new min = 0, prev min = 0, new max = 1, prev
max =
1,
new current = 1, prev current = 1
2007-05-18 07:40:49.609 [ERR ] CLUSTER: Checking that all nodes have
access
to the quorum resource... (hr=0x800713de,
{EBC8AEFF-10C3-4D5B-AC17-FC0F4C3871B7},
{B8C4066E-0246-4358-9DE5-25603EDD0CA0}, 0, 3, 3), (null)
2007-05-18 07:40:49.625 [ERR ] CLUSTER: (null) (hr=0x800713de,
{FDC75680-7DBB-42CA-8003-E4CDB01FF062},
{EBC8AEFF-10C3-4D5B-AC17-FC0F4C3871B7}, 0, 8, 8), (null)
2007-05-18 07:40:49.656 [INFO] [MT] [CTaskAnalyzeClusterBase] Exiting
task.
The task was not cancelled.




.

Loading