 | ||
| Gathering LLT and GAB information for support analysis | ||
|---|---|---|
| Prev | VCS message logging | Next |
You must run the getcomms script to gather LLT and GAB information when you encounter issues with LLT and GAB. The getcomms script also collects core dump and stack traces along with the LLT and GAB information.
To gather LLT and GAB information for support analysis
If you had changed the default value of the GAB_FFDC_LOGDIR parameter, you must again export the same variable before you run the getcomms script.
See GAB message logging.
# /opt/VRTSgab/getcomms
The script uses rsh by default. Make sure that you have configured passwordless rsh. If you have passwordless ssh between the cluster nodes, you can use the -ssh option. To gather information on the node that you run the command, use the -local option.
Troubleshoot and fix the issue.
See Troubleshooting Low Latency Transport (LLT).
See Troubleshooting Group Membership Services/Atomic Broadcast (GAB).
If the issue cannot be fixed, then contact Symantec technical support with the file /tmp/commslog.<time_stamp>.tar that the getcomms script generates.