LLT, GAB, and I/O fencing fixed issues

Table: LLT, GAB, and I/O fencing fixed issues lists the fixed issues for LLT, GAB, and I/O fencing.

Table: LLT, GAB, and I/O fencing fixed issues

Incident

Description

1908938

[GAB] In a large cluster, cascaded lowest node failures result in GAB panic during sequence space recovery.

1840826

[GAB] Prevent 'gabconfig -c' while port 'a' is in the middle of iofence processing.

1989645

[GAB] Whenever there is a disparity in connected memberships, GAB master must wait for maximum gab_conn_wait time. However, when the GAB master is a new joinee it does not wait which caused wrong iofence message being sent to healthy nodes in the cluster.

2066020

[LLT] The dlpiping utility exits with an error similar to "dlpiping: send ECHO_REQ failed."

2005045

[LLT] The hastart command fails to start HAD on one of the nodes with message "GabHandle::open failed errno = 16" in syslog after HAD is stopped on all the nodes in the cluster simultaneously.

1859023

[LLT] The lltconfig -T query command displays a partially incorrect output

1846387

2084121

[Fencing] The vxfenswap and the vxfentsthdw utilities fail when rsh or ssh communication is not set to the same node.

1922413

[Fencing] The vxfentsthdw utility should detect storage arrays which interpret NULL keys as valid for registrations/reservations.

1847517

[Fencing] The vxfenswap utility has an incorrect usage message for -n option

1992560

[Fencing] The vxfentsthdw utility uses scp to communicate with the local host.

1512956

[Fencing] The vxfenclearpre utility displays error messages

2151166

[VxCPS] Need strict host name matching in coordination point installer.