Pre
Migration Checks
-------------------------- --
30 to 40 min
1. Check the
consistency of installed Licensed Program Products (LPPs)
#lppchk -v -m3
This will ideally display the
inconsistencies (if any) of the LPPs.
# instfix -i|grep -i ml
2. Check previous
day night incremental backup is completed successfully.
if the scheduled backup still going on, wait
for backup to complete.
If the scheduled backup is not successful,
run the backup manually
more
/tsmlog/dsmsched.log | grep -i successfully
3. Take the
mksysb backup and copy the mksysb to
tusnim00 server
4. Capture all
the below outputs into user home (/home/rchandra)directory and scp to tusnim00
server also.
df -g >
df.orig
lspv >
lspv.orig
cat
/etc/filesystems > filesystems.orig
lscfg >
lscfg.orig
lsconf>
lsconf.orig
ps -ef >
ps.orig
netstat -nr >
netstat.orig
ifconfig -a >
ifconfig.orig
lsfs >
lsfs.orig
lsdev -Cc disk
> diskconfig.orig
cp /etc/motd /home/rchandra/
cp /usr/sbin/sendmail /home/rchandra/
cp
/etc/inetd.conf /home/rchandra/
cp /etc/environment
/home/rchandra/
5. Check the compatibility
of firmware with the upgrade version ( AIX 6.1)
6. /tmp
filesystem will be clear during migration. Check /tmp before initiate
migration. Take the backup of files and
directories to some other filesystem or server if require.
7 . Check the status of all
harddisks (local,virtual and SAN) status configured in server.
8. Make sure that all
application/data VG filesystems backing
up to TSM server.
Clone
the rootvg using alt_disk method
--------------------------------------------------
Note: We are using only phase1 and phase3
of IBM alt_disk_install method
1. Disable the quorum before unmirroring 20 Min
chvg -Qn rootvg
Unmirrorvg rootvg hdiskx
lsvg
-l rootvg
Check filesystems, which are not mirrored.
Also compare the output of "lspv -l hdisk0"
and "lspv -l hdisk1" and try to find out the unmirror filesystems.
Then
migrate the filesystem as per your requirement. E.g. if you want to unmirror
hdisk1, migrate all unmirrored filesystems to hdisk0 from hdisk1.
e.g. #migratepv -l pdumplv hdisk1 hdisk0
#unmirrorvg rootvg hdisk1
#chpv -c hdisk1
#reducevg rootvg hdisk1
#bootlist -m normal hdisk0
#chvg -Qn rootvg
#synclvodm -Pv rootvg
2. Clone rootvg
40 to 50 Min
#mkdir /tmp/Migration
#chmod 777 /tmp/Migration
#alt_disk_install -C -P 1 hdisk5 >
/tmp/Migration/rootvg_clone.log_1 2>&1
#tail -f
/tmp/Migration/rootvg_clone.log_1
Note ; hdisk1 should be the empty disk and
not assigned to any volumegroup(generally we will use the disk which we free up
by unmirroring rootvg)
It
will create an additional VG called altinst_rootvg and filesyems named liked
/alt_usr, /alt_home etc.
3. Complete
update process:
10 Min
#alt_disk_install -C -P 3 hdisk5 >
/tmp/Migration/altinst_P3.log 2>&1
It will unmount all
the /alt_usr, /alt_home etc. filesystems and then varyoff the altinst_rootvg
NIM server side preparation
------------------------------------- 15 Min
1 . Prepare the NIM resources as below
Define the client ( ex : tusfidb07)
Prepare the respective lppsource using BOS
filesets (AIX 6.1)
Make a spot using LPPSOURCE
Bind the resources lppsource and spot with the client machine(
nim_bosinst)
Below are NIM resources which we are using
currently in tusnim00
LPPSSOURCE - AIX61TL06SP05_lppsource
SPOT - AIX61TL06SP05_spot
Note: Here we should use rte option while binding client with
the NIM resources (lppsource and spot).
NIM
Client side Preparation
-------------------------------------
Note : Perform a precautionary reboot before starting any
migration steps.
1 . Shut down the server once we get the
confirmation call from Application team.
10 Min
2 . Boot the client node in SMS menu and
start the migration activity. 10 Min
Set the IP parameters properly
NIM server IP :
Client IP :
Gateway:
Subnet mask:
Perform ping test to NIM server ( If fails
stop the activity and check the network connectivity between NIM server and
client)
Select network as boot device.
3 . Change the installation option as
Migration after language selection. 120 Mins
Check the destination disk where migration
going to happen (That should be your currnent running rootvg disk generally
hdisk0).
Observe and give few inputs till the fileset installation started .Once
Migration completed server will automatically reboot with new version of OS
Post
Migration Tasks
----------------------------
Check the oslevel and consistency of the
filesets using below command
#lppchk –v –m3
1)
Upgrade the TL to latest level
AIX 6.1 TL7 SP2 using smit update_all 60
Mins
Filesets available in
tadmin server under
/aix_sw/AIX61TL7SP2.
Run bosboot and set
your bootlist order to correct harddisk before you initiate reboot.
#bosboot –ad
/dev/diskname ( disk should be part of rootvg)
#bootlist –m normal hdiskx hdisky
2)
Check sshd daemon is running
after migration, If not do the uninstall and
reinstall of openssh and openssl filesets.
Recreate the ssh
keys after installing ssh.
15 Min
3) Modify
the /etc/motd file after migration with server and data centre
4) Check
/etc/environment and modify if required (ex: LANG parameter LANG=en_US)
No comments:
Post a Comment