I am reading how to install SQL 2005 in a clustered environment from a text book and have never done it personally myself. When you reach the Virtual Server Configuration during setup, it states:

"The next thing you need to do for this new virtual server specification is to identify an IP address and which network it should use"

In the example, they show adding the "ClientPublic" network as it was defined in the text. However, I gather you have the ability to add the Internal "heartbeat" network also. The text doesn't say anything else. My guess is that you only want to add the public network to the virtual server configuration as this is what the client machines will connect to. And there is no need to add the heartbeat network as this will just serve to interfere with the monitoring process.

Is my assumption correct?

Please forgive me if the terms I am using are incorrect.

Thank-you,
Rubens

Your assumption is correct. The heartbeat is only for internal
communication within the cluster. the public network is used for apps to
connect to your virtual server.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"Rubens" <rubensrose (AT) hotmail (DOT) com> wrote

I am reading how to install SQL 2005 in a clustered environment from a text
book and have never done it personally myself. When you reach the Virtual
Server Configuration during setup, it states:

"The next thing you need to do for this new virtual server specification is
to identify an IP address and which network it should use"

In the example, they show adding the "ClientPublic" network as it was
defined in the text. However, I gather you have the ability to add the
Internal "heartbeat" network also. The text doesn't say anything else. My
guess is that you only want to add the public network to the virtual server
configuration as this is what the client machines will connect to. And
there is no need to add the heartbeat network as this will just serve to
interfere with the monitoring process.

Is my assumption correct?

Please forgive me if the terms I am using are incorrect.

Thank-you,
Rubens

Your assumption is correct. The heartbeat is only for internal
communication within the cluster. the public network is used for apps to
connect to your virtual server.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"Rubens" <rubensrose (AT) hotmail (DOT) com> wrote

I am reading how to install SQL 2005 in a clustered environment from a text
book and have never done it personally myself. When you reach the Virtual
Server Configuration during setup, it states:

"The next thing you need to do for this new virtual server specification is
to identify an IP address and which network it should use"

In the example, they show adding the "ClientPublic" network as it was
defined in the text. However, I gather you have the ability to add the
Internal "heartbeat" network also. The text doesn't say anything else. My
guess is that you only want to add the public network to the virtual server
configuration as this is what the client machines will connect to. And
there is no need to add the heartbeat network as this will just serve to
interfere with the monitoring process.

Is my assumption correct?

Please forgive me if the terms I am using are incorrect.

Thank-you,
Rubens

Your assumption is correct. The heartbeat is only for internal
communication within the cluster. the public network is used for apps to
connect to your virtual server.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"Rubens" <rubensrose (AT) hotmail (DOT) com> wrote

I am reading how to install SQL 2005 in a clustered environment from a text
book and have never done it personally myself. When you reach the Virtual
Server Configuration during setup, it states:

"The next thing you need to do for this new virtual server specification is
to identify an IP address and which network it should use"

In the example, they show adding the "ClientPublic" network as it was
defined in the text. However, I gather you have the ability to add the
Internal "heartbeat" network also. The text doesn't say anything else. My
guess is that you only want to add the public network to the virtual server
configuration as this is what the client machines will connect to. And
there is no need to add the heartbeat network as this will just serve to
interfere with the monitoring process.

Is my assumption correct?

Please forgive me if the terms I am using are incorrect.

Thank-you,
Rubens

Your assumption is correct. The heartbeat is only for internal
communication within the cluster. the public network is used for apps to
connect to your virtual server.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"Rubens" <rubensrose (AT) hotmail (DOT) com> wrote

I am reading how to install SQL 2005 in a clustered environment from a text
book and have never done it personally myself. When you reach the Virtual
Server Configuration during setup, it states:

"The next thing you need to do for this new virtual server specification is
to identify an IP address and which network it should use"

In the example, they show adding the "ClientPublic" network as it was
defined in the text. However, I gather you have the ability to add the
Internal "heartbeat" network also. The text doesn't say anything else. My
guess is that you only want to add the public network to the virtual server
configuration as this is what the client machines will connect to. And
there is no need to add the heartbeat network as this will just serve to
interfere with the monitoring process.

Is my assumption correct?

Please forgive me if the terms I am using are incorrect.

Thank-you,
Rubens

Your assumption is correct. The heartbeat is only for internal
communication within the cluster. the public network is used for apps to
connect to your virtual server.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"Rubens" <rubensrose (AT) hotmail (DOT) com> wrote

I am reading how to install SQL 2005 in a clustered environment from a text
book and have never done it personally myself. When you reach the Virtual
Server Configuration during setup, it states:

"The next thing you need to do for this new virtual server specification is
to identify an IP address and which network it should use"

In the example, they show adding the "ClientPublic" network as it was
defined in the text. However, I gather you have the ability to add the
Internal "heartbeat" network also. The text doesn't say anything else. My
guess is that you only want to add the public network to the virtual server
configuration as this is what the client machines will connect to. And
there is no need to add the heartbeat network as this will just serve to
interfere with the monitoring process.

Is my assumption correct?

Please forgive me if the terms I am using are incorrect.

Thank-you,
Rubens

Your assumption is correct. The heartbeat is only for internal
communication within the cluster. the public network is used for apps to
connect to your virtual server.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"Rubens" <rubensrose (AT) hotmail (DOT) com> wrote

I am reading how to install SQL 2005 in a clustered environment from a text
book and have never done it personally myself. When you reach the Virtual
Server Configuration during setup, it states:

"The next thing you need to do for this new virtual server specification is
to identify an IP address and which network it should use"

In the example, they show adding the "ClientPublic" network as it was
defined in the text. However, I gather you have the ability to add the
Internal "heartbeat" network also. The text doesn't say anything else. My
guess is that you only want to add the public network to the virtual server
configuration as this is what the client machines will connect to. And
there is no need to add the heartbeat network as this will just serve to
interfere with the monitoring process.

Is my assumption correct?

Please forgive me if the terms I am using are incorrect.

Thank-you,
Rubens

Your assumption is correct. The heartbeat is only for internal
communication within the cluster. the public network is used for apps to
connect to your virtual server.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"Rubens" <rubensrose (AT) hotmail (DOT) com> wrote

I am reading how to install SQL 2005 in a clustered environment from a text
book and have never done it personally myself. When you reach the Virtual
Server Configuration during setup, it states:

"The next thing you need to do for this new virtual server specification is
to identify an IP address and which network it should use"

In the example, they show adding the "ClientPublic" network as it was
defined in the text. However, I gather you have the ability to add the
Internal "heartbeat" network also. The text doesn't say anything else. My
guess is that you only want to add the public network to the virtual server
configuration as this is what the client machines will connect to. And
there is no need to add the heartbeat network as this will just serve to
interfere with the monitoring process.

Is my assumption correct?

Please forgive me if the terms I am using are incorrect.

Thank-you,
Rubens

Your assumption is correct. The heartbeat is only for internal
communication within the cluster. the public network is used for apps to
connect to your virtual server.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"Rubens" <rubensrose (AT) hotmail (DOT) com> wrote

I am reading how to install SQL 2005 in a clustered environment from a text
book and have never done it personally myself. When you reach the Virtual
Server Configuration during setup, it states:

"The next thing you need to do for this new virtual server specification is
to identify an IP address and which network it should use"

In the example, they show adding the "ClientPublic" network as it was
defined in the text. However, I gather you have the ability to add the
Internal "heartbeat" network also. The text doesn't say anything else. My
guess is that you only want to add the public network to the virtual server
configuration as this is what the client machines will connect to. And
there is no need to add the heartbeat network as this will just serve to
interfere with the monitoring process.

Is my assumption correct?

Please forgive me if the terms I am using are incorrect.

Thank-you,
Rubens

Your assumption is correct. The heartbeat is only for internal
communication within the cluster. the public network is used for apps to
connect to your virtual server.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"Rubens" <rubensrose (AT) hotmail (DOT) com> wrote

I am reading how to install SQL 2005 in a clustered environment from a text
book and have never done it personally myself. When you reach the Virtual
Server Configuration during setup, it states:

"The next thing you need to do for this new virtual server specification is
to identify an IP address and which network it should use"

In the example, they show adding the "ClientPublic" network as it was
defined in the text. However, I gather you have the ability to add the
Internal "heartbeat" network also. The text doesn't say anything else. My
guess is that you only want to add the public network to the virtual server
configuration as this is what the client machines will connect to. And
there is no need to add the heartbeat network as this will just serve to
interfere with the monitoring process.

Is my assumption correct?

Please forgive me if the terms I am using are incorrect.

Thank-you,
Rubens