Install Windows 2000 Cluster Services: Installing the Windows 2000 Cluster Service: Node 1

16) This screen is informational only. It recommends that besides the public network used to access the cluster by clients, that you also have a private network that can be used by the nodes in the cluster to communicate. This is the approach we will take here. After reading the message, click “Next,” and the following screen appears. 

17) The Cluster Configuration Wizard is now asking you to specify which network card to use for the Private Network in the cluster. Note that the “Network name” above is “Private Network.” It is named this because when we originally configured the private network card, we give this connection the name “Private Network.” We did this to make this step in the Cluster Server configuration process easier.

Be sure that the checkbox next to “Enable this network for cluster use” is selected. This must be selected; otherwise the cluster would not use this network card.

Under the option, “This network performs the following role in the cluster,” the radio button next to “Internal cluster communications only (private network) is selected. This means that the internal network can only be used by cluster service, which is the only option that makes sense.

Note that this screen will appear for every network card in your server. In most cases, such as this one, there are only two network cards in the server, and so this screen will only appear twice, as shown next.

Once all the options are set, click “Next,” and this screen appears:

18) This is similar to the previous screen, but now, we are configuring the public network. Under “Network name,” the name “Public Network” is there because that is the name we gave it when we configured this network card when we installed Windows 2000. “Enable this network for cluster use” must be selected.

Under the option, “This network performs the following role in the cluster,” the radio button next to “All communications (mixed network) is selected. Although you could choose “Client access only (public network), we chose “All communications (mixed network) instead because this provides additional redundancy should the private network fail. For example, since this option is selected, should the private network fail, Cluster Service will still be able to communicate via the public network if need be.

Once all the options are set, click “Next,” and this screen appears:

19) Because we specified that the Public Network was mixed, the Cluster Configuration Wizard needs to know which network should be used as the primary network for internal communications, and which one to be used as the backup network should the primary network fail. The primary network must appear first in this list, and the backup network second. If they are not correct, you can move then with the “Up” and “Down” options.

Continues…

Pages: 1 2 3 4 5 6




Related Articles :

  • No Related Articles Found

No comments yet... Be the first to leave a reply!

Software Reviews | Book Reviews | FAQs | Tips | Articles | Performance Tuning | Audit | BI | Clustering | Developer | Reporting | DBA | ASP.NET Ado | Views tips | | Developer FAQs | Replication Tips | OS Tips | Misc Tips | Index Tuning Tips | Hints Tips | High Availability Tips | Hardware Tips | ETL Tips | Components Tips | Configuration Tips | App Dev Tips | OLAP Tips | Admin Tips | Software Reviews | Error | Clustering FAQs | Performance Tuning FAQs | DBA FAQs |