ML8 SP2 Upgrade

8/8/2019 ML8 SP2 Upgrade

1/4

#This procedure defines upgrading an AIX 5.3 Lam server from ML06-SP3 to ML07-SP1.

Prior to starting this procedure, you must contact OPS and stop any applications as required.1. Contact DSMOPS (1-859-243-4030) and stop the application running on host.

If you have to edit a file in order to shutoff apps ( eg /etc/inittab), make a note of in caseyou need to restore original file after change and backup file first to filename.date (ie,inittab.07232007).

2. Log into the lamdns server.

a. cd /tmp/lam.server.< host >

b. ls -l ---> should show last Saturday date. This is the automated server config output.

3. Log into the target host, check the following outputs for errors.

a. errpt ---> check for any recent hardware errors

b. oslevel -s ----> 5300-07-01

c. lppchk -v This command is very important as it checks the integrity of the AIXinstalled fileset database. It should run clean. If not, you need to fix it ( ie make it runclean) before proceeding further.

4. Make backup copies of these files:

a. /etc/filesystems

b. /etc/inetd.conf

c. /etc/inittab

5. Perform required mksysb backup.

a. Run /usr/local/bin/backup.sh (backup_dr.sh for DR Servers)

b. FTP /mksysbdata/hostname.mksysb.0 to another server for storage during change.

6. Run the TSM incremental backup prior to the upgrade.

a. dsmc - a prompt should appear.

b. incr- this command does the incremental backup.c. quit - exit from TSM session

7. Manipulate the /usr/sap/trans NFS mount (If applicable)

a. Determine if a /usr/sap/trans filesystem is NFS mounted: df | grep trans

b. Unmount the NFS mount (if applicable): sudo umount /usr/sap/trans

8. Manipulate the SDD volume groups or filesystems.

a. Capture a snapshot of the system. sudo /home/nis/scripts/get.cfgThis will create a file named .cfg

b. Determine the volume groups configured on the system: lsvg

c. Notate the names of the externalvolume groups: rootvg and sys01vg are internal

d. Unmount all filesystem configured in SDD volume groups:sudoumount -t VGname

The filesystems should all be set to have a mount type equivalent to the volumegroup name. Therefore, you should be able to unmount the filesystems in eachexternal volume group using one command.

e. Verify only the internal filesystems are mounted: df

f. Vary off all SDD volume groups: sudo varyoffvg VGname


2/4

g. Verify only the internal volume groups are varied on: lsvg o

9. Manipulate the SDD/2105/2107 device definitions as applicable.

a. Determine if any vpath devices are configured: lsdev | grep vpath | wc l

b. Remove SDD vpath devices: sudo rmdev dl dpo R

c. Verify the vpath definitions were removed: lsdev | grep vpath | wc l

d. Determine if any 2105 devices are configured: lsdev | grep 2105 | wc l

e. Remove hdisk devices for 2105 devices:lsdev C t 2105* -F name | xargs n1 sudo rmdev -dl

f. Verify 2105 hdisk devices for were removed: lsdev C t 2105*

g. Determine if any 2107 devices are configured: lsdev | grep 2107 | wc -l

h. Remove hdisk devices for 2107 devices:lsdev C t 2107* -F name | xargs n1 sudo rmdev -dl

i. Verify 2105 hdisk devices for were removed: lsdev C t 2107*

j. Verify only the internal disk drives are configured: lsdev Cc disk

10. Run command: lslpp -l | grep APP ---> If no output skip this step.

a. If there is output, then perform smit commit per text below:

b. Commit existing filesets using smit fastpath "smit commit".

c. smitty commit

d. press enter key and SMIT will commit all applied filesets.

11. Check above command with lslpp -l | grep APPLIED - there should be no output. Now,time to do the upgrade.

12. mount prdop01:/repository /mnt onto target host

13. Uninstall SDDSRV fileset and update 2107 and aparsa. stopsrc sddsrv ----> stops the sddsrv service

b. smitty install -> software maintenance -> Remove Installed Software

c. esc-4 to get software list, /sdd to search and select/mark devices.sdd.53.rted. hit enter, then execute to uninstall old sdd filesete. cd /mnt/sdd/2107

f. smitty update_all ----> update the 2107 driver (if for some reason it doesntexist, simply do an install instead of an update on the fileset)

g. cd /mnt/aix53

h. ls ----> You should see this output: ML7 TL8_SP2

i. cd TL8_SP2

j. smitty update_all ( You should be in directory /mnt/aix53/ML7) enter "." for current directory and then press enter. You should now

have the " Update Installed Software to Latest Level (Update All)"SMIT menu displayed.

Set "Commit software updates" = no Set "Save replaced files" = yes Set "DETAILED output" = yes The remaining fields should be the default and "_update_all" must be

in the "SOFTWARE to update" field.


3/4

Press enter to run update..... When finished, you should see the "OK" symbol. If it states failure,

call Craig or Patty, or call IBM Support to debug immediately (1-800-IBMSERV).

k. cd /mnt/sdd/sdd1630

i. smitty install -> install software -> install

j. esc-4 to get software list, select devices.sdd.53.rte and install

14. oslevel -s -----> 5300-08-02; if this output does not appear, STOP and check thesmit.log for error messages.

15. lppchk -v; this command should display no output. If not, do as above if failed.

16. Check bootlist with command: bootlist -m normal o

a. You will see this output: hdisk0 blv=hd5hdisk1 blv=hd5

b. The disk numbers may be different for each server, but hdisk0 will almost alwaysbe listed.

17. If a cdrom device is listed in bootlist, then removed it to insure server does not attempt toboot to a cd disk left in the drive. bootlist m normal hdisk0 hdisk1, use abovecommand to verify the change took.

18. If you are not at a console session, open a console session from the HMC or consolescript lamdns:/usr/local/bin/lam_console so that you can see any bootup issues or SMSmenus

19. Reboot server with shutdown Fr

20. Post check...

a. Compare the output from the /home/nis/scripts/.cfg file to the output fromthe following commands on the system:

lsvg

lsvg -o

lspv | wc -l

lspv ==> Only the internal hdisk and the vpath should have PVIDS associatedwith them

df | wc -l

df | grep sapdata | wc -l

b. Open window to lamdns:/tmp/lam.server/

c. Check the df -k output number of lines with df -k |wc -l. This number should be same

as the lamdns:/tmp/lam./dfk.info value.d. Check the NFS client mounts by running /usr/local/bin/check.nfs.mounts all@ /usr/local/bin # ./check.nfs.mounts all ( see section example below)

e. Check the showmount and showmount -e outputs. They should be same as that inlamdns:/tmp/lam./showmount* files.

f. Compare the output from the /home/nis/scripts/.cfg file to the output fromthe following commands on the system:

g. If there were any changes to system files made to stop changes, change back thosefiles.


4/4

Note: If changing the /etc/inittab file, run telinit q after changing ( vi) file.

21. Call DSMOPS to restart the applications

22. Close out the change record as successful.

Documents

ML8 SP2 Upgrade