Date: 2012-01-16
OS: SLES
OS Version: 11 SP1
Etrack Incidents: 2309472, 2309478, 2309485, 2414820, 2414941, 2414920, 2414898, 2360118, 2580929, 2592680, 2612689, 2444257, 2570932, 2505193
Symantec FileStore N8300
N8300 5.7P1 Patch Upgrade README
CONTENTS
I. Overview
II. Upgrade procedure
III. Fixed issues
IV. Known issues
PATCH ID : N/A
PATCH NAME : Filestore-N8300-5.7P1.tar.gz
MD5SUM : 1030add86f0a87cc6cef17288ef9ae07
BASE PACKAGE NAME : Symantec FileStore N8300
BASE PACKAGE VERSION : 5.7
OBSELETE PATCHES : N/A
SUPERCEDED PATCHES : N/A
INCOMPATIBLE PATCHES : N/A
SUPPORTED OS : SLES
SUPPORTED OS VERSION : SLES 11 SP1
CREATION DATE : 2012-01-16
CATEGORY : N/A
REBOOT REQUIRED : Yes
SUPPORTS ROLLBACK : NO
I. Overview
==========
This readme file is for upgrading from FileStore 5.7GA to 5.7P1.
Notes:
1. Patch upgrade will cause service failover from one node to another which will take about 15 seconds. This will not impact NFS client mounts and replication jobs, but CIFS client mounts will need to connect again, and backup jobs need to be resumed as well after an upgrade.
2. For the above reason, it is recommended to stop CIFS, backup, and EV I/O loads during an upgrade.
3. The 5.7P1 patch can only be applied to the 5.7RTM and the 5.7GA release, not the 5.6 release.
4. Patch upgrade cannot be rollbacked once applied.
II. Upgrade procedure
=====================
Prerequisites
-------------
1. Stop I/O load on client or stop services:
Via ISM (Backup is managed at ISM):
ISM ----> CIFS ---> CIFS Service ---->Disable
ISM ----> FTP ----> FTP Service ---->Disable
ISM ----> HTTP ----> HTTP Service ---->Disable
Via CLISH:
N8300>CIFS server stop
N8300>FTP server stop
N8300>HTTP server stop
N8300>Backup stop
2. Copy Filestore-N8300-5.7P1.tar.gz to the master node, and check md5sum:
1030add86f0a87cc6cef17288ef9ae07 Filestore-N8300-5.7P1.tar.gz
3. If fencing is enabled, turn off fencing, and remove I/O fencing before the upgrade:
N8300> storage fencing off
N8300> storage fencing destroy
4. Total patch upgrade time is about 45 minutes for a two-node cluster:
5. FileStore 5.7P1 has the same array version as 5.7GA. The system version should be 126.T03 and SES version should be 077.
Install Patch
-------------
1. Expand Filestore-N8300-5.7P1.tar.gz.
N8300_01# tar xzvf Filestore-N8300-5.7P1.tar.gz
SPC001B013_patch/
SPC001B013_patch/monitor.sh
SPC001B013_patch/upgrade.tar
SPC001B013_patch/pre_patch.sh
SPC001B013_patch/N8000V2_PATCH_2011_12_31.tar.gz
2. Run the "pre_patch.sh" script in the SPC001B013_patch directory. After about 5 minutes, enter "BOTH" at prompt:
N8300_01#./pre_patch.sh
which part do you want to upgrade?[HS|BOTH] BOTH
<command outcome="upgrade">
<record>
<field name="status" value="0"/>
</record>
Where "value=0" means the upgrade just started and is 0% completed.
3. Monitor upgrade progress from the SPC001B013_patch directory on the master node:
N8300_01# cd SPC001B013_patch
N8300_01# ./monitor.sh | grep progress
<field name="progress" value="26.8"/>
Where "value=26.8" means the current progress percentile.
4. When the master node is disconnected due to a reboot, connect the console IP to the new master node, and do the above step to monitor the progress on the new master node (SPC001B013_patch path structure will be created on the new master node):
<field name="progress" value="100"/> means upgrade is done.
5. Check the cluster status:
To check that the installation is done, login to the master node via the console IP, and check that all nodes are in the RUNNING state:
N8300>cluster show
-------- ----- ----------- -------- -------- -------- --------
N8300_01 RUNNING 0.98 0.01 0.00 0.01 0.00
N8300_02 RUNNING 0.97 0.01 0.00 0.01 0.00
N8300_01# gabconfig -a
GAB Port Memberships
=================================
Port a gen 1128e02 membership 01
Port b gen 1128e04 membership 01
Port f gen 1128e0c membership 01
Port h gen 1128e06 membership 01
Port v gen 1128e08 membership 01
Port w gen 1128e0a membership 01
Post-Install Processes
-----------------------
1. If fencing was enabled, enable it again.
2. Start I/O load on client and start services:
Via ISM (Backup is managed at ISM):
ISM ----> CIFS ---> CIFS Service ---->Enable
ISM ----> FTP ----> FTP Service ---->Enable
ISM ----> HTTP ----> HTTP Service ---->Ensable
Via CLISH:
N8300>CIFS server start
N8300>FTP server start
N8300>HTTP server start
N8300>Backup start
3. Download ISM to Windows:
Remove current ISM version:
At the Windows command prompt, type "javaws -viewer". A Java Cache Viewer window will display with a list of ISM installations.
Highlight ISM, and click the "X" button to delete it.
Install ISM:
Open an Internet browser and type: http://<console IP>:/8088. Click "Click Here to Launch FileStore ISM" and follow the prompt to install a new ISM version.
III. Fixed issues
=========================================
ISM/array fixed issue list:
2309472, 2308478: ISM: cannot delete host group and no meaningful error prompt
2309478, 2308485: ISM: page at port 8088 does not have SYMC logo displayed
2309485, 2308489: ISM: SYMC logo not displayed
2414820, 2412676: ISM: initiator-host mapping not displayed
2414941, 2412681: ISM: displays DMP paths linked to one node only
2414920, 2412690: ISM: does not allow to select NIC for replication link
2414898, 2413780: ISM[FTP]: need to allow FTP share inside and CIFS shared FS
2360118, 2358905: ISM: unable to add node using the ISM GUI
2580929: ISM: warning message without details
2592680, 2496441: ISM: ISM issue with logrotate errors
2612689, 2612687: ISM: missing engine version display
2444257, 2414941: ISM: ISM displays DMP paths linked to one node only
2570932, 2572376: ISM: ISM failed to refresh devices
2505193, 2505190: UPGRADE: track HS side of plug in change to use softlink
FileStore fixed issues list:
Refer to: https://sort.symantec.com/patch/detail/5770
IV. Known Issues:
=================
Refer to: https://sort.symantec.com/patch/detail/5770
2670274 ISM: system type is displayed as 8350 on N8300 cluster
