document template - wikileaks · web viewmicrosoft word opens on your laptop and the document is...

© EMC Corporation CONFIDENTIAL AND PROPRIETARY

Celerra upgrd-ck script User Guide

REVISION 11-01NOV 2, 2012

CONFIDENTIAL AND PROPRIETARY

document.doc 1


Revision History...................................................................................................................................... 3

What’s New In upgrd-ck script.................................................................................................................3

What’s New in the PUHC ( check_nas_upgrade )....................................................................................3

Disclaimers............................................................................................................................................. 3

Comments.............................................................................................................................................. 3

Supported Code and Platforms...............................................................................................................3

Task List................................................................................................................................................. 3

Acquire the latest version of the script and it User Guide.........................................................................3

Installing the script on the Control Station................................................................................................5

Using WINSCP:...................................................................................................................................... 6

Using Mcopy with a floppy:.................................................................................................................... 11

Using Untar and Unzip:......................................................................................................................... 12

autolog collection scripts....................................................................................................................... 13

Run the script before the upgrade.........................................................................................................13

Analyze the pre-upgrade log data..........................................................................................................17

Failure Counts...................................................................................................................................... 19

What to file with your CCA request........................................................................................................20

Run the script post upgrade.................................................................................................................. 20

Analyze the post upgrade log data.........................................................................................................22

File Clean up......................................................................................................................................... 24

Using cpgInput.rpt as the Configuration Source for NAS Code Upgrades...............................................25

Error Messages.................................................................................................................................... 34

Copyright © 2003 EMC Corporation. All rights reserved.EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

document.doc 2


Revision History Date Revision Change Description

9/14/2012 10.99 Listed in what’s new

10/19/2012 11.00 Listed in what’s new ( re-called)

11/02/2012 11.01 Listed in what’s new

What’s New In upgrd-ck scriptFix backup of cron jobs for NAS > 5.6Add check for user event.cfg files ( need a Primus ) Add check for 720 MB / free space when 5.6 to 6.0 upgrade Add check W000217 for ETA emc277607Add check E000218 for running tasksAdd check E000219 for LUN 5 size Add check E000220 for Invalid DM netmask

Change logging for external usermapper check.

What’s New in the PUHC ( check_nas_upgrade )

DisclaimersThis script is intended for use by EMC Support Personnel and Authorized EMC Partners.

Comments Any comments, problems, issues or concerns should be submitted via email to the feedback email link [email protected]

Please include the /home/nasadmin/lists-tar-<hostname>-<date stamp>-<run level>.tar.gz file produced by the upgrd-ck script along with any screen captures and other supporting information and a detailed description of the problem encountered.

Supported Code and PlatformsThe script has been tested with NAS code version 5.1 or higher on all supported Celerra Hardware.

document.doc 3

mailto:[email protected]


Task List Acquire the latest version of the script and it User Guide

Read and understand this Users Documentation

Install the script to the Control Station

Run the script before the upgrade

Analyze the pre-upgrade log data

Collect log for transfer with CCA request or transfer to Celerra Support for Assistance

Run the script post upgrade

Analyze the post upgrade log data

File clean up

Acquire the latest version of the script and it User Guide

Always check that the latest version of the script is what you will be testing with.

The upgrd-ck Script and support document are bundled with the Celerra Procedure Generator.

1. Click here to visit the Celerra Procedure Generator Web Site.

2. Download and install the latest Celerra Procedure Generator with default settings.

3. Retrieve the latest upgrd-ck script along with the support documentation from the following location on your local computer:

C:\Program Files\EMC\Celerra Procedure Generator\Modules\SCRIPTS

Note: If you do not install the Celerra Procedure Generator in the default directory, you will have to navigate to the SCRIPTS directory to find the upgrd-ck script. It will be in the following location: [Install Location]\Modules\SCRIPTS.

Available for EMC Partners on EMC Services Partner Web via Powerlink web site at

https://powerlink.emc.com

Note: Use the “bin” option when using ftp to download the file.

document.doc 4

https://powerlink.emc.com/

http://www.cs.isus.emc.com/csweb2/dgweb/celerrapg/index.htm


Installing the script on the Control Station1. [ ] Once you have the latest version of the script on your PC

2. [ ] Copy the file to a floppy

copy c:\upgrd-ckvX.tar.gz a:\

3. [ ] Mount the floppy on the Control Station

mount /dev/fd0 /mnt

4. [ ] Copy the script from the mounted floppy to the /home/nasadmin directory on the Control Station

cp /mnt/upgrd-ckvX.tar.gz /home/nasadmin

Note: You could also ftp the file to the Control Station, but this will require that you first copy the upgrd-ck script file to a ftp server, then logon to the Control Station and from the /home/nasadmin directory, ftp the upgrd-ckvX.tar.gz file in binary mode from the source ftp server, to the Control Station.

5. [ ] Untar and gzip the file:

tar xvfz upgrd-ckv10-5.tar.gzupgrd-ckv10-5.bincheck_nas_upgrade_5.4.27.2.tar.gzcheck_nas_upgrade_5.5.25.2.tar.gzlogcoltrans.tar.gzconnectivity2212007.tar.gz

6. [ ] When you run the script as you normally would it will extract, install and run the appropriate check_nas_upgrade package, based on user response about which version you are upgrading to. The scripts will be installed in the /tmp directory. The NAS Code upgrade will do the installation to the proper location.

7. [ ] If you selection option 3 when prompted the installation to the /tmp directory will not be performed. The check_nas_upgrade script will only be installed if you are currently running NAS code 5.2 or higher. If the current version of the installed version of this script is higher then the one included with the upgrd-ck script, it will not be installed, and the current /nas/tools/check_nas_upgrade script will be run instead.

document.doc 5


Using WINSCP: 8. [ ] To start WinSCP3, Double click on WinSCP3.exe in the Program Files directory or

double click on the WinSCP3 Icon.

9. [ ] Click on the NEW tab in the WinSCP Login window.

Figure 1 WinSCP Login Window

10. [ ] Enter the Control Station IP as the host name, root as the user name and the root password.

Figure 2 WinSCP Login Session Window

11. [ ] Click on Login tab.

12. [ ] The Connecting to Host and the Authentication and Reading Remote Directory messages will display.

13. [ ] The WinSCP Dual Screen display opens.

document.doc 6


14. [ ] In the right window navigate to the directory containing the upgrade check script.The default location is C:\Program Files\EMC\Celerra Procedure Generator \Modules\Scripts.

15. [ ] In the left window navigator to the Celerra /home/nasadmin directory.

Figure 3 WinSCP WinSCP Dual Screen display Window

document.doc 7


16. [ ] Drag the upgrd-ck script to the /home/nasadmin directory window.

Figure 4 WinSCP Copy display

17. [ ] Click on copy.

18. [ ] The WinSCP Copy Status screen displays.

Figure 5 WinSCP Copy Status

document.doc 8


19. [ ] When the copy has completed verify that both files are the same size.

20. [ ] Click on the F10 Quit tab to close WinSCP.

21. [ ] Click on OK to Terminate the Session and close the WinSCP application.

22. [ ] Open an SSH, secure shell connection or serial connection, with the Control Station.A connection may be made over the Customer’s network using SSH, PuTTY or another SSH utility.

23. [ ] Use the following procedure to establish serial communication with an NS-series Control Station.

a. Connect the NULL modem cable to the front of the Control Station and to the service laptop.

b. Open a HyperTerminal session as follows:

c. From the Start Menu, select Programs > Accessories > Communications > HyperTerminal.

d. Enter a session name and click OK.

e. Select the COM port the cable connects to in the Connect Using box and click OK.

f. Enter the following port settings; then click OK.

Bits per second: 19200 Flow Control: None

Data bits: 8 Emulation: Auto Detect

Parity: None Telnet terminal ID: ANSI

Stop bits: 1

g. Open the Properties window and click the Settings Tab. Select Auto Detect in the Emulation box and ANSI in the Telnet terminal ID box.

document.doc 9


24. [ ] Log onto the Control Station as nasadmin.

login:nasadmin

25. [ ] Become the root user.

$ suPassword:

document.doc 10


Using Mcopy with a floppy: 26. [ ] On the service lap top navigate to the directory containing the upgrade check script.The default location is C:\Program Files\EMC\Celerra Procedure Generator\Modules\Scripts.

27. [ ] Copy the upgrd-ck script to a floppy.

28. [ ] Place the floppy in the Celerra Control Station.

29. [ ] Open an SSH, secure shell connection or serial connection, with the Control Station.A connection may be made over the Customer’s network using SSH, PuTTY or another SSH utility.

30. [ ] Use the following procedure to establish communication with an NS-series Control Station.

a. Connect the NULL modem cable to the front of the Control Station and to the service laptop.

b. Open a HyperTerminal session as follows:

c. From the Start Menu, select Programs > Accessories > Communications > HyperTerminal.

d. Enter a session name and click OK.

e. Select the COM port the cable connects to in the Connect Using box and click OK.

f. Enter the following port settings; then click OK.

Bits per second: 19200 Flow Control: None

Data bits: 8 Emulation: Auto Detect

Parity: None Telnet terminal ID: ANSI

Stop bits: 1

g. Open the Properties window and click the Settings Tab. Select Auto Detect in the Emulation box and ANSI in the Telnet terminal ID box.

h. Emulation box and ANSI in the Telnet terminal ID box.

31. [ ] Log onto the Control Station as nasadmin.

login:nasadmin

32. [ ] Become the root user.

$ suPassword:33. [ ] Enter the command below to copy the upgrd-ck script from the floppy to the Celerra.

# mcopy a:upgrd-ckv10-19p.tar.gz upgrd-ckv10-19p.tar.gzFile "upgrd-ckv10-19p.tar.gz" exists, overwrite (y/n) ? y

34. [ ] Wait for the # prompt to return.

35. [ ] Enter ls –l and verify that the copied files is the correct size.

# ls -l up*-rwxr-xr-x 1 root bin 1434304 Jan 7 15:54 upgrd-ckv10-19p.bin-rw-r--r-- 1 root root 1171837 Feb 4 13:06 upgrd-ckv10-9p.tar.gz

document.doc 11


Using Untar and Unzip: 36. [ ] To untar and unzip the file upgrd-ckvxx-xxx.tar.gz enter the command shown below.

# tar xvfz upgrd-ckv10-19p.tar.gzupgrd-ckv10-19p.bincheck_nas_upgrade_5.4.31.2.tar.gzcheck_nas_upgrade_5.5.31.6.tar.gzconnectivity2212007.tar.gzlogcoltrans.tar.gz

document.doc 12


autolog collection scripts 37. [ ] The autolog collection scripts will also be installed on all Celerras running NAS code 5.1 or higher with this version of the upgrd-ck script. The installation will be skipped if the tool is already installed and running on the Control Station.

38. [ ] There is a separate user’s document (Celerra Automatic Log collection tool) available on the above Website. This tool when installed, will automatically collect logs and handle Data Mover panic dumps. By default it is not configured to transmit this information to EMC, but will create log files on the Control Station. It can be configured to ftp these logs to EMC, consult the user documentation, for instructions on setting this up.

39. [ ] If you do not wish to install this tool, simply remove the “logcoltrans.tar.gz” file before running the upgrd-ck script. If you wish to uninstall the autolog collector after it has been installed do the following:

a. Change directory to the installation directory

cd /home/nasadmin/logcoltransb. Uninstall the application

# ./UNINSTALLc. Starting deleting files....

EventLog : will unload /nas/site/automaticcollection-cs.cfg... doneEventLog : will unload /nas/site/automaticcollection-ui.cfg... doneDone.

40. [ ] The backend connectivity monitor tool will be installed on all Celerras running NAS code 5.4 or higher with this version of the upgrd-ck script. The installation will be skipped if the tool is already installed and running on the Control Station.

41. [ ] There is a separate user’s document (Celerra Connection Change Monitor) available on the above Website. This tool will monitor changes to the backend (Fibre Channel ) configuration, and log changes discovered. This tool can be configured to monitor Fibre Switch Changes, but is not configured to do so by default. Consult the user’s document for further information.

42. [ ] If you do not wish to install this tool, simply remove the “connectivity.tar.gz” file before running the upgrd-ck script. If you wish to uninstall the connection monitor after it has been installed do the following:

a. Change directory to the installation directory

# cd /home/nasadmin/connectivity_check

b. Uninstall the application

# ./UNINSTALL

c. The uninstall script removes everything in the /celerra, including the directory itself.

Starting removing files....Remove execution of the feature in /etc/init.d/nasRemove execution of the feature in /nas/site/cron.d/nas_sysDone.

Run the script before the upgrade The script should be run just prior to the NAS code upgrade and then again the upgrade has completed. It can also be run as a quick health check of the Celerra.

document.doc 13


To run the script before the code upgrade:

43. [ ] Become the root user

su 44. [ ] Enter the following command to start the script :

/home/nasadmin/upgrd-ckv10-5.bin -v 1

Note: If you wish to backup configuration files, use “-vb 1” switch instead and file backup will also be run. There are many other switch combinations which can be used, these are explained in Appendix 4 of this document.

[Sample script output]

[root@hammer1 nasadmin]# ]# ./upgrd-ckv10-13.bin -v 1options vrun level is 1Tue Aug 28 07:58:28 EDT 2007 upgrd-ckv10-13

########################################################### This script will log all activity to: /home/nasadmin/pre-upgrade.rpt# 59 days left before script expires # As a best practice you should verify this is the latest# version of the script.## NOTICE *** UUNET numbers are not available for use effective 12/31/2007.# Please check emc82645 for further instructions.##########################################################

UPGRD-CK Version: 10-13 v 1 /nas 5.5.26.1 Celerra: hammer1 Serial Number: FCNHH050500031 modem# 15003 VERIFY MODE TURNED ON##########################################################

Pre-upgrade checker run: Tue Aug 28 07:58:28 EDT 2007Enter the number that corresponds to the version of NAS code you will be upgrading to:

1 NAS 5.4 2 NAS 5.53 NAS 5.3 or lower3

3. Enter the number which corresponds to the version of NAS code you are upgrading to.Then the test will continue.

Installing 5.5 nas_check_upgrade scripts .................... NOT INSChecking for old logcollector ............................... SKIPChecking for installed logcollector ......................... PassedChecking for installed configuration monitor ................ PassedCleanup logcollector and connectivity tar files ............. SKIPChecking minimum NAS code version ........................... PassedCheck /nbsnas is mounted ................................... PassedCheck /nas/dos is mounted ................................... PassedCheck /nas is mounted ....................................... PassedCheck /nas/var is mounted ................................... PassedCheck NAS Services are running .............................. PassedChecking /etc/nsswitch.conf entries ......................... PassedChecking server entries in /etc/hosts file .................. Passed

document.doc 14


Checking Control Station entries in /etc/hosts file ......... PassedChecking NS600 DM Hardware revision ......................... PassedCheck nas_server command present ............................ PassedChecking number of data movers .............................. PassedChecking for failed over data movers ........................ PassedChecking DM is at RC 5 ...................................... PassedChecking param for link speed of be0 and be1 ................ PassedChecking DM xlt files ....................................... PassedCheck for duplicate nas_disk entries ........................ PassedDiscovering disks ........................................... PassedChecking for multiple LUN 0s ................................ PassedChecking that all configured backends are discovered ........ PassedChecking that all discovered backends are configured ........ PassedChecking DM root_fs exist ................................... PassedChecking DM root_fs extension ............................... Passed######## Performing file system checks this could take a while #####Checking the maximum number of file systems per Celerra ..... PassedChecking the maximum number of file systems per data mover .. PassedChecking for MPD exclude file ............................... PassedCheck DM File systems for ETA EMC122604 applicability ....... PassedChecking for Compat type file systems ....................... PassedChecking for DIR3 type file systems ........................ PassedChecking data mover non-MPD fs free space ................... PassedChecking data mover MPD fs free space ....................... PassedChecking ISCSI for ETA EMC141515 exposure ................... SKIPChecking for ETA143208 exposure ............................. PassedChecking for UPS AC loss condition .......................... PassedChecking for correct nodes and dnlc settings ................ PassedChecking for IWD running on CS .............................. PassedChecking CS external interface ...................... eth3 FD PassedChecking /boot free space ............................... 90% PassedChecking /nas free space ................................ 70% PassedChecking /nbsnas free space ............................. 59% PassedChecking / free space ................................... 57% PassedChecking /nas/dos free space ............................ 72% PassedChecking /nas/var free space ............................ 95% PassedChecking nas_eventlog.cfg file loaded ....................... PassedChecking for timefinder fs with mirror on .................. PassedChecking for current backups of nas_db ................... 9 PassedCollecting control station network config ................... PassedCollecting control station cron information ................. PassedChecking for correct DM model, and memory size .............. PassedCollecting Symm device information .......................... PassedChecking SymmAPI is in sync ................................. PassedChecking Symm Device emulation type ......................... PassedChecking SRDF feature ....................................... SkipChecking DM unique ID matches ............................... PassedChecking DM dart version does not match CS version ......... PassedChecking data mover Hostname ................................ PassedChecking DM pre-upgrade mounted file systems ................ PassedChecking DM file system capacity ............................ PassedChecking DM exported file system post-upgrade ............... PassedChecking DM standby relationships ........................... PassedCollecting DM server_sysconfig information .................. PassedCollecting DM server_ifconfig data ......................... PassedCollecting DM nas_server -i information ..................... PassedChecking for internal usermapper ............................ PassedChecking for either internal and external usermapper running Passed##### Checking NAS Params will take a little while.............#####Checking for param values changed by NAS upgrade ............ PassedChecking for param values no longer visible after upgrade ... PassedChecking the number of NAS params visible ................... Passed

document.doc 15


Checking NAS params not at default values ................... PassedRunning nas_check_upgrade checks ............................ WARNAll Tests Completed !

###################################Script run completed at Thu Mar 8 08:19:35 EST 2007

######################################################################THERE WERE (1) FAILURES DETECTED ON THIS RUN.PLEASE EXAMINE THE LOGFILE FOR DETAILS.

The log for this script is in /home/nasadmin/pre-upgrade.rpt !

Please Consult the "Celerra upgrd-ck script User Guide" Document and Primus for Help resolving any issues.

When reporting problems, or requesting assistance please include the following file: /home/nasadmin/lists-tar-hammer1-1173359975-1.tar.gz

[root@hammer1 nasadmin]#

45. [ ] Examine the log file for additional details about failures noted, check the error section of this document and the Primus Solution for each error if additional information is necessary. In this example we see that we had a Warning returned from nas_check_grade script.

document.doc 16


Analyze the pre-upgrade log dataExamine the pre-upgrade.rpt file to see the details of the tests run and failures found. In this example we see that check_nas_upgrade script has found 1 item which results in a warning. The script will classify issues found as information, warnings or errors. Issues which appear in this file which are classified as errors must be corrected before the NAS code upgrade can begin. The recommended corrective action for the check_nas_upgrade script issues found appear in this log following the script run log.

more /home/nasadmin/pre-upgrade.rptmore /home/nasadmin/pre-upgrade.rptTue Aug 28 07:58:28 EDT 2007 upgrd-ckv10-13

########################################################### This script will log all activity to: /home/nasadmin/pre-upgrade.rpt# 59 days left before script expires # As a best practice you should verify this is the latest# version of the script.###########################################################

UPGRD-CK Version: 10-13 v 1 /nas 5.6.26.1 Celerra: hammer1 Serial Number: FCNHH050500031 modem# 15003 VERIFY MODE TURNED ON##########################################################

Pre-upgrade checker run: Tue Aug 28 07:58:28 EDT 2007Installing 5.5 nas_check_upgrade scripts .................... NOT INSChecking for old logcollector ............................... SKIPChecking for installed logcollector ......................... PassedChecking for installed configuration monitor ................ PassedCleanup logcollector and connectivity tar files ............. SKIPChecking minimum NAS code version ........................... PassedCheck /nbsnas is mounted ................................... PassedCheck /nas/dos is mounted ................................... PassedCheck /nas is mounted ....................................... PassedCheck /nas/var is mounted ................................... PassedCheck NAS Services are running .............................. PassedChecking /etc/nsswitch.conf entries ......................... PassedChecking server entries in /etc/hosts file .................. PassedChecking Control Station entries in /etc/hosts file ......... PassedChecking NS600 DM Hardware revision ......................... PassedCheck nas_server command present ............................ PassedChecking number of data movers .............................. PassedChecking for failed over data movers ........................ PassedChecking DM is at RC 5 ...................................... PassedChecking param for link speed of be0 and be1 ................ PassedChecking DM xlt files ....................................... PassedCheck for duplicate nas_disk entries ........................ PassedDiscovering disks ........................................... PassedChecking for multiple LUN 0s ................................ PassedChecking that all configured backends are discovered ........ PassedChecking that all discovered backends are configured ........ PassedChecking DM root_fs exist ................................... PassedChecking DM root_fs extension ............................... Passed######## Performing file system checks this could take a while #####Checking the maximum number of file systems per Celerra ..... PassedChecking the maximum number of file systems per data mover .. PassedChecking for MPD exclude file ............................... PassedCheck DM File systems for ETA EMC122604 applicability ....... PassedChecking for Compat type file systems ....................... PassedChecking for DIR3 type file systems ........................ Passed

document.doc 17


Checking data mover non-MPD fs free space ................... PassedChecking data mover MPD fs free space ....................... PassedChecking ISCSI for ETA EMC141515 exposure ................... SKIPChecking for ETA143208 exposure ............................. PassedChecking for UPS AC loss condition .......................... PassedChecking for correct nodes and dnlc settings ................ PassedChecking for IWD running on CS .............................. PassedChecking CS external interface ...................... eth3 FD PassedChecking /boot free space ............................... 90% PassedChecking /nas free space ................................ 70% PassedChecking /nbsnas free space ............................. 59% PassedChecking / free space ................................... 57% PassedChecking /nas/dos free space ............................ 72% PassedChecking /nas/var free space ............................ 95% PassedChecking nas_eventlog.cfg file loaded ....................... PassedChecking for timefinder fs with mirror on .................. PassedChecking for current backups of nas_db ................... 9 PassedCollecting control station network config ................... PassedCollecting control station cron information ................. PassedChecking for correct DM model, and memory size .............. PassedCollecting Symm device information .......................... PassedChecking SymmAPI is in sync ................................. PassedChecking Symm Device emulation type ......................... PassedChecking SRDF feature ....................................... SkipChecking DM unique ID matches ............................... PassedChecking DM dart version does not match CS version ......... PassedChecking data mover Hostname ................................ PassedChecking DM pre-upgrade mounted file systems ................ PassedChecking DM file system capacity ............................ PassedChecking DM exported file system post-upgrade ............... PassedChecking DM standby relationships ........................... PassedCollecting DM server_sysconfig information .................. PassedCollecting DM server_ifconfig data ......................... PassedCollecting DM nas_server -i information ..................... PassedChecking for internal usermapper ............................ PassedChecking for either internal and external usermapper running Passed##### Checking NAS Params will take a little while.............#####Checking for param values changed by NAS upgrade ............ PassedChecking for param values no longer visible after upgrade ... PassedChecking the number of NAS params visible ................... PassedChecking NAS params not at default values ................... PassedRunning nas_check_upgrade checks ............................ WARNCheck Version:5.5.25.2Check Command:/tmp/check_nas_upgradeCheck Log :/nas/log/check_nas_upgrade.Aug-28-07:59:06.log

-------------------------------------Checks-----------------------------------Control Station: Checking if enough free space exists ns................. PassControl Station: Checking if NAS Storage API is installed correctly...... PassControl Station: Checking if NBS clients are started..................... PassControl Station: Checking if NBS configuration exists.................... PassControl Station: Checking if NBS devices are accessible.................. PassControl Station: Checking if NBS service is started...................... PassControl Station: Checking if NIS is stopped.............................. FailControl Station: Checking if standby is down............................. PassControl Station: Checking if Symapi data is present...................... PassControl Station: Checking if Symapi is synced with Storage System........ PassControl Station: Checking integrity of NASDB............................. PassControl Station: Checking that no cron jobs are scheduled................ PassControl Station: Checking all callhome files delivered................... PassControl Station: Checking resolv conf.................................... PassControl Station: Checking if NAS partitions are mounted.................. Pass

document.doc 18


Control Station: Checking there is no exclusion file for MPD translation. PassControl Station: Checking nas sys mcd configuration...................... PassControl Station: Checking nas sys eventlog configuration................. PassData Movers : Checking boot files..................................... PassData Movers : Checking if hardware is supported....................... PassData Movers : Checking if primary is active........................... PassData Movers : Checking if root filesystem has enough free space....... PassData Movers : Checking if using standard DART image................... PassData Movers : Checking network connectivity........................... PassData Movers : Checking status......................................... PassData Movers : Checking dart release compatibility..................... PassData Movers : Checking dart version compatibility..................... PassStorage System : Checking disk emulation type............................ PassStorage System : Checking disk high availability access.................. PassStorage System : Checking disks read cache enabled....................... PassStorage System : Checking disks and storage processors write cache enabledPassStorage System : Checking if access logix is enabled..................... PassStorage System : Checking if FLARE is committed.......................... PassStorage System : Checking if FLARE is supported.......................... PassStorage System : Checking if microcode is supported...................... PassStorage System : Checking no disks or storage processors are failed over..PassStorage System : Checking that no disks or storage processors are faulted.PassStorage System : Checking that no hot spares are in use.................. PassStorage System : Checking that no hot spares are rebuilding.............. PassStorage System : Checking control lun size............................... Pass------------------------------------------------------------------------------One or more warnings are shown below. It is recommended that you follow theinstructions below to correct the problem then try again. ------------------------------------Warnings----------------------------------Control Station: Check if NIS is stoppedSymptom: NIS is running on the Control Station. It will be shutdown during the upgrade and restarted after the upgrade completes Action : If you do not want the upgrade to do this for you, shutdown NIS manually before the upgrade by running command "/etc/init.d/ypbind stop", and restart it after the upgrade by running command "/etc/init.d/ypbind start".------------------------------------------------------------------------------All Tests Completed !

###################################Script run completed at Thu Mar 8 08:19:35 EST 2007

######################################################################

THERE WERE (1) FAILURES DETECTED ON THIS RUN.PLEASE EXAMINE THE LOGFILE FOR DETAILS.The log for this script is in /home/nasadmin/pre-upgrade.rpt !



[root@hammer1 nasadmin]#

Note: The NIS test line says “Failed” yet the error is categorized as a warning. This is way all check_nas_upgrade tests will handle issues found.

document.doc 19


Failure CountsThe failure count displayed when the script completes, does not count Warnings as errors, except in the case where the check_nas_upgrade script has been run and returns a reason code greater than 0. In that case it will count as one failure, even if the check_nas_upgrade scripts uncovered multiple errors. Check the log specified in the message to determine what failures were encountered.

eg.

THERE WERE (2) FAILURES DETECTED ON THIS RUN.

PLEASE EXAMINE THE LOGFILE FOR DETAILS.

The log for this script is in /home/nasadmin/post-upgrade.rpt !


What to file with your CCA requestWhen filing your CCA request always attach the file

/home/nasadmin/lists-tar-<hostname>-<date stamp>.tar.gz to the CCA.

Run the script post upgradeAfter the NAS code upgrade has completed, run the upgrd-ck script using the “-v 2” option to run the Post upgrade checks.

[root@hammer1 nasadmin]# ./upgrd-ckv10-13.bin -v 2options vrun level is 2Tue Aug 28 10:32:51 EDT 2007 upgrd-ckv10-13

########################################################### This script will log all activity to: /home/nasadmin/post-upgrade.rpt# 59 days left before script expires# As a best practice you should verify this is the latest# version of the script.###########################################################

POST UPGRD-CK Version: 10-13 v 2 /nas 5.6.26.1Celerra: hammer1 Serial Number: FCNHH050500031 modem# 15003VERIFY MODE TURNED ON##########################################################

Post upgrade checker run: Tue Aug 28 10:32:51 EDT 2007

Checking for old logcollector ............................... SKIPChecking for installed logcollector ......................... PassedChecking for installed configuration monitor ................ PassedCleanup logcollector and connectivity tar files ............. SKIPChecking minimum NAS code version ........................... PassedCheck /nbsnas is mounted ................................... PassedCheck /nas/dos is mounted ................................... PassedCheck /nas is mounted ....................................... PassedCheck /nas/var is mounted ................................... PassedCheck NAS Services are running .............................. Passed

document.doc 20


Checking /etc/nsswitch.conf entries ......................... PassedChecking server entries in /etc/hosts file .................. PassedChecking Control Station entries in /etc/hosts file ......... PassedChecking NS600 DM Hardware revision ......................... PassedCheck nas_server command present ............................ PassedChecking number of data movers .............................. PassedChecking for failed over data movers ........................ PassedChecking Post Upgrade DM ACL setting ........................ FAILEDChecking DM is at RC 5 ...................................... PassedChecking param for link speed of be0 and be1 ................ PassedChecking DM xlt files ....................................... PassedCheck for duplicate nas_disk entries ........................ PassedDiscovering disks ........................................... PassedChecking for multiple LUN 0s ................................ PassedChecking that all configured backends are discovered ........ PassedChecking that all discovered backends are configured ........ PassedChecking DM root_fs exist ................................... PassedChecking DM root_fs extension ............................... Passed######## Performing file system checks this could take a while #####Checking the maximum number of file systems per Celerra ..... PassedChecking the maximum number of file systems per data mover .. PassedChecking for MPD exclude file ............................... PassedCheck DM File systems for ETA EMC122604 applicability ....... PassedChecking for Compat type file systems ....................... PassedChecking for DIR3 type file systems ........................ PassedChecking data mover non-MPD fs free space ................... PassedChecking data mover MPD fs free space ....................... PassedChecking ISCSI for ETA EMC141515 exposure ................... SKIPChecking for ETA143208 exposure ............................. PassedChecking for UPS AC loss condition .......................... PassedChecking for correct nodes and dnlc settings ................ PassedChecking for IWD running on CS .............................. PassedChecking CS external interface ...................... eth3 FD PassedChecking nas_eventlog.cfg file loaded ....................... PassedChecking for correct DM model, and memory size .............. PassedCollecting Symm device information .......................... PassedChecking SymmAPI is in sync ................................. PassedChecking Symm Device emulation type ......................... PassedChecking SRDF feature ....................................... SkipChecking DM unique ID matches ............................... PassedChecking DM mac addr matches ............................... PassedChecking DM dart version does not match CS version ......... PassedChecking data mover Hostname ................................ PassedChecking DM post upgrade mounted file system ................ PassedChecking DM file system capacity ............................ PassedChecking DM exported file system post-upgrade ............... PassedChecking DM standby relationships ........................... PassedCollecting DM server_sysconfig information .................. PassedCollecting DM server_ifconfig data ......................... PassedCollecting DM nas_server -i information ..................... PassedChecking Upgrade log for errors ............................. PassedChecking for internal usermapper ............................ PassedChecking for either internal and external usermapper running PassedChecking for pre-upgrade cksum file ......................... PassedChecking for post-upgrade cksum file ........................ PassedChecking for site cksum file ................................ Passed##### Checking NAS Params will take a little while.............#####Checking for param values changed by NAS upgrade ............ PassedChecking for param values no longer visible after upgrade ... PassedChecking the number of NAS params visible ................... PassedChecking NAS params not at default values ................... PassedAll Tests Completed !

document.doc 21


###################################Script run completed at Tue Aug 28 10:41:01 EDT 2007

######################################################################

THERE WERE (1) FAILURES DETECTED ON THIS RUN.PLEASE EXAMINE THE LOGFILE FOR DETAILS.The log for this script is in /home/nasadmin/post-upgrade.rpt !



Analyze the post upgrade log dataUsing the previous section as an example we see from looking at the script after the script has completed that (1) problem was found “Checking Post Upgrade DM ACL setting ........... FAILED”.

To get additional information about the failure you should look at the detail log specified on the screen. “/home/nasadmin/post-upgrade.rpt”. Use the more command to examine the log, note that all test were completed and that error E000107 is related to the ACL failure, you can read the text included with the message and also reference Appendix 1 for additional information and the Primus Solution number for this error.

[root@hammer1 nasadmin]# more /home/nasadmin/post-upgrade.rpt Tue Aug 28 10:32:51 EDT 2007 upgrd-ckv10-13

########################################################### This script will log all activity to: /home/nasadmin/post-upgrade.rpt# 59 days left before script expires# As a best practice you should verify this is the latest# version of the script.###########################################################

POST UPGRD-CK Version: 10-13 v 2 /nas 5.6.26.1Celerra: hammer1 Serial Number: FCNHH050500031 modem# 15003VERIFY MODE TURNED ON##########################################################

Post upgrade checker run: Tue Aug 28 10:32:51 EDT 2007Checking for old logcollector ............................... SKIPChecking for installed logcollector ......................... PassedChecking for installed configuration monitor ................ PassedCleanup logcollector and connectivity tar files ............. SKIPChecking minimum NAS code version ........................... PassedCheck /nbsnas is mounted ................................... PassedCheck /nas/dos is mounted ................................... PassedCheck /nas is mounted ....................................... PassedCheck /nas/var is mounted ................................... PassedCheck NAS Services are running .............................. Passed

document.doc 22


Checking /etc/nsswitch.conf entries ......................... PassedChecking server entries in /etc/hosts file .................. PassedChecking Control Station entries in /etc/hosts file ......... PassedChecking NS600 DM Hardware revision ......................... PassedCheck nas_server command present ............................ PassedChecking number of data movers .............................. PassedChecking for failed over data movers ........................ PassedChecking Post Upgrade DM ACL setting ........................ FAILEDChecking DM is at RC 5 ...................................... PassedChecking param for link speed of be0 and be1 ................ PassedChecking DM xlt files ....................................... PassedCheck for duplicate nas_disk entries ........................ PassedDiscovering disks ........................................... PassedChecking for multiple LUN 0s ................................ PassedChecking that all configured backends are discovered ........ PassedChecking that all discovered backends are configured ........ PassedChecking DM root_fs exist ................................... PassedChecking DM root_fs extension ............................... Passed######## Performing file system checks this could take a while #####Checking the maximum number of file systems per Celerra ..... PassedChecking the maximum number of file systems per data mover .. PassedChecking for MPD exclude file ............................... PassedCheck DM File systems for ETA EMC122604 applicability ....... PassedChecking for Compat type file systems ....................... PassedChecking for DIR3 type file systems ........................ PassedChecking data mover non-MPD fs free space ................... PassedChecking data mover MPD fs free space ....................... PassedChecking ISCSI for ETA EMC141515 exposure ................... SKIPChecking for ETA143208 exposure ............................. PassedChecking for UPS AC loss condition .......................... PassedChecking for correct nodes and dnlc settings ................ PassedChecking for IWD running on CS .............................. PassedChecking CS external interface ...................... eth3 FD PassedChecking nas_eventlog.cfg file loaded ....................... PassedChecking for correct DM model, and memory size .............. PassedCollecting Symm device information .......................... PassedChecking SymmAPI is in sync ................................. PassedChecking Symm Device emulation type ......................... PassedChecking SRDF feature ....................................... SkipChecking DM unique ID matches ............................... PassedChecking DM mac addr matches ............................... PassedChecking DM dart version does not match CS version ......... PassedChecking data mover Hostname ................................ PassedChecking DM post upgrade mounted file system ................ PassedChecking DM file system capacity ............................ PassedChecking DM exported file system post-upgrade ............... PassedChecking DM standby relationships ........................... PassedCollecting DM server_sysconfig information .................. PassedCollecting DM server_ifconfig data ......................... PassedCollecting DM nas_server -i information ..................... PassedChecking Upgrade log for errors ............................. PassedChecking for internal usermapper ............................ PassedChecking for either internal and external usermapper running PassedChecking for pre-upgrade cksum file ......................... PassedChecking for post-upgrade cksum file ........................ PassedChecking for site cksum file ................................ Passed##### Checking NAS Params will take a little while.............#####Checking for param values changed by NAS upgrade ............ PassedChecking for param values no longer visible after upgrade ... PassedChecking the number of NAS params visible ................... PassedChecking NAS params not at default values ................... PassedAll Tests Completed !

document.doc 23


###################################Script run completed at Tue Aug 28 10:41:01 EDT 2007

######################################################################E00107: Data Mover ACL setting changed by NAS code upgrade.The file (/home/nasadmin/preServerAcl.rpt) contains the setting before theupgrade, (/home/nasadmin/postServerAcl.rpt) contains the current values.Use the nas_server -list command to display current settings,use the nas_server -acl <value> <server_name> to correct the settings.

THERE WERE (1) FAILURES DETECTED ON THIS RUN.PLEASE EXAMINE THE LOGFILE FOR DETAILS.

The log for this script is in /home/nasadmin/post-upgrade.rpt !Please Consult the "Celerra upgrd-ck script User Guide" Document and Primus for Help resolving any issues.When reporting problems, or requesting assistance please include the following file: /home/nasadmin/lists-tar-hammer1-1173358763-2.tar.gz

File Clean upAfter you have completed the NAS code upgrade, you may want to remove some of the log files to free up some space in the /home/nasadmin directory, you can remove the .rpt files.

WARNING: Extreme care should be used whenever using a Wild Card character while doing removes, so that you do not remove files that were not intended to be removed.

Note: You can specify the specific names for those files you wish to remove or use the Wild Card “*“ to remove all such files.

# rm /home/nasadmin/*.rpt

You can also remove the lists* files to free up additional space, although you may want to keep the most recent copies of the lists files.

ls -l lists*

-rw-r--r-- 1 root root 114778 Mar 7 15:21 lists-tar-hammer1-1173298863-2.tar.gz

-rw-r--r-- 1 root root 115598 Mar 7 21:29 lists-tar-hammer1-1173320993-1.tar.gz

# rm lists-*.tar.gz

document.doc 24


Using cpgInput.rpt as the Configuration Source for NAS Code UpgradesTo create a customized upgrade procedure, you must first provide specific information regarding the current hardware and software configuration of the Celerra server. This task is simplified through the use of a script that captures the necessary information in a configuration file to feed into the Celerra Procedure Generator.

In addition, you must resolve any problem conditions that could cause the upgrade to fail. The script checks the current state of the server and creates a report detailing any conditions that you need to correct before performing an upgrade.

Once the configuration file is created and any existing error conditions on the Celerra are resolved, you can run the Celerra Procedure Generator to create the upgrade procedure.

An overview of the steps involved in using the Celerra Procedure Generator is listed below. Details on each step are included in the pages that follow.

Extract the script from the Celerra Procedure Generator folder Copy the script to the Celerra Control Station Change permissions on the script to make it executable Run the script to create the configuration input file for the Celerra Procedure Generator and perform

the pre-upgrade health check on the server Note and resolve any problems uncovered by the health check Copy the configuration input file to you laptop Run the Celerra Procedure Generator Use the resulting upgrade procedure to perform the NAS upgrade.

Step 1: Extract upgrd-ckX.tar.gz script bundle from NASCPG FolderOn your laptop, browse to the NASCPG > Application > Modules > SCRIPTS folder and locate the file named upgrd-ckvX.tar.gz as shown in the screenshot below.

Note: The vX in the script name indicates the version number of the script.

Figure 1 Locate the upgrd-ckvX.tar.gz file

document.doc 25


Step 2: Copy upgrd-ck Script to Control StationCopy the upgrd-ckvX.tar.gz file to the /home/nasadmin directory on the Control Station of the Celerra server. This can be accomplished using a variety of methods:

Copy the script to a floppy diskette, mount the floppy on the Control Station and copy the script to the /home/nasadmin directory.

# mount /dev/fd0 /mnt# cp /mnt/upgrd-ckvX.bin /home/nasadmin# umount /dev/fd0

Use ftp or another file transfer method of your choosing to copy the script to the /home/nasadmin directory.

Untar the upgrd-ck script bundle

# tar xvfz upgrd-ckv10-0.tar.gzcheck_nas_upgrade_5.4.25.1.tar.gzcheck_nas_upgrade_5.5.24.2.tar.gzlogcoltrans.tar.gzconnectivity.tar.gz

Step 3: Change file permissions to make the script executableOnce the upgrd-ckvX.bin script is copied to the Control Station, use the chmod command to change the permissions on the script to make it executable:

# chmod +x /home/nasadmin/upgrd-ckv*

Step 4: Create Configuration File and Perform Pre-upgrade ChecksAs root, run the upgrd-ckvX.bin script in verify mode as shown below. The script examines the Celerra system and create a configuration filenamed cpgInput.rpt. This file is used later with the Celerra Procedure Generator to create the upgrade procedure.

# ./upgrd-ckv10-21.bin -v 1

options vrun level is 1Sun Mar 9 19:25:52 EDT 2008 upgrd-ckv10-21

########################################################### This script will log all activity to: /home/nasadmin/pre-upgrade.rpt# 58 days left before script expires# As a best practice you should verify this is the latest# version of the script.##########################################################

UPGRD-CK Version: 10-21 v 1 /nas 5.6.36.2Celerra: la5 Serial Number: ML2809000146 modem# 918005270941VERIFY MODE TURNED ON##########################################################

Pre-upgrade checker run: Sun Mar 9 19:25:52 EDT 2008Enter the number that corresponds to the version of NAS codeyou will be upgrading to:

1 NAS 5.42 NAS 5.53 NAS 5.64 NAS 5.3 or lower

document.doc 26


At the prompt, enter a 1 if you are upgrading to 5.4 or 2 for 5.5 or 3 for 5.6 or 4 for 5.3 or lower or if you do not wish to install and run the check_nas_upgrade script. The script then performs the pre-upgrade health check on the Celerra. The results of the health check is logged to a file named pre-upgrade.rpt. in the /home/nasadmin directory.

Step 5: Check the script output for error conditionsThe last few lines of the script output display a count of any error or warning conditions encountered on the Celerra that might prevent a successful upgrade.

Always look for the All Tests Completed ! line, which indicates that the script ran to completion. Some checks cause the script to exit before completion. If this should occur examine the log file for errors and correct these errors before continuing.

All Tests Completed !

###################################Script run completed at Sun Mar 9 19:35:10 EDT 2008

######################################################################

THERE WERE (1) FAILURES and (3) WARNINGS DETECTED ON THIS RUN.PLEASE EXAMINE THE LOGFILE FOR DETAILS.


Please Consult the "Celerra upgrd-ck script User Guide" Document and Primus forHelp resolving any issues.

When reporting problems, or requesting assistance please include the following file: /home/nasadmin/lists-tar-la5-1205105710-1.tar.gz

(This information can also be found in the pre-upgrade.rpt file in the /home/nasadmin directory). You must resolve these problems before you attempt the NAS code upgrade.

For example, the sample output below identified three issues. When you examine the pre-upgrade.rpt file, you see the summary of all Checks run and any errors or warnings encountered.

In this example:

There is a Data Mover (server_2) failed over (E000012 & E000073) and ESRS (W000102) is configured and running on this Celerra.

Sample Output:######################################################################E000012: Data mover server_2.faulted.server_3 failed over ! You must fail the data mover back before continuing this upgrade.E000073: server_standby server_2 -v command failed.W000102: ESRS is configured and loaded on this Celerra.If you are upgrading to 5.5.31.x or higher leave the rsc5*_nas_event.cfg fileloaded.If you are upgrading to 5.5.30.x or below, just prior to the start of the NAScode upgrade you should unload its event file, to prevent un-necessary dialhomes during the NAS code upgrade. Use the following command to do this: /nas/bin//nas_event -U /nas/site/rsc5527_nas_event.cfg. After the NAS code upgrade has completed you will need to re-load the correct ESRS event configuration file to restart the service.

THERE WERE (2) FAILURES and (1) WARNINGS DETECTED ON THIS RUN.PLEASE EXAMINE THE LOGFILE FOR DETAILS.


document.doc 27


Step 6: Copy the cpginput.rpt configuration file to your laptopAs mentioned in the Step 5, the upgrd-ck script creates a file containing specific configuration information about the Celerra you plan to upgrade. This configuration file is saved to /home/nasadmin /cpgInput.rpt. The file is used as input to the Celerra Procedure Generator, saving you the trouble of manually selecting the various configuration options required by the Celerra Procedure Generator. Copy the file to your laptop using FTP or a floppy diskette.

Sample cpginput.rpt Contents:

Celerra CPG Input for laip2 Thu Sep 29 08:47:45 EDT 2005CKPT: yesCLARIION BACKEND: yes APM00030600872MPD FS: yesCIFS CONFIGURED: yesVDM CONFIGURED: yesDHSM: yesHIGHRD: noISCSI: noDUAL CS: noREPLICATION: yesNUMBER OF BACKENDS: 1SERIAL NUMBER: APM00030600872NAS_VERSION: 5.5BOX_TYPE: 3MODEL: NS700 MODEL: NS700 INTERNAL USRMAPPER: yes

document.doc 28


Step 7: Run the Celerra Procedure Generator On your laptop, click Start > Programs NAS Generator to start the Celerra Procedure Generator.

The Celerra Procedure Generator Select Activity screen appears (Figure 2). Click the hand icon to proceed to the next screen of the Procedure Generator.

Figure 2 Click Hand Icon

In the New Procedure window, enter all the customer, site, and activity-related information in the appropriate fields as shown in Figure 3. Do not click the hand icon when you are finished.

Figure 3 Enter Site and Activity Information

document.doc 29


Select File > Open from the menu bar. In the File name: field enter cpgInput.rpt and click Open.

Figure 4 Create a Filename

The Open window close, and the New Procedure window is visible again. Click the hand icon to continue.

Figure 5 Click Hand Icon

document.doc 30


The Select Activity Type window appears (Figure 6). Click Software Upgrades on the selection screen and click the hand icon to continue.

Figure 6 Select Activity Screen

document.doc 31


The NAS Code Upgrade window appears (Figure 7). The appropriate selections should already be checked off (as in the screen shot below) as a result of the configuration file that was provided as input earlier in the process.

Note: Although the Current NAS Version is also supplied, you must still select it from the drop down menu drop-down menu. Then select the appropriate NAS code version you are upgrading to from the New NAS Version

Figure 7 NAS Code Upgrades Screen

If the selections on the NAS Code Upgrade window are correct,

1. Select the Current NAS version drop down to select the current NAS code version

2. Select the New NAS version to the NAS code family you are upgrading to.

3. Click Generate Document.

This starts the document creation process.

At the Procedure Generator window, enter a name for your document and click OK to continue (Figure 8).

Note: If you wish to Generate a Procedure to simply patch/replace the Dart Image (nas.exe)

1. Do not select the Current NAS version, this grays out this box. Click Clear All to re-enable this selection box.

2. Check the Dart Image Upgrade Only box in the lower right hand corner of the screen (Figure 7).

3. Click Generate Document.

document.doc 32


Figure 8 Create a Filename

Note: The file created is not called upgrade ABC.doc but instead is called upgrade.doc. This is due to a limitation with the software used in the Procedure Generator so only an 8.3 DOS name is preserved.

Microsoft Word opens on your laptop and the document is created. When the process completes, the NAS Code Upgrade window re-appears. Click Exit to terminate the Celerra Procedure Generator.

The newly-created upgrade procedure can be found in the NASCPG > Application > ProcDoc directory on your laptop (Figure 9).

Figure 9 NASCPG > Application > ProcDoc Directory

Open and read the new upgrade procedure immediately as there are steps you should begin well in advance of the scheduled upgrade activity.

document.doc 33


Error MessagesMessage Number

Description Primus Solution Number

E000001 Found that iwd daemon is running on Control Station.It must be shutdown before proceeding with the upgrade.Shut down iwd by entering killall -9 /nasmcd/sbin/iwdThen verify that it has shutdown by doing a ps -ef |grep iwd

EMC118218

E000002 This test will only run if the current NAS code version is 5.3 or higher, it will use the /nas/sbin/dbchk –vx command to do a nas_db check. If the command returns anything except done, it should investigated before doing the NAS code upgrade.

EMC139962

W000003 This test counts the total number of non-root file systems on the VNX. As of NAS 5.4 VNX supports up to 4096 file systems per VNX.

EMC 139964

W000004 This test uses the server_mount server_x command to determine the number of file systems mounted per data mover, a data mover can mount a maximum of 2047 total file systems as of NAS code 5.4

EMC139965

E000005 The data mover serial number entry in the NAS DB for this data mover does not match the serial number returned from the Hardware resume prom.

EMC139966

E000006 This test was unable to determine the SNMP community name for this data mover

EMC140021

E000007 This test was unable to determine the number of network interfaces for this data mover

EMC140051

E000008 This test was unable to determine the name of a network interface for a data mover

EMC140682

E000009 This test was unable to determine the mac address for a network interface on this data mover

EMC140683

E000010 This test could not match the mac address returned from the data mover with the mac address for this data mover

EMC140684

E000011 This test could not match the mac address returned from the data mover with the mac address in the NAS DB entry for this data mover

EMC140685

E000012 This test checks if data mover is failed over EMC140686E000013 Test tried to determine server_version, but was unable to do so

because the data mover was not at rc = 5.EMC140228

E000014 The NAS Code family running on the Control Station does not match the version running on this data mover

EMC140229

E000015 This test determined that the reason code for this data mover is not equal to 5.

EMC140735

E000016 This test determined that this data mover is not setup to boot nas.exe EMC140741E000017 This test has determined that the nas.exe file does not exist EMC140742E000018 This test has determined that this data movers server name does not

match its hostnameEMC140743

E000019 This test has determined that the file systems mounted on this data mover post upgrade does not match the file systems mounted on this data mover prior to the upgrade

EMC140744

E000020 This test has determined that the file systems mounted state on this data mover post upgrade does not match the file systems mounted state on this data mover prior to the upgrade

EMC140745

E000021 This test has determined that the file systems exported by this data mover post upgrade does not match the file systems exported prior to the upgrade

EMC140746

E000022 This test checked the NAS code upgrade log and found an error message

EMC140820

document.doc 34

http://csexplorer.isus.emc.com/eservice/iviewcs/ui/eserver.asp?id=emc140820























E000023 This test found timefinder file systems in mirror on state EMC140821W000024 This test determined that CIFS is configured and that neither internal

or external usermapper are configuredEMC140867

E000025 This test has determined that both internal and external usermapper are configured and running

EMC140755

E000026 This test has determined that no backups for the NAS DB created today exist

EMC140756

E000027 This test has determined that /boot free space is lower than 25% EMC140757E000028 This test has determined that /nas free space is lower than 45% EMC140758E000029 This test has determined that /nbsnas free space is lower than 45% EMC143651E000030 This test has determined that / free space is lower than 20% except

for CNS 14 model which requires 30% free space.EMC140963

E000031 This test has determined that /nas/dos free space is lower than 50% EMC140964E000032 This test has determined that /nas/var free space is lower than 65% EMC140965E000033 This test has determined that /nas/sys/nas_eventlog.cfg file is not

loaded for nas_eventsEMC140966

E000034 This test has determined that NIS is running on the Control Station, it should be stopped prior to NAS code upgrade

EMC140967

E000035 This test has determined that before the NAS code upgrade there were cron jobs in /var/spool/cron, they are missing after the code upgrade

EMC141005

W000036 This test has determined that after the NAS code upgrade the number of data mover params has changed

EMC141006

E000037 This test has determined that the amount of time it took for a navicli getagent command to return was in excess of 5 seconds

EMC141071

E000038 This test has determined that the information returned from a navicli getcrus command indicates there is a problem with the Clariion backend

EMC141089

E000039 This test has determined that LUNs in the range of 6-15are configured on this VNX, these are considered “reserved LUNs”

EMC94879

E000040 This test has determined that the Clariion AutoAssign setting is incorrect for this version of NAS code

EMC141132

E000041 This test has determined that the Clariion AutoTrespass setting is incorrect

EMC141133

E000042 This test has determined that the Clariion write cache is not enabled EMC141134E000043 This test has determined that the Clariion LUNs configured to this

VNX are trespassedEMC141135

E000044 This test has determined that the Clariion LUNs configured to this VNX are currently unowned, by either SP A or SP B.

EMC141215

E000045 E000045: Control LUN <disk name > default owner is not SP A it is (B)

EMC141216

E000046 E000046: Control LUN <disk name> current owner is not SP A it is (B)

EMC141395

E000047 This test has determined that there are file systems currently in a unmounted state on this data mover

EMC141396

E000048 This test has determined that there are non MPD file systems mounted on this data mover that are 90% full, making conversion to DIR3 format impossible.

EMC129149

W000049 This test has determined that there are MPD file systems mounted on this data mover that are 90% full, this information only.

EMC141497

E000050 This test has determined that there may be multiple LUN0 disks configured to this VNX

EMC141498

W000051 This test has determined that the Control LUN sizes are not the expected sizes

EMC141499

document.doc 35































E000052 This test has determined that the param “clariion no_trespass” is set to “1” it should be set to “0” to allow proper data mover recovery.

EMC141593

W000053 This test has determined that a number of params are not set to their default values

EMC141594

E000054 This test has determined that this data mover has tree and group quotas configure din such a way that ETA121367 applies, please consult this ETA before proceeding.

EMC121367

E000055 This test has determined that the number of nodes configured for this data mover does not match the data movers memory model.

EMC141595

E000056 This test has determined that the number of dnlc buffers configured for this data mover does not match the data movers memory model.

EMC141666

E000057 This test has determined that boxmonitor daemon is not running on the Control Station, this is a indication the NAS services are not started

EMC141665

E000058 This test has determined that the /nas partition is not mounted on the Control Station , this maybe a indication the NAS services are not started

EMC141809

E000059 This test has determined that the /nas/dos partition is not mounted on the Control Station , this maybe a indication the NAS services are not started

EMC141810

E000060 This test has determined that the /nas/var partition is not mounted on the Control Station , this maybe a indication the NAS services are not started

EMC141811

E000061 External usrmapper upgrade failed. The current version of external usrmapper is not 3.1.4

EMC141812

E000062 This test has determined that there are a number of Clariion LUNs configured to this data mover that have read cache disabled

EMC141813

E000063 This test has determined that a nmfs system exists on this VNX and this condition requires that ETA EMC122604 be checked before proceeding with the ANS Code upgrade.

EMC122604

E000064 This test has determined that the IP address for a Clariion appearing in the nas_storage –list output can not be located in the /etc/hosts file

EMC141923

W000065 This test has determined that the value of some params have changed as a result of the NAS code upgrade

EMC141924

W000066 This test has determined that some params are no longer visible after the NAS code upgrade

EMC141925

E000067 This test has determined that the there is a duplicate disk entry in the nas disk db.

EMC141926

E000068 This test has determined that the Clariion ArrayCommPath setting is set to “1” for some connectivity path between the VNX and the Clariion it should be “0”

EMC143531

E000069 This test has determined that the Clariion FailOverMode setting is set to “1” for some connectivity path between the VNX and the Clariion it should be “0”

EMC143532

E000070 This test has determined that data mover entries are missing from the /etc/hosts file

EMC141650

E000071 This test has determined that the Control Station entry is msiing from the /etc/hosts file

EMC142013

E000072 This test has determined that this NS600 data mover may need to be upgraded.

EMC133397

E000073

W00073

This test has determined that the server_standby –verify command returned a error.See Primus Solution emc142068 for additional information.

W000073: server_standby $server -v command returned the following

EMC142068

document.doc 36
























warning : < warning message content>

See Primus Solution emc142068 for additional information.

E000074 TEST DELETEDE000075 TEST DELETEDE000076 This test has determined that Symmetrix disks configured to this VNX

do not have their emulation type to VNX_FBA as requiredEMC94067 and EMC142159

E000077 This test has determined that the Control Station external interface link state does not show link ok.

EMC142161

W000078 TEST DELETEDE000079 This test has determined that this Integrated Clariion backend has

layered Software installed.EMC142245

E000080 This test has determined that a MPD exclude file /nas/site/fs_exclude exists, this is no longer supported with NAs code 5.5 and higher

EMC129149

E000081 This test has determined that VNX files systems that have not been converted to DIR3 format exist on this VNX

EMC129149

E000082 This test has determined that VNX COMPAT mode files systems have been found which “NeedTranslation”

EMC129149

E000083 This test has determined that VNX DIR3 mode files systems have been found which “NeedTranslation”

EMC129149

E000084 This test has determined that NAS code version of this VNX is less than 4.2, the script will exit.

EMC142537

E000085 This test has determined that no disks are discovered on a configured backend

EMC142538

E000086 This test has determined that a discovered backend is not configured to this VNX, yet its devices are visible

EMC142539

E000087 This test has determined that the param fcTach linx_speed_be0 or the param linx_speed_be1 are set to 1GB

EMC142829

E000088 TEST DELETEDE000089 TEST DELETEDE000090 TEST DELETEDE000091 This test has determined that the root file system usage for this data

mover exceeds 90%EMC142992

E000092 This test has determined that the Clariion Base Flare Code is not committed

EMC142993

E000093 This test has determined that the root file system for this data mover has been extended using root_disk_reserve

EMC142994

E000094 This test has determined that the /nas/rootfs/slot_x/.etc_common/xlt directory does not exist or is not mounted on this data mover

EMC143514

E000095 This test has determined that the /etc/nsswitch.conf entry for hosts does not have “files” as the first entry, or that the entry for passwd does not have a “ldap” entry on this Control Station.

EMC142995

E000096 This test has determined that the Control Station’s internal network is configured as a class C network

EMC142991

E000097 This test has determined that one more of the required root_fs_* file systems do no exist

EMC142996

E000098 TEST DELETEDE000099 TEST DELETEDE000100 This test has determined that the /nas/symcli/bin/symcfg verify –sid

command returned a errorEMC156165

E000101 This test has determined that the amount of free space available in file systems which contain ISCSI LUNs is insufficient to upgrade to NAS code 5.5 per ETA emc141515ETA emc141515: VNX: iSCSI LUNs become corrupted

EMC141515

document.doc 37























after performing a NAS code upgradeW000102 This test has determined that ESRS is loaded and configured on this

VNX user action is required prior to NAS code upgradeW000103 This test has determined that ESRS is loaded and configured on this

VNX user action is required prior to NAS code upgradeE000104 This test has determined that LDAP service is configured on this data

mover consult ETA emc143208 before proceeding with the NAS code upgradeETA emc143208: VNX File Server: If DART is configured as a Client to an iPlanet Sun ONE Directory Server, a CIFS deadlock (hang) can occur when DART attempts to map Windows Groups to UNIX GIDs

EMC143208

E000105 TEST DELETED E000106 UPS AC Loss File exists, see ETA emc154409 for corrective action.

Checks for the existence of /nas/log/.acloss0 or .acloss1 files which indicate a loss of AC power to UPS0 or UPS1 at some time in the past. (NSX or NS80 only )ETA emc154409: VNX: NSX Series system could potentially shutdown after losing A/C power to both UPS units at alternating times

EMC154409

E000107 The Data Mover ACL settings were changed by NAS code upgrade.The test preserves the pre-upgrade settings for the Data Mover ACL values in the file preServerAcl.rpt , when the script is run post upgrade (runlevel 2) it compares these values with the values after the NAS code upgrade. The error indicates they do not compare. Use the nas_server -list command to display current settings, then use the nas_server -acl <value> <server_name > to correct the settings.

EMC156164

E000108 This check will only be run on systems with 5.5 NAS code, it checks for the existence and attributes of the file : /nas/volume/.row_locking_db_version

EMC156920

E000109 DM (<name>) has a tape device configured to HBA <#> chain <#>, tape devices should not be mixed with disk devices on the same HBA, see Primus Solution emc161424

EMC161424

E000110 The server_sysconfig server_x -p has changed from its pre-upgrade values. The difference can be examined in server_x.pre-sysconfig.rpt and server_x.post-sysconfig.rpt.<difference data output >

EMC161784

E000111 Server (<server_name>) acl <acl value>) does not have an owner, see Primus Solution emc183421

EMC183421

E000112 Checking ETA emc158129 Clariion HLU > 127 see Primus for cause and resolution. Fixed at 5.5.28.1 and higherETA emc158129: VNX: LUNs with a HLU greater than 127 fails to trespass during SP reboot or other path event failure, eventually resulting in an I/O loss of connectivity panic on Data Mover

EMC158129

E000113 5.6 Upgrade check, root_disk is too small (4153) for Cognac upgrade. EMC163260E000114 5.6 Upgrade check, root_ldisk is too small (4153) for Cognac upgrade EMC163260E000115 E000115: 5.6 Code Upgrade check, Data Mover (<server name>)

Model (<model>) is not supported in 5.6 NAS codeEMC182111

W000116 W000116: 5.6 Code Upgrade check, Current NAS code version (<version>) does not support upgrading to 5.6. Upgrade to 5.6 is

EMC182112

document.doc 38














only possible if the current NAS code version is 5.4 or 5.5.E000117 TEST DELETEDE000118 5.6 Upgrade check, NAS Control LUNs are not 11GB (rc= #).

See Primus emcxxxxxx for corrective action required.EMC182129

E000119 E000119: server_x <root_fs_x> inode usage is 95% or higher ($percentUsed). This condition can cause Data Unavailable condition, see Primus Solution .emc176923

EMC179623

W000119 W000119: server_x <root_fs_x> inode usage is 90% or higher ($percentUsed). This condition should be addressed before it causes a Data Unavailable condition, see Primus Solution emc176923.

EMC176923

W000120 W000120: NAS code 5.6 changes the format of nas_events configuration files. There are non system event file(s) loaded on this system: < file names > Solution emc185549 for more information.

EMC185549

E000121 E000121: The Clariion configured to this system is running Flare <ver> at patch level <patch ver>. In order to upgrade to NAS code x.x , you must be running patch version 034 or higher. See Primus Solution emc185579 for more information.

EMC185579

W000122 W000122: Control Station interface eth3 is configured ($filename) with dhcp to obtain its IP address. See Primus Solution emc187062 for more information.

EMC187062

E000123 E000123: Secmap is disabled on Server (server_x).DO NOT PROCEED WITH NAS 5.6 CODE UPGRADE. See Solution emc197662 for additional information.

EMC197662

E000124 E000124: File system (<fs name>) mounted on server_x gidmap file is the wrong size (<actual size>) it should be (<expected size>).This error can be ignored if upgrading to EMC NAS code 5.6.42.1 orhigher, otherwise check Primus Solution emc197578 for additional information.

OR E000124: File system (<fs name>) mounted on server_x gidmap file is missing.Check Primus Solution emc198382 for additional information.

EMC197578

OR EMC198382

E000125 RCM checks found model is CNS-14, box type ($boxType) is not eligible for upgrade.

Only valid for RCM

E000126 E000126: RCM upgrade version selected is not valid ($upgradeTo). Only valid for RCME000127 TEST DELETEDE000128 E000128: File system (<fs name>) mounted on server_x gidmap file

aclId is not 0 it is (<actual acl>). This error can be ignored if upgrading to EMC NAS code 5.6.40.3 or higher, otherwise check Primus Solution emc192697 for additional information.

EMC192697

W000129 W000129: Cifs parameter lg.localXidEnforcement is set to (value), please see Primus emc202075 for additional information.

EMC202075

W000130 W000130: SAC Server was setup on this system prior to the NAS code upgrade. It is no longer set up please see Primus emc203353 for required action you must take.

EMC203353

E000131 E000131: Control Station interface configuration file check failed.File (<file name>) is not expected to be present, check Primus Solution emc205929 for additional information.

EMC205929

E000132 E000132: Control Station interface configuration file contains entries with double quotes (< list of entries found >). See Primus Solution emc205376 for additional information.E000132: /nas/site/nas_param file entries contain double quotes.See Primus Solution emc205376 for additional information.E000132: /nas/site/slot_param file entries contain double quotes.

EMC205376

document.doc 39
















See Primus Solution emc205376 for additional information.

E000133W000133

W000133: Data Mover (server_3) has been up over (60) days, and is running(5.6.38.5) DART code. Please check ETA emc196251 for possible work around before proceeding.

E000133: Data Mover (server_3) has been up over (90) days, and is running(5.6.38.5) DART code. Please consult ETA emc196251 for required work around before proceeding.ETA emc196251: VNX: Data Movers running 5.6 code (up to 5.6.39) may panic after 97 continuous days of runtime

EMC196251

W000134 W000134: Upgrade to 5.6 while running Flare version (24) Flare (actual version )require that Flare 24 be upgraded to Flare 26 after the NAS code upgrade to 5.6. See Solution emc216195 for more information.

EMC216195

W000135 W000135: Warning if you are upgrading to a NAS Code version less than 5.6.46.4, please follow the instructions in ETA emc222801 before proceeding with the code upgrade. Your current switchMgmt module firmware level is 01.82.ETA emc222801: VNX: Upgrades to NAS code 5.6.42.x through 5.6.45.x may hang when upgrade of management switch firmware fails

EMC222801

W000136 W000136: If you are upgrading to NAS code 5.6.47.x, please review Primus Solution emc223821 before proceeding with the code upgrade.

EMC223821

W000137 W000137: The output from the /nas/tools/nas_stig command indicates that stig is turned ( < value returned >). It must be turned off before starting the NAS code upgrade. Please consult with the Customer before turning off stig. See Primus Solution emc227643 for more information.

EMC227643

W000138 W000138: Warning you are currently running ( nas_version) check ETA emc112328 for applicabilityETA emc112328: VNX File Server: NDMP backups fail after upgrading to NAS code version 5.4

EMC112328

W000139 W000139: Warning you are currently running (nas_version) check ETA emc125099 for applicability.ETA emc125099: VNX File Server: Captive VNX/CLARiiON backend events do not generate Control Station CallHomes

EMC125099

W000140 W000140: Warning you are currently running (< nas_version>) check ETA emc132443 for applicabilityETA emc132443: VNX: Microsoft hotfix causes secondary incompatibility with VNX Manager

EMC132443

W000141 W000141: Warning the VNX number is not configured (<VNX_serial>) check ETA emc144743 for applicability.ETA emc144743: VNX File Server: After installation, NS Series VNXs are missing VNX Serial number in Resume PROM causing unknown dial homes

EMC144743

W000142 W000142: Warning the VNX has an attached Symmetrix ( <symm EMC222370

document.doc 40












serial number >) and may have exposure to this ETA emc222370 check the ETA for applicability.ETA emc222370: VNX: Diskmarking newly added disk devices may fail with 'Error 5002' or 'Input/Output errorRPC' for very large backend systems

W000143 W000143: Warning this VNX model ( NSX ) may have exposure to this ETA emc149819 check the ETA for applicability.ETA emc149819: VNX: NSX Blade replacements or upgrades may be incompatible with NAS versions prior to 5.5.22.2

EMC149819

W000144 W000144: Warning this NAS code version (nas_version) is covered by this ETA emc150583 check the ETA for applicability.ETA emc150583: VNX: How to update the VNX in order to properly handle the United States Daylight Saving Time change occurring in year 2007

EMC150583

W000145 W000145: Warning this NAS code version (nas_version) is covered by this ETA emc151481 check the ETA for applicability.ETA emc151481: VNX: All replications become inactive after Data Mover shutdown using nas_halt command

EMC151481

W000146 W000146: Warning this NAS code version (5.5.41.1) is covered by this ETA emc158208 check the ETA for applicability.ETA emc158208: VNX: NDMP incremental backup may cause Data Mover panic after NAS code upgrade to version 5.5.27.5

EMC158208

W000147 W000147: Warning this NAS code version (nas_version) is covered by this ETA emc158502 check the ETA for applicability.ETA emc158502: VNX: Upgrading from NAS code 5.3 or 5.4 to 5.5 causes DU on iSCSI LUNs managed by Replication Manager/SE (RM/SE )

EMC158502

W000148 W000148: Warning this NAS code version (nas_version) is covered by this ETA emc158629 check the ETA for applicability.ETA emc158629: VNX: CIFS Server DNS Aliases Requires Parameter Change with Windows 2003 Domain or Later

EMC158629

W000149 W000149: Warning this NAS code version (nas_version) is covered by this ETA emc166433 check the ETA for applicability.ETA emc166433: VNX File Server: How to address 'Both internal interfaces are down' on Hammerhead (NSX or NS80) system

EMC166433

W000150 W000150: Warning this NAS code version (nas_version) is covered by this ETA emc167225 check the ETA for applicability.ETA emc167225: VNX: Replication cannot be started or will not restart if the file system meta volume ID is greater than 16383

EMC167225

W000151 W000151: Warning this NAS code version (nas_version) is covered by this ETA emc167945 check the ETA for applicability.ETA emc167945: VNX: SCCS script error causes configuration changes to not be saved

EMC167945

W000152 W000152: Warning this NAS code version (nas_version) is covered by EMC170690

document.doc 41












this ETA emc170690 check the ETA for applicability.ETA emc170690: VNX File Server: CIFS users cannot access shares after NAS code upgrade to version 5.5.29.1 or 5.5.30.5

W000153 W000153: Warning this NAS code version (nas_version) is covered by this ETA emc174059 check the ETA for applicability.ETA emc174059: VNX: NAS upgrades to 5.5.31.6 replaces the VNX CallHome feature with the VNX ConnectHome feature--custom modem settings may be lost and require resetting

EMC174059

W000154 W000154: Warning this NAS code version (nas_version) is covered by this ETA emc174326 check the ETA for applicability.ETA emc174326: VNX File Server: In an IP replication environment, the fs_replicate -restart command can potentially restart replication from an incorrect checkpoint resulting in destination file system corruption

EMC174326

W000155 W000155: Warning this NAS code version (5.4.31.2) is covered by this ETA emc175871 check the ETA for applicability.ETA emc175871: VNX: Do not perform any upgrades from NAS version 5.4.31.2 to NAS version 5.5.31.6

EMC175871

W000156 W000156: Warning this NAS code version (nas_version) is covered by this ETA emc176658 check the ETA for applicability.ETA emc176658: VNX: CDMS migration causes rolling panic in NAS codes 5.5.29, 5.5.30 and 5.4.30

EMC176658

W000157 W000157: Warning this NAS code version ( nas_version ) is covered by this ETA emc178175 check the ETA for applicability.'DART panic message: alloc failed: file system full' occurs after a file system is extended

EMC178175

W000158 W000158: Warning this NAS code version ( nas_version ) is covered by this ETA emc179185 check the ETA for applicability.ETA emc179185: VNX: During Rainfinity DHSM operations, Data Mover runs out of vnodes and spikes the CPU to 100%

EMC179185

W000159 W000159: Warning this NAS code version (nas_version) is covered by this ETA emc181913 check the ETA for applicability.ETA emc181913: VNX: The VNX Daylight Saving Time updates for March 2008

EMC181913

W000160 W000160: Warning this NAS code version (nas_version) is covered by this ETA emc183389 check the ETA for applicability.ETA emc183389: VNX: The revector and cse_recover tools will not be available in NAS Code 5.6 at GA

EMC183389

W000161 W000161: Warning this NAS code version (nas_version) is covered by this ETA emc186599 check the ETA for applicability.ETA emc186599: VNX: CLARiiON backend events are not generating NAS events on Integrated VNXs running NAS code 5.6.36 or 5.6.37

EMC186599

W000162 W000162: Warning this NAS code version (nas_version) is covered by this ETA emc188184 check the ETA for applicability.

EMC188184

document.doc 42













ETA emc188184: VNX: ConnectHome test not working and modem does not dial home after upgrade to, or an install of, 5.6 NAS code

W000163 W000163: Warning this NAS code version (nas_version) is covered by this ETA emc189395 check the ETA for applicability.ETA emc189395: VNX: iSCSI LUNs need resignaturing from VMware server after NAS code upgrade from version 5.5 to 5.6

EMC189395

W000164 W000164: Warning this NAS code version (nas_version) is covered by this ETA emc192298 check the ETA for applicability.ETA emc192298: VNX: Cannot dial in using a modem after an upgrade to (or an installation of) NAS code version 5.6, or after a Control Station reboot

EMC192298

W000165 W000165: Warning this NAS code version (nas_version) is covered by this ETA emc192662 check the ETA for applicability.ETA emc192662: VNX SnapSure Checkpoint: After upgrade to NAS code 5.6, the Data Mover may panic with a Page Fault Interrupt if a single new CheckPoint (ckpt) is created

EMC192662

W000166 "W000166: Warning this NAS code version (nas_version) is covered by this ETA emc193912 check the ETA for applicability.ETA emc193912: VNX: Replication V2 session sync can fail when a file system extension is in progress

EMC193912

W000167 W000167: Warning this NAS code version (nas_version) is covered by this ETA emc194364 check the ETA for applicability.ETA emc194364: VNX: Symmetrix NDU may cause attached VNX systems to panic

EMC194364

W000168 W000168: Warning this NAS code version (nas_version) is covered by this ETA emc194888 check the ETA for applicability.ETA emc194888: VNX: Managing storage or performing array NDUs with NAS Integrated systems fails after FLARE 24 or 26 upgrade

EMC194888

W000169 W000169: Warning this NAS code version (nas_version) is covered by this ETA emc196974 check the ETA for applicability.ETA emc196974: VNX: NX4, NSX, NS80, NS40, or NS20 systems may experience memory corruption

EMC196974

W000170 W000170: Warning this NAS code version (nas_version) is covered by this ETA emc197458 check the ETA for applicability.ETA emc197458: VNX: NS systems with 10 Gb network interface cards can receive checksum errors

EMC197458

W000171 W000171: Warning this NAS code version (nas_version) is covered by this ETA emc208473 check the ETA for applicability.ETA emc208473: VNX: CLARiiON stale log events are triggering excessive call-homes in VNX Integrated systems

EMC208473

W000172 W000172: Warning this Flare code version (XX XXX) is covered by this ETA emc209392 check the ETA for applicability.ETA emc209392 CLARiiON: Storage Processor may panic while using MirrorView/Asynchronous in Release

EMC209392

document.doc 43












24 or Release 26W000173 W000173: Warning this NAS code version (nas_version) is covered by

this ETA emc211169 check the ETA for applicability.EMC211169


EMC213367


EMC216760

W000176 W000176: Warning this Symmetrix code version (revision) is covered by this ETA emc218272 check the ETA for applicability

EMC218272


EMC224962


EMC229599


EMC230290


EMC230656


EMC230801


EMC158723


EMC155873


EMC150251

W000185 W000185: Warning this NAS code version (nas_version) is covered by this ETA emc117671 check the ETA for applicability..

EMC117671


EMC115896

W000187 W000187: Warning this integrated Clariion is setup for gateway address (100) the corrective action required for this issue is covered in emc240241.

EMC240241

W000188 Dropped

W000189 W000189: Warning if this (<model>) VNX is attached to the Clariion with copper cables, this issue is covered in emc236029.

EMC236029

W000190 W000190: Warning CLARiiON(<serial number>) does not have naviSecCli configured(< value returned> ) see Solution emc239261 for additional information.

EMC239261

W000191 W000191: Warning, please read the following ETA which may affect this system if upgrading to 5.6.48.0 or 5.6.49.0, issue is covered in emc243184.

EMC243184

W000192 W000192: Warning ,please read the following ETA which may affect this system if upgrading to 5.6.48.0 or 5.6.49.0, issue is covered in emc243717.

EMC243717

E000193 E000193: Error the server in slot(5) has an export entry that is (2435 /nas/server/slot_5/export) characters in length. This exceeds 2048 characters in length, which exceeds the allowed limits. Check emc247995 for additional information.

EMC247995

W000194 W000194: Warning , please read the following ETA which may affect this system if upgrading to 6.0, issue is covered in emc254145. Server (server name) filesystem name (fs name)."

EMC254145

W000195 W000195: Warning, server (server name) has parameter initCgBitmap set to (value), please read the following ETA which may affect this

EMC253731

document.doc 44
























system if upgrading to 6.0, issue is covered in emc253731.W000196 W000196: Warning, server in slot_$mytry is configured for NFS v4,

please read the following ETA which may affect this system, further information can be found in Knowledge base Solution emc248825.

EMC248825

W000197 W000197: Warning, The CLARiiON Storage is running FLARE version < version >, please read the following ETA which affects this system, further information can be found in Knowledge base Solution emc255604. A fix to this issue is available in the Flare Release 30 patch 508 (R30p509).

EMC255604

W000198 W000198: NDMP backup/restore might experience an authentication failure after upgrading to NAS 5.6.40.3 or later

EMC199297

E000199 Dropped

W000200 W000200: Warning, current DART code is (DART version) please read the following ETA which affects this system, further information can be found in Knowledge base Solution emc261201. A fix for this issue is available in the NAS server Code 6.0.40.8 or 6.0.40.500

EMC261201

W000201 W000201: Warning, current NAS code is (5.6.51.0) if upgrading to NAS 6.0.40.x code or lower please read the following Solution which affects this system, further information can be found in Knowledge base Solution emc261598.

EMC261598

E000202

OR

W000202

E000202: Warning, a check of the Control Station /dev/hda indicates it is inconsistent (OK), do not proceed with the NAS code upgrade until this issue is resolved. Further information can be found in Knowledge base Solution EMC257271OR

W000202: Warning the command that checks the Control Station /dev/hda partition returned an error rc (255). Further information can be found in Knowledge base Solution EMC257271.

EMC257271

W000203 W000203: Warning if upgrading to NAS code 6.0.41.x the server_name ( name ) exposes this system to the following upgrade issue. Further information can be found in Knowledge base Solution EMC267861.

EMC267861

W000204 W000204: Warning this (nas code version) system may encounter the following upgrade issue. Further information can be found in Knowledge base Solution ETA EMC266764.

EMC266764

W000205 W000205: Warning this (6.0.41.4) system may encounter a CIFS client issue. Further information can be found in Knowledge base Solution ETA EMC263721.

EMC263721

W000206 W000206: Warning the StorageGroupName (bad&group1) contains characters that arenot supported. Further information can be found in Knowledge base Solution EMC242512.

EMC242512

W000207 W000207: Warning this system requires the callhome template update, the following file was not found (<file name >). Further information can be found in Knowledge base Solution ETA EMC277773. ORW000207: Warning this system requires the callhome template update, the update has not been performed on this system. Further information can be found in Knowledge base Solution ETA EMC277773.

EMC277773

document.doc 45







http://csexplorer.isus.emc.com/eservice/iviewcs/ui/eserver.asp?id=261598






W000208 W000208: Warning this system is configured for CIFS and DeDuplication and running DART code version (5.6.48.701 ). Further information can be found in Knowledge base Solution ETA EMC267599.

EMC267599

W000209 W000209: Warning this system requires the apl_event_mgr update, the following file was not found (/nas/http/webui/bin/apl_event_mgr ). Further information can be found in Knowledge base Solution ETA EMC281631.W000209: Warning this system requires the apl_event_mgr update, the update has not been performed on this system. Further information can be found in Knowledge base Solution ETA EMC281631.

EMC281631

W000210

E000210

Warning if upgrading to NAS 6.0.55.3 please follow the instructions in knowledge base Solution ETA EMC291071, before proceeding with the upgrade.If upgrading to NAS 6.0.55.300 or NAS 6.0.56.x and higher this warning can be ignored.E000210: Error you are running ( <NAS version>) and the server in slot(<slot number>) has param <param name> equals <param current value> please follow the instructions in knowledge base Solution ETA EMC291071, to correct this error.

EMC291071

E000211 dropped

E000212 E000212: Meta LUNs (<disk name>) (<protection type>) are configured to this system and are not supported. See Solution emc294525 for assistance in resolving this issue.

EMC294525

E000213 E000213: While checking the DIMM status in enclosure(<enclosure number>), the following status was returned (<DIMM status>). If additional information required see emc298683

EMC298683

W000214 W000214: The following file system is configured for FLR and replication ( <file name >) please follow the instructions in knowledge base Solution ETA EMC300513, before performing this code upgrade.

EMC300513

W000215 W000215: Please read and follow the instructions in knowledge base Solution ETA EMC299745, before performing this code upgrade.

EMC299745

W000216 W000216: This system is configured for RecoverPoint and is running(<flare version>). Please read and follow the instructions in knowledge base Solution ETA EMC298607, before performing this code upgrade.

EMC298607

W000217 W000217: This system is configured for deduplication and is checkpoints. Please read and follow the instructions in knowledge base Solution ETA EMC277607, before performing this code upgrade.

EMC277607

E000218 E000218: The following running tasks (<task id list >) may be hung. Please read and follow the instructions in knowledge base Solution EMC204889, before performing this code upgrade.

EMC204889

E000219 E000219: This is type ( 2 ) system it cannot be upgraded to NAS 6.0 code.000219: LUN 5 is (<LUN size>) in size, you cannot upgrade to 6.60.65.x of higher unless LUN 5 is at least 4 GB. Please read and follow the instructions in knowledge base Solution ETA EMC307415, before performing this code upgrade.

EMC307415

E000220 E000220: The netmask for slot(#) interface (<name>) is not valid (<netmask>), you cannot upgrade with this configuration. Please read

EMC307209

document.doc 46














and follow the instructions in knowledge base Solution EMC307209, before performing this code upgrade.

Appendix A: Log Files explained

Log files

The following section gives an explanation for each file produced by the upgrd-ck script. The data is these files in some cases is used to preserve system information discovered before the code upgrade so that it might be compared with the post upgrade information. Do not remove these files until you have run the script post upgrade (runlevel 2).

post-upgrade.rpt

pre-upgrade.rpt

trace.rpt

clartool_<cs hostname>.rpt

config.rpt

cpgInput.rpt

clartool_<cs hostname>.rpt

This file contains the tagged Clariion backend data collected by the script by running various navicli commands. The file name is clartool_<cs hostname>.rpt.

-rw-r--r-- 1 root root 51395 Sep 7 07:53 clartool_laip2.rpt

The file contains data, produced by running the following commands, and logging that information to the file:

hostname

nas_version

nas_disk –l

Data mover WWN

Clariion IP addr

Output from navilci commands :

ndu –list

getcrus

storagegroup –list

getlun –name –type –default –owner –at –aa –wc –rc

port –list –all

spportspeed –get

pre-upgrade.rpt

Report produced when upgrd-ck script run with runlevel 1 option, it contains the following information:

document.doc 47


The number of days left before script expires ( becomes un-usable)

Date and time script was run

Script options selected

List of tests run, with pass / fail / skip status

List of errors encountered

config.rpt

Data mover list

List of failed over data movers

Status of iwd daemon check

Status of file system data structure and dbchk status

Status of CS mounted fs free spaces checks

Status of nas_events check

Status of timefinder mirror on checks

Status of NIS running on the CS checks

Status of nasdb_backup cron job by checking for current /home/nasadmin/_nasbkup* files

The output from /sbin/ifconfig –a command run on the control station

The output from netstat –rn command run on the control station

The status of a check for any cron jobs not owned by nas on the control station

The status from checking the free file system space in all user file systems mounted on the data movers

The backend serial numbers

The backend IP address for SPA

The status from running the navicli getcrus command

A list of ALU to HLU address for each Clariion backend

The status from checking Clariion for reserved LUNs (6 -15)

The status from checking the Clariion Auto assign flags

The status from checking the Clariion Auto trespass flags

The status from checking the Clariion write cache enabled

The status from checking the Clariion for trespassed or un-owned LUNs

The status from checking the Clariion for control LUNs (0-5) owned by SP A

The status from checking for Multiple LUN 0 configured

The status from checking data mover serial numbers match /nas/server/slot_x/start file entry

The status from checking that data mover mac addresses in /nas/server/slot_x/ifconfig* match actual hardware mac addresses

The status from checking if nas.exe is configured as the boot image for all data movers

The status from checking data mover reason codes

The status from running the server_mount command on the data movers

document.doc 48


The status from running the server_df command on the data movers

The status from running the server_export command on the data movers

The status from running the server_standby –v command on the data movers

The output from running the server_sysconfig –pci command on the data movers

The output from running the nas_server –i –a command

trace.rpt

The trace.rpt file contains a list of script modules entered and exited along with the time in seconds it took to execute each section. From time to time it may also contain raw data dumped from some routine that is under investigation. The most useful information for the user is the amount of time it took to execute each section, if the script hangs, the last entry in the trace.rpt should be the entry into the module hung the script. The amount of time needed to execute each section, such as the dump_usrm , srv_mnt, or srv_exp can indicate which switches need to be used to complete the script in a certain time frame.

post-upgrade.rpt

Report produced when upgrd-ck script run with runlevel 2 option, it contains the following information:

The number of days left before script expires ( becomes unusable)

Date and time script was run

Script options selected

Data mover list

List of failed over data movers

Status of iwd daemon check

Status of file system data structure and dbchk status

Status of CS mounted fs free spaces checks

Status of nas_events check

Status of timefinder mirror on checks

Status from restarting NIS running on the CS if it was previously running on the CS

The status of a check for any cron jobs not owned by nas on the control station

The status from checking the free file system space in all user file systems mounted on the data movers

The backend serial numbers

The backend IP address for SPA

The status from running the navicli getcrus command

A list of ALU to HLU address for each Clariion backend

The status from checking Clariion for reserved LUNs (6 -15)

The status from checking the Clariion Auto assign flags

The status from checking the Clariion Auto trespass flags

The status from checking the Clariion write cache enabled

document.doc 49


The status from checking the Clariion for trespassed or un-owned LUNs

The status from checking the Clariion for control LUNs (0-5) owned by SP A

The status from checking for Multiple LUN 0 configured

The status from checking data mover serial numbers match /nas/server/slot_x/start file entry

The status from checking that data mover mac addresses in /nas/server/slot_x/ifconfig* match actual hardware mac addresses

The status from checking if nas.exe is configured as the boot image for all data movers

The status from checking data mover reason codes

The status from checking if the data mover nas versions match the nas_version installed on the control station

The status from checking that the server_name and hostnames for all data movers match

The status from comparing pre and post upgrade file systems mounted on the data movers

The status from comparing pre and post upgrade file systems server_df command on the data movers

The status from comparing pre and post upgrade file systems server_export command on the data movers

The status from running the server_standby –v command on the data movers

The output from running the server_sysconfig –pci command on the data movers

The output from running the nas_server –i –a command

The status from running checks for both internal and external usermapper configurations

The status from checking the upgrade log for a failed external usermapper upgrade

The status from check the upgrade log from nas code upgrade for any error messages

A listing of files in the /nas/server and /nas/site directories which have been changed during the upgrade

A listing of number of nas_params pre and post upgrade

A listing of params that changed during upgrade

The status of usermapper after the upgrade

A list of any errors encountered

*.rpt files explained

The following files are created by the script their contents and purpose is explained in this section :

postcksums.rpt

precksums.rpt

presitecksum.rpt

postsitecksum.rpt

presite.rpt

postsite.rpt

preupgrd.rpt

postupgrd.rpt

postparams.server_2.rpt

document.doc 50


preparams.server_2.rpt

predffs.rpt

preexp.rpt

premtfs.rpt

preServerAcl.rpt

postServerAcl.rpt

server_2.post-sysconfig.rpt

server_2.pre-sysconfig.rpt

pre / postcksum.rpt

postcksums.rpt – created at runlevel 2, is a cksum of each file in the /nas/server directory, purpose to compare against precksums.rpt which was created at runlevel 1. This will document which files in the /nas/server/slot_x directories were changed by the upgrade, in the event that a problem should arise. To be sure the cksum and even the file sizes of these files will change during a NAS code upgrade.

This is an example of how to determine what has changed. In this case the mis-compare is saying that the data files (virtualdevs and virtualdevstab ) changed to size 0 in the postcksums.rpt files. This is actually caused by the fact that the script was run level 1 on Sept 7 but the run level 2 or post upgrade check script has not been run since Sept 4 so the pre and post are not looking at the data from the same day (operator error ). It may not be an error if the file size and cksums change, this has been observed to be normal during nas code upgrades. But there have been instances where a configuration file was changed as a result of a nas code upgrade, which caused a problem. So this list is provided for information purposes, to assist in troubleshooting problems following an install.

diff precksums.rpt postcksums.rpt |more

< 255512050 73 /nbsnas/server/server_1/virtualdevstab

< 2578139787 552 /nbsnas/server/server_1/ifconfigtab

> 4294967295 0 /nbsnas/server/server_1/virtualdevstab

> 2595785278 415 /nbsnas/server/server_1/ifconfigtab

< 374666679 516 /nbsnas/server/server_1/ifconfig

> 377681235 388 /nbsnas/server/server_1/ifconfig

< 110895282 63 /nbsnas/server/server_1/virtualdevs

4294967295 0 /nbsnas/server/server_1/virtualdevs

pre / postupgrd.rpt

Files containing the output from a ls –LR of the /nas/server directory from before and after a NAS code upgrade. Provided for information purposes.

pre / postsitecksum.rpt

Files containing a cksum listing of the /nas/site directory files, the purpose of these files is to provide a method to determine which files in the /nas/site directory may have been changed by the NAS code upgrade.

pre / postsite.rpt

Files containing the output from a ls –lR of the /nas/site directory from before and after the NAS code upgrade. Provided for information purposes.

pre / postparams.server_x.rpt

document.doc 51


The pre and postparams.server_x.rpt files are listings of the data mover param settings pre and post upgrade. The upgrd-ck script does the diff for and will report how many params have changed in the post-upgrade.rpt file, the changes will not be reported as errors, since params change without notice.

You can simply run the diff command to compare the pre – post files. If there is any question you can always display the param in question and compare its value to the value in the preparam.server_x.rpt file to verify the change. It could be a problem, check it out….

pre / postsitecksum.rpt

The pre and postsitecksum.rpt files are listings of cksums for all the files in the /nas/site directory before and after the upgrade. A diff is run against these files during runlevel 2 and reported in the post-upgrade.rpt file. But it will not be listed in the errors list. A diff of the two files will reveal those files which have changed as a result of the upgrade.

preexp.rpt / premtfs.rpt

The preexp.rpt and premtfs.rpt are used by script to compare against during the post upgrade run (runlevel 2) for data mover exported and mounted file systems.

preServerAcl.rpt / postServerAcl.rpt

These files contain a entry for each Data Mover which contists of the server_name and it ACL value, the values of these settings are compared pre/post upgrade and if a difference exists a error will be flagged.

server_x.post-sysconfig.rpt/ server_x.pre-sysconfig.rpt

These files contain a capture of the output from a server_sysconfig server_x –pci from runlevel 1 (pre) and runlevel 2 (post). The script will use the diff command to compare these two files, if there is a difference an error will be flagged. Examine the error output or use the diff command to determine if what has changed is of any consequence.

document.doc 52


Appendix B: Warnings and ExceptionsThe script will exit at the first major error encountered when envoked with the “-r” switch, if you wish to run through all checks and correct the errors at the completion of the script us the “-v” switch.

If the system is running external usermapper and has a very large list of users and groups, it may be necessary to use the “-U” switch to bypass the dumping of the usrmap db files to passwd and group files. The reason for this is that it can take hours for this section to complete. If the “-b” switch is used the backup section of the script will backup the /nas/cifs/usermapper* directory and its files, so this step can be bypassed by using the “-U” switch.

If the system has a very large number of file systems mounted and exported (1000’s), the sections of the script which check mounts and exports can also take some time. After running the script, check the trace.rpt file to determine how long each section takes. Use the “-ME” switches to avoid running the mount and export checks. It is best to let these checks run, since if you don’t you must manually check these 1000’s of file systems.

A system with 14 data movers will also spend a long time performing the param checks. A switch “-P” is also provided to bypass these checks. It is best practice not to bypass this test since it provides a snapshot of the param settings before and after the upgrade, and also provides details about the number of params changed by the upgrade. Changes to params, while normal during an upgrade, have caused problems in the past.

Appendix C: Script Usage and options[root@la2 nasadmin]# ./upgrd-ckv10-48.bin -h

options h

run level is

usage:

upgrd-ckv10-48.bin <options>

options:

-h Help.

-r runlevel - start test, must be accompanied by either a 1 or

2 . 1 if the this pre-upgrade, and 2 if post upgrade.

-P Do not check nas parameters

-D Diagnose ( do not halt for severe errors)

-d Specify directory to run script and create logs in.

-v Run in verify mode, perform checks only, error list created

-b Run control station backup sections, to be used with -r or -v

-E Skip checking server_export (use if there are many exports)

-M Skip checking server_mount (use if there are many mounted fs)

-Q Skip test for ETA121367 (127 tree quotas & group quotas)

-U Skip usermapper files (use if there are many users)

-N Skip Symmetrix Backend checks.

document.doc 53


-Y Enable replication V2 logging to config.rpt file ( may extend length of time necessary run script).

Default Values are:

Working directory : /home/nasadmin

RunLevel:

The 1 denotes "pre-upgrade" and the 2 is for "post-upgrade".

Switches

“r” run switch, which can be run pre and post upgrade. It will just do the checks, and attempt to either correct the issues found or ask the user to correct them, and print out a list of issues at the end. When run with the –D switch the switch will not force the user to resolve issues, but will allow negative answers and continue to the end of the script. It will then report all errors encountered.

"v" verify switch - can be run pre and post upgrade. It will only do the checks, and print out a list of issues at the end. This will allow checks to be run several days before upgrade to determine if any of the issues checked by the script are present, such as not enough free space in a file system, so that it can be worked on before the upgrade window.

"b" backup switch - unless you specify this switch the backup portion of the script will not run

Exception Switches

“d” switch – allows the user to specify a directory other than /home/nasadmin to install the script to and create log files in.

"D" switch - which will allow script to run and not exit for errors, such as if "free space check fails" , or if "nis" is running on the Control Station and the user does not want to turn it off (not a good idea as this has caused problems).

Note: The D switch should not be used normally, run the script with -vb switches instead, and then fix the issues in the error list at the end of the report, before doing the upgrade.

“E” switch which will suppress the checking of server_exports, in the case where the customer has a large number of exports the script can take a long time to acquire the output from the data mover. Setting this switch will cause the server_export command to not be run. Would normally be used with the “M” switch.

“M” switch which will suppress checking server_mounts, in the case where the customer has a large number of mounts and the script can take a long time to acquire the output from the data mover. Setting this switch will cause the server_mount command to not be run.

Would normally be used with the “E” switch.

"P" param switch - if you specify this switch the param checks will not be run. Switch was added because param check can be time consuming on Celerras with a large number of data movers.

“Q” param switch – can be used if the upgrd-ck script should hang during the ETA121367 test, use of this switch in addition to the “-v” or “-r” switch will result in this test being skipped if NAS code level is 5.3.x.x

“T” switch enables stand alone health checks. Test series 1 checks file system health issues. Test series 2 checks Clariion backend health as a standalone series of tests. A log file is produced which can be viewed to look at the raw data should the script indicate there is an error.

document.doc 54


“U” switch which will suppress dumping the usrmapper data base files, in the case where the customer has a extremely large number of users and groups and the dump command would take a very long time to run. Using this switch will suppress running the commands to dump the usrmapper data base files.

“N” switch disables collecting Symmetrix Backend information and running Symmetrix checks.

Here are a few examples of the switches and the results expected:

-rb 1 or 2 Run script normally and backup files.

-rbEM 1 or 2 Run script normally and backup files, suppress running server_mount

and server_export commands

-rbU 1 or 2 Run script normally and backup files, suppress running dump of

usrmapper data base files

-rbUEM 1 or 2 Run script normally and backup files, suppress running dump of

usrmapper data base files, and suppress running server_mount and

server_export commands

-rbP 1 or 2 Run script and backup files, but do not run param checks

-v 1 Run verify mode do not run backups, print out issue list

-vb 1 Run verify and backups files

-v 2 Run post upgrade verifications, print out issue list

-rbD 1 or 2 Run script and backup files, do not exit script at normal exit points

-rbPD 1 or 2 Run script and backup files, do not exit script at normal exit points, do

not run param checks

-TD 1 Run file system health checks

-TD 2 Run Clariion backend health checks

Note: The 1 denotes "pre-upgrade" and the 2 is for "post-upgrade".

document.doc 55

document template - wikileaks · web viewmicrosoft word opens on your laptop and the document is...

Documents