This guide provides condensed instructions for setting up and configuring Oracle's MiniCluster S7-2. Use this guide if you are already familiar with the setup and configuration procedures for MiniCluster. For more detailed setup and configuration instructions, refer to the Oracle MiniCluster S7-2 Installation Guide.
Following are checklists that you can use to verify that you have completed the necessary tasks to install and configure your MiniCluster:
|
|
|
There are certain preliminary tasks that you can complete prior to receiving your MiniCluster, which will reduce the amount of setup time you will go through when your MiniCluster arrives at your site.
Run the Initial Configuration tool on any system outside of MiniCluster to provide initial configuration information for your MiniCluster, though at some point in the procedure, you will need to run the tool on the same network where you will be installing MiniCluster. When you finish providing all the necessary configuration information, the tool generates two text configuration files (userinputs.txt and omcips.txt) that you copy to the first MiniCluster compute node to complete the configuration process.
Go to the My Oracle Support site:
and click on the Sign In button to log in to the site.
Enter 2153282.1 in the search field in the upper right corner of the page, or in the search field beneath the Enter search terms text lower on the page, and locate the MiniCluster MOS note (Oracle MiniCluster S7-2 Software Download Center).
Click on the Latest Release link at the top of the MOS note, or on the MiniCluster Initial Configuration Tool link beneath the Latest Release link, to go to the section in the MOS note with the latest version of the Initial Configuration tool.
The Initial Configuration tool is contained within a patch. Clicking on the patch ID brings you to the download page for this particular patch.
Download the patch zip file onto any system, such as a laptop. Note that the information in the Platform or Language field on the patch page refers to the OS that runs on MiniCluster itself, not the OS for the system where you will be running the tool. The Initial Configuration tool can be run on a Windows, Solaris or Linux environment.
You will use the Initial Configuration tool to enter system-level configuration information for your MiniCluster. At one point later in the Initial Configuration tool process, the tool uses the information that you enter to verify system-level IP addresses and host names on the network, so at that point, you must run the tool on the same network where you will be installing MiniCluster. However, if necessary, you can enter the majority of the configuration information into the tool on any system, without being connected to the same network where MiniCluster will be installed. These procedures will tell you when you are at the point when you must be connected to the same network where you will be installing MiniCluster.
A TAR file and README text file are created.
The UserInput directory is created.
In a Windows environment, double-click the config-tool.bat file or enter the following in a terminal window from the directory containing the file:
config-tool
In a Solaris or Linux environment, enter the following in a terminal window from the directory containing the file:
./config-tool.sh
The Initial Configuration tool window appears.
Make the following selections in the General pane.
Select the type of MiniCluster system that you ordered. Only valid option is S7-2.
If you have a previously-completed configuration file that you want to import, click the Import Configuration File button and navigate to the userinputs.txt file that you want to import. The remaining fields in this screen automatically populate with the information that you provided in the previously-completed configuration file.
The host name prefix must be 20 alphanumeric characters or fewer. For example, mc2.
The name can contain alphanumeric characters, periods (.), and hyphens (-). The name must start with an alphanumeric character. This field cannot be empty.
Together, these Hostname Prefix and Domain Name fields are used when host names are generated for components in the system.
For example, a value of mc2 as the system-level host name prefix and us.example.com as the domain name results in the following host names generated for components in the system:
mc2-n1-ilom.us.example.com for the Oracle ILOM host name for the service processor in the first compute node
mc2-n1.us.example.com for the host name for the first compute node
mc2-n2-ilom.us.example.com for the Oracle ILOM host name for the service processor in the second compute node
mc2-n2.us.example.com for the host name for the second compute node
And so on.
Ideally, the management network should be on a separate subnet from the client network, but they can be on the same subnet, if necessary.
The configuration fields for the management network is displayed.
The two management network IP addresses do not have to be consecutive, but they should be on a separate subnet from the client network IP addresses.
For example, 10.129.105.1.
For example, 24.
Use this table to find the CIDR equivalent of your subnet mask.
|
At least one DNS server IP address must be provided. The entries for the DNS servers can be the same, or they can be different, from the entries for the DNS servers that you will provide in the Management Network tab.
At least one NTP server IP address must be provided. The entries for the NTP servers can be the same, or they can be different, from the entries for the NTP servers that you will provide in the Management Network tab.
If you do not want to set up a VLAN configuration on the management network, leave the two VLAN fields blank. Go to Provide Client Network Configuration Information.
If you want to set up a VLAN configuration on the management network, determine if you want to set up a tagged VLAN configuration or an untagged (port-based) VLAN configuration.
VLAN ID — If you want to set up a tagged VLAN configuration on the management network, enter the VLAN tag ID.
Port VLAN ID — If you want to set up an untagged (port-based) VLAN configuration on the management network, enter the port VLAN ID.
Ideally, the client network should be on a separate subnet from the management network, but they can be on the same subnet, if necessary.
The configuration fields for the client access network is displayed.
The Configure IP Allocation window appears.
Information that you enter into this tool will assign IP addresses for the client access network. The first twelve IP addresses will be assigned to components at the system level (for example, for the two compute nodes and the kernel zone), and the remaining IP addresses will be used for the database and application virtual machines that you create later on.
Starting IP address — The starting IP address for the IP addresses assigned to the client access network.
IP Address Pool Size — The total number of IP addresses that you need for the client access network. Beginning with the starting IP address you entered above, this number represents the number of consecutive IP addresses that will be available for the system-level components, such as compute nodes, and the client access network when creating database or application virtual machines and groups.
You need at least twelve IP addresses for the client access network for the system-level components. The additional number of IP addresses that you need for virtual machines and groups varies, depending on the number of virtual machines and groups you create. However, the maximum number of IP addresses that you need for virtual machines and groups is typically around 45.
The starting IP and IP address pool size information is populated into the table on this page.
You can add additional sets of IP addresses for the client access network by entering additional starting IP addresses and IP pool size information in those fields, and clicking the Add button for each set. Each set of new starting IP addresses and IP address pool size is populated into the table each time.
To delete a set of IP addresses from the list, select that set of address and click Delete.
You can access this window again from the main Initial Configuration tool window. However, once you have completed the Initial Configuration tool process and you have generated the IP addresses, the only way to change the IP address pool information is to completely rerun these procedures again.
The Configure IP Allocation window disappears, and the IP address information is populated with the information that you entered in the Configure IP Allocation window.
If you provided information for more than one set of IP addresses in the Configure IP Allocation window, then the IP address information will reflect everything that you entered in the Configure IP Allocation window. For example, if you entered information for two sets of IP addresses, and entered 25 for the IP pool size for each of those two sets of IP addresses, you would see 50 in the IP Pool Size field.
You can click the Configure IP Allocation button again to view or edit the IP addresses that you entered for the client access network.
For example, 10.129.106.1.
For example, 23. See Step 4 in Provide Management Network Configuration Information for the table to find the CIDR equivalent of your subnet mask.
At least one IP address must be provided, starting with the DNS Server 1 field. The entries for the DNS servers can be the same, or they can be different, from the entries for the DNS servers that you provided in the Management Network tab.
At least one IP address must be provided, starting with the NTP Server 1 field. The entries for the NTP servers can be the same, or they can be different, from the entries for the NTP servers that you provided in the Management Network tab.
Options are IPMP (IP network multipathing) or LACP (link aggregation control protocol).
If you select LACP, complete the following fields:
Load Balancing Policy — The load balancing policy. Options are L4, L2, or L3.
Configured LACP Mode — The configured LACP mode. Options are:
Active — Enables LACP unconditionally.
Passive — Enables LACP only when an LACP device is detected.
If you do not want to set up a VLAN configuration on the client access network, leave the two VLAN fields blank. Go to Step 14.
If you want to set up a VLAN configuration on the client access network, determine if you want to set up a tagged VLAN configuration or an untagged (port-based) VLAN configuration.
VLAN ID — If you want to set up a tagged VLAN configuration on the client access network, enter the VLAN tag ID.
Port VLAN ID — If you want to set up an untagged (port-based) VLAN configuration, enter the port VLAN ID.
Options are:
Copper — Choose this option if you are connecting to the client access network through the NET 2 and NET 3 ports, using Category 6/6E (RJ45) Ethernet cabling.
Fiber — Choose this option if you are connecting to the client access network through the 10GbE NIC, using either of the these two cables:
QSFP to 4x SFP copper splitter cable
MPO to 4x LC duplex fiber optic splitter cable
See 10GbE Client Access Network Connections for more information.
Time Zone — Time zone where MiniCluster will be installed. For example, America/Los_Angeles.
Storage Array No. — The number of storage arrays that you are connecting as part of the initial installation. Options are 1 or 2.
Security Profile — Sets the security profile at the system level and for the global zone. Options are:
CIS Equivalent — Satisfies requirements comparable and equivalent to benchmarks set forth by Center for Internet Security (CIS).
PCI DSS — Complies with the Payment Card Industry Data Security Standard (PCI DSS) standard defined by the Payment Card Industry Security Standards Council.
STIG — Satisfies the organizations requiring security controls and compliance with Security Technical Implementation Guides for Oracle Solaris 11 published by the United States Defense Information Systems Agency.
Review — Begins the review process to verify that all the information entered in the tool is valid. Go to Step 2.
Reset — Clears all the fields in the tool.
Exit — Exits out of the tool.
A screen appears with a summary of the information that you entered, including the IP address and host name mapping for the management and client access networks.
The IP address information that you provided in the IP Allocation pane is displayed.
The first 12 IP addresses, which have hostnames provided automatically through the tool, are for the management network (2 IP addresses) and client access network (10 IP addresses) for the system-level components. Enter all 12 of these system-level IP address and host names into DNS before proceeding. These 12 IP addresses are automatically used for these system-level components:
On the management network, Oracle ILOM for the service processors (SPs) in compute nodes 1 and 2 (two IP addresses and host names)
On the client access network:
Host names for compute nodes 1 and 2 (two IP addresses and host names)
Host names for kernel zones on compute nodes 1 and 2 (two IP addresses and host names)
Oracle RAC VIP for kernel zones on compute nodes 1 and 2 (two IP addresses and host names)
NFS VIP (one IP address and host name)
SCAN IP addresses for system-level Oracle RAC (three IP addresses and host names)
The remaining unassigned IP addresses on the client access network will be used later on when you create virtual machines.
The next step verifies that the IP Hostname Mapping information was entered into DNS correctly and assumes that you are connected to the same network where MiniCluster will be installed.
If you are running the Initial Configuration tool on a system that is on the same network where MiniCluster will be installed, go to Step 5.
If you are not on the same network where MiniCluster will be installed, you can continue with these instructions at this time without verifying that the information was entered into DNS correctly. However, you must return to these instructions later on, when you are able to run the Initial Configuration tool on the same network where MiniCluster will be installed, and verify the information prior to setting up MiniCluster.
If you are postponing the DNS check until a later date, continue to Step 7 to generate the necessary configuration files, including the userinputs.txt file, and continue with the remaining preliminary configuration tasks. At a later date, when you are on the same network where MiniCluster will be installed (but prior to receiving your MiniCluster), click the Import Configuration File button described in Provide General Configuration Information to import the userinputs.txt that you generated, then repeat these instructions from this point to use the Check IP button to verify the DNS information before setting up your MiniCluster.
The tool checks DNS to verify you entered the information into DNS properly. A progress bar appears at the bottom of the screen, providing status for this check.
If you see matched/unreachable in the Status field for all of the system-level fields, then you entered the system-level IP addresses and host names into DNS properly. Go to Step 7.
If you see unmatched/unreachable in the Status field for any of the system-level fields, then there was an issue with the DNS entry. Either verify the entries in DNS, or click the Back button to go to the previous screen to correct the IP addresses. Then repeat this step until all the system-level IP addresses and host names are shown as matched/unreachable in the Status field.
Do not proceed with these procedures until you see matched/unreachable in the Status field for all of the system-level fields.
This generates the necessary configuration files.
The tool generates the userinputs.txt and omcips.txt files, which you need to complete the initial configuration procedure. The files are copied into the same directory where you ran the tool. Note this location for future use.
In this procedure, you are downloading the MiniCluster component bundle, which is contained in a series of patch zip files. You are only downloading these patch zip files at this point, and you will move the MiniCluster component bundle files to the compute nodes later in the overall installation process.
Go to the My Oracle Support (MOS) site:
and click on the Sign In button to log in to the site.
Enter 2153282.1 in the search field in the upper right corner of the page, or in the search field beneath the Enter search terms text lower on the page, and locate the MiniCluster MOS note (Oracle MiniCluster S7-2 Software Download Center).
Click on the Latest Release link at the top of the MOS note, or on the MiniCluster Component Bundle link beneath the Latest Release link, to go to the section in the MOS note with the latest version of the MiniCluster component bundle.
The MiniCluster component bundle is contained within a patchset. Clicking on the patch ID brings you to the download page for this particular patchset.
Download the patch zip files onto any system, such as a laptop. Note that the information in the Platform or Language field on the patch page refers to the OS that runs on the MiniCluster itself, not the OS for the system where you will be downloading the patch zip files. You can download the patch zip files for the MiniCluster component bundle onto any system that runs the Windows, Solaris or Linux operating systems.
A set of TAR files are created.
At this point in the process, you have downloaded and extracted the necessary MiniCluster component bundle files onto your system. You will move the MiniCluster component bundle files to the compute nodes later in the overall installation process.
See Connecting Compute Node Interconnects and Storage Arrays.
|
|
|
|
|
Make the following connections for both compute nodes (compute node 1 and 2).
|
Make one of these connections to the client access network, depending on the type of cabling that you want to use:
QSFP to 4x SFP+ splitter cable — Copper cabling through the 10GbE NIC. This cable has a single connector at one end and is split into four connectors at the other end, though you will only use two of these four connectors. Additional transceivers are not needed for this cable.
MPO to 4x LC duplex splitter cable — Fiber optic cabling through the 10GbE NIC. This cable has a single connector at one end and is split into four connectors at the other end, though you will only use two of these four connectors. Additional transceivers are needed for this cable, both for the 10GbE NICs in the compute nodes and for the 10GbE switch. Order and install these transceivers before proceeding with these instructions.
CAT6 cable — Category 6/6E (RJ45) Ethernet cabling using NET 2 and NET 3 ports.
Make the same connections for both compute nodes (compute node 1 and 2).
|
Connect a terminal device to the SER MGT port only on the first compute node (compute node 1).
|
Note the following:
When connecting a DB-9 cable, use an adapter to perform the crossovers given for each connector.
Configure a terminal or terminal emulator with these settings:
9600 baud
8 bits
No parity
1 Stop bit
No handshake
A null modem configuration is needed, meaning the transmit and receive signals are reversed (crossed over) for DTE to DTE communications. You can use the supplied RJ-45 crossover adapters with a standard RJ-45 cable to achieve the null modem configuration.
Caution - Do not attach power cords to the power supplies on the compute nodes until you have connected the compute nodes to a serial terminal or a terminal emulator (PC or workstation). The compute nodes go into Standby mode and Oracle ILOM on the SP initializes as soon as power cables connect the power supplies to an external power source. System messages might be lost after 60 seconds if a terminal or terminal emulator is not connected to the SER MGT ports before power is applied. |
Provide a suitable power source with electrical overload protection to meet the power supply input voltage range of 100 to 240 VAC, 50 to 60 Hz. The storage arrays are compatible with 100 to 120 VAC or 200 to 240 VAC sources. The power source must not be overloaded by the total number of storage arrays in the rack.
Ensure that the power source provides a reliable earth connection for each storage array and the rack.
Ensure that the power source is easily accessible because the power cord is the main disconnect device for the storage array.
When the power cords are connected, the SP initializes and the power supply LEDs illuminate. After a few minutes, the SP login prompt is displayed on the terminal device. At this time, the host is not initialized or powered on.
Powering on can take several minutes.
See SER MGT Connection.
The server is provided with an Administrator account (root) with an initial password (welcome1) to enable first-time login and access to Oracle ILOM. To ensure a secure environment, you must change the password as soon as possible after your initial login to Oracle ILOM. For instructions, refer to Change the Default Oracle ILOM root Passwords in the Oracle MiniCluster S7-2 Security Guide.
If you find this default Administrator account has already been changed, contact your system administrator to obtain an Oracle ILOM user account with Administrator privileges.
login: root Password: ******** . . . ->
For more information about administration tasks such as changing passwords, adding accounts, and setting account privileges, refer to the Oracle ILOM documentation.
-> start /System Are you sure you want to start /System (y/n)? y
The initialization might take several minutes to complete. The compute nodes are completely powered on when the OK LED at the front of the system is lit a steady green.
To cancel the initialization, press the #. (Hash+Dot) keys to return to the Oracle ILOM prompt. Then type: stop /System
When you first get the MiniCluster, the Oracle Solaris OS is preinstalled on both compute nodes. Once you boot up both compute nodes, you then must go through the MiniCluster-specific initial installation procedures.
The mcinstall user is set up at Oracle before the MiniCluster is shipped to your site. The mcinstall user is given the main system administrator role for MiniCluster, similar to the traditional root user role. Only the mcinstall user can go through the initial installation and administration procedures.
Part of the initial installation process uses the 10GbE private network to reassign the static IP address on compute node 2. Do not proceed with these instructions if you have not completed the 10GbE private network cabling procedure. See 10GbE Client Access Network Connections.
See Power On the Storage Array and Power On the Compute Nodes for the First Time.
See SER MGT Connection. Log in as root with the initial password (see Power On the Compute Nodes for the First Time), but without the domain name.
For example, if you used mc2-n1-ilom.us.example.com for the DNS entry, enter this for this command:
-> set /SP hostname=mc2-n1-ilom
-> set /SP/network pendingipdiscovery=static Set 'pendingipdiscovery' to 'static'
-> set /SP/network pendingipaddress=service-processor-IPaddr Set 'pendingipaddress' to 'service-processor-IPaddr'
where service-processor-IPaddr is the Oracle ILOM IP address for the SP on compute node 1 that you entered into DNS in Performing Preliminary Tasks.
-> set /SP/network pendingipgateway=gateway-IPaddr Set 'pendingipgateway' to 'gateway-IPaddr'
where gateway-IPaddr is the gateway that you entered in the Initial Configuration tool or in the table in Performing Preliminary Tasks.
-> set /SP/network pendingipnetmask=netmask Set 'pendingipnetmask' to 'netmask'
where netmask is the netmask (subnet mask) that you entered in the Initial Configuration tool or in the table in Performing Preliminary Tasks. The information that you provided for the subnet mask was in CIDR format. For example, if you used the CIDR format of 22 for the subnet mask, use 255.255.252.0 for this command.
The code example shows parameters that have been set to convert an SP from a DHCP configuration to a static configuration.
-> show /SP/network -display properties /SP/network Properties: commitpending = (Cannot show property) dhcp_server_ip = none ipaddress = xxx.xxx.xxx.xxx ipdiscovery = dhcp ipgateway = xxx.xxx.xxx.xxx ipnetmask = 255.255.xxx.0 macaddress = 00:21:28:6F:A7:BB managementport = /SYS/MB/SP/NETMGMT outofbandmacaddress = 00:21:28:6F:A7:BB pendingipaddress = xxx.xxx.xxx.xxx pendingipdiscovery = static pendingipgateway = xxx.xxx.xxx.xxx pendingipnetmask = 255.255.255.0 pendingmanagementport = /SYS/MB/SP/NETMGMT sidebandmacaddress = 00:21:F8:6F:A7:BA state = enabled
set /SP/network commitpending=true Set 'commitpending' to 'true'
The NET MGT port is now accessible.
Use the settings that you provided in Assign a Static IP Address to the NET MGT Port. For example, connect to the Oracle ILOM on the SP on compute node 1 by using a terminal emulator and typing:
# ssh root@ILOM-IPaddress
where ILOM-IPaddress is the Oracle ILOM IP address that you assigned to the service processor on the first compute node in Assign a Static IP Address to the NET MGT Port.
start /HOST/console
Type y when you see the question Are you sure you want to start /HOST/console (y/n).
The userinputs.txt or omcips.txt configuration files were generated at the end of Performing Preliminary Tasks.
compute-node-1% installmc --init Enter Temporary IP addresses : Enter Netmask in CIDR form (valid range: 8-28) : Enter Default Gateway Address : Type of Cable Used to Connect Network Ports with the 10 GbE Switch: Copper/Fiber :
where:
Temporary IP address is the IP address for compute node 1 that you entered into DNS in Performing Preliminary Tasks.
Netmask in CIDR form is the netmask (subnet mask) that you entered in the Initial Configuration Tool in Performing Preliminary Tasks. For example, 23.
Default gateway address is the gateway that you entered in the Initial Configuration Tool in Performing Preliminary Tasks.
Type of cable that you used to connect the MiniCluster to the 10GbE client access network (copper or fiber). See 10GbE Client Access Network Connections for more information.
After you enter all the necessary information, after 15 or 20 seconds, an Input Summary screen appears.
In the Do you want to change the inputs? line, type N if all the information is correct, or Y if you need to redo any of the information that you entered.
This screen appears:
----------------------------------------------------------------------------------- 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 offline tool. Then, run installmc --deploy to continue with Firstnet setup -----------------------------------------------------------------------------------
remote-system# scp userinputs.txt omcips.txt mcinstall@ipaddress:/var/opt/oracle.minicluster/store
where ipaddress is the temporary IP address that you entered in Step 1.
If you use a tool such as WinSCP to transfer the two configuration files to compute node 1, use the temporary IP address that you entered in Step 1, and log in as mcinstall, with the initial password (see Power On the Compute Nodes for the First Time).
compute-node-1% installmc --deploy
The installmc window appears.
If you copied the userinputs.txt and omcips.txt configuration files to the /var/opt/oracle.minicluster/store directory on compute node 1, then the initial system configuration steps are performed automatically for you. The information that you entered earlier is displayed.
If you want to use the existing configuration information, type Y. Go to Step 3.
If you do not want to use that configuration information, type N. You will be prompted to enter the information manually.
If you did not copy the two configuration files to the correct directory on compute node 1, then this message appears:
[INFO ] Configuring Firstnet.. [INFO ] userinputs.txt does not exist in /var/opt/oracle.minicluster/store [INFO ] omcips.txt does not exist in /var/opt/oracle.minicluster/store Did not find the userinputs.txt or omcips.txt files in /var/opt/oracle.minicluster/store. Do you wish to continue and generate the data now ? (Y/N)(N):
Type Y to continue the initial system configuration process, and type the necessary information at the appropriate prompts.
Enter Unique Prefix for this MiniCluster : Enter Netmask in CIDR form (valid range: 8-28) : Enter First IP address in IP addresses range 1 : Enter Count of IP addresses reserved for range 1 : Do you want to input more IP addresses range? Enter Y/N (Y): Enter Default Gateway Address : Enter Domain Name : Enter Comma Separated List of IP Addresses of DNS Servers : Enter Comma Separated List of NTP Servers : [ILOM] Enter Netmask in CIDR form (valid range: 8-31) for ILOM : [ILOM] Enter ILOM IP address of first compute node : [ILOM] Enter ILOM IP address of second compute node : [ILOM] Enter Default Gateway Address for ILOM : [ILOM] Enter Comma Separated List of IP Addresses of DNS Servers for ILOM : [ILOM] Enter Comma Separated List of NTP Servers for ILOM : Type of Cable Used to Connect Network Ports with the 10 GbE Switch: Copper/Fiber : Enter CAN HA type (IPMP/AGGR) : Enter your location 1 : Enter your location 2 : Enable PCI DSS Compliance: Yes/No (No): Enter Security Keystore Type [Choose: pkcs11] : VLAN ID is optional. Do you want to input this value? Enter Y/N (N): Port VLAN ID is optional. Do you want to input this value? Enter Y/N (N): [ILOM] VLAN ID for ILOM is optional. Do you want to input this value? Enter Y/N (N): [ILOM] Port VLAN ID for ILOM is optional. Do you want to input this value? Enter Y/N (N):
An input summary page is generated. Type Y if you are satisfied with the information displayed or N if you want to change the information displayed.
---------- Input Summary ---------- MACHINE_TYPE = S7-2 OMC_UPREFIX = mc2 FIRST_PUBLIC_IP = xx.xxx.xx.xx IPCOUNT = 50 GATEWAY = xx.xxx.xx.xx NETMASK_CIDR = 22 DOMAIN_NAME = us.example.com DNS_SERVER_LIST = xx.xxx.xx.xx,yy.yyy.yy.yy NTP_SERVER_LIST = xx.xxx.xx.xx CAN_CABLE_TYPE = COPPER FIRST_ILOM_IP = xx.xxx.xx.xx SECOND_ILOM_IP = xx.xxx.xx.xx ILOM_GATEWAY = xx.xxx.xx.xx ILOM_NETMASK_CIDR = 24 ILOM_DNS_SERVER_LIST = xx.xxx.xx.xx,yy.yyy.yy.yy ILOM_NTP_SERVER_LIST = xx.xxx.xx.xx CAN_HA = YES CAN_HA_TYPE = IPMP SS_DISK_COUNT = 6 TZ = America/Los_Angeles PCI_DSS_COMPL = NO KEYSTORE_TYPE = pkcs11 Do you want to change the inputs? Enter Y/N (N):
The installmc --deploy command goes through these processes:
|
Explorer output enables Oracle's engineers to perform assessments of the system by applying the output against knowledge-based rules engine. For more information on Explorer, refer to the following documents:
Chapter 2, "Oracle Explorer Data Collector," in Services Tools Bundle (STB) User's Guide
For the Explorer questions at Step 4 in the MiniCluster initial system configuration process:
Provide the standard information for your company at the appropriate prompts.
Press Return to accept the default entries at these prompts:
Absolute path of the Explorer output top location? [/var/explorer/output]
Select the Explorer default transport upload method from this list:
1) Using Diagnostic Assistant (DA)
2) Other transport
3) None
[Using Diagnostic Assistant (DA)]
Do you want to configure Diagnostic Assistant to save credentials (y/n)? [y]
Enter a dash (-) at the Solaris zones prompt:
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 []:
Note that you will not be able to schedule a cron job for Explorer, as shown in the message that appears as part of Step 4 in the initial system configuration process:
[INFO ] Please do not schedule any cron job to run the Explorer, as cron entries will be removed and not run on the MiniCluster.
The process has completed successfully when you see the message Configuring Firstnet Completed.
Successful completion yields output similar to this:
----------------------------------------------------------------------------------- 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://compute-node1-hostname/MCMU -OR- https://compute-node1-IP-address/MCMU Administrator login ID: mcinstall. 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 -----------------------------------------------------------------------------------
where the compute-node1-hostname and compute-node1-IP-address is the same information in the IP Hostname Mapping screen in Performing Preliminary Tasks.
In this procedure, you are transferring the MiniCluster component bundle files that you downloaded in Download the MiniCluster Component Bundle to both MiniCluster compute nodes and installing those component bundle files.
From a terminal window, type:
remote-system# scp path-on-remote-system/mc-*-sfw.tar.a* mcinstall@ipaddress:/var/tmp
where ipaddress is the IP address for compute node 1 that was provided in the output screen after installmc --deploy was successfully completed. You can also find the IP address for compute node 1 in the omcips.txt file that was generated as part of the process in Initial Configuration Tasks.
If you use a tool such as WinSCP to transfer the component bundle files to compute node 1, use the IP address for compute node 1, and log in as mcinstall, with the initial password (see Power On the Compute Nodes for the First Time).
compute-node-1% cat component-bundle.tar.a? | gtar -x -C /var/opt/oracle.minicluster/ -f -
The a? portion of the command is essentially a wild card entry, encompassing TAR files that end with .aa, .ab, and so on.
For example, if the component bundle packages are named mc-1.1.13-sfw.tar.aa to mc-1.1.13-sfw.tar.ah, type:
compute-node-1% cat mc-1.1.13-sfw.tar.a? | gtar -x -C /var/opt/oracle.minicluster/ -f -
# ssh mcinstall@compute-node2-IP-address
where compute-node2-IP-address is the IP address on the client access network for compute node 2 that you entered into DNS in Initial Configuration Tasks. You can also find the IP address for compute node 2 in the omcips.txt file that was generated as part of the process in Initial Configuration Tasks.
You can copy the component bundle files from either the remote system or from compute node 1 to the /var/tmp directory on compute node 2.
Once the installmc process has completed, both compute nodes should be reachable directly from the client access network. Disconnect from the Oracle ILOM connection through the NET MGT port.
Open a web browser and type:
https://compute-node1-hostname/MCMU/
where the compute-node1-hostname was provided in the output when installmc was completed. This compute node 1 client access network hostname was also in Performing Preliminary Tasks. For example:
https://mc2-n1.us.example.com/MCMU/
The login window appears.
The MiniCluster Install Administrator Account Registration window appears.
Set up two accounts as part of this process:
Install Administrator — A MiniCluster-specific user account. The Install Administrator has full administrative privileges, and can perform all BUI and CLI operations, and approve new users.
Supervisor — An existing user account outside of the MiniCluster. The Supervisor role is used to provide a second layer in the approval process (for example, if you want to include your company's Human Resources department in the approval process for any new user being created).
Whenever you create a new user account, two users approve that new user account: the Install Administrator and the supervisor. Both of those users get the approval email, and both need to approve any new user.
The Supervisor role is outside of the MiniCluster and is used to provide a second layer in the approval process.
You see mail similar to this, where you are asked to approve the new Install Administrator account that you just created:
Dear MiniCluster Administrator, A new user has been created and is awaiting your action. Please approve or deny registration of user Joe Smith, as Primary Admin by following the link provided: https://compute-node1-hostname/MCMU/admin_approve/mcinstall/749cee7610a4e594ee867b243a22cae537fe77b81b92c4aad33d8befbd8e8611/approve/
For example, using the example output, you would copy this approval link URL string:
https://compute-node1-hostname/MCMU/admin_approve/mcinstall/749cee7610a4e594ee867b243a22cae537fe77b81b92c4aad33d8befbd8e8611/approve/
The approval screen appears.
A screen appears, confirming that the Install Administrator account has been approved.
The login window appears.
The MiniCluster Install and Administrator Account password reset window appears.
Note these password restrictions:
Minimum of 14 characters
Cannot match the previous 10 passwords
Must differ from the previous password by at least 3 characters
Must contain a minimum of:
1 digit
1 uppercase letter
2 alphabetic characters
1 non-alphabetic character
Username and password cannot be identical
A window appears, prompting you to change the password for the Supervisor account.
You entered information on the Supervisor account in the Account Registration page earlier, where you provided information such as the Supervisor username, and the full name and email address for the person or group who will be using the Supervisor account. Change the password for the Supervisor account using these instructions.
Enter the username that you provided in the Account Registration page for the Supervisor account and use the initial password that was used with other accounts (see Power On the Compute Nodes for the First Time).
The password reset page for the Supervisor account appears.
Note these password restrictions:
Minimum of 14 characters
Cannot match the previous 10 passwords
Must differ from the previous password by at least 3 characters
Must contain a minimum of:
1 digit
1 uppercase letter
2 alphabetic characters
1 non-alphabetic character
Username and password cannot be identical
The MCMU login page appears.
Username — mcinstall
Password — The password for the mcinstall user that you set in Finish Setting Up the Install Administrator Account.
The Welcome to MiniCluster Configuration Utility page appears.
The System Setup page appears.
Certain steps in the remaining initial configuration process will fail if you have not installed the MiniCluster component bundle on both compute nodes. See Transfer and Install MiniCluster Component Bundle for more information.
As part of the process in Perform Initial Configuration, you went through steps 1 through 10 using the installmc tool. So those steps should be shown as Finished in the Status column.
Complete the remaining steps in this System Setup page, either by clicking the Run button for each step, or by clicking the Run All Steps button. Clicking the Run All Steps button will begin the process after the last completed step (in this case, after Step 10). It normally takes about 3 to 4 hours to run all of the remaining steps in this page. Click Hide Detail to provide less detail or Show Detail to provide more detail for all of the steps that are run on this screen.
The Create Profile page appears.
You are provided with a walk-through on creating virtual machine groups. If you decide not to create virtual machine groups as part of the initial configuration, click on the Skip button in any screen until you get to the Home page in the MCMU BUI. You can create virtual machine groups manually at any point later on.
Refer to these documents for more information:
Oracle MiniCluster S7-2 Installation Guide — Provides detailed system installation and configuration information, including how to create VM groups as part of the initial installation walk-through.
Oracle MiniCluster S7-2 Administration Guide — Provides instructions for creating database or application VM groups.
These are important post-installation activities:
Configure the password for the Oracle Engineered Systems Hardware Manager. Refer to
For instructions refer to Configure the Oracle Engineered System Hardware Manager Password in Oracle MiniCluster S7-2 Installation Guide
Configure the mctuner notification email address so that, If the tuning assistant detects any issues, it sends email notifications to the email address that is configured for the tuning assistant.
For instructions, refer to Configure the mctuner Notification Email Address (CLI) in Oracle MiniCluster S7-2 Administration Guide