'Port a' membership not reported when the LLT and GAB services are started.
Article ID: 100018904
Updated On:
Cause
This issue will occur if the 'Veritas VCSComm Startup' service is not running. The gabconfig utility requires this service in order to correctly report on the GAB port status.
Resolution
To verify and/or resolve this issue, perform one of the following options:
From the Services Control Panel:
1. Open the Services Applet (start > run > services.msc).
2. Located the 'VeritasVCSComm Startup' service to see if it is in the 'Started' state
3. If the service is not started, start it from the Services Console or using command line as "net start vcscomm"
Once started, the 'gabconfig -a' output should then show the Port a membership similar to the example below:
GAB Port Memberships
===============================================================
Port a gen 1ff1601 membership ;1
For any issues with VCSComm startup issues refer to VCSComm Startup Issues
Issue/Introduction
The 'gabconfig -a' command fails to report 'Port a' membership even when the LLT and GAB services are started.
Was this article helpful?
Yes
No
Powered by
