5.3 act-upgrade
Use this command to perform a software upgrade from a source release to the target release on an in-service system.
Caution:
It is strongly recommended that this command be used only in conjunction with the system Upgrade Procedure for your target release. The Upgrade Procedure provides step-by-step information on performing an upgrade.Parameters
- action (mandatory)
- The action to be performed for the upgrade
process.
Caution:
The convertoam and netcomplete actions should be used only under the direction of My Oracle Support (MOS).- Range:
- yyyyyyyyyy
Up to 10 alphabetic characters. Valid actions are:
- chkrel—Validates the stored upgrade target release on the physical disk as specified by the src parameter.
- convertoam—Converts the standby OAM database.
- convertstp—Performs all OAM and network conversions necessary for an upgrade. This command transitions through all of the upgrade phases to upgrade completion. If measurement collection is turned on, this command automatically inhibits measurements during the upgrade. Upon completion of the upgrade, this command returns the MASPs to full-function mode with measurement collection turned back on.
- createsets—Assigns network cards to upgrade-grouping sets.
-
dbstatus—Reports the status of all database partitions on the TDM
fixed disks and the removable drive(s) (similar to the
rept-stat-db:display=version
command). - displaysets—Reports the upgrade-grouping sets of network cards.
- getrel—Retrieves the upgrade target release file from either the EAGLE software release distribution server or the plug-in flash drive. It then expands the data on the inactive partition group of the hard disks.
- netcomplete—Indicates upgrade completion and places the system in a fully functional mode.
- oamcomplete—Sets the upgrade phase number to 3, and enables the beginning of controlled card loading.
- refreshsets—Not yet supported.
- verifysets—Verifies that the card set list is consistent with the current EAGLE configuration and displays detailed information on any inconsistencies found.
- force (optional)
- Allows the user to override Card Set List verification and perform upgrade when only minor inconsistencies are present.
- release (optional)
- The name of the software release file to be
downloaded.
This file contains the upgrade target release on the software release distribution server or plug-in flash drive.
- Range:
-
xyyyyyyyyyyyyyyyyyyyyyyyyyyyyy
1 alphabetic character followed by up to 29 alphanumeric characters. One or more periods can be used.
Note:
The value must be at least 11 characters in length and must contain a hyphen (-). The format of the value must be xx.xx.xx-yy.yy.yy, where xx.xx.xx is the release number, and yy.yy.yy is the engineering build number.
Example
act-upgrade:action=convertstp
act-upgrade:action=dbstatus
act-upgrade:action=convertstp:thres=75
act-upgrade:action=getrel:release="46.7.0.0.0-74.2.0.tar.gz":src=usb
act-upgrade:action=chkrel:src=fixed
Dependencies
The value specified for the action parameter must correspond to a specific upgrade phase:
- action=convertoam—upgrade phase=0 and 1
- action=oamcomplete—upgrade phase=2
- action=convertnet—upgrade phase=3
- action=netcomplete—upgrade phase=3
- action=convertstp—upgrade phase=0-3
The Measurements Collection function must be turned off
(chg-meas:collect=off
) or the Measurements
Platform feature must be turned on (chg-measopts:platformenable=on
) before a value of
convertoam,
oamcomplete, or
netcomplete can be specified for the
action parameter.
A valid upgrade release must reside on the plug-in flash drive or the inactive partition of the fixed disk.
The standby OAM database must be the source release.
The current OAM database must be the source release.
The database partition must be coherent.
The database partition must be in the correct functional mode.
The action=convertstp and thres parameters must be specified together in the command.
Upgrade conversion cannot be initiated from a telnet-type terminal (terminal IDs 17-40).
The DCM cards are obsolete for SS7IPGW, IPGWI, IPLIM, and IPLIMI applications.
The action=getrel and release parameters must be specified together in the command.
An IPSM card must be provisioned and in service before a value of getrel or chkrel can be specified for the action parameter.
The
ent-ftp-serv:app=dist
command must be entered before a value of
getrel or
chkrel can be specified for the
action parameter.
The act-upgrade:action=convertstp cannot be issued with any removable media inserted in any of the USB ports.
Invalid hardware configuration alarms are set or an HMUX alarm must be addressed.
All cards that are in the auto-inhibited state must be removed before this command can be entered.
Cards that prevent the IMT buses from being inhibited during the upgrade cannot exist in the system.
The specified source drive must be at the correct database version for the upgrade to proceed.
The plug-in flash drive cannot contain an EAGLE backup image.
If the src=usb parameter is selected, then the plug-in flash drive upgrade media must be inserted in the Active OAM's flush-mounted USB port.
The internal RAM disk must be available for the plug-in flash drive's upgrade image to be unpackaged.
The disk that contains the upgrade target release must be in a known upgrade mode.
If the src=usb or src=server parameter is specified, then the action=getrel parameter must be specified. If the src=fixed parameter is specified, then the action=getrel parameter cannot be specified.
The EAGLE PVN address in the source database cannot be identical to the EAGLE FCNA or FCNB network address in the target database.
The icdpnunknx and icdpnunknX and the gcdpnunknx and gcdpnunknX NPP Action Sets cannot co-exist in the source release.
The value specified for the release parameter must be at least 11 characters in length and contain a hyphen (-). The format of the value must be xx.xx.xx-yy.yy.yy, where xx.xx.xx is the release number, and yy.yy.yy is the engineering build number.
The card must have sufficient DRAM memory to perform the GTMOD table Health Check.
The AMGTT data in the GTT table cannot exceed the capacity of the GTMOD table (100 K).
Unable to access GTT table from source drive.
The MFC feature must be ON prior to upgrading to release 46.2 or later.
The action=refreshsets and action=verifysets parameters are not supported.
The thres parameter cannot be specified if the threshold type (threstype) has been changed to set.
When issuing the
act-upgrade
command with the threstype
assigned to card sets, the list of card sets needs to be created and valid.
When issuing the act-upgrade command with the threstype assigned to Card Set, the card set list must be consistent with the current EAGLE configuration, unless force=yes is allowed and specified. Details of any such inconsistencies and recovery instructions will be reported in a similar manner as act-upgrade:action=verifysets.
Security log purging must be stopped
(CHG-ATTR-SECULOG:PURGEPERIOD=0
) when the
act-upgrade
command is executed.
Notes
The
act-upgrade:action=convertstp
command
executes all four upgrade phases consecutively.
If the
act-upgrade:action=convertstp
command
is entered following a command abort, the upgrade processing determines the
last upgrade phase that was successfully completed. The upgrade processing then
attempts to restart from that point to successful completion. Re-entering the
act-upgrade:action=convertstp
command
following a command abort is the recommended method for recovery.
The TDMs and plug-in flash drives have upgrade phase indicators. The upgrade command expects the disks to be in certain phases before executing a specific action. If the disks are not in the correct phases, an error is generated.
The
act-upgrade:action=dbstatus
command
generates output similar to that provided by the
rept-stat-db:display=version
command.
The thres parameter is used to:
- Allow multiple cards to be upgraded together, as
long as the specified percentage of links remains in service. The value is
applied to groups of links based upon the link-supporting group or the entire
system. The grouping is set by the
chg-upgrade-config:threstype=
command. - Enable SCCP thresholding, which allows multiple Service Module cards to be upgraded together. The specified thres parameter value is not used to determine the number of Service Module cards to upgrade. The peak SCCP load since the last OAM boot is used to determine the number of cards that must remain in service (at least half of the cards must remain in service).
- Enable the non-provisioned flash function, which flash-downloads any boot-prom type card if the card is in the system but not provisioned.
The
act-upgrade:action=getrel
action
defaults to getting the release from the provisioned IPSM card using the
provisioned FTP Server. If the
src=usb parameter is specified, then
the release is obtained from the plug-in USB flash drive upgrade media.
Output
Note:
Theact-upgrade:action=convertstp
command
performs the OAM conversion and the network conversion. During the
conversion, this command broadcasts the current activity in the scroll area.
Refer to Appendix B of the EAGLE Release Software Upgrade Procedure for a
sample of message output.
The action dbstatus reports the current database status.
act-upgrade:action=dbstatus
eaglestp 15-02-13 11:45:51 MST EAGLE5 45.0.1-64.70.35 Upg Phase 0
DATABASE STATUS: >> OK <<
TDM 1114 ( STDBY) TDM 1116 ( ACTV )
C LEVEL TIME LAST BACKUP C LEVEL TIME LAST BACKUP
- -------- ---------------------- - -------- ----------------------
FD BKUP Y 210 - - Y 210 - -
FD CRNT Y 210 Y 210
MCAP 1113 MCAP 1115
- -------- - --------
RD BKUP - - - - - - - -
USB BKP - - - - - - - -
CARD/APPL LOC C T LEVEL TIME LAST UPDATE VERSION STATUS
--------- ---- - - ---------- ----------------- -------------------
OAM-RMV 1113 - - - - - -
TDM-CRNT 1114 Y N 210 15-01-16 12:22:02 135-000-000 NORMAL
TDM-BKUP 1114 Y - 210 15-01-16 12:22:02 135-000-000 NORMAL
OAM-RMV 1115 - - - - - -
OAM-USB 1115 - - - - - -
TDM-CRNT 1116 Y N 210 15-01-16 12:22:02 135-000-000 NORMAL
TDM-BKUP 1116 Y - 210 15-01-16 12:22:02 135-000-000 NORMAL
INACTIVE PARTITION GROUP
CARD/APPL LOC C T LEVEL TIME LAST UPDATE VERSION STATUS
--------- ---- - - ---------- ----------------- -------------------
TDM-CRNT 1114 N - 1 00-00-00 00:00:00 136-000-000 NORMAL
TDM-BKUP 1114 N - 1 00-00-00 00:00:00 136-000-000 NORMAL
TDM-CRNT 1116 Y - 1 00-00-00 00:00:00 136-000-000 NORMAL
TDM-BKUP 1116 Y - 1 00-00-00 00:00:00 136-000-000 NORMAL
;