Re: Cannot Add Physical Disk Resource from Boot from SAN Node
- From: "Chuck Timon [Microsoft]" <ctimon@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 11 Sep 2006 09:04:53 -0400
It may be listed as an 'Approved Vendor" but is it listed as part of a
certified cluster soltuion on the cluster HCL? That is the critical part.
--
Chuck Timon, Jr.
Microsoft Corporation
Longhorn Readiness Team
This posting is provided "AS IS" with no
warranties, and confers no rights.
"Ken" <kenkwan@xxxxxxxxx> wrote in message
news:1157741530.948493.307490@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Chuck Timon [Microsoft] wrote:
"Compellent" as your storage vendor? I've been working with clustering
for
a while and I do not recognize that name so it is probably not part of an
HCL cluster soltuion.
However, you can create the physical disk resource on one of the other
nodes
and then try failing it over to Node 4 and see what happens.
--
Chuck Timon, Jr.
Microsoft Corporation
Longhorn Readiness Team
This posting is provided "AS IS" with no
warranties, and confers no rights.
"Ken" <kenkwan@xxxxxxxxx> wrote in message
news:1157670560.443267.161410@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have a 3-node 2003 cluster that is currently setup for local boot
attached via fibre channel to a SAN. Everything is working fine.
I have added a 4th boot from SAN node using a single FC HBA. All
hardware is identical. Node4 is joined to the cluster and is recognized
as a member node.
I have created a new virtual server and assigned it a name and IP
address. This VS functions normally and can be moved between all
cluster nodes.
When I create a new volume and map it to all cluster nodes, I cannot
create a cluster physical disk resource for this volume on Node4. The
Disk Parameters field is blank. If I try to create the same physical
disk resource on Node3, it works as expected.
Note that the disk is recognized in Disk Administrator on Node4 as
expected.
I have applied the registry fix noted in the MS KB article:
http://support.microsoft.com/kb/886569
All FC HBAs are running the latest Storport drivers.
My storage vendor (Compellent) has confirmed that a single HBA
configuration is tested and working in their lab.
Any ideas how to create this resource?
Thanks,
Ken
Yes, the node was rebooted after the registry fix was applied.
Creating the disk resource on the non-boot from SAN volume works
normally and I can fail it over to the boot from SAN node. The problem
I am having is creating a new disk resource using the boot from SAN
node.
Our intention is to move all of the cluster nodes to boot from SAN so
creating all the resources on the local-boot servers is not an option
and does not really address the problem I am having.
Using a single FC HBA to access both the boot volume and cluster data
should not be an issue, should it?
Compellent is listed as an approved vendor on the MS HCL.
.
- References:
- Cannot Add Physical Disk Resource from Boot from SAN Node
- From: Ken
- Re: Cannot Add Physical Disk Resource from Boot from SAN Node
- From: Chuck Timon [Microsoft]
- Re: Cannot Add Physical Disk Resource from Boot from SAN Node
- From: Ken
- Cannot Add Physical Disk Resource from Boot from SAN Node
- Prev by Date: Re: Running CHKDSK on shared cluster volumes on a SAN
- Next by Date: Re: Size and number of shared cluster volumes
- Previous by thread: Re: Cannot Add Physical Disk Resource from Boot from SAN Node
- Next by thread: W2K3 Cluster, cannot start the 50th generic apps (49 working good)
- Index(es):
Relevant Pages
|
