1 Introduction
Purpose and Scope
This document describes methods utilized and procedures executed to perform a software upgrade on any in-service EAGLE-based STP to EAGLE Software Release 45.0, 45.1, 46.0, 46.1, 46.2, 46.3, 46.5, or 46.6 as well as any future maintenance releases. The audience for this document includes Oracle customers as well as these Oracle CommunicationsEAGLE groups: Software Development, Product Verification, Technical Communications, and Customer Service including the Upgrade Center and New Product Engineering. This document provides step-by-step instructions to execute any upgrade to Release 45.0 and beyond.
See appropriate upgrade kit instructions/references for the software upgrade of peripheral equipment.
References
External
- EAGLE 45.0 and above Health Check Procedure, E54339, latest revision
- EAGLE 46.8 Maintenance Manual, F11910, latest revision
- EAGLE 46.8 Database Administration – System Management, F11885, latest revision
Internal
The following are references internal to Oracle. They are provided here to capture the source material used to create this document. Internal references are only available to Oracle personnel.
- EAGLE Hardware Field Baseline, CGBU_ENG_24_1893, latest revision, Tekelec
- TEKELEC Acronym Guide, CGBU_ENG_24_1732, current revision
- Tekelec Eagle - Eng Release Mapping web page, , http://devtools.nc.tekelec.com/cgi-bin/eng_eag.cgi, Tekelec
- Tekelec CSR-PR Reports By Build, http://devtools.nc.tekelec.com/cgi-bin/release_desc.cgi
- Tekelec Tekpedia web page, http://tekpedia.ssz.tekelec.com/tekpedia/index.php/Methods_to_correct_distributed_network_database_(DDB)_inconsistencies, Tekelec
- EAGLE 45.0 Product Functional Specification PF005994, latest version, GSS Product Management
- EAGLE 45.1 Product Functional Specification PF006147, latest version, GSS Product Management
- EAGLE 46.0 Product Functional Specification PF006165, latest version, GSS Product Management
- EAGLE 46.6 Product Functional Specification CGBU_025773, latest version, GSS Product Management
Software Release Numbering
To determine the correct GPL version numbers for the EAGLE® applications, refer to the appropriate internal release-mapping web tool or to the Release Notice located on My Oracle Support web portal. Appendix G describes how to access My Oracle Support web portal. For FOA releases or Engineering prototype releases, refer to internal references [6] in section 1.2.2.
Note:
Verifying the correct GPL versions ensures that the system is being upgraded to the correct target software release.Database Version Number
To determine the correct database version numbers for the EAGLE® release, refer to the appropriate internal release-mapping web tool. Appendix G describes how to access My Oracle Support web portal. For FOA releases or Engineering prototype releases, refer to internal references [6] in section 1.2.2.
Acronyms and Terminology
Table 1-1 Acronyms
| Acronym | Definition |
|---|---|
| AWA | Alternate Work Area |
| DDB | Dynamic Database |
| DDL | Dynamic Data Load |
| E5-MDAL | EAGLE Maintenance Disk and Alarm Card |
| E5-OAM | EAGLE Operation, Admission, & Maintenance |
| FAK | Feature Access Key |
| FOA | First Office Application |
| GA | General Availability |
| GLS | Generic Loading Service |
| GPL | Generic Program Load |
| GPSM | Legacy General Purpose Service Module |
| IMT | Interprocessor Message Transport |
| IS-NR | In Service - Normal |
| IS-ANR | In Service - Abnormal |
| KSR | Keyboard Send & Receive |
| LA | Limited Availability |
| LIM | Link Interface Module |
| LNP | Local Number Portability |
| LSMS | Local Service Management System |
| MCPM | Measurement Collection and Polling Module |
| MPS | Multi Purpose Server |
| MSD | Media Software Delivery |
| OAM | Operations Administration and Maintenance |
| OAP | Operations, Administration and Maintenance Applications Processor |
| OOS-MT | Out Of Service - Maintenance |
| RMD | Removable Media Drive/Disk such as USB |
| SAK | Software Access Key |
| SATA | Serial ATA |
| SEAS | Signaling Engineering and Administration System |
| SLIC | Service and Link Interface Card |
| SSD | Server Software Delivery |
| STP | Signal Transfer Point |
| TDM | Terminal Disk Module |
| TPS | Transactions Per Second (feature) |
| UHC | Upgrade Health Check |
Table 1-2 Terminology
| Terminology | Definition |
|---|---|
| Backout (abort) | The process to take a system back to a Source Release prior to completion of upgrade and commitment to Target release. Includes restoration of source databases and system configuration. |
| DDay | Date of the start of the maintenance window of the upgrade execution. |
| E5-OAM system | An EAGLE running with E5-MCAP & E5-MDAL cards for front-end hardware. |
| Fixed disk based upgrade | An upgrade that uses the inactive partitions of the fixed disks as the workspaces to covert the data. With 9Gb and bigger hard drives, this is the expected method. |
| HHour | Hour at which the system enters upgrade phase 0 during upgrade execution. |
| Incremental upgrade | EAGLE: Upgrade to a maintenance release (external customers) or upgrade to a new build (internal test labs). |
| Intra-release upgrade |
Any upgrade within a release; this includes incremental as well as full function upgrades where only the minor database version changes. Note: Intra-release upgrades are not covered by this document. |
| Intrusive Operation | Operation that impacts the redundancy of the system by isolation of the duplicate component. |
| Legacy system |
An EAGLE running with GPSMII, TDM, & MDAL cards for front-end hardware. This hardware is obsolete beginning in Release 45.0. |
| Non-intrusive Operation | Operation that collects data and does not impact the redundancy of the system. |
| Non-preserving upgrade | “Upgrade” that does not adhere to the standard goals of software upgrade methodology. The outcome of the execution is that the system is running on the Target Release; however the Source Release database was not preserved. |
| Rollback | The process to take a system from a Target Release back to a Source Release including preservation of databases and system configuration. |
| Session 0 | This is a new set of tasks required in the Upgrade Health Check #2 timeframe. The work needs to be accomplished successfully prior to the execution of the upgrade. |
| Source release | Software release from which the system is upgraded. |
| Target release | Software release to which the system is upgraded. |
| Upgrade Media | The USB thumb drives for E5-MCAP systems |
Table 1-3 Generic VS. E5-OAM Terminology
| Generic Term | E5-OAM Term |
|---|---|
| Drive Slot | Thumb Drive on the E5-MCAP |
| Fixed Disk | Sata Drive |
| MASP | E5-MCAP |
| Removable media | Removable media |
| RMD | USB Thumb Drive |
| Upgrade media | USB Thumb Drive |
Recommendations
- It is recommended that command input and command-line/scroll-area output be captured during the execution of an upgrade. The preferred method is the use of two serial terminals; one used to enter commands and to echo to the second, which is set to capture all output except for traffic-related unsolicited messages. These terminals should be configured as KSR type. Another acceptable method is the use of one serial terminal, which has a terminal-emulation application that supports input/output capture. This terminal should be set to the KSR type. It is unacceptable to use a telnet terminal since it does not support the echo capability. Serial terminals are designated ports 1 – 16 and telnet terminal are designed ports 17 and above.
- It is recommended that measurement collection be retrieved prior to upgrade execution because, if the MCPM or Intergrated Measurements features are not enabled, the data collected will not be persistent across the upgrade. Inhibiting measurements does NOT stop collection that is already in progress. OAM-based measurements are inhibited on the next cycle. It is recommended that time should be given to allow the current cycle to complete. Those procedures that inhibit measurements manually contain steps to ensure that current collection is complete.
- It is recommended that the OAP terminals be turned down for SEAS-enabled systems and others with high OAP traffic. If OAP terminals are not inhibited, any database updates successfully entered during the period between the last database backup and Upgrade Phase 0 are lost if it becomes necessary to fall back to the source release using the spare E5-MASP.
- It is recommended that the Measurements Platform NOT be shut down and the Measurement Collection and Polling Module (MCPM) cards NOT be inhibited.
- It is recommended to issue the command in Procedure 8, Step 1 with the
threshold type assigned to SET (Card Set network conversion method.) In addition, it
is recommended that the card sets be created with the number of service card sets
assigned to 2 and the number of link card sets to 4. The following command is issued
in Procedure 8, Step
1:
ACT-UPGRADE:ACTION=CONVERTSTP:SRC=FIXEDBased on a system’s configuration and customer objectives, the SRVSETS and LIMSETS parameters of the CHG-UPGRADE-CONFIG comand may be adjusted. Refer to Appendix B.2for the procedure to configure the Card Set network conversion method. If the network conversion phase of the upgrade is pushing the execution of the upgrade outside the maintenance window the configuration can be altered to reduce the execution time. Please go to Appendix G to contact support to determine the recommended course of action.
- Although an IP telnet terminal may be configured, the terminal is not recommended for use in the upgrade process because it does not support echo and capture mode. Any application connected via a Telnet session through an IPSM card, should be configured for interruption during the upgrade. That application’s configuration procedure needs to be provided by the application’s manufacturer.
- The following commands obtain the current system status. It is recommended that the
following commands be run in order to obtain the current system status in the
following situations: 1) prior to and completion of executing the upgrade, 2) the
upgrade terminates prior to successful completion and 3) before re-starting the
upgrade. The commands should be issued in addition to the diagnosis of the any
terminating condition. This status is not complete and inclusive, additional
commands, which are deemed relevant, can be run at that
time.
REPT-STAT-SYS REPT-STAT-GPL:DISPLAY=ALL REPT-STAT-CARD REPT-STAT-SLK REPT-STAT-TRBL RTRV-TRBL:NUM=25:LOC=<1113|1115> RTRV-STP ACT-UPGRADE:ACTION=DBSTATUS