4 Upgrade Preparation
- Perform hardware inventory to identify any hardware not supported by the target release baseline.
- Bring all non-supported hardware up to baseline (to be coordinated with My Oracle Support personnel).
- Perform pre-upgrade system health checks to establish that the system is fit to upgrade.
- Download target release software if necessary (E5-MASP) or capability available.
- Configure network conversion to use Card-Set method.
- Enter upgrade Software Access Key (SAK).
Hardware Upgrade Preparation
Before the upgrade execution, the customer site should have three source-release fixed drives (E5-TDMs \ Sata fixed drives) and at least one source-release removable media (two if using SSD). If MSD, a target-release upgrade media drive (USB drives for E5-MASP systems) must be created as outlined in appendix B1 before the upgrade. Before the target release installation, the spare equipment inventory should be as shown in Table 11 and Table 12.
Table 4-1 Equipment Inventory Before Upgrade If Media Software Delivery (MSD)
| Equipment | In-service | Spare | Upgrade | Totals: |
|---|---|---|---|---|
| Source-release fixed drives | 2 | 1 | 0 | 3 |
| Source-release removable media | 1 | 0 | 0 | 1 |
| Target-release fixed drives | 0 | 0 | 0 | 0 |
| Target-release upgrade media | 0 | 0 | 1 | 1 |
Table 4-2 Equipment Inventory Before Upgrade If Server Software Delivery (SSD)
| Equipment | In-service | Spare | Upgrade | Totals: |
|---|---|---|---|---|
| Source-release fixed drives | 2 | 1 | 0 | 3 |
| Source-release removable media | 2 | 0 | 0 | 2 |
| Target-release fixed drives | 0 | 0 | 0 | 0 |
| Target-release upgrade media | 0 | 0 | 0 | 0 |
During the procedure, both the active and standby in-service source-release E5-TDMs are converted to the target release and the spare is reserved in case a fallback to the source release is required. Upon completion of the procedure, the spare equipment should be as shown in the tables below.
Note:
The spare E5-TDM and source-release RMDs are upgraded to the target release in the second session. This allows a soak period for the target release and the possibility to fallback to the source release.Table 4-3 Spare Equipment After Upgrade If Media Software Delivery (MSD)
| Equipment | In-service | Spare | Upgrade | Totals: |
|---|---|---|---|---|
| Source-release fixed drives | 0 | 0 | 1 | 1 |
| Source-release removable media | 0 | 0 | 1 | 1 |
| Target-release fixed drives | 2 | 0 | 0 | 2 |
| Target-release upgrade media | 1 | 0 | 0 | 1 |
Table 4-4 Spare Equipment After Upgrade If Server Software Delivery (SSD)
| Equipment | In-service | Spare | Upgrade | Totals: |
|---|---|---|---|---|
| Source-release fixed drives | 0 | 0 | 1 | 1 |
| Source-release removable media | 0 | 0 | 1 | 1 |
| Target-release fixed drives | 2 | 0 | 0 | 2 |
| Target-release upgrade media | 1 | 0 | 0 | 1 |
Software Upgrade Preparation
In releases 45.x and 46.0, it is necessary for the customer to obtain a Software access Key (SAK) from Oracle to perform the upgrade; the SAK should be entered during System Health Check #2 (see Appendix C). The SAK is used in the validation of the target release software. In release 46.1 and higher, it is not neccessay for the customer to obtain a SAK. Also, the target release software needs to be loaded onto the inactive partition of the E5-TDMs (see Appendix B). The release can either be downloaded from the E5-MASP upgrade media (USB drive) or via an FTP server. In order to utilize this software download capability via an FTP server, the EAGLE must have an IPSM Card installed in the system. See General Description section for general steps and timeline associated with the upgrade process.