A word of caution here. Per the documentation I pulled down figuring this
out,
the crossover cable solution causes load balancing not to work. See Article
ID: Q242248 - http: // support. microsoft. com/ support/ kb /
articles/Q242/2/48.ASP (NOTE: spaces inserted to avoid URL striping).
HTH
Darren
p.s. I have a Word document with several of these articles which I will send
to
anyone who's interested.
At 09:49 PM 05/09/2001 -0800, Bill Pearch wrote:
>One possible solution to this issue that was practiced early in the wolfpack
>development was to have a nic in each cluster node that was connected via
>cross over cable to the other node. By having a pair of NIC's dedicated to
>heartbeat we can avoid having the heartbeat flood the network.
>TTFN,
>Bill in Anchorage
>
>-----Original Message-----
>From: Darren Crawford [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, May 09, 2001 11:26 AM
>To: [EMAIL PROTECTED]
>Subject: Re: Protocol Type 0x886F [7:3737]
>
>
>I ran into this same problem at my current client. Apparently this is a
>necessary evil in a NT clustered environment for load balancing and fault
>tolerancy. There are two 1,514 byte packets sent every second by default.
>One
>to the MAC of the NIC and the other to the multicast address. The size of
>these packets cannot be adjusted but the interval of how often they occur
>can. The heartbeat can be set between 100 and 10000 milliseconds (default
>is
>1000). The time period before the device is determined dead can be set
>between
>5 and 100 (default is 5).
>
>We did the following:
>
>Registry items alivestatus (aka AliveMsgPeriod) and aliveperiod (aka
>AliveMsgTolerance) were changed to 10000 and 9 respectively. What this
>meant on
>the network was that there were only 6 pairs of heartbeats per minute
>instead
>of 60.
>
>This should be adjusted based on the organizations tolerance of a failure.
>
>HTH
>
>Darren
>
>At 12:47 AM 05/09/2001 -0400, Andy Prima wrote:
>>Dear all,
>>I need help on protocol type 0x886F. It seems that this kind of Ethernet
>>Broadcast is circling around my network and I do not have a clue what it
>>really is.
>>
>>TIA
>>andy
>>FAQ, list archives, and subscription info:
>>http://www.groupstudy.com/list/cisco.html
>>Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>
>
>****************************************************************************
>***********************************
>Darren S. Crawford
>Lucent Technologies Worldwide Services
>2377 Gold Meadow Way Phone: (916) 859-5200 x310
>Suite 230 Fax: (916) 859-5201
>Sacramento, CA 95670 Pager: (800) 467-1467
>Email: [EMAIL PROTECTED] Epager: [EMAIL PROTECTED]
>http://www.lucent.com Network Systems
>Consultant - CCNA, CCIE Written
>
> "Providing the Power Operable Networks."
>
>****************************************************************************
>***********************************
>FAQ, list archives, and subscription info:
>http://www.groupstudy.com/list/cisco.html
>Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
****************************************************************************
***********************************
Darren S. Crawford
Lucent Technologies Worldwide Services
2377 Gold Meadow Way Phone: (916) 859-5200 x310
Suite 230 Fax: (916) 859-5201
Sacramento, CA 95670 Pager: (800) 467-1467
Email: [EMAIL PROTECTED] Epager: [EMAIL PROTECTED]
http://www.lucent.com Network Systems
Consultant - CCNA, CCIE Written
"Providing the Power Operable Networks."
****************************************************************************
***********************************
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=4037&t=3737
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
