I use a simple, inexpensive hub with the power plug glued in place. I rely
on the ability of the cluster to use one or more of the 'public' networks
for heartbeat if necessary.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Stephen Strong" <anonymous (AT) discussions (DOT) microsoft.com> wrote
Quote:
What do other people do for switch redundancy on their heartbeat networks
with 4-node SQL2K/W2K3 clusters in their datacenters? As NIC teaming isn't
|
supported on the heartbeat network one cannot simply point one NIC to switch
A and the second (teamed) NIC to switch B.
Quote:
Sure, if the [single] heartbeat switch fails, comms is redirected by
clustering across the "public" network to the other nodes but this has stuff
|
like authentication, DNS, SQL traffic etc to complicate things (which is all
excluded from the heartbeat network for good reason).
Quote:
Currently I've been unable to locate any doco on the MS public website
that lists the MS-recommended best practices for the heartbeat network
|
architecture. Any suggestions?
Re: Switch redundancy on heatbeat network -
04-01-2004
, 09:20 PM
Linear Mode
