Document fins/I0804-1
FIN #: I0804-1
SYNOPSIS: SMS 1.1 to 1.2 upgrade path using the software available with Solaris
8 Update 7 requires complete reconfiguration of platform
DATE: Mar/22/02
KEYWORDS: SMS 1.1 to 1.2 upgrade path using the software available with Solaris
8 Update 7 requires complete reconfiguration of platform
---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------
FIELD INFORMATION NOTICE
(For Authorized Distribution by SunService)
SYNOPSIS: SMS 1.1 to 1.2 upgrade path using the software available with
Solaris 8 Update 7 requires complete reconfiguration of platform.
Sun Alert: No
TOP FIN/FCO REPORT: Yes
PRODUCT_REFERENCE: SMS 1.1 on Sun Fire 15K
PRODUCT CATEGORY: Server / Service
PRODUCTS AFFECTED:
Systems Affected
----------------
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
- F15K ALL Sun Fire 15000 -
X-Options Affected
------------------
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
- - - - -
PART NUMBERS AFFECTED:
Part Number Description Model
----------- ----------- -----
- - -
REFERENCES:
URL: http://cpre-amer.west/esg/hsg/starcat/
http://sdpsweb.ebay/FIN_FCO/FIN/FINI0798-1_dir/SMS1.1toSMS1.2UpgradeProc
http://cpre-amer.west/esg/hsg/starcat/docs.html
http://www.sun.com/servers/highend/sunfire15k/sms.html#1
PROBLEM DESCRIPTION:
Upgrading an F15K system from SMS 1.1 to SMS 1.2 using the software
provided with Solaris 8 Update 7 might cause serious system problems if
the proper steps are not followed. Failure to follow the amended
upgrade procedure, as detailed in this FIN, will result in the loss of
operation of the system controller being upgraded. The SMS system
daemons will not start properly, and the controller will be unable to
assume control of the platform. The platform and domain states will
not be preserved. Operation of running domains might be interrupted.
Changes in the structures of some files between the two SMS versions
are not accounted for with the procedure of using smsbackup(1m) and
smsrestore(1m) commands. Additionally, some system critical files are
not saved or are overwritten. Should one wish to upgrade at this time,
manual intervention is required to save the appropriate files and
restore operation. In addition, domain configuration and system state
can not be properly preserved. For this reason, it is recommended
that the upgrade be planned with the intention of shutting down and
reconfiguring all domains.
Attempts to keep both versions of SMS installed and to use smsversion
to switch back and forth will not work. At this time it is not
recommended to attempt to have both SMS versions resident on the same
system controller. Here are some of the symptoms if both of SMS
versions reside in the SC:
. SMS will fail to start after the upgrade is complete.
. System controller will be unable to control the platform.
. User defined access control configuration for administration
commands will be lost.
. Domain configuration may be lost.
For further information on these issues, please reference the StarCat news
section at:
http://cpre-amer.west/esg/hsg/starcat/
IMPLEMENTATION:
---
| | MANDATORY (Fully Pro-Active)
---
---
| X | CONTROLLED PRO-ACTIVE (per Sun Geo Plan)
---
---
| | REACTIVE (As Required)
---
CORRECTIVE ACTION:
An Authorized Enterprise Services Field Service Representative may avoid
the above mentioned problems by following the recommendations as shown
below.
Please adhere to the following guideline in order to upgrade from
SMS1.1 to SMS1.2:
1. Ensure the system is in a stable condition:
a) No commands or hpost running, check this with a ps -ef
check the following are not present:
hpost
smsconfig
poweron
poweroff
setkeyswitch
cfgadm
rcfgadm
addtag
deletetag
addboard
moveboard
deleteboard
setbus
setdefaults
setobpparams
setupplatform
enablecomponent
disablecomponent
b) datasync complete, ie 0 files queued.
sms-svc> showdatasync
File Propagation State: ACTIVE
Active File: -
Queued Files: 0
2. On both SC's, as root create an smsbackup:
# /opt/SUNWSMS/bin/smsbackup <target directory>
Note the name and location of both of these files, you will
need these later.
3. From MAIN SC (I will call this SC0 for this document), as
sms-svc:
sms-svc:3> setfailover off
showfailvoer: Command not found
sms-svc:4> showfailover
SC Failover Status: DISABLED
4. On SPARE SC (I will call this SC1 for this document), as root:
# /etc/init.d/sms stop
5. As root on SC1 unpack and install SMS 1.2 packages, following
instructions detailed in:
SMS 1.2 Installation Guide & Release Notes (S8U7)
==> Manually reinstall the SMS Software Packages
==> Chapter 1, Page 13
http://cpre-amer.west/esg/hsg/starcat/docs.html
To obtain 1.2 packages, go to:
http://www.sun.com/servers/highend/sunfire15k/sms.html#1
Uncompress and unpack the tar file and install the packages.
Note that the package order is very important to ensure that
SUNWSMSr (#11) and SUNWSMSop (#7) are installed first. The
following packages make up the SMS 1.2 release:
Packages:
SUNWSMSdf
SUNWSMSjh
SUNWSMSlp
SUNWSMSmn
SUNWSMSob
SUNWSMSod
SUNWSMSop ..SECOND
SUNWSMSpd
SUNWSMSpo
SUNWSMSpp
SUNWSMSr ..FIRST
SUNWSMSsu
SUNWscdvr.u
SUNWufrx.u
SUNWufu
# pkgadd -d .
Package order:
11,7,1-6,8-10,12-15
Check packages were installed without failure:
# pkginfo -c SMS
Lists:
SUNWSMSdf
SUNWSMSjh
SUNWSMSlp
SUNWSMSmn
SUNWSMSob
SUNWSMSod
SUNWSMSop
SUNWSMSpd
SUNWSMSpo
SUNWSMSpp
SUNWSMSr
SUNWSMSsu
SUNWscdvr.u
# pkginfo -i SUNWufrx SUNWufu
Lists:
SUNWufrx
SUNWufu
# pkginfo -p
Lists:
nothing
6. As root on SC1 install SMS 1.2 patches listed at:
http://cpre-amer.west/esg/hsg/starcat/patches.html#SMS 1.2
Be sure to check that they have installed successfully.
7. As root on SC1 use smsversion to switch to SMS1.2, then use
smsrestore to restore the back up made in #2, follow the detailed
instructions at:
SMS 1.2 Installation Guide & Release Notes (S8U7)
==> Restore or Upgrade SMS Software
==> Chapter 1, Page 17
http://cpre-amer.west/esg/hsg/starcat/docs.html
# /opt/SUNWSMS/bin/smsversion
# /opt/SUNWSMS/bin/smsrestore <SC1 smsbackup file>
8. Reboot SC1
9. As root on SC0 stop SMS:
# /etc/init.d/sms stop
10. As root on SC1 start SMS:
# /etc/init.d/sms start
SMS may ask to run smsconfig, if it does do a "smsconfig -m"
and
reboot.
# /etc/init.d/sms start
sms: smsconfig(1M) has not been run. Unable to start sms services.
SC1 will become the MAIN.
11. Repeat #5-7, 9, and 10 for SC0.
12. As sms-svc on SC1 Activate failover:
# setfailover on
Please go to the following URL in order to obtain more detailed
upgrading procedure:
http://sdpsweb.ebay/FIN_FCO/FIN/FINI0798-1_dir/SMS1.1toSMS1.2UpgradeProc
COMMENTS:
None
=========================================================================
Implementation Footnote:
i) In case of MANDATORY FINs, Enterprise Services will attempt to
contact all affected customers to recommend implementation of
the FIN.
ii) For CONTROLLED PROACTIVE FINs, Enterprise Services mission critical
support teams will recommend implementation of the FIN (to their
respective accounts), at the convenience of the customer.
iii) For REACTIVE FINs, Enterprise Services will implement the FIN as the
need arises.
-------------------------------------------------------------------------
All released FINs and FCOs can be accessed using your favorite network
browser as follows:
SunWeb Access:
--------------
* Access the top level URL of http://sdpsweb.ebay/FIN_FCO/
* From there, select the appropriate link to query or browse the FIN and
FCO Homepage collections.
SunSolve Online Access:
-----------------------
* Access the SunSolve Online URL at http://sunsolve.Corp/
* From there, select the appropriate link to browse the FIN or FCO index.
Internet Access:
----------------
* Access the top level URL of https://infoserver.Sun.COM
--------------------------------------------------------------------------
General:
--------
* Send questions or comments to finfco-manager@Sun.COM
--------------------------------------------------------------------------
Copyright (c) 1997-2003 Sun Microsystems, Inc.