When a client node goes down, for reasons such as node panic, I/O fencing does not come up on that client node after node restart (3341322)

Last published : Sep 23, 2026
This issue happens when one of the following conditions is true:
  • Any of the CP servers configured for HTTPS communication goes down.
  • The CP server service group in any of the CP servers configured for HTTPS communication goes down.
  • Any of the VIPs in any of the CP servers configured for HTTPS communication goes down.
When you restart the client node, fencing configuration starts on the node. The fencing daemon, vxfend, invokes some of the fencing scripts on the node. Each of these scripts has a timeout value of 120 seconds. If any of these scripts fails, fencing configuration fails on that node.
Some of these scripts use cpsadm commands to communicate with CP servers. When the node comes up, cpsadm commands try to connect to the CP server using VIPs for a timeout value of 60 seconds. So, if the multiple cpsadm commands that are run within a single script exceed the timeout value, then the total timeout value exceeds 120 seconds, which causes one of the scripts to time out. Hence, I/O fencing does not come up on the client node.
Note that this issue does not occur with IPM-based communication between CP server and client clusters.
Workaround: Fix the CP server.
Related information