Error Message

From the system logs:
Feb 28 01:41:39 server102 systemd: Failed to start VERITAS I/O Fencing (VxFEN).
Feb 28 01:41:39 server102 systemd: Unit vxfen.service entered failed state.
Feb 28 01:41:39 server102 systemd: vxfen.service failed.
Feb 28 01:41:39 server102 systemd: Starting VERITAS Cluster Server (VCS)...
Feb 28 01:41:39 server102 vcs: Starting VCS: [  OK  ]
Feb 28 01:41:39 server102 Had[5934]: VCS NOTICE V-16-1-10619 'HAD' starting on: server102
Feb 28 01:41:39 server102 systemd: Started VERITAS Cluster Server (VCS).
Feb 28 01:41:39 server102 systemd: vxfen.service holdoff time over, scheduling restart.
Feb 28 01:41:39 server102 systemd: Starting VERITAS I/O Fencing (VxFEN)...

From the engine logs:
# tail -f  /var/*vcs*/log/engine_A.log
2018/02/28 04:49:19 VCS CRITICAL V-16-1-10037 VxFEN driver not configured. Retrying...
2018/02/28 04:49:24 VCS CRITICAL V-16-1-10037 VxFEN driver not configured. Retrying...
2018/02/28 04:49:29 VCS CRITICAL V-16-1-10037 VxFEN driver not configured. Retrying...
2018/02/28 04:49:34 VCS CRITICAL V-16-1-10037 VxFEN driver not configured. Retrying...
2018/02/28 04:49:39 VCS CRITICAL V-16-1-10037 VxFEN driver not configured. Retrying...

# hastatus -sum

-- SYSTEM STATE
-- System               State                Frozen

A  server101            LOCAL_BUILD          0
A  server102            CURRENT_PEER_WAIT    0
 

1. Open this file with a text editor.
/etc/systemd/system/multi-user.target.wants/vxfen.service

2. Under the "service" tab, change Restart=no to Restart=on-failure.
[Service]
Type=forking
Restart=no
IgnoreSIGPIPE=no
KillMode=process
GuessMainPID=no
RemainAfterExit=yes
StandardOutput=journal+console
ExecStart=/opt/VRTSvcs/vxfen/bin/vxfen start 2>&1
ExecStop=/opt/VRTSvcs/vxfen/bin/vxfen stop 2>&1

3. Reboot the server.