The message "GAB INFO V-15-1-20037 Port a gen [membership number] jeopardy ; [n]" appears in Veritas Storage Foundation HA for Windows
|Article:TECH53404|||||Created: 2007-01-10|||||Updated: 2014-03-15|||||Article URL http://www.symantec.com/docs/TECH53404|
The message "GAB INFO V-15-1-20037 Port a gen [membership number] jeopardy ; [n]" appears in the System log for Veritas Storage Foundation HA for Windows server.
GAB INFO V-15-1-20037 Port a gen [membership number] jeopardy ; [n]
A status of jeopardy means that only one heartbeat is alive between the affected node and the rest of the cluster (Figure 1).
The number following the message is the node ID for the node that is in jeopardy. This ID corresponds with the IDs that are stored in llthosts.txt.
Figure - 1
A status of jeopardy can be caused by many things, including the following:
- A physical connectivity problem with the NIC, cable or switch. To test network connectivity on the heartbeat network, bind TCP/IP to the NICs and use Ping to verify that the nodes can communicate with each other.
- One of more of the nodes may be very busy or low on resources. This may cause the node to be slow to respond to heartbeats.
- A configuration problem within VCS (Veritas Cluster Server). Ensure that llttab.txt contains valid MAC addresses for the heartbeat nics.
- For a link low-pri heartbeat, the port that used for heartbeats may be blocked. By default, VCS uses port 4145 UDP for heartbeats.
- If these messages only occur immediately after a reboot, it may not indicate that there is a problem with the cluster. This is sometimes caused by differences in timing between the heartbeats of the nodes. Once the nodes have detected each other over all heartbeat paths, the messages should stop.
Article URL http://www.symantec.com/docs/TECH53404