sfsfs-sles10_x86_64-5.5HF5

 Basic information
Release type: Hot Fix
Release date: 2010-03-31
OS update support: None
Technote: None
Documentation: None
Popularity: 364 viewed    downloaded
Download size: 38.69 MB
Checksum: 3455131781

 Applies to one or more of the following products:
FileStore 5.5 On SLES10 x86-64

 Obsolete patches, incompatibilities, superseded patches, or other requirements:
None.

 Fixes the following incidents:
1941992

 Patch ID:
None.

Readme file
README: HF5


Date:2010-03-26
OS:SLES10SP2
Etrack Incidents:1941992 

Errors/Problems Fixed: listed below

Issue Details:
1) A node in cluster halt, but it's vip can't online in other nodes

Install Patch:

Please skip step 1) and 4) if, you have already applied 5.5HF4

Step 1) Pre-Install Instructionis:

	Before installing the patch, please perform following steps:

	a) Login "support" account

	b) List out all the filesystem, those are mounted:
	   > mount -t vxfs | grep "type vxfs"

	c) Unmount all the filesystem from all the nodes:
	   > cfsumount </vx/fsname> 

	d) Make sure no FS remain mounted. Run follwoing command and nothing should be displayed
	   > mount -t vxfs | grep "type vxfs"


Step 2) Apply patch only. 

	a) Login through master
	   > su - master

	b) Go to patch install
	   > upgrade patch install <URL>


Step 3) Check Status:

	As upgrade to HF5, requires ManagementConsole to go offline once, so Admin will not be able to see 
	any messages on the screen. Admin needs to perform following steps:

	a) Login through "support" on the master node( at the time of patch upgrade)

	b) Do tail of upgrade.log
	   > tail -f /opt/VRTSnagw/log/upgrade.log

	c) check for the message "Patch Installation of 5.5HF5 completed successfully"

	d) If you do not able to get the above message at the end, please contact FileStore Team.



Step 4) Reboot the cluster:

	a) Login through master
	   > su - master

	b) Go to "cluster" section and do reboot
	   > cluster > reboot <all|nodename>


	Check State:

	Once cluster comes up, verfify followiing

	a)Please check the state of filesystems. And run below comamnd in case it is in FAULTED state.
	   >storage scanbus
	   >support services autofix