6 - ethnoworld.ruTitle: 6_ _ .cdr Created Date: 5/24/2017 1:32:10 PM
SMS1 6_ Upgrade
-
Upload
jeetmajumdar007 -
Category
Documents
-
view
10 -
download
0
description
Transcript of SMS1 6_ Upgrade
Updated: 10/29/08 Case# 66104503 (Closed) New Case# 66123217
1. OS RequirementsAs a minimum, the Solaris 9 OS version of SMS 1.6 requires: * Solaris 9 4/04 OS release (We are at Solaris 9 9/05) * Same version of SMS software on both system controllers (SCs) (Current 1.5.1) * Installation of the Entire Distribution software group of the Solaris OS, including update version and installed patches, on both SCs. * Patches (first supported versions): o 113027-03 (Currently have Rev 04) o 111712-12 (Currently have Rev 16)
*Solaris 9 OS Requirements As a minimum, the Solaris 9 OS version on the domains requires: * Solaris 9 4/04 OS release * Patches (first supported versions): o 112233-09 (Currently have Rev 13)
Note - On systems with UltraSPARC IV+ 1.8 GHz processors, the first supported version of the Solaris 9 OS is Solaris 9 9/05. (Current Sol 9 9/05)
2. Prep WorkSuppress tivoli, inhibit compulertGet root passwordsDetermine the directory where SMS software will be loaded to (/var/tmp/SMS)Ensure you have console accessSet auto-boot? To falseBefore upgrading, make sure that failover between the two System Controllers is active, that no files are queued in `showdatasync`, and that a test failover between the two System Controllers works.
Ensure that the SC data is synchronized between the two SCs by typing this command on the main SC. sc0:# /opt/SUNWsms/bin/setdatasync backup
Ensure that both SC clocks are phase-locked. You can do this by looking at the most recent messages in the platform logs, which say whether the SC clocks are locked or not.
Note - During installation, or whenever the other SC is at the OpenBoot PROM prompt or not running SMS, you might see "SC clocks NOT phase locked" messages in the platform log. You can ignore them
After you install SMS 1.6 and reboot the SC, the hardening performed by the smsinstall script disables remote access.
Install the release-appropriate Solaris patch cluster available at http://sunsolve.sun.com, to ensure that SMS runs properly. Apply any patches to the Solaris OS before reinstalling or upgrading the SMS software.
3. Sequence of EventsSMS 1.5 --> All Patches up to date --> smsupgrade to SMS 1.6
TABLE 3-3 Upgrading SMS Software to Version 1.6
Main SC Spare SC
1. To Unharden the Main SC
2. To Disable Failover on the Main SC
TABLE 3-3 Upgrading SMS Software to Version 1.6
Main SC Spare SC
3. To Back Up the SMS Environment on the Main SC
4. To Unharden the Spare SC
5. To Back Up the SMS Environment on the Spare SC
6. To Upgrade the Solaris OS on the Spare SC (Optional)
7. To Download SMS 1.6 Software From the Web for the Spare SC
8. To Remove the Solaris Security Toolkit from the Spare SC If You Have a Previous Package
9. To Upgrade SMS Software on the Spare SC
10. To Install Any SMS Patches on the Spare SC
11. To Manually Harden the Spare SC
12. To Switch Control to the Spare SC
13. To Upgrade the Spare SC Flash PROMs
14. To Reboot the Spare System Controller
15. To Upgrade the Solaris OS on the Main SC (Optional)
16. To Download SMS 1.6 Software From the Web for the Main SC
17. To Remove the Solaris Security Toolkit from the Main SC If You Have a Previous Package
18. To Upgrade SMS Software on the Main SC
19. To Install Any SMS Patches on the Main SC
20. To Manually Harden the Main SC
21. To Reboot the Main System Controller
22. To Upgrade the Main SC Flash PROMs
23. To Switch Control Back to the Main SC
24. To Enable Failover
25. To Upgrade the System Board Flash PROMs
THE ENTIRE PROCEDURE can be done without bringing the DOMAINS to the OK prompt, however domains do need to be booted after the procedure, so we will bring everything to the ok prompt and bring up when done.
BRING all the DOMAINS down to the OK PROMPT (1.5 hrs)1. fail cluster over as necessary2. bring down the apps3. bring up one telnet sessions for each domain in case of any hang problems4. bring the domains down to the ok prompt
1. Unharden the MAIN System Controller. We did not harden the SC during the last upgrade, therefore skip this step
2, Disable Filover on the Main SC (5 Min) Log onto the MAIN SC as root then su – sms-svc Disable failover: kscfmp2p:sms-svc:1> /opt/SUNWSMS/bin/setfailover off Enter: showfailover and showfailover –r to ensure failover is DISABLED
3. Backup SMS on the MAIN SC You can skip this step as the upgrade does this log in to the MAIN SC as superuser stop sms: /etc/init.d/sms stop backup SMS environment: /opt/SUNWSMS/bin/smsbackup /var/tmp/SMSBKUP/
4. Unharden the SPARE System Controller. We did not harden the SC during the last upgrade, therefore skip this step
5. Backup SMS on the SPARE SC You can skip this step as the upgrade does this log in to the SPARE SC as superuser stop sms: /etc/init.d/sms stop backup SMS environment: /opt/SUNWSMS/bin/smsbackup /var/tmp/SMSBKUP/
6. Upgrade Solaris OS (Optional) N/A
7. Download zip file (10 min) cd kscfmbky:/oamstore/SW_PKGS/SMS/SMS1.6 cp –rp SMS-1_6-S9-sparc.zip /var/tmp/SMS cd /var/tmp/SMS unzip SMS-1_6-S9-sparc.zip The packages and upgrade scripts will be downloaded
After the file is extracted, the SMS 1.6 packages are located in /var/tmp/SMS/sms_1_6_sparc/System_Management_Services_1.6/Product
Note - The smsinstall script and smsupgrade script are located in the directory
/var/tmp/SMS/sms_1_6_sparc/System_Management_Services_1.6/Tools. Use the scripts located in this directory, not the scripts that might already be installed in /opt/SUNWSMS/bin, to run the upgrade and installation processes.
8. Remove Solaris Security Toolkit from the SPARE System Controller (5 Min)pkginfo –l SUNWjasspkgrm SUNWjasspkginfo –l SUNWjass
***********************9. Upgrade the SPARE SMS Software (20 min)
Log onto the SPARE SC as root (from compulert) cd /etc/init.d and enter: ./sms stop (to stop sms – may already be done) cd /var/tmp/SMS/sms_1_6_sparc/System_Management_Services_1.6/Tools Begin the upgrade:
./smsupgrade /var/tmp/SMS/sms_1_6_sparc/System_Management_Services_1.6/Product
The SMS upgrade script will:- Stop the picld daemon- Backup SMS to /var/tmp/- Check to see if Solaris Security Toolkit exists and install it if it does not (SUNWjass)- Install the SMS packages- Restores the previous SMS environment and start the picld daemon- Outputs messages regarding how to manually harden the System Controller
DO NOT Harden the System, as this prevents Console Access. Disregard the error
10. Install SMS Patches on the SPARC System Controller Patching will be done at the very end instead of here since some have to be done at the same time on both SC
11. Manually Harden the SPARE System Controller Skip this step. N/A
12. Switch Control to the SPARE System Controller (20 min) Log onto the main SC a root Stop SMS: /etc/init.d/sms stop Log into the Spare SC: shutdown –i0 –g0 –y At the ok prompt: boot –rv After rebooting the SPARE SC, SMS will start on the spare, acting as the MAIN
13. Upgrade the SPARE System Controller Flash Proms (10 Min) Log into SPARE SC as root and su – sms-svc cd /opt/SUNWSMS/firmware and ensure there are 3 new files: (These are the old ones)
-rw-r--r-- 1 root bin 524288 Jul 21 2005 SCOBPimg.di-rw-r--r-- 1 root bin 524288 Jul 21 2005 nSSCPOST.di-rw-r--r-- 1 root bin 524288 Jul 21 2005 oSSCPOST.di
sc:sms-svc: flashupdate -f /opt/SUNWSMS/firmware/SCOBPimg.di sc1/fp0a. Note: when doing the MAIN use sc0/fp0
sc1:sms-user:> flashupdate -f /opt/SUNWSMS/firmware/SCOBPimg.di sc1/fp0
Use flasupdate again to upgrade the fp1 Flash Prom using the appropriate board For the CP1500 Board (run a prtdiag –v to find the board) a
sc:sms-svc:> flashupdate -f /opt/SUNWSMS/firmware/nSSCPOST.di sc1/fp1o Note: when doing the MAIN use sc0/fp1
sc1:sms-user:> flashupdate -f /opt/SUNWSMS/firmware/nSSCPOST.di sc1/fp1
14. Reboot the SPARE System Controller (20 Min) shutdown –i0 –g0 –y at the ok prompt: boot –rv Once the system comes back up, check to ensure all looks good. See that sms is running
15. Upgrade Solaris OS on the MAIN System Controller Skip this step. N/A
16. Download zip file to MAIN SC (10 min) cd kscfmbky:/oamstore/SW_PKGS/SMS/SMS1.6 cp –rp SMS-1_6-S9-sparc.zip /var/tmp/SMS cd /var/tmp/SMS unzip SMS-1_6-S9-sparc.zip The packages and upgrade scripts will be downloaded
After the file is extracted, the SMS 1.6 packages are located in /var/tmp/SMS/sms_1_6_sparc/System_Management_Services_1.6/Product
Note - The smsinstall script and smsupgrade script are located in the directory /var/tmp/SMS/sms_1_6_sparc/System_Management_Services_1.6/Tools. Use the scripts located in this directory, not the scripts that might already be installed in /opt/SUNWSMS/bin, to run the upgrade and installation processes
17. Remove Solaris Security Toolkit from the MAIN System Controller (5 Min)pkginfo –l SUNWjasspkgrm SUNWjasspkginfo –l SUNWjass
18. Upgrade SMS Software on the MAIN System Controller (20 Min) Log into MAIN SC as root and su – sms-svc cd /etc/init.d and enter: ./sms stop (to stop sms – may already be done) cd /opt/SUNWSMS/firmware and ensure there are 3 new files: (These are the old ones)
-rw-r--r-- 1 root bin 524288 Jul 21 2005 SCOBPimg.di-rw-r--r-- 1 root bin 524288 Jul 21 2005 nSSCPOST.di-rw-r--r-- 1 root bin 524288 Jul 21 2005 oSSCPOST.di
Change directory to the location of the smsupgrade scriptsc0:# cd /var/tmp/SMS/sms_1_6_sparc/System_Management_Services_1.6/Tools
Begin the upgrade process by running the smsupgrade script
sc0:# ./smsupgrade /var/tmp/SMS/sms_1_6_sparc/System_Management_Services_1.6/Product
The SMS upgrade script will:- Stop the picld daemon- Backup SMS to /var/tmp/- Check to see if Solaris Security Toolkit exists and install it if it does not (SUNWjass)- Install the SMS packages- Restores the previous SMS environment and start the picld daemon- Outputs messages regarding how to manually harden the System Controller
19. Install SMS Patches on the MAIN System Controller Patching be done at the very end instead of here since some have to be done at the same time on both SC
20. Manually Harden the MAIN System Controller Skip this step. N/A
21. Reboot the MAIN System Controller (20 Min) shutdown –i0 –g0 –y at the ok prompt: boot –rv Once the system comes back up, check to ensure all looks good. See that sms is running
22. Upgrade the MAIN System Controller Flash Proms (10 Min) Log into MAIN SC as root and su – sms-svc cd /opt/SUNWSMS/firmware and ensure there are 3 new files: (These are the old ones)
-rw-r--r-- 1 root bin 524288 Jul 21 2005 SCOBPimg.di-rw-r--r-- 1 root bin 524288 Jul 21 2005 nSSCPOST.di-rw-r--r-- 1 root bin 524288 Jul 21 2005 oSSCPOST.di
sc:sms-svc: flashupdate -f /opt/SUNWSMS/firmware/SCOBPimg.di sc0/fp0
sc1:sms-user:> flashupdate -f /opt/SUNWSMS/firmware/SCOBPimg.di sc1/fp0
Use flasupdate again to upgrade the fp1 Flash Prom using the appropriate board For the CP1500 Board (run a prtdiag –v to find the board) a
sc:sms-svc:> flashupdate -f /opt/SUNWSMS/firmware/nSSCPOST.di sc0/fp1
sc1:sms-user:> flashupdate -f /opt/SUNWSMS/firmware/nSSCPOST.di sc1/fp1
23. Switch control back to the Main System Controller (15 Min) Log into the SPARE SC (acting at the main) Stop SMS; /etc/init.d/sms stop Log into the MAIN SC: shutdown –i0 –g0 –y at the ok prompt: boot –rv After rebooting the MAIN SC, SMS will start on the MAIN Had to boot the SPARE one more time to start SMS or use /etc/init.d sms start
24. Enable Failover (5 Min) Log onto the MAIN SC, su to root, and su to sms-svc Enter: setfailover on Enter: showfailover and showfailover –r to ensure everything is normal
25. Upgrade the System Board Flash Proms (3 hrs) Log into the MAIN SC as root
Flashupdate the CPU Flash Proms in a domain:a. sc:sms-svc#> flashupdate -d <domainID> -f /opt/SUNWSMS/hostobjs/sgcpu.flash
This must be done for EVERY domain (Enter showplatform to gather all the active DOMAIN
Reboot: shutdown –i0 –g0 –y at the ok prompt: boot –rv Ensure all comes back up ok. Run showfailover –r and showfailover to ensure the MAIN SC is the main and
the SPARE is the spare.
**********************************************26. Applying Patches
Here is the SMS 1.6 patches:. Only one patch can be installed at a time and go thru the complete install instructions before moving onto the next patch.
cd /opt/sysadmin/patches/SMS
Patch Synopsis124243-03 SMS 1.6: scman driver Solaris Release: 10 N/A124264-03 SMS 1.6: SMS 1.6: lpost patch Solaris Release: 9 10124319-04 SMS 1.6: hpost redx libxcpost patch Solaris Release: 9 10123300-10 SMS 1.6: efhd patch (req 124319-02) Solaris Release: 9 10137195-01 SMS 1.6: SMS 1.6: Upgrade from 1.4 patch Solaris Release: 9 10 N/A122608-06(07) SMS 1.6: Solaris Security Toolkit 4.2 Solaris Release: 8 8_x86 9 9_x86 10 10_x86124460-03 SMS 1.6: OBP patch alignes with OBP 4.22.32 Solaris Release: 9 10126372-02 SMS 1.6: directory permissions Solaris Release: 9 10
124264-03 SMS 1.6: SMS 1.6: lpost patch Solaris Release: 9 10 Log onto the MAIN SC using root then su – sms-svc Turn failover off: setfailover off Enter: showfailover to ensure it is disabled Stop the SMS processes on both SC's simultaneously. /etc/init.d/sms stop Ensure all processes have stopped Install the patch on both SC’s (patchadd 124264-03)
Start the SMS processes on the MAIN SC first: /etc/init.d/sms start Enter: showenvironment to get the system status and ensure SMS has started Start the SMS processes on the SPARE SC: /etc/init.d/sms start
Enable failover on the MAIN SC: setfailover on Enter: showfailover to ensure the failover started
124319-04 SMS 1.6: efhd patch Solaris Release: 9 10 Log onto the MAIN SC using root then su – sms-svc Turn failover off: setfailover off Enter: showfailover to ensure it is disabled Stop the SMS processes on both SC's simultaneously. /etc/init.d/sms stop Ensure all processes have stopped Install the patch on both SC’s (patchadd 124319-02)
Start the SMS processes on the MAIN SC first: /etc/init.d/sms start Enter: showenvironment to get the system status and ensure SMS has started Start the SMS processes on the SPARE SC: /etc/init.d/sms start Enable failover on the MAIN SC: setfailover on Enter: showfailover to ensure the failover started
123300-10 SMS 1.6: efhd patch Solaris Release: 9 10 Log onto the MAIN SC using root then su – sms-svc Turn failover off: setfailover off Enter: showfailover to ensure it is disabled Stop the SMS processes on both SC's simultaneously. /etc/init.d/sms stop Ensure all processes have stopped Install the patch on both SC’s (patchadd 123300-10)
Start the SMS processes on the MAIN SC first: /etc/init.d/sms start Enter: showenvironment to get the system status and ensure SMS has started Start the SMS processes on the SPARE SC: /etc/init.d/sms start Enable failover on the MAIN SC: setfailover on Enter: showfailover to ensure the failover started
122608-06(07) SMS 1.6: Solaris Security Toolkit 4.2 Solaris Release: 8 8_x86 9 9_x86 10 10_x86 Log onto the MAIN SC using root then su – sms-svc Turn failover off: setfailover off Enter: showfailover to ensure it is disabled Stop the SMS processes on both SC's simultaneously. /etc/init.d/sms stop Ensure all processes have stopped Install the patch on both SC’s (patchadd 123300-10) Start the SMS processes on the MAIN SC first: /etc/init.d/sms start Enter: showenvironment to get the system status and ensure SMS has started Start the SMS processes on the SPARE SC: /etc/init.d/sms start Enable failover on the MAIN SC: setfailover on Enter: showfailover to ensure the failover started
124460-03 SMS 1.6: OBP patch alignes with OBP 4.22.32 Solaris Release: 9 10 This patch aligns SMS 1.6 with OBP 4.22.32 Changes will be in effect after booting the domain Cd /opt/sysadmin/patches/SMS Patchadd 124460-03 Do this on both the MAIN and SPARE SC
126372-02 SMS 1.6: directory permissions Solaris Release: 9 10 Log onto the MAIN SC using root then su – sms-svc Turn failover off: setfailover off Enter: showfailover to ensure it is disabled Stop the SMS processes on both SC's simultaneously. /etc/init.d/sms stop Ensure all processes have stopped Install the patch on both SC’s (patchadd 123300-10)
Start the SMS processes on the MAIN SC first: /etc/init.d/sms start
Enter: showenvironment to get the system status and ensure SMS has started Start the SMS processes on the SPARE SC: /etc/init.d/sms start Enable failover on the MAIN SC: setfailover on Enter: showfailover to ensure the failover started
27. Getting Console access to each Domain (15 min) Sign onto compulert and access the first domain You may need to change the sms-svc password – doesn’t matter what you change it to Once changed you should receive the sc:sms-svc> prompt Enter: console –d <domain> Hit Enter, which should bring you to the ok prompt Cntl/q out of compulert Continue doing this for each domain so that each one has console access at the ok prompt
28. Booting the Domains (3 hours) Log into the MAIN SC session and su – root cd /var/opt/SUNWSMS/adm/<domainid> and tail –f messages This is so that you can watch the messages
file while the domain is processing
Telnet to another login on the MAIN SC and su – sms-svc Run showplatform to see what status they are in and to obtain all your DOMAIN ids Enter: setkeyswitch –d <domain> standby Once the standby completes, Enter: setkeyswitch –d <domain> off This will turn off the system boards Once the off completes, Enter: setkeyswitch –d <domain> on This will power on the system boards and
reboot the box Repeat this procedure for each domain, one at a time.
29. Checks & Balances (15 min) Bring up the application and balance the cluster on clustered boxes Run Tivoli checks on all domains and SC Enter: prtconf -V on each domain to ensure the OBP is at 4.22.20 Turn back on Compulert Send out email of completion
30. Re-create the Links which were removed (THIS IS FOR DOMAIN 1 ONLY – these commands should be done appropriate to the DOMAIN you are working with
cd /var/opt/SUNWSMS/SMS1.5/adm and make note of the following linkslrwxrwxrwx 1 root other 1 May 7 12:06 kscfmn1d -> Glrwxrwxrwx 1 root other 1 May 7 12:06 kscfmn1e -> Flrwxrwxrwx 1 root other 1 May 7 12:06 kscfmn1f -> Elrwxrwxrwx 1 root other 1 May 7 12:06 kscfmn1g -> Blrwxrwxrwx 1 root other 1 May 7 12:06 kscfmp1a -> Clrwxrwxrwx 1 root other 1 May 7 12:06 kscfmp1b -> Dlrwxrwxrwx 1 root other 1 May 7 12:06 kscfmp1c -> A
They need to be recreated under the new version of SMS Bring up a 2nd telnet session on the system controller and cd /var/opt/SUNWSMS/SMS1.6/adm Create a softlink like the one that existed in the previous version of SMS
ln –s G kscfmn1dln -s F kscfmp1eln -s E kscfmp1fln -s B kscfmp1gln –s C kscfmp1aln –s D kscfmp1bln –s A kscfmp1c