Re: URGENT: Unable to view quorum or data drives on attached SAN

[MarvinC]

I realized that I did forget to configure the Initiator settings on the
second server and I did get an error during the install of the 2nd node at
"checking cluster feasibility". I've already "evicted" that 2nd node and
from the looks of it will need to start over. Is there a documented process
for removing the cluster instance and starting over? I see the old cluster
names when creating a new one wantd to try to delete it.

Thanks




On Tue, Jul 29, 2008 at 4:39 PM, Ziots, Edward <[EMAIL PROTECTED]> wrote:

>  The code is a network path can't be found.
>
>
>
> Are you sure you zoned your disk to both servers?  It looks like an issue
> with the transference of the disk itself to the 2nd cluster.  ( Did you
> setup the cluster accordingly)
>
> Power down 2nd server, power up first server and disk build first node,
> bring up second node and then add that node to the cluster?) The use the
> default cluster group and disk groups for your LUN and similate failover
> accordingly?
>
>
>
> What you could do is evict the 2nd node, and rejoin it, and just have
> regular disk groups and fail them over to each node ( NO SQL no MSDTC) and
> verify that the groups and there associated disk fail to the nodes
> accordingly.
>
>
>
> Did you receive any errors from the cluster setup gui when adding the 2ndnode 
> to the cluster?
>
>
>
> Z
>
> Edward E. Ziots
>
> Network Engineer
>
> Lifespan Organization
>
> MCSE,MCSA,MCP,Security+,Network+,CCA
>
> Phone: 401-639-3505
>  --------------
>
> *From:* MarvinC [mailto:[EMAIL PROTECTED]
> *Sent:* Tuesday, July 29, 2008 4:13 PM
> *To:* NT System Admin Issues
> *Subject:* URGENT: Unable to view quorum or data drives on attached SAN
>
>
>
>
>
>

~ Upgrade to Next Generation Antispam/Antivirus with Ninja!~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~

RE: URGENT: Unable to view quorum or data drives on attached SAN

[Ziots, Edward]

The code is a network path can't be found. 

 

Are you sure you zoned your disk to both servers?  It looks like an
issue with the transference of the disk itself to the 2nd cluster.  (
Did you setup the cluster accordingly)

Power down 2nd server, power up first server and disk build first node,
bring up second node and then add that node to the cluster?) The use the
default cluster group and disk groups for your LUN and similate failover
accordingly?

 

What you could do is evict the 2nd node, and rejoin it, and just have
regular disk groups and fail them over to each node ( NO SQL no MSDTC)
and verify that the groups and there associated disk fail to the nodes
accordingly. 

 

Did you receive any errors from the cluster setup gui when adding the
2nd node to the cluster? 

 

Z

Edward E. Ziots

Network Engineer

Lifespan Organization

MCSE,MCSA,MCP,Security+,Network+,CCA

Phone: 401-639-3505



From: MarvinC [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, July 29, 2008 4:13 PM
To: NT System Admin Issues
Subject: URGENT: Unable to view quorum or data drives on attached SAN

 

 


~ Upgrade to Next Generation Antispam/Antivirus with Ninja!~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~

URGENT: Unable to view quorum or data drives on attached SAN

[MarvinC]

I've got a JetStor416iS that's attached to an HP c700 blade chassis filled
with BL465 G1 blades. I've set up MS Clustering on the two blades and can
view them in Cluster Administrator. I've also set up my groups including
an MSDTC resource. Here are my problems:
1. I can't see any of the shared drives, including the quorum from my 2nd
server and when simulating a failover by taking the first server offline the
Cluster services stops. It doesn't fail over to the 2nd server and insteads
returns the following errors:

The Cluster Service on node 'server1' cannot be started.
The network ath was not found.
Error ID: -2147024843 (80070035)

An error occurred attempting to open the cluster at 'server-cluster'.
The network path was not found.
Error ID: -2147024843 (80070035)

I am setting this up to build a SQL cluster and the crazy is that I had all
of this working before having to rebuild and attached to a different storage
solution. Any feedback or direction on resolving this is greatly
appreciated.

~ Upgrade to Next Generation Antispam/Antivirus with Ninja!~
~   ~