VxFen fails to configure at startup in standalone non-VCS CVM environments (4200117)

On AIX nodes running CVM or CFS with I/O fencing where VCS is not managing the stack, VxFen fails to start and configure when invoked in a standalone manner via /etc/init.d/vxfen.rc start. During startup, GAB port b is not established, and running vxfenadm -d returns error V-11-2-1115.

Note: In VCS-managed clusters, this issue does not manifest because the VCS parent process exports VCS_ENABLE_PUBSEC_LOG_PERM directly to the startup path.

Workaround: Choose one of the following options:

Option 1 (Recommended): Pass the variable inline at startup.

Supply the default variable explicitly when starting the service: VCS_ENABLE_PUBSEC_LOG_PERM=0 /etc/init.d/vxfen.rc start

Option 2: Export the variable globally.

Add the variable definition to your shell environment or node profile (/etc/profile): export VCS_ENABLE_PUBSEC_LOG_PERM=0