Cluster Server on AIX, patch detail

To use SORT, JavaScript must be enabled. How to enable JavaScript.
4.0MP3 VCS JumboPatchA Go to Download Center to download.
Basic information
Release type:	Rolling Patch
Release date:	2006-02-28
OS update support:	None
Technote:	269928
Documentation:	None
Popularity:	634 viewed downloaded
Download size:	4.14 MB
Checksum:	2188950337
Applies to one or more of the following products:
Cluster Server 4.0 MP3 On AIX 5.3
Cluster Server 4.0MP2 On AIX 5.3
Obsolete patches, incompatibilities, superseded patches, or other requirements:
None.
Fixes the following incidents:
297779, 494563, 519858, 520034, 529849, 530312, 542092
Patch ID:
None.
Readme file
* * * PATCH 4.0MP3+JumboPatch for VERITAS Cluster Server 4.0 MP3 (AIX) * * *

                  Patch Date:  February 2006


   This README provides information on:

   * BEFORE GETTING STARTED
   * FIXES AND ENHANCEMENTS INCLUDED IN THIS VCS PATCH
   * KNOWN ISSUES AND WORKAROUNDS
   * FILES AFFECTED BY THIS VCS PATCH
   * CRC AND BYTE COUNT VERIFICATION
   * SAVING YOUR CURRENT FILES AND CONFIGURATION
   * INSTALLING THIS VCS PATCH
   * UNINSTALLING THIS VCS PATCH



BEFORE GETTING STARTED
----------------------

This patch applies to VCS 4.0 MP2/MP3 running on AIX 5.3.
Ensure that you are running this configuration before 
installing this patch. Also, please ensure that you have installed 
the IBM APAR IY65664 fix.



FIXES AND ENHANCEMENTS INCLUDED IN THIS VCS PATCH
-------------------------------------------------

This patch includes the following fixes : 

e494563		MultiNICB fails when device name length is 
		greater than 3 characters. 
		Titan escalation # 290-096-248.	This fix was 
		also included in VCS 4.0 MP3.

e542092		Clean entry point not implemented for IP

e529849		MultiNICB: IP Failover is incorrect when more 
		than one VIP is configured.
		Titan escalation # 280-533-263.

e530312		NIC Agent does not report OFFLINE state on NIC failure

e520034		Support for multiple MultiNICA instances
		Titan escalation # 240-129-604

e297779		Support for multiple MultiNICB instances
		Titan escalation # 230-106-409

e519858		Report correct error message when haping fails
		because NetworkHost is on a different subnet

	 


KNOWN ISSUES AND WORKAROUNDS
----------------------------

e565151 	LinkTest using 'haping -l' fails to correctly 
		report NIC status.

		The MultiNICB agent has an optional attribute
		called LinkTestRatio which controls the frequency 
		of the pings the agent does to determine the status 
		of an interface. If this attribute is set to 0, pings
		are not done at all and the link status of the driver
		is used to determine the state of the network interface.
		The default value is 1 which means that pings are done
		every monitor cycle.
		On AIX, the ethernet driver knows about link failure 
		only from the software state but not from the hardware 
		state (i.e. if you were to remove the back end cable 
		into the network).  If the LinkTestRatio is set to
		a value other than 1, the agent will rely on the OS driver
		telling it the status of the interface, and hence if the cable 
		is pulled the agent will not detect a failure. 

		A forthcoming efix from IBM for PMR 87796, 756 will fix this issue.
		Until then make sure that LinkTestRatio is set to its default value 
		of 1.
		
All other known issues and workarounds for VCS 40MP3 apply. Please refer to 
VCS 40MP3 release notes for more information.


FILES AFFECTED BY THIS VCS PATCH
--------------------------------

	$VCS_HOME/bin/NIC/monitor

	$VCS_HOME/bin/IP/clean

	$VCS_HOME/bin/MultiNICA/close
	$VCS_HOME/bin/MultiNICA/open
	$VCS_HOME/bin/MultiNICA/monitor
	$VCS_HOME/bin/MultiNICA/MultiNICA.pm
	$VCS_HOME/bin/MultiNICA/MultiNICA/Nic.pm
	$VCS_HOME/bin/MultiNICA/MultiNICA/Command.pm
	$VCS_HOME/bin/MultiNICA/MultiNICA/Common.pm
	
	$VCS_HOME/bin/MultiNICB/MultiNICBAgent
        $VCS_HOME/bin/MultiNICB/haping  
	$VCS_HOME/bin/IPMultiNICB/IPMultiNICBAgent
	$VCS_HOME/bin/IPMultiNICB/haipswitch
      

Note: $VCS_HOME is typically set to "/opt/VRTSvcs"


CRC AND BYTE COUNT VERIFICATION
-------------------------------
Ensure that the files you have downloaded match the following cksum and
byte count :

The following command can be used to ascertain this:

# cksum NIC/monitor
66178915        7128    NIC/monitor

# cksum IP/clean
3650656539 2379 IP/clean

# cksum MultiNICA/close
2489271429 1268 MultiNICA/close

# cksum MultiNICA/open
738040939 1423 MultiNICA/open

# cksum MultiNICA/monitor
2989459094 4849 MultiNICA/monitor

# cksum MultiNICA/MultiNICA.pm
1082116677 5571 MultiNICA/MultiNICA.pm

# cksum MultiNICA/MultiNICA/Nic.pm
2683020427      11865   MultiNICA/MultiNICA/Nic.pm

# cksum MultiNICA/MultiNICA/Command.pm
4205920318 3268 MultiNICA/MultiNICA/Command.pm

# cksum MultiNICA/MultiNICA/Common.pm
3605512596 1129 MultiNICA/MultiNICA/Common.pm

# cksum MultiNICB/MultiNICBAgent
3924521904 3954474 MultiNICB/MultiNICBAgent

# cksum MultiNICB/haping
3121415047 89422 MultiNICB/haping

# cksum IPMultiNICB/IPMultiNICBAgent
3950173135 3948176 IPMultiNICB/IPMultiNICBAgent

# cksum IPMultiNICB/haipswitch
92429529 3793174 IPMultiNICB/haipswitch


SAVING YOUR CURRENT FILES AND CONFIGURATION
-------------------------------------------
Do the following on each node of the VCS cluster:


1. Save copy of the original NIC agent file:

	# cp $VCS_HOME/bin/NIC/monitor 
		$VCS_HOME/bin/NIC/monitor.orig

2. Save copies of the original IP agent files:

	# cp $VCS_HOME/bin/IP/clean  $VCS_HOME/bin/IP/clean.orig

3. Save copies of the original MultiNICA agent files:

	# cp $VCS_HOME/bin/MultiNICA/close 
		$VCS_HOME/bin/MultiNICA/close.orig
	# cp $VCS_HOME/bin/MultiNICA/open 
		$VCS_HOME/bin/MultiNICA/open.orig
	# cp $VCS_HOME/bin/MultiNICA/monitor 
		$VCS_HOME/bin/MultiNICA/monitor.orig
	# cp $VCS_HOME/bin/MultiNICA/MultiNICA.pm 
		$VCS_HOME/bin/MultiNICA/MultiNICA.pm.orig
	# cp $VCS_HOME/bin/MultiNICA/MultiNICA/Nic.pm 
		$VCS_HOME/bin/MultiNICA/MultiNICA/Nic.pm.orig
	# cp $VCS_HOME/bin/MultiNICA/MultiNICA/Command.pm 
		$VCS_HOME/bin/MultiNICA/MultiNICA/Command.pm.orig
	# cp $VCS_HOME/bin/MultiNICA/MultiNICA/Common.pm 
		$VCS_HOME/bin/MultiNICA/MultiNICA/Common.pm.orig	

4.  Save copies of the original MultiNICB and haping agent executables:

	# cp $VCS_HOME/bin/MultiNICB/MultiNICBAgent 
		$VCS_HOME/bin/MultiNICB/MultiNICBAgent.orig
        # cp $VCS_HOME/bin/MultiNICB/haping 
                $VCS_HOME/bin/MultiNICB/haping.orig

5. Save copies of the original IPMultiNICB and haipswitch agent executables:

        # cp $VCS_HOME/bin/IPMultiNICB/IPMultiNICBAgent 
                $VCS_HOME/bin/IPMultiNICB/IPMultiNICBAgent.orig
        # cp $VCS_HOME/bin/IPMultiNICB/haipswitch 
                $VCS_HOME/bin/IPMultiNICB/haipswitch.orig



INSTALLING THIS VCS PATCH
-------------------------
To install the patch:

1.  Open the VCS configuration in read/write mode using the command:

	# haconf -makerw
    
2.  Freeze all the service groups persistently using the command:

	# hagrp -freeze <group_name> -persistent

3.  Dump the VCS configuration using the command:

	# haconf -dump -makero

4.  Stop VCS:

	# hastop -all -force

5.  Remove the following files on each node in the cluster after
    verifying that original copies of these files were saved as instructed
    in the previous section:

        # rm $VCS_HOME/bin/NIC/monitor

        # rm $VCS_HOME/bin/IP/clean

        # rm $VCS_HOME/bin/MultiNICA/close
        # rm $VCS_HOME/bin/MultiNICA/open
        # rm $VCS_HOME/bin/MultiNICA/monitor
        # rm $VCS_HOME/bin/MultiNICA/MultiNICA.pm
        # rm $VCS_HOME/bin/MultiNICA/MultiNICA/Nic.pm
        # rm $VCS_HOME/bin/MultiNICA/MultiNICA/Command.pm
        # rm $VCS_HOME/bin/MultiNICA/MultiNICA/Common.pm

        # rm $VCS_HOME/bin/MultiNICB/MultiNICBAgent
        # rm $VCS_HOME/bin/MultiNICB/haping
        # rm $VCS_HOME/bin/IPMultiNICB/IPMultiNICBAgent
        # rm $VCS_HOME/bin/IPMultiNICB/haipswitch



6.  On each node in the cluster, copy the following agent excutables from 
    this patch to their respective locations:

	# cd <patch-area>

        # cp -p NIC/monitor $VCS_HOME/bin/NIC/monitor

        # cp -p IP/clean $VCS_HOME/bin/IP/clean

        # cp -p MultiNICA/close $VCS_HOME/bin/MultiNICA/close
        # cp -p MultiNICA/open $VCS_HOME/bin/MultiNICA/open
        # cp -p MultiNICA/monitor $VCS_HOME/bin/MultiNICA/monitor
        # cp -p MultiNICA/MultiNICA.pm $VCS_HOME/bin/MultiNICA/MultiNICA.pm
        # cp -p MultiNICA/MultiNICA/Nic.pm $VCS_HOME/bin/MultiNICA/MultiNICA/Nic.pm
        # cp -p MultiNICA/MultiNICA/Command.pm $VCS_HOME/bin/MultiNICA/MultiNICA/Command.pm
        # cp -p MultiNICA/MultiNICA/Common.pm $VCS_HOME/bin/MultiNICA/MultiNICA/Common.pm

        # cp -p MultiNICB/MultiNICBAgent $VCS_HOME/bin/MultiNICB/MultiNICBAgent
        # cp -p MultiNICB/haping $VCS_HOME/bin/MultiNICB/haping
        # cp -p IPMultiNICB/IPMultiNICBAgent $VCS_HOME/bin/IPMultiNICB/IPMultiNICBAgent
        # cp -p IPMultiNICB/haipswitch $VCS_HOME/bin/IPMultiNICB/haipswitch



7. Start VCS on each node in the cluster:

	# hastart

8. Open the VCS configuration in read/write mode using the command:

	# haconf -makerw

9. Unfreeze all the service groups using the command:

	# hagrp -unfreeze <group_name> -persistent

10. Dump the VCS configuration using the command:

	# haconf -dump -makero



UNINSTALLING THIS VCS PATCH
---------------------------

To uninstall the patch:

1.  Make the VCS configuration writable. On any system, type:

	# haconf -makerw

2.  Freeze the service groups where LVMVG is running.
    On any system, type:

	# hagrp -freeze <service_group> -persistent

3.  Save the configuration file (main.cf) with the groups frozen.
    On any system, type:

	# haconf -dump -makero

4.  Stop VCS:

	# hastop -all -force

5.  Remove the following files on each node in the cluster:

        # rm $VCS_HOME/bin/NIC/monitor

        # rm $VCS_HOME/bin/IP/clean

        # rm $VCS_HOME/bin/MultiNICA/close
        # rm $VCS_HOME/bin/MultiNICA/open
        # rm $VCS_HOME/bin/MultiNICA/monitor
        # rm $VCS_HOME/bin/MultiNICA/MultiNICA.pm
        # rm $VCS_HOME/bin/MultiNICA/MultiNICA/Nic.pm
        # rm $VCS_HOME/bin/MultiNICA/MultiNICA/Command.pm
        # rm $VCS_HOME/bin/MultiNICA/MultiNICA/Common.pm

        # rm $VCS_HOME/bin/MultiNICB/MultiNICBAgent
        # rm $VCS_HOME/bin/MultiNICB/haping
        # rm $VCS_HOME/bin/IPMultiNICB/IPMultiNICBAgent
        # rm $VCS_HOME/bin/IPMultiNICB/haipswitch




6.  Restore copies of the original agent 
    executables:

        # cp $VCS_HOME/bin/NIC/monitor.orig 
                $VCS_HOME/bin/NIC/monitor

        # cp $VCS_HOME/bin/IP/clean.orig  $VCS_HOME/bin/IP/clean


        # cp $VCS_HOME/bin/MultiNICA/close.orig 
                $VCS_HOME/bin/MultiNICA/close
        # cp $VCS_HOME/bin/MultiNICA/open.orig 
                $VCS_HOME/bin/MultiNICA/open
        # cp $VCS_HOME/bin/MultiNICA/monitor.orig 
                $VCS_HOME/bin/MultiNICA/monitor
        # cp $VCS_HOME/bin/MultiNICA/MultiNICA.pm.orig 
                $VCS_HOME/bin/MultiNICA/MultiNICA.pm
        # cp $VCS_HOME/bin/MultiNICA/MultiNICA/Nic.pm.orig 
                $VCS_HOME/bin/MultiNICA/MultiNICA/Nic.pm
        # cp $VCS_HOME/bin/MultiNICA/MultiNICA/Command.pm.orig 
                $VCS_HOME/bin/MultiNICA/MultiNICA/Command.pm
        # cp $VCS_HOME/bin/MultiNICA/MultiNICA/Common.pm.orig 
                $VCS_HOME/bin/MultiNICA/MultiNICA/Common.pm


	# cp $VCS_HOME/bin/MultiNICB/MultiNICBAgent.orig 
		$VCS_HOME/bin/MultiNICB/MultiNICBAgent
        # cp $VCS_HOME/bin/MultiNICB/haping.orig 
                $VCS_HOME/bin/MultiNICB/haping
        # cp $VCS_HOME/bin/IPMultiNICB/IPMultiNICBAgent.orig 
                $VCS_HOME/bin/IPMultiNICB/IPMultiNICBAgent
        # cp $VCS_HOME/bin/IPMultiNICB/haipswitch.orig 
                $VCS_HOME/bin/IPMultiNICB/haipswitch


7.  Start VCS on each node in the cluster:

	# hastart

8.  Open the VCS configuration in read/write mode using the command:

	# haconf -makerw

9. Unfreeze all the service groups using the command:

	# hagrp -unfreeze <group_name> -persistent

10. Save the VCS configuration using the command:

	# haconf -dump -makero