E EEDB Installation

This section defines the step-by-step actions performed to execute EEDB software installation on E5-APP-B-02.

Figure E-1 Initial EEDB Application Installation Path


Initial EEDB Application Installation Path

Upgrade Overview

Required Materials

  • Two (2) target-release USB media or a target-release ISO file.
  • A terminal and null modem cable to establish a serial connection.
  • Write down the system configuration information.

    Table E-1 EEDB System Configuration Information

    Description Information
    Node A IP (IPv4)  
    Node A NetMask (IPv4)  
    Node A Default Router IP (IPv4)  
    Node B IP (IPv4)  
    Node B NetMask (IPv4)  
    Node B Default Router IP (IPv4)  
    NTP1 IP (IPv4)  
    NTP2 IP (IPv4)  
    NTP3 IP (IPv4)  
    VIP  
    Time Zone  
  • Passwords for users on the local system:

    Table E-2 EEDB User Password Table

    EEDB USERS
    Login Node A password Node B password
    root
    eedbconfig
    admusr

Installation Phases

The following table illustrates the progression of the installation process by procedure with estimated times. The estimated times and the phases that must be completed may vary due to differences in typing ability and system configuration. The phases outlined in Upgrade Preparation Overview and Pre-Upgrade Overview are to be executed in the order they are listed.

Table E-3 Installation Phases for EEDB

Phase Elapsed Time (Minutes) Activity Procedure
This Step Cum.
Connectivity setup 15 15 Set up connectivity to the MPS Servers. Setting Up the Upgrade Environment for EEDB
Pre-upgrade check 5 20 Verify requirements for install are met. Verify the Pre-Upgrade Requirements
Configure the Network 5 25 Configure the Network using platcfg on Node A Configure Network Interface Using platcfg Utility
Configure the Network 5 30 Configure the Network using platcfg on Node B Configure Network Interface Using platcfg Utility
Create the bulkconfig file 5 35 Create the configuration file Create Configuration File on Node A
Create the bulkconfig file 5 40 Create the configuration file Create Configuration File on Node B
Pre-install health check 5 45 Run the syscheck utility to verify that all servers are operationally sound on Node A. Perform System Health Check
Pre-install health check 5 50 Run the syscheck utility to verify that all servers are operationally sound on Node B. Perform System Health Check
Configure Server Node A 5 55 Set hostname, designation and time. Pre-Install Configuration on Node A
Configure Server Node B 5 60 Set hostname, designation and time. Pre-Install Configuration on Node B
Install Servers 30 90 Install software on Node A and B Install Application on Node A, Install Application on Node B

Upgrade Preparation

Setting Up the Upgrade Environment for EEDB
This procedure sets up the upgrade environment. Windows are opened for both MPS servers.

Note:

Call My Oracle Support (MOS) for assistance if modem access is the method use for upgrade.
Should THIS PROCEDURE FAIL, CONTACT My Oracle Support (MOS) AND ASK FOR UPGRADE ASSISTANCE.
  1. Establish a connection to MPS A.
    If access to the MPS servers is not available through an IP network, connect to the E5-APP-B card via the serial port.

    For connecting the E5-APP-B A card, disconnect the console cable from the serial port on the E5-APP-B B card’s adapter. The cable should be disconnected at the point where it connects to the serial port labeled ‘S1’ on the E5-APP-B B card’s adapter and use it for serial access. Cable part numbers - 830-1220-xx.

  2. On the workstation, open one terminal window in preparation for establishing remote connections to the MPS servers.
    Create a terminal window.
  3. Create a terminal window for MPS A.
    Create a terminal window and give it a title of MPS A.
  4. MPS A: Enable capture file and verify the correspondent file is created.
    Enable the data capture and verify that the data capture file is created at the path specified.
  5. Log into MPS A.
    <hostname> console login:  admusr
    password:   <password>
  6. MPS A: Start screen Session.
    Execute the following command to start screen and establish a console session with MPS A.

    $ screen -L

  7. Establish a connection to MPS B.
    If access to the MPS servers is not available through an IP network, connect to the E5-APP-B card via the serial port.

    For connecting the E5-APP-B B card, disconnect the console cable from the serial port on the E5-APP-B A card’s adapter. The cable should be disconnected at the point where it connects to the serial port labeled ‘S1’ on the E5-APP-B A card’s adapter and use it for serial access. Cable part numbers - 830-1220-xx

  8. Create a terminal window for MPS B.
    Create a terminal window and give it a title of MPS B.
  9. MPS B: Enable capture file and verify a correspondent file is created.
    Enable the data capture and verify that the data capture file is created at the path specified.
  10. Log into MPS B.
    <hostname> console login:  admusr
    password:   <password>
    
  11. MPS B: Start screen Session.
    Execute the following command to start screen and establish a console session with MPS B.

    $ screen –L

    MPS A and B: Procedure Complete.

Verify the Pre-Upgrade Requirements
This procedure verifies that all pre-upgrade requirements have been met.

Note:

Call My Oracle Support for assistance if modem access is the method use for upgrade.
Should THIS PROCEDURE FAIL, CONTACT My Oracle Support AND ASK FOR UPGRADE ASSISTANCE.
  1. Verify all required materials are present.
    Verify that the materials listed in Upgrade Material List (Required Materials) are present.
  2. Verify the availability of passwords for MPS systems.
    Refer to Required Materials for the list of users.

    This procedure is complete.

Software Installation Procedures

Create Configuration File on Node A
This procedure creates the EEDB configuration file.

Note:

Call My Oracle Support (MOS) for assistance if modem access is the method use for upgrade.
SHOULD THIS PROCEDURE FAIL, CONTACT My Oracle Support AND ASK FOR UPGRADE ASSISTANCE.

Note:

Installation of the Operating System on an Oracle Application Server should be completed before starting installation procedure. Refer to IPM MPS Server with TPD 7.6.X for TPD installation.
  1. Log in as admusr user.
    If not already logged in, then login as admusr:
    [hostname] consolelogin:  admusr
    password:   password
    
  2. Switch super user to root.
    $ sudo su -
  3. Create the file in root directory named as bulkconfig.
    $ vim /root/bulkconfig

    Content of file should be as follow:

    host,<NodeA-hostname>,<Node A-IP>,bond0:1,<Node A- NetMask>,<Node A Default route>,1A
    host,<NodeB-hostname>,<Node B-IP>,bond0:1,<Node B- NetMask>,<Node B Default route>,1B
    vip,<Virtual IP>,bond0:2,<VIP Netmask>
    ntpserver1,<NTP Server IP>
    timezone,America/New_York
    

    For Example:

    host,Santos-A,10.75.141.64,bond0:1,255.255.255.0,10.75.141.1,1A
    host,Santos-B,10.75.141.65,bond0:1,255.255.255.0,10.75.141.1,1B
    vip,10.75.141.66,bond0:2,255.255.255.0
    ntpserver1,10.250.32.10
    timezone,America/New_York
    

    Note:

    Upto 3 NTP servers can be added in bulkconfig file. NTP servers should have names ntpserver1, ntpserver2 and ntpserver3 respectively.

    This procedure is complete.

Create Configuration File on Node B
This procedure creates the EEDB configuration file.

Note:

Call My Oracle Support for assistance if modem access is the method use for upgrade.

Should THIS PROCEDURE FAIL, CONTACT My Oracle Support AND ASK FOR UPGRADE ASSISTANCE.

Note:

Installation of the Operating System on an Oracle Application Server should be completed before starting installation procedure. Refer to IPM MPS Server with TPD 7.6.X for TPD installation.
  1. Log in as admusr user on Node B.
    If not already logged in, then login as admusr:
    [hostname] consolelogin:  admusr
    password:   password
    
  2. Switch super user to root.
    $ sudo su -
  3. Create the file in root directory named as bulkconfig.
    $ vim /root/bulkconfig

    Content of file should be as follow:

    host,<NodeA-hostname>,<Node A-IP>,bond0:1,<Node A- NetMask>,<Node A Default route>,1A
    host,<NodeB-hostname>,<Node B-IP>,bond0:1,<Node B- NetMask>,<Node B Default route>,1B
    vip,<Virtual IP>,bond0:2,<VIP Netmask>
    ntpserver1,<NTP Server IP>
    timezone,America/New_York
    

    For Example:

    host,Santos-A,10.75.141.64,bond0:1,255.255.255.0,10.75.141.1,1A
    host,Santos-B,10.75.141.65,bond0:1,255.255.255.0,10.75.141.1,1B
    vip,10.75.141.66,bond0:2,255.255.255.0
    ntpserver1,10.250.32.10
    timezone,America/New_York
    

    Note:

    Upto 3 NTP servers can be added in bulkconfig file NTP servers should have names ntpserver1, ntpserver2 and ntpserver3 respectively.

    This procedure is complete.

Pre-Install Configuration on Node A
This procedure provides instructions to perform pre-configuration for an initial install of the application.

IF THIS PROCEDURE FAILS, CONTACT MY ORACLE SUPPORT AND ASK FOR ASSISTANCE.

  1. Connect to the Server.
    If not already connected, connect to the E5-APP-B card via the serial port.

    For connecting the E5-APP-B B card, disconnect the console cable from the serial port on the E5-APP-B A card’s adapter. The cable should be disconnected at the point where it connects to the serial port labeled S1 on the E5-APP-B A cards’ adapter and use it for serial access. Cable part numbers - 830-1220-xx

  2. Log in as admusr user. If not already logged in, then login as admusr:
    [hostname] consolelogin:  admusr
    password:   password
    
  3. Start platcfg utility.
    $ sudo su - platcfg
  4. Navigate to the Server Configuration screen.
    Select Server Configuration and press [ENTER].
    Server Configuration
  5. Navigate to the Hostname screen.
    Select Hostname and press [ENTER].
    Hostname
  6. Select Edit to edit the hostname.
    Select Edit and press [ENTER].
    Edit
  7. Enter the hostname and press ok.
    Delete the default entry and enter the Hostname as mps-xxxx-a where xxxx is the last 4 digits of server serial number. Press OK when done.
    Edit Hostname

    While connected to the serial console, some console output might come when the user is using the serial console to configure the EEDB. Those serial output are harmless and can be ignored.

  8. Exit Back to the Server Configuration Menu.
    Select EXIT to exit back to the Server Configuration Menu. Verify that the hostname has been properly set.
    Hostname Configuration
  9. Navigate to the Designation/Function menu option.
    Select Designation/Function and press [ENTER].
    Designation
  10. Enter the designation.
    Enter the appriopriate designation in the Designation field (Note: the designation must be capitalized).

    Select OK and press [ENTER].


    Edit Designation
  11. Enter the Designation press Exit.

    Designation Information
  12. Select Set Clock Menu.

    Set Clock
  13. Select Edit from the options dialogue box. Using an NTP source, set the Date/Time to be correct for the Eastern Time zone (GMT -5) and press OK.

    Note:

    All systems default to Eastern time post IPM. It is important to set the time for the Eastern Time zone at this time

    Options

    Change Date and Time
  14. Verify that the Date and Time is correct then select and press Exit.

    Time Configuration

    Options
  15. Exit from platcfg menu.
    Select EXIT until the platcfg menu is closed and the command line is displayed.
  16. Reboot the Server.
    $ sudo reboot

    Procedure is complete.

Pre-Install Configuration on Node B
This procedure provides instructions to perform pre-configuration for an initial install of the application.

IF THIS PROCEDURE FAILS, CONTACT MY ORACLE SUPPORT AND ASK FOR ASSISTANCE.

  1. Connect to the Server.
    If not already connected, connect to the E5-APP-B card via the serial port.

    For connecting the E5-APP-B B card, disconnect the console cable from the serial port on the E5-APP-B A card’s adapter. The cable should be disconnected at the point where it connects to the serial port labeled S1 on the E5-APP-B A cards’ adapter and use it for serial access. Cable part numbers - 830-1220-xx

  2. Log in as admusr user. If not already logged in, then login as admusr:
    [hostname] consolelogin:  admusr
    password:   password
    
  3. Start platcfg utility.
    $ sudo su - platcfg
  4. Navigate to the Server Configuration screen.
    Select Server Configuration and press [ENTER].
    Main Menu
  5. Navigate to the Hostname screen.
    Select Hostname and press [ENTER].
    Server Configuration
  6. Select Edit to edit the hostname.
    Select Edit and press [ENTER].
    Options
  7. Enter the hostname and press ok.
    Delete the default entry and enter the Hostname as mps-xxxx-a where xxxx is the last 4 digits of server serial number. Press OK when done.
    Edit Hostname

    While connected to the serial console, some console output might come when the user is using the serial console to configure the EEDB. Those serial output are harmless and can be ignored.

  8. Exit Back to the Server Configuration Menu.
    Select EXIT to exit back to the Server Configuration Menu. Verify that the hostname has been properly set.
    Hostname Configuration
  9. Navigate to the Designation/Function menu option.
    Select Designation/Function and press [ENTER].
    Server Configuration Menu
  10. Enter the designation.
    Enter the appriopriate designation in the Designation field (Note: the designation must be capitalized).

    Select OK and press [ENTER].
    Edit Designation

  11. Enter the Designation press Exit.

    Designation Information
  12. Select Set Clock Menu.

    Set Clock
  13. Select Edit from the options dialogue box. Using an NTP source, set the Date/Time to be correct for the Eastern Time zone (GMT -5) and press OK.

    Note:

    All systems default to Eastern time post IPM. It is important to set the time for the Eastern Time zone at this time

    Options

    Date and Time
  14. Verify that the Date and Time is correct then select and press Exit.

    Time Configuration

    Options
  15. Exit from platcfg menu.
    Select EXIT until the platcfg menu is closed and the command line is displayed.
  16. Reboot the Server.
    $ sudo reboot

    Procedure is complete.

Install Application on Node A
This procedure installs the application on the server.

IF THIS PROCEDURE FAILS, CONTACT MY ORACLE SUPPORT AND ASK FOR ASSISTANCE.

  1. MPS A: Copy the EEDB ISO on 1A.
    Refer ISO Image download from Oracle Software Delivery Cloud to download the EEDB ISO and copy EEDB 46.8 ISO to /var/TKLC/upgrade directory.
  2. Create a terminal window log into MPS A.

    If not already connected, connect to the E5-APP-B card via the serial port.

    For connecting the E5-APP-B A card, disconnect the console cable from the serial port on the E5-APP-B B card’s adapter. The cable should be disconnected at the point where it connects to the serial port labeled S1 on the E5-APP-B B card’s adapter and use it for serial access. Cable part numbers - 830-1220-xx

  3. MPS A: Login prompt is displayed.
    <hostname> console login:

    Note:

    Hit enter if no login prompt is displayed.
  4. MPS A: log in as admusr user.
    <hostname> consolelogin:  admusr
    password:   password
    
  5. MPS A: Validate ISO file.
    Validate ISO file using Validate Upgrade Media.
  6. MPS A: Start platcfg utility.
    $ sudo su - platcfg
  7. MPS A: Navigate to the Upgrade menu.
    The platcfg Main Menu appears.

    On the Main Menu, select Maintenance and press [ENTER].


    Main Menu

    Select the Upgrade menu and press [ENTER].


    Maintenance Menu
  8. MPS A: Select Early Upgrade Checks.
    Select the Early Upgrade Checks menu to verify that the system is ready for upgrade.
    Early Upgrade Checks

    If the Early Upgrade Checks fail due to the ongoing syncing of raid mirrors, then wait until the resync is completed and run the Early Upgrade Checks again.

    Contact My Oracle Support following the instructions on the front page if the early upgrade checks fail due to any other reason.

  9. MPS A: Navigate to the Initiate Upgrade menu.
    Select the Initiate Upgrade menu and press [ENTER].
    Initiate Upgrade
  10. MPS A: Select the Upgrade Media.
    The screen displays a message that it is searching for upgrade media. When the upgrade media is found, an Upgrade Media selection menu appears similar-to the example below.

    Select the desired upgrade media and press [ENTER].


    Choose Upgrade Media Menu
  11. MPS A: Upgrade proceeds.
    The screen displays the output like following, indicating that the upgrade software is first running the upgrade checks, and then proceeding with the upgrade.
  12. MPS A: Upgrade proceeds.
    Many informational messages appear on the terminal screen as the upgrade proceeds. The messages are not shown here for clarity sake.

    When installation is complete, the server reboots.

  13. MPS A: Upgrade completed.
    After the final reboot, the screen displays the login prompt as in the example below.
    Authorized uses only. All activity may be monitored and reported.
    1542751724: Upstart Job alarmMgr: started
    #####################
    
    
    1542751724: Upstart Job tpdProvd: started
    #####################
    
    
    1542751724: Upstart Job syscheck: started
    #####################
    
    
    1542751725: Upstart Job ntdMgr: started
    #####################
    
  14. MPS A: log in as admusr user.
    [hostname] consolelogin:  admusr
    password:   password
    
  15. MPS A: Check the Upgrade log.
    Examine the upgrade logs in the directory /var/TKLC/log/upgrade and verify that no errors and warnings were reported.

    $ grep -i error /var/TKLC/log/upgrade/upgrade.log

    Check the output of the upgrade log, Contact My Oracle Support following the instructions on the front page or the instructions on the My Oracle Support (MOS), if the output contains any errors beside the following:

    1542696235::Bringing up interface bond0:  /etc/sysconfig/network-scripts/ifup-eth: line 141: echo: write error: Permission denied
    1542696235::error in ifcfg-bond0:1: didn't specify device or ipaddr
    1542696235::error in ifcfg-bond0:2: already seen ipaddr in ifcfg-bond0:1.
    

    $ grep -i warning /var/TKLC/log/upgrade/upgrade.log

    Examine the output of the above command to determine if any warnings were reported.

    Contact My Oracle Support following the instructions on the front page or the instructions on the My Oracle Support (MOS), if the output contains any warnings beside the following:

    1542695599::WARNING: /usr/TKLC/plat/etc/alarms/alarms.xml has been updated...reparsing xml...
    1542695670::warning:    erase unlink of /etc/ssm/hwmgmtd.conf failed: No such file or directory
    1542695672::kexec-tools                 #warning: /etc/kdump.conf created as /etc/kdump.conf.rpmnew
    1542695778::setup                       #################################################warning: /etc/shadow created as /etc/shadow.rpmnew
    1542695794::ca-certificates             ################warning: /etc/pki/tls/certs/ca-bundle.crt created as /etc/pki/tls/certs/ca-bundle.crt.rpmnew
    1542695843::WARNING: This capability is not defined in the default capabilities.
    1542695843::WARNING: Nor is it defined in the current hardware ID's capabilities.
    1542695843::WARNING:  CAPABILITY: service_hp-asrd_disabled
    1542695843::WARNING: HARDWARE ID: E5APPB
    1542695915::WARNING: This capability is not defined in the default capabilities.
    1542695916::WARNING: Nor is it defined in the current hardware ID's capabilities.
    1542695916::WARNING:  CAPABILITY: service__disabled
    1542695916::WARNING: HARDWARE ID: E5APPB
    1542696000::cloud-init                  warning: /etc/cloud/cloud.cfg created as /etc/cloud/cloud.cfg.rpmnew
    
  16. MPS A: Check that the upgrade completed successfully.
    $ grep "Upgrade returned success" /var/TKLC/log/upgrade/upgrade.log
  17. MPS A: Check that the upgrade completed successfully.
    Verify that the message Upgrade returned success! is displayed. If it is not, contact My Oracle Support following the instructions on the front page or the instructions on the My Oracle Support (MOS).

    1399367207:: Upgrade returned success!

    Install Procedure is complete.

Install Application on Node B
This procedure installs the application on the server.

IF THIS PROCEDURE FAILS, CONTACT MY ORACLE SUPPORTAND ASK FOR ASSISTANCE.

  1. MPS B: Install 1B.
    Refer ISO Image download from Oracle Software Delivery Cloud to download the EEDB ISO and copy EEDB 46.8 ISO to /var/TKLC/upgrade directory.
  2. Create a terminal window log into MPS B.

    If not already connected, connect to the E5-APP-B card via the serial port.

    For connecting the E5-APP-B B card, disconnect the console cable from the serial port on the E5-APP-B A card’s adapter. The cable should be disconnected at the point where it connects to the serial port labeled S1 on the E5-APP-B A card’s adapter and use it for serial access. Cable part numbers - 830-1220-xx

  3. MPS B: Login prompt is displayed.
    <hostname> console login:

    Note:

    Hit enter if no login prompt is displayed.
  4. MPS B: log in as admusr user.
    <hostname> consolelogin:  admusr
    password:   password
    
  5. MPS X: Validate ISO file.
    Validate ISO file using Validate Upgrade Media.
  6. MPS B: Start platcfg utility.
    $ sudo su - platcfg
  7. MPS B: Navigate to the Upgrade menu.
    The platcfg Main Menu appears.

    On the Main Menu, select Maintenance and press [ENTER].


    Main Menu

    Select the Upgrade menu and press [ENTER].


    Maintenance Menu
  8. MPS A: Select Early Upgrade Checks.
    Select the Early Upgrade Checks menu to verify that the system is ready for upgrade.
    Early Upgrade Checks

    If the Early Upgrade Checks fail due to the ongoing syncing of raid mirrors, then wait until the resync is completed and run the Early Upgrade Checks again.

    Contact My Oracle Support following the instructions on the front page or the instructions on the Appendix G, if the early upgrade checks fail due to any other reason.

  9. MPS A: Navigate to the Initiate Upgrade menu.
    Select the Initiate Upgrade menu and press [ENTER].
    Initiate Upgrade
  10. MPS B: Select the Upgrade Media.
    The screen displays a message that it is searching for upgrade media. When the upgrade media is found, an Upgrade Media selection menu appears similar-to the example below.

    Select the desired upgrade media and press [ENTER].


    Choose Upgrade Media Menu
  11. MPS B: Upgrade proceeds.
    The screen displays the following, indicating that the upgrade software is first validating the media, and then proceeding with the upgrade.
  12. MPS B: Upgrade proceeds.
    Many informational messages appear on the terminal screen as the upgrade proceeds. The messages are not shown here for clarity sake.

    When installation is complete, the server reboots.

  13. MPS B: Upgrade completed.
    After the final reboot, the screen displays the login prompt as in the example below.
    Authorized uses only. All activity may be monitored and reported.
    1542751724: Upstart Job alarmMgr: started
    #####################
    
    
    1542751724: Upstart Job tpdProvd: started
    #####################
    
    
    1542751724: Upstart Job syscheck: started
    #####################
    
    
    1542751725: Upstart Job ntdMgr: started
    #####################
    
  14. MPS B: log in as admusr user.
    [hostname] consolelogin:  admusr
    password:   password
    
  15. MPS B: Check the Upgrade log.
    Examine the upgrade logs in the directory /var/TKLC/log/upgrade and verify that no errors and warnings were reported.

    $ grep -i error /var/TKLC/log/upgrade/upgrade.log

    Check the output of the upgrade log, Contact My Oracle Support following the instructions on the front page or the instructions on the My Oracle Support (MOS), if the output contains any errors beside the following:

    1542696235::Bringing up interface bond0:  /etc/sysconfig/network-scripts/ifup-eth: line 141: echo: write error: Permission denied
    1542696235::error in ifcfg-bond0:1: didn't specify device or ipaddr
    1542696235::error in ifcfg-bond0:2: already seen ipaddr in ifcfg-bond0:1.
    

    $ grep -i warning /var/TKLC/log/upgrade/upgrade.log

    Examine the output of the above command to determine if any warnings were reported.

    Contact My Oracle Support following the instructions on the front page or the instructions on the My Oracle Support (MOS), if the output contains any warnings beside the following:

    1542695599::WARNING: /usr/TKLC/plat/etc/alarms/alarms.xml has been updated...reparsing xml...
    1542695670::warning:    erase unlink of /etc/ssm/hwmgmtd.conf failed: No such file or directory
    1542695672::kexec-tools                 #warning: /etc/kdump.conf created as /etc/kdump.conf.rpmnew
    1542695778::setup                       #################################################warning: /etc/shadow created as /etc/shadow.rpmnew
    1542695794::ca-certificates             ################warning: /etc/pki/tls/certs/ca-bundle.crt created as /etc/pki/tls/certs/ca-bundle.crt.rpmnew
    1542695843::WARNING: This capability is not defined in the default capabilities.
    1542695843::WARNING: Nor is it defined in the current hardware ID's capabilities.
    1542695843::WARNING:  CAPABILITY: service_hp-asrd_disabled
    1542695843::WARNING: HARDWARE ID: E5APPB
    1542695915::WARNING: This capability is not defined in the default capabilities.
    1542695916::WARNING: Nor is it defined in the current hardware ID's capabilities.
    1542695916::WARNING:  CAPABILITY: service__disabled
    1542695916::WARNING: HARDWARE ID: E5APPB
    1542696000::cloud-init                  warning: /etc/cloud/cloud.cfg created as /etc/cloud/cloud.cfg.rpmnew
    
  16. MPS B: Check that the upgrade completed successfully.
    $ grep "Upgrade returned success" /var/TKLC/log/upgrade/upgrade.log
  17. MPS B: Check that the upgrade completed successfully.
    Verify that the message Upgrade returned success! is displayed. If it is not, contact My Oracle Support following the instructions on the front page or the instructions on the My Oracle Support (MOS).

    1399367207:: Upgrade returned success!

    Install Procedure is complete.

Generic Procedure

ISO Image download from Oracle Software Delivery Cloud
This procedure provides instructions to download an ISO image from OSDC and copy to the required server.

IF THIS PROCEDURE FAILS, CONTACT MY ORACLE SUPPORT AND ASK FOR UPGRADE ASSISTANCE.

  1. MPS X: Log in to the server as the admusr user.
    [hostname] consolelogin: admusr
    password: <admusr_password>
  2. MPS X: Verify ISO image doesn’t already exist.
    Execute the following command to perform directory listing:
    $ ls –alrt /var/TKLC/upgrade

    The output should look like as follows (There is no ISO present in following example):

    [admusr@Osorna-B-PDBonly ~]$ ls -alrt /var/TKLC/upgrade/
    total 12
    drwxrwxr-x.  3 root admgrp 4096 Feb 19 21:43 .
    dr-xr-xr-x. 22 root root   4096 Jun 15  2018 ..
    

    If an ISO image exists, remove it by executing the following command:

    $ rm –f /var/TKLC/upgrade/<ISO image>
  3. Download the ISO image from OSDC (Oracle Software Delivery Cloud).
  4. Copy the ISO from source path to destination path.

    Note:

    Skip this step if same ISO is already present on destination folder.

    Copy the ISO image from source path to destination path using scp/ftp command.

    Execute the following command on destination server:

    $ sudo scp <source_username>@<source_server_IP>:/<source_path>/xyz.iso             
             /var/TKLC/upgrade

    Password: <enter source userpassword>

    OR,

    Execute the following command on source server:

    $ scp /<source_path>/<xyz.iso>
             admusr@<destination_server_IP>:/var/TKLC/upgrade

    Password: <Enter admusr password>

  5. MPS X: Verify ISO image copied on destination path.
    Execute the following command to perform directory listing:

    $ ls –alrt /var/TKLC/upgrade

    The output should look like:

    [admusr@hostname ~]$ ls -alrt /var/TKLC/upgrade
    total 684816
    drwxr-xr-x.  2 root sys         4096 Mar 20  2018 patch
    drwxrwxr-x.  3 root admgrp      4096 Jun 15 18:09 .
    -rw-r-----   1 root root   701235200 Nov 21 18:12 EEDB-46.7.0.0.0_75.24.0-x86_64.iso
    dr-xr-xr-x. 21 root root        4096 Nov 21 18:37 ..
    

    Repeat this procedure from step 1 if EEDB ISO file is not as expected.

  6. MPS X: Validate ISO file.
    Validate ISO file using Validate Upgrade Media.

    This procedure is complete.

Validate Upgrade Media
This procedure is used to execute a validation of the Upgrade Media (typically an ISO image) separately from executing an upgrade. The upgrade process automatically validates the upgrade media. However, sometime the user may wish to perform just a validation before proceeding with upgrade, thus the reason for this separate process.

Validation could be performed on MPS A or B, however, this procedure specifies MPS X for simplicity.

This procedure provides instructions to perform a validation of the upgrade media on the MPS X server. This procedure assumes that the E5-APP-B card IPM procedure has been executed and the user has an EEDB Upgrade ISO image available.

IF THIS PROCEDURE FAILS, CONTACT MY ORACLE SUPPORT AND ASK FOR UPGRADE ASSISTANCE.
  1. MPS X: If necessary, log in to the server as the user admusr. If not already logged in to the MPS server, then login as user admusr.
    <hostname> console login:  admusr
    password:   <password>
    
  2. MPS X: Execute the platcfg menu.
    $ sudo su - platcfg
  3. MPS X: Select the Maintenance submenu.
    The platcfg Main Menu appears.

    On the Main Menu, select Maintenance and press [ENTER].


    Main Menu
  4. MPS X: Select the Upgrade submenu and press [ENTER].

    Maintenance Menu
  5. MPS X: Select the Validate Media selection and press [ENTER].

    Validate Media
  6. MPS X: Output from the Validate Media selection.

    The screen will display a message that it is searching for upgrade media. Once the upgrade media is found, an Upgrade Media selection menu will be displayed similar to the example shown below.

    If the upgrade media is not found, follow to copy the ISO Image download from Oracle Software Delivery Cloud upgrade ISO.

    Select the upgrade media or ISO image. There should only be one selection available, as shown in the example below. If there is more than one selection available, contact My Oracle Support following the instructions on the front page or the instructions on the My Oracle Support (MOS).


    Choose Upgrade Media
  7. MPS X: View the Validation results.
    The results of the validation will be displayed, similar to the example below.

    Press the [ENTER] key to continue.


    Validation Results
  8. MPS X: Select the Exit option.
    Select the Exit option, and keep selecting the Exit option, until you reach the command line prompt or you return to another menu that you wish to use.

    Media Validation is complete. Return to the procedure that you came here from.

IPM MPS Server with TPD 7.6.X

Note:

Both the MPS-A and MPS-B servers can be IPM’ed at the same time.

This procedure will IPM the E5-APP-B Server.

IF THIS PROCEDURE FAILS, CONTACT MY ORACLE SUPPORT AND ASK FOR UPGRADE ASSISTANCE.

  1. MPS X: Insert TPD 7.6.x USB media into the USB port (E5-APP-B).

    Note:

    Refer Copy ISO image in USB to copy the ISO in USB.

    Reboot server.

    # reboot

  2. MPS X: Press del key to enter the BIOS, set System Time to GMT time, and System Date.

    Main
  3. MPS X: Select BootHard Disk Drives option.

    Boot Menu
  4. MPS X: Press Enter key and select USB as the 1st Drive.
    remo
    Boot Menu
  5. MPS X: Press Esc key and select Boot Device Priority.

    Boot Device Priority
  6. MPS X: Verify that the 1st Boot Device is set to USB.

    1st Boot Device
  7. MPS X: Press Esc key and select ExitSave Changes and Exit option.

    Save Changes and Exit
  8. MPS X: Select [OK] to save the configuration changes.
    The server will reboot and TPD boot prompt will appear.
    Configuration Changes
  9. MPS X: Start the IPM process by entering the TPDlvm command at the boot prompt.

    TPDlvm
  10. MPS X: After a few seconds, additional messages will begin scrolling by on the screen as the Linux kernel boots, and then the drive formatting and file system creation steps will begin.

    Formatting
  11. MPS X: Once the drive formatting and file system creation steps are complete, the screen at right will appear indicating that the package installation step is about to begin.

    Package Installation
  12. MPS X: After a few minutes, you will see a screen similar to that at right, showing the status of the package installation step. For each package, there will be a status bar at the top indicating how much of the package has been installed, with a cumulative status bar at the bottom indicating how many packages remain. In the middle, you will see text statistics indicating the total number of packages, the number of packages installed, the number remaining, and current and projected time estimates.

    Package Installation
  13. MPS X: Once all the packages have been successfully installed, the screen at right will appear letting you know the installation process is complete.
    On E5-APP-B server remove the installation media (USB) and press <ENTER> to reboot the system and continue with the next step.
    Complete
  14. MPS X: Press del key to enter the BIOS, set correct System Time in GMT and System Date.

    Main Menu
  15. MPS X: Select BootHard Disk Drives option

    Hard Disk Drives
  16. MPS X: Press Enter key and select HDD:P0 as the 1st Drive

    Hard Disk Drives
  17. MPS X: Press Esc key and select Boot Device Priority

    Boot Device Priority
  18. MPS X: Verify that the 1st Boot Device is set to HDD:P0.

    1st Boot Device
  19. MPS X: Press Esc key and select ExitSave Changes and Exit option.

    Save Changes and Exit
  20. MPS X: Select [OK] to save the configuration changes. The server will reboot. Remove USB media from USB drive.

    Configuration Changes
  21. MPS X: Log in to the server as the user admusr.
    console login:  admusr
    password:   <admusr_password>
    
  22. MPS X: Verify that the platform revision is same as the TPD DVD or ISO used.
    $ getPlatRev
     7.6.x.0.0-y.z.0
    
  23. MPS X: Verify the system date.
    $ date -u Wed Mar
            21 11:04:54 UTC 2018

    Verify that the output time matches the time set in step 14. If mismatch is found, then Refer to Appendix G for instructions on accessing My Oracle Support.

    Return to the procedure that you came here from.

Perform System Health Check
This procedure performs a system health check on any MPS server.

IF THIS PROCEDURE FAILS, CONTACT MY ORACLE SUPPORT AND ASK FOR UPGRADE ASSISTANCE.

  1. MPS X: If necessary, log in to the server as the user admusr. If not already logged in to the MPS server, then login as user admusr.
    <hostname> console login:  admusr
    password:   <password>
    
  2. MPS X: Execute the platcfg menu.
    $ sudo su - platcfg
  3. MPS X: Select the Diagnostics submenu.
    The platcfg Main Menu appears.

    On the Main Menu, select Diagnostics and press [ENTER].


    Main Menu
  4. Select the Online Diagnostics submenu. Select the Online Diagnostics submenu and press [ENTER].

    Online Diagnostics
  5. Select the Non Verbose option and press [ENTER].

    Online Diagnostics Menu
  6. Examine the output of the Online Diagnostics

    Output

    Exit from the above menu.

    If the System Check was successful, return to the procedure that you came here from.

    If the Server Disk Space Shortage Error was there in the output, proceed to step 7 to clean up the / directory.

    If any other failures were detected by System Check, contact My Oracle Support following the instructions on the front page or the instructions on My Oracle Support (MOS).

  7. Server clean-up to create space using the following command:
    $ df -h /var/TKLC

    The output may look like:

    [admusr@hostname ~]$ df -h /var/TKLC
    Filesystem            Size  Used Avail Use% Mounted on
    /dev/mapper/vgroot-plat_var_tklc
                          3.9G  2.2G  1.5G  60% /var/TKLC
    

    Verify that there is at least 600M in the Avail column. If not, clean up files until there is space available.

    WARNING:

    Make sure you know what files you can remove safely before cleaning up. It is recommended that you only clean up files in the /var/TKLC/upgrade directory as this is a platform owned directory that should only contain ISO images. This directory should not be expected to contain images for any length of time as they can get purged.

    Also, execute the following command to check space in /lib/module directory.

    $ df -h /lib/modules
    [admusr@hostname ~]$ df -h /lib/modules
    Filesystem            Size  Used Avail Use% Mounted on
    /dev/mapper/vgroot-plat_root
                          976M  397M  529M  43% /
    

    Verify that the Use% column does not exceed the value 80%.

    Media Validation is complete. Return to the procedure that you came here from.

Configure Network Interface Using platcfg Utility
This procedure configures the network interfaces and makes the E5APPB servers accessible to the network.
IF THIS PROCEDURE FAILS, CONTACT MY ORACLE SUPPORT AND ASK FOR UPGRADE ASSISTANCE.
  1. MPS X: If necessary, log in to the server as the user admusr.
    If not already logged in to the MPS server, then login as user admusr.
    <hostname> console login:  admusr
    password:   <password>
  2. MPS X: Execute the platcfg menu.
    $ sudo su - platcfg
  3. MPS X: configure Network Interfaces

    Main Menu

    Network Configuration Menu

    Network Interfaces Menu

    Edit Menu

    Options
  4. Select Interface options.

    Interface Options

    Configure Options

    IP Address

    IP Version Menu

    IP Address Action

    Diagnostics Menu
  5. Input the IP Address and Netmask.

    Select Exit until you reach the network configuration menu.


    IPv4 Interface

    Message
  6. Configure Routing.

    Select Exit until you exit from the platcfg utility.
    Network Configuration Menu

    IP Version Menu

    IPv4 Static Routes

    Add Route
    Add Default Route
    Default Route

    Message

    This procedure is complete.

Copy ISO image in USB
This procedure provides instructions to copy an ISO to USB.

If this procedure fails, contact My Oracle Support and ask for upgrade assistance.

  1. MPS X: Log in to the server as the admusr user.
    [hostname] consolelogin: admusr 
    password: <admusr_password>
  2. MPS X: Verify ISO image present at directory.
  3. Execute the following command to perform directory listing:
    $ cd /var/TKLC/upgrade
    $ ls -alrt

    The output should look like as follows (There is no ISO present in following example):

    [admusr@waffle-a upgrade]$ ls -arlt
    total 695312
    drwxr-xr-x.  2 root sys         4096 Mar 20  2018 patch
    dr-xr-xr-x. 21 root root        4096 Nov 20 02:57 ..
    -r--r-----   1 root root   711983104 Dec  5 12:25 TPD.install-7.6.0.0.0_88.54.0-OracleLinux6.9-x86_64.iso
    drwxrwxr-x.  3 root admgrp      4096 Dec  5 12:26 
    
  4. MPS X: Copy ISO to the USB.
    $ sudo dd if=/var/TKLC/upgrade/TPD.install-7.6.0.0.0_88.54.0-OracleLinux6.9-x86_64.iso of=/dev/sdc
    1390592+0 records in
    1390592+0 records out
    711983104 bytes (712 MB) copied, 111.797 s, 6.4 MB/s
    

    This procedure is complete.