3 Upgrade Overview
This section lists the required materials and information needed to execute an upgrade. It also provides a brief timing overview of the activities needed to upgrade the source release software that is installed and running on an SDS server to the target release software. The approximate time required is outlined in sections Upgrade Preparation Overview through Recovery Procedures Overview. These tables are used to plan and estimate the time necessary to complete the upgrade.
Timing values are estimates only. They estimate the completion time of a step or group of steps for an experienced user. These tables are not to be used to execute procedures. Detailed steps for each procedure are provided in Upgrade Preparation.
3.1 Upgrade Requirements
The following levels of access, materials and information are needed to execute an upgrade:
- Target-release ISO image file.
Example: SDS-8.6.0.0.0_95.14.0.iso
- VPN access to the customer’s network.
- GUI access to the SDS network OAM&P VIP with administrator’s privileges.
- SSH/SFTP access to the SDS network OAM&P XMI VIP as the
admusruser.Note:
All logins into the SDS active and DR site servers are made using the external management (XMI) VIP unless otherwise stated. - User logins, passwords, IP addresses and other administration information. See section Logins, Passwords, and Site Information.
- Direct access to server IMI IP addresses from the user’s local workstation is preferable in the case of a back out.
Note:
If direct access to the IMI IP addresses is not available, then access to target server can be made using a tandem connection through the active primary SDS (that is, an SSH connection is made to the active primary SDS XMI first, then from the active primary SDS, an 2nd SSH connection can be made to the target server’s IMI IP address).
3.1.1 ISO Image File
Obtain a copy of the target release ISO image file. This file is necessary to perform the upgrade. The SDS ISO image file name is in the following format:
For example: SDS-8.6.0.0.0_95.14.0.iso
Note:
Actual number values vary between releases.Before executing this upgrade procedure, it is assumed the SDS ISO image file has already been delivered to the customer’s system. The delivery of the ISO image requires the file be placed on the disk of a workstation with GUI access to the SDS XMI VIP. If the user performing the upgrade is at a remote location, it is assumed the ISO file is has already been transferred to the active primary SDS server before starting the upgrade procedure.
3.1.2 Logins, Passwords, and Site Information
Obtain all the information requested in the following table. This ensures the necessary administration information is available before an upgrade. Consider the confidential nature of the information recorded in this table. While all of the information in the table is required to complete the upgrade, there may be security policies in place that require secure disposal once the upgrade has been completed.
Table 3-1 Logins, Passwords, and Site Information
| NE Type | NE Name |
|---|---|
| Primary SDS site | |
| DR SDS site | |
| SOAM 1 site | |
| SOAM 2 site | |
| SOAM 3 site | |
| SOAM 4 site |
Table 3-2 Software
| Software | Value |
|---|---|
| Source release level | |
| Target release level | |
| Target release ISO filename |
Table 3-3 Access Information
| Access Information | Value |
|---|---|
| Primary site XMI VIP (GUI) | |
| DR site XMI VIP | |
| SDS GUI admin user name and password | |
| SDS root user password | |
| SDS admusr user password | |
| SDS platcfg user password | |
| Blade’s iLO admin username and password | |
| PMAC GUI admin username and password* | |
| PMAC user root password* | |
| PMAC user admusr password* | |
| PMAC user PMACftpusr password* | |
| On board administrator GUI admin user name and password |
* Not applicable for cloud deployments
3.2 Upgrade Maintenance Windows
Note:
It is recommended that SOAM NE sites containing mated Database Processors (DPs) be upgraded in separate maintenance windows, if possible.Upgrade Maintenance Windows
Maintenance Window 1:
The following information has to be recorded in this maintenance window:
- Record the date of the maintenance window.
- Record the names of the primary SDS NE site, DR SDS NE site, and server’s hostnames to be upgraded during Maintenance Window.
- Verify and record the following information after each server upgrade is completed:
- Primary SDS NE site name
- Primary SDS active server
- Primary SDS standby server
- Primary SDS query server
- DR SDS NE site name
- DR SDS active server
- DR SDS standby server
- DR SDS query server
- Primary SDS NE site name
Upgrade Maintenance Windows
Maintenance Window 2:
The following information has to be recorded in this maintenance window:
- Record the name of SOAM NE site and its server’s host names to be upgraded during the maintenance window .
- Verify and record the following information after each server upgrade is completed:
- SOAM NE site name
- Active SOAM Server
- Standby SOAM Server
- DP Server Names
- DP 1 Server
- DP 2 Server
- DP 3 Server
- DP 4 Server
- DP 5 Server
- DP 6 Server
- DP 7 Server
- DP 8 Server
- DP 9 Server
- DP 10 Server
- SOAM NE site name
Keep track of maintenance windows for each SOAM NE site.
3.3 Upgrade Preparation Overview
The pre-upgrade procedures shown in the following table should be performed before the upgrade maintenance window and may be performed outside a maintenance window if desired.
Note:
If the customer deployment has both the FABR and PCA features enabled, then upgrade the DSR nodes first before upgrading the SDS nodes.Note:
In Upgrade DR SDS NOAM procedure, Ext ID/MTC-HSS features are introduced in SDS. Provisioning these features is not allowed until all the servers are upgraded and the upgrade is accepted.Upgrade Preparation Procedures
Table 3-4 Upgrade Preparation Procedures
| Procedure Title | Elapsed Time (Hrs:Min) | |
|---|---|---|
| This Step | Cumulative | |
| Required Materials Check | 00:15 | 00:15 |
| ISO Administration | * | * |
| Full Database Backup (PROV and COMCOL Env for All Servers | 01:00 | 01:15 |
Note:
ISO transfers to the target systems cannot be estimated since times vary significantly depending on the number of systems and the speed of the network. The ISO transfers to the target systems should be performed before the scheduled maintenance window. The user should schedule the required maintenance windows accordingly.3.4 Primary SDS Site or DR SDS Site Upgrade Execution Overview
The procedures shown in the following table are performed inside a maintenance window. The order of the upgrade for the primary NOAM NE and DR NOAM NE needs to be followed as shown in following table.
Note:
During the upgrade of servers, there are steps to check the replication status before going to the next server back out. Follow those steps to execute; otherwise, data loss is possible.Note:
During upgrade some alarms/events may be raised that can be ignored. Alarms are mentioned in Access the OAM GUI Using the VIP (NOAM/SOAM).Table 3-5 Primary SDS or DR SDS Upgrade Procedures Strategy
| Procedure Title | Elapsed Time (Hrs:Min) | |
|---|---|---|
| This Step | Cumulative | |
| Upgrade the Primary SDS NOAM | 01:00 | 02:15 |
| Upgrade the Primary SDS NOAM | 01:00 | 03:15 |
3.5 SOAM Upgrade Execution Overview
The procedures shown in the following table should be performed inside a separate maintenance window.
Table 3-6 SOAM Upgrade Procedures
| Procedure Title | Elapsed Time (Hrs:Min) | |
|---|---|---|
| This Step | Cumulative | |
| Upgrade SOAM | 01:30 | 01:30 |
3.6 Post Upgrade Execution Overview
These procedures are performed only after all sites on network have been upgraded.
Table 3-7 Post Upgrade Procedures
| Procedure Title | Elapsed Time (Hrs:Min) | |
|---|---|---|
| This Step | Cumulative | |
| Accept the Upgrade | * | * |
3.7 Recovery Procedures Overview
These procedures are customized to the specific situation encountered and therefore do not have well-established time frames. The order of the back out for the primary NOAM NE and DR NOAM NE needs to be followed as shown in the following table.
Note:
During back out of servers, there are steps to check the replication status before going to the next server back out. Follow those steps to execute; otherwise, data loss is possible.Note:
During the back out some alarms/events may be raised that can be ignored. Alarms are mentioned in step 4 of Health Check Procedures.Table 3-8 Backout Procedures
| Procedure Title | Elapsed Time (Hrs:Min) | |
|---|---|---|
| This Step | Cumulative | |
| Back Out the SOAM | * | * |
| Back Out the DR SDS NOAM | * | * |
| Back Out the Primary SDS NOAM | * | * |