Oracle MiniCluster MC-S7: How to factory reset the entire system

Asset ID:	1-71-2151620.1
Update Date:	2018-01-09
Keywords:

Solution Type Technical Instruction Sure

Solution 2151620.1 : Oracle MiniCluster MC-S7: How to factory reset the entire system

Applies to:

MiniCluster S7-2 Hardware - Version All Versions to All Versions [Release All Releases]
Oracle Solaris on SPARC (64-bit)
Oracle MiniCluster S7-2 is a customer self install-able system and as such a factory reset procedure is required.

Goal

Perform a factory reset of the system.

Note: the Oracle MiniCluster S7-2 EIS document has an appendix covering the same topic.

Solution

1. Prerequisites
2. General Flow
3. Setting up re-imaging via ISO/ILOM storage redirection
4. Installing the Oracle Minicluster S7-2 ISO
5. Installing Core Components
6. Install SFW components and reboot
7. Resetting ILOM password

2017-04-25 Installing MC-S7 software components with AI server can be done by setting up a laptop or other server. There is some internal information on this in item # 8 at the end of this document. I'll add some more details on this later as necessary.

Oracle MiniCluster S7-2 Factory Reset Instructions

1. Prerequisites

In case a given MiniCluster S7-2 requires a reset back to factory default image one will also need to refer to the Oracle MiniCluster S7-2 Software Download Center MOS Document ID 2153282.1 in order to download the correct factory reset ISO and necessary patches and bundles.

Note that one will need to download all of the following patches for the desired release:

MiniCluster Initial Configuration Tool
MiniCluster Core Software
MiniCluster Component Bundle
MiniCluster Patch Bundle
MiniCluster Factory Reset ISO

To locate the ISO image file simply download and unpack the required MiniCluster Factory Reset ISO patch bundle and look for a file with the naming convention of Oracle_Minicluster_AI_SPARC-MM-DD-YY-VV.iso from within patch bundle (where VV is latest version#)

Extract all components from the patch and store the ISO image on an external NFS server that can be reached / resolved via the management network and share it. This share will be used to boot the ISO image for the installation as well as a staging area for the rest of the installation.

If the "EEPROM Password" has been enabled either via MCMU BUI "System Security" -> "Security" Tab or via the CLI "mcmu security -e" setting, disable it before doing an ISO reset. If not, you will be prompted for the EEPROM password during the reset procedure and after setup is complete, MCMU will incorrectly show eeprom password as disabled.

During MiniCluster MC-S7 factory reset, all passwords are reset to 'default' automatically with the exception of root user at service processor ILOM. During re-image one is prompted for the password and some users do not realize that the ILOM password did *not* get reset, and so the re-image fails. One must either reset the password to default before the re-image, or else use the correct password when prompted. This process will need to be done on both nodes of the cluster. Should a need arise to reset the ILOM user account info, please refer to Oracle MiniCluster MC-S7: Example of how to manually reset ILOM root password (Doc ID 2254209.1).

Note that how to create and share NFS file systems on an NFS server is beyond the scope of this document.

2. General flow

Recent improvements in the MC-S7 re-image/install process have simplified matters. In general the flow is for both nodes as follows:

MC-S7 ISO (As of release 1.1.18.2 and until further notice all shall use the same ISO)
Install latests MC-S7 core image
Install latests SFW components
Reboot node1, then when it is completed the process, reboot node 2

3. Setting up re-imaging via ISO/ILOM redirection

Log into the ILOM as user root.
Make sure that the kvms service is enabled:

->show /SP/services/kvms/ servicestate
/SP/services/kvms
Properties:
servicestate = enabled

Set the host_storage_device to “remote”:

-> set /SP/services/kvms/host_storage_device mode=remote
Set 'mode' to 'remote'
-> show /SP/services/kvms/host_storage_device mode
/SP/services/kvms/host_storage_device
Properties:
mode = remote

Setup NFS boot via KVMS. The server_URI used here is just an example. The file system '/root/mincluster/Factory' is the share name from the NFS server

-> cd /SP/services/kvms/host_storage_device/remote
/SP/services/kvms/host_storage_device/remote
-> ls
/SP/services/kvms/host_storage_device/remote
Targets:

Properties:
password = (none)
server_URI = (none)
username = (none)

Commands:
cd
show

-> set server_URI=nfs://1.2.3.57:/root/minicluster/Factory/Oracle_Minicluster_AI_SPARC-10-13-16-59.iso

Note: the above steps can be performed from BUI as well. See the MC-S7 Administrator's guide or the internal only Enterprise Installation Standards EIS document for MC-S7 for more details.

When using ILOM storage redirection after the installation has completed go back to the Redirection Screen on the Windows / Linux system:

In the top bad select the KVMS pull-down and then Storage
If the option is greyed out, click on "Take Full Control..." and try again.
Disconnect the storage.
In the pop-up select "Disconnect" and "OK".
Then exit the KVMS screen

4. Installing the Oracle Minicluster S7-2 ISO

It is suggested to have four windows open with SSH connections, two per physical node ILOM (i.e. two windows for node1 and two windows for node2), with one window each for host console and one for ILOM interaction.

From the SP, set auto-boot to false:

-> set /HOST/bootmode script="setenv auto-boot? false"

Reset the host:

-> reset /SYS

From another window connect directly to the SP via SSH (user root) and bring the domain to the OBP prompt.

-> start -f /HOST/console

Boot off the rcdom device:

NOTE: If you are resetting to SRU19 or below, use the following command. If you are using SRU19.5 ISO, please use the 2nd form of the boot comand below.

ISO version SRU12.5:

ok> boot rcdrom - install aimanifest=/var/tmp/mc-default-iso.xml profile=/var/tmp/mc-n1-profile.xml

ISO version SRU19.5 and above:

ok> boot rcdrom - install aimanifest=/.cdrom/auto_install/mc-default-iso.xml profile=/.cdrom/auto_install/mc-n1-profile.xml

The system will install (takes 2 – 3 hours). All warnings should be ignored.
When you see the following do NOT try to login:

Solaris console login:

Ignore the following warnings:

WARNING: Can not verify signature on unsupported binary format
WARNING: Signature verification of boot-archive bootblk failed

The system will reboot when the installation is complete.
If you receive the following error

“Can't open disk label package”
or
“Can't open boot device”

Then reset the SP and try again:

-> reset /SP

Important Note

After installation is finished and if ILOM storage redirection was used do not forget to execute these last steps also documented in Section 3 above:

When the installation has completed go back to the Redirection Screen on the Windows / Linux system:

In the top bad select the KVMS pull-down and then Storage
If the option is greyed out, click on "Take Full Control..." and try again.
Disconnect the storage.
In the pop-up select "Disconnect" and "OK".
Then exit the KVMS screen

At ILOM set the host_storage_device for the each host to the default value:

-> set /SP/services/kvms/host_storage_device mode=miniroot

Set 'mode' to 'miniroot'

-> show /SP/services/kvms/host_storage_device mode status
/SP/services/kvms/host_storage_device
   Properties:
      mode = miniroot
      status = operational
      Restore auto-boot to true:

Set bootmode script to set auto-boot? to true:

->set /HOST/bootmode script="setenv auto-boot? true"

Now you are ready to install the core bundle.

5. Installing Core Components

Assuming we are still logged into the ILOM, start the console on each server:

-> start /HOST/console

Assign temporary IP addresses required to transfer files. Use your IP addresses to replace 1.2.3.4 below

# ipadm create-ip -t net2
# ipadm create-addr -t -a 1.2.3.4/24 net2

Add default route if needed

# route add default 1.2.3.1

We assign a temporary IP address on both hosts in order to transfer the core and component files. It is recommended to use the same IP information for each host as will be used in the final customer configuration.
Assumption: The downloaded files that form the core and component bundles have already been concatenated (via tar(1m)) into a single file (e.g mc-1.1.25.4-sfw.tar).
In addition, since sftp/ssh/scp are not enabled for root by default the file /etc/ssh/sshd_config must be modified. Comment out the following line:

#PermitRootLogin no

Allow root on non-console, by editing file /etc/default/login to comment out the following line:

#CONSOLE=/dev/console

Then restart sshd:

#svcadm restart svc:/network/ssh:default

Transfer the single MiniCluster core and component bundles (filenames mc-*.tar.*) to each host into directory /var/tmp
If using a personal laptop be sure to assign it an IP address from the customer’s network.
Transfer MiniCluster core bundle (files named mc-*.tar.*) to each server that will be part of the target MiniCluster
Extract the core bundle as in the following example:

root@mccn:~# cd /var/tmp
root@mccn:/var/tmp# gtar xvf mc-1.1.25.4-core.tar

Complete MCMU bundle installation on each S7-2 server by running

# root@mccn:/var/tmp# cd mc-1.1.25.4/onsite
# root@mccn:/var/tmp/mc-1.1.25.4/onsite#./Install.sh

If the host is accessed from the ILOM, please make sure timeout for ILOM is set to at least 30 minutes before running Install.sh, this is to prevent ILOM disconnecting during running Install.sh

-> show /SP/cli
/SP/cli
Targets:
Properties:
legacy_targets = disabled
prompt = (none)
timeout = 30
Commands:
cd
set
show

If current timeout is less than 30 minutes, set it to 30 minutes or higher value

-> set /SP/cli timeout=30

Install.sh installs MiniCluster software, creates local repo, creates template zones and completes factory setup.
Expected elapsed time: ~20 minutes
Reboot both nodes to simulate system being power-off for delivery to customer.
Console log example of an old 1.1.3 install:

root@mccn1:~/mc-1.1.3/onsite# ./Install.sh
Installing MCMU toolkit.
Boot environment before-mcmu created as snapshot of current BE.
It will be removed when MCMU is installed
Extracting files.
Installing omctoolkit package.
Packages to install: 2
Services to change: 4
Create boot environment: No
Create backup boot environment: No
DOWNLOAD PKGS FILES XFER (MB) SPEED
Completed 2/2 5767/5767 28.4/28.4 10.3M/s
PHASE ITEMS
Installing new actions 6571/6571
Updating package state database Done
Updating package cache 0/0
Updating image state Done
Creating fast lookup database working
Creating fast lookup database Done
Updating package cache 2/2
Creating local repo
Using sol-11_3-repo download.
Uncompressing sol-11_3-repo_1of5.zip...done.
Uncompressing sol-11_3-repo_2of5.zip...done.
Uncompressing sol-11_3-repo_4of5.zip...done.
Uncompressing sol-11_3-repo_5of5.zip...done.
Repository can be found in /repo.
Using sol-11_3_8_3_0-incr-repo download.
IPS repository exists at destination /repo
Current version: 0.175.3.1.0.5.0
Adding packages to existing repository.
Uncompressing sol-11_3_8_3_0-incr-repo_1of3.zip...done.
Uncompressing sol-11_3_8_3_0-incr-repo_2of3.zip...done.
Uncompressing sol-11_3_8_3_0-incr-repo_3of3.zip...done.
Repository can be found in /repo.
Initiating repository rebuild.
Local repository created successfully
Publisher set to /repo
Clean
mcpool 2.17T 190K 2.17T 0% 1.00x ONLINE -
Creating zone appzonetemplate template
/mcpool/appzonetemplate must not be group readable.
/mcpool/appzonetemplate must not be group executable.
/mcpool/appzonetemplate must not be world readable.
/mcpool/appzonetemplate must not be world executable.
changing zonepath permissions to 0700.
Progress being logged to
/var/log/zones/zoneadm.20160506T004155Z.appzonetemplate.install
Image: Preparing at /mcpool/appzonetemplate/root.
Install Log: /system/volatile/install.3028/install_log
AI Manifest: /tmp/manifest.xml.t1aa5f
SC Profile: /usr/share/auto_install/sc_profiles/enable_sci.xml
Zonename: appzonetemplate
Installation: Starting ...
Creating IPS image
Startup linked: 1/1 done
Installing packages from:
solaris
origin:
http://localhost:1008/solaris/bbb612b800c4a05fe489e22179376fa4cb0b1970/omc
origin:
http://localhost:1008/omc/3b27ec6dc20835df755859ff9015985749646692/
DOWNLOAD PKGS FILES XFER (MB) SPEED
Completed 405/405 74503/74503 528.3/528.3 10.1M/s
PHASE ITEMS
Installing new actions 97847/97847
Updating package state database Done
Updating package cache 0/0
Updating image state Done
Creating fast lookup database working \
Creating fast lookup database Done
Updating package cache 2/2
Installation: Succeeded
Note: Man pages can be obtained by installing pkg:/system/manual
done.
Done: Installation completed in 195.937 seconds.
Next Steps: Boot the zone, then log into the zone console (zlogin -C)
to complete the configuration process.
Log saved in non-global zone as
/mcpool/appzonetemplate/root/var/log/zones/zoneadm.20160506T004155Z.appzonetemplate.ins
tall
Creating zone dbzonetemplate template
/mcpool/dbzonetemplate must not be group readable.
/mcpool/dbzonetemplate must not be group executable.
/mcpool/dbzonetemplate must not be world readable.
/mcpool/dbzonetemplate must not be world executable.
changing zonepath permissions to 0700.
Progress being logged to /var/log/zones/zoneadm.20160506T004527Z.dbzonetemplate.install
Image: Preparing at /mcpool/dbzonetemplate/root.
Install Log: /system/volatile/install.4088/install_log
AI Manifest: /tmp/manifest.xml.jraG9h
SC Profile: /usr/share/auto_install/sc_profiles/enable_sci.xml
Zonename: dbzonetemplate
Installation: Starting ...
Creating IPS image
Startup linked: 1/1 done
Installing packages from:
solaris
origin:
http://localhost:1008/solaris/bbb612b800c4a05fe489e22179376fa4cb0b1970/
omc
origin:
http://localhost:1008/omc/3b27ec6dc20835df755859ff9015985749646692/
DOWNLOAD PKGS FILES XFER (MB) SPEED
Completed 255/255 46791/46791 323.5/323.5 10.9M/s
PHASE ITEMS
Installing new actions 63200/63200
Updating package state database Done
Updating package cache 0/0
Updating image state Done
Creating fast lookup database Done
Updating package cache 2/2
Installation: Succeeded
Note: Man pages can be obtained by installing pkg:/system/manual
done.
Done: Installation completed in 126.634 seconds.
Next Steps: Boot the zone, then log into the zone console (zlogin -C)
to complete the configuration process.
Log saved in non-global zone as
/mcpool/dbzonetemplate/root/var/log/zones/zoneadm.20160506T004527Z.dbzonetemplate.insta
ll
Progress being logged to /var/log/zones/zoneadm.20160506T004734Z.acfskz.install
pkg cache: Using /var/pkg/publisher.
Install Log: /system/volatile/install.4600/install_log
AI Manifest: /tmp/zoneadm4338.Bea4Zi/devel-ai-manifest.xml
SC Profile: /var/opt/oracle.minicluster/setup/schema/acfskz-sysconfig.xml
Installation: Starting ...
Creating IPS image
Startup: Retrieving catalog 'solaris' ... Done
Startup: Caching catalogs ... Done
Startup: Refreshing catalog 'omc' ... Done
Startup: Refreshing catalog 'solaris' ... Done
Startup: Caching catalogs ... Done
Installing packages from:
solaris
origin: file:///repo/
omc
origin: file:///var/tmp/omctoolkit.p5p/
Startup: Refreshing catalog 'omc' ... Done
Startup: Refreshing catalog 'solaris' ... Done
Planning: Solver setup ... Done
Planning: Running solver ... Done
Planning: Finding local manifests ... Done
Planning: Fetching manifests: 1/441 0% complete
Planning: Fetching manifests: 441/441 100% complete
Planning: Package planning ... Done
Planning: Merging actions ... Done
Planning: Checking for conflicting actions ... Done
Planning: Consolidating action changes ... Done
Planning: Evaluating mediators ... Done
Planning: Planning completed in 50.44 seconds
The following licenses have been accepted and not displayed.
Please review the licenses for the following packages post-install:
consolidation/osnet/osnet-incorporation
Package licenses may be viewed using the command:
pkg info --license
Download: 0/87010 items 0.0/512.9MB 0% complete
Download: 37647/87010 items 247.8/512.9MB 48% complete (9.7M/s)
Download: Completed 512.91 MB in 8.19 seconds (3.5M/s)
Actions: 1/110681 actions (Installing new actions)
Actions: 22517/110681 actions (Installing new actions)
Actions: 31427/110681 actions (Installing new actions)
Actions: 39240/110681 actions (Installing new actions)
Actions: 47089/110681 actions (Installing new actions)
Actions: 54594/110681 actions (Installing new actions)
Actions: 61662/110681 actions (Installing new actions)
Actions: 69446/110681 actions (Installing new actions)
Actions: 77644/110681 actions (Installing new actions)
Actions: 85378/110681 actions (Installing new actions)
Actions: 93820/110681 actions (Installing new actions)
Actions: 101724/110681 actions (Installing new actions)
Actions: 109058/110681 actions (Installing new actions)
Actions: 109263/110681 actions (Installing new actions)
Actions: Completed 110681 actions in 71.16 seconds.
Done
Installation: Succeeded
Done: Installation completed in 198.584 seconds.
Starting factory setup script. Please review /var/log/omc-factory.log for details
Creating /var/opt/oracle.minicluster/sfw/silentgi ..
Creating /var/opt/oracle.minicluster/sfw/oracle-eshm ..
Creating /var/opt/oracle.minicluster/sfw/oracle-emsi ..
May 5 17:51:11 mccn1 root[5232]: Oracle MiniCluster : factory setup in progress.
May 5 17:51:11 mccn1 root[5232]: [ID 702911 user.alert] Oracle MiniCluster : factory
setup in progress.
Broadcast Message from root (???) on mccn1 Thu May 5 17:51:11...
Oracle MiniCluster v1.0 : Factory Setup
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.. currently in progress.
As part of factory setup, root becomes a role , and
the system may get rebooted at the end of this exercise.
Please connect as 'mcinstall' user after successful factory setup.
Current IP recovery probe time setting
PROTO PROPERTY PERM CURRENT PERSISTENT DEFAULT POSSIBLE
ip _dup_recovery rw 300000 -- 300000 0-3600000
Setting duplicate IP recovery probe time to one second ..
New IP recovery probe time setting
PROTO PROPERTY PERM CURRENT PERSISTENT DEFAULT POSSIBLE
ip _dup_recovery rw 100 100 300000 0-3600000
Creating an aggregated link for interconnect setup ..
[INFO ] Log file path :
mccn1:/var/opt/oracle.minicluster/setup/logs/omc_pvtconfig_v2_050516_175111.log
[INFO ] Setting Aggregate link on Management Interconnect..
[INFO ] Verifying Setting of Aggregate link on Management Interconnect..
[INFO ] Setting Aggregate link on Management Interconnect.. Verified Successfully
[INFO ] Setting Aggregate link on Management Interconnect.. Completed
Creating mcinstall user ..
[INFO ] Log file path :
mccn1:/var/opt/oracle.minicluster/setup/logs/omc_crmcadmuser_v2_050516_175113.log
[INFO ] Creating MiniCluster Administator users ..
[INFO ] Creating Minicluster Administrator profile..
[INFO ] Creating mcadmin role...
[INFO ] Creating mcadm user and assigning mcadmin as a role...
[INFO ] Adding root as a role to mcinstall...
[INFO ] Verifying MiniCluster Administator users ..
[INFO ] Checking if mcadmin(role) , mcadm and mcinstall users exist...
[INFO ] Checking if mcadmin is assigned as a role to mcadm...
[INFO ] Checking if root is assigned as a role to mcinstall...
[INFO ] Creating MiniCluster Administator users .. Verified Successfully
[INFO ] Creating MiniCluster Administator users .. Completed
Creating a system identifier ..
[INFO ] Log file path :
mccn1:/var/opt/oracle.minicluster/setup/logs/omc_sysid_v2_050516_175115.log
[INFO ] Setting the System Identifier..
[INFO ] Verifying the System Identifier..
[INFO ] Setting the System Identifier.. Verified Successfully
[INFO ] Setting the System Identifier.. Completed
Secured by Default (SBD) settings for ILOM ..
[INFO ] Log file path :
mccn1:/var/opt/oracle.minicluster/setup/logs/omc_sbd_ilom_v2_050516_175118.log
[INFO ] Secured by Default Settings..
[INFO ] Verifying Secured by Default Settings..
[INFO ] Secured by Default Settings.. Verified Successfully
[INFO ] Secured by Default Settings.. Completed
Check if multipathing was enabled ..
Running OS command: prtconf -vc /devices/scsi_vhci |grep dev_link.*s2
Output:
dev_link=/dev/dsk/c0t5000CCA02D0FAAD0d0s2
dev_link=/dev/rdsk/c0t5000CCA02D0FAAD0d0s2
dev_link=/dev/dsk/c0t5000CCA02D0FA18Cd0s2
dev_link=/dev/rdsk/c0t5000CCA02D0FA18Cd0s2
dev_link=/dev/dsk/c0t5000CCA02D0FD608d0s2
dev_link=/dev/rdsk/c0t5000CCA02D0FD608d0s2
dev_link=/dev/dsk/c0t5000CCA02D0F9F00d0s2
dev_link=/dev/rdsk/c0t5000CCA02D0F9F00d0s2
dev_link=/dev/dsk/c0t5000CCA02D0FC338d0s2
dev_link=/dev/rdsk/c0t5000CCA02D0FC338d0s2
dev_link=/dev/dsk/c0t5000CCA02D0FA03Cd0s2
dev_link=/dev/rdsk/c0t5000CCA02D0FA03Cd0s2
dev_link=/dev/dsk/c0t5000CCA05351B638d0s2
dev_link=/dev/rdsk/c0t5000CCA05351B638d0s2
dev_link=/dev/dsk/c0t5000CCA04E0E08E4d0s2
dev_link=/dev/rdsk/c0t5000CCA04E0E08E4d0s2
dev_link=/dev/dsk/c0t5000CCA05351AA98d0s2
dev_link=/dev/rdsk/c0t5000CCA05351AA98d0s2
dev_link=/dev/dsk/c0t5000CCA23B109E88d0s2
dev_link=/dev/rdsk/c0t5000CCA23B109E88d0s2
dev_link=/dev/dsk/c0t5000CCA23B10C2E8d0s2
dev_link=/dev/rdsk/c0t5000CCA23B10C2E8d0s2
dev_link=/dev/dsk/c0t5000CCA04E0D3358d0s2
dev_link=/dev/rdsk/c0t5000CCA04E0D3358d0s2
dev_link=/dev/dsk/c0t5000CCA05351B568d0s2
dev_link=/dev/rdsk/c0t5000CCA05351B568d0s2
dev_link=/dev/dsk/c0t5000CCA05351BA80d0s2
dev_link=/dev/rdsk/c0t5000CCA05351BA80d0s2
dev_link=/dev/dsk/c0t5000CCA05351B998d0s2
dev_link=/dev/rdsk/c0t5000CCA05351B998d0s2
dev_link=/dev/dsk/c0t5000CCA05351B4FCd0s2
dev_link=/dev/rdsk/c0t5000CCA05351B4FCd0s2
dev_link=/dev/dsk/c0t5000CCA23B10C8E4d0s2
dev_link=/dev/rdsk/c0t5000CCA23B10C8E4d0s2
dev_link=/dev/dsk/c0t5000CCA05351B9B8d0s2
dev_link=/dev/rdsk/c0t5000CCA05351B9B8d0s2
dev_link=/dev/dsk/c0t5000CCA05351AB84d0s2
dev_link=/dev/rdsk/c0t5000CCA05351AB84d0s2
dev_link=/dev/dsk/c0t5000CCA04E0E002Cd0s2
dev_link=/dev/rdsk/c0t5000CCA04E0E002Cd0s2
dev_link=/dev/dsk/c0t5000CCA23B0FB920d0s2
dev_link=/dev/rdsk/c0t5000CCA23B0FB920d0s2
dev_link=/dev/dsk/c0t5000CCA053558890d0s2
dev_link=/dev/rdsk/c0t5000CCA053558890d0s2
dev_link=/dev/dsk/c0t5000CCA05351B678d0s2
dev_link=/dev/rdsk/c0t5000CCA05351B678d0s2
dev_link=/dev/dsk/c0t5000CCA05351B788d0s2
dev_link=/dev/rdsk/c0t5000CCA05351B788d0s2
dev_link=/dev/dsk/c0t5000CCA04E0D26ECd0s2
dev_link=/dev/rdsk/c0t5000CCA04E0D26ECd0s2
dev_link=/dev/dsk/c0t5000CCA23B108B9Cd0s2
dev_link=/dev/rdsk/c0t5000CCA23B108B9Cd0s2
dev_link=/dev/dsk/c0t5000CCA05351B330d0s2
dev_link=/dev/rdsk/c0t5000CCA05351B330d0s2
dev_link=/dev/dsk/c0t5000CCA23B109C30d0s2
dev_link=/dev/rdsk/c0t5000CCA23B109C30d0s2
dev_link=/dev/dsk/c0t5000CCA05351B3A0d0s2
dev_link=/dev/rdsk/c0t5000CCA05351B3A0d0s2
dev_link=/dev/dsk/c0t5000CCA05351A8ECd0s2
dev_link=/dev/rdsk/c0t5000CCA05351A8ECd0s2
IO multipathing was enabled already.
Destroying BE snapshot that was created right before the factory setup
Notice: Compiled catalog for mccn1 in environment production in 0.05 seconds
Notice: /Stage[main]/Main/Boot_environment[before-mcmu]/ensure: removed
Notice: Finished catalog run in 5.00 seconds
Done.
May 5 17:52:50 mccn1 root[5572]: Oracle MiniCluster factory setup completed
successfully by running omc-factorysetup script.
May 5 17:52:50 mccn1 root[5572]: [ID 702911 user.alert] Oracle MiniCluster factory
setup completed successfully by running omc-factorysetup script.
Broadcast Message from root (???) on mccn1 Thu May 5 17:52:50...
@@ [INFO] Oracle MiniCluster factory setup completed successfully by running omcfactorysetup
script. @@
Done.

6. Install SFW components

After running Install.sh you will also need to copy the sfw components bits to both nodes under /var/tmp.
Here is an example using 1.1.25.4

remote-system# scp mc-1.1.25.4-sfw.tar mcinstall@<ipaddress>:/var/tmp/mc-1.1.25.4-sfw.tar

Then login to each node as user mcinstall and extract the sfw components:

mcinstall@mccn1:/var/home/mcinstall % cd /var/opt/oracle.minicluster
mcinstall@mccn1:/var/opt/oracle.minicluster % gtar xvf /var/tmp/mc-1.1.25.4-sfw.tar

mcinstall@mccn2:/var/home/mcinstall % cd /var/opt/oracle.minicluster
mcinstall@mccn2:/var/opt/oracle.minicluster % gtar xvf /var/tmp/mc-1.1.25.4-sfw.tar

Restore the files /etc/ssh/sshd_config and /etc/default/login to their previous state and restart sshd.
Allow root on non-console, by editing file /etc/default/login to comment out the following line:

#CONSOLE=/dev/console

Then restart sshd:

#svcadm restart svc:/network/ssh:default

Finally reboot node 1, then node2; otherwise, you may receive some errors during MCMU DB / Admin VM group deployment phase.

7. Resetting ILOM password

Refernece the following document: Oracle MiniCluster MC-S7: Example of How to Manually Reset ILOM Root Password (Doc ID 2254209.1)

8. Installing servers with AI server

System can be installed from an AI server. If you don't have an AI server then proceed with Installing from ISO file.
- Installing from AI server takes about 20 min.
- Install with latest MiniCluster manifest. You will need to download the following items
- Manifest
- Profile
Here is an Oracle Internal example. These links do not work unless one has access to eng work space:

https://stbeehive.oracle.com/content/dav/st/MiniCluster%20Management%20Utility/Documents/AI%20manifest/mc-default-sonoma.xml
https://stbeehive.oracle.com/content/dav/st/MiniCluster%20Management%20Utility/Documents/AI%20manifest/mc-n1-profile.xml

Example installing system from AI server:

sca15-1070-install$ pfexec /opt/cr-labtech/bin/cr-install add 00:10:e0:9a:04:76 sca15-1070-install-s11u3-SRU9-4-sparc sun4v -n ar01 -m mc-default-sonoma.xml -p ./mc-n1-profile.xml
where 00:10:e0:9a:04:76 is MAC address of net2 interface
{0} ok set-defaults
{0} ok setenv auto-boot? false
{0} ok reset-all
{0} ok setenv
auto-boot? true
{0} ok boot net2:dhcp - install

<END>

References

<NOTE:2153282.1> - Oracle MiniCluster S7-2: Software Download Center
<NOTE:2254209.1> - Oracle MiniCluster MC-S7: Example of How to Manually Reset ILOM Root Password

Attachments

This solution has no attachment