Академический Документы
Профессиональный Документы
Культура Документы
1 INTRODUCTION....................................................................................................................................... 2
2 MANUAL PRECHECKS............................................................................................................................. 2
3 GENERAL............................................................................................................................................... 3
3.1 Exchange SSH user keys.................................................................................................. 3
3.2 IPCCLI Interface to issue SU commands...........................................................................4
3.3 Delete Versions Precheck.................................................................................................. 5
3.4 Delete Versions.................................................................................................................. 6
4 SU UPGRADE ACTIONS........................................................................................................................... 6
4.1 SU Commit Precheck......................................................................................................... 6
4.2 SU Commit......................................................................................................................... 6
4.3 SU Download Precheck..................................................................................................... 6
4.4 SU Download..................................................................................................................... 7
4.5 SU Install Precheck............................................................................................................ 8
4.6 SU Install........................................................................................................................... 8
4.7 SU Firmware Update Precheck.......................................................................................... 8
4.8 SU Firmware Update......................................................................................................... 9
4.9 SU Activate Precheck........................................................................................................ 9
4.10 SU Activate.................................................................................................................. 10
5 SU DOWNGRADE ACTIONS................................................................................................................... 10
5.1 SU Backout Precheck...................................................................................................... 10
5.2 SU Backout...................................................................................................................... 11
5.3 SU Fallback Precheck...................................................................................................... 11
5.4 SU Fallback...................................................................................................................... 11
6 Applying Private Patches.................................................................................................................... 12
IPC Software Upgrade Procedure
1 Introduction
Purpose of this document is to assist only Alcatel-Lucent Test and Field engineers to
perform Software Upgrade actions.
This document explains in brief the steps that are involved in carrying out the IPC
Software Upgrade.
Before starting with the download of new load on to the IPC, operator must exchange the
ssh user keys for swdnload user.
Precheck
All the SU Action has an associated Precheck action to be completed before performing
SU Action. If Precheck Action returns warning then operator must understand the
warning and if required to proceed further then actual SU action should be executed with
FORCED option as YES.
Some of the actions need same input values to be specified for precheck and actual
action. Make sure that this input values match for precheck and actual action.
Monitoring SU Actions
All the below SU actions invoked through IPCCLI will return the status as ACCEPTED
or FAILED to indicate the acceptance of action. Operator must monitor the SU action
status through suReport file after action is accepted through IPCCLI.
suReport will only be available on the solaris/fms blade where SUMgr is currently
available. So during Activate/Backout/Fallback actions wherein there is switchover of
OAMServers suReport should be monitored where SUMgr is available.
For SU Actions like SU Firmware Update, SU Delete Versions, SU Commit status of the
command can also be checked through IPCCLI command.
2 Manual Prechecks
1. Make sure that both solaris/fms blades are in LEAD/ACT state by issuing
RCCcstat command on solaris/fms blade.
2. Make sure that all the 17 OAMServers are running successfully using
rnccheckservers command.
3. Make sure that following ICC processors are pingable from both solaris/fms blade
GICC-3 or GICC-4 from both shelf (GICCpair should be pingable)
GICC-19 or GICC-20 from both shelf (GICCpair should be pingable)
CICC1-12-0 and CICC2-12-0 (SPs)
Atleast 2 TPs per shelf
4. Make sure that all the CMMs and ESC cards are pingable from both solaris/fms
blade.
5. Make sure that “resetRequired” attribute of LIPC is set to “false”. If
resetRequired attribute is set to “true” then perform LIPC Reset through IPCCLI
before proceeding with SU Action.
3 General
3.1 Exchange SSH user keys
This step needs to be carried out on either fms01 or fms02 only once per IPC for the
specific remote host.
1. Generate the SSH user keys for ‘swdnload’ user on IPC using following
command
/flx/RNCsec/current/bin/GenerateSSHUserKeys.sh swdnload
2. Create ‘swdnload’ user on the remote machine from where new IPC load will be
picked. To create the user execute following command on remote machine
useradd -m swdnload
passwd swdnload
On some unix machines, “passwd swdnload” may throw errors. In that case use
following command to give password.
passwd –r files swdnload
touch authorized_keys
5. To make sure that SSH User keys are successfully added to remote host,
Login to IPC as swdnload user and then try sftp or ssh to remote machine.
sftp swdnload@<IP of remote host>
Delete Versions action is used to remove one or more IPC software versions from the IPC
Note: Regardless of the options specified, the delete versions command does not
allow you to delete a current or committed software version.
1. type=IPC
2. version=allVers
version=obvers
To check that all versions except the current, previous, committed, newdownloaded and
newinstalled versions can be deleted.
version=allvers
IPC Software Upgrade Procedure
To check that all versions except the current and committed versions can be deleted.
1. type=IPC
2. version=allVers
3. forced=NO
Specify type and version as specified in the corresponding precheck action above.
4 SU Upgrade Actions
4.1 SU Commit Precheck
For carrying out IPC Upgrade through SUMgr, atleast one load should exist as committed
load on IPC.
SU Commit Precheck does not prompt for any input from operator.
4.2 SU Commit
1. forced=NO
1. sourceFile=
2. server=
3. install=NO
Do not put quotes around sourceFile= and server= when specifying the input parameter.
Specify sourceFile= with the gdf file name without path. Specify only gdf filename
Eg. IPC-02.02.00.02.gdf
4.4 SU Download
1. sourceFile=
2. server=
3. install=NO
4. forced=NO
Do not put quotes around sourceFile= and server= when specifying the input parameter.
Specify sourceFile= with the same value that was specified for corresponding precheck
Action.
Specify server= with the same value that was specified for corresponding precheck
Action.
Specify install= with the same value that was specified for corresponding precheck
Action..
This STEP needs to be followed only if install= option was set to NO in the Download
action above.
1. sourceFile=
Do not put quotes around sourceFile= when specifying the input parameter.
Specify sourceFile= with the gdf file name without path. Specify only gdf filename.
Eg. IPC-02.02.00.02.gdf
4.6 SU Install
1. sourceFile=
2. forced=NO
Do not put quotes around sourceFile= when specifying the input parameter.
Specify sourceFile= with the same value that was specified for corresponding precheck
Action.
1. fwUpdateOperation=UPGRADE
ROLLBACK, Use this option only if firmware update has to be done from the current
load
1. fwUpdateOperation=UPGRADE
2. forced=NO
Specify fwUpdateOperation= with the same value that was specified for corresponding
precheck Action.
1. autobackout=NO
Activate Precheck may throw some warnings, because of improper number of healthy
CICC, GICC processors. In that case you have to activate using forced=YES as
mentioned above.
Note2: If SUActivate action fails for some reason and if the issue can be fixed, then
SUActivate action can be reissued. One needs to do SU Activate Precheck and then
issue SU Activate which will proceed from the same step where it failed earlier.
4.10 SU Activate
1. forced=NO
2. autobackout=NO
Specify autobackout= with the same value that was specified for corresponding
precheck Action
5 SU Downgrade Actions
SU Backout and SU Fallback actions are required incase of Activation failure. Also if
operator is not satisfied with the newly activated load then Backout and Fallback actions
can be performed.
Note that SUBackout will go back to the previous load that is present on the IPC whereas
SUFallback will go back to the committed load.
SU Backout can be performed when operator is not satisfied with the newly activated
load or incase of failure during SU Activate.
Note: SUBackout will be automatically issued, if autobackout option was set to YES
during SU Activate action.
Backout Precheck may throw some warnings, because of improper number of healthy
CICC, GICC processors. In that case you have to backout using forced=YES as
mentioned above.
IPC Software Upgrade Procedure
Note: If Backout action fails for some reason, then backout cannot be reissued.
Operator has to do Fallback, which will move to the previously committed IPC load.
5.2 SU Backout
1. forced=NO
SU Fallback can be performed when operator is not satisfied with the newly activated
load or incase of failure during SU Activate.
Difference between Backout and Fallback is that, Fallback will always go back to
committed load, whereas Backout will go back to previous load.
Fallback Precheck may throw some warnings, because of improper number of healthy
CICC, GICC processors. In that case you have to fallbackactivate using forced=YES as
mentioned above
Note1: If SUFallback action fails for some reason and if the issue can be fixed, then
SUFallback action can be reissued. One needs to do SU Fallback Precheck and then
issue SU Fallback which will proceed from the same step where it failed earlier.
5.4 SU Fallback
1. forced=NO
Any patches applied on IPC before SUActivate, SUBackout or SUFallback will not be
available after the completion of SU Actions. Operator must reapply the patches if they
are required.