Re: Is this a bug?

Edwin vMierlo [MVP] wrote:
Sorry, I missed something. The key is not the failed of creating cluster.
The key is this failed caused some subnets could not visit the web
application.


Ok, well lets take this from the beginning:

If you have shared storage, do the following
- present 2 (minimum) disk from your shared storage to your cluster nodes
- install MSCS with a Shared Quorum on 1 of the disks
- test that you can fail-over the "Cluster Group" from and to all nodes
- test that you can connect to the "Cluster IP" using Cluster Administrator,
from and to all nodes
- create a new group called "Application Group" (or any other name you
desire)
- to this new group, add an IP address, Network Name and the remaining disk
- test that you can fail-over this new Application Group from and to all
nodes
- test that you can connect to both the IP and Network Name, from and to all
nodes

Once you have done that, install your Application in the Application group,
and test your application.
Your application must be configured to store any data, on the disk in the
application group.

If you do not have shared storage, and do not require shared storage, do the
following
- install MSCS with an MNS Quorum
- test that you can fail-over the "Cluster Group" from and to all nodes
- test that you can connect to the "Cluster IP" using Cluster Administrator,
from and to all nodes
- create a new group called "Application Group" (or any other name you
desire)
- to this new group, add an IP address, Network Name.
- test that you can fail-over this new Application Group from and to all
nodes
- test that you can connect to both the IP and Network Name, from and to all
nodes

Once you have done that, install your Application in the Application group,
and test your application.
(please note, your application cannot store any data anywhere, as you do not
have share storage. If you require your application to store data, then you
MUST have a shared storage disk to BOTH nodes, and create a Phisical Disk
resource in your Application Group)

Optionally, when you choose to run an MNS Quorum, and you have an even
number of cluster nodes, I would strongly recommend that you use a FSW
(Fileshare Witness).

The key here is that you have a fully working cluster, including networks
and proper quorum, before you attempt to install any applications.

HTH,
Edwin.





Ok, first what I want to know is not how to create a MS cluster. There are lots of documents about it.

I wanna to know why some subnets could not visit the web application after this failed. It lets me remembered Windows 2003 SP1 which caused the same issue.

Flybean
.

Relevant Pages

  • Re: cluster group
    ... All networks designated for cluster use on the node where the disk is online ... access the data that is stored on it (e.g. IP address, Network Name, File ... >> group to fail over. ...
    (microsoft.public.windows.server.clustering)
  • Re: Physical disk and cluster groups
    ... >> 2) The projects Group will need to have an IP Address and Network Name ... >> Cluster Group will fail over to the passive node, ... >> 3) When a disk or share fails, consider what you want to happen carefully. ...
    (microsoft.public.windows.server.clustering)
  • Re: Accessing Cluster Disks from a WEB Application
    ... Cluster Name ... Cluster Quorum Disk ... SQL Network Name ...
    (microsoft.public.windows.server.clustering)
  • Re: Physical disk and cluster groups
    ... >> 2) The projects Group will need to have an IP Address and Network Name ... >> Cluster Group will fail over to the passive node, ... >> 3) When a disk or share fails, consider what you want to happen carefully. ...
    (microsoft.public.windows.server.clustering)
  • Re: Physical disk and cluster groups
    ... We just have the one cluster group that has my cluster name and IP then everyone connects to that cluster name for their file shares. ... >> 2) The projects Group will need to have an IP Address and Network Name ... >> 3) When a disk or share fails, consider what you want to happen carefully. ...
    (microsoft.public.windows.server.clustering)