I/O fencing known issues
This section describes the known issues in this release of I/O fencing.
Related information
Cluster Server known issues
VxFen fails to configure at startup in standalone non-VCS CVM environments (4200117)Online fencing migration from custom to SCSI3 mode might fail (4189051, 4189048)Fencing port b is visible for few seconds even if cluster nodes have not registered with CP server (2415619)The cpsadm command fails if LLT is not configured on the application cluster (2583685)When I/O fencing is not up, the svcs command shows VxFEN as online (2492874)The vxfenswap utility does not detect failure of coordination points validation due to an RSH limitation (2531561)The vxfenswap utility deletes comment lines from the /etc/vxfemode file, if you run the utility with hacli option (3318449)The vxfentsthdw utility may not run on systems installed with partial SFHA stackWhen 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)The vxfenconfig -l command output does not list Coordinator disks that are removed using the vxdmpadm exclude dmpnodename=<dmp_disk/node> commandStale .vxfendargs file lets hashadow restart vxfend in Sybase mode (2554886)CP server configuration fails while setting up secure credentials for CP server hosted on an SFHA cluster (2621029)The CoordPoint agent faults after you detach or reattach one or more coordination disks from a storage array (3317123)