Configuring Oracle MiniCluster for SAP

Version 2

    by Hans-Juergen Denecke, Kevin Klapak, and Pierre Reynes

     

    This article is Part 1 of a multipart series that describes steps for setting up a highly available configuration to run SAP applications on Oracle MiniCluster. It focuses on procedures to prepare the infrastructure on Oracle MiniCluster prior to the installation of the SAP software components.

     

    Table of Contents

    OOS_Logo_small125.png
    Oracle Optimized Solutions provide tested and proven best practices for how to run software products on Oracle systems. Learn more.

     

    Introduction

     

    This multipart series of articles provides best practices and recommendations for setting up highly available SAP applications on Oracle MiniCluster. To compile and test the step-by-step procedures and recommendations provided in these articles, a team of Oracle engineers and SAP experts constructed a sample deployment using an Oracle MiniCluster S7-2 system. This article, Part 1, outlines the steps necessary to set up the MiniCluster, while Part 2 describes how to install and configure SAP ERP 6.0 EHP8 on two Oracle Database 12c nodes in a clustered environment. Figure 1 depicts the resulting solution.

     

    Configuring Oracle MiniCluster for SAP - Figure 1.png

    Figure 1. A sample SAP ERP installation on Oracle MiniCluster with Oracle Real Application Clusters (Oracle RAC).

     

    About Oracle MiniCluster

     

    For organizations that use SAP solutions to run their business, the infrastructure that supports SAP applications must offer outstanding agility, data protection mechanisms, and excellent reliability. To this end, Oracle MiniCluster is ideal for SAP deployments, especially for SAP applications that process security-sensitive data such as applications managing patient medical records, processing financial transactions, performing mission-critical enterprise resource planning, or handling secure communications and other security-related services.

     

    Oracle MiniCluster S7-2 is a preintegrated system that includes compute, storage, virtualization, operating system, and management components. Its simplicity, out-of-the-box performance, proven reliability, and small form factor make it an excellent choice for deployments in remote offices and small business locations or for agile software development (DevOps) environments.

     

    Tools provided with Oracle MiniCluster automate the deployment of Oracle Database and Oracle RAC software components, setting up virtual machines (VMs), making it easier to manage security and compliance, and deploying system patches. Numerous security controls are built in, which helps to simplify secure configurations to meet DISA-STIG, PCI-DSS, and other security benchmarks.

     

    This article summarizes the steps necessary to set up Oracle MiniCluster S7-2 and how to use its configuration tools to prepare the system prior to installing SAP components. For more detailed setup and configuration instructions, refer to the Oracle MiniCluster documentation, specifically the Oracle MiniCluster S7-2 Getting Started Guide and the Oracle MiniCluster S7-2 Installation Guide.

     

    Install the Hardware

     

    Unpack the two nodes and the storage array and connect them based on the instructions provided. In the sample deployment, Oracle MiniCluster includes a single storage array, which is connected to the two compute nodes as shown in Figure 2.

     

    f2.png

    Figure 2: Oracle MiniCluster compute and storage connection topology.

     

    Collect Network Information

     

    Before configuring Oracle MiniCluster using subsequent procedures in this article, gather system-specific networking information. The tables below show networking information used in the sample deployment.

     

    Table 1: Management Network Settings

            

    ParameterValue
    Management IP Node 1 Address10.133.82.96
    Management IP Node 2 Address10.133.82.97
    Default Gateway Address10.133.80.1
    Subnet CIDR Prefix/22
    DNS Server 1 Address10.209.76.197
    DNS Server 2 Address10.209.76.198
    DNS Server 3 Address192.135.82.132
    NTP Server 1 Address10.132.0.121
    NTP Server 2 Address10.132.0.122

     

    Table 2: Client Network IP Protocol

            

    ParameterValue
    Pool Starting IP Address10.133.82.98
    Pool Size27
    Gateway Address10.133.80.1
    Subnet CIDR Prefix/22
    DNS Server 1 Address10.209.76.197
    DNS Server 2 Address10.209.76.198
    DNS Server 3 Address192.135.82.132
    NTP Server 1 Address10.132.0.121
    NTP Server 2 Address10.132.0.122

     

    The host names in Table 3 should be configured and resolved by the DNS servers listed in Table 1 and Table 2.

     

    Table 3: Host Names and IP Addresses

                  

    Host NameIP Address
    oosmc1-n1-ilom10.133.82.96
    oosmc1-n2-ilom10.133.82.97
    oosmc1-n110.133.82.98
    oosmc1-n210.133.82.99
    oosmc1ss0110.133.82.100
    oosmc1ss0210.133.82.101
    oosmc1ss01-vip10.133.82.102
    oosmc1ss02-vip10.133.82.103
    oosmc1ss-nfsvip10.133.82.104
    oosmc1ss-scan10.133.82.105
    oosmc1ss-scan10.133.82.106
    oosmc1ss-scan10.133.82.107

     

    Perform Initial Configuration Steps

     

    These software components are used in subsequent setup procedures for Oracle MiniCluster:

     

    • Oracle MiniCluster Initial Configuration Tool. This tool generates initial configuration files based on collected parameters.
    • Oracle MiniCluster Component Bundle. This bundle, which is contained within a patch set, includes updated software components (Oracle Database and Oracle Grid Infrastructure binaries, software for creating Oracle Solaris 10 and Oracle Solaris 11 VMs, and disk calibration software). It is used during the initial Oracle MiniCluster installation or whenever there are updates needed prior to configuring VMs.
    • Oracle MiniCluster Core Software. This software supplies required Oracle Solaris repository files and the Oracle MiniCluster Configuration Utility (this tool is also called the MiniCluster Management Utility or MCMU). Download this software only if Oracle MiniCluster needs to be upgraded.

     

    Step 1. Locate the software to download.

     

    Sign in to My Oracle Support (support.oracle.com) and click the Patches & Updates tab on top of the screen. Refine your search as follows:

     

    • In the Patch Search section, click Product or Family (Advanced).
    • In the Product field, enter MiniCluster and select MiniCluster S7-2 Hardware.
    • In the Release field, select the latest release (in this case, Oracle MiniCluster S7-2 1.x), and click the Search button (Figure 3).
    • In the search results, click the Sort Descending down arrow in the Updated column header to sort the patches starting with the latest version.

     

    f3.png

    Figure 3: Search for Oracle MiniCluster patches and updates on My Oracle Support.

     

    Step 2. Download the Oracle MiniCluster Initial Configuration Tool.

     

    From the list of software choices (Figure 4), select the latest release of the Oracle MiniCluster Initial Configuration Tool. Click the filename to download the tool (Figure 5).

     

    f4.png

    Figure 4: Select the Oracle MiniCluster Initial Configuration Tool.

     

    f5.png

    Figure 5: Download the Oracle MiniCluster Initial Configuration Tool.

     

    Step 3. Download the Oracle MiniCluster Component Bundle and other required software, if needed.

     

    Next, select MiniCluster Component Bundle from the list of software (Figure 6), and download the bundle. If Oracle MiniCluster also needs to be upgraded, select MiniCluster Core Software to download the archive and then follow the upgrade instructions.

     

    f6.png

    Figure 6: Download the Oracle MiniCluster Component Bundle.

     

    Step 4. Unpack the Oracle MiniCluster Initial Configuration Tool.

     

    Unzip and unpack the Java archive file for the Oracle MiniCluster Initial Configuration Tool (Listing 1). Follow the instructions in the README.txt document.

     

    user$ java -jar /Users/user/Downloads/MiniCluster/1.1.25.4/p25801095_100_SOLARIS64/UserInput/UserInput.jar

    Listing 1: Unpacking the Java archive file for the Oracle MiniCluster Initial Configuration Tool.

     

    Step 5. Run the Oracle MiniCluster Initial Configuration Tool to configure parameter settings.

     

    Start the tool. When it opens, configure the General and Management Network sections in the main window (Figure 7).

     

    f7.png

    Figure 7: Specify initial configuration parameters for Oracle MiniCluster.

     

    Click the Client Network tab and configure the client network settings (Figure 8).

     

    f8.png

    Figure 8: Specify client network settings.

     

    Click Configure IP Allocation and enter the IP address ranges to be used by Oracle MiniCluster (Figure 9).

     

    f9.png

    Figure 9: Configure the allocated IP address ranges.

     

    Click the Review button and review the configuration summary.

     

    f10.png

    Figure 10: Review the configuration settings.

     

    Click the Check IP button. This step allows you to verify that host names match the names resolved by the DNS servers (Figure 11).

     

    f11.png

    Figure 11: Verify that Oracle MiniCluster host names match DNS host names.

     

    If the configuration is correct, click Save to generate the Oracle MiniCluster configuration files (Figure 12). Click Finish.

     

    f12.png

    Figure 12: The tool creates required configuration files.

     

    Step 6. Prepare to install Oracle MiniCluster.

     

    Connect with SSH to the Oracle Lights Out Manager (Oracle ILOM) service processor on node 1.

     

    Joebar:UserInput user$ ssh root@10.133.82.96
    The authenticity of host '10.133.82.96 (10.133.82.96)' can't be established.
    RSA key fingerprint is SHA256:AZT/TdJNNfzBv4emtEXUS3DRK6Jl9nZbWr5394jwPWI.
    Are you sure you want to continue connecting (yes/no)? yes
    Warning: Permanently added '10.133.82.96' (RSA) to the list of known hosts.
    Password: 
     
    Oracle(R) Integrated Lights Out Manager
     
    Version 3.2.6.3.b r110516
     
    Copyright (c) 2016, Oracle and/or its affiliates. All rights reserved.
     
    Warning: HTTPS certificate is set to factory default.
     
    Hostname: oosmc1-n1-ilom
     
    -> 

    Listing 2: Connect to the Oracle ILOM service processor on node 1.

     

    Open a console on the main system from the Oracle ILOM service processor.

     

    -> start sp/console
    Are you sure you want to start /SP/console (y/n)? y
     
    Serial console started.  To stop, type #.
     
    oosmc1-n1 console login: mcinstall
    Password: 
    Last login: Tue Oct 25 17:13:07 2016 on console
    Oracle Corporation      SunOS 5.11      11.3    August 2016
    mcinstall@oosmc1-n1:/var/home/mcinstall % 

    Listing 3: Start a console.

     

    Launch the mcinstall script on node 1 using the --init parameter. This captures initial configuration information for Oracle MiniCluster into two files that are later used in the deployment process.

     

    mcinstall@oosmc1-n1:/var/home/mcinstall % installmc --init  
    [INFO    ] Log file path : /var/opt/oracle.minicluster/setup/logs/installmc_102816_140555.log
    [INFO    ]  Configuring Firstnet..
    Enter Temporary IP addresses : 10.133.82.98
    Enter Netmask in CIDR form (valid range: 8-28) : 22
    Enter Default Gateway Address : 10.133.80.1
    VLAN ID is optional. Do you want to input this value?
    Enter Y/N (N): 
    Type of Cable Used to Connect Network Ports with the 10 GbE Switch: Copper/Fiber : Copper
    ---------- Input Summary ----------
    PUBLIC_IP = 10.133.82.98
    GATEWAY = 10.133.80.1
    NETMASK_CIDR = 22
    CAN_CABLE_TYPE = COPPER
    Do you want to change the inputs?
    Enter Y/N (N): 
    -------------------------------------------------------------------------------
        Initialization of Temporary IP Complete.
        Please copy over omcips.txt,userinputs.txt to /var/opt/oracle.minicluster/store 
    if you have generated them using the MiniCluster Initial Configuration tool.
        Then, run installmc --deploy to continue with Firstnet setup
        
    ----------------------------------------------------------------------------
        
    mcinstall@oosmc1-n1:/var/home/mcinstall % 

    Listing 4: Run the mcinstall script on node 1.

     

    Copy the two generated configuration files to /var/opt/oracle.minicluster/store as instructed in Listing 4, and then launch installmc using the --deploy parameter.

     

    mcinstall@oosmc1-n1:/var/home/mcinstall % installmc --deploy
    [INFO    ] Log file path : /var/opt/oracle.minicluster/setup/logs/installmc_102816_141732.log
    [INFO    ]  Configuring Firstnet..
     
     
     
     
             +---------------------------------------------------+
             | Oracle MiniCluster v1.0 :: Initial System Install |
             +---------------------------------------------------+
     
     
     
     
    Oct 28 14:17:32 mccn su: 'su root' succeeded for mcinstall on /dev/pts/1
    Ready to setup MiniCluster? (Y/N)(Y): 
     
     
    Initial system install in progress.
    Please do not interrupt. Wait for further on-screen instructions.
     
     
    Start Time: 10-28-2016 14:18:51
     
     
    Oct 28 14:18:51 mccn su: 'su root' succeeded for mcinstall on /dev/pts/2
    [INFO    ] Log file path : oosmc1-n1:/var/opt/oracle.minicluster/setup/logs/mcmu_102816_141851.log
    [INFO    ] No MCMUACTION table found in the table . ARGS list not updated this time
    [INFO    ] ---------- Starting Oracle MiniCluster Management Utility
    [INFO    ] STEP 1: Check Package Version and Gather User Input STARTED
    [INFO    ] Invoked by OS user: mcinstall
    [INFO    ] Find log at: oosmc1-n1:/var/opt/oracle.minicluster/setup/logs/omc_checkpkg_102816_141854.log
    [INFO    ] ---------- Starting Checking System Package Version
    [INFO    ] Checking System Package Version started.
    [INFO    ] Checking System Package Version succeeded.
    [INFO    ] Checking System Package Version Completed
    File /var/opt/oracle.minicluster/store/userinputs.txt already exists.
    ---------- Input Summary ----------
    MACHINE_TYPE = S7-2
    OMC_UPREFIX = oosmc1
    FIRST_PUBLIC_IP = 10.133.82.98
    IPCOUNT = 27
    GATEWAY = 10.133.80.1
    NETMASK_CIDR = 22
    DOMAIN_NAME = us.oracle.com
    DNS_SERVER_LIST = 10.209.76.197,10.209.76.198,192.135.82.132
    NTP_SERVER_LIST = 10.132.0.121,10.132.0.122
    CAN_CABLE_TYPE = Copper
    FIRST_ILOM_IP = 10.133.82.96
    SECOND_ILOM_IP = 10.133.82.97
    ILOM_GATEWAY = 10.133.80.1
    ILOM_NETMASK_CIDR = 22
    ILOM_DNS_SERVER_LIST = 10.209.76.197,10.209.76.198,192.135.82.132
    ILOM_NTP_SERVER_LIST = 10.132.0.121,10.132.0.122
    CAN_HA = YES
    CAN_HA_TYPE = IPMP
    STORAGE_ARRAY_COUNT = 1
    SS_DISK_COUNT = 6
    TZ = America/Los_Angeles
    SECURITY_PROFILE = CIS
    KEYSTORE_TYPE = pkcs11
    OMCTOOLKIT_VERSION = 1.1.17
    You can either use the values provided in this file or you can manually overwrite it. 
    Do you wish to use the existing /var/opt/oracle.minicluster/store/userinputs.txt file?
    Enter Y/N (Y): 
    User Inputs Validation for File /var/opt/oracle.minicluster/store/userinputs.txt Succeeded.
    [INFO    ] STEP 1: Check Package Version and Gather User Input COMPLETED
    [INFO    ] STEP 2: Prepare for System Install STARTED
    [INFO    ] Invoked by OS user: mcinstall
    [INFO    ] Find log at: oosmc1-n1:/var/opt/oracle.minicluster/setup/logs/omc_crdb_102816_141943.log
    [INFO    ] ---------- Starting Creating SQLite Database and Populating USER_INPUT Table
    [INFO    ] Populate USER_INPUT table in SQLite Database started.
    [INFO    ] Populate USER_INPUT table in SQLite Database succeeded.
    [INFO    ] Populate IPADDRESS table in SQLite Database started.
    [INFO    ] Populate IPADDRESS table in SQLite Database succeeded.
    [INFO    ] Set description for IPADDRESS table entries succeeded.
    [INFO    ] ---------- Starting Creating SQLite Database and Populating USER_INPUT Table Verification
    [INFO    ] Check existance of entries in USER_INPUT table started.
    [INFO    ] Check existance of entries in USER_INPUT table succeeded.
    [INFO    ] Populating USER_INPUT Table Completed
    [INFO    ] Invoked by OS user: mcinstall
    [INFO    ] Find log at: oosmc1-n1:/var/opt/oracle.minicluster/setup/logs/omc_gentmpenvvar_102816_141945.log
    [INFO    ] ---------- Starting Generating Environment Variables
    [INFO    ] Generating Environment Variables started.
    [INFO    ] Generating Environment Variables succeeded.
    [INFO    ] ---------- Starting Temporary Environment Variable File Verification
    [INFO    ] Check existence of $OMC_SETUP_DIR/tmp/setenv2.sh file started.
    [INFO    ] Check existence of $OMC_SETUP_DIR/tmp/setenv2.sh file succeeded.
    [INFO    ] Generating Environment Variables Completed
    [INFO    ] STEP 2: Prepare for System Install COMPLETED
    [INFO    ] STEP 3: Interconnect Setup STARTED
     
    [INFO    ] Log file path : oosmc1-n1:/var/opt/oracle.minicluster/setup/logs/omc_fn_changepvtip_v2_102816_141946.log
    [INFO    ] Reconfiguring Interconnect IP address..
    [INFO    ] Verifying reconfiguration of Interconnect IP address..
    [INFO    ] Reconfiguring Interconnect IP address.. Verified Successfully
    [INFO    ] Reconfiguring Interconnect IP address.. Completed
    [INFO    ] STEP 3: Interconnect Setup COMPLETED
    [INFO    ] STEP 4: Configure Explorer STARTED
     
    [INFO    ] Log file path : oosmc1-n1:/var/opt/oracle.minicluster/setup/logs/omc_explorer_102816_141950.log
    [INFO    ] Configuring explorer...
    [INFO    ] Enter the information to configure Oracle Explorer.
    [INFO    ] Please do not schedule any cron job to run the Explorer, as cron entries will be removed and not run on the MiniCluster.
    [INFO    ] Setting up explorer
     
    Absolute path of the Explorer output top location?
    [/var/explorer/output]: 
    [y]: 
     
    Retrieving serial number ... (can take time)
     
    Company name
    []: Oracle
    Contract Identifier
    []: SAP OOS
    System (oosmc1-n1, 86bb68e6) serial number
    [unknown]: 86bb68e6
    Contact name
    []: My Name
    Contact email address
    []: my.name@oracle.com
    Phone number
    []: 16505067000
    Address (line 1)
    []: 
    Address (line 2)
    []: 
    City
    []: Santa Clara
    State
    []: CA
    Zip
    []: 95054
    Select your geography from this list:
        1) AMERICAS
        2) EMEA
        3) APAC
    [AMERICAS] 1
    AMERICAS
    Two-character country code or '?' for a list of countries
    []: US
    Select the Explorer default transport upload method from this list:
        1) Using Diagnostic Assistant (DA)
        2) Other transport
        3) None
    [Using Diagnostic Assistant (DA)] 
    Selected: Using Diagnostic Assistant (DA)
    Do you want to configure Diagnostic Assistant to save credentials (y/n)?
    [y]: 
    Configuring Diagnostic Assistant to save credentials ... (can take time)
     
    If you would like to be notified by email when your explorer output is uploaded
    into the repository, enter the email address here. When notification is not
    needed, enter a single '-'.
    []: my.name@oracle.com
     
    Solaris zones:
     
    By default, Explorer collects data from all running local zones when the option
    -w localzones is specified. If you wish to limit data collection to only some
    of the local zones, enter the names of those zones below. Separate multiple
    zone names with a comma ','.
    Comma-separated list of zone names or '-' for all zones
    []: -
     
    You have answered:
                   Company name: Oracle
                    Contract ID: SAP OOS
     
           System serial number: 86bb68e6
     
                   Contact name: My Name
          Contact email address: my.name@oracle.com
                   Phone number: 16505067000
               Address (line 1): 
               Address (line 2): 
                           City: Santa Clara
                          State: CA
                            Zip: 95054
                        Country: United States
                   Country Code: US
     
                      Geography: AMERICAS
          Default result upload: Using Diagnostic Assistant (DA)
               Mail output from: my.name@oracle.com
              Mail on data load: my.name@oracle.com
             Solaris zone names: 
    Are these values okay (y/n)?
    []: y
    Do you wish to schedule explorer in cron (y/n)?
    []: y
    Run explorer weekly or monthly (with w=weekly and m=monthly)
    []: w
    At which hour would you like this to run (0 to 23)?
    23
    At which minute would you like this to run (0 to 59)?
    0
    On which day would you like this to run (0-6 with 0=Sunday)?
    0
    Oct 28 14:25:24 oosmc1-n1[21075] explorer:  Explorer defaults file updated.
    Oct 28 14:25:24 oosmc1-n1[21075] explorer:  Run /usr/sbin/explorer with options to collect data.
    [INFO    ] To run the Oracle Explorer, please login to the Oracle Engineered
    Systems Hardware Manager and go to the Support File Bundle tab.
    [INFO    ] Select Compute Server 1 (Node 1) or Compute Server 2 (Node 2) and
    click create. Explorer will be gathered as a part of the new Support File Bundle.
     
    [INFO    ] Configuring explorer... Completed
    [INFO    ] Invoked by OS user: mcinstall
    [INFO    ] Find log at: oosmc1-n1:/var/opt/oracle.minicluster/setup/logs/omc_scptonode1_102816_142525.log
    [INFO    ] ---------- Starting Copying Files from 1st Node to 2nd Node
    [INFO    ] Copy file started.
    [INFO    ] Copy file succeeded.
    [INFO    ] All Files have been Copied to 2nd Node successfully
    [INFO    ] Invoked by OS user: mcinstall
    [INFO    ] Find log at: oosmc1-n1:/var/opt/oracle.minicluster/setup/logs/omc_node1exec_102816_142525.log
    [INFO    ] ---------- Starting Executing Script on the 2nd Node
    [INFO    ] Executing Script on the 2nd Node started.
    [INFO    ] Check the existence of the script on the 2nd node
    [INFO    ] Execute the script on the 2nd node
     
    [INFO    ] Log file path : oosmc1-n2:/var/opt/oracle.minicluster/setup/logs/omc_explorer_102816_142532.log
    [INFO    ] Configuring explorer...
    [INFO    ] Configuring explorer... Completed
    [INFO    ] Executing Script on the 2nd Node succeeded.
    [INFO    ] Executing Script on the 2nd Node Completed
    [INFO    ] STEP 4: Configure Explorer COMPLETED
    [INFO    ] STEP 5: Check System Readiness STARTED
    [INFO    ] Log file path : oosmc1-n1:/var/opt/oracle.minicluster/setup/logs/omc_sysready_combined_v2_102816_142529.log
    [INFO    ]  Checking for System Readiness..
    Oct 28 14:19:50 mccn last message repeated 2 times
    Oct 28 14:25:31 mccn su: 'su root' succeeded for mcinstall on /dev/pts/3
     
    [INFO    ] Checking for System Readiness.. Completed
    [INFO    ] STEP 5: Check System Readiness COMPLETED
    [INFO    ] STEP 6: Verify Topology STARTED
     
    Oct 28 14:27:22 mccn su: 'su root' succeeded for mcinstall on /dev/pts/2
    [INFO    ] Invoked by OS user: root
    [INFO    ] Find log at: oosmc1-n1:/var/opt/oracle.minicluster/setup/logs/omc_verifytopology_102816_142723.log
    [INFO    ] ---------- Starting Verify Topology
    [INFO    ] Check PCI Layout of Network Cards started.
    [INFO    ] Check PCI Layout of Network Cards succeeded.
    [INFO    ] Check PCI Layout of Estes Cards started.
    [INFO    ] Check PCI Layout of Estes Cards succeeded.
    [INFO    ] Check JBOD Disk Arrays started.
    [INFO    ] Check JBOD Disk Arrays succeeded.
    [INFO    ] Check Interconnectivity between two Compute Nodes started.
    [INFO    ] Check Interconnectivity between two Compute Nodes succeeded.
    [INFO    ] Check Interconnect interface status started.
    [INFO    ] Check Interconnect interface status finished.
    [INFO    ] Check interface status of client access network started.
    [INFO    ] Check interface status of client access network finished.
    [INFO    ] Check SAS cabling started.
    [INFO    ] Check SAS cabling finished.
    [INFO    ] Verifying JBOD(s) Topology
    Oct 31 11:26:54 mccn last message repeated 2 times
    Oct 31 11:26:58 mccn su: 'su root' succeeded for root on /dev/pts/4
    INFO su to user root successfully.
    INFO:MCMU.controllers.common.pexpect_util:su to user root successfully.
    INFO SSH login to 192.168.10.51 successfully.
    INFO:MCMU.controllers.common.pexpect_util:SSH login to 192.168.10.51 successfully.
    INFO su to user root successfully.
    INFO:MCMU.controllers.common.pexpect_util:su to user root successfully.
    [INFO    ] The current connections are -
    [INFO    ] Compute_Node1 PCIE2 SAS_Port0 <--> Storage_Array1 IOM1 Port0 Correct
    [INFO    ] Compute_Node1 PCIE3 SAS_Port1 <--> Storage_Array1 IOM0 Port0 Correct
    [INFO    ] Compute_Node2 PCIE2 SAS_Port1 <--> Storage_Array1 IOM1 Port1 Correct
    [INFO    ] Compute_Node2 PCIE3 SAS_Port0 <--> Storage_Array1 IOM0 Port1 Correct
    [INFO    ] Verifying JBOD(s) Topology finished.
    [INFO    ] Executing omc_verifytopology on the other Compute Node started.
    : 
    [INFO    ] Invoked by OS user: root
    [INFO    ] Find log at: oosmc1-n2:/var/opt/oracle.minicluster/setup/logs/omc_verifytopology_103116_112743.log
    [INFO    ] ---------- Starting Verify Topology
    [INFO    ] Check PCI Layout of Network Cards started.
    [INFO    ] Check PCI Layout of Network Cards succeeded.
    [INFO    ] Check PCI Layout of Estes Cards started.
    [INFO    ] Check PCI Layout of Estes Cards succeeded.
    [INFO    ] Check JBOD Disk Arrays started.
    [INFO    ] Check JBOD Disk Arrays succeeded.
    [INFO    ] Check Interconnectivity between two Compute Nodes started.
    [INFO    ] System setup was not initiated yet. Cannot check interconnectivity 
    between two compute nodes at this time. Try again after initiating system setup.
    [INFO    ] Verify Topology Completed
    [INFO    ] Executing omc_verifytopology on the other Compute Node succeeded.
    [INFO    ] Verify Topology Completed
    [INFO    ] STEP 6: Verify Topology COMPLETED
    [INFO    ] STEP 7: Prepare Network Interfaces STARTED
     
    Oct 31 11:27:37 mccn su: 'su root' succeeded for mcinstall on /dev/pts/2
    [INFO    ] Log file path : oosmc1-n1:/var/opt/oracle.minicluster/setup/logs/omc_fn_netdiscovery_v3_103116_112737.log
    [INFO    ] Network Interface Discovery..
    [INFO    ] Identifying network interfaces for public network
    [INFO    ] Identifying network interfaces for private network
    [INFO    ] Verifying Network Interface Discovery..
    [INFO    ] Network Interface Discovery.. Verified Successfully
    [INFO    ] Network Interface Discovery.. Completed
     
    [INFO    ] Log file path : oosmc1-n1:/var/opt/oracle.minicluster/setup/logs/omc_fn_preppubnet_v2_103116_112742.log
    [INFO    ] Preparing public network for Client Access..
    [INFO    ] Verifying public network for Client Access..
    [INFO    ] Preparing public network for Client Access.. Verified Successfully
    [INFO    ] Preparing public network for Client Access.. Completed
    [INFO    ] Invoked by OS user: mcinstall
    [INFO    ] Find log at: oosmc1-n1:/var/opt/oracle.minicluster/setup/logs/omc_scptonode1_103116_112748.log
    [INFO    ] ---------- Starting Copying Files from 1st Node to 2nd Node
    [INFO    ] Copy file started.
    [INFO    ] Copy file succeeded.
    [INFO    ] Copy file started.
    [INFO    ] Copy file succeeded.
    [INFO    ] All Files have been Copied to 2nd Node successfully
    [INFO    ] Invoked by OS user: mcinstall
    [INFO    ] Find log at: oosmc1-n1:/var/opt/oracle.minicluster/setup/logs/omc_node1exec_103116_112749.log
    [INFO    ] ---------- Starting Executing Script on the 2nd Node
    [INFO    ] Executing Script on the 2nd Node started.
    [INFO    ] Check the existence of the script on the 2nd node
    [INFO    ] Execute the script on the 2nd node
     
    [INFO    ] Log file path : oosmc1-n2:/var/opt/oracle.minicluster/setup/logs/omc_fn_preppubnet_v2_103116_112756.log
    [INFO    ] Preparing public network for Client Access..
    [INFO    ] Verifying public network for Client Access..
    [INFO    ] Preparing public network for Client Access.. Verified Successfully
    [INFO    ] Preparing public network for Client Access.. Completed
    [INFO    ] Executing Script on the 2nd Node succeeded.
    [INFO    ] Executing Script on the 2nd Node Completed
    [INFO    ] STEP 7: Prepare Network Interfaces COMPLETED
    [INFO    ] STEP 8: Configure Client Access Network on Node 1 STARTED
     
    [INFO    ] Log file path : oosmc1-n1:/var/opt/oracle.minicluster/setup/logs/omc_fn_initialpubip_v2_103116_112756.log
    [INFO    ] Performing public IP configuration ..
    Oct 31 11:27:56 mccn last message repeated 2 times
    Oct 31 11:28:08 mccn in.mpathd[70]: All IP interfaces in group ipmppub0 are now unusable
    [INFO    ] Verification of public IP configuration ..
    [INFO    ] Performing public IP configuration .. Verified Successfully
    [INFO    ] Performing public IP configuration .. Completed
     
    Oct 31 11:28:22 mccn su: 'su root' succeeded for mcinstall on /dev/pts/2
    [INFO    ] Log file path : oosmc1-n1:/var/opt/oracle.minicluster/setup/logs/omc_fn_routerconfig_v2_103116_112822.log
    [INFO    ] Configuring default router ..
    [INFO    ] Check if gateway(10.133.80.1) is reachable
    [INFO    ] Trial:0
    [INFO    ] Gateway is reachable. Continuing with configuration
    [INFO    ] Verifying Configuration of default router ..
    [INFO    ] Configuring default router .. Verified Successfully
    [INFO    ] Configuring default router .. Completed
     
    [INFO    ] Log file path : oosmc1-n1:/var/opt/oracle.minicluster/setup/logs/omc_fn_dnsconfig_v2_103116_112829.log
    [INFO    ] Setting up DNS Client ..
    [INFO    ] Check if any of DNS Server 10.209.76.197,10.209.76.198,192.135.82.132 is un-reachable.
    [INFO    ] Configuring name service switch to use DNS ..
    [INFO    ] Verification of Setting  DNS Client ..
    [INFO    ] Setting up DNS Client .. Verified Successfully
    [INFO    ] Setting up DNS Client .. Completed
    [INFO    ] STEP 8: Configure Client Access Network on Node 1 COMPLETED
    [INFO    ] STEP 9: Configure Client Access Network on Node 2 STARTED
    [INFO    ] Invoked by OS user: mcinstall
    [INFO    ] Find log at: oosmc1-n1:/var/opt/oracle.minicluster/setup/logs/omc_scptonode1_103116_112848.log
    [INFO    ] ---------- Starting Copying Files from 1st Node to 2nd Node
    [INFO    ] Copy file started.
    [INFO    ] Copy file succeeded.
    [INFO    ] Copy file started.
    [INFO    ] Copy file succeeded.
    [INFO    ] All Files have been Copied to 2nd Node successfully
    [INFO    ] Invoked by OS user: mcinstall
    [INFO    ] Find log at: oosmc1-n1:/var/opt/oracle.minicluster/setup/logs/omc_node1exec_103116_112849.log
    [INFO    ] ---------- Starting Executing Script on the 2nd Node
    [INFO    ] Executing Script on the 2nd Node started.
    [INFO    ] Check the existence of the script on the 2nd node
    [INFO    ] Execute the script on the 2nd node
     
    [INFO    ] Log file path : oosmc1-n2:/var/opt/oracle.minicluster/setup/logs/omc_fn_initialpubip_v2_103116_112856.log
    [INFO    ] Performing public IP configuration ..
    [INFO    ] Verification of public IP configuration ..
    [INFO    ] Performing public IP configuration .. Verified Successfully
    [INFO    ] Performing public IP configuration .. Completed
    [INFO    ] Executing Script on the 2nd Node succeeded.
    [INFO    ] Executing Script on the 2nd Node Completed
    [INFO    ] Invoked by OS user: mcinstall
    [INFO    ] Find log at: oosmc1-n1:/var/opt/oracle.minicluster/setup/logs/omc_node1exec_103116_112915.log
    [INFO    ] ---------- Starting Executing Script on the 2nd Node
    [INFO    ] Executing Script on the 2nd Node started.
    [INFO    ] Check the existence of the script on the 2nd node
    [INFO    ] Execute the script on the 2nd node
     
    [INFO    ] Log file path : oosmc1-n2:/var/opt/oracle.minicluster/setup/logs/omc_fn_routerconfig_v2_103116_112923.log
    [INFO    ] Configuring default router ..
    [INFO    ] Check if gateway(10.133.80.1) is reachable
    [INFO    ] Trial:0
    [INFO    ] Gateway is reachable. Continuing with configuration
    [INFO    ] Verifying Configuration of default router ..
    [INFO    ] Configuring default router .. Verified Successfully
    [INFO    ] Configuring default router .. Completed
    [INFO    ] Executing Script on the 2nd Node succeeded.
    [INFO    ] Executing Script on the 2nd Node Completed
    [INFO    ] Invoked by OS user: mcinstall
    [INFO    ] Find log at: oosmc1-n1:/var/opt/oracle.minicluster/setup/logs/omc_node1exec_103116_112953.log
    [INFO    ] ---------- Starting Executing Script on the 2nd Node
    [INFO    ] Executing Script on the 2nd Node started.
    [INFO    ] Check the existence of the script on the 2nd node
    [INFO    ] Execute the script on the 2nd node
     
    [INFO    ] Log file path : oosmc1-n2:/var/opt/oracle.minicluster/setup/logs/omc_fn_dnsconfig_v2_103116_113001.log
    [INFO    ] Setting up DNS Client ..
    [INFO    ] Check if any of DNS Server 10.209.76.197,10.209.76.198,192.135.82.132 is un-reachable.
    [INFO    ] Configuring name service switch to use DNS ..
    [INFO    ] Verification of Setting  DNS Client ..
    [INFO    ] Setting up DNS Client .. Verified Successfully
    [INFO    ] Setting up DNS Client .. Completed
    [INFO    ] Executing Script on the 2nd Node succeeded.
    [INFO    ] Executing Script on the 2nd Node Completed
    [INFO    ] STEP 9: Configure Client Access Network on Node 2 COMPLETED
    [INFO    ] STEP 10: Configure NTP Client, Set Password Policy and Setup Apache Web Server STARTED
     
    [INFO    ] Log file path : oosmc1-n1:/var/opt/oracle.minicluster/setup/logs/omc_ntpconfig_v2_103116_113013.log
    [INFO    ] Setting up NTP Client ..
    [INFO    ] Check if any of NTP Server 10.132.0.121,10.132.0.122 is reachable.
    [INFO    ] Verifying NTP Client ..
    [INFO    ] Setting up NTP Client .. Verified Successfully
    [INFO    ] Setting up NTP Client .. Completed
    [INFO    ] Invoked by OS user: mcinstall
    [INFO    ] Find log at: oosmc1-n1:/var/opt/oracle.minicluster/setup/logs/omc_node1exec_103116_113141.log
    [INFO    ] ---------- Starting Executing Script on the 2nd Node
    [INFO    ] Executing Script on the 2nd Node started.
    [INFO    ] Check the existence of the script on the 2nd node
    [INFO    ] Execute the script on the 2nd node
     
    [INFO    ] Log file path : oosmc1-n2:/var/opt/oracle.minicluster/setup/logs/omc_ntpconfig_v2_103116_113140.log
    [INFO    ] Setting up NTP Client ..
    [INFO    ] Check if any of NTP Server 10.132.0.121,10.132.0.122 is reachable.
    [INFO    ] Verifying NTP Client ..
    [INFO    ] Setting up NTP Client .. Verified Successfully
    [INFO    ] Setting up NTP Client .. Completed
    [INFO    ] Executing Script on the 2nd Node succeeded.
    [INFO    ] Executing Script on the 2nd Node Completed
     
    [INFO    ] Log file path : oosmc1-n1:/var/opt/oracle.minicluster/setup/logs/omc_passwdpolicy_103116_113301.log
    [INFO    ] Starting Configuring Password Policy..
    [INFO    ] Configuring Password Policy.. Verified Successfully
    [INFO    ] Configuring Password Policy.. Completed
    [INFO    ] Invoked by OS user: mcinstall
    [INFO    ] Find log at: oosmc1-n1:/var/opt/oracle.minicluster/setup/logs/omc_node1exec_103116_113302.log
    [INFO    ] ---------- Starting Executing Script on the 2nd Node
    [INFO    ] Executing Script on the 2nd Node started.
    [INFO    ] Check the existence of the script on the 2nd node
    [INFO    ] Execute the script on the 2nd node
     
    [INFO    ] Log file path : oosmc1-n2:/var/opt/oracle.minicluster/setup/logs/omc_passwdpolicy_103116_113303.log
    [INFO    ] Starting Configuring Password Policy..
    [INFO    ] Configuring Password Policy.. Verified Successfully
    [INFO    ] Configuring Password Policy.. Completed
    [INFO    ] Executing Script on the 2nd Node succeeded.
    [INFO    ] Executing Script on the 2nd Node Completed
    [INFO    ] Log file path : oosmc1-n1:/var/opt/oracle.minicluster/setup/logs/omc_fn_apachesslcfg_103116_113304.log
    [INFO    ] Configuring Apache SSL security and Synchronizing the DB..
    Oct 31 11:33:01 mccn last message repeated 3 times
    Oct 31 11:33:07 mccn su: 'su root' succeeded for mcinstall on /dev/pts/3
    Oct 31 11:33:08 mccn last message repeated 3 times
    Oct 31 11:33:08 mccn su: 'su root' succeeded for mcinstall on /dev/pts/3
    [INFO    ] Verifying Apache SSL setup..
    [INFO    ] Configuring Apache SSL security and Synchronizing the DB.. Verified Successfully
    [INFO    ] Configuring Apache SSL security and Synchronizing the DB.. Completed
     
        -------------------------------------------------------------------------------
        -------------------------------------------------------------------------------
        
        Please download the MiniCluster Component Bundle from Oracle MiniCluster S7-2 
    Software Download Center (My Oracle Support Doc ID: 2153282.1) and follow the 
    instructions if not done already -
        If you download the Bundle on your local host, transfer files to both MiniCluster 
    nodes by executing step 1 on both nodes
            1.scp <path-on-local-host>/mc-*-sfw.tar.a* mcinstall@<ip-or-host-of-node>:/var/tmp
     
            If you downloaded the Bundle directly on MiniCluster nodes, then make 
    sure both nodes have the Bundle under /var/tmp directory.
     
            Then run these steps -
            2.cd /var/tmp on both the nodes and extract the files using
            3.cat mc-*-sfw.tar.a? | gtar -x -C /var/opt/oracle.minicluster/ -f -
     
        
     
        Please use browser user interface (BUI) to complete the system and tenant setup
        URL:
            https://oosmc1-n1.us.oracle.com/MCMU -OR- https://10.133.82.98/MCMU
            Administrator login ID: mcinstall. Default password: welcome1
        
     
        If you want to continue using Command Line Interface(CLI) and are currently connected via ILOM,
        login back to the host as mcinstall user, using public hostname or IP Address, then follow these steps -
        1.Register mcinstall user using 'mcmu user --create -u mcinstall -e <email> -n <fullname> -p <phone>' command
        2.Supervisor must check email and register 'mcinstall' user to activate account
        3.Change mcinstall user password using 'mcmu user --changepswd -u mcinstall' command
        4.Continue with setup using 'mcmu setupmc -s all' command
        
        ------------------------------------------------------------------------------
        ------------------------------------------------------------------------------
        
    [INFO    ] STEP 10: Configure NTP Client, Set Password Policy and Setup Apache Web Server COMPLETED
    [INFO    ] Step execution completed successfully
     
     installmc completed successfully
    [INFO    ] Configuring Firstnet.. Completed
    mcinstall@oosmc1-n1:/var/home/mcinstall % 

    Listing 5: Output from running the mcinstall script on node 1.

     

    Make sure that the script output ends with the message installmc completed successfully. If it does not, fix the error and rerun the script until you achieve successful execution.

     

    Step 7. Prepare to install the Oracle MiniCluster Component Bundle.

     

    Follow the steps listed at the end of the output (Listing 5). If you have not downloaded the Oracle MiniCluster Component Bundle files previously, go back to My Oracle Support, download the files, and follow the instructions in the file.readme file.

     

    Copy the downloaded component bundle files over to node 1 of Oracle MiniCluster (Listing 6).

     

    Joebar:UserInput user$ scp /Users/user/Downloads/MiniCluster/1.1.18.2/Component\ 
    Bundle/*.zip mcinstall@oosmc1-n1.us.oracle.com:/var/tmp
    The authenticity of host 'oosmc1-n1.us.oracle.com (10.133.82.98)' can't be established.
    RSA key fingerprint is SHA256:qUSQ7Z2JrTGdz26XxzrRiKnxs3X0MORWjpPWoF5Sg3c.
    Are you sure you want to continue connecting (yes/no)? yes
    Warning: Permanently added 'oosmc1-n1.us.oracle.com' (RSA) to the list of known hosts.
    Password: 
    p24844733_100_SOLARIS64_10of12.zip                         100%  710MB  11.3MB/s   01:03    
    p24844733_100_SOLARIS64_11of12.zip                         100% 1561MB  11.2MB/s   02:19    
    p24844733_100_SOLARIS64_12of12.zip                         100% 1335MB  11.2MB/s   01:59    
    p24844733_100_SOLARIS64_1of12.zip                          100% 1773MB  11.2MB/s   02:38    
    p24844733_100_SOLARIS64_2of12.zip                          100% 1147MB  11.2MB/s   01:42    
    p24844733_100_SOLARIS64_3of12.zip                          100%  389MB  11.1MB/s   00:35    
    p24844733_100_SOLARIS64_4of12.zip                          100% 1160MB  11.3MB/s   01:43    
    p24844733_100_SOLARIS64_5of12.zip                          100% 1969MB  11.3MB/s   02:55    
    p24844733_100_SOLARIS64_6of12.zip                          100% 1962MB  11.2MB/s   02:55    
    p24844733_100_SOLARIS64_7of12.zip                          100% 1655MB  11.3MB/s   02:27    
    p24844733_100_SOLARIS64_8of12.zip                          100% 1432MB  11.3MB/s   02:07    
    p24844733_100_SOLARIS64_9of12.zip                          100%  258MB  11.7MB/s   00:22    
    Joebar:UserInput user$ 

    Listing 6:  Copy the Oracle MiniCluster Component Bundle to node 1.

     

    Copy the bundle files from node 1 over to node 2.

     

    Joebar:UserInput user$ ssh mcinstall@oosmc1-n1
    The authenticity of host 'oosmc1-n1 (10.133.82.98)' can't be established.
    RSA key fingerprint is SHA256:qUSQ7Z2JrTGdz26XxzrRiKnxs3X0MORWjpPWoF5Sg3c.
    Are you sure you want to continue connecting (yes/no)? yes
    Warning: Permanently added 'oosmc1-n1' (RSA) to the list of known hosts.
    Password: 
    Last login: Mon Oct 31 13:42:08 2016 from Joebar
    Oracle Corporation      SunOS 5.11      11.3    August 2016
    mcinstall@oosmc1-n1:/var/home/mcinstall % scp /var/tmp/*.zip mcinstall@oosmc1-n2.us.oracle.com:/var/tmp
    The authenticity of host 'oosmc1-n2.us.oracle.com (10.133.82.99)' can't be established.
    RSA key fingerprint is 02:38:61:d5:4f:33:4c:dd:d9:ad:93:20:19:89:28:1b.
    Are you sure you want to continue connecting (yes/no)? yes
    Warning: Permanently added 'oosmc1-n2.us.oracle.com,10.133.82.99' (RSA) to the list of known hosts.
    Password: 
    p24844733_100_SOLARI 100% |*********************************|    709 MB    00:06    
    p24844733_100_SOLARI 100% |*********************************|   1561 MB    00:13    
    p24844733_100_SOLARI 100% |*********************************|   1334 MB    00:11    
    p24844733_100_SOLARI 100% |*********************************|   1772 MB    00:15    
    p24844733_100_SOLARI 100% |*********************************|   1146 MB    00:10    
    p24844733_100_SOLARI 100% |*********************************|    388 MB    00:03    
    p24844733_100_SOLARI 100% |*********************************|   1160 MB    00:10    
    p24844733_100_SOLARI 100% |*********************************|   1968 MB    00:17    
    p24844733_100_SOLARI 100% |*********************************|   1962 MB    00:17    
    p24844733_100_SOLARI 100% |*********************************|   1655 MB    00:14    
    p24844733_100_SOLARI 100% |*********************************|   1432 MB    00:12    
    p24844733_100_SOLARI 100% |*********************************|    258 MB    00:02    
    mcinstall@oosmc1-n1:/var/home/mcinstall % 

    Listing 7: Copy the Oracle MiniCluster Component Bundle files to node 2.

     

    On both nodes, unzip the downloaded files, assemble the image files into a full tar image, and uncompress the final images into the path /var/opt/oracle.minicluster/. Listings 8 and 9 show the steps to unpack the bundle on node 1 and node 2, respectively.

     

    mcinstall@oosmc1-n1:/var/home/mcinstall % cd /var/tmp
    mcinstall@oosmc1-n1:/var/tmp % /bin/unzip '*.zip'
    Archive:  p24844733_100_SOLARIS64_1of12.zip
      inflating: mc-1.1.18.2-sfw.tar.aa  
      inflating: MC-README.txt           
     
    Archive:  p24844733_100_SOLARIS64_5of12.zip
      inflating: mc-1.1.18.2-sfw.tar.ae  
     
    Archive:  p24844733_100_SOLARIS64_9of12.zip
      inflating: mc-1.1.18.2-sfw.tar.ai  
     
    Archive:  p24844733_100_SOLARIS64_12of12.zip
      inflating: mc-1.1.18.2-sfw.tar.al  
     
    Archive:  p24844733_100_SOLARIS64_8of12.zip
      inflating: mc-1.1.18.2-sfw.tar.ah  
     
    Archive:  p24844733_100_SOLARIS64_4of12.zip
      inflating: mc-1.1.18.2-sfw.tar.ad  
     
    Archive:  p24844733_100_SOLARIS64_10of12.zip
      inflating: mc-1.1.18.2-sfw.tar.aj  
     
    Archive:  p24844733_100_SOLARIS64_2of12.zip
      inflating: mc-1.1.18.2-sfw.tar.ab  
     
    Archive:  p24844733_100_SOLARIS64_6of12.zip
      inflating: mc-1.1.18.2-sfw.tar.af  
     
    Archive:  p24844733_100_SOLARIS64_11of12.zip
      inflating: mc-1.1.18.2-sfw.tar.ak  
     
    Archive:  p24844733_100_SOLARIS64_3of12.zip
      inflating: mc-1.1.18.2-sfw.tar.ac  
     
    Archive:  p24844733_100_SOLARIS64_7of12.zip
      inflating: mc-1.1.18.2-sfw.tar.ag  
     
    12 archives were successfully processed.
    mcinstall@oosmc1-n1:/var/tmp % cat mc-*-sfw.tar.a? | gtar -x -C /var/opt/oracle.minicluster/ -f -
    mcinstall@oosmc1-n1:/var/tmp % 

    Listing 8: Unpacking the archive files on node 1.

     

    Joebar:UserInput user$ ssh mcinstall@oosmc1-n2
    The authenticity of host 'oosmc1-n2 (10.133.82.99)' can't be established.
    RSA key fingerprint is SHA256:qZbF3BjP+i9TGZSp81JELn0Muk6fG+VNmG5yDqt8g7M.
    Are you sure you want to continue connecting (yes/no)? yes
    Warning: Permanently added 'oosmc1-n2,10.133.82.99' (RSA) to the list of known hosts.
    Password: 
    Last login: Mon Oct 31 14:15:57 2016 from oosmc1-n1.us.or
    Oracle Corporation      SunOS 5.11      11.3    August 2016
    mcinstall@oosmc1-n2:/var/home/mcinstall % cd /var/tmp
    mcinstall@oosmc1-n2:/var/tmp % /bin/unzip '*.zip'
    Archive:  p24844733_100_SOLARIS64_3of12.zip
      inflating: mc-1.1.18.2-sfw.tar.ac  
     
    Archive:  p24844733_100_SOLARIS64_7of12.zip
      inflating: mc-1.1.18.2-sfw.tar.ag  
     
    Archive:  p24844733_100_SOLARIS64_12of12.zip
      inflating: mc-1.1.18.2-sfw.tar.al  
     
    Archive:  p24844733_100_SOLARIS64_2of12.zip
      inflating: mc-1.1.18.2-sfw.tar.ab  
     
    Archive:  p24844733_100_SOLARIS64_6of12.zip
      inflating: mc-1.1.18.2-sfw.tar.af  
     
    Archive:  p24844733_100_SOLARIS64_8of12.zip
      inflating: mc-1.1.18.2-sfw.tar.ah  
     
    Archive:  p24844733_100_SOLARIS64_4of12.zip
      inflating: mc-1.1.18.2-sfw.tar.ad  
     
    Archive:  p24844733_100_SOLARIS64_11of12.zip
      inflating: mc-1.1.18.2-sfw.tar.ak  
     
    Archive:  p24844733_100_SOLARIS64_1of12.zip
      inflating: mc-1.1.18.2-sfw.tar.aa  
      inflating: MC-README.txt           
     
    Archive:  p24844733_100_SOLARIS64_5of12.zip
      inflating: mc-1.1.18.2-sfw.tar.ae  
     
    Archive:  p24844733_100_SOLARIS64_9of12.zip
      inflating: mc-1.1.18.2-sfw.tar.ai  
     
    Archive:  p24844733_100_SOLARIS64_10of12.zip
      inflating: mc-1.1.18.2-sfw.tar.aj  
     
    12 archives were successfully processed.
    mcinstall@oosmc1-n2:/var/tmp % cat mc-*-sfw.tar.a? | gtar -x -C /var/opt/oracle.minicluster/ -f -
    mcinstall@oosmc1-n2:/var/tmp % 

    Listing 9: Unpacking the archive files on node 2.

     

    Step 8. Complete the setup using the Oracle MiniCluster Configuration Utility.

     

    Complete the setup using the Oracle MiniCluster Configuration Utility (MCMU), which is a browser-based user interface (BUI) for performing management tasks. Open the utility by pointing a browser to the address https://oosmc1-n1.us.oracle.com/MCMU (Figure 13). If you are logging into MCMU for the first time, the utility requires you to sign in using default credentials (username mcinstall and password welcome1) and then define a new password.

     

    f13.png

    Figure 13: Open the Oracle MiniCluster Configuration Utility.

     

    Register and approve the installation administrator account (Figure 14). An email should be sent to you with an approval link.

     

    f14.png

    Figure 14: Register the new administrator account.

     

    Figure 15 lists the configuration steps. Click Next to proceed with the configuration.

     

    f15.png

    Figure 15: Oracle MiniCluster configuration steps.

     

    On the System Setup screen, click Run all steps to complete the system setup (Figure 16). Steps 1 to 10 should already be completed.

     

    f16.png

    Figure 16: Run the system setup steps.

     

    Figure 17 reflects system setup progress. Once all the system setup steps are complete (Figure 18), click Continue.

     

    f17.png

    Figure 17: System setup is in progress.

     

    f18.png

    Figure 18: System setup is complete.

     

    Create Database VM Profiles for the SAP Environment

     

    After the system setup process is complete, it is necessary to configure database (DB) and application (App) VM group profiles according to SAP environment requirements. VM groups are collections of VMs that share the same profile characteristics, such as the number of VMs per compute node, the number of cores assigned to each VM, and management network host names and IP addresses for VMs. You will use the Oracle MiniCluster Configuration Utility interface to define (or later modify) the database and application VM group profiles.

     

    Step 1. Create host name entries for database VMs in the DNS configuration.

     

    First, add the necessary host names with their corresponding IP addresses to the DNS configuration. Table 4 lists the entries for database VMs in the sample deployment.

     

    Table 4: Host Names and IP Addresses for Database VMs

        

    Host NameIP Address
    sapdb1-vm1-n110.133.82.108
    sapdb1-vm1-n1-vip10.133.82.109
    sapdb1-vm1-n210.133.82.110
    sapdb1-vm1-n2-vip10.133.82.111
    sapdb1scan10.133.82.112
    sapdb1scan10.133.82.113
    sapdb1scan10.133.82.114

     

    Step 2. Use the Oracle MiniCluster Configuration Utility to configure the database VM group profile.

     

    Figure 19 shows the main screen of the Oracle MiniCluster Configuration Utility. Under Database, click Virtual Machine Group Profile.

     

    f19.png

    Figure 19: Oracle MiniCluster Configuration Utility main screen.

     

    Click Create New Profile (Figure 20).

     

    f20.png

    Figure 20: Creating a new database VM group profile.

     

    Enter a name in the Virtual Machine Group Name field. For Role Separated, select Yes. As shown in Figure 21, the utility will create profile with single VM on node 1 and a single VM on node 2. Click Next.

     

    f21.png

    Figure 21: Enter information for the database VM group.

     

    Enter public host names for the VMs (Figure 22). It is an SAP requirement that you limit the number of characters in host names to 13 characters or less. According to "SAP Note 611361," a host name must be an alphanumerical string up to 13 characters; it can contain alpha characters [A–Z] and [a–z], digits [0–9], and a hyphen or minus character (-); and it must begin with an alpha character. (Access to SAP Notes requires logon and authentication to the SAP Support Portal.) After entering the host names, click Next.

     

    f22.png

    Figure 22: Enter host names for the database VMs.

     

    As shown in Figure 23, enter a database Single Client Access Name (SCAN). Click Next.

     

    f23.png

    Figure 23: Enter a SCAN name for the database cluster.

     

    On the Review screen (Figure 24), verify the parameters and click Generate.

     

    f24.png

    Figure 24: Review the database profile parameters.

     

    Figure 25 shows status for the database VM group profile.

     

    f25.png

    Figure 25: Status of the database VM group profile.

     

    After profile configuration is complete (Figure 26), click Done.

     

    f26.png

    Figure 26: Profile configuration is complete.

     

    Click Deploy to confirm and create the VMs based on the profile (Figure 27).

     

    f27.png

    Figure 27: Deploying the profile.

     

    Figure 28 shows profile deployment status. Click Finish once the process completed. Do not close the pop-up window until the Finish button appears.

     

    f28.png

    Figure 28: Status of deploying the database VM group profile.

     

    As Figure 29 shows, the database VM group (with one VM on each node) is now active.

     

    f29.png

    Figure 29: The database VM group is active.

     

    Create Application VM Profiles for the SAP Environment

     

    Using a similar process and the Oracle MiniCluster Configuration Utility, create a VM group profile for the application VMs.

     

    Step 1. Create host name entries for application VMs in DNS.

     

    Add the necessary host names with their corresponding IP addresses to the DNS configuration. Table 5 lists the entries for the application VMs in the sample deployment.

     

    Table 5: Host Names and IP Addresses for Application VMs

     

    Host NameIP Address
    oos1-app110.133.82.115
    oos1-app210.133.82.116

     

    Step 2. Use the Oracle MiniCluster Configuration Utility to configure the application VM group profile.

     

    Under Application, click Virtual Machine Group Profile. On that screen, click Create New Profile. Enter a name for the profile group (Figure 30) and click Next.

     

    f30.png

    Figure 30: Creating a new application VM group profile.

     

    Enter the public host names (Figure 31) and then click Next.

     

    f31.png

    Figure 31: Enter public host names for the application VMs.

     

    Review the settings, and then click Generate (Figure 32).

     

    f32.png

    Figure 32: Review profile parameters.

     

    After the application VM group profile is configured, click Done (Figure 33).

     

    f33.png

    Figure 33: Profile configuration is complete.

     

    Review the settings and then click Deploy (Figure 34).

     

    f34.png

    Figure 34: Deploying the profile.

     

    Click Finish once the process has been completed.

     

    f35.png

    Figure 35: Status of deploying the application VM group profile.

     

    As Figure 36 shows, the application VM group (with a single VM on each node) is now active.

     

    f36.png

    Figure 36: The application VM group is active.

     

    Complete the Installation

     

    To complete the rest of the SAP installation steps, it is necessary to perform two additional steps: creating the user sapadmin as a Tenant Admin user and setting up an Oracle Database home.

     

    Step 1. Create the sapadmin user.

     

    From the MCMU initial screen, click Register and complete the user registration screen, selecting Tenant Admin for Type of User (Figure 37).

     

    f37.png

    Figure 37: Creating a Tenant Admin user.

     

    An email with the subject "New User Approval Request: MiniCluster Administration" will be sent to the Oracle MiniCluster Approval Board. The link in the email must be used to approve the new user account. After the new user approval request is approved, the sapadmin account appears in the listing of user accounts (Figure 38).

     

    f38.png

    Figure 38: The sapadmin account now appears on the User Accounts page.

     

    An email will be sent directly to the sapadmin user to activate the account and create a new password.

     

    Step 2. Create the Oracle Database home.

     

    Create a database home for the SAP installation in both database VMs. Under Database, select Instances and click Create DB Home (Figure 39).

     

    f39.png

    Figure 39: Select Create Database Home to create the database home.

     

    On the Create Database Home page, specify the appropriate settings for the database version, the Oracle home path, and the patch level (Figure 40). Click Create.

     

    f40.png

    Figure 40: Specify settings for the database home.

     

    A status page appears, estimating the remaining time needed to create the database home (Figure 41).

     

    f41.png

    Figure 41: The status page estimates the time remaining to create the database home.

     

    Final Thoughts

     

    Business-critical SAP applications require database and application servers implemented on highly available infrastructure. Oracle MiniCluster S7-2 features fully redundant, high-performance, shared flash storage and active/active independent compute nodes with redundant network connectivity, enabling a highly available architecture for strategic, performance-sensitive SAP applications. As shown in this article, Oracle MiniCluster software tools help to simplify the Oracle MiniCluster setup process for configuring VMs and preparing Oracle Database and Oracle RAC configurations. In this way, an SAP solution on Oracle MiniCluster can help to reduce implementation errors and improve time to deployment.

     

    A second article in this series, "Installing SAP on Oracle MiniCluster ," describes the subsequent procedures to install and configure SAP software components in the infrastructure VMs created in this article.

     

    See Also

     

    Online Resources

     

     

    White Papers

     

     

    Documentation

     

     

    About the Authors

     

    Hans-Juergen Denecke is a principal software engineer in the Oracle's Cloud Applications Engineering organization in Germany. He is responsible for certifications of the SAP software stack on Oracle hardware and Oracle Solaris and other Oracle software products. Denecke is a graduate engineer in mechanical engineering and has over 20 years of experience in the computer industry.

     

    Kevin Klapak is a product manager in the Oracle Optimized Solutions team. He joined the team in January 2015 after completing his master's degree from Carnegie Mellon University. He has a background in computer science and over five years of IT experience. Since joining Oracle, he has been working on database migration, Apache Spark/big data analytics, and systems security.

     

    Pierre Reynes is a solution manager for Oracle Optimized Solution for SAP and Oracle Optimized Solution for PeopleSoft. He is responsible for driving the strategy and efforts to help raise customer and market awareness for Oracle Optimized Solutions in these areas. Reynes has over 25 years of experience in the computer and network industries.