"TAG_E 2002/05/14 05:28:10 VCS:10485:Excessive delay between successive calls to GAB heartbeat (x seconds)" is reported by Veritas Cluster Server (VCS)
book
Article ID: 100031516
calendar_today
Updated On:
Description
Error Message
TAG_E 2002/05/14 05:28:10 VCS:10485:Excessive delay between successive calls to GAB heartbeat (x seconds)
Resolution
1. Private network NIC configuration:
- Ensure that all Private (Heartbeat) NICs are configured the same.
- Never run the Private (Heartbeat) communication over the public network.
- Set to half duplex and specific speed settings (no auto detect or default).
- Disable NetBIOS over TCP/IP on Private NICs (only if TCP/IP is bound).
- Confirm that each Private NIC is connected to a completely separate network segment or VLAN. For example: in a 2 node cluster (each member having 2 Private NICs), each server would connect one Private NIC to one network segment and the other to a separate segment. Summary: 4 Private NICs, 2 network segments.
2. Check the cluster node for signs of being overloaded. Establish baseline and compare to load testing. Contact Microsoft and server manufacturer for details.
3. Ensure that all, OS, or application service packs are up to date.
4. Ensure that the hardware drivers are up to date.
5. Check the network for signs of being overloaded. Check switches and routers for dropped packets. Contact network hardware manufacturers for detail.
Issue/Introduction
A GAB timeout error is recorded in the Veritas Cluster Server (VCS) log files.
Was this article helpful?
thumb_up
Yes
thumb_down
No