OS: HPUX

OS Version: 11iv3 (11.31)

Etrack Incidents: 1843835


Fixes Applied for Products:
	VRTSgab - Veritas Group Membership and Atomic Broadcast By Symantec

Patch Name: UNOF_40448

Patch Description: 11.31 VRTS 5.0 RP2 HF1 VRTSgab Kernel Patch

Creation Date: 09/09/24

Post Date: 09/09/24

Hardware Platforms - OS Releases:
	11.31

Products:
	VRTSgab 5.0 RP2 HF1

Filesets:
	VRTSgab.VRTSGAB-KRN, fr=5.0.31.0, fa=HP-UX_B.11.31_IA, v=HP
	VRTSgab.VRTSGAB-KRN, fr=5.0.31.0, fa=HP-UX_B.11.31_IA, v=Symantec
	VRTSgab.GABRUNTIME, fr=5.0.31.0, fa=HP-UX_B.11.31_IA, v=HP
	VRTSgab.GABRUNTIME, fr=5.0.31.0, fa=HP-UX_B.11.31_IA, v=Symantec
	VRTSgab.VRTSGAB-KRN, fr=5.0.31.0, fa=HP-UX_B.11.31_PA, v=HP
	VRTSgab.VRTSGAB-KRN, fr=5.0.31.0, fa=HP-UX_B.11.31_PA, v=Symantec
	VRTSgab.GABRUNTIME, fr=5.0.31.0, fa=HP-UX_B.11.31_PA, v=HP
	VRTSgab.GABRUNTIME, fr=5.0.31.0, fa=HP-UX_B.11.31_PA, v=Symantec
	VRTSgab.VRTSGAB-ENG-MAN, fr=5.0.31.0, fa=HP-UX_B.11.31_IA/PA, v=HP
	VRTSgab.VRTSGAB-ENG-MAN, fr=5.0.31.0, fa=HP-UX_B.11.31_IA/PA, v=Symantec

Automatic Reboot?: Yes (Dynamically Loadable Kernel Modules in the
			patch may not always require a reboot)

Status: Beta Release

Critical:
	Yes
	UNOF_40448: PANIC
		VERITAS Incident Number: 1843835
	PHNE_39147: PANIC

Category Tags:
	defect_repair trial_patch critical panic dlkm

Path Name: /hp-ux_patches/11.X/UNOF_40448

Symptoms:
	UNOF_40448:
	VERITAS Incident Number: 1843835
	System panics with the following panic string:
	"Port w halting system due to depleted memory"

	PHNE_39147:
	(SR: QXCR1000787691)
	VERITAS Incident Number: 1060657
	In a Serviceguard environment, when the GAB master leaves
	the cluster and another node, having a lower node ID than
	the master node, joins the cluster, other surviving node(s)
	in the cluster may fail to complete cluster reconfiguration
	and panic with the following message:
	"panic: GAB: Port d halting system due to network failure"

	(SR:  QXCR1000787694)
	VERITAS Incident Number: 1084656
	Running the 'gabdebug' utility in a loop may trigger a data
	page fault. The panic stack trace includes the following
	kernel routines:
	"
	gab_print_uio
	gab_print_msg
	gab_ioc_debug
	gabioctl
	gabhpioctl
	spec_ioctl
	vno_ioctl
	ioctl
	syscall
	"

	(SR:  QXCR1000787703)
	VERITAS Incident Number: 862507
	The system panics with the panic string "assert failed"
	during cluster reconfiguration. The stack trace shows
	the following routines:
	"
	gab_sf_restseq
	gab_sf_recv_start
	gab_recv_start
	gab_receive
	gab_receive_port_que
	gab_receive_que
	gab_lrecv
	llt_lrsrv_port
	llt_deliver
	llt_threadfunc
	"

Defect Description:
	UNOF_40448:
	VERITAS Incident Number: 1843835
	This panic happens only when system does not have
	sufficient memory in spinlock safe cache.
	Resolution:
	Code updated to allocate memory from gab internal memory,
	when spinlock safe cache does not have sufficient memory.

	PHNE_39147:
	(SR: QXCR1000787691)
	VERITAS Incident Number: 1060657
	GAB is not equipped to address a scenario wherein the GAB
	master node with the lowest GAB node id leaves the cluster
	and another node with a lower node ID than the master node,
	joins the cluster. As a result, the cluster reconfiguration
	process fails to complete on the surviving nodes.
	Eventually, GAB halts these nodes.

	Resolution:
	GAB is modified to complete the cluster reconfiguration
	when the master node leaves the cluster and another node
	with a lower node id joins the cluster.

	(SR:  QXCR1000787694)
	VERITAS Incident Number: 1084656
	The debug utility accesses certain GAB internal variables
	that are incorrectly typecast, leading to an invalid
	pointer dereference and eventually a system panic.

	Resolution:
	The typecasting issues with GAB's internal variables
	are now resolved.

	(SR:  QXCR1000787703)
	VERITAS Incident Number: 862507
	The assertion failure uncovers a race condition in GAB.
	Due to the race condition, GAB incorrectly set a flag
	indicating that a sequence number request was sent during
	a previous cluster reconfiguration. This incorrect setting
	of the flag eventually led to a system panic with the panic
	string "assert failed" on a subsequent cluster
	reconfiguration.

	Resolution:
	GAB is now modified to reflect the correct sequence
	request status.

Enhancement:
	No

SR:
	QXCR1000787691 QXCR1000787694 QXCR1000787703

Patch Files:
	VRTSgab.VRTSGAB-KRN, fr=5.0.31.0, fa=HP-UX_B.11.31_IA, v=HP:

	VRTSgab.VRTSGAB-KRN, fr=5.0.31.0, fa=HP-UX_B.11.31_IA,
		v=Symantec:
	/usr/conf/mod/gab

	VRTSgab.GABRUNTIME, fr=5.0.31.0, fa=HP-UX_B.11.31_IA, v=HP:

	VRTSgab.GABRUNTIME, fr=5.0.31.0, fa=HP-UX_B.11.31_IA,
		v=Symantec:
	/sbin/gabdebug

	VRTSgab.VRTSGAB-KRN, fr=5.0.31.0, fa=HP-UX_B.11.31_PA, v=HP:

	VRTSgab.VRTSGAB-KRN, fr=5.0.31.0, fa=HP-UX_B.11.31_PA,
		v=Symantec:
	/usr/conf/mod/gab

	VRTSgab.GABRUNTIME, fr=5.0.31.0, fa=HP-UX_B.11.31_PA, v=HP:

	VRTSgab.GABRUNTIME, fr=5.0.31.0, fa=HP-UX_B.11.31_PA,
		v=Symantec:
	/sbin/gabdebug

	VRTSgab.VRTSGAB-ENG-MAN, fr=5.0.31.0, fa=HP-UX_B.11.31_IA/PA,
		v=HP:

	VRTSgab.VRTSGAB-ENG-MAN, fr=5.0.31.0, fa=HP-UX_B.11.31_IA/PA,
		v=Symantec:
	/opt/VRTS/man/man1m/gabconfig.1m

cksum(1) Output:
	VRTSgab.VRTSGAB-KRN, fr=5.0.31.0, fa=HP-UX_B.11.31_IA, v=HP:
	3630476484 1133856 /usr/conf/mod/gab

	VRTSgab.GABRUNTIME, fr=5.0.31.0, fa=HP-UX_B.11.31_IA, v=HP:
	338717218 87156 /sbin/gabdebug

	VRTSgab.VRTSGAB-KRN, fr=5.0.31.0, fa=HP-UX_B.11.31_PA, v=HP:
	63309362 939200 /usr/conf/mod/gab

	VRTSgab.GABRUNTIME, fr=5.0.31.0, fa=HP-UX_B.11.31_PA, v=HP:
	4091025027 40960 /sbin/gabdebug

	VRTSgab.VRTSGAB-ENG-MAN, fr=5.0.31.0, fa=HP-UX_B.11.31_IA/PA,
		v=HP:
	1018755946 5905 /opt/VRTS/man/man1m/gabconfig.1m

Patch Conflicts: None

Patch Dependencies: None

Hardware Dependencies: None

Other Dependencies: None

Supersedes:
	PHNE_39147 

Equivalent Patches: None

Patch Package Size: 2210 KBytes

Installation Instructions:
	Please review all instructions and the Hewlett-Packard
	SupportLine User Guide or your Hewlett-Packard support terms
	and conditions for precautions, scope of license,
	restrictions, and, limitation of liability and warranties,
	before installing this patch.
	------------------------------------------------------------
	NOTE: This patch is a un-official patch, before installing 
	any offcial patch on top of this patch, please uninstall 
	this patch from all your cluster nodes.
	------------------------------------------------------------
	To Install the UNOF_40448 patch to your system:	
	1. Back up your system before installing a patch.

	2. Login as root.

	3. Install/Upgrade all the cluster nodes to VCS 5.0RP2/11iv3.
	   Refer to the VCS Release Notes for HP-UX 11iv3 for 5.0RP2.

	4. Uncompress the patch downloaded from Symantec site to 
	   a directory of your choice (ex. /[dir])

	5. Run swinstall command to install the Un-Official patch:
		swinstall -s /[dir]/patches -x autoreboot=true UNOF_40448


	NOTE: Installation of this patch might require a reboot of 
	the system, if gab driver is in loaded state. To unload gab driver, 
	please follow instructions in "VCS 5.0 Installation & Configuration 
	Guide" to stop all modules dependent on gab.

	6. Configure the cluster. Refer to the VCS 5.0RP2/11iv3 Release Notes 
	   for more information.

	------------------------------------------------------------
	To Remove/Uninstall the UNOF_40448 patch from your system:

	1. Back up your system before installing a patch.

	2. Login as root.

	3. Run the following command to remove the Un-Official Patch 
	   from the cluster node:
		swremove -x autoreboot=true UNOF_40448			

	NOTE: Uninstall of this patch might require a reboot of 
	the system, if gab driver is in loaded state. To unload gab driver, 
	please follow instructions in "VCS 5.0 Installation & Configuration 
	Guide" to stop all modules dependent on gab.

	4. Check with "swlist PHNE_39147" command to confirm VCS 5.0RP2/11iv3 
	   patch is installed on the system.

	------------------------------------------------------------
	For future reference, the contents of the UNOF_40448.text file is 
	available in the product readme:
		swlist -l product -a readme -d @ /[dir]

Special Installation Instructions:
	If you are installing/removing this patch on an inactive
	DRD system image:
	* You need not and MUST not stop/kill or restart any
	  processes or daemons. Since the patch is being installed
	  on a DRD clone these actions are not needed, and in fact
	  could leave the running system in an undesirable state.
	  When the DRD clone is booted, all processes will be
	  stopped and restarted.
	* Only make kernel changes by running "drd runcmd kctune".

	If you are installing/removing this patch on a
	live system:
	* While using Serviceguard with CVM 5.0 or CFS 5.0
	  products, it is advised to halt the cluster before
	  applying this patch. All the nodes within the
	  cluster must have the same level of patches.