Oracle MiniCluster S7-2 Administration Guide

Oracle MiniCluster S7-2 Administration Guide
Oracle MiniCluster S7-2 Administration
Guide
Part No: E69473-05
March 2017
Oracle MiniCluster S7-2 Administration Guide
Part No: E69473-05
Copyright © 2017, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except
as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform,
publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS. Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered
to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As
such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or
documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous
applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all
appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of
SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered
trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are
not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement
between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content,
products, or services, except as set forth in an applicable agreement between you and Oracle.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Référence: E69473-05
Copyright © 2017, Oracle et/ou ses affiliés. Tous droits réservés.
Ce logiciel et la documentation qui l’accompagne sont protégés par les lois sur la propriété intellectuelle. Ils sont concédés sous licence et soumis à des restrictions d’utilisation et
de divulgation. Sauf stipulation expresse de votre contrat de licence ou de la loi, vous ne pouvez pas copier, reproduire, traduire, diffuser, modifier, accorder de licence, transmettre,
distribuer, exposer, exécuter, publier ou afficher le logiciel, même partiellement, sous quelque forme et par quelque procédé que ce soit. Par ailleurs, il est interdit de procéder à toute
ingénierie inverse du logiciel, de le désassembler ou de le décompiler, excepté à des fins d’interopérabilité avec des logiciels tiers ou tel que prescrit par la loi.
Les informations fournies dans ce document sont susceptibles de modification sans préavis. Par ailleurs, Oracle Corporation ne garantit pas qu’elles soient exemptes d’erreurs et vous
invite, le cas échéant, à lui en faire part par écrit.
Si ce logiciel, ou la documentation qui l’accompagne, est livré sous licence au Gouvernement des Etats-Unis, ou à quiconque qui aurait souscrit la licence de ce logiciel pour le
compte du Gouvernement des Etats-Unis, la notice suivante s’applique:
U.S. GOVERNMENT END USERS. Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered
to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As
such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or
documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
Ce logiciel ou matériel a été développé pour un usage général dans le cadre d’applications de gestion des informations. Ce logiciel ou matériel n’est pas conçu ni n’est destiné
à être utilisé dans des applications à risque, notamment dans des applications pouvant causer des dommages corporels. Si vous utilisez ce logiciel ou matériel dans le cadre d’
applications dangereuses, il est de votre responsabilité de prendre toutes les mesures de secours, de sauvegarde, de redondance et autres mesures nécessaires à son utilisation dans des
conditions optimales de sécurité. Oracle Corporation et ses affiliés déclinent toute responsabilité quant aux dommages causés par l’utilisation de ce logiciel ou matériel pour ce type
d’applications.
Oracle et Java sont des marques déposées d’Oracle Corporation et/ou de ses affiliés. Tout autre nom mentionné peut correspondre à des marques appartenant à d’autres propriétaires
qu’Oracle.
Intel et Intel Xeon sont des marques ou des marques déposées d’Intel Corporation. Toutes les marques SPARC sont utilisées sous licence et sont des marques ou des marques
déposées de SPARC International, Inc. AMD, Opteron, le logo AMD et le logo AMD Opteron sont des marques ou des marques déposées d’Advanced Micro Devices. UNIX est une
marque déposée d’The Open Group.
Ce logiciel ou matériel et la documentation qui l’accompagne peuvent fournir des informations ou des liens donnant accès à des contenus, des produits et des services émanant de
tiers. Oracle Corporation et ses affiliés déclinent toute responsabilité ou garantie expresse quant aux contenus, produits ou services émanant de tiers, sauf mention contraire stipulée
dans un contrat entre vous et Oracle. En aucun cas, Oracle Corporation et ses affiliés ne sauraient être tenus pour responsables des pertes subies, des coûts occasionnés ou des
dommages causés par l’accès à des contenus, produits ou services tiers, ou à leur utilisation, sauf mention contraire stipulée dans un contrat entre vous et Oracle.
Accessibilité de la documentation
Pour plus d’informations sur l’engagement d’Oracle pour l’accessibilité à la documentation, visitez le site Web Oracle Accessibility Program, à l’adresse http://www.oracle.com/
pls/topic/lookup?ctx=acc&id=docacc.
Accès aux services de support Oracle
Les clients Oracle qui ont souscrit un contrat de support ont accès au support électronique via My Oracle Support. Pour plus d’informations, visitez le site http://www.oracle.com/
pls/topic/lookup?ctx=acc&id=info ou le site http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs si vous êtes malentendant.
Contents
Using This Documentation ................................................................................ 13
Product Documentation Library ....................................................................... 13
Feedback ...................................................................................................... 13
Understanding Administration Resources ........................................................ 15
MCMU Overview .......................................................................................... 15
ORAchk Overview ........................................................................................ 16
Administration Resources ............................................................................... 17
Understanding Zones, VMs, and Storage ......................................................... 19
MiniCluster Zones Overview ........................................................................... 19
MiniCluster VM Groups and VMs Overview ..................................................... 21
MiniCluster Storage Overview ......................................................................... 23
Accessing the System ...................................................................................... 25
Accessing the MCMU (BUI and CLI) ............................................................... 25
▼ Log in to the MCMU BUI ................................................................. 26
MCMU BUI Overview ........................................................................... 27
▼ Log Out of the MCMU BUI .............................................................. 29
▼ Log in to the MCMU CLI ................................................................. 29
▼ Log Out of the MCMU CLI ............................................................... 29
Accessing VMs ............................................................................................. 30
▼ Log in to a DB VM ......................................................................... 30
▼ Log in to an App VM ....................................................................... 31
▼ Log Out of a VM ............................................................................. 32
Accessing Underlying VM Support Structures .................................................... 33
▼ Log in to the Global or Kernel Zone .................................................... 33
▼ Log Out of the Global Zone ............................................................... 34
5
Contents
Accessing Oracle ILOM ................................................................................. 35
▼ Log in to Oracle ILOM on a Node ...................................................... 35
▼ Log Out of Oracle ILOM .................................................................. 36
Managing MCMU User Accounts (BUI) ............................................................. 37
User Roles ................................................................................................... 37
User Accounts .............................................................................................. 38
MCMU Password Policies .............................................................................. 39
MCMU User Approval Process Overview ......................................................... 39
▼ Display MCMU Users (BUI) ..................................................................... 40
▼ Create a New MCMU User (BUI) ............................................................... 41
▼ Approve or Reject a New User (BUI) .......................................................... 43
▼ Change an MCMU User Password (BUI) ..................................................... 44
▼ Reset an MCMU User Password (BUI) ........................................................ 44
▼ Delete a User Account (BUI) ..................................................................... 46
▼ Change a User Profile (BUI) ...................................................................... 47
Starting and Stopping the System .................................................................... 49
▼ Start the System ....................................................................................... 49
▼ Shut Down, Reset, or Power Cycle the System .............................................. 50
Obtaining System Information (BUI) ................................................................. 53
▼ Display the MCMU Version (BUI) .............................................................. 53
▼ View System Information (BUI) ................................................................. 54
▼ View and Update Network Configuration Information (BUI) ............................ 56
▼ Review or Run Initialization Steps (BUI) ..................................................... 58
▼ View the Status of Running Tasks (BUI) ...................................................... 60
Planning to Create VMs .................................................................................... 61
Configuration Planning Overview ..................................................................... 61
DB VM Planning Worksheets (Optional) ........................................................... 62
DB VM Group Parameters .............................................................................. 65
VM Group Profile Name ........................................................................ 65
Shared Storage ...................................................................................... 66
Security Profile ..................................................................................... 66
ASM Redundancy ................................................................................. 66
6
Oracle MiniCluster S7-2 Administration Guide • March 2017
Contents
Number of VMs on Each Node ............................................................... 67
Role Separation ..................................................................................... 67
Group Description ................................................................................. 69
DB VM Parameters ....................................................................................... 69
Public Hostname ................................................................................... 69
Number of Cores ................................................................................... 70
Password .............................................................................................. 70
SCAN Name ........................................................................................ 70
GI Patch Level ...................................................................................... 70
System Disk Group ............................................................................... 71
Data Disk Group ................................................................................... 71
DATA/RECO Disk Group Split ................................................................ 71
REDO Disk Group ................................................................................ 71
RECO Disk Group ................................................................................ 71
DB Home Parameters ..................................................................................... 72
Oracle Database Version ......................................................................... 72
Oracle Home Path ................................................................................. 73
Patch Level .......................................................................................... 73
DB Instance Parameters .................................................................................. 73
New Instance or Import Existing Instance .................................................. 74
Template Type ...................................................................................... 74
Instance Type ....................................................................................... 74
Database Instance Version ....................................................................... 76
Container DB ....................................................................................... 76
PGA Memory Space .............................................................................. 77
SGA Memory Space .............................................................................. 77
Character Sets ....................................................................................... 77
Instance Name ...................................................................................... 77
App VM Planning Worksheets (Optional) .......................................................... 77
App VM Group Parameters ............................................................................. 78
VM Group Profile Name ........................................................................ 79
Description ........................................................................................... 79
Number of VMs .................................................................................... 79
Shared Storage ...................................................................................... 79
Security Profile ..................................................................................... 80
VM Type ............................................................................................. 80
Enable Security ..................................................................................... 80
7
Contents
Public Hostname ................................................................................... 81
Cores ................................................................................................... 81
Password .............................................................................................. 81
Define Cluster ...................................................................................... 82
Configuring DB VMs (BUI) ................................................................................ 83
▼ View the DB VM Group and VMs (BUI) ..................................................... 83
DB VM Creation Task Overview ..................................................................... 85
▼ Create a DB VM Group Profile (BUI) ......................................................... 87
▼ Deploy the DB VM Group (BUI) ................................................................ 96
▼ Create DB Homes (BUI) ........................................................................... 99
▼ Create DB Instances (BUI) ....................................................................... 101
▼ Edit a DB VM Group Profile (BUI) ........................................................... 105
▼ Add a DB VM to a Group (BUI) .............................................................. 108
Deleting DB Components (BUI) ..................................................................... 111
▼ Delete a DB Instance (BUI) ............................................................. 111
▼ Delete a DB Home (BUI) ................................................................ 113
▼ Delete a DB VM Group (BUI) .......................................................... 115
▼ Delete a DB VM Group Profile (BUI) ................................................ 116
Configuring Application VMs (BUI) ................................................................. 119
▼ View App VM Groups and VMs (BUI) ...................................................... 119
App VM Creation Task Overview .................................................................. 120
▼ Create an App VM Group Profile (BUI) ..................................................... 121
▼ Deploy App VM Groups (BUI) ................................................................. 126
▼ Edit an App VM Group (BUI) .................................................................. 128
▼ Delete an Undeployed App VM Group ....................................................... 131
▼ Delete a Deployed App VM Group ............................................................ 132
Configuring Storage for VM Groups (BUI) ....................................................... 135
▼ Enable or Disable Shared Storage (BUI) ..................................................... 135
▼ Add an External NFS to a VM Group (BUI) ............................................... 137
▼ Delete a Network File System From a VM Group (BUI) ................................ 140
Viewing System Security Information (BUI) .................................................... 143
Security Compliance Benchmarks ................................................................... 143
8
Oracle MiniCluster S7-2 Administration Guide • March 2017
Contents
▼ View Security Information (BUI) .............................................................. 144
▼ View Benchmark Reports (BUI) ................................................................ 145
Configuring Oracle Engineered Systems Hardware Manager .......................... 149
Oracle Engineered Systems Hardware Manager Overview ................................... 149
▼ Access Oracle Engineered Systems Hardware Manager ................................. 150
▼ Update Component Passwords .................................................................. 151
▼ Configure the Utility's Password Policy and Passwords .................................. 152
▼ Configure Certificates and Port Numbers .................................................... 153
Checking the Virtual Tuning Status (BUI) ........................................................ 155
Virtual Tuning Assistant Overview ................................................................. 155
▼ View Virtual Tuning Assistant Status (BUI) ................................................ 155
Updating MiniCluster Software (BUI) ............................................................... 159
Component Update Process Overview ............................................................. 159
▼ View Software Component Versions (BUI) .................................................. 160
▼ Check for and Obtain the Latest Updates .................................................... 162
▼ Extract the Patch Bundle ......................................................................... 164
▼ Install the Component Bundle ................................................................... 165
▼ Update MiniCluster Software (BUI) ........................................................... 167
Performing System Checks (BUI) .................................................................... 173
▼ Perform a Readiness Check (BUI) ............................................................. 173
▼ View the Hardware Topology (BUI) .......................................................... 174
▼ Calibrate Disks (BUI) ............................................................................. 174
Performing Support Tasks (BUI) ..................................................................... 177
▼ Access My Oracle Support (BUI) .............................................................. 177
▼ Access Oracle Engineered Systems Hardware Manager ................................. 178
▼ Creating A support file bundle (OESHM) ................................................... 178
▼ Configure the Oracle ASR Client (BUI) ..................................................... 179
Using the MCMU CLI ....................................................................................... 183
MCMU CLI Overview ................................................................................. 183
9
Contents
▼ Display mcmu Help For All Subcommands (CLI) .......................................... 184
▼ Display mcmu Help for a Specific Subcommand (CLI) ................................... 185
Listing Version, Group, and VM Details (CLI) .................................................. 187
▼ List the MCMU Version (CLI) .................................................................. 188
▼ List a Summary of All DB VM Groups (CLI) .............................................. 188
▼ List a Summary of a DB VM Group Profile (CLI) ........................................ 188
▼ List Details of a DB VM Group Profile (CLI) .............................................. 189
▼ List Details for a DB VM Group (CLI) ...................................................... 192
▼ List All DB Homes in a Group (CLI) ......................................................... 195
▼ List Details for a DB Home (CLI) ............................................................. 195
▼ List All DB Instances in a Group (CLI) ...................................................... 196
▼ List Details of a DB Instance (CLI) ........................................................... 197
▼ List a Summary of All App VM Group Profiles (CLI) ................................... 197
▼ List Details of an App Group Profile (CLI) ................................................. 199
▼ List a Summary of All App VMs (CLI) ...................................................... 200
▼ List Details of an App VM (CLI) .............................................................. 201
▼ List the IP and Hostname Entries for DNS (CLI) .......................................... 202
Obtaining Status (CLI) ..................................................................................... 205
▼ Show the Status of Zones and DB VMs (CLI) ............................................. 205
▼ Show the Kernel Zone GI Status (CLI) ....................................................... 206
▼ Show the GI Status of a DB VM (CLI) ...................................................... 208
▼ Show Kernel Zone Status (CLI) ................................................................ 209
▼ Show the VM Status (CLI) ...................................................................... 210
▼ Check the Status of the GI on the Kernel Zone (CLI) .................................... 210
▼ Run orachk Health Checks (CLI) .............................................................. 212
Starting and Stopping VM Components (CLI) ................................................. 215
Starting VM Components (CLI) ..................................................................... 215
▼ Start a Kernel Zone (CLI) ................................................................ 215
▼ Start All VMs in a Group (CLI) ........................................................ 216
▼ Start a Single VM (CLI) .................................................................. 216
▼ Start the Grid Infrastructure for the Application VM Groups (CLI) ........... 217
▼ Start the Grid Infrastructure for the DB VM Group (CLI) ....................... 217
Stopping VM Components (CLI) .................................................................... 217
10
Oracle MiniCluster S7-2 Administration Guide • March 2017
Contents
▼
▼
▼
▼
▼
Stop the Grid Infrastructure in the DB VM Group (CLI) ........................ 218
Stop the Grid Infrastructure in an Application VM Group (CLI) .............. 218
Stop All VMs in a Group (CLI) ........................................................ 219
Stop a Single VM (CLI) .................................................................. 219
Stop a Kernel Zone (CLI) ................................................................ 219
Verifying that the System Is Ready for the Creation of VMs (CLI) .................... 221
▼ List the System Setup Steps (CLI) ............................................................. 221
▼ (If Needed) Run or Rerun System Setup Steps (CLI) ..................................... 223
▼ Verify the System Setup (CLI) .................................................................. 224
▼ Verify the System, Topology, and Disk Readiness (CLI) ................................ 225
▼ Add IP Addresses for Future VMs (CLI) .................................................... 227
Configuring DB VMs (CLI) ............................................................................... 229
Creating DB VMs (CLI) ............................................................................... 229
▼ Create a DB VM Group Profile (CLI) ................................................ 229
▼ Deploy the DB VM Group (CLI) ...................................................... 232
▼ Create DB Homes (CLI) .................................................................. 234
▼ Create DB Instances (CLI) ............................................................... 236
▼ Update a DB VM Group (CLI) ................................................................. 241
Deleting DB VM Group Components (CLI) ..................................................... 251
▼ Delete a DB VM Group Profile (CLI) ................................................ 252
▼ Delete a DB VM Group (CLI) .......................................................... 253
▼ Delete a DB Home (CLI) ................................................................. 253
▼ Delete a DB Instance (CLI) .............................................................. 254
Configuring Application VMs (CLI) .................................................................. 255
▼ Create an APP VM Group (CLI) ............................................................... 255
▼ Deploy an App VM Group (CLI) .............................................................. 257
▼ Update an App VM Group (CLI) .............................................................. 258
▼ Toggle Shared Storage for an App Group (CLI) ........................................... 260
▼ Delete an App VM Group (CLI) ............................................................... 260
Managing MCMU User Accounts (CLI) ............................................................ 261
▼ Create a New MCMU User (CLI) ............................................................. 261
▼ Approve a New MCMU User (CLI) .......................................................... 262
11
Contents
▼
▼
▼
▼
▼
Reject a New MCMU User (CLI) .............................................................. 263
List MCMU User Approval and Rejection Status (CLI) ................................. 264
Delete an MCMU User (CLI) ................................................................... 265
Change an MCMU User Password (CLI) .................................................... 266
Edit a User Profile (CLI) ......................................................................... 266
Managing Networks (CLI) ................................................................................ 269
▼ Configure Additional Networks ................................................................. 269
Managing the Security Configuration (CLI) ..................................................... 273
▼ Show Compliance Information (CLI) ......................................................... 273
▼ Schedule a Compliance Run (CLI) ............................................................ 274
▼ Set SSH Key Options (CLI) ..................................................................... 274
▼ Show Encryption Keys (CLI) ................................................................... 275
▼ Back Up the Encryption Keystore (CLI) ..................................................... 277
Managing Storage (CLI) ................................................................................... 279
▼ Enable or Disable Shared Storage (CLI) ..................................................... 279
▼ Add External NFS (CLI) ......................................................................... 282
▼ Configure an Added Storage Array (CLI) ................................................... 284
▼ Prepare a Drive for Removal (CLI) ............................................................ 287
▼ Reattach a Replaced Disk (CLI) ................................................................ 290
Administering the Virtual Tuning Assistant (CLI) ............................................ 293
▼ Configure the mctuner Notification Email Address (CLI) ............................... 293
▼ View Virtual Tuning Assistant Status (CLI) ................................................. 294
Updating MiniCluster Software (CLI) ............................................................... 297
▼ View Software Component Versions (CLI) .................................................. 297
▼ Update the MCMU Component (CLI) ........................................................ 299
▼ Update Other MiniCluster Software Components (CLI) ................................. 302
Index ................................................................................................................ 307
12
Oracle MiniCluster S7-2 Administration Guide • March 2017
Using This Documentation
■
■
■
Overview – Describes how to perform Oracle MiniCluster S7-2 administration using
specific MiniCluster tools.
Audience – System administrators, and authorized service providers
Required knowledge – Advanced experience administering enterprise servers
Product Documentation Library
Documentation and resources for this product and related products are available at http://
docs.oracle.com/cd/E69469_01.
Feedback
Provide feedback about this documentation at http://www.oracle.com/goto/docfeedback.
Using This Documentation
13
14
Oracle MiniCluster S7-2 Administration Guide • March 2017
Understanding Administration Resources
This document is updated with functions and features for MiniCluster v1.1.25 software.
Depending on the version of software running on your MiniCluster, some features might be
slightly different or not present.
These topics describe administration resources for MiniCluster.
■
■
■
“MCMU Overview” on page 15
“ORAchk Overview” on page 16
“Administration Resources” on page 17
MCMU Overview
The MiniCluster Management Utility (MCMU) enables you to perform a variety of installation,
configuration, and management activities with a secure, browser-based interface (BUI). You
select management tasks and provide configuration information, and the utility performs the
complex operations in the background.
Note - The MCMU also provides a CLI. See “Using the MCMU CLI” on page 183.
This list summarizes the types of activities you can perform using this utility:
■
■
Initially configure MiniCluster – The utility verifies the network and storage topology
for MiniCluster, sets up the two SPARC S7-2 compute nodes for internet and management
access, and configures an NFS shared file system for application virtual machine group
usage as required. The utility configures the network according to site preferences,
configures the hostnames and IP addresses for client access and for the management
console.
Create and manage database virtual machines – The utility installs Oracle Grid
Infrastructure 12c on the database virtual machine group and also supports provisioning
Understanding Administration Resources
15
ORAchk Overview
■
■
■
■
■
■
■
of Oracle 11g and 12c single instance databases, RAC databases, and RAC One Node
databases.
Create and manage application virtual machines – Based on your configuration
preferences, the utility provisions either two virtual machines (one on each compute node),
or one virtual machine per application group. Multiple App VM groups can be created.
Configuration parameters enable you to host application binaries on local storage or install
the binaries in shared storage.
View the system configuration and network information – By clicking a few buttons,
you can view the configuration of VMs on the compute nodes, view the network topology,
see network parameters, and verify initialization processes.
Run security benchmarks – Based on your security requirements, use the MCMU to
configure, run, and monitor security benchmarks.
Upgrade MiniCluster firmware and software – The utility installs MiniCluster quarterly
patch updates, which can include updates to the OS, firmware, Oracle ILOM, and the Oracle
Database software.
Enable automatic system tuning capabilities – The MCMU includes a virtual tuning
assistant which automatically adjusts system parameters to ensure the system runs
optimally.
Perform system checks – By clicking a few buttons in the utility, you can verify the
configuration of the system and check the status of the drives.
Simplified support tasks – The MCMU provides the ability to generate support bundles
and to configure the automatic service request (ASR) feature.
ORAchk Overview
ORAchk is a configuration audit tool that validates the Oracle environment. It enables you to
complete a variety of system checks that would otherwise have to be done manually. ORAchk
provides these features:
■
■
■
■
Checks the database VM for problems across the various layers of the stack.
Reports show system health risks with the ability to drill down into specific problems and
understand their resolutions
Can be configured to send email notifications when it detects problems.
Can be configured to run automatically at scheduled times.
ORAchk is supported for database VMs.
To download ORAchk and to find out more about ORAchk, refer to these resources:
■
16
My Oracle Support article, Doc ID 1268927.02– Download is available from this article.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Administration Resources
■
The ORAchk Quick Start Guide available from http://docs.oracle.com/cd/E75572_01/.
For an example of running ORAchk on MiniCluster, see “Run orachk Health Checks
(CLI)” on page 212.
Administration Resources
Use this table to identify the task you want to perform and to locate information about the task.
Administrative Task
Description
Links
Initially install and configure
the software on MiniCluster.
Use a combination of tools (such as the
MCMU) that are provided with the system.
Installation procedures are described in the Oracle
MiniCluster S7-2 Installation Guide.
http://docs.oracle.com/cd/E69469_01
Create and manage database
and application virtual
machines (VMs) and virtual
machine groups (VM
groups).
Use the MCMU, which is described in this guide.
“MCMU Overview” on page 15
Perform administrative tasks
in a VM through the Oracle
Solaris OS.
Oracle Solaris documentation includes
information about getting started, booting the OS,
administering networks, managing users, creating
virtual environments, and setting up an application
development environment.
http://docs.oracle.com/en/operating-systems
Perform DB administrative
tasks in a DB VM.
The MCMU provides simplified ways to manage
the database on VMs. These administrative tasks
are described in this guide.
“Configuring DB VMs (BUI)” on page 83
Additional DB
administration
Oracle Database documentation provides
information about getting started, managing
users, application development, using Enterprise
Manager plug-ins.
http://docs.oracle.com/en/database
Perform administrative tasks
through Oracle ILOM.
Oracle ILOM is firmware that runs on a service
processor and is embedded on the compute nodes.
It enables lights-out remote management. You
manage and monitor the server independently of
the OS state.
http://www.oracle.com/goto/ilom/docs
Oracle ILOM documentation includes information
on getting started, administration, monitoring and
diagnostics, and configuring Oracle ILOM with
SNMP and IPMI.
Administer the system using
Enterprise Manager.
You can install an Enterprise Manager plug-in that
enables you to add the system to an Enterprise
Manager server in your environment.
<future link to EM plug-in info in this doc>
http://docs.oracle.com/cd/E11857_01/index.htm
Understanding Administration Resources
17
Administration Resources
Administrative Task
Description
Links
Oracle Enterprise Manager documentation
includes getting started, installation, and
administration information.
Power on the system.
In this guide.
“Starting and Stopping the System” on page 49
Shut down or power off the
system.
In this guide.
“Starting and Stopping the System” on page 49
Configure Oracle
Engineered Systems
Hardware Manager.
In this guide.
“Configuring Oracle Engineered Systems Hardware
Manager” on page 149
Check the status of the
virtual tuning feature.
In this guide.
“Checking the Virtual Tuning Status
(BUI)” on page 155
.
18
Oracle MiniCluster S7-2 Administration Guide • March 2017
Understanding Zones, VMs, and Storage
These topics describe the components of MiniCluster.
■
■
■
“MiniCluster Zones Overview” on page 19
“MiniCluster VM Groups and VMs Overview” on page 21
“MiniCluster Storage Overview” on page 23
MiniCluster Zones Overview
MiniCluster uses Oracle Solaris zones as the underlying support structure for the system. The
creation of zones is automatically handled by the MiniCluster initialization process based on
configuration information that you provide. You do not need to administer the technical details
of zones, but the MiniCluster tools and documentation use zone technology and terminology, so
this section explains key concepts and terms.
Caution - Never manually manage VMs using Oracle Solaris zone commands. Always manage
the VMs through MCMU BUI or MCMU CLI.
Zones are used to virtually divide the resources of a physical machine to simulate multiple
machines and OSs.
The Oracle Solaris Zones partitioning technology used in MiniCluster enables you to
consolidate multiple hosts and services on a system, affording these benefits:
■
■
■
■
Increased hardware utilization
Flexibility in resource allocation
Reduced power requirements
Lower cost of ownership
This illustration shows the zones that are automatically created on every MiniCluster. The
illustration represents the system's zone configuration before the creation of VMs.
Understanding Zones, VMs, and Storage
19
MiniCluster Zones Overview
These zones are automatically created when the system is initialized:
■
■
Global zones – One on each node, they include the initial installation of the Oracle Solaris
OS from which all the other zones and VMs are created. The global zone on node 1 also
contains the MCMU software. Each global zone is assigned 2 CPU cores. Each global zone
is automatically configured with network parameters that enable you to access it from your
network (see “Log in to the Global or Kernel Zone” on page 33). However, there is
minimal administration required in the global zones.
Kernel zones – One on each node, they include an installation of the Oracle Solaris OS,
NFS shared with the VMs, and grid infrastructure (GI) components. The OS and GI provide
the necessary drivers for the VMs to access file systems on the storage arrays. Each kernel
zone is assigned 2 CPU cores. Each kernel zone is automatically configured with network
parameters that enable you to access it from your network (see “Log in to the Global or
Kernel Zone” on page 33). However, there is minimal administration required in the
kernel zones because no site-specific software is added to them.
Note - The zones are automatically configured when the system is installed. For details about
the installation process, refer to the Oracle MiniCluster S7-2 Installation Guide. See “Product
Documentation Library” on page 13 for the location of that guide.
20
Oracle MiniCluster S7-2 Administration Guide • March 2017
MiniCluster VM Groups and VMs Overview
MiniCluster VM Groups and VMs Overview
Virtual machines (VMs) are used to virtually divide the resources of the system to simulate
multiple machines and OSs. Each VM is dedicated to the programs running inside. VMs are
isolated, providing a secure environment for running applications and databases.
You might configure separate VMs for individual departments in your organization, with each
VM hosting a unique set of applications and databases. Or use VMs to control licensing costs
by limiting some software to a set number of cores now with the ability to easily add more
cores later. You can use some VMs for development and others for production, or any other
combination of deployments.
MiniCluster VMs are created using Solaris non-global zones, and have very similar attributes
to MiniCluster zones (described in “MiniCluster Zones Overview” on page 19), including
secure isolation, flexibility in resource allocation, and so on. The distinction between
MiniCluster zones and VMs is that the zones provide underlying support structures for the
system (uniform from one MiniCluster to another) and VMs are the virtual machines that
you customize to suit your enterprise compute needs. You determine the number, type, and
configuration of VMs on MiniCluster.
There are two types of VMs:
■
■
DB VM – A virtual machine that contains the Oracle Database running in the Oracle Solaris
OS.
App VM – A virtual machine that contains the Oracle Solaris OS and any applications that
you choose to install.
You can configure the system with only one type of VM, or a combination of DB and App
VMs.
VMs are easily provisioned using the MCMU BUI or CLI. MCMU prompts you for the VM
parameters and then creates, deploys, and configures the VMs.
Note - When the system is installed, the initialization process automatically invokes the MCMU
BUI and prompts the installer to configure VMs. The installer can create VMs at that time, or
skip that process so that the VMs can be created later. To determine if VMs are present, see
“View the DB VM Group and VMs (BUI)” on page 83 and “View App VM Groups and
VMs (BUI)” on page 119.
Each VM has its own set of network parameters that enable you to access it from your network
(see “Accessing VMs” on page 30).
This illustration shows an example of how the VMs are logically arranged, and lists the main
components that make up each type of VM.
Understanding Zones, VMs, and Storage
21
MiniCluster VM Groups and VMs Overview
■
■
■
■
■
■
22
Global zone – See “MiniCluster Zones Overview” on page 19.
Kernel zone – See “MiniCluster Zones Overview” on page 19.
DB VM group – This Is the collection of database VMs on the system (the group spans
both nodes). One database VM group is supported on the system. The group is configured
by specifying the parameters described in “Planning to Create VMs” on page 61.
DB VM – A database virtual machine is a VM that contains the Oracle Database software.
You choose to assign a set number of cores to a DB VM, or to have the DB VM share cores
with other VMs.
DB Home – Is the installation of the Oracle Database software in the group. You can choose
to install one version, or a combination of versions. Oracle Database 11g, 12c, or 12 SE
(single-instance only), are supported . You can also specify the home directory and patch
level of the software.
DB Instance – Provides the individual DB configuration details for a given instance of
the DB. You create one or more instances in each DB VM. There are a variety of instance
parameters to choose from such as RAC, RAC one-node, or single instance, ASM disk
group redundancy, and the security profile.
Oracle MiniCluster S7-2 Administration Guide • March 2017
MiniCluster Storage Overview
■
■
■
App VM group – Is a logical grouping of application VMs. You can have one or two
application VMs in a group. Unlike the DB VM group, you can have as many App VM
groups as there are resources available to support them.
App VM – An application virtual machine is a VM that contains the Oracle Solaris OS and
any applications you install. You choose to assign a set number of cores to an App VM, or
to have the App VM share cores with other VMs.
Future DB and App VMs – As long as storage and CPU resources are available, you can
create additional VMs at any time.
MiniCluster Storage Overview
MCMU automatically assigns each VM the appropriate amount of storage based on the
configuration of the VM. This section describes how the MCMU configures the storage.
MiniCluster includes six HDDs in each node, and one or two storage arrays.
Each compute node provides these storage components:
■
■
2 HDDs, used by the global and kernel zones. The drives use RAID 10 for high availability.
4 HDDs, store the VM root file systems. The drives use RAID 10 for high availability.
One storage array provides these storage components:
■
■
■
14 SSDs, reserved for DB VMs. The DB disk groups are either configured for normal
redundancy (protection against a single disk failure) or high redundancy (protection against
two disk failures).
4 SSDS, reserved for DB REDO logs (always set at high redundancy).
6 HDDs, provide the shared storage that can be exported to DB and App VMs. This storage
is enabled or disabled when you define a group profile, and can be changed on the fly in
the MCMU BUI or CLI. For highly secure environments, refer to the recommendations in
the Oracle MiniCluster S7-2 Security Guide at http://docs.oracle.com/cd/E69469_01/
html/E69475/grbfj.html.
This figure represents how the storage is arranged.
Understanding Zones, VMs, and Storage
23
MiniCluster Storage Overview
If you add another storage array to the system (see “Configure an Added Storage Array
(CLI)” on page 284), the utility automatically doubles the amount of storage for each of the
categories shown in the figure.
In addition to the storage that comes with MiniCluster, you can provide access to network file
systems. See “Add an External NFS to a VM Group (BUI)” on page 137.
24
Oracle MiniCluster S7-2 Administration Guide • March 2017
Accessing the System
These topics describe how to access different aspects of the system based on the kind of tasks
you need to perform.
Note - These topics assume that the system is already installed and initialized. For details about
accessing the system for installation, refer to the Oracle MiniCluster S7-2 Installation Guide.
See “Product Documentation Library” on page 13.
Description
Links
Access the MCMU BUI or CLI to create, edit, and delete DB and application VMs. Also use
the MCMU to perform administrative tasks such as managing security benchmarks, updating
firmware and software, and to perform any other MCMU functions.
“Accessing the MCMU (BUI and
CLI)” on page 25
Access individual VMs to administer software within the VM.
“Accessing VMs” on page 30
Access the underlying VM support structures such as the global zone and kernel zones.
Accessing these components is only performed in unique situations, such as to alter certain
default system configurations.
“Accessing Underlying VM Support
Structures” on page 33
Access Oracle ILOM.
“Accessing Oracle ILOM” on page 35
Accessing the MCMU (BUI and CLI)
These topics describe how to access and navigate the MCMU BUI, and MCMU CLI.
■
■
■
■
■
“Log in to the MCMU BUI” on page 26
“MCMU BUI Overview” on page 27
“Log Out of the MCMU BUI” on page 29
“Log in to the MCMU CLI” on page 29
“Log Out of the MCMU CLI” on page 29
Accessing the System
25
Log in to the MCMU BUI
Log in to the MCMU BUI
1.
Open a browser on a system that has network access to MiniCluster.
2.
Type https://node1_name/MCMU in the browser address field.
Replace node1_name with the name of the MiniCluster compute node 1.
Note - Ensure that you specify https, because the utility requires a secure connection.
Note - If your browser displays a warning about an insecure connection, add an exception to
enable connectivity to the system.
For example:
https://mc7-n1/MCMU
The MCMU login page is displayed.
26
3.
(Optional) In your browser, bookmark this page.
4.
Enter an MCMU user name and password.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Log in to the MCMU BUI
Note - If you are logging into MCMU for the first time, the utility requires you to create a new
password. See “Reset an MCMU User Password (BUI)” on page 44.
The System Status page is displayed. For further details, see “MCMU BUI
Overview” on page 27.
For more information about user accounts, see “Managing MCMU User Accounts
(BUI)” on page 37.
The MCMU BUI automatically logs out users after 30 minutes of inactivity.
MCMU BUI Overview
When you log into the MCMU BUI, the System Status page is displayed. In the upper right
corner, you can select your language and access various options from the user-name drop-down
menu.
This example shows the System Status page.
The left navigation panel provides links to these MCMU functions:
Accessing the System
27
Log in to the MCMU BUI
■
Home – Displays the system status page, which provides an overall status of the system,
and access to these items:
Compliance Information – Shows information about security compliance reports. See
“Viewing System Security Information (BUI)” on page 143.
■ Virtual Tuning Assistant Status (not shown in the example) – Farther down the page is
an area that shows information from the built-in tuner feature. See “Checking the Virtual
Tuning Status (BUI)” on page 155.
Database – Expands to provide access to DB VM group profile features, and to DB VM
instance features. This page is where you manage DB VMs. See “Configuring DB VMs
(BUI)” on page 83.
Application – Expands to provide access to application VM group profile features, and
to a view of App VMs. This page is where you manage App VMs. See “Configuring
Application VMs (BUI)” on page 119.
Patches and Updates – Provides access to the utility patching features. See “Updating
MiniCluster Software (BUI)” on page 159.
Tasks – Displays information about running MCMU activities. See “View the Status of
Running Tasks (BUI)” on page 60.
System Settings – Expands, providing access to these pages:
■
■
■
■
■
■
■
■
■
■
■
■
■
■
28
System Information – Displays the MCMU version, Oracle Solaris OS
version, and compute node and storage details. See “View System Information
(BUI)” on page 54.
Security – Displays information about encryption keys on each compute node and
provides links to administer the encryption keys. See “View Security Information
(BUI)” on page 144.
Support – Provides access to generate support bundles, to start the Oracle Engineered
Systems Hardware Manager (under Oracle direction), and to configure ASR. See
“Performing Support Tasks (BUI)” on page 177.
User Accounts – Displays information about MCMU user accounts. See “Display
MCMU Users (BUI)” on page 40.
System Checks – Provides access to perform readiness checks, verify the topology, and
calibrate disks. See “Performing System Checks (BUI)” on page 173.
System Setup – Provides access to the tasks that are performed when the system is
initially installed. See “Review or Run Initialization Steps (BUI)” on page 58.
User Input Summary – Displays the information that was applied to the system during
the initial installation, such as IP address allocation. This page also provides a link
that enables you to add additional IP addresses to the system. See “View and Update
Network Configuration Information (BUI)” on page 56.
Hardware Topology – Displays a visual representation of the I/O connections to
storage arrays. See “View the Hardware Topology (BUI)” on page 174.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Log Out of the MCMU BUI
Log Out of the MCMU BUI
In the upper right corner, click on your login name, and select Log Out.
Log in to the MCMU CLI
1.
From a system that has network access to MiniCluster, use the ssh command to
log into MiniCluster.
Syntax:
% ssh mcmu_user_name@minicluster_node_name_or_IPaddress
where:
■
■
mcmu_user_name is the name of an MCMU user. The mcinstall user is the default primary
admin user. The password was set when the system was installed.
minicluster_node_name_or_IPaddress is the name of the first node on MiniCluster, or the
IP address of the first node.
For example:
% ssh mcinstall@mc4-n1
2.
When prompted, enter the password.
For more information about running mcmu CLI commands, see “Using the MCMU
CLI” on page 183.
Log Out of the MCMU CLI
Note - After 15 minutes of CLI inactivity, the session is automatically logged out.
At the command line prompt, type:
# exit
Accessing the System
29
Accessing VMs
Accessing VMs
These topics describe how to access individual VMs (not through the MCMU). Use these
procedures to administer software installed in individual VMs.
Caution - Never manually manage VMs using Oracle Solaris zone commands. Always manage
the VMs through the MCMU BUI or MCMU CLI. See “Accessing the MCMU (BUI and
CLI)” on page 25.
■
■
■
“Log in to a DB VM” on page 30
“Log in to an App VM” on page 31
“Log Out of a VM” on page 32
Log in to a DB VM
Use this procedure to log into a VM.
You must have the Tenant Admin (tadmin) role to log into a VM. For more information about
roles, see “User Roles” on page 37.
If you log directly into a DB VM, you are not accessing the system through the MCMU and you
cannot run mcmu commands.
Caution - Never manually manage VMs using Oracle Solaris zone commands. Always manage
the VMs through MCMU BUI or MCMU CLI.
This procedure describes how to access VMs using the ssh command. Depending on the
software and services installed in the VM, the VM might also be accessible through those
services.
1.
From a terminal window with network access to the system, use the ssh
command to log into a DB VM.
Syntax:
% ssh user_name@VM-hostname_or_IPaddress
where:
■
30
user_name is a valid user name with the Tenant Admin (tadmin) role.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Log in to an App VM
■
The default user that is initially configured in DB VMs is oracle. For more information
about the oracle user, see “User Accounts” on page 38
VM-hostname_or_IPaddress is either the hostname or IP address of the VM. You can obtain
VM names from DB → Virtual Machine Instances (see “View the DB VM Group and VMs
(BUI)” on page 83.
For Example:
% ssh oracle@dbvmg1-zone-1-mc4-n1
2.
Enter a valid password for the oracle user account.
The oracle user password is the password that was configured for the mcinstall user account.
3.
If needed, assume the root role.
The password is the same password used for the oracle user.
For example:
% su root
Password: **************
#
At this point, you can perform administrative tasks in the DB VM.
Log in to an App VM
Use this procedure to log into a VM.
You must have the Tenant Admin (tadmin) role to log into a VM. For more information about
roles, see “User Roles” on page 37.
If you log directly into a App VM, you are not accessing the system through the MCMU and
you cannot run mcmu commands.
Caution - Never manually manage VMs using Oracle Solaris zone commands. Always
manage the VMs through MCMU BUI or MCMU CLI. See “Accessing the MCMU (BUI and
CLI)” on page 25.
This procedure describes how to access VMs using the ssh command. Depending on the
software and services installed in the VM, the VM might also be accessible through those
services.
Accessing the System
31
Log Out of a VM
1.
From a terminal window with network access to the system, use the ssh
command to log into a VM.
Syntax:
% ssh user_name@VM-hostname_or_IPaddress
where:
■
■
user_name is a valid user name of a user with the Tenant Admin (tadmin) role.
VM-hostname_or_IPaddress is either the hostname or IP address of the VM. You can obtain
VM names from Application → Virtual Machine Instances (see “View App VM Groups and
VMs (BUI)” on page 119.
For Example:
% ssh mcinstall@appg500-zone-1-mc4-n2
2.
Enter a valid password for the mcinstall user account.
3.
If needed, assume the root role.
The password is the same password used for the mcinstall user.
For example:
% su root
Password: **************
#
At this point, you can perform administrative tasks in the App VM.
Log Out of a VM
Use this procedure to log out of a DB VM or App VM.
To completely log out, you need to exit from each login and su that you've performed. For
example, if you logged into a VM then used the su command to assume the root role, type
exit twice.
At the prompt, type:
# exit
Repeat exit as needed.
32
Oracle MiniCluster S7-2 Administration Guide • March 2017
Accessing Underlying VM Support Structures
Accessing Underlying VM Support Structures
In a few specialized situations, you might need to access the underlying VM support structures
such as the global zone and kernel zones.
Caution - Accessing the global zone and kernel zones should only be performed by trusted and
experienced Oracle Solaris administrators. Performing this procedure involves assuming the
root role, which has all administrative privileges. If administrative commands are not performed
properly, there is a potential for damaging or deleting critical system data.
■
■
“Log in to the Global or Kernel Zone” on page 33
“Log Out of the Global Zone” on page 34
Log in to the Global or Kernel Zone
Use this procedure to log in to the global zone. From the global zone, you can access the kernel
zones, if needed.
Caution - Never manually create, edit, or delete VMs using Oracle Solaris zone commands.
Always create, edit, and delete the VMs through MCMU BUI or MCMU CLI. See “Accessing
the MCMU (BUI and CLI)” on page 25.
1.
From a terminal window with network access to the system, use the ssh
command to log into the global zone.
Use the mcinstall user account. For more details about this account, see “User
Accounts” on page 38.
Syntax:
% ssh mcinstall@Node-hostname_or_IPaddress
where Node-hostname_or_IPaddress is either the hostname or the IP address of node 1 or
2. You can obtain the node name (Hostname Preview) from the MCMU System Settings
→ System Information page. See “View and Update Network Configuration Information
(BUI)” on page 56.
For example:
% ssh mcinstall@mc2.us.company.com
2.
Enter the password for mcinstall.
Accessing the System
33
Log Out of the Global Zone
The factory default password is welcome1, but was changed when the system was installed.
Specify the password that was configured for your system.
3.
If needed, assume the root role.
The password is the same password used for the mcinstall user.
For example:
% su root
Password: **************
#
At this point, you can perform administrative tasks in the global zone or access the kernel
zones.
4.
To get to a kernel zone, perform these commands:
Note - Alternatively, you can log directly into a kernel zone using ssh
mcinstall@kz_public_hostname, where kz_public_hostname is the system prefix (shown in
System Settings → User Input Summary) appended with ss01 (kernel zone on node 1) or ss02
(kernel zone on node 2). For example: ssh mcinstall@mc4ss01.
# zoneadm list
global
acfskz
appvmg1-zone-1-mc4-n1
dbvmg1-zone-3-mc4-n1
dbvmg1-zone-1-mc4-n1
dbvmg1-zone-4-mc4-n1
dbvmg1-zone-2-mc4-n1
In the output, the global zone is identified as global. The kernel zone is identified as acfskz.
# zlogin acfskz
Enter the password for mcinstall.
Log Out of the Global Zone
To completely log out, you need to exit from each login and su that you've performed. For
example, if you logged into the global zone then used the su command to assume the root role,
type exit twice.
34
Oracle MiniCluster S7-2 Administration Guide • March 2017
Accessing Oracle ILOM
At the prompt, type:
# exit
Repeat exit as needed.
Accessing Oracle ILOM
These topics describe how to access Oracle ILOM on the nodes. You can use Oracle ILOM to
perform a variety of lights-out-management activities such as controlling the power state of the
nodes, obtaining health status and fault information, configure boot modes, and so on.
For more information about Oracle ILOM, refer to the Oracle ILOM documentation library at
http://docs.oracle.com/cd/E37444_01.
■
■
“Log in to Oracle ILOM on a Node” on page 35
“Log Out of Oracle ILOM” on page 36
Log in to Oracle ILOM on a Node
The default user account in Oracle ILOM is root with a default password of welcome1, which is
usually changed after the system is installed.
To access Oracle ILOM, you need to know the Oracle ILOM hostname or IP address. To
identify these items on your system, see “View System Information (BUI)” on page 54 for
hostnames, and “View and Update Network Configuration Information (BUI)” on page 56
for IP addresses (ILOM IP addresses are listed as management IP addresses).
Depending on how you want to access Oracle ILOM, perform one of these
actions:
■
Oracle ILOM web interface – In a browser, enter this address, and press
Return:
http://ILOM_ipaddress
The Oracle ILOM Login screen is displayed. Log in using a Oracle ILOM account such as
root and password.
■
Oracle ILOM CLI – In a terminal window, enter:
Accessing the System
35
Log Out of Oracle ILOM
% ssh root@ILOM_hostname_or_ipaddress
root password: ********
->
Log Out of Oracle ILOM
Depending on how you accessed Oracle ILOM, perform one of these actions:
■
Oracle ILOM web interface – In the upper right corner, click Logout.
The Oracle ILOM Login screen is displayed. Log in using a Oracle ILOM account such as
root and password.
■
Oracle ILOM CLI – Enter:
-> exit
36
Oracle MiniCluster S7-2 Administration Guide • March 2017
Managing MCMU User Accounts (BUI)
These topics describe how to manage MCMU user accounts through the BUI. To manage user
accounts through the CLI, See “Managing MCMU User Accounts (CLI)” on page 261.
■
■
■
■
■
■
■
■
■
■
“User Roles” on page 37
“User Accounts” on page 38
“MCMU Password Policies” on page 39
“Display MCMU Users (BUI)” on page 40
“Create a New MCMU User (BUI)” on page 41
“Approve or Reject a New User (BUI)” on page 43
“Change an MCMU User Password (BUI)” on page 44
“Reset an MCMU User Password (BUI)” on page 44
“Delete a User Account (BUI)” on page 46
“Change a User Profile (BUI)” on page 47
User Roles
When you create an MCMU user, you assign the user one of these roles:
■
Primary admin (root role) – The root role defines the rights and privileges of primary
administrators of the MiniCluster system including all its compute nodes, networks,
database, and storage. Users with the root role can perform all installation and all critical
administrative operations without any constraints. As primary administrators, they can
delegate operations and approve adding and deleting users including new primary and
secondary administrators. The user must login with his/her own credentials. The mcinstall
user has the root role. All actions and operations carried out are logged and audited based on
the user identifier, not the role identifier.
■
Secondary admin (mcadmin role) – Users who are assigned with this role have readonly access to the global zones. They cannot run the MCMU BUI or CLI. All actions and
Managing MCMU User Accounts (BUI)
37
User Accounts
■
■
operations carried out are logged and audited based on the user identifier, not the role
identifier.
Tenant admin (tadmin role) – This role defines the rights and privileges of the
administrator of a MiniCluster VM. The role defines the rights and privileges of a VM
administer involved with day-to-day administrative operations supporting application
installations and deployment. Tenant admins cannot run MCMU, nor access the global
or kernel zones. If the user is created with the MCMU CLI, the role is identified as
tenant_admin. All actions are audited based on the user identifier, not the role identifier.
Auditor (auditor role) – Users with this role only have access to the MCMU BUI audit
review page where they can view the audit pool status and generate reports for user activity.
Only users with this role can access the audit review page. Auditors cannot access the
MCMU (except for the audit page), nor can they log into kernel zones or VMs.
User Accounts
MiniCluster includes the user accounts listed in this table.
User
Password
Role
Description
mcinstall
The password
is initially
configured
during the
installation.
root
The installation process requires you to create mcinstall as the MCMU primary
administrator and create a password. This account is intended to be the primary
administrator for the MCMU.
This user account is used for these activities:
■ Performing the system initialization at installation time by running installmc.
■ Administering the system, including VMs using the MCMU BUI and mcmu CLI.
■ To assume the root role (su to root) on application VMs and in the global zone
and kernel zones for superuser privileges.
MCMU
Supervisor –
Account name
determined at
installation time
The password
is configured
during the
installation.
root
(Optional)
Tenant Admin –
Account name
determined at
user registration
time
Determined
upon initial log
in.
tadmin
oracle
Set during
the DB VM
group profile
root
38
In the MiniCluster software, the supervisor user is only intended to approve or deny
MCMU users as they are created and deleted.
This user receives email every time a new MCMU user is created. The new user
must be approved by the supervisor and the primary admin (such as mcinstall) for
the user account to be enabled.
This user can perform all post-installation activities only on VMs.
This user cannot access the global or kernel zones, and cannot run the MCMU BUI
or CLI.
Note - If the user is created with the MCMU CLI, the role is identified as
tenant_admin.
Each DB VM has an individual oracle user account. This user account is used for
these activities:
Oracle MiniCluster S7-2 Administration Guide • March 2017
MCMU Password Policies
User
Password
Role
configuration.
See
“Password” on page 70
Note - Until
the DB VM
group profile
is created, the
password is the
same as for the
mcinstall user.
Description
■ Used as the initial login account to database VMs, from which you can
configure the database VMs with a database, data, and other accounts, as
needed.
■ To assume the root role (su to root) on database VMs for superuser privileges.
The default MCMU password that is used on the first login is welcome1. Once welcome1
is entered, the utility forces the user to create a new password that adheres to the password
policies. See “MCMU Password Policies” on page 39.
All actions performed by all MCMU users are logged based on the user's identifier.
Note - MCMU user accounts are not used for the routine use of the system, such as using
the applications and databases. Those user accounts are managed through Oracle Solaris, the
application, the database on the VMs, and through your site's name services.
MCMU Password Policies
When an MCMU user logs into MCMU for the first time, the utility requires the user to create a
password that meets these requirements:
■
■
■
■
■
■
Must contain a minimum of 14 characters (or 15 for DISA STIG Profile configurations)
Must have a minimum of one numeric character
Must have a minimum of one uppercase alpha character
(DISA STIG Profile configurations) Must include one non-alpha-numeric character
Must differ from a previous password by at least three characters
Must not match the previous ten passwords
MCMU User Approval Process Overview
All MCMU user accounts require approval by the MCMU supervisor and primary admin
(mcinstall). The process works as follows:
Managing MCMU User Accounts (BUI)
39
Display MCMU Users (BUI)
1. The prospective user (or an MCMU user on their behalf) accesses the MCMU registration
page and provides these mandatory details:
MCMU user name
■ Email address
■ Full name
■ Phone number
■ MCMU role
2. MCMU sends the MCMU supervisor and primary admin an email requesting approval or
denial.
■
If the user was registered through the MCMU BUI, the email includes a URL to the MCMU
approval/denial feature and includes a unique key identifier.
If the user was created through the MCMU CLI, the email includes an mcmu command and
the unique key identifier.
3. When both the supervisor and primary admin approve the account, the user account is
enabled, and MCMU sends the new user and email confirming the account activation.
Subsequent topics in this section describe how to perform these tasks.
Display MCMU Users (BUI)
1.
Access the MCMU BUI as a primary admin, such as mcinstall.
See “Log in to the MCMU BUI” on page 26.
2.
In the navigation panel, select System Settings → User Accounts.
The User Summary page is displayed.
The page provides this information:
40
Oracle MiniCluster S7-2 Administration Guide • March 2017
Create a New MCMU User (BUI)
■
■
■
■
■
■
■
■
User name – The user account name.
Role – The role assigned to the user. See “User Roles” on page 37.
Status – Lists the status. Active indicates an approved user.
Date Joined – Lists the date that the user account was approved.
Last Login – Lists the date that the user last logged into MCMU.
Email – Lists the user's email address.
Phone – Lists the user's phone number.
Supervisor – Lists the MCMU supervisor that approved the user.
Create a New MCMU User (BUI)
Use this procedure to create MCMU users.
1.
Access the MCMU BUI.
See “Log in to the MCMU BUI” on page 26.
2.
Click the Register button.
Managing MCMU User Accounts (BUI)
41
Create a New MCMU User (BUI)
The MCMU Registration page is displayed.
3.
Complete the MCMU registration page.
Fields marked with an asterisk are mandatory.
42
Oracle MiniCluster S7-2 Administration Guide • March 2017
Approve or Reject a New User (BUI)
Specify these items:
■
■
■
■
■
■
■
■
■
User name – Enter a unique user name for the new user.
Email – Enter the email address for the new user.
Title – (Optional) Enter the user's title.
Full Name – Enter the first and last name for the new user.
Organization – (Optional) Enter the user's organization.
Department – (Optional) Enter the new user's department.
Phone Number – Enter the new user's phone number. Do not include any special characters
or spaces.
Address – (Optional) Enter the new user's address.
Type of User – See “User Roles” on page 37 and select one of the following:
■
■
■
■
4.
Primary admin
Secondary admin
Tenant admin
Auditor admin
Click Register.
The account is created, but is not activated until the new user is approved by the primary admin
and supervisor (accounts created during the initial installation). The utility sends the primary
admin and supervisor an email that includes a secure key that is used to approve the user. See
“Approve or Reject a New User (BUI)” on page 43.
Once the primary admin and supervisor approve the account, the new user receives email with
a link to the MCMU BUI. Upon the first login, the new user is forced to create a password
according to the password policies. See “MCMU Password Policies” on page 39.
Approve or Reject a New User (BUI)
Before a new account is enabled, the MCMU primary admin and supervisor must both approve
the new user. See “User Accounts” on page 38.
1.
As the MCMU primary admin or supervisor, obtain the MCMU approval email.
The email is sent from mcinstall@company-name.
2.
In the email, click the approval link (or copy it into a browser).
The MCMU approval page is displayed.
3.
Click Approve or Reject, then click Submit.
Managing MCMU User Accounts (BUI)
43
Change an MCMU User Password (BUI)
For example:
MCMU sends email to the user either confirming account activation, or denial.
Change an MCMU User Password (BUI)
Note - The first time a user logs into MCMU, the utility requires the user to enter a new
password.
1.
Open a browser on a system that has network access to MiniCluster.
2.
Type https://node1_name/MCMU in the browser address field.
Replace node1_name with the name of the MiniCluster compute node 1.
3.
In the login page, enter your user name and password.
4.
In the upper right corner, click on your user name and select Change Password.
5.
Enter a new password twice, and click Change Password.
Reset an MCMU User Password (BUI)
Note - The first time a user logs into MCMU, the utility requires the user to enter a new
password.
44
Oracle MiniCluster S7-2 Administration Guide • March 2017
Reset an MCMU User Password (BUI)
1.
Open a browser on a system that has network access to MiniCluster.
2.
Type https://node1_name/MCMU in the browser address field.
Replace node1_name with the name of the MiniCluster compute node 1.
3.
On the login page, enter your user name and password.
4.
Click Reset Password.
5.
Enter your user name and click Reset.
Email is sent to the MCMU supervisor and primary admin to approve or deny the reset. Once
both approvals are submitted to MCMU, you receive an email with a link to MCMU.
6.
Obtain the email approving the password reset.
The email is sent to you from mcinstall@mcmu_domainname.
7.
Log into MCMU with your user name and a password welcome1.
Managing MCMU User Accounts (BUI)
45
Delete a User Account (BUI)
The utility requires you to provide a new password.
8.
Enter a new password twice and click Change Password.
Delete a User Account (BUI)
Use this procedure to delete a user account. You must know the user name and password
to delete an account through the BUI. The primary admin and supervisor must approve the
deletion though email sent from MCMU.
Note - Alternatively, you can delete a user account using the MCMU CLI. See “Delete an
MCMU User (CLI)” on page 265
1.
Log into the MCMU BUI as the user you plan to delete.
See “Log in to the MCMU BUI” on page 26.
2.
46
In the upper right corner, access the drop-down menu under the user name, and
select Delete Account.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Change a User Profile (BUI)
The MCMU Delete Account page is displayed.
3.
Enter your password and click Request Deletion.
Once the deletion request is approved by the primary admin and supervisor, the account is
deleted.
Change a User Profile (BUI)
1.
Log into the MCMU BUI as the user that you plan to change.
See “Log in to the MCMU BUI” on page 26.
2.
In the upper right corner, access the drop-down menu under the user name and
select Edit Profile.
The user registration page is displayed.
3.
Enter changes into the registration page.
4.
Click Save.
Managing MCMU User Accounts (BUI)
47
48
Oracle MiniCluster S7-2 Administration Guide • March 2017
Starting and Stopping the System
These topics describe how to start and stop App and DB components, and how to power on and
off the system.
■
■
“Start the System” on page 49
“Shut Down, Reset, or Power Cycle the System” on page 50
Start the System
This procedure assumes that power is applied to the system, but the compute nodes are shut
down (the system is in standby mode). For instructions on how to connect the system to power,
refer to the MiniCluster S7-2 Installation Guide.
For additional information about Oracle ILOM, refer to the Oracle ILOM documentation at:
http://docs.oracle.com/cd/E37444_01.
1.
On a system with network access to MiniCluster, log into Oracle ILOM as root
using one of these methods:
Note - Start node 1 first because the MCMU is on node 1.
■
Oracle ILOM web interface – In a browser, enter this address, and press
Return:
http://ILOM_hostname_or_ipaddress
The Oracle ILOM Login screen is displayed. Log in using your Oracle ILOM root account
and password.
■
Oracle ILOM CLI – In a terminal window, enter:
% ssh root@ILOM_hostname_or_ipaddress
root password: ********
Starting and Stopping the System
49
Shut Down, Reset, or Power Cycle the System
->
2.
Perform one of these actions:
■
Oracle ILOM web interface – Click Host Management → Power Control and
select Power On from the Select Action list.
■
Oracle ILOM CLI – Enter this command:
-> start /System
3.
Repeat this procedure to boot the other compute node.
4.
(Optional) If you are using the Oracle ILOM CLI and you want to connect to the
host from Oracle ILOM, start the host console:
-> start /HOST/console
Log into the compute node with valid credentials.
As the compute node boots, messages are displayed on the host console.
5.
Verify the state of the VM components.
See:
■
■
“Obtaining Status (CLI)” on page 205
“View System Information (BUI)” on page 54
When booting is complete, all the configured VMs are available for use. If for some reason
any of the VMs are not running, you can manually start them. See “Starting VM Components
(CLI)” on page 215.
Shut Down, Reset, or Power Cycle the System
Caution - If the system is not properly shutdown, data corruption can occur.
1.
Notify affected users that the server will be shut down.
2.
Save any open files and quit all running programs.
3.
Log into one of the nodes as an MCMU administrator such as mcinstall.
Do not assume the root role.
50
Oracle MiniCluster S7-2 Administration Guide • March 2017
Shut Down, Reset, or Power Cycle the System
See “Log in to the MCMU CLI” on page 29.
4.
Stop the DB grid infrastructure.
Use this syntax:
% mcmu stop -G -n VMgroupname
where VMgroupname is the name of the DB VM group. To determine the name, see “List a
Summary of All DB VM Groups (CLI)” on page 188.
For example:
% mcmu stop -G -n dbgrp1
5.
Stop the GI in the kernel zones.
Use this syntax:
% mcmu stop -G -k nodex
where x is 1 or 2.
For example:
% mcmu stop -G -k node1
% mcmu stop -G -k node2
6.
Stop all DB and App VMs in all groups.
Repeat this command for all groups on the system (one DB VM group, and any number of App
VM groups).
Use this syntax:
% mcmu stop -V -n VMgroupname
where VMgroupname is the name of the VM group. To determine the name, see “List a
Summary of All DB VM Groups (CLI)” on page 188.
For example:
% mcmu stop -V -n vm2
MCMU stops each VM in the group one by one. You are prompted to confirm the stopping of
each VM in the group.
If your system has more than one App VM group, stop all of them.
7.
Stop the kernel zones.
Use this syntax:
Starting and Stopping the System
51
Shut Down, Reset, or Power Cycle the System
% mcmu stop -Z -k nodex
where x is 1 or 2.
Stop the kernel zone on each node, type:
% mcmu stop -Z -k node1
% mcmu stop -Z -k node2
8.
(Optional) Verify that all the VM components are stopped on the compute nodes.
See:
■
■
9.
“Obtaining Status (CLI)” on page 205
“View System Information (BUI)” on page 54
From a system with network access to MiniCluster, log into Oracle ILOM on a
MiniCluster compute node as root using one of these methods:
■
Oracle ILOM web interface – In a browser, enter this address, and press
Return:
http://ILOM_hostname_or_ipaddress
The Oracle ILOM Login screen is displayed. Log in using your Oracle ILOM root account
and password.
■
Oracle ILOM CLI – In a terminal window, enter:
% ssh root@ILOM_hostname_or_ipaddress
root password: ********
->
■
Perform one of these actions:
■
Oracle ILOM web interface – Click Host Management → Power Control
and select the desired operation. For example, select Reset.
■
Oracle ILOM CLI – Enter this command:
-> stop /System
52
10.
Repeat Step 9 to stop the other compute node.
11.
Verify the state of the system.
See “View System Information (BUI)” on page 54
Oracle MiniCluster S7-2 Administration Guide • March 2017
Obtaining System Information (BUI)
These topics describe how to get system information using the MCMU BUI.
■
■
■
■
■
“Display the MCMU Version (BUI)” on page 53
“View System Information (BUI)” on page 54
“View and Update Network Configuration Information (BUI)” on page 56
“Review or Run Initialization Steps (BUI)” on page 58
“View the Status of Running Tasks (BUI)” on page 60
Display the MCMU Version (BUI)
1.
Access the MCMU BUI.
See “Log in to the MCMU BUI” on page 26.
2.
In the upper right corner, click on your user name and select About.
Obtaining System Information (BUI)
53
View System Information (BUI)
The About window is displayed, showing the version of MCMU:
For additional information about software versions, select System Settings → System
Information as described in “View System Information (BUI)” on page 54.
View System Information (BUI)
Use this procedure to view specific information about the system, its components, and their
current state.
1.
Access the MCMU BUI.
See “Log in to the MCMU BUI” on page 26.
2.
54
In the System Status page, view the system status.
Oracle MiniCluster S7-2 Administration Guide • March 2017
View System Information (BUI)
For example:
The System Status panel provides this information:
■
■
■
■
■
■
■
System Status – Shows a brief status of the system.
Core Usage – Shows the percentage of used and unused cores.
Virtual Machines – Shows the percentage of VMs that are online and offline.
Database Instances – Shows the percentage of DB instances that are online and offline.
Silicon Secured Memory – Indicates whether the feature is functioning on each compute
node or not.
Database Accelerator Engine – Indicates whether the feature is functioning on each
compute node or not.
SPARC Hardware Assisted Cryptography – Indicates whether the feature is functioning
on each compute node or not.
Note - For descriptions of MiniCluster features, refer to the product page at https://www.
oracle.com/engineered-systems/supercluster/minicluster-s7-2/features.html.
3.
In the navigation panel, select System Settings → System Information.
Obtaining System Information (BUI)
55
View and Update Network Configuration Information (BUI)
The Software and OS Information page is displayed.
For example:
This page displays this information:
■
■
■
Software and OS Information – Shows the MCMU and Oracle Solaris OS versions.
System Information – Shows the compute node hostnames, Oracle ILOM hostnames,
number of cores, memory, and state.
Storage Information – Shows statistics about the storage array. Click the triangle to
expand.
View and Update Network Configuration Information
(BUI)
1.
Access the MCMU BUI.
See “Log in to the MCMU BUI” on page 26.
2.
In the navigation panel, select System Settings → User Input Summary.
This page shows hostname and network parameters that were configured during the initial
installation.
56
Oracle MiniCluster S7-2 Administration Guide • March 2017
View and Update Network Configuration Information (BUI)
For example:
Obtaining System Information (BUI)
57
Review or Run Initialization Steps (BUI)
3.
(If needed) Add additional IP addresses.
When the system was installed, groups of IP addresses were added to the system for the future
creation of VMs. If those addresses have been consumed, and you need more addresses,
perform these steps.
4.
a.
Under Add IP Range, enter the starting IP address and IP address range.
b.
Click Add.
To see the DB VM hostnames and IP addresses, perform these steps:
a.
Go to the Database → Virtual Machine Group Profile page.
b.
Click the Edit button.
The edit page lists the VM hostname (public hostname) and the associated public IP
address for each database VM.
c.
5.
At the bottom of the page, click Cancel.
To see the application VM hostnames and IP addresses, perform these steps:
a.
Go to the Application → Virtual Machine Group Profile page.
b.
Click the Edit button for an application group.
The edit page lists the VM hostname (public hostname) and the associated public IP
address for each VM.
c.
At the bottom of the page, click Cancel.
Review or Run Initialization Steps (BUI)
Use this procedure to review the status of the initialization steps that were run when the system
was initially installed.
You can also use this procedure to rerun the initialization steps.
For more information about the initialization process, refer to the Oracle MiniCluster S7-2
Installation Guide.
1.
58
Access the MCMU BUI as a primary admin, such as mcinstall.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Review or Run Initialization Steps (BUI)
See “Log in to the MCMU BUI” on page 26.
2.
In the navigation panel, select System Settings → System Setup.
The System Setup page is displayed.
For example:
The initialization steps are listed with a status of finished or not finished.
3.
If needed, run initialization steps.
■
Click an individual step Run button to run the step.
■
Click Run all steps to automatically run all the steps.
Obtaining System Information (BUI)
59
View the Status of Running Tasks (BUI)
As each step runs, the status is updated.
View the Status of Running Tasks (BUI)
Use this procedure to view that status of the tasks that the utility is performing.
1.
Access the MCMU BUI as a primary admin, such as mcinstall.
See “Log in to the MCMU BUI” on page 26.
2.
In the navigation panel, select Tasks.
The Current Action Queue page is displayed.
If the current action queue is empty, no tasks are currently being performed by the utility.
For example:
3.
60
For additional details about the activity, click the Detail button.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Planning to Create VMs
These topics provide information about planning the configuration of VMs.
Description
Links
Plan the overall configuration.
“Configuration Planning Overview” on page 61
Plan DB VMs.
“DB VM Planning Worksheets (Optional)” on page 62
“DB VM Group Parameters” on page 65
“DB VM Parameters” on page 69
“DB Home Parameters” on page 72
“DB Instance Parameters” on page 73
Plan App VMs.
“App VM Planning Worksheets (Optional)” on page 77
“App VM Group Parameters” on page 78
Configuration Planning Overview
You can create, edit, and delete DB and App VMs at any time. However, if you want to plan for
the overall configuration of the system, make these decisions:
Note - If you are not sure exactly how many VMs to create, you can skip the planning, create
VMs to see how it works, then edit, delete and recreate VMs until you have the configuration
that meets your needs.
1. Determine if VMs have already been created on the system.
The MiniCluster installation process automatically prompts the installer to create VMs.
DB VMs – See “View the DB VM Group and VMs (BUI)” on page 83.
■ App VMs – See “View App VM Groups and VMs (BUI)” on page 119.
2. Determine the number of DB VMs and App VMs to create, keeping these points in mind:
■
Planning to Create VMs
61
DB VM Planning Worksheets (Optional)
■
■
■
Total VMs – You can create a maximum of 12 VMs on each node (24 total).
Number of DB VMs – You can configure a maximum of 4 DB VMs on each node (8
total).
Number of App VMs – The maximum number of App VMs per node is 12 minus the
number of DB VMs you plan to have.
One example – On each node, if you create 4 DB VMs, therefore you can create a total
of 8 App VMs per node.
Another example – On each node, If you create 1 DB VM, therefore you can create a
total of 11 App VMs per node.
Note - As you create VMs. MCMU keeps track of used resources and only enables you to
create VMs and assign cores that are available.
You do not need to plan to use all the resources at one time. If resources are available, you
can add more VMs later.
3. Determine how the VMs will be grouped.
VMs in a group share certain resources such as database installations, shared storage, and
so on. For further details, see “DB VM Group Parameters” on page 65 and “App VM
Group Parameters” on page 78.
DB VMs – All the DB VMs are automatically created in one DB VM group, and only
one group is supported.
■ App VMs – You can include one or two (one on each node) App VMs in a group. You
can have as many App VM groups as there are resources to support them.
4. Determine the details for each VM.
■
Details include things like number of cores, hostnames, database versions, instance
configurations, and more. For a list of configuration details, review these planning
worksheets:
■
■
DB VMs – See “DB VM Planning Worksheets (Optional)” on page 62.
App VMs – See “App VM Planning Worksheets (Optional)” on page 77.
DB VM Planning Worksheets (Optional)
You can use these planning worksheets to plan the creation of DB VMs, and to anticipate the
configuration information that you are asked to provide.
For more details about a particular parameter, click the parameter.
62
Oracle MiniCluster S7-2 Administration Guide • March 2017
DB VM Planning Worksheets (Optional)
TABLE 1
Worksheet for a DB VM Group Profile and Cluster
Parameter
Your Value
“VM Group Profile Name” on page 65
1 - 12 lowercase alpha/numeric and - (hyphen)
characters
“Shared Storage” on page 66
No or Yes
“Security Profile” on page 66
CIS equivalent, PCI-DSS, or DISA STIG
“ASM Redundancy” on page 66
Normal or High
Node 1:
“Number of VMs on Each
Node” on page 67
Node 2:
0 - 4 per node
“Role Separation” on page 67
No or Yes
“Group Description” on page 69
Optional descriptive text
TABLE 2
Worksheet for DB VMs, Homes, and Instances
Parameter
Node 1
VM 1
Node 2
VM 2
VM 3
VM 4
VM 1
VM 2
VM 3
VM 4
“Public
Hostname” on page 69
1-25 lowercase alpha/
numeric and - (hyphen)
characters
“Number of
Cores” on page 70
If assigned:
1 - 12 max. cores
available per node for
both DB and APP VMs
For a VM to use shared
cores, specify 0 (zero).
“Password” on page 70
oracle
Planning to Create VMs
63
DB VM Planning Worksheets (Optional)
Parameter
Node 1
VM 1
Node 2
VM 2
VM 3
mcinstall
CLUSTER
PARAMETERS
“SCAN
Name” on page 70
for the cluster.
“System Disk
Group” on page 71
Normal or High
“DATA/RECO
Disk Group
Split” on page 71
HOME PARAMETERS
“Oracle Database
Version” on page 72
11g,12c, or 12c SE
Note - Create one home
for each DB version you
need.
Note - 12c SE can only
be configured as a single
instance. and must be
downloaded from MOS.
Version for the first home:
(Optional) Versions for additional homes:
INSTANCE
PARAMETERS
“New Instance or
Import Existing
Instance” on page 74
“Template
Type” on page 74
DW, OLTP, or Custom
“Instance
Type” on page 74
Single, RAC, or RACONE-Node
“Database Instance
Version” on page 76
“Container
DB” on page 76
Y/N
64
Oracle MiniCluster S7-2 Administration Guide • March 2017
VM 4
VM 1
VM 2
VM 3
VM 4
DB VM Group Parameters
Parameter
Node 1
VM 1
Node 2
VM 2
VM 3
VM 4
VM 1
VM 2
VM 3
VM 4
“PGA Memory
Space” on page 77
Default or custom value
in MB
“SGA Memory
Space” on page 77
Default or custom value
in MB
“Character
Sets” on page 77
Select from menu
“Instance
Name” on page 77
1 - 8 lowercase alpha/
numeric characters
DB VM Group Parameters
This section describes the parameters you define when you create a DB VM group profile. Use
this information in conjunction with these activities:
■
■
Planning DB VMs, described in “DB VM Planning Worksheets (Optional)” on page 62
While creating DB VM group profile with the MCMU BUI, described in “Create a DB VM
Group Profile (BUI)” on page 87, or CLI described in “Create a DB VM Group Profile
(CLI)” on page 229
VM Group Profile Name
The VMs are logically grouped (see “MiniCluster VM Groups and VMs Overview” on page 21.
During the configuration process, you specify a group profile name of your choice. The name
can be up to 12 characters, and can contain lowercase letters, numbers, and the - (hyphen)
symbol. Later, the VM group name is automatically used as a prefix in the VM hostnames, so
specifying a short name can lead to shorter VM names.
Planning to Create VMs
65
DB VM Group Parameters
Shared Storage
All DB VMs are allocated with storage space (the amount of storage depends on the type of
instances configured in the VM). The shared storage provides additional storage, if enabled.
6 HDDs on each storage array are set aside for additional storage space (see “MiniCluster
Storage Overview” on page 23).
■
■
If enabled – All the VMs in the group have access to the shared storage.
If disabled – The VMs will not have access to the shared storage space in the 6 HDDs.
Note - After the creation of VMs, you can enable or disable access to the shared storage at any
time. See “Enable or Disable Shared Storage (BUI)” on page 135.
Security Profile
You define a security profile that is applied to the VMs in the group. The security profile
automatically configures the system with over 225 security controls. The choices are:
■
■
■
CIS Equivalent Profile – Satisfies requirements comparable and equivalent to benchmarks
set forth by the Center for Internet Security (CIS) and Security Technical Implementation
Guidelines (STIG) assessments.
PCI-DSS Profile – Complies with the Payment Card Industry Data Security Standard (PCI
DSS) standard defined by the Payment Card Industry Security Standards Council.
DISA STIG Profile – Includes all the security features of the CIS equivalent Security
profile and provides 75 additional security controls. This profile also includes FIPS-140-2
cryptography.
Note - If the system is configured with the DISA STIG profile (performed during the
installation), all VMs that are subsequently created should also be configured with the DISA
STIG profile.
ASM Redundancy
Defines the level of redundancy that you want applied to database VMs. All the VMs in the
group are configured with the same type of redundancy The choices are:
66
Oracle MiniCluster S7-2 Administration Guide • March 2017
DB VM Group Parameters
■
■
Normal – Provides protection against a single disk failure.
High – Provides protection against two disk failures.
Number of VMs on Each Node
You choose between zero to four VMs on each node for a maximum of eight DB VMs. For
Oracle RAC configurations, ensure that you specify VMs on each node.
You can always change the number of VMs later. See “Add a DB VM to a Group
(BUI)” on page 108.
Role Separation
This feature enables you to create a single administrative user, or to create two separate
DB administrative users with separate roles (separating ASM administration from RDBMS
administration). Separate roles might be required by certain third-party applications.
If you choose to create one administrative user, that user is the Oracle DB Installation user for
all Oracle DB software and is a member of the groups needed to perform administration of the
grid infrastructure and to administer the DB.
If you choose role separation, two users are created, each a member of different groups so that
each user is only able to administer either the ASM grid infrastructure, or the DB.
Based on your selection, the utility automatically provides industry standard values for user and
group names, IDs, and file system base.
■
No – Configures one DB administrative user (oracle) with privileges to administer the
ASM and RDBMS. These pre-assigned fields are displayed:
User Name and Base
■
Name — oracle
■
ID — 1001
■
Base — /u01/app/oracle
DBA Group
■
Name — dba
■
ID — 1002
Planning to Create VMs
67
DB VM Group Parameters
OINSTALL Group
■
Name — oinstall
ID — 1001
Yes – Enables role separation, and configures these pre-assigned DB administrator users and
roles.
■
■
Grid ASM Home OS User and Base
■
Name — oracle
■
ID — 1001
■
Base — /u01/app/oracle
ASM DBA Group
Membership in this group enables access to the files managed by Oracle ASM.
■
Name — asmdba
■
ID — 1004
ASM Home Oper Group
This group of operating system users has a limited set of Oracle instance administrative
privileges including starting up and stopping the Oracle ASM instance.
■
Name — asmoper
■
ID — 1005
ASM Home Admin Group
This group uses SQL to connect to an Oracle ASM instance as SYSASM using operating
system authentication. The SYSASM privileges permit mounting and dismounting of disk
groups, and other storage administration tasks. SYSASM privileges provide no access
privileges on an Oracle Database instance. The SYSASM privileges permit mounting and
dismounting of disk groups, and other storage administration tasks. SYSASM privileges
provide no access privileges on an Oracle Database instance.
■
Name — asmadmin
■
ID — 1006
RDBMS Home OS User and Base
■
Name — oracle
■
ID — 1000
■
Base — /u01/app/oracle
RDBMS DBA Group
■
68
Name — dba
Oracle MiniCluster S7-2 Administration Guide • March 2017
DB VM Parameters
■
ID — 1002
RDBMS Home Oper Group
■
Name — oper
■
ID — 1003
ASM Home Admin Group
■
Name — oinstall
■
ID — 1001
Group Description
You can leave the field blank, or add a description that briefly describes the DB VM group.
DB VM Parameters
This section describes the DB VM parameters you define while creating the DB VM group
profile. Use this information in conjunction with these activities:
■
■
Planning DB VMs, described in “DB VM Planning Worksheets (Optional)” on page 62
While creating DB VM group profile with the MCMU BUI, described in “Create a DB VM
Group Profile (BUI)” on page 87, or CLI described in “Create a DB VM Group Profile
(CLI)” on page 229
Public Hostname
For each VM, specify a unique hostname. This is the name that you add to your DNS. It is the
hostname that is used for client access to the VM.
The hostname can be up to 25 alpha-numeric characters and include the - (hyphen) symbol.
Planning to Create VMs
69
DB VM Parameters
Number of Cores
For each VM, specify the number of cores (0 - 12). Before the creation of VMs, there are 24
cores available (12 on each node that are available for VMs). MCMU keeps track of how many
cores are assigned to VMs and only enables you to select a number from what is available.
Cores that are not assigned to VMs are pooled together and are available as shared cores.
If you select 0 (zero) cores, the VM uses shared cores.
After the DB VM group is deployed, you can change the number of cores on the VMs. See
“Edit a DB VM Group Profile (BUI)” on page 105.
Password
For each VM, set a password for the oracle user and mcinstall user.
If you select Use Default Password, MCMU sets the password to welcome1.
For details about MCMU users, see “User Accounts” on page 38.
Password policies vary based on the security profile that was selected. See “MCMU Password
Policies” on page 39 and “Security Profile” on page 66.
SCAN Name
When you create database clusters, the VMs from both compute nodes are clustered together.
Provide a SCAN name for the database cluster that you are setting up.
Single Client Access Name (SCAN) is a feature used in Oracle RAC configurations. The SCAN
provides a single name for clients to access any database running in a cluster. MCMU provides
a default SCAN, or you can specify your own name. The SCAN must be a name that is up to 15
characters long. You can use lowercase letters, numbers and the - (hyphen) symbol.
GI Patch Level
The MCMU BUI provides a drop-down list of patch levels that you can choose.
70
Oracle MiniCluster S7-2 Administration Guide • March 2017
DB VM Parameters
System Disk Group
Select the level of redundancy that you want for the Oracle Cluster Registry (OCR) voting disk
group, or SYSTEM disk group. The choices are:
■
■
Normal – Provides three voting disks.
High – Provides five voting disks.
Data Disk Group
In the Define Cluster page, the data disk group redundancy level is displayed. The value is
based on what was selected for “ASM Redundancy” on page 66 in a previous page.
DATA/RECO Disk Group Split
You can configure the percentage of storage that the DATA disk group and RECO disk group
use. The default is 80% DATA, 20% RECO.
Use the slider to assign percentage values in 10% increments.
Note - The percentage number shown is the amount for DATA, with the remaining percentage
applied to RECO.
REDO Disk Group
In the Define Cluster page, the REDO disk group redundancy level is displayed. This disk
group is always configured for high redundancy (provides protection against two disk failures).
RECO Disk Group
In the Define Cluster page, the RECO disk group redundancy level is displayed. The value is
based on what was selected for “ASM Redundancy” on page 66 in a previous page.
Planning to Create VMs
71
DB Home Parameters
DB Home Parameters
This section describes the parameters you define while creating the DB VM homes. Use this
information in conjunction with these activities:
■
■
Planning DB VMs, described in “DB VM Planning Worksheets (Optional)” on page 62
While creating a DB VM home with the MCMU BUI, described in “Create DB Homes
(BUI)” on page 99, or CLI described in “Create DB Homes (CLI)” on page 234
Oracle Database Version
When you configure a database home, you are provided with a choice of Oracle Database 11g,
12c Enterprise Edition, or 12c Standard Edition (the latter only supports a single instance).
The Oracle Database 11g and 12c Enterprise Edition are automatically available to install in
DB VM homes because they were downloaded to MiniCluster during the installation process.
Oracle Database 12c Standard Edition (12c SE), must be downloaded separately from MOS.
Each home provides one database version, but you can install multiple homes in a DB VM
group. The DB homes you create determine the specific versions of the Oracle Database that are
available to each DB instance.
Once the DB home is created, the utility allocates these resources for each DB VM:
■
■
■
■
ZFS root file system – 40 GB.
Database directory – 100 GB ZFS file system mounted on /u01.
DB REDO Logs – Configured for high redundancy on the storage array.
Client network – 1 virtual network.
This figure shows an example of a DB VM group with two DB homes.
72
Oracle MiniCluster S7-2 Administration Guide • March 2017
DB Instance Parameters
Oracle Home Path
Is the directory path for the Oracle Database. The default is /u01/app/oracle/
product/release_number/dbhome_number. Accept the default or change the name used for the
dbhome_number.
Patch Level
Select a version from the drop-down menu.
DB Instance Parameters
This section describes the parameters you define while creating the DB VM instances. Use this
information in conjunction with these activities:
■
■
Planning DB VMs, described in “DB VM Planning Worksheets (Optional)” on page 62
While creating instances with the MCMU BUI, described in “Create DB Instances
(BUI)” on page 101, or CLI described in “Create DB Instances (CLI)” on page 236
Planning to Create VMs
73
DB Instance Parameters
New Instance or Import Existing Instance
Select an option from the drop-down list. If you choose to create a new instance, MCMU
creates the instance.
If you choose to import an existing instance, you specify another instance on the system that
will be used to create this instance. The instance must be an instance that was not created using
MCMU. You are prompted to enter this information and click Import:
■
■
■
Instance name – Specify the name of the non-MCMU-created instance that will be used to
create this instance.
Instance user name – Specify the name of a user that will have access to this DB instance.
Instance password – Specify the user's password.
Template Type
For each DB instance, you define the type of DB by selecting a type from the pull-down menu:
■
■
■
DW — Creates a data warehouse type database, commonly used for analytic workloads.
OLTP — Creates an online transaction processing type database, commonly used for
business transaction workloads.
Custom — If selected, you are prompted to browse to a DB template that you provide.
Instance Type
For each DB instance, you define the type of instance by selecting a type from the pull-down
menu:
■
■
■
Single — Creates a single database instance on one VM on one compute node. This is the
only choice for Oracle Database 12c Standard Edition.
RAC — Creates an active-active clustered database instance (two VMs) across both
compute nodes.
RAC One Node — Creates an active-passive clustered database instance (two VMs) across
both compute nodes.
These figures illustrate some examples.
74
Oracle MiniCluster S7-2 Administration Guide • March 2017
DB Instance Parameters
FIGURE 1
Single Instance Example
Planning to Create VMs
75
DB Instance Parameters
FIGURE 2
RAC Instance Example
Database Instance Version
If multiple homes were created, you select the version of the Oracle Database for this instance.
If only one home was created, MCMU automatically uses the database version that is available.
Container DB
This feature enables a single container database to host multiple separate pluggable databases. If
you are installing Oracle Database 12c, you can select this option.
76
Oracle MiniCluster S7-2 Administration Guide • March 2017
App VM Planning Worksheets (Optional)
PGA Memory Space
You have the option to specify the size of the PGA (memory for the server processes for the
instance), or accept the default value.
SGA Memory Space
You have the option to specify the size of the SGA (memory shared by the processes in the
instance), or you can accept the default value
Character Sets
You have the option to assign the database and national character sets for the instance. If you
choose the Recommended option, MCMU assigns the character set.
Instance Name
Each instance must be named. Specify a unique name that is up to 8 characters long. You can
use alpha and numeric characters (no special characters).
App VM Planning Worksheets (Optional)
You can use these planning worksheets to plan the creation of App VMs, and to anticipate the
configuration information that you are asked to provide.
For more details about a particular parameter, click the parameter.
TABLE 3
Worksheet for an App VM Group Profile
Parameter
Your Value
“VM Group Profile Name” on page 79
Planning to Create VMs
77
App VM Group Parameters
Parameter
Your Value
1 - 12 lowercase alpha/numeric and - (hyphen)
characters
“Description” on page 79
Optional descriptive text
“Number of VMs” on page 79
pair or single
“Shared Storage” on page 79
Y/N
“VM Type” on page 80
Oracle Solaris 11 or Oracle Solaris 10
“Enable Security” on page 80
(only applies to Oracle Solaris 10 VMs) JASS or
none
TABLE 4
Worksheet for App VMs
Parameter
App VM 1
App VM 2
“Public Hostname” on page 81
“Cores” on page 81
If assigned:
1 - 12 max. cores available per node (for both DB
and APP VMs)
For a VM to use shared cores, specify 0 (zero).
Plan to set a “Password” on page 81 for the
oracle and mcinstall users on this VM.
“Define Cluster” on page 82 Y/N
If yes, provide a SCAN.
App VM Group Parameters
This section describes the parameters you define when you create an App VM group profile.
Use this information in conjunction with these activities:
■
78
Planning App VMs, described in “App VM Planning Worksheets
(Optional)” on page 77
Oracle MiniCluster S7-2 Administration Guide • March 2017
App VM Group Parameters
■
While creating App VM group profile with the MCMU BUI, described in “Create an App
VM Group Profile (BUI)” on page 121, or CLI described in “Configuring Application
VMs (CLI)” on page 255
VM Group Profile Name
During the configuration process, you specify a group profile name of your choice. The name
can be up to 12 characters, and can contain lowercase letters, numbers, and the - (hyphen)
symbol. Later, the VM group name is automatically used as a prefix in the VM hostnames, so
specifying a short name can lead to shorter VM names.
Description
You can specify an optional description of the VM group.
Number of VMs
You choose one of these options.
■
■
Pair – The utility configures two application VMs (one on each node) in the group.
Single – The utility configures one VM in the group.
Shared Storage
All App VMs are allocated with storage space. The shared storage provides additional storage,
if enabled.
6 HDDs on each storage array are set aside for additional storage space (see “MiniCluster
Storage Overview” on page 23).
■
■
If enabled – All the VMs in the group have access to the shared storage.
If disabled – The VMs will not have access to the shared storage space in the 6 HDDs.
Note - After the creation of VMs, you can enable or disable access to the shared storage at any
time. See “Enable or Disable Shared Storage (BUI)” on page 135.
Planning to Create VMs
79
App VM Group Parameters
For systems in highly secure environments, do not enable shared storage. For additional
security information, refer to the Oracle MiniCluster S7-2 Security Guide.
Security Profile
For current versions of MCMU, the security profile is automatically configured for each Oracle
Solaris 11 VM based on what was selected for the system during the initial configuration. The
following list describes the security profiles that can be selected at install time:
■
■
■
CIS Equivalent – Satisfies requirements comparable and equivalent to benchmarks set
forth by the Center for Internet Security (CIS) and Security Technical Implementation
Guidelines (STIG) assessments.
PCI-DSS – Complies with the Payment Card Industry Data Security Standard (PCI DSS)
standard defined by the Payment Card Industry Security Standards Council.
DISA STIG – Builds on the CIS Equivalent security profile and introduces 75 additional
security controls, and includes FIPS-140-2 cryptography.
VM Type
Select one of the types from the drop-down list to assign the VMs with an OS version:
■
■
Solaris 11 Native Zone – Configures Oracle Solaris 11 OS for the App VM. This is a native
OS installation because the version is the same as what is installed in the global zones.
Choose this VM type if you plan to use the App VM clustering feature.
Solaris 10 Branded Zone – (Introduced in v1.1.25) Configures Oracle Solaris 10 OS for
the App VM. This is a branded OS installation because the version is different than what is
installed in the global zones. Branded zones are usually used when applications require a
specific OS version.
Note - For two VM configurations, MCMU automatically configures both VMs with the same
VM type.
Enable Security
(Only for Oracle Solaris 10 branded zones) If selected, an Oracle Solaris 10 security service
called Java Authentication and Authorization Service (JASS) is assigned to the VMs.
80
Oracle MiniCluster S7-2 Administration Guide • March 2017
App VM Group Parameters
JASS hardens and minimizes the OS attack surface. The configuration is based on the Solaris
Security Toolkit, which enforces security controls such as RBAC, white-listed ports, protocols
and services, and ensures that unnecessary services are disabled.
For more information about JASS, refer to the JASS Reference Guide at https://docs.
oracle.com/javase/8/docs/technotes/guides/security/jaas/JAASRefGuide.html.
Note - For two VM configurations, MCMU automatically configures both VMs with or without
the security service based on your selection.
Public Hostname
For each VM, specify a unique hostname. This is the name that you add to your DNS. It is the
hostname that is used for client access to the VM.
The hostname can be up to 32 lowercase alpha-numeric characters and include the - (hyphen)
symbol.
Cores
For each VM, specify the number of cores. Before the creation of VMs, there are 24 cores
available (12 on each node that are available for VMs). MCMU keeps track of how many cores
are assigned to VMs and only enables you to select a number from what is available. If you
select 0 (zero) cores, the VM shares available cores. You can assign a different number of cores
to each VM within a group.
After the App VM group is deployed, you can change the number of cores on the VMs. See
“Edit an App VM Group (BUI)” on page 128.
Password
For each VM, set a password for the oracle and mcinstall users.
If you select Use Default Password, MCMU sets the password to welcome1.
For details about MCMU users, see “User Accounts” on page 38.
Planning to Create VMs
81
App VM Group Parameters
Password policies vary based on the security profile that was selected. See “MCMU Password
Policies” on page 39 and “Security Profile” on page 66.
Note - The default password selection only applies to Oracle Solaris 11 VMs.
Define Cluster
(Introduced in v1.1.25) If you selected the Oracle Solaris 11 VM type, MCMU BUI displays
the Define Cluster section (see “Create an App VM Group Profile (BUI)” on page 121). If
you enable Clusterware, MCMU configures the two App VMs into a cluster, providing a highly
available configuration. If one VM goes down, the system automatically fails over. You can
only cluster two App VMs.
Note - If you want to cluster Oracle Solaris 10 branded zones, you must do so manually.
To enable this feature, slide the selector to Yes, and enter a name in the SCAN name field.
Single Client Access Name (SCAN) is a feature used in cluster configurations. The SCAN
provides a single name for clients to access all VMs running in the cluster. The SCAN must
be a name that is up to 15 characters long. You can use lowercase letters, numbers and the (hyphen) symbol.
MCMU handles the configuration of the cluster, but if you want additional details, refer to the
Database Clusterware Administration and Deployment Guide at: http://docs.oracle.com/
database/121/nav/portal_booklist.htm.
82
Oracle MiniCluster S7-2 Administration Guide • March 2017
Configuring DB VMs (BUI)
Perform these tasks to view, create, edit, and delete DB VMs:
Description
Link
View the DB VM group and DB VMs.
“View the DB VM Group and VMs (BUI)” on page 83
Create database VMs.
“DB VM Creation Task Overview” on page 85
“Create a DB VM Group Profile (BUI)” on page 87
“Deploy the DB VM Group (BUI)” on page 96
“Create DB Homes (BUI)” on page 99
“Create DB Instances (BUI)” on page 101
Edit a DB VM.
“Edit a DB VM Group Profile (BUI)” on page 105
“Add a DB VM to a Group (BUI)” on page 108
Delete various DB components.
“Deleting DB Components (BUI)” on page 111
Caution - Never manually manage VMs using Oracle Solaris zone commands. Always manage
the VMs through MCMU BUI or MCMU CLI.
View the DB VM Group and VMs (BUI)
This task describes how to view DB VMs. You can also use this task to determine if DB VMs
are configured or not.
1.
Access the MCMU BUI.
See “Log in to the MCMU BUI” on page 26.
2.
In the navigation panel, select Database → Virtual Machine Group Profile.
Configuring DB VMs (BUI)
83
View the DB VM Group and VMs (BUI)
In this example, the page reports No data to display because a DB group profile has not yet
been created.
This example shows that a DB VM group profile has been created.
3.
In the navigation panel, select Database → Virtual Machine Instances.
The Database Virtual Machine Instances page is displayed.
If this page is blank, the DB group profile has not yet been created or deployed.
Tip - If the VMs are not listed, click the triangle that is next to the VM group to expand the
display. You might need to select another navigation item, then come back to this page.
84
Oracle MiniCluster S7-2 Administration Guide • March 2017
DB VM Creation Task Overview
In this example, the scroll bars are moved to the right to show the instances on the VMs. There
is one VM on each node, and each VM has one online DB instance.
DB VM Creation Task Overview
Creating DB VMs is accomplished though five main tasks:
Configuring DB VMs (BUI)
85
DB VM Creation Task Overview
Task
No.
Description
Details You Provide During the
Task
BUI Instructions
CLI Instructions
1.
Create DB VM Group Profile.
“DB VM Group
Parameters” on page 65
“Create a DB VM
Group Profile
(BUI)” on page 87
“Create a DB VM
Group Profile
(CLI)” on page 229
2.
Enter IP addresses and names in
your DNS.
MCMU provides you with the
public IP addresses and hostnames
when you create the DB group
profile.
3.
Deploy the DB VM Group.
None
“Deploy the
DB VM Group
(BUI)” on page 96
“Deploy the
DB VM Group
(CLI)” on page 232
4.
Create DB Homes in the VMs.
“DB Home Parameters” on page 72
“Create DB Homes
(BUI)” on page 99
“Create DB Homes
(CLI)” on page 234
5.
Create DB Instances in Homes.
“DB Instance
Parameters” on page 73
“Create DB Instances
(BUI)” on page 101
“Create DB Instances
(CLI)” on page 236
“DB VM Parameters” on page 69
86
Oracle MiniCluster S7-2 Administration Guide • March 2017
Create a DB VM Group Profile (BUI)
Create a DB VM Group Profile (BUI)
Perform this procedure to create a DB VM group profile.
The DB VM group provides the foundation for the DB VMs and DB instances. Before you
can create DB VMs, you must create a DB VM group. One DB VM group is supported on the
system. If a DB VM group profile already exists, you cannot create another one.
Note - It is possible that the DB VM group profile was created when the system was initially set
up. To determine if a group profile has already been created, see “View the DB VM Group and
VMs (BUI)” on page 83.
Your system must be installed and initialized as described in the Oracle MiniCluster S7-2
Installation Guide. This ensures that the required packages that contain several necessary files,
such as Oracle Solaris OS, Oracle Grid Infrastructure, and so on, are on the system.
1.
Access the MCMU BUI as a primary admin, such as mcinstall.
See “Log in to the MCMU BUI” on page 26.
2.
Ensure that the system has pool of IP addresses to apply to the DB VMs.
For each DB VM, you need 2 IP addresses. The SCAN requires 3 IP addresses.
When the system was installed, a pool of IP addresses was allocated to the system. To see the
amount of IP addresses in the pool, in the MCMU BUI, go to System Settings → User Input
Summary, and view the IP Address Pool Size.
3.
In the navigation panel, select Database → Virtual Machine Group Profile.
The Database Virtual Machine Group Profile Summary page is displayed.
Configuring DB VMs (BUI)
87
Create a DB VM Group Profile (BUI)
This example indicates that a DB group has not yet been created.
4.
Click the Create New Profile button.
The Define Profile page is displayed.
5.
In the Define DB VMs page, enter the required information, then click Next.
For details about the required information, use the optional worksheet (“DB VM Planning
Worksheets (Optional)” on page 62), or see “DB VM Group Parameters” on page 65.
Note - You do not have to have the same number of VMs on each compute node. However, if
you plan to configure all the DB VMs in RAC pairs, assign the same number of VMs to the
second compute node.
88
Oracle MiniCluster S7-2 Administration Guide • March 2017
Create a DB VM Group Profile (BUI)
This example shows the page when Role Separated is set to No.
Configuring DB VMs (BUI)
89
Create a DB VM Group Profile (BUI)
If Role Separated is set to Yes, the lower part of the page shows the users and roles that will be
configured.
6.
90
Complete the Define DB VMs page, then click Next.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Create a DB VM Group Profile (BUI)
For details about the required information, use the optional worksheet (“DB VM Planning
Worksheets (Optional)” on page 62), or see “DB VM Parameters” on page 69.
7.
Complete the Define Cluster page, then click Next.
Many of the parameters on this page are automatically populated based on the information you
provided in the earlier screens.
Configuring DB VMs (BUI)
91
Create a DB VM Group Profile (BUI)
For details about the required information, use the optional worksheet (“DB VM Planning
Worksheets (Optional)” on page 62), or see “DB VM Parameters” on page 69.
92
Oracle MiniCluster S7-2 Administration Guide • March 2017
Create a DB VM Group Profile (BUI)
8.
Verify that the information in the Review page is correct.
Configuring DB VMs (BUI)
93
Create a DB VM Group Profile (BUI)
The Review page lists all the information that you filled in from the previous pages for this DB
VM group. The information in this page is not editable.
■
If you find any issues with any of the information on the Review page, click
either the Back button to return to a previous screen, or click the Cancel
button to return to the Home page.
■
If you are satisfied with the information displayed on the Review page, click
the Generate button. A progress window is displayed:
The utility begins assigning IP addresses to the VMs based on the IP address information that
was entered during the initial installation of the system. This process can take 10 to 30 minutes
to complete, depending on the number of DB VMs specified. When the process is finished, a
screen is displayed that shows the IP mapping assignments.
9.
94
Verify that the VM group profile is correct, and note the hostnames and IP
addresses for DNS.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Create a DB VM Group Profile (BUI)
Caution - Do not click the Continue button until you have recorded all the information shown
in this Mapping IP review page.
■
If you find any issues with any of the information, close the window and
repeat this task.
■
If you are satisfied with the information displayed on the Mapping IP review
page, record all the information shown in this screen so that you can enter
the IP addresses and hostnames into DNS.
Once you have recorded all the information in the Mapping IP review page, click the Confirm
button. The utility reserves the names and IP addresses for the DB VM group.
10.
Enter all of the IP addresses and names into DNS.
As part of the next set of procedures, the utility verifies that the IP addresses and names for
the VMs have been entered into DNS correctly, so you must have all of these IP addresses and
names entered into DNS before proceeding.
Configuring DB VMs (BUI)
95
Deploy the DB VM Group (BUI)
11.
When you have entered all the IP addresses and hostnames into DNS, click
Confirm.
The utility performs a set of configuration verifications. This takes approximately 15 minutes to
complete.
12.
When the group profile process is complete, perform the next task.
See “Deploy the DB VM Group (BUI)” on page 96.
Deploy the DB VM Group (BUI)
Use this procedure to deploy the VM group. When you deploy a group, MCMU installs the
VMs that were defined in the VM group profile.
If you need to change any of these DB VM parameters, do so before you deploy the group:
■
■
IP addresses
Hostnames
Once the VM group is deployed, you can change the number of cores assigned to each VM, and
add or delete VMs.
1.
Ensure that you complete these tasks before deploying the VM group:
■
■
2.
96
“Create a DB VM Group Profile (BUI)” on page 87
Enter all of the VM IP addresses and hostnames into your DNS server.
In the navigation panel, click Database → Virtual Machine Group Profile.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Deploy the DB VM Group (BUI)
The Deployment Review page is displayed.
Configuring DB VMs (BUI)
97
Deploy the DB VM Group (BUI)
3.
98
Click Deploy, and review the configuration in the Deployment Review Page.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Create DB Homes (BUI)
4.
Click Deploy.
The Create Virtual Machine Group window is displayed. As the utility deploys the VM group,
status of each deployment step is updated in this window.
The deployment takes 40 to 80 minutes to complete.
5.
(Optional) If you want to see all the steps involved, click the Detail button.
6.
When the deployment is complete, click Complete, and go to the next task.
See “Create DB Homes (BUI)” on page 99.
Create DB Homes (BUI)
Use this procedure to create DB homes. Each DB home provides a particular Oracle Database
version to the VMs in the group. You must create at least one DB home in the group, and
optionally, you can create multiple DB homes so that the group is configured with multiple
versions of the Oracle Database.
1.
Ensure that you complete these tasks before creating a DB home:
■
■
■
2.
“Create a DB VM Group Profile (BUI)” on page 87
Enter all of the VM IP addresses and hostnames into your DNS server.
“Deploy the DB VM Group (BUI)” on page 96
In the navigation panel, select Database → Virtual Machine Instances.
Configuring DB VMs (BUI)
99
Create DB Homes (BUI)
The Database Virtual Machine Group Summary page is displayed.
3.
Click Create DB Home.
The Create Oracle Database Home window is displayed.
100
Oracle MiniCluster S7-2 Administration Guide • March 2017
Create DB Instances (BUI)
4.
Specify the selectable items in this window.
For details about the required information, use the optional worksheet (“DB VM Planning
Worksheets (Optional)” on page 62), or see “DB Home Parameters” on page 72.
5.
Click the Create button.
The utility creates DB home information for every VM within the DB VM group.
After approximately 15 to 30 minutes, the status reports that the process is complete.
6.
Once complete, click Finish and consider your next task.
■
■
Create another DB home – Repeat this task.
Go to the next task –See “Create DB Instances (BUI)” on page 101.
Create DB Instances (BUI)
Before you can perform this task, you must complete these tasks:
■
■
■
■
1.
“Create a DB VM Group Profile (BUI)” on page 87
Enter all of the VM IP addresses and hostnames into your DNS server.
“Deploy the DB VM Group (BUI)” on page 96
“Create DB Homes (BUI)” on page 99
In the navigation panel, select Database → Virtual Machine Instances.
The Database Virtual Machine Group Summary page is displayed, showing all the VMs in the
group.
Configuring DB VMs (BUI)
101
Create DB Instances (BUI)
Tip - If the VMs are not listed, click the triangle that is next to the VM group to expand the
display. You might need to select another navigation item, then come back to this page.
In this example, the VMs do not yet have any DB instances, which is evident because no
instance names are displayed.
2.
102
Under one of the VMs, click the + symbol.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Create DB Instances (BUI)
The Create Oracle Database Instance window is displayed.
3.
Complete the required information in the order indicated.
For details about the required information, use the optional worksheet (“DB VM Planning
Worksheets (Optional)” on page 62), or see “DB Instance Parameters” on page 73.
4.
Click Create.
Configuring DB VMs (BUI)
103
Create DB Instances (BUI)
A progress pop-up window is displayed. This process can take from 15 to 90 minutes to
complete, depending on the configuration selected.
Tip - While the DB instance is being created, you can dismiss the pop-up window and then
perform other actions in the main BUI (such as create additional DB instances). To return to the
progress pop-up window, in the Virtual Machine Instances page, click on
104
5.
When the process is finished, click Finish.
6.
Verify that the instance is online.
Oracle MiniCluster S7-2 Administration Guide • March 2017
link.
Edit a DB VM Group Profile (BUI)
In the Database → Instances page, identify the VM for which the instance was created. Scroll to
the right and verify that the Instance Status is online.
7.
Repeat these steps for each DB instance that you want to create.
You can create multiple DB instances, until the point where the utility determines that you have
reached the limit. At that point, a message stating that there is not enough memory available to
create additional DB instances is displayed.
Edit a DB VM Group Profile (BUI)
Use this procedure to edit DB VMs.
You can edit VMs even when they are online and in production. The utility only enables
changes to VM parameters that are safe, based on the state of the VM.
For deployed DB groups, you can change the number of cores assigned to the VMs (increase
or decrease) and add VMs to the group (to add a VM, see “Add a DB VM to a Group
(BUI)” on page 108).
Configuring DB VMs (BUI)
105
Edit a DB VM Group Profile (BUI)
For non-deployed DB groups, you can make the same changes as deployed DB groups, plus
change the VM names and IP addresses.
1.
Access the MCMU BUI as a primary admin, such as mcinstall.
See “Log in to the MCMU BUI” on page 26.
2.
In the navigation panel, select the Database → Virtual Machine Group Profile
page.
For example:
106
Oracle MiniCluster S7-2 Administration Guide • March 2017
Edit a DB VM Group Profile (BUI)
3.
Click Edit.
Configuring DB VMs (BUI)
107
Add a DB VM to a Group (BUI)
4.
Edit any of the parameters that are enabled for changes, such as the number of
cores.
If a VM is not deployed, you can change the IP addresses and hostnames.
For a description of DB VM parameters, see “DB VM Parameters” on page 69.
5.
Click one of these lower buttons:
■
■
6.
Save – Saves the change and provides a summary page. The change does not become active
until you click Apply.
Cancel – Cancels the change and closes the window.
Click Apply.
Note - Before clicking Apply, click Save.
Apply prompts you to confirm changes, then applies the changes to the system.
7.
If you changed the name or IP address of a VM, make the equivalent change in
DNS.
8.
Redeploy the VM group.
See “Deploy the DB VM Group (BUI)” on page 96.
MCMU only redeploys the changes.
Add a DB VM to a Group (BUI)
Use this procedure to add a DB VM to a DB VM group.
You can add VMs even when the group is active.
1.
Access the MCMU BUI as a primary admin, such as mcinstall.
See “Log in to the MCMU BUI” on page 26.
108
2.
In the navigation panel, select the Database → Virtual Machine Group Profile
page.
3.
Click Edit.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Add a DB VM to a Group (BUI)
This page is displayed.
4.
Increase the number of VMs on the nodes.
Configuring DB VMs (BUI)
109
Add a DB VM to a Group (BUI)
Details for the added VMs are displayed.
5.
As needed, check and change the details for the new VMs.
For example, check the hostnames, IP addresses, and number of cores and change them to meet
your requirements.
For a description of DB VM parameters, see “DB VM Parameters” on page 69.
110
Oracle MiniCluster S7-2 Administration Guide • March 2017
Deleting DB Components (BUI)
6.
Click one of these lower buttons:
■
■
7.
Save – Saves the change and provides a summary page. The change does not become active
until you click Apply.
Cancel – Cancels the change and closes the window.
Click Apply.
Note - Before clicking Apply, click Save.
Apply prompts you to confirm changes, then applies the changes to the system.
8.
Add the new DB VMs to your DNS.
9.
Complete the configuration of the new VMs.
Perform these tasks:
■
■
■
“Deploy the DB VM Group (BUI)” on page 96
“Create DB Homes (BUI)” on page 99
“Create DB Instances (BUI)” on page 101
Deleting DB Components (BUI)
Use these procedures to delete DB instances, DB home, VMs, and group profiles.
■
■
■
■
“Delete a DB Instance (BUI)” on page 111
“Delete a DB Home (BUI)” on page 113
“Delete a DB VM Group (BUI)” on page 115
“Delete a DB VM Group Profile (BUI)” on page 116
Delete a DB Instance (BUI)
Caution - Deleting a DB instance cannot be undone. Proceed with caution.
1.
Access the MCMU BUI as a primary admin, such as mcinstall.
Configuring DB VMs (BUI)
111
Delete a DB Instance (BUI)
See “Log in to the MCMU BUI” on page 26.
2.
112
In the navigation panel, go to Database → Instances.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Delete a DB Home (BUI)
3.
Identify the instance you want to delete and scroll right.
4.
Under Delete Instance, click the trash can.
5.
Click Confirm.
The deletion takes a few minutes to complete.
6.
Once complete, click Confirm.
7.
Repeat these steps for each DB instance that you want to delete.
Delete a DB Home (BUI)
You can only delete a DB home if all the instances in the home have been deleted.
Caution - Deleting a DB home cannot be undone. Proceed with caution.
1.
Access the MCMU BUI as a primary admin, such as mcinstall.
Configuring DB VMs (BUI)
113
Delete a DB Home (BUI)
See “Log in to the MCMU BUI” on page 26.
2.
114
In the navigation panel, go to Database → Instances.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Delete a DB VM Group (BUI)
3.
Locate the DB home you want to delete.
4.
Under the Edit column, click the trash can.
5.
Click Confirm to delete this DB home.
Delete a DB VM Group (BUI)
Use this procedure to delete a DB VM group. All the VMs in the group will be deleted. The
DB group profile is not deleted, and can be redeployed. If the DB group contains DB VMs, the
primary admin is notified though email as each VM is deleted.
Caution - Deleting a DB VM group deletes all the VMs, applications, and data associated with
the VM group. The deletion cannot be undone. Proceed with caution.
1.
Access the MCMU BUI as a primary admin, such as mcinstall.
See “Log in to the MCMU BUI” on page 26.
2.
In the navigation panel, select Database → Instances.
Configuring DB VMs (BUI)
115
Delete a DB VM Group Profile (BUI)
3.
Click Delete VM Group.
4.
Click the confirmation checkbox, then click Confirm.
The deletion can take 15 to 60 minutes, depending on the number of VMs in the group.
5.
Once complete, click Quit.
Delete a DB VM Group Profile (BUI)
Use this procedure to delete a DB VM group profile. You can only perform this procedure if the
DB group is does not exist, has been deleted, or is not deployed.
Caution - The deletion cannot be undone. Proceed with caution.
1.
Access the MCMU BUI as a primary admin, such as mcinstall.
See “Log in to the MCMU BUI” on page 26.
2.
116
In the navigation panel, select Database → Virtual Machine Group Profile.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Delete a DB VM Group Profile (BUI)
3.
Click Delete.
4.
Click Confirm.
The deletion takes less than a minute.
5.
Once complete, click Quit.
Configuring DB VMs (BUI)
117
118
Oracle MiniCluster S7-2 Administration Guide • March 2017
Configuring Application VMs (BUI)
Perform these tasks to view, create, edit, and delete App VMs:
Description
Link
View App VMs.
“View App VM Groups and VMs (BUI)” on page 119
Create App VMs.
“App VM Creation Task Overview” on page 120
“Create an App VM Group Profile (BUI)” on page 121
“Deploy App VM Groups (BUI)” on page 126
Edit an App VM.
“Edit an App VM Group (BUI)” on page 128
Delete an App VM.
“Delete an Undeployed App VM Group” on page 131
“Delete a Deployed App VM Group” on page 132
Caution - Never manually manage VMs using Oracle Solaris zone commands. Always manage
the VMs through MCMU BUI or MCMU CLI.
View App VM Groups and VMs (BUI)
1.
Access the MCMU.
See “Log in to the MCMU BUI” on page 26.
2.
In the navigation panel, select Application → Virtual Machine Group Profile.
The Application Virtual Machine Group Profile Summary page is displayed.
Configuring Application VMs (BUI)
119
App VM Creation Task Overview
This is an example of a system with one App VM group. If this page reports no data to display,
App groups have not been configured yet.
3.
In the navigation panel, select Application → Virtual Machines.
The Application Virtual Machines summary page is displayed.
Tip - If the VMs are not listed, click the triangle that is next to the VM group to expand the
display. You might need to select another navigation item, then come back to this page.
This example shows one App VM group with two VMs.
App VM Creation Task Overview
Creating App VMs is accomplished though these main tasks:
120
Oracle MiniCluster S7-2 Administration Guide • March 2017
Create an App VM Group Profile (BUI)
Task
No.
Description
Details You Provide During the
Task
BUI Instructions
CLI Instructions
1.
Create App VM Group Profile.
“App VM Group
Parameters” on page 78
“Create an App
VM Group Profile
(BUI)” on page 121
“Create an APP
VM Group
(CLI)” on page 255
2.
Deploy the App VM Group.
None
“Deploy App
VM Groups
(BUI)” on page 126
“Deploy an
App VM Group
(CLI)” on page 257
Create an App VM Group Profile (BUI)
The profile is used to define an App VM group, which supports one or two VMs (one on each
compute node).
The total number of App VM groups you can create is only limited by the amount of system
resources that are available.
For each App VM, you need 1 IP address. When the system was installed, a pool of IP
addresses was defined in the system. To see the amount of IP addresses in the pool, in the
MCMU BUI, go to System Settings → User Input Summary, and view the IP Address Pool
Size.
Note - It is possible that App VM group profiles were created when the system was initially set
up. To determine if a group profile has already been created, see “View App VM Groups and
VMs (BUI)” on page 119.
1.
Access the MCMU BUI as a primary admin, such as mcinstall.
See “Log in to the MCMU BUI” on page 26.
Configuring Application VMs (BUI)
121
Create an App VM Group Profile (BUI)
2.
In the navigation panel, select Application → Virtual Machine Group Profile.
The Application Virtual Machine Group Profile Summary page is displayed.
3.
Click Create New Profile button.
The Application Virtual Machine Group Description page is displayed.
4.
Enter the required information, then click Next.
For details about the required information, use the optional worksheet (“App VM Planning
Worksheets (Optional)” on page 77), or see “App VM Group Parameters” on page 78.
5.
122
Enter information in the page section.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Create an App VM Group Profile (BUI)
This example shows the page that is displayed when a pair of VMs are selected in Step 4. If
Single is selected, only one VM is displayed.
If you plan to cluster the App VMs for high availability, complete the Define Cluster section
and click Next (for details, see “Define Cluster” on page 82). Otherwise, click Next.
Configuring Application VMs (BUI)
123
Create an App VM Group Profile (BUI)
Note that this section of the page is only enabled when you are configuring Oracle Solaris 11
type VMs.
6.
Verify that the information in the Review page is correct.
The information in this page is not editable.
124
Oracle MiniCluster S7-2 Administration Guide • March 2017
Create an App VM Group Profile (BUI)
If you find any issues with any of the information on the Review page, either click the Back
button to return to a previous screen, or click the Cancel button to return to the Home page.
7.
Click Generate.
Configuring Application VMs (BUI)
125
Deploy App VM Groups (BUI)
A progress window is displayed. The process takes a couple minutes to complete.
8.
When the creation is finished, click Finish.
The App VM group is created with the specified VMs, but the VMs are not available for use
until they are deployed.
9.
10.
Configure additional App VM groups, as needed.
Go to the next task.
See “Deploy App VM Groups (BUI)” on page 126.
Deploy App VM Groups (BUI)
Perform this deployment task for each App VM group that you create.
Once complete, the utility allocates these resources to each App VM:
■
■
■
1.
ZFS root file system – 40 GB.
Storage for application binaries and files – 100 GB ZFS file system mounted on /u01.
Client network – 1 virtual network.
Ensure that you have created a VM group before performing this task.
See “Create an App VM Group Profile (BUI)” on page 121.
2.
126
In the Navigation panel, select Application → Virtual Machine Group Profile.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Deploy App VM Groups (BUI)
3.
For the App VM group that you want to deploy, click the Deploy button.
The Deployment Review page is displayed.
4.
Review the App parameters, then click the Deploy button.
Note - If the parameters are not correct, instead select Application → Virtual Machine Group
Profile.
Configuring Application VMs (BUI)
127
Edit an App VM Group (BUI)
A progress window is displayed. The process takes approximately 7 to 15 minutes to complete.
To see all the status of the deployment steps, click the Detail button.
5.
When the deployment is finished, click Finish.
6.
Display the App VM hostnames and IP addresses:
a.
Go to the Application → Virtual Machine Group Profile page.
b.
Click the Edit button for the application group.
The edit page lists the VM hostname (public hostname) and the associated public IP
address for each VM.
c.
7.
At the bottom of the page, click Cancel.
Enter the IP addresses and public hostnames into DNS.
Edit an App VM Group (BUI)
Use this procedure to edit an App VM. You can edit a deployed VM.
1.
Access the MCMU BUI as a primary admin, such as mcinstall.
See “Log in to the MCMU BUI” on page 26.
128
Oracle MiniCluster S7-2 Administration Guide • March 2017
Edit an App VM Group (BUI)
2.
In the navigation panel, select Application → Virtual Machine Group Profile.
3.
For the App VM group that you want to edit, click the corresponding Edit button.
Configuring Application VMs (BUI)
129
Edit an App VM Group (BUI)
The Edit Application Virtual Machine Group Profile page is displayed.
130
Oracle MiniCluster S7-2 Administration Guide • March 2017
Delete an Undeployed App VM Group
4.
Edit any of the parameters that are enabled for changes.
5.
Click one of these lower buttons:
■
■
6.
Save – Saves the change and provides a summary page. The change does not become active
until you click Apply.
Cancel – Cancels the change and closes the window.
Click Apply.
Note - Before clicking Apply, click Save.
Apply prompts you to confirm changes, then applies the changes to the system.
Delete an Undeployed App VM Group
Use this procedure to delete an App VM group that has not been deployed.
Caution - The deletion cannot be undone. Proceed with caution.
1.
Access the MCMU BUI as a primary admin, such as mcinstall.
See “Log in to the MCMU BUI” on page 26.
2.
In the navigation panel, select Application → Virtual Machine Group Profile.
Configuring Application VMs (BUI)
131
Delete a Deployed App VM Group
This page is displayed.
3.
For the App VM group that you want to delete, click the corresponding Delete
button.
4.
Click Confirm.
The App VM group is deleted.
Delete a Deployed App VM Group
Use this procedure to delete an App VM group that has VMs and has been deployed.
When you delete a deployed App VM group, the VMs in the group are deleted and storage and
network resources are returned to the system for future allocation. The utility sends the primary
admin email reporting the deletion of each VM.
132
Oracle MiniCluster S7-2 Administration Guide • March 2017
Delete a Deployed App VM Group
Caution - Deleting App VM groups deletes all the VMs, applications, and data associated with
the VM group. The deletion cannot be undone. Proceed with caution.
1.
Access the MCMU BUI as a primary admin, such as mcinstall.
See “Log in to the MCMU BUI” on page 26.
2.
In the navigation panel, select Application → Virtual Machines.
3.
For the App VM group that you want to delete, click the corresponding Delete VM
Group button.
A confirmation window is displayed.
Configuring Application VMs (BUI)
133
Delete a Deployed App VM Group
4.
Click Confirm.
The App VM group and associated App VMs are deleted. The process takes about 5 minutes to
complete.
5.
134
When the confirmation window indicates that the deletion is done, click Quit.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Configuring Storage for VM Groups (BUI)
These topics describe how to configure the shared storage and how to add or remove a network
file system:
■
■
■
“Enable or Disable Shared Storage (BUI)” on page 135
“Add an External NFS to a VM Group (BUI)” on page 137
“Delete a Network File System From a VM Group (BUI)” on page 140
Note - Additional storage management procedures such as preparing a drive for replacement
and adding another storage array must be performed using the mcmu CLI. See “Managing
Storage (CLI)” on page 279.
Enable or Disable Shared Storage (BUI)
Use this procedure to enable or disable access to the shared storage and NFS for a DB VM
group or an App VM group. You can also use this procedure to identify if shared storage is
enabled or disabled.
The shared storage provides storage space for any storage purpose, and is available to all VMs
within a group.
Caution - Systems deployed in highly secured environments should disable shared storage.
For more information, refer to the Oracle MiniCluster S7-2 Security Guide at http://docs.
oracle.com/cd/E69469_01.
This tables describes the configuration results of enabling or disabling shared storage.
Shared Storage
Configuration
Shared Storage on the Storage Array
External NFS
Enabled
NFS services are enabled for all VMs in the group.
If external NFS is configured, all VMs in the group
have access to the external NFS through the mount point
specified in the group profile.
Configuring Storage for VM Groups (BUI)
135
Enable or Disable Shared Storage (BUI)
Shared Storage
Configuration
Shared Storage on the Storage Array
External NFS
All the VMs in the group have access to the /sharedstore
directory and its contents.
Disabled
All NFS services are disabled for all VMs in the group.
The /sharedstore directory and its contents is not
available to any VMs in the group.
Network file systems are not available to any VMs in the
group.
If previously configured, the NFS mount point is not
deleted from VMs, but no file system is mounted to it.
The change takes effect immediately and applies to all the VMs in the group.
For more information about shared storage on the storage array, see “MiniCluster Storage
Overview” on page 23.
Caution - If any software is dependent on data in the shared storage, and you plan to disable
shared storage, take appropriate actions to remove the dependencies before you perform this
procedure.
1.
Access the MCMU BUI as a primary admin, such as mcinstall.
See “Log in to the MCMU BUI” on page 26.
2.
Navigate to the group profile page.
■
■
For a DB VM group, select the Database → Virtual Machine Group Profile page
For an App VM group, select the Application → Virtual Machine Group Profile page
This is an example of the DB VM group profile page:
If the button is labeled Disabled Shared Storage, that means the shared storage is currently
shared, and visa versa.
136
Oracle MiniCluster S7-2 Administration Guide • March 2017
Add an External NFS to a VM Group (BUI)
3.
Click either Disable Shared Storage or Enable Shared Storage.
4.
When prompted, click Quit.
The change takes effect immediately.
5.
To access the shared file system, log into the VM and perform Oracle Solaris
commands.
To access the file system:
% cd /sharedstore
List contents of the directory:
Note - The /sharedstore directory is empty until you put software in the directory.
% ls /sharedstore
Downloads
Music
Videos
Pictures
Presentations Templates
Texts
Related Information
■
Securing Files and Verifying File Integrity in Oracle Solaris 11.3 (https://docs.oracle.
com/cd/E53394_01/html/E54827/index.html)
■
Managing File Systems in Oracle Solaris 11.3 (http://docs.oracle.com/cd/E53394_01/
html/E54785/index.html)
■
Oracle Solaris 11.3 Information Library (https://docs.oracle.com/cd/E53394_01/)
Add an External NFS to a VM Group (BUI)
Use this procedure to add a network file system (NFS) to a DB VM group or an App VM
group.
The NFS service must be at minimum NFSv4.
The NFS that you add can be any whole or partial directory tree or a file hierarchy, including a
single file that is shared by and NFS server.
When you add external NFS to a group, the remote file system is immediately accessible to all
the VMs in the group.
External NFS is only made available to VMs in a group if shared storage is enabled. See
“Enable or Disable Shared Storage (BUI)” on page 135.
Configuring Storage for VM Groups (BUI)
137
Add an External NFS to a VM Group (BUI)
1.
(If needed) Check what the NFS server is sharing:
a.
Log into the mcmu CLI as a primary admin such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
b.
Ensure that an NFS is available form a server in your environment.
There are a variety of ways to perform this step, depending on the type of server. This is an
example of an Oracle Solaris command that shows what file systems a server is sharing:
% /usr/sbin/showmount -e NFSserver_name_or_IPaddress
c.
To check the version of the NFS service provided by the NFS server, type:
% rpcinfo -p NFSserver_name_or_IPaddress | egrep nfs
100003
4 tcp 2049 nfs
The second column displays the version number. You might see several lines of output.
One of them must report version 4.
2.
Access the MCMU BUI as a primary admin, such as mcinstall.
See “Log in to the MCMU BUI” on page 26.
3.
Navigate to the group profile page.
■
■
4.
For a DB VM group, select the Database → Virtual Machine Group Profile page
For an App VM group, select the Application → Virtual Machine Group Profile page
Click Edit.
The Edit Virtual Machine Group Profile page is displayed. Locate this section:
5.
Enter the required information.
■
138
Server IP – Specify the IP address of the NFS server.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Add an External NFS to a VM Group (BUI)
■
■
Share– Specify the NFS file system that is being shared by your NFS server. For example:
/my_nfs
Mount – Specify the mount point. For example: /my_mountpoint MCMU will create the
mount point and make it available to the VMs in the group.
6.
At the bottom of the screen, click Save.
7.
When prompted, click Done.
8.
In the DB VM Group Profile page, click Edit.
9.
At the bottom of the screen, click Apply, and confirm the change.
10.
When prompted, click Done.
11.
Change the permissions on the mount point in the VMs.
You might need to lighten the permissions on the mount point so that users can access the file
system.
a.
Log into a VM.
See “Accessing VMs” on page 30.
b.
Assume the root role.
% su root
password: **************
c.
List the mount point permissions.
In this example, my_mountpoint is the mount point, and the permissions are read, write,
execute for the root user which doesn't allow any other users access.
# ls -ld /my_mountpoint
drwx------ 2 root
root
d.
Change permissions on the mount point, and list the permissions.
In this example, the permissions are set to read, write, and execute for the owner and
group, and set to read-only for others.
# chmod 774 /my_mountpoint
# ls -ld /my_mountpoint
drwxrwxr-- 2 root
root
e.
6 Oct 25 17:20 my_mountpoint
2 Oct 27 09:03 my_mountpoint
Repeat Step 11 for each VM in the group.
Configuring Storage for VM Groups (BUI)
139
Delete a Network File System From a VM Group (BUI)
12.
To access the network file system, log into the VM and perform Oracle Solaris
commands.
To access the file system:
% cd /my_mountpoint
List contents of the directory:
% ls /my_mountpoint
Downloads
Music
Videos
Pictures
Presentations Templates
Texts
Related Information
■
Securing Files and Verifying File Integrity in Oracle Solaris 11.3 (https://docs.oracle.
com/cd/E53394_01/html/E54827/index.html)
■
Managing File Systems in Oracle Solaris 11.3 (http://docs.oracle.com/cd/E53394_01/
html/E54785/index.html)
■
Oracle Solaris 11.3 Information Library (https://docs.oracle.com/cd/E53394_01/)
Delete a Network File System From a VM Group (BUI)
Use this procedure to delete a network file system (NFS) from a DB VM group or an App VM
group.
When you delete an NFS from a group, the remote file system is immediately unavailable to all
the VMs in the group. The mount point is deleted from the system.
1.
Access the MCMU BUI as a primary admin, such as mcinstall.
See “Log in to the MCMU BUI” on page 26.
2.
Navigate to the group profile page.
■
■
3.
140
For a DB VM group, select the Database → Virtual Machine Group Profile page
For an App VM group, select the Application → Virtual Machine Group Profile page
Click Edit.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Delete a Network File System From a VM Group (BUI)
The Edit Virtual Machine Group Profile page is displayed. Locate this section:
4.
Click the Delete button that is associated with the NFS you want to delete.
5.
At the bottom of the screen, click Save.
6.
When prompted, click Done.
7.
In the DB VM Group Profile page, click Edit.
8.
At the bottom of the screen, click Apply, and confirm the change.
9.
When prompted, click Done.
Configuring Storage for VM Groups (BUI)
141
142
Oracle MiniCluster S7-2 Administration Guide • March 2017
Viewing System Security Information (BUI)
These topics describe how to view security benchmarks and encryption key information in the
MCMU BUI.
Note - Detailed information about running security benchmarks and changing SSH keys is
provided in the MiniCluster S7-2 Security Guide. Refer to Oracle MiniCluster S7-2 Security
Guide.
■
■
■
“Security Compliance Benchmarks” on page 143
“View Security Information (BUI)” on page 144
“View Benchmark Reports (BUI)” on page 145
Security Compliance Benchmarks
When the system is installed, a security profile (CIS Equivalent, PCI-DSS, or DISA-STIG) is
selected, and the system is automatically configured to meet that security profile. To ensure that
the system continues to operate in accordance with security profiles, the MCMU provides the
means to run security benchmarks and access to the benchmark reports.
Running security benchmarks provides these benefits:
■
■
■
■
■
Enables you to evaluate and assess the current security state of the database and application
VMs.
The security compliance tests support the security profile standards based on the security
level configured during the installation.
The security compliance tests run automatically when the system is booted, and can be run
on-demand or at scheduled intervals.
Only available to MCMU primary admins, compliance scores and reports are easily
accessed from the MCMU BUI.
The compliance reports provide remediation recommendations.
Viewing System Security Information (BUI)
143
View Security Information (BUI)
View Security Information (BUI)
Use this procedure to view security related information such as compliance reports and
encryption key details.
For information about configuring security compliance benchmarks, see “Viewing System
Security Information (BUI)” on page 143.
1.
Access the MCMU BUI as a primary admin, such as mcinstall.
See “Log in to the MCMU BUI” on page 26.
2.
In the Home page, scroll down to Compliance Information.
This example shows compliance information for a system that has not yet scheduled security
benchmarks.:
The Compliance Information panel provides this information:
■
■
■
■
■
■
■
■
144
Node – Lists the compute nodes. You can expand and collapse the individual nodes by
clicking on the arrow.
Hostname – Lists the hostname of the VMs.
Benchmark Type – Specifies the type of benchmark used (CIS Equivalent, PCI-DSS, or
DISA-STIG).
Compliance Score – Lists the overall score of the compliance run.
Date & Time – Displays the most recent time that the benchmark was performed.
Remarks – Provides information about benchmark results.
View Report – Provides a button that enables you to view a compliance report.
Schedule Compliance – Provides a button that enables you to schedule a benchmark.
Oracle MiniCluster S7-2 Administration Guide • March 2017
View Benchmark Reports (BUI)
3.
To access encryption key information, In the navigation panel, select System
Settings → Security.
Click on a node to display details.
To manage encryption keys, refer to the Oracle MiniCluster S7-2 Security Guide.
View Benchmark Reports (BUI)
Note - You can only view benchmark reports if a benchmark was schedule and ran.
1.
Access the MCMU BUI as a primary admin, such as mcinstall.
See “Log in to the MCMU BUI” on page 26.
2.
In the Home page, scroll down to the Compliance Information panel.
3.
Click Update Reports.
The update process take a minute or so to complete.
Viewing System Security Information (BUI)
145
View Benchmark Reports (BUI)
4.
Expand the node display and identify the compliance report.
5.
Scroll to the right and click View Report.
The benchmark report is displayed.
146
Oracle MiniCluster S7-2 Administration Guide • March 2017
View Benchmark Reports (BUI)
Under Rule Overview, you can select which types of test to display based on their results. You
can also specify a search string in the search field.
6.
Click on the name of a test to get details and recommended remediation
information.
Viewing System Security Information (BUI)
147
View Benchmark Reports (BUI)
Note - You can display all the details of all tests by clicking Show all Result Details at the
bottom of the report.
7.
148
Evaluate the security warnings and make corrections as needed.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Configuring Oracle Engineered Systems
Hardware Manager
Oracle Engineered Systems Hardware Manager is a BUI-based system-level hardware
management utility intended for use by Oracle Service personnel, or under their direction.
By default, utility is configured at installation. However, if you change Oracle ILOM root
passwords after the installation, you must update the Oracle Engineered Systems Hardware
Manager configuration with the new passwords. This action is required so that service
personnel can use the tool to ensure optimum problem resolution and health of the system.
These topics describe how to configure this utility:
■
■
■
■
■
“Oracle Engineered Systems Hardware Manager Overview” on page 149
“Access Oracle Engineered Systems Hardware Manager” on page 150
“Update Component Passwords” on page 151
“Configure the Utility's Password Policy and Passwords” on page 152
“Configure Certificates and Port Numbers” on page 153
Oracle Engineered Systems Hardware Manager Overview
Oracle Engineered Systems Hardware Manager is a BUI-based system-level hardware
management utility used by Oracle Service personnel, or under their direction.
The utility provides service personnel with these capabilities:
■
■
■
■
■
Hardware dashboard/health view
Hardware inventory summary
Hardware component details
Ability to launch other Oracle MiniCluster tools
Easy access to Oracle ILOM and the MCMU
Configuring Oracle Engineered Systems Hardware Manager
149
Access Oracle Engineered Systems Hardware Manager
■
■
■
■
Problem summary across all components
System-level problem history, and the ability to manually clear hardware faults and
warnings
Automatic and manual collection of support file bundles
Manual delivery of support file bundles to My Oracle Support (MOS)
If you change Oracle ILOM root passwords after the installation, you must update the Oracle
Engineered Systems Hardware Manager configuration with the new passwords. This action is
required so that service personnel can use the tool to ensure optimum problem resolution and
health of the system.
There are two accounts in Oracle Engineered Systems Hardware Manager:
■
admin – Use this account to configure Oracle Engineered Systems Hardware Manager.
■
service – An account used by Oracle Service personnel.
In addition, Oracle Engineered Systems Hardware Manager must be configured with the
passwords for the root account on all the Oracle ILOMs in the system.
Note - The utility does not need to know the passwords for the OS, database, applications, or
virtual machines.
Related Information
■
■
■
■
“Access Oracle Engineered Systems Hardware Manager” on page 150
“Update Component Passwords” on page 151
“Configure the Utility's Password Policy and Passwords” on page 152
“Configure Certificates and Port Numbers” on page 153
Access Oracle Engineered Systems Hardware Manager
You can access this tool from a browser as described in this procedure, or you can launch
the tool from the MCMU BUI. See “Access Oracle Engineered Systems Hardware
Manager” on page 178.
150
1.
Open a browser on a system that has network access to MiniCluster.
2.
In the browser, type this address:
Oracle MiniCluster S7-2 Administration Guide • March 2017
Update Component Passwords
https://node1_name.domain:8001
Example: https://mc4-n1.us.company.com:8001
The Oracle Engineered Systems Hardware Manager login screen is displayed.
3.
Log in to the admin account.
The user name is admin. The password is the same password used for the mcinstall account.
Tip - For assistance, refer to the online help that is displayed on each page.
Related Information
■
■
■
■
“Oracle Engineered Systems Hardware Manager Overview” on page 149
“Update Component Passwords” on page 151
“Configure the Utility's Password Policy and Passwords” on page 152
“Configure Certificates and Port Numbers” on page 153
Update Component Passwords
You must perform this procedure whenever the Oracle ILOM root password is changed.
Keeping Oracle Engineered Systems Hardware Manager up to date ensures that Oracle Service
personnel can use the utility to manage MiniCluster components.
For details on which component passwords are required see “Oracle Engineered Systems
Hardware Manager Overview” on page 149.
1.
Access the utility.
See “Access Oracle Engineered Systems Hardware Manager” on page 150.
2.
Choose Setup → Authentication, and select the Component Access tab.
3.
Update component passwords:
a.
Click on Compute Severs to display Compute Server 1 and Computer Server
2.
b.
Click in the check boxes for ILOM (user root), and press Provide Credentials.
c.
Enter the password that you have already set in the ILOM.
Configuring Oracle Engineered Systems Hardware Manager
151
Configure the Utility's Password Policy and Passwords
Select the compute servers (MiniCluster nodes), and click Provide Credentials. Enter the node's
Oracle ILOM passwords.
4.
Restart Oracle Engineered Systems Hardware Manager for the changes to take
effect:
Go to Set Up → Maintenance, select the Restart tab, and click the Restart button.
OESHM restarts and requires the you to log in again.
Related Information
■
■
■
■
“Oracle Engineered Systems Hardware Manager Overview” on page 149
“Access Oracle Engineered Systems Hardware Manager” on page 150
“Configure the Utility's Password Policy and Passwords” on page 152
“Configure Certificates and Port Numbers” on page 153
Configure the Utility's Password Policy and Passwords
Perform this procedure to configure these passwords and policies for the utility:
1.
■
Password policy
■
admin and service passwords
Access the utility.
See “Access Oracle Engineered Systems Hardware Manager” on page 150.
2.
Configure the password policy.
Choose Setup → Authentication → Password Policy.
3.
Change the passwords for the admin and service accounts.
Choose Setup → Authentication → User Management.
Related Information
■
■
■
■
152
“Oracle Engineered Systems Hardware Manager Overview” on page 149
“Access Oracle Engineered Systems Hardware Manager” on page 150
“Update Component Passwords” on page 151
“Configure Certificates and Port Numbers” on page 153
Oracle MiniCluster S7-2 Administration Guide • March 2017
Configure Certificates and Port Numbers
Configure Certificates and Port Numbers
Perform the relevant steps in this procedure to configure these items used by Oracle Engineered
Systems Hardware Manager:
■
■
1.
Certificates – Use your own certificates instead of the site- and instance-specific
certificates that the utility generates.
Ports – If an application running on MiniCluster uses the same port that the utility uses
(8001), you or Oracle Service can configure Oracle Engineered Systems Hardware Manager
to use a different port.
Access the utility.
See “Access Oracle Engineered Systems Hardware Manager” on page 150.
2.
If needed, configure the utility to use your own certificates.
Choose Setup → Certificates.
3.
Change network ports if they conflict with our environment.
Choose Setup → Network.
Related Information
■
■
■
■
“Oracle Engineered Systems Hardware Manager Overview” on page 149
“Access Oracle Engineered Systems Hardware Manager” on page 150
“Update Component Passwords” on page 151
“Configure the Utility's Password Policy and Passwords” on page 152
Configuring Oracle Engineered Systems Hardware Manager
153
154
Oracle MiniCluster S7-2 Administration Guide • March 2017
Checking the Virtual Tuning Status (BUI)
The virtual tuning assistance is used to keep MiniCluster automatically tuned to best practices.
Note - This section describes how to administer the virtual tuning assistant using the MCMU
BUI. For instructions on how to administer the virtual tuning assistant (mctuner) using the
MCMU CLI, see “Administering the Virtual Tuning Assistant (CLI)” on page 293.
These topics describe how to obtain information from the virtual tuning assistant.
■
■
“Virtual Tuning Assistant Overview” on page 155
“View Virtual Tuning Assistant Status (BUI)” on page 155
Virtual Tuning Assistant Overview
By default, the virtual tuning assistant is enabled on the system to ensure that the system is
running with optimal tuning parameters. There is a tuning instance running on the global and
kernel zones on each node.
By default, the tuning assistant sends notices to root@localhost. To change the email
notification email address, see “Configure the mctuner Notification Email Address
(CLI)” on page 293.
View Virtual Tuning Assistant Status (BUI)
1.
Access the MCMU BUI as a primary admin, such as mcinstall.
See “Log in to the MCMU BUI” on page 26.
Checking the Virtual Tuning Status (BUI)
155
View Virtual Tuning Assistant Status (BUI)
2.
In the Home page, scroll down to the Virtual Tuning Assistant Status panel.
For example:
3.
Click Update Stats.
The virtual tuning assistant process is continually monitoring the system's tuning parameters.
By updating the stats, the latest tuning information is displayed in the BUI.
4.
156
Click on a node to expand the details for the node.
Oracle MiniCluster S7-2 Administration Guide • March 2017
View Virtual Tuning Assistant Status (BUI)
For example:
The Virtual Tuning Assistant Status Information panel provides this information:
■
■
■
■
Virtual Machine – For each VM, this column indicates the type of zone that the VM is
based on.
Status – Indicates if the VM is online or offline.
Issues – Displays any issues that the virtual tuning assistant detects.
Notices – Displays virtual tuning assistant notices.
Checking the Virtual Tuning Status (BUI)
157
158
Oracle MiniCluster S7-2 Administration Guide • March 2017
Updating MiniCluster Software (BUI)
These topics describe how to update MiniCluster system software.
■
■
■
■
■
■
“Component Update Process Overview” on page 159
“View Software Component Versions (BUI)” on page 160
“Check for and Obtain the Latest Updates” on page 162
“Extract the Patch Bundle” on page 164
“Install the Component Bundle” on page 165
“Update MiniCluster Software (BUI)” on page 167
Component Update Process Overview
Updates for Oracle Engineered Systems such as MiniCluster, are issued on a periodic basis.
The bundled updates are available for download from My Oracle Support (http://support.
oracle.com.)
Applying updates to MiniCluster involves these tasks:
1. Fully backup the system.
2. Download update bundles from My Oracle Support.
3. Unzip, concatenate, and extract the downloaded files to a predefined directory on
MiniCluster.
4. Identify software components that require updating. Important – Update the MCMU
component before you update any other component.
5. Use the MCMU BUI or CLI to update the system.
Subsequent topics describe how to perform these tasks.
There are a number of MiniCluster software and firmware components that can be updated
using MCMU. At any given time, updates might be available for one component, and not
others.
Updating MiniCluster Software (BUI)
159
View Software Component Versions (BUI)
This table lists components that can be updated (subject to update availability):
Note - The list of components is subject to change for different versions of MiniCluster. To see
the exact list for your system, view the current MCMU versions as described in “View Software
Component Versions (BUI)” on page 160.
Component Name in the BUI
Component Option Used in the
CLI
Description
MiniCluster Configuration
Utility
update_omctoolkit
MCMU BUI and CLI software.
Storage tray firmware
update_jbod
Firmware on the storage array.
Shared filesystem software
update_acfs
Grid infrastructure and ACFS in kernel zones.
OS package repository
updater
OS repository used to install and update VMs and global zones.
Shared storage OS
update_kz
OS on the kernel zones.
Compute nodes OS
update_gz
Updates the OS on the compute nodes.
Compute node firmware
update_ilom
Oracle ILOM on the compute nodes.
Grid infrastructure
update_gi
Grid infrastructure in DB VMs.
Oracle DB home
Update_oh
Updates the Oracle DB in DB VMs.
Related Information
■
■
■
“Check for and Obtain the Latest Updates” on page 162
“Update MiniCluster Software (BUI)” on page 167
“Updating MiniCluster Software (CLI)” on page 297
View Software Component Versions (BUI)
The MCMU BUI provides a list of MCMU software versions currently installed on the system.
1.
Access the MCMU BUI as a primary admin, such as mcinstall.
See “Log in to the MCMU BUI” on page 26.
2.
160
In the navigation panel, select Patches and Updates.
Oracle MiniCluster S7-2 Administration Guide • March 2017
View Software Component Versions (BUI)
The page shows current software versions on your system.
3.
Identify the availability of any updates.
You can identify the availability of updates in a couple of different ways:
■
■
Manually – Go to My Oracle Support (http://support.oracle.com), search for
2153282.1, review the information in the Oracle MiniCluster S7-2: Software Download
Center to see if later updates are available.
Through the MCMU BUI – Perform “Check for and Obtain the Latest
Updates” on page 162, “Extract the Patch Bundle” on page 164 and “Update
MiniCluster Software (BUI)” on page 167 through Step 6.
Note - Do not click Check Status unless you have installed the latest updates in the /var/
opt/oracle.minicluster/patch directory as described in “Check for and Obtain the Latest
Updates” on page 162. The Check Status feature compares component versions of the system
against what is in the /var/opt/oracle.minicluster/patch directory.
Updating MiniCluster Software (BUI)
161
Check for and Obtain the Latest Updates
Check for and Obtain the Latest Updates
Some updates require you to download multiple large zip files. Depending on your network
capabilities and the size of the zip files, the download can take a significant amount of time.
IMPORTANT – Update the MCMU component before you update any other component. If you
follow the steps in this procedure, you are directed to do so.
Note - There are multiple software update scenarios based on the state of MiniCluster (before
initial setup, after initial setup) and based on the version currently running on MiniCluster.
Depending on your situation, you might need to perform updates in a specific way. For further
details, refer to the MiniCluster S7-2 Release Notes on MOS. Instructions for accessing the
release notes are in this procedure.
1.
Follow best practices and backup the system before updating software.
2.
Access the MCMU BUI.
See “Log in to the MCMU BUI” on page 26.
3.
In the upper right corner, click on your user name and select My Oracle Support.
4.
Sign into MOS.
5.
Search 2153282.1.
This MOS document is the MiniCluster S7-2: Software Download Center and provides access
to MiniCluster downloads.
6.
In Doc ID 2153282.1, click the Latest Release link.
You are directed to the latest downloads.
This table describes the different downloads that are available. Note that not all of these
downloads pertain to updating a system. This procedure describes how to download and install
the Patch Bundle and the Component Bundle, which are used to update software components.
MiniCluster Initial Configuration Tool
Provides the initial configuration tool used to create configuration files required at installation time.
For information, refer to the Oracle MiniCluster S7-2 Installation Guide, at http://docs.oracle.com/cd/
E69469_01
MiniCluster Component Bundle
Provides all or a subset of updates for these components:
162
Oracle MiniCluster S7-2 Administration Guide • March 2017
Check for and Obtain the Latest Updates
■ Oracle DB and GI binaries
■ Oracle Solaris 10 Zone flash archive (for creating Solaris 10 branded VMs)
■ Disk calibration software
Download and install the Component Bundle for these situations:
■ During the initial installation. Refer to the Oracle MiniCluster S7-2 Installation Guide, at http://docs.oracle.
com/cd/E69469_01.
■ Any time that there are updated versions and you want to use those updated versions to configure VMs. This
procedure explains how to perform this activity.
MiniCluster Core Software
Provides MiniCluster management software (MCMU), Solaris 11.3 SRU and SRU repository files.
Download and install the core software if you see a screen telling you that your core software is out of date when you
run the installmc --deploy command as part of your initial installation.
Note - MiniCluster systems ship from the factory with the core software installed. You usually only need this
download if instructed to obtain it during the installation. You do not use this download for routine software updates.
In those cases use the Patch Bundle and Component bundle.
MiniCluster Patch Bundle
Provides all or a subset of updates for these components:
■
■
■
■
■
■
MCMU
GI and DB patches for all supported DB versions (applied to existing DB VMs)
Oracle Solaris SRUs (applied to existing VMs)
Oracle Solaris 10 Zone flash archive (applied to existing Solaris 10 branded VMs)
Compute node firmware (Oracle ILOM)
Storage array firmware
Download and install the Patch Bundle to determine if any of the MiniCluster software components are out of date
and to update out of date components.
This procedure describes how to download this Patch Bundle.
MiniCluster Factory Reset ISO
Download and install the factory reset ISO if you want to reset your MiniCluster system back to the original factory
settings.
For information on downloading and installing the factory reset ISO, refer to the MOS article titled Oracle
MiniCluster S7-2: How to factory reset the entire system (Doc ID 2151620.1).
7.
Open and review the Release Notes.
Click the MiniCluster Release Notes link under MiniCluster Core Software section.
The Release Notes provide important information about specific update procedures.
8.
In Doc ID 2153282.1, begin the download process for one of these bundles:
Updating MiniCluster Software (BUI)
163
Extract the Patch Bundle
■
■
Patch Bundle – For updating MCMU, existing VMs GI, DB, and OS, compute node's OS,
GI, and firmware, and storage array firmware.
Component Bundle – (Recommended when you plan to update MCMU) This bundle is for
installing the latest versions of the Oracle Database in the DB repository (used to create and
update DB VMs).
To begin the download process, click on the patch number for the particular bundle you want to
download.
9.
Using your browser, download each zip file to the /var/opt/oracle.minicluster/
patch directory on compute node 1.
Click on the patch number to access the download page, then download all applicable zip files.
If desired, read any accompanying README or release notes.
10.
(If needed) Download the other bundle.
Repeat Step 8 and Step 9 If you want to download both bundles. If you are only updating a
particular component, choose the bundle that provides the component update that you want.
11.
Consider your next action.
Based on the bundles you downloaded, perform one or more of these procedures:
■
■
“Extract the Patch Bundle” on page 164
“Install the Component Bundle” on page 165
Extract the Patch Bundle
1.
Ensure that you have downloaded the latest Patch Bundle.
See “Check for and Obtain the Latest Updates” on page 162.
2.
Log into the compute node 1 MCMU CLI as the primary admin such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
3.
Unzip the zip files.
% cd /var/opt/oracle.minicluster/patch
% /bin/unzip '*zip'
4.
Identify the version_no in the names of the patch tar files.
In this example, the tar file version_no is 1.1.21.4. Your version_no might be different. Make
note of the version_no for the next step.
164
Oracle MiniCluster S7-2 Administration Guide • March 2017
Install the Component Bundle
% ls
MC-README.txt
mc-1.1.21.4-patch.tar.aa
mc-1.1.21.4-patch.tar.ab
mc-1.1.21.4-patch.tar.ac
mc-1.1.21.4-patch.tar.ad
5.
p25218297_100_SOLARIS64_2of4.zip
p25218297_100_SOLARIS64_3of4.zip
p25218297_100_SOLARIS64_4of4.zip
Extract the tar Files.
In this example, replace version_no with the appropriate version_no for your download.
This command concatenates and extracts all of the files.
% cat mc-version_no-patch.tar.a? | gtar -xf -
6.
Consider your next action.
If you also downloaded the Component Bundle, go to “Install the Component
Bundle” on page 165.
If you plan to update the MCMU component, go to: “Update the MCMU Component
(CLI)” on page 299
Otherwise, perform one of these procedures:
■
■
Update components using the MCMU BUI – See “Update MiniCluster Software
(BUI)” on page 167.
Update components using the MCMU CLI – See “Update the MCMU Component
(CLI)” on page 299.
Install the Component Bundle
Use this procedure to update the Oracle Database software. Once the Component Bundle is
installed, the latest Oracle Database binaries are installed and available for configuration of
VMs.
This procedure is also required when you update the MCMU component as described in
“Update the MCMU Component (CLI)” on page 299. You can install the Component Bundle
before or after updating the MCMU component.
1.
Ensure that you have downloaded the latest Component Bundle.
See “Check for and Obtain the Latest Updates” on page 162.
2.
Log into the compute node 1 MCMU CLI as the primary admin such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
Updating MiniCluster Software (BUI)
165
Install the Component Bundle
3.
Unzip the zip files.
% cd /var/opt/oracle.minicluster/patch
% /bin/unzip '*zip'
4.
Identify the version_no in the names of the tar files.
In this example, the version_no is 1.1.21.4. Your version_no might be different. Make note of
the version_no for the next step.
% ls
MC-README.txt
mc-1.1.21.4-sfw.tar.ad
mc-1.1.21.4-sfw.tar.aa
mc-1.1.21.4-sfw.tar.ae
mc-1.1.21.4-sfw.tar.ab
5.
Extract the tar Files.
This command might run for 1.5 hours.
In this command line, replace version_no with the version of your tar files.
% cat /var/opt/oracle.minicluster/patch/mc-version_no-sfw.tar.a? | gtar -x -C /commonfs/ -f 6.
(Only required on systems running v1.1.3 or earlier) Set the permissions for
these directories:
%
%
%
%
%
7.
chmod
chmod
chmod
chmod
chmod
1777 /commonfs/sfw/
-R a+rx /commonfs/sfw/OracleDBSW
-R a+rx /commonfs/sfw/calibration
-R a+rx /commonfs/sfw/s7-sysfw
-R a+rx /commonfs/sfw/s11.3
Consider your next action.
IMPORTANT – Update the MCMU component before you update any other component. See
“Update the MCMU Component (CLI)” on page 299.
If you have already updated the MCMU component, you can update other components by
performing one of these procedures:
■
■
166
Update components using the MCMU BUI – See “Update MiniCluster Software
(BUI)” on page 167.
Update components using the MCMU CLI – See “Update the MCMU Component
(CLI)” on page 299.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Update MiniCluster Software (BUI)
Update MiniCluster Software (BUI)
This procedure describes how to apply updates to MiniCluster components using the MCMU
BUI after the system's initial setup is done.
The system can be updated while DB and App VMs are running.
Caution - The MCMU component must be updated before you update any other component.
(see “Update the MCMU Component (CLI)” on page 299).
Caution - For systems running MCMU v1.1.21 and earlier, you must update the
MCMU software component through the CLI (see “Update the MCMU Component
(CLI)” on page 299). Do not attempt to update MCMU through the BUI because the update
might fail. If you experience this problem, follow the instructions in the MiniCluster Release
Notes (Doc ID 2214746.1) available at http://support.oracle.com, under the heading
Upgrading Fully Configured MiniCluster to 1.1.21.4.
Note - There are multiple software update scenarios based on the state of MiniCluster (before
initial setup, after initial setup) and based on the version currently running on MiniCluster.
Depending on your situation, you might need to perform updates in a specific way. For further
details, refer to the MiniCluster S7-2 Release Notes on MOS. Instructions for accessing the
release notes are available in “Check for and Obtain the Latest Updates” on page 162.
1.
Ensure that you have downloaded the latest Patch Bundle as described in
“Check for and Obtain the Latest Updates” on page 162.
2.
Access the MCMU BUI as a primary admin, such as mcinstall.
See “Log in to the MCMU BUI” on page 26.
3.
In the navigation panel, select Patches and Updates.
The page shows the versions of software installed on your system.
4.
Click the Check Status button.
MCMU compares the software versions installed on MiniCluster with the versions of the patch
files in the /var/opt/oracle.minicluster/patch directory.
Updating MiniCluster Software (BUI)
167
Update MiniCluster Software (BUI)
5.
In the dialog window, click Confirm.
6.
In the Patches and Updates page, identify what updates are available.
Review the Current Level and Latest Level information.
These buttons indicate which components can be updated:
■
■
Apply – An update is available and the component can be updated. Important – Do not use
the MiniCluster Configuration Utility Apply button. That component must be updated using
the MCMU CLI.
Not Applicable – No updates are available for the component, and the component cannot
be updated.
Update availability is based on what is in the /var/opt/oracle.minicluster/patch directory.
168
Oracle MiniCluster S7-2 Administration Guide • March 2017
Update MiniCluster Software (BUI)
For the components marked with an asterisk, MCMU automatically reboots the compute node
after the update is applied. The compute nodes are rebooted one at a time, so system availability
is maintained.
7.
Choose a method for applying updates.
Caution - The MCMU component must be updated before you update any other component.
(see “Update the MCMU Component (CLI)” on page 299).
Caution - Do not attempt to update the MiniCluster Configuration Utility through the
BUI. For systems running MCMU v1.1.21 and earlier, you must update the MiniCluster
Configuration Utility component through the CLI (see “Update the MCMU Component
(CLI)” on page 299).
Take one of these actions:
■
Click an individual component Apply button – MCMU applies the update for that
component.
Updating MiniCluster Software (BUI)
169
Update MiniCluster Software (BUI)
■
Important – Do not use the MiniCluster Configuration Utility Apply button. That
component must be updated using the MCMU CLI.
Click the Apply All button – Important – Do not use this button if the MiniCluster
Configuration Utility component shows an Apply button. MCMU automatically applies
available component updates in this order:
1.
2.
3.
4.
5.
6.
MCMU
Storage tray firmware
ACFS
Solaris repository
Solaris in kernel zones
Solaris in global zones (updates node 2 first, reboots node 2, then updates node 1 and
reboots node 1)
Note - Apply All does not automatically apply the compute node firmware (Oracle ILOM),
Grid infrastructure, or Oracle DB home software. Those component updates must be applied
individually.
A confirmation window is displayed.
8.
Click Confirm.
MCMU applies the updates to the system.
The duration of the update process varies based on the type and number of updates. MCMU
displays the progress.
9.
When the dialog window indicates that the update process is complete, click
Confirm.
The dialog window is dismissed, and you can run other MCMU BUI functions.
170
Oracle MiniCluster S7-2 Administration Guide • March 2017
Update MiniCluster Software (BUI)
If you are updating the MiniCluster Configuration Utility, web services are restarted and you
might need to refresh the browser cache (shift-reload).
Updating MiniCluster Software (BUI)
171
172
Oracle MiniCluster S7-2 Administration Guide • March 2017
Performing System Checks (BUI)
The MCMU BUI provides access to several features that enable you to check system states.
These topics describe how to access the features:
■
■
■
“Perform a Readiness Check (BUI)” on page 173
“View the Hardware Topology (BUI)” on page 174
“Calibrate Disks (BUI)” on page 174
Perform a Readiness Check (BUI)
The system readiness check feature checks to ensure that the MiniCluster hardware and
software are configured properly and at expected levels. This check is normally performed
before the system is configured, but you can run this feature any time.
1.
Access the MCMU BUI as a primary admin, such as mcinstall.
See “Log in to the MCMU BUI” on page 26.
2.
In the navigation panel, select System Settings → System Checks.
The System Checks page is displayed.
Performing System Checks (BUI)
173
View the Hardware Topology (BUI)
3.
Click the Readiness Check button.
View the Hardware Topology (BUI)
Use this task to check that the I/O cards locations and to verify network connectivity.
1.
Access the MCMU BUI as a primary admin, such as mcinstall.
See “Log in to the MCMU BUI” on page 26.
2.
In the navigation panel, select System Hardware Topology.
The System Checks page is displayed.
This example shows the topology of a system with one storage array. Note that a second storage
array is shown, but with no connections to the nodes, the system probably only has one storage
array.
3.
Click the Verify Topology button.
Calibrate Disks (BUI)
Use this procedure to check the health of the drives in the system. This feature performs read
and write tests on a reserved area of each drive. The check is not destructive to data.
174
Oracle MiniCluster S7-2 Administration Guide • March 2017
Calibrate Disks (BUI)
1.
Access the MCMU BUI as a primary admin, such as mcinstall.
See “Log in to the MCMU BUI” on page 26.
2.
In the navigation panel, select System Settings → System Checks.
The System Checks page is displayed.
3.
Click the Disk Calibration button.
Performing System Checks (BUI)
175
176
Oracle MiniCluster S7-2 Administration Guide • March 2017
Performing Support Tasks (BUI)
The MCMU BUI provides access to several support related features. These topics describe how
to access the features:
■
“Access My Oracle Support (BUI)” on page 177
■
“Access Oracle Engineered Systems Hardware Manager” on page 178
“Creating A support file bundle (OESHM)” on page 178
“Configure the Oracle ASR Client (BUI)” on page 179
■
■
Access My Oracle Support (BUI)
The MCMU BUI provides a link to My Oracle Support (MOS). MOS provides access to these
support functions:
■
Oracle knowledge database
Patches and updates
Service requests
■
Certifications
■
■
Note - Access to MOS requires an Oracle support agreement and MOS login credentials.
1.
Access the MCMU BUI.
See “Log in to the MCMU BUI” on page 26.
2.
In the upper right corner, click on your user name and select My Oracle Support.
My Oracle Support is opened in a new tab or window.
3.
Sign in to MOS.
Performing Support Tasks (BUI)
177
Access Oracle Engineered Systems Hardware Manager
Access Oracle Engineered Systems Hardware Manager
At the direction of Oracle personnel, you can start the Oracle Engineered Systems Hardware
Manager from the MCMU BUI to perform various service related activities.
Note - Oracle Engineered Systems Hardware Manager must be configured before it is accessed.
See “Configuring Oracle Engineered Systems Hardware Manager” on page 149.
1.
Access the MCMU BUI as a primary admin, such as mcinstall.
See “Log in to the MCMU BUI” on page 26.
2.
In the navigation panel, select System Settings → Support.
3.
Click the Launch ESHM button.
The Oracle Engineered Systems Hardware Manager opens in another tab or window.
4.
Log into Oracle Engineered Systems Hardware Manager.
These are the login credentials:
5.
■
User name: admin
■
Password: Is the same password used for the mcinstall user account.
Follow the direction of Service personnel to perform Oracle Engineered Systems
Hardware Manager activities.
You can also access the online help by clicking More details on each page.
Creating A support file bundle (OESHM)
A support file bundle is a collection of log files which contain system information that can be
used to diagnose hardware problems. A support file bundle is always automatically created
when a hardware fault is detected. You can also create them manually. You can export support
file bundles to Oracle Services through the Oracle Engineered Systems Hardware Manager
BUI.
Note - For storage space efficiency, the utility only supports the existence of one support file
bundle per component. If a support file bundle exists, it is automatically replaced when a new
bundle is generated.
Use this procedure to manually create a support file bundle.
178
Oracle MiniCluster S7-2 Administration Guide • March 2017
Configure the Oracle ASR Client (BUI)
1.
Log into Oracle Engineered Systems Hardware Manager through the MCMU BUI.
Log in as the admin user. See “Access Oracle Engineered Systems Hardware
Manager” on page 178.
2.
From Oracle Engineered Systems Hardware Manager, in the left navigation
panel, select Support File Bundles.
The Support File Bundles page is displayed.
3.
Click Create Bundle.
4.
In the Create Bundle dialog box, select one of the compute servers.
5.
Click Create.
The utility creates a support file bundle.
6.
To see the status, view the Support File Bundles page.
Configure the Oracle ASR Client (BUI)
When you have completed the initial installation of the system, you can use MCMU to activate
Oracle ASR software for the system.
Oracle ASR software provides the ability to resolve problems quickly by automatically opening
service requests for Oracle's qualified server, storage, and Engineered System products when
specific faults occur. Parts are dispatched upon receipt of a service request sent by Oracle ASR.
In many cases, Oracle engineers are already working to resolve an issue before you are aware
that a problem exists.
Performing Support Tasks (BUI)
179
Configure the Oracle ASR Client (BUI)
Oracle ASR securely transports electronic fault telemetry data to Oracle automatically to help
expedite the diagnostic process. The one-way event notification requires no incoming Internet
connections or remote access mechanism. Only the information needed to solve a problem is
communicated to Oracle.
Oracle ASR is a feature of the Oracle hardware warranty, Oracle Premium Support for Systems,
and Oracle Platinum Services. To learn more, go to https://www.oracle.com/support/
premier/index.html.
Oracle ASR documentation is available at: http://www.oracle.com/technetwork/systems/
asr/documentation
1.
Access the MCMU BUI as a primary admin, such as mcinstall.
See “Log in to the MCMU BUI” on page 26.
2.
In the navigation panel, select System Settings → Support.
3.
Click the Configure Automatic Service Request Client button.
4.
In the pop-up window, complete the requested information:
■
My Oracle Support Username – Specify a valid My Oracle Support user name.
■
Password – Specify the password.
■
ASR Endpoint – Select one of the following:
■
Oracle Transport Server – The ASR client connects directly to Oracle.
■
ASRM – The ASR client connects to an ASR manager running on a system in your
environment.
■
180
Register Point – Select one of the following:
Oracle MiniCluster S7-2 Administration Guide • March 2017
Configure the Oracle ASR Client (BUI)
5.
■
ILOM – Telemetry information is handled by Oracle ILOM. This is the preferred setting.
■
Solaris –Telemetry information is handled by Oracle Solaris.
Click Configure.
Performing Support Tasks (BUI)
181
182
Oracle MiniCluster S7-2 Administration Guide • March 2017
Using the MCMU CLI
Previous sections in this document describe how to administer MiniCluster using the MCMU
BUI, which is a good interface to use for guided visual procedures. The majority of BUI
procedures can also be performed using the MCMU CLI. The remainder of this document
covers the MCMU CLI procedures.
These topics describe how to use the mcmu command and how to display mcmu help:
■
“MCMU CLI Overview” on page 183
■
“Display mcmu Help For All Subcommands (CLI)” on page 184
■
“Display mcmu Help for a Specific Subcommand (CLI)” on page 185
MCMU CLI Overview
MiniCluster includes the mcmu command that enables you to administer the system at the
command line.
To perform mcmu commands, you must log into the mcmu CLI with a valid MCMU account such
as the mcinstall user account. See “Log in to the MCMU CLI” on page 29.
This is the syntax for the mcmu command:
mcmu subcommand subcommand_option additional_option
where:
■
■
subcommand — specifies one of the subcommands listed in the table.
subcommand_option — is an argument that can be specified in either of these formats:
■
-A — A is a single alpha character (Note: this is case sensitive. Uppercase and
lowercase letters perform different operations).
■
--string — string is a valid string for the subcommand.
Using the MCMU CLI
183
Display mcmu Help For All Subcommands (CLI)
■
additional_option — is a valid argument for the subcommand_option.
This example creates a DB instance using the tenant subcommand with -I (instance) and -c
(create) options.
% mcmu tenant -I -c
This example performs the same operation as the previous example:
% mcmu tenant --dbinstance -c
For the latest CLI information, additional details, and valid options, use the mcmu help option.
See “Display mcmu Help For All Subcommands (CLI)” on page 184 and “Display mcmu Help
for a Specific Subcommand (CLI)” on page 185.
Display mcmu Help For All Subcommands (CLI)
Use this procedure to display the mcmu CLI syntax for all the mcmu subcommands and options.
1.
Log into the MCMU CLI.
See “Log in to the MCMU CLI” on page 29.
2.
Type:
% mcmu -h
Usage: mcmu [Sub-Command][Sub-command options]
Oracle MiniCluster Configuration Utility
MCMU v1.1.18
Sub-Commands:
/var/opt/oracle.minicluster/bin/mcmu [setupmc|patch|tenant|status|start|stop|
compliance|sshkey|user|readiness|mctuner|asr|security|diskutil]
MCMU Options:
-h, --help
-V, --version
,
<some output omitted>
.
.
.
184
Oracle MiniCluster S7-2 Administration Guide • March 2017
Show supported options
Print version string
Display mcmu Help for a Specific Subcommand (CLI)
Display mcmu Help for a Specific Subcommand (CLI)
1.
Log into the MCMU CLI.
See “Log in to the MCMU CLI” on page 29.
2.
To display help for a specific subcommand, use this syntax:
mcmu subcommand -h
where subcommand is one of the mcmu subcommands. For a full list of subcommands, see
“Display mcmu Help For All Subcommands (CLI)” on page 184, or type mcmu -h.
For example:
% mcmu mctuner -h
Usage: mcmu mctuner < -h | -S | -P <options> >
Options:
-h, --help
show this help message and exit
-S, --status
show mctuner status in all zones
-P, --property set mctuner property in one zone
3.
To display help for a specific subcommand option, use this syntax:
mcmu subcommand subcommand_option -h
where:
■
■
subcommand is one of the mcmu subcommands.
subcommand_option is a valid option for the subcommand.
For example:
% mcmu status --zone -h
Usage: mcmu status --zone [-h] [-k NODENUM] [-n ZONENAME]
Options:
-h, --help
-k NODENUM, --kernelzone=NODENUM
node number (node1 or node2)
-n ZONENAME, --zonename=ZONENAME
zone name
show this help message and exit
Show kernel zone status, specified by
Show tenant zone status, specified by
Using the MCMU CLI
185
186
Oracle MiniCluster S7-2 Administration Guide • March 2017
Listing Version, Group, and VM Details (CLI)
Note - For information about displaying the status of VMs and zones, see “Obtaining Status
(CLI)” on page 205.
These topics describe how to display information about the MCMU version, VM group profiles,
and VMs:
Description
Links
Determine the version of the MCMU
software.
“List the MCMU Version (CLI)” on page 188
List information about DB VMs.
“List a Summary of All DB VM Groups (CLI)” on page 188
“List a Summary of a DB VM Group Profile
(CLI)” on page 188
“List Details of a DB VM Group Profile (CLI)” on page 189
“List Details for a DB VM Group (CLI)” on page 192
“List All DB Homes in a Group (CLI)” on page 195
“List Details for a DB Home (CLI)” on page 195
“List All DB Instances in a Group (CLI)” on page 196
“List Details of a DB Instance (CLI)” on page 197
List information about App VMs.
“List a Summary of All App VM Group Profiles
(CLI)” on page 197
“List Details of an App Group Profile (CLI)” on page 199
“List a Summary of All App VMs (CLI)” on page 200
“List Details of an App VM (CLI)” on page 201
List VM IP addresses and hostnames
“List the IP and Hostname Entries for DNS (CLI)” on page 202
Listing Version, Group, and VM Details (CLI)
187
List the MCMU Version (CLI)
List the MCMU Version (CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Type:
% mcmu -V
Oracle MiniCluster Configuration Utility
MCMU v1.1.18
List a Summary of All DB VM Groups (CLI)
Use this procedure to list information about DB groups.
This procedure also lists DB VMgroupIDs, which are required to perform other CLI commands.
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Type:
% mcmu tenant -G -l
Listing DB VM Group...
Status : Active
Description :
VMgroupName : dbzg2
editable : True
deletable : True
progress : False
VMgroupID : 1
List a Summary of a DB VM Group Profile (CLI)
Use this procedure to list information about DB groups.
This procedure also lists DB VMgroupIDs, which are required to perform other CLI commands.
188
Oracle MiniCluster S7-2 Administration Guide • March 2017
List Details of a DB VM Group Profile (CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Type:
% mcmu tenant -P -l
Examples:
■
This is an example of a system that does not have any DB VM group profiles configured:
% mcmu tenant -P -l
Listing DB VM Group Profile..
No VM Group Profiles available yet
■
This is an example of a system with one DB VM group profile:
% mcmu tenant -P -l
Listing DB VM Group Profile..
Status : Active
EditStatus :
Description : Initial DB VM Group
- NORMAL redundancy
- Shared Storage
- CIS
deletable : True
progress : False
VMgroupName : dbgp1
editable : True
VMgroupID : 1
List Details of a DB VM Group Profile (CLI)
Use this procedure to list details about a DB VM group profile.
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Use this syntax:
% mcmu tenant -P -L VMgroupID
Listing Version, Group, and VM Details (CLI)
189
List Details of a DB VM Group Profile (CLI)
where VMgroupID is the ID of the DB VM group profile. To determine the VMgroupID,
see .“List a Summary of a DB VM Group Profile (CLI)” on page 188
For example, to get details on a DB VM group profile with an ID of 1, type:
% mcmu tenant -P -L 1
Getting DB VM Group Profile...
GRID DEFINITION
Status : Active
inventoryLocation : /u01/app/oraInventory
gridLocation : /u01/app/12.1.0.2/grid
redoDiskGroup : HIGH
dataDiskGroup : NORMAL
recoDiskGroup : NORMAL
SCAN_name : dbgp1-scan
SCAN_ip : 10.129.115.204,10.129.115.205,10.129.115.206
STORAGE DEFINITION
redundancy : NORMAL
numberOfDisks : None
storageArrays :
DB VM GROUP DEFINITION
status : Active
VMGroupDesc : Initial DB VM Group
- NORMAL redundancy
- Shared Storage
- CIS
VMGroupType : database
VMGroupName : dbgrp1
operationType : DBZoneGroup_MapIP
VMGroupID : 1
globalName : mc3-n1,mc3-n2
compliance benchmark : No
shared storage : Yes
DB VM DEFINITIONS
VM 1
status : Active
id : 1
name : dbgp1-vm1-mc3-n1
globalName : mc3-n1
cores : 0
DNSServers : 10.209.76.197,10.209.76.198
190
Oracle MiniCluster S7-2 Administration Guide • March 2017
List Details of a DB VM Group Profile (CLI)
memory : 522496
virtualNetworks
private_ip : 192.168.10.60
private_hostname : mc3-n1vm1-z1-priv
private_mask : 24
public_ip : 10.129.115.196
public_hostname : mc3-n1vm1-z1
public_mask : 20
public_gateway : 10.129.112.1
virtual_ip : 10.129.115.197
virtual_hostname : mc3-n1vm1-z1-vip
VM 2
status : Active
id : 2
name : dbgp1-vm1-mc3-n2
globalName : mc3-n2
cores : 3
DNSServers : 10.209.76.197,10.209.76.198
memory : 522496
virtualNetworks
private_ip : 192.168.10.61
private_hostname : mc3-n2vm1-z1-priv
private_mask : 24
public_ip : 10.129.115.200
public_hostname : mc3-n2vm1-z1
public_mask : 20
public_gateway : 10.129.112.1
virtual_ip : 10.129.115.201
virtual_hostname : mc3-n2vm1-z1-vip
VM 3
status : Active
id : 3
name : dbgp1-vm2-mc3-n1
globalName : mc3-n1
cores : 0
DNSServers : 10.209.76.197,10.209.76.198
memory : 522496
virtualNetworks
private_ip : 192.168.10.62
private_hostname : mc3-n1vm1-z2-priv
private_mask : 24
public_ip : 10.129.115.198
public_hostname : mc3-n1vm1-z2
public_mask : 20
public_gateway : 10.129.112.1
virtual_ip : 10.129.115.199
Listing Version, Group, and VM Details (CLI)
191
List Details for a DB VM Group (CLI)
virtual_hostname : mc3-n1vm1-z2-vip
VM 4
status : Active
id : 4
name : dbgp1-vm2-mc3-n2
globalName : mc3-n2
cores : 2
DNSServers : 10.209.76.197,10.209.76.198
memory : 522496
virtualNetworks
private_ip : 192.168.10.63
private_hostname : mc3-n2vm1-z2-priv
private_mask : 24
public_ip : 10.129.115.202
public_hostname : mc3-n2vm1-z2
public_mask : 20
public_gateway : 10.129.112.1
virtual_ip : 10.129.115.203
virtual_hostname : mc3-n2vm1-z2-vip
List Details for a DB VM Group (CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Use this syntax:
% mcmu tenant -G -L VMgroupID
where VMgroupID is the ID of the DB VM group profile. To determine the VMgroupID,
see .“List a Summary of All DB VM Groups (CLI)” on page 188
For example:
% mcmu tenant -G -L 1
Getting DB VM Group Profile...
GRID DEFINITION
Status : Active
inventoryLocation : /u01/app/oraInventory
gridLocation : /u01/app/12.1.0.2/grid
redoDiskGroup : HIGH
dataDiskGroup : NORMAL
recoDiskGroup : NORMAL
SCAN_name : dbgp1-scan
192
Oracle MiniCluster S7-2 Administration Guide • March 2017
List Details for a DB VM Group (CLI)
SCAN_ip : 10.129.115.204,10.129.115.205,10.129.115.206
STORAGE DEFINITION
redundancy : NORMAL
numberOfDisks : None
storageArrays :
DB VM GROUP DEFINITION
status : Active
VMGroupDesc : DB MVM Group 1 - NORMAL - SHARED - CIS
VMGroupType : database
VMGroupName : dbgp1
operationType : DBZoneGroup_MapIP
VMGroupID : 1
globalName : mc3-n1,mc3-n2
compliance benchmark : No
shared storage : Yes
DB VM DEFINITIONS
VM 1
status : Active
id : 1
name : dbgp1-vm1-mc3-n1
globalName : mc3-n1
cores : 4
DNSServers : 10.209.76.197,10.209.76.198
memory : 522496
virtualNetworks
private_ip : 192.168.10.66
private_hostname : mc3-n1vm1-z1-priv
private_mask : 24
public_ip : 10.129.115.196
public_hostname : mc3-n1vm1-z1
public_mask : 20
public_gateway : 10.129.112.1
virtual_ip : 10.129.115.197
virtual_hostname : mc3-n1vm1-z1-vip
VM 2
status : Active
id : 2
name : dbgp1-vm2-mc3-n1
globalName : mc3-n1
cores : 3
DNSServers : 10.209.76.197,10.209.76.198
memory : 522496
virtualNetworks
Listing Version, Group, and VM Details (CLI)
193
List Details for a DB VM Group (CLI)
private_ip : 192.168.10.67
private_hostname : mc3-n1vm1-z2-priv
private_mask : 24
public_ip : 10.129.115.198
public_hostname : mc3-n1vm1-z2
public_mask : 20
public_gateway : 10.129.112.1
virtual_ip : 10.129.115.199
virtual_hostname : mc3-n1vm1-z2-vip
VM 3
status : Active
id : 3
name : dbgp1-vm1-mc3-n2
globalName : mc3-n2
cores : 0
DNSServers : 10.209.76.197,10.209.76.198
memory : 522496
virtualNetworks
private_ip : 192.168.10.68
private_hostname : mc3-n2vm1-z1-priv
private_mask : 24
public_ip : 10.129.115.200
public_hostname : mc3-n2vm1-z1
public_mask : 20
public_gateway : 10.129.112.1
virtual_ip : 10.129.115.201
virtual_hostname : mc3-n2vm1-z1-vip
VM 4
status : Active
id : 4
name : dbgp1-vm2-mc3-n2
globalName : mc3-n2
cores : 0
DNSServers : 10.209.76.197,10.209.76.198
memory : 522496
virtualNetworks
private_ip : 192.168.10.69
private_hostname : mc3-n2vm1-z2-priv
private_mask : 24
public_ip : 10.129.115.202
public_hostname : mc3-n2vm1-z2
public_mask : 20
public_gateway : 10.129.112.1
virtual_ip : 10.129.115.203
virtual_hostname : mc3-n2vm1-z2-vip
194
Oracle MiniCluster S7-2 Administration Guide • March 2017
List All DB Homes in a Group (CLI)
List All DB Homes in a Group (CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Use this syntax:
% mcmu tenant -H -l VMgroupID
where VMgroupID is the DB VM group ID. To determine the VMgroupID, see .“List a
Summary of a DB VM Group Profile (CLI)” on page 188
In this example, the home_ID is listed in the left column (ID: 1, ID: 9, ID: 2, and so on).
% mcmu tenant -H -l 1
LIST OF DB HOMES IN DB VM GROUP 1
ID:
ID:
ID:
ID:
ID:
ID:
ID:
ID:
ID:
ID:
ID:
ID:
ID:
ID:
ID:
ID:
1, VM_ID: 1, TYPE: RAC, STATUS: Active
9, VM_ID: 1, TYPE: RAC, STATUS: Active
2, VM_ID: 2, TYPE: RAC, STATUS: Active
10, VM_ID: 2, TYPE: RAC, STATUS: Active
3, VM_ID: 3, TYPE: RAC, STATUS: Active
11, VM_ID: 3, TYPE: RAC, STATUS: Active
4, VM_ID: 4, TYPE: RAC, STATUS: Active
12, VM_ID: 4, TYPE: RAC, STATUS: Active
5, VM_ID: 13, TYPE: RAC, STATUS: Active
13, VM_ID: 13, TYPE: RAC, STATUS: Active
6, VM_ID: 14, TYPE: RAC, STATUS: Active
14, VM_ID: 14, TYPE: RAC, STATUS: Active
7, VM_ID: 15, TYPE: RAC, STATUS: Active
15, VM_ID: 15, TYPE: RAC, STATUS: Active
8, VM_ID: 16, TYPE: RAC, STATUS: Active
16, VM_ID: 16, TYPE: RAC, STATUS: Active
List Details for a DB Home (CLI)
Use this procedure to list the details about a DB home.
1.
Log into the MCMU CLI.
See “Log in to the MCMU CLI” on page 29.
2.
Use this syntax:
Listing Version, Group, and VM Details (CLI)
195
List All DB Instances in a Group (CLI)
% mcmu tenant -H -L home_ID
where home_ID is the ID of the DB home. To determine the home_ID, see “List All DB Homes
in a Group (CLI)” on page 195.
For example:
% mcmu tenant -H -L 2
DB HOME INFORMATION
ID: 2
VM_ID: 2
VMGROUP_ID: 1
DB_HOME: /u01/app/oracle/product/12.1.0/db_12c
VERSION: 12.1.0.2
TYPE: RAC
PATCH: 12.1.0.2.160419
STATUS: Active
List All DB Instances in a Group (CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Use this syntax:
% mcmu tenant -I -l VMgroupID
where VMgroupID is DB VM group ID. To determine the VMgroupID, see .“List a Summary of
a DB VM Group Profile (CLI)” on page 188
In this example, the instance_ID is listed in the left column (ID: 3, ID: 4, ID: 7, and so on).
mcmu tenant -I -l 1
LIST OF DB INSTANCES IN DB VM GROUP 1
ID:
ID:
ID:
ID:
ID:
196
3, NAME: ol12racC,
4, NAME: ol12racC,
7, NAME: dw11rac1,
8, NAME: dw11rac1,
10, NAME: dw12sin,
VM_ID:
VM_ID:
VM_ID:
VM_ID:
VM_ID:
Oracle MiniCluster S7-2 Administration Guide • March 2017
1, DBHOME_ID: 1, TYPE: RAC, STATUS: Active
2, DBHOME_ID: 2, TYPE: RAC, STATUS: Active
3, DBHOME_ID: 11, TYPE: RACONENODE, STATUS: Active
4, DBHOME_ID: 12, TYPE: RACONENODE, STATUS: Active
15, DBHOME_ID: 7, TYPE: SINGLE, STATUS: Active
List Details of a DB Instance (CLI)
List Details of a DB Instance (CLI)
Use this procedure to list the details for all the DB instances in a DB home.
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Use this syntax:
% mcmu tenant -I -L instance_ID
where instance_ID is the ID of the instance. To determine the instance_ID, see .“List All DB
Instances in a Group (CLI)” on page 196.
For example, to list details on a DB instance with an ID of 3, type:
% mcmu tenant -I -l 1
Setting ssh timeout before carrying out further operations. Please wait..
[INFO
] Log file path : /var/opt/oracle.minicluster/setup/logs/
tenant_cli_100316_155137.log
LIST OF DB INSTANCES IN DB VM GROUP 1
ID: 1, NAME: si1, VM_ID: 1, DBHOME_ID: 1, TYPE: SINGLE, STATUS: Active
ID: 2, NAME: ins7, VM_ID: 1, DBHOME_ID: 1, TYPE: SINGLE, STATUS: Active
List a Summary of All App VM Group Profiles (CLI)
Use this procedure to a summary of App VM group profiles.
This procedure also lists App VMgroupIDs, which are required to perform other CLI
commands.
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Type:
% mcmu tenant -A -l
For example:
Listing Version, Group, and VM Details (CLI)
197
List a Summary of All App VM Group Profiles (CLI)
% mcmu tenant -A -l
Listing APP VM Group...
Status : Active
EditStatus :
Description : Drama App VM Group
- shared
- multiple
- CIS
deletable : True
progress : False
VMgroupName : avm1
editable : True
VMgroupID : 2
Status : Active
EditStatus :
Description : Thriller App VM Group - Multiple
- shared
- PCI-DSS
deletable : True
progress : False
VMgroupName : avm2
editable : True
VMgroupID : 3
Status : Active
EditStatus :
Description : Documentary App VM Group
- single
- no shared storage
- pci-dss
deletable : True
progress : False
VMgroupName : avm3
editable : True
VMgroupID : 4
Status : Active
EditStatus :
Description : Sci-Fi App VM Group
- single
- no shared storage
- CIS
deletable : True
progress : False
198
Oracle MiniCluster S7-2 Administration Guide • March 2017
List Details of an App Group Profile (CLI)
VMgroupName : avm5
editable : True
VMgroupID : 5
List Details of an App Group Profile (CLI)
Use this procedure to list the details for an App group profile.
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Use this syntax:
% mcmu tenant -A -L VMgroupID
where VMgroupID is the App group profile ID. To determine the VMgroupID, see .“List a
Summary of All App VM Group Profiles (CLI)” on page 197.
For example:
% mcmu tenant -A -L 2
Getting APP VM Group...
APP VM GROUP DEFINITION
status : Active
description : Drama App VM Group
- shared
- multiple
- CIS
globalName : mc3-n1,mc3-n2
Name : avm1
Type : application
ID : 2
compliance benchmark : No
APP VM DEFINITION
APPVM 1
id : 5
status : Active
name : avm1-vm1-mc3-n1
globalName : mc3-n1
cores : 0
DNSServers : 10.209.76.197,10.209.76.198
memory : 522496
Listing Version, Group, and VM Details (CLI)
199
List a Summary of All App VMs (CLI)
virtualNetworks
private_ip : 192.168.10.64
private_hostname : mc3-n1vm2-az1-priv
private_mask : 24
public_ip : 10.129.115.207
public_hostname : mc3-n1vm2-az1
public_mask : 20
public_gateway : 10.129.112.1
virtual_ip :
virtual_hostname : mc3-n1vm2-az1-vip
APPVM 2
id : 6
status : Active
name : avm1-vm1-mc3-n2
globalName : mc3-n2
cores : 2
DNSServers : 10.209.76.197,10.209.76.198
memory : 522496
virtualNetworks
private_ip : 192.168.10.65
private_hostname : mc3-n2vm2-az1-priv
private_mask : 24
public_ip : 10.129.115.208
public_hostname : mc3-n2vm2-az1
public_mask : 20
public_gateway : 10.129.112.1
virtual_ip :
virtual_hostname : mc3-n2vm2-az1-vip
List a Summary of All App VMs (CLI)
Use this procedure to a summary of App VM group profiles.
This procedure also lists App VMgroupIDs, which are required to perform other CLI
commands.
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Type:
% mcmu tenant -V -l
Listing APP VM Group...
200
Oracle MiniCluster S7-2 Administration Guide • March 2017
List Details of an App VM (CLI)
Status : Active
VMgroupName : mc12appzg2
Description : zonegroup description
VMgroupID : 2
List Details of an App VM (CLI)
Use this procedure to list the details for an App group profile.
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Use this syntax:
% mcmu tenant -V -L VMgroupID
where VMgroupID is the App group profile ID. To determine the VMgroupID, see “List a
Summary of All App VM Group Profiles (CLI)” on page 197.
% mcmu tenant -V -L 2
Setting ssh timeout before carrying out further operations. Please wait..
[INFO
] Log file path : /var/opt/oracle.minicluster/setup/logs/
tenant_cli_100316_161932.log
Getting APP VM Group...
APP VM GROUP DEFINITION
status : Active
description : zonegroup description
Name : mc12appzg2
Type : application
ID : 2
Security Profile : No
EXTERNAL NFS
APP VM DEFINITION
APPVM 1
id : 5
status : Active
name : mc12appzg2n1
globalName : mc12-n1
cores : 3
Listing Version, Group, and VM Details (CLI)
201
List the IP and Hostname Entries for DNS (CLI)
DNSServers : 10.209.76.197,10.209.76.198,192.135.82.132
memory : 522496
virtualNetworks
private_ip : 192.168.10.64
private_hostname : mc12appzg2n1-pub-priv
private_mask : 24
public_ip : 10.129.73.68
public_hostname : mc12appzg2n1-pub
public_mask : 22
public_gateway : 10.129.72.1
virtual_ip :
virtual_hostname : mc12appzg2n1-pub-vip
APPVM 2
id : 6
status : Active
name : mc12appzg2n2
globalName : mc12-n2
cores : 3
DNSServers : 10.209.76.197,10.209.76.198,192.135.82.132
memory : 522496
virtualNetworks
private_ip : 192.168.10.65
private_hostname : mc12appzg2n2-pub-priv
private_mask : 24
public_ip : 10.129.73.69
public_hostname : mc12appzg2n2-pub
public_mask : 22
public_gateway : 10.129.72.1
virtual_ip :
virtual_hostname : mc12appzg2n2-pub-vip
List the IP and Hostname Entries for DNS (CLI)
Use this procedure to see a list of hostname and IP addresses that should be mapped in DNS.
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Type:
% mcmu tenant -M -n
IP
| HOSTNAME
-------------+-----------------------------
202
Oracle MiniCluster S7-2 Administration Guide • March 2017
List the IP and Hostname Entries for DNS (CLI)
10.129.73.68
10.129.73.69
10.129.73.76
10.129.73.77
|
|
|
|
mc12dbzg1-zone-3-mc12-n1
mc12dbzg1-zone-3-mc12-n1-vip
mc12dbzg1-zone-3-mc12-n2
mc12dbzg1-zone-3-mc12-n2-vip
Listing Version, Group, and VM Details (CLI)
203
204
Oracle MiniCluster S7-2 Administration Guide • March 2017
Obtaining Status (CLI)
These topics describe how to view various aspects of the system status:
■
“Show the Status of Zones and DB VMs (CLI)” on page 205
“Show the Kernel Zone GI Status (CLI)” on page 206
“Show the GI Status of a DB VM (CLI)” on page 208
“Show Kernel Zone Status (CLI)” on page 209
“Show the VM Status (CLI)” on page 210
“Check the Status of the GI on the Kernel Zone (CLI)” on page 210
■
“Run orachk Health Checks (CLI)” on page 212
■
■
■
■
■
Note - For mcmu commands that list information about zones and VMs, see “Listing Version,
Group, and VM Details (CLI)” on page 187.
Show the Status of Zones and DB VMs (CLI)
Use this procedure to display the status of the zones on both nodes.
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Type:
% mcmu status -Z -a
In this example, the zones are identified as:
■
global – the global zone.
■
acfskz – the kernel zone.
DB_VMname – the DB VMs.
■
For zone descriptions, see “MiniCluster Zones Overview” on page 19.
Obtaining Status (CLI)
205
Show the Kernel Zone GI Status (CLI)
% mcmu status -Z -a
[INFO
] Zone status on node1
ID NAME
STATUS
0 global
running
2 acfskz
running
7 dbgp1-vm1-mc3-n1 running
8 dbgp1-vm2-mc3-n1 running
- appzonetemplate installed
- dbzonetemplate installed
[INFO
] Zone status on node2
ID NAME
STATUS
0 global
running
2 acfskz
running
7 dbgp1-vm1-mc3-n2 running
8 dbgp1-vm2-mc3-n2 running
- appzonetemplate installed
- dbzonetemplate installed
PATH
BRAND
/
solaris
solaris-kz
/mcpool/dbgp1-vm1-mc3-n1zroot solaris
/mcpool/dbgp1-vm2-mc3-n1zroot solaris
/mcpool/appzonetemplate
solaris
/mcpool/dbzonetemplate
solaris
IP
shared
excl
excl
excl
excl
excl
PATH
BRAND
/
solaris
solaris-kz
/mcpool/dbgp1-vm1-mc3-n2zroot solaris
/mcpool/dbgp1-vm2-mc3-n2zroot solaris
/mcpool/appzonetemplate
solaris
/mcpool/dbzonetemplate
solaris
IP
shared
excl
excl
excl
excl
excl
Show the Kernel Zone GI Status (CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Type:
% mcmu status -G -k
-------------------------------------------------------------------------------Name
Target State
Server
State details
-------------------------------------------------------------------------------Local Resources
-------------------------------------------------------------------------------ora.LISTENER.lsnr
ONLINE ONLINE
mc2ss01
STABLE
ONLINE ONLINE
mc2ss02
STABLE
ora.OCRVOTE.dg
ONLINE ONLINE
mc2ss01
STABLE
ONLINE ONLINE
mc2ss02
STABLE
ora.SHARED.COMMONVOL.advm
ONLINE ONLINE
mc2ss01
STABLE
ONLINE ONLINE
mc2ss02
Volume device /dev/a
sm/commonvol-230 is
online,STABLE
ora.SHARED.SSVOL.advm
ONLINE ONLINE
mc2ss01
STABLE
206
Oracle MiniCluster S7-2 Administration Guide • March 2017
Show the Kernel Zone GI Status (CLI)
ONLINE ONLINE
mc2ss02
Volume device /dev/a
sm/ssvol-230 is onli
ne,STABLE
ONLINE ONLINE
ONLINE ONLINE
mc2ss01
mc2ss02
STABLE
STABLE
ONLINE ONLINE
ONLINE ONLINE
ora.net1.network
ONLINE ONLINE
ONLINE ONLINE
ora.ons
ONLINE ONLINE
ONLINE ONLINE
ora.shared.commonvol.acfs
ONLINE ONLINE
mc2ss01
mc2ss02
Started,STABLE
Started,STABLE
mc2ss01
mc2ss02
STABLE
STABLE
mc2ss01
mc2ss02
STABLE
STABLE
mc2ss01
ONLINE ONLINE
mc2ss02
mounted on /mnt/comm
onfs,STABLE
mounted on /mnt/comm
onfs,STABLE
ora.shared.ssvol.acfs
ONLINE ONLINE
mc2ss01
ora.SHARED.dg
ora.asm
mounted on /mnt/shar
edstore,STABLE
ONLINE ONLINE
mc2ss02
mounted on /mnt/shar
edstore,STABLE
-------------------------------------------------------------------------------Cluster Resources
-------------------------------------------------------------------------------ora.LISTENER_SCAN1.lsnr
1
ONLINE ONLINE
mc2ss02
STABLE
ora.LISTENER_SCAN2.lsnr
1
ONLINE ONLINE
mc2ss01
STABLE
ora.LISTENER_SCAN3.lsnr
1
ONLINE ONLINE
mc2ss01
STABLE
ora.MGMTLSNR
1
ONLINE ONLINE
mc2ss01
169.254.96.22 192.16
8.10.250,STABLE
ora.commonfs.export
1
ONLINE ONLINE
mc2ss02
STABLE
ora.cvu
1
ONLINE ONLINE
mc2ss01
STABLE
ora.mc2ss01.vip
1
ONLINE ONLINE
mc2ss01
STABLE
ora.mc2ss02.vip
1
ONLINE ONLINE
mc2ss02
STABLE
ora.mgmtdb
1
ONLINE ONLINE
mc2ss01
Open,STABLE
ora.oc4j
Obtaining Status (CLI)
207
Show the GI Status of a DB VM (CLI)
1
ONLINE ONLINE
mc2ss01
STABLE
ora.omcss.havip
1
ONLINE ONLINE
mc2ss02
STABLE
ora.scan1.vip
1
ONLINE ONLINE
mc2ss02
STABLE
ora.scan2.vip
1
ONLINE ONLINE
mc2ss01
STABLE
ora.scan3.vip
1
ONLINE ONLINE
mc2ss01
STABLE
ora.sharedstore.export
1
ONLINE ONLINE
mc2ss02
STABLE
--------------------------------------------------------------------------------
Show the GI Status of a DB VM (CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Use this syntax:
% mcmu status -G -n VMgroupname
where VMgroupname is the name of the DB VM group. To determine the VMgroupname, see
“List a Summary of All DB VM Groups (CLI)” on page 188.
For example:
% mcmu status -G -n dbvmg1
-------------------------------------------------------------------------------Name
Target State
Server
State details
-------------------------------------------------------------------------------Local Resources
-------------------------------------------------------------------------------ora.DATA.dg
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n1 STABLE
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n2 STABLE
ora.LISTENER.lsnr
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n1 STABLE
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n2 STABLE
ora.RECO.dg
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n1 STABLE
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n2 STABLE
ora.REDO.dg
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n1 STABLE
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n2 STABLE
208
Oracle MiniCluster S7-2 Administration Guide • March 2017
Show Kernel Zone Status (CLI)
ora.SYSTEM.dg
ONLINE ONLINE
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n1
dbzg2-zg2zone-1-mc2-n2
STABLE
STABLE
ora.asm
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n1 Started,STABLE
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n2 Started,STABLE
ora.net1.network
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n1 STABLE
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n2 STABLE
ora.ons
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n1 STABLE
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n2 STABLE
-------------------------------------------------------------------------------Cluster Resources
-------------------------------------------------------------------------------ora.LISTENER_SCAN1.lsnr
1
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n2 STABLE
ora.LISTENER_SCAN2.lsnr
1
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n1 STABLE
ora.LISTENER_SCAN3.lsnr
1
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n1 STABLE
ora.MGMTLSNR
1
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n1 169.254.186.82 192.1
68.10.60,STABLE
ora.cvu
1
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n1 STABLE
ora.dbzg2-zg2zone-1-mc2-n1.vip
1
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n1 STABLE
ora.dbzg2-zg2zone-1-mc2-n2.vip
1
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n2 STABLE
ora.mgmtdb
1
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n1 Open,STABLE
ora.oc4j
1
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n1 STABLE
ora.scan1.vip
1
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n2 STABLE
ora.scan2.vip
1
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n1 STABLE
ora.scan3.vip
1
ONLINE ONLINE
dbzg2-zg2zone-1-mc2-n1 STABLE
--------------------------------------------------------------------------------
Show Kernel Zone Status (CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
Obtaining Status (CLI)
209
Show the VM Status (CLI)
2.
Use this syntax:
% mcmu status -Z -k nodex
where x is either 1 or 2.
For example:
% mcmu status -Z -k node1
[INFO
] Log file path :
/var/opt/oracle.minicluster/setup/logs/mcmu_050616_112555.log
ID NAME
STATUS
PATH
BRAND
IP
2 acfskz
running
solaris-kz excl
Show the VM Status (CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Use this syntax:
% mcmu status -Z --zonename=VMname
where VMname is the name of the VM. To determine the name of a DB VM, see “List Details
of a DB VM Group Profile (CLI)” on page 189. For an App VM, see “List Details of an App
Group Profile (CLI)” on page 199.
For example:
% mcmu status -Z -n dbgp1-vm1-mc3-n1
ID NAME
STATUS
7 dbgp1-vm1-mc3-n1 running
PATH
BRAND
/mcpool/dbgp1-vm1-mc3-n1zroot solaris
IP
excl
Check the Status of the GI on the Kernel Zone (CLI)
Use this procedure to check the status of the grid infrastructure in a kernel zone.
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Type:
% mcmu status -G -k
210
Oracle MiniCluster S7-2 Administration Guide • March 2017
Check the Status of the GI on the Kernel Zone (CLI)
INFO:MCMU.controllers.common.pexpect_util:su to user root successfully.
-------------------------------------------------------------------------------Name
Target State
Server
State details
-------------------------------------------------------------------------------Local Resources
-------------------------------------------------------------------------------ora.LISTENER.lsnr
ONLINE ONLINE
mc3ss01
STABLE
ONLINE ONLINE
mc3ss02
STABLE
ora.OCRVOTE.dg
ONLINE ONLINE
mc3ss01
STABLE
ONLINE ONLINE
mc3ss02
STABLE
ora.SHARED.COMMONVOL.advm
ONLINE ONLINE
mc3ss01
STABLE
ONLINE ONLINE
mc3ss02
Volume device /dev/a
sm/commonvol-377 is
online,STABLE
ora.SHARED.SSVOL.advm
ONLINE ONLINE
mc3ss01
STABLE
ONLINE ONLINE
mc3ss02
Volume device /dev/a
sm/ssvol-377 is onli
ne,STABLE
ora.SHARED.dg
ONLINE ONLINE
mc3ss01
STABLE
ONLINE ONLINE
mc3ss02
STABLE
ora.asm
ONLINE ONLINE
mc3ss01
Started,STABLE
ONLINE ONLINE
mc3ss02
Started,STABLE
ora.net1.network
ONLINE ONLINE
mc3ss01
STABLE
ONLINE ONLINE
mc3ss02
STABLE
ora.ons
ONLINE ONLINE
mc3ss01
STABLE
ONLINE ONLINE
mc3ss02
STABLE
ora.shared.commonvol.acfs
ONLINE ONLINE
mc3ss01
mounted on /commonfs
,STABLE
ONLINE ONLINE
mc3ss02
mounted on /commonfs
,STABLE
ora.shared.ssvol.acfs
ONLINE ONLINE
mc3ss01
mounted on /sharedst
ore,STABLE
ONLINE ONLINE
mc3ss02
mounted on /sharedst
ore,STABLE
-------------------------------------------------------------------------------Cluster Resources
--------------------------------------------------------------------------------
Obtaining Status (CLI)
211
Run orachk Health Checks (CLI)
ora.LISTENER_SCAN1.lsnr
1
ONLINE ONLINE
ora.LISTENER_SCAN2.lsnr
1
ONLINE ONLINE
ora.LISTENER_SCAN3.lsnr
1
ONLINE ONLINE
ora.MGMTLSNR
1
ONLINE ONLINE
mc3ss02
STABLE
mc3ss01
STABLE
mc3ss01
STABLE
mc3ss01
xxx.xxx.xxx.144 192.
xxx.xx.250,STABLE
ora.commonfs.export
1
ONLINE ONLINE
mc3ss01
STABLE
ora.cvu
1
ONLINE ONLINE
mc3ss01
STABLE
ora.mc3ss01.vip
1
ONLINE ONLINE
mc3ss01
STABLE
ora.mc3ss02.vip
1
ONLINE ONLINE
mc3ss02
STABLE
ora.mgmtdb
1
ONLINE ONLINE
mc3ss01
Open,STABLE
ora.oc4j
1
ONLINE ONLINE
mc3ss01
STABLE
ora.omcss.havip
1
ONLINE ONLINE
mc3ss01
STABLE
ora.scan1.vip
1
ONLINE ONLINE
mc3ss02
STABLE
ora.scan2.vip
1
ONLINE ONLINE
mc3ss01
STABLE
ora.scan3.vip
1
ONLINE ONLINE
mc3ss01
STABLE
ora.sharedstore.export
1
ONLINE ONLINE
mc3ss01
STABLE
-------------------------------------------------------------------------------%
Run orachk Health Checks (CLI)
Use this procedure to run health checks on database VMs. ORAchk does not run on APP VMs.
Before you can run ORAchk, you must download it and install it in the database VMs.
For more information about ORAchk, refer to “ORAchk Overview” on page 16.
212
1.
Log in to a database VM and assume the root role.
See “Log in to a DB VM” on page 30.
2.
Change to the directory where orachk is installed.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Run orachk Health Checks (CLI)
3.
Run orachk.
root@mc1dbzg1-mc1zg1zone1:~# ./orachk
CRS stack is running and CRS_HOME is not set. Do you want to set
CRS_HOME to /u01/app/12.1.0.2/grid?[y/n][y]y
Checking for prompts on mc1dbzg1-mc1zg1zone1 for oracle user...
Checking ssh user equivalency settings on all nodes in cluster
Node mc1dbzg1-mc1zg1zone2 is not configured for ssh user equivalency and the script uses
ssh to execute checks on remote nodes.
Without this facility the script cannot run audit checks on the remote nodes.
If necessary due to security policies the script can be run individually on each node.
Do you want to configure SSH for user root on mc1dbzg1-mc1zg1zone2
Enter root password on mc1dbzg1-mc1zg1zone2 :Verifying root password.
. .
Checking for prompts for oracle user on all nodes...
Searching for running databases . . . . .
. .
List of running databases registered in OCR
1.rac12c1
[y/n][y]y
2. None of above
Select databases from list for checking best practices. For multiple
select 1 for All or comma separated number like 1,2 etc
[1-2][1].1
databases,
. . . . . Checking Status of Oracle Software Stack - Clusterware, ASM,
RDBMS . . . . . . . . . . . .
-------------------------------------------------------------------------------------------------------
Oracle Stack Status
------------------------------------------------------------------------------------------------------Host Name CRS Installed RDBMS Installed CRS UP
ASM UP
RDBMS UP DB Instance
Name
------------------------------------------------------------------------------------------------------mc1dbzg1-mc1zg1zone1 Yes
Yes
Yes
Yes
Yes
rac12c11
------------------------------------------------------------------------------------------------------. . . . . . root passwords are incorrect or login to as root is
disabled in ssh
configuration for following nodes.
You can still continue but root privileged checks will not be executed on following
nodes.
1. mc1dbzg1-mc1zg1zone2
Do you want to continue[y/n][y]:- y
*** Checking Best Practice Recommendations (PASS/WARNING/FAIL) ***
Collections and audit checks log file is
/root/orachk_mc1dbzg1-mc1zg1zone1_rac12c1_061716_150741/log/orachk.log
Obtaining Status (CLI)
213
Run orachk Health Checks (CLI)
Checking for prompts in /root/.profile
on mc1dbzg1-mc1zg1zone1 for
root user...
=============================================================
Node name - mc1dbzg1-mc1zg1zone1
=============================================================
Collecting
Collecting
Collecting
Collecting
Collecting
Collecting
-
ASM
ASM
ASM
ASM
ASM
ASM
. . . . .
Disk Groups
Disk I/O stats
Diskgroup Attributes
disk partnership imbalance
diskgroup attributes
diskgroup usable free space
<output omitted>
Detailed report (html) /root/orachk_mc1dbzg1-mc1zg1zone1_rac12c1_061716_150741/orachk_mc1dbzg1mc1zg1zone1_rac12c1_061716_150741.html
UPLOAD(if required) /root/orachk_mc1dbzg1mc1zg1zone1_rac12c1_061716_150741.zip
214
Oracle MiniCluster S7-2 Administration Guide • March 2017
Starting and Stopping VM Components (CLI)
Use the MCMU CLI to start and stop individual VM and zone components.
Typically, the system is started and stopped using Oracle ILOM, which provides a lights-out
method for controlling the system. For Oracle ILOM starting instructions, see “Starting and
Stopping the System” on page 49. However, there can be situations where you need to start or
stop individual MiniCluster components such as the kernel zones. This section provides those
instructions:
■
■
“Starting VM Components (CLI)” on page 215
“Stopping VM Components (CLI)” on page 217
Starting VM Components (CLI)
Note - These topics assume that power is applied to the system, but the particular component
you plan to start is stopped.
These topics describe how to start individual VM and zone components.
■
■
■
■
■
“Start a Kernel Zone (CLI)” on page 215
“Start All VMs in a Group (CLI)” on page 216
“Start a Single VM (CLI)” on page 216
“Start the Grid Infrastructure for the Application VM Groups (CLI)” on page 217
“Start the Grid Infrastructure for the DB VM Group (CLI)” on page 217
Start a Kernel Zone (CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
Starting and Stopping VM Components (CLI)
215
Start All VMs in a Group (CLI)
2.
Use this syntax:
% mcmu start -Z -k nodex
where x is 1 or 2.
For example:
$ mcmu start -Z -k node1
Start All VMs in a Group (CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Use this syntax:
% mcmu start -V -n VMgroupname
where VMgroupname is the name of the VM group. To determine the name, see “List a
Summary of All DB VM Groups (CLI)” on page 188.
For example:
% mcmu start -V -n dbzg2
Start a Single VM (CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Use this syntax:
% mcmu start -Z -n VMname
where VMname is the name of the VM. To determine the name of a DB VM, see “List Details
of a DB VM Group Profile (CLI)” on page 189. For an App VM, see “List Details of an App
Group Profile (CLI)” on page 199.
For example:
% mcmu start -Z -n dbzg2-zone-1-mc2-n2
216
Oracle MiniCluster S7-2 Administration Guide • March 2017
Start the Grid Infrastructure for the Application VM Groups (CLI)
Start the Grid Infrastructure for the Application VM
Groups (CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Use this syntax:
% mcmu start -G -k nodex
where x is the node number (1 or 2).
For example:
% mcmu start -G -k node1
Start the Grid Infrastructure for the DB VM Group
(CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Use this syntax:
% mcmu start -G -n VMgroupname
where VMgroupname is the name of the DB VM group. To determine the group name, see “List
a Summary of All DB VM Groups (CLI)” on page 188.
For example:
% mcmu start -G -n dbgrp1
Stopping VM Components (CLI)
Caution - To properly shutdown the system, follow the instructions in “Shut Down, Reset, or
Power Cycle the System” on page 50. If the system is not properly shutdown, data corruption
can occur.
Starting and Stopping VM Components (CLI)
217
Stop the Grid Infrastructure in the DB VM Group (CLI)
These topics describe how to stop individual VM components:
■
■
■
■
■
“Stop the Grid Infrastructure in the DB VM Group (CLI)” on page 218
“Stop the Grid Infrastructure in an Application VM Group (CLI)” on page 218
“Stop All VMs in a Group (CLI)” on page 219
“Stop a Single VM (CLI)” on page 219
“Stop a Kernel Zone (CLI)” on page 219
Stop the Grid Infrastructure in the DB VM Group
(CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Use this syntax:
% mcmu stop -G -n VMgroupname
where VMgroupname is the name of the DB VM group. To determine the name, see “List a
Summary of All DB VM Groups (CLI)” on page 188.
For example:
% mcmu stop -G -n dbgrp1
Stop the Grid Infrastructure in an Application VM
Group (CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Use this syntax:
% mcmu stop -G -k nodex
where x is 1 or 2.
For example:
% mcmu stop -G -k node1
218
Oracle MiniCluster S7-2 Administration Guide • March 2017
Stop All VMs in a Group (CLI)
Stop All VMs in a Group (CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Use this syntax:
% mcmu stop -V -n VMgroupname
where VMgroupname is the name of the VM group. To determine the name, see “List a
Summary of All DB VM Groups (CLI)” on page 188.
For example:
% mcmu stop -V -n vm2
MCMU stops each VM in the group one by one. You are prompted to confirm the stopping of
each VM in the group.
Stop a Single VM (CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Use this syntax:
% mcmu stop -Z -n VMname
where VMname is the name of the VM. To determine the name of a DB VM, see “List Details
of a DB VM Group Profile (CLI)” on page 189. For an App VM, see “List Details of an App
Group Profile (CLI)” on page 199
For example:
% mcmu stop -Z -n dbzg2-zone-1-mc2-n2
Stop a Kernel Zone (CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
Starting and Stopping VM Components (CLI)
219
Stop a Kernel Zone (CLI)
2.
Use this syntax:
% mcmu stop -Z -k nodex
where x is 1 or 2.
For example, to stop the kernel zone on each node, type:
% mcmu stop -Z -k node1
% mcmu stop -Z -k node2
220
Oracle MiniCluster S7-2 Administration Guide • March 2017
Verifying that the System Is Ready for the
Creation of VMs (CLI)
Before you can create VMs, all of the system setup steps must be complete, and the state of the
system software, drives, and connectivity must be in expected healthy state. The MCMU CLI
provides a number of commands that enable you to verify various aspects of the system setup.
Note - To install and set up the system, refer to the MiniCluster S7-2 Installation Guide. To
locate the guide, refer to the “Product Documentation Library” on page 13.
These topics describe how to verify the setup, and run readiness checks through the CLI:
■
■
■
■
■
“List the System Setup Steps (CLI)” on page 221
“(If Needed) Run or Rerun System Setup Steps (CLI)” on page 223
“Verify the System Setup (CLI)” on page 224
“Verify the System, Topology, and Disk Readiness (CLI)” on page 225
“Add IP Addresses for Future VMs (CLI)” on page 227
List the System Setup Steps (CLI)
Use this procedure to determine if the system is set up, and to see if the setup process completed
all steps. The setup steps are normally run when the system is initially set up at installation
time.
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Display the list of setup steps and the status of each step.
This example indicates that all the system setup steps have been performed and completed with
a status of OK. The log file of the setup process is also displayed.
% mcmu setupmc -a
Verifying that the System Is Ready for the Creation of VMs (CLI)
221
List the System Setup Steps (CLI)
[INFO
] Log file path : mc_name-n1:/var/opt/oracle.minicluster/setup/logs/
mcmu_082216_160419.log
+----------------------------------------------------------------------------------------------------+
| STEP | DESCRIPTION
| STATUS |
+----------------------------------------------------------------------------------------------------+
| 1
| Check Package Version and Gather User Input
| OK
|
| 2
| Prepare for System Install
| OK
|
| 3
| Interconnect Setup
| OK
|
| 4
| Configure Explorer
| OK
|
| 5
| Check System Readiness
| OK
|
| 6
| Verify Topology
| OK
|
| 7
| Prepare Network Interfaces
| OK
|
| 8
| Configure Client Access Network on Node 1
| OK
|
| 9
| Configure Client Access Network on Node 2
| OK
|
| 10 | Configure NTP Client, Set Password Policy and Setup Apache Web Server
| OK
|
| 11 | Check Configuration and IP Mappings
| OK
|
| 12 | Configure ILOM Network
| OK
|
| 13 | Storage: Create Storage Alias, Reset JBOD(s) and Partition All Disks in All
JBOD(s) | OK
|
| 14 | Calibrate Disks in All JBOD(s)
| OK
|
| 15 | Shared Storage Setup: Configure and Secure All Kernel Zones
| OK
|
| 16 | Shared Storage Setup: Install Oracle Grid Infrastructure 12c in Kernel Zones
| OK
|
| 17 | Shared Storage Setup: Apply GI PSU
| OK
|
| 18 | Shared Storage Setup: Configure ACFS and Mount Shared Filesystem in Global
Zones
| OK
|
| 19 | Apply Global Zone Security Settings
| OK
|
+----------------------------------------------------------------------------------------------------+
222
Oracle MiniCluster S7-2 Administration Guide • March 2017
(If Needed) Run or Rerun System Setup Steps (CLI)
%
(If Needed) Run or Rerun System Setup Steps (CLI)
Use this procedure to run any system setup steps that have not been completed, or require
rerunning due to a possible problem. To determine the state of the system setup steps, see “List
the System Setup Steps (CLI)” on page 221.
Note - The setup steps are normally run when the system is initially set up at installation time.
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Perform one of these commands:
■
Run all the setup steps, type:
% mcmu setupmc -s all
■
Run a specific setup step, type:
% mcmu setupmc -s step-number
For example, to run step 1 in the system setup, type:
% mcmu setupmc -s 1
■
Run a range of setup steps, type:
% mcmu setupmc -s starting-step-number-ending-step-number
For example, to run steps 1 through 5 in the system setup, type:
% mcmu setupmc -s 1-5
■
Force a step to run, type:
This command forces a rerun of a step that previously completed successfully. Not all
steps are re-runnable.
% mcmu setupmc -s step-number -f
For example, to force a rerun on step 1 in the system setup, type:
% mcmu setupmc -s 1 -f
Verifying that the System Is Ready for the Creation of VMs (CLI)
223
Verify the System Setup (CLI)
■
Undo the last setup step (if it successfully completed), type:
You might need to perform this task if the setup process ran into an error. Check the log
files to see what step encountered an error. Then undo all the steps back to the faulted step,
then redo
% mcmu setupmc -u step-number
For example, to undo step 5, if step 5 was successfully completed, type:
% mcmu setupmc -u 5
Verify the System Setup (CLI)
Use this procedure to verify the setup process that was performed at installation time. This
procedure is similar to “List the System Setup Steps (CLI)” on page 221, but provides more
details about the setup process.
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Type:
% mcmu setupmc -v all
[INFO
] STEP 1: Gather User Inputs VERIFICATION STARTED
To DO://
[INFO
] STEP 1: Gather User Inputs VERIFICATION COMPLETED
[INFO
] STEP 2: Prepare for System Install VERIFICATION STARTED
[INFO
] Invoked by OS user: mcinstall
[INFO
] Find log at: mc2-n1:/var/opt/oracle.minicluster/setup/logs/
omc_crdb_verify_050516_164030.log
[INFO
] ---------- Starting Creating SQLite Database and Populating USER_INPUT Table
Verification
[INFO
] Check existence of entries in USER_INPUT table started.
[INFO
] Check existence of entries in USER_INPUT table succeeded.
[INFO
] Creating SQLite Database / Populating USER_INPUT Table Verification Completed
To DO://
[INFO
] STEP 2: Prepare for System Install VERIFICATION COMPLETED
[INFO
] STEP 3: Interconnect Setup VERIFICATION STARTED
:
[INFO
] Log file path : mc2-n1:/var/opt/oracle.minicluster/setup/logs/
omc_fn_hangepvtip_verify_050516_164031.log
[INFO
] Verifying reconfiguration of Interconnect IP address..
[INFO
] Verifying reconfiguration of Interconnect IP address.. Completed
224
Oracle MiniCluster S7-2 Administration Guide • March 2017
Verify the System, Topology, and Disk Readiness (CLI)
...
Verify the System, Topology, and Disk Readiness (CLI)
Use this procedure to run MCMU readiness checks to ensure that the system is ready for the
creation of VMs.
Readiness checks perform these verifications:
■
■
■
1.
System readiness – Checks to ensure that the MiniCluster hardware and software are
configured properly and at expected levels. This check is normally performed before the
system is configured, but you can run this feature any time.
Topology verification – Checks that the I/O card locations and verifies network
connectivity.
Disk calibration – Checks the health of the drives in the system. This feature performs read
and write tests on a reserved area of each drive. The check is not destructive to data.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Run all or an individual check.
% mcmu readiness -option
where option is one of these values:
■
a – Run all checks.
■
c – Run the disk calibration check.
■
h – Display the help for the readiness option.
■
s – Run the system readiness check.
■
t – Run the topology verification.
This is an example of running all of the readiness checks.
% mcmu readiness -a
[INFO
] Log file path : mc3-n1:/var/opt/oracle.minicluster/setup/logs/
mcmu_082216_171559.log
[INFO
] Log file path : mc3-n1:/var/opt/oracle.minicluster/setup/logs/
omc_sysready_combined_v2_082216_171559.log
[INFO
] [40;1;36m Checking for System Readiness..[0m
Aug 22 17:16:00 mccn su: 'su root' succeeded for mcinstall on /dev/pts/2
[INFO
] ___________________________REPORT________________________________
[INFO
] Description : Checking if aggrpvt0 aggregated link exists... OK
Verifying that the System Is Ready for the Creation of VMs (CLI)
225
Verify the System, Topology, and Disk Readiness (CLI)
[INFO
] Description
network.....OK
[INFO
] Description
mapping...OK
[INFO
] Description
slots...OK
[INFO
] Description
[INFO
] Description
[INFO
] Description
[INFO
] Description
[INFO
: Each node should be able to ping the other node over private
: Both nodes should have identical physical device - vanity name
: Both nodes should have the physical devices on the same
:
:
:
:
Checking
Checking
Checking
Checking
INT and EXT HBA
INT and EXT HBA
System firmware
System firmware
firmware version on
firmware version on
version on mc3-n1..
version on mc3-n2..
mc3-n1.. ...OK
mc3-n2.. ...OK
...OK
...OK
] [40;1;32mChecking for System Readiness.. Completed[0m
Aug 22 17:17:50 mccn su: 'su root' succeeded for mcinstall on /dev/pts/1
[INFO
] Invoked by OS user: root
[INFO
] Find log at: mc3-n1:/var/opt/oracle.minicluster/setup/logs/
omc_verifytopology_082216_171750.log
[INFO
] [40;1;36m---------- Starting Verify Toplogy[0m
[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.
<some output omitted.>
[INFO
] Log file path : mc3-n1:/var/opt/oracle.minicluster/setup/logs/
omc_diskcalib_v2_082216_171755.log
[INFO
] [40;1;36m Calibrating all disks ..[0m
[ HDD ] /dev/chassis/JBODARRAY1/HDD0/disk c0t5000CCA23B0FBDA4d0
[ HDD ] /dev/chassis/JBODARRAY1/HDD1/disk c0t5000CCA23B12B068d0
[ HDD ] /dev/chassis/JBODARRAY1/HDD2/disk c0t5000CCA23B12DA48d0
[ HDD ] /dev/chassis/JBODARRAY1/HDD3/disk c0t5000CCA23B12D4A4d0
[ HDD ] /dev/chassis/JBODARRAY1/HDD4/disk c0t5000CCA23B12C030d0
[ HDD ] /dev/chassis/JBODARRAY1/HDD5/disk c0t5000CCA23B12F358d0
[ SSD ] /dev/chassis/JBODARRAY1/HDD6/disk c0t5000CCA0536CA820d0
[ SSD ] /dev/chassis/JBODARRAY1/HDD7/disk c0t5000CCA0536CA788d0
[ SSD ] /dev/chassis/JBODARRAY1/HDD8/disk c0t5000CCA0536CB3ACd0
[ SSD ] /dev/chassis/JBODARRAY1/HDD9/disk c0t5000CCA0536CA818d0
<some output omitted.>
S U M M A R Y
R E P O R T
STORAGE GROUP: JBODARRAY1_SSD
Average Sequential Write Throughput:
226
Oracle MiniCluster S7-2 Administration Guide • March 2017
Add IP Addresses for Future VMs (CLI)
Achieved: 671 MB/s
Expected: ~690 MB/s
c0t5000CCA05351B45Cd0 : 661 MB/s
c0t5000CCA0536CAC08d0 : 652 MB/s
c0t5000CCA053558800d0 : 656 MB/s
<some output omitted.>
c0t5000CCA04E0DEBA8d0 : 719 MB/s
c0t5000CCA0536CA788d0 : 658 MB/s
STORAGE GROUP: JBODARRAY1_HDD
Average Sequential Write Throughput:
Achieved: 203 MB/s
Expected: ~195 MB/s
c0t5000CCA23B12C030d0
c0t5000CCA23B12DA48d0
c0t5000CCA23B0FBDA4d0
c0t5000CCA23B12D4A4d0
c0t5000CCA23B12B068d0
c0t5000CCA23B12F358d0
:
:
:
:
:
:
188
204
205
208
218
194
MB/s
MB/s
MB/s
MB/s
MB/s
MB/s
[INFO
] [40;1;32mCalibrating all disks .. Completed
[INFO
] Calibration report path : /var/opt/oracle.minicluster/setup/logs/
calibration_report.txt
%
Add IP Addresses for Future VMs (CLI)
Use this procedure to add IP addresses to MiniCluster so they can be applied to VMs as they are
created.
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Type:
% mcmu tenant -M -i
3.
When prompted, enter the starting IP address and the range.
Verifying that the System Is Ready for the Creation of VMs (CLI)
227
228
Oracle MiniCluster S7-2 Administration Guide • March 2017
Configuring DB VMs (CLI)
For information about planning for VMs, see “Planning to Create VMs” on page 61.
These topics provide CLI procedures for the DB VM groups and their associated components
(VMs, DB home, and DB instances):
■
■
■
“Creating DB VMs (CLI)” on page 229
“Update a DB VM Group (CLI)” on page 241
“Deleting DB VM Group Components (CLI)” on page 251
Creating DB VMs (CLI)
For information about planning for VMs, see “Planning to Create VMs” on page 61.
These topics describe how to create DB VMs:
■
■
■
■
“Create a DB VM Group Profile (CLI)” on page 229
“Deploy the DB VM Group (CLI)” on page 232
“Create DB Homes (CLI)” on page 234
“Create DB Instances (CLI)” on page 236
Create a DB VM Group Profile (CLI)
Use this procedure to create a DB VM group.
This task involves performing these activities:
■
■
1.
Create a DB VM group profile
Deploy the DB VM group
Log into the MCMU CLI as a primary admin, such as mcinstall.
Configuring DB VMs (CLI)
229
Create a DB VM Group Profile (CLI)
See “Log in to the MCMU CLI” on page 29.
2.
Create the DB VM group profile.
% mcmu tenant -P -c
You are prompted to enter DB VM group profile configuration information.
a.
Enter the necessary information for the DB VM group profile.
Listing DB VM Group Profile..
Database Virtual Machine Group Profile Description
Enter Virtual Machine Group Profile Name : dbgp1
Enter ASM Disk Group Redundancy [NORMAL,HIGH] (NORMAL): NORMAL
CIS Equivalent Security Settings are default.Do you want to enable PCI DSS Security
Settings [Yes,No] (No)? NO
Enter Number of VM(s) on Node 1, Max(4) (1): 2
Enter Number of VM(s) on Node 2, Max(4) (1): 2
Enter Description : DB Group 1 - NORMAL - SHARED - CIS
b.
Enter the necessary information for the DB VMs.
For example, if you entered 2 as the number of VMs on each compute node, these fields
are displayed:
Define Virtual Machines
Node 1 : mc3-n1
Virtual Machine 1
Enter Cores [0 to max 12] (0): 4
Enter Public Hostname (dbgp1-vm1-mc3-n1): mc3-n1
Virtual Machine 2
Enter Cores [0 to max 8] (0): 3
Enter Public Hostname (dbgp1-vm2-mc3-n1): mc3-n1vm1-z2
Node 2 : mc3-n2
Virtual Machine 1
Enter Cores [0 to max 12] (0): 0
Enter Public Hostname (dbgp1-vm1-mc3-n2): mc3-n2vm1-z1
Virtual Machine 2
230
Oracle MiniCluster S7-2 Administration Guide • March 2017
Create a DB VM Group Profile (CLI)
Enter Cores [0 to max 12] (0): 0
Enter Public Hostname (dbgp1-vm2-mc3-n2): mc3-n2vm1-z2
c.
Enter the configuration information for the DB cluster.
Define Cluster
Enter SCAN Name : dbgp1-scan
Select GRID Infrastructure Patch Level [12.1.0.2.160419]
(12.1.0.2.160419): 12.1.0.2.160419
Shared Storage [Yes,No] (No): yes
MCMU creates the DB VM group profile according to the parameters you supplied.
Creating DB VM Group Profile...
INFO dbgp1-scan
INFO:MCMU.controllers.zones.dbzonemanager:dbgp1-scan
INFO {'redundancy': 'NORMAL', 'storageArrays': [], 'numberOfDisks': ''}
INFO:MCMU.controllers.zones.dbzonemanager:{'redundancy': 'NORMAL', 'storageArrays':
[], 'numberOfDisks': ''}
.
<some output omitted>
.
message: Creating DB VM Group succeeded.
Getting DB VM Group Profile...
PROFILE INFORMATION
VMGroupName : dbgp1
SCAN_name : dbgp1-scan
SCAN_ip : 10.129.115.204,10.129.115.205,10.129.115.206
VM DEFINITIONS
VM 1
name : dbgp1-vm1-mc3-n1
globalName : mc3-n1
public_ip : 10.129.115.196
public_hostname : mc3-n1vm1-z1
virtual_ip : 10.129.115.197
virtual_hostname : mc3-n1vm1-z1-vip
VM 2
name : dbgp1-vm2-mc3-n1
globalName : mc3-n1
public_ip : 10.129.115.198
public_hostname : mc3-n1vm1-z2
virtual_ip : 10.129.115.199
virtual_hostname : mc3-n1vm1-z2-vip
Configuring DB VMs (CLI)
231
Deploy the DB VM Group (CLI)
VM 3
name : dbgp1-vm1-mc3-n2
globalName : mc3-n2
public_ip : 10.129.115.200
public_hostname : mc3-n2vm1-z1
virtual_ip : 10.129.115.201
virtual_hostname : mc3-n2vm1-z1-vip
VM 4
name : dbgp1-vm2-mc3-n2
globalName : mc3-n2
public_ip : 10.129.115.202
public_hostname : mc3-n2vm1-z2
virtual_ip : 10.129.115.203
virtual_hostname : mc3-n2vm1-z2-vip
Please insert the IP-mappings in the DNS Server if not already done.
3.
Enter all VM and SCAN public IP addresses and public hostnames into your
DNS.
Ensure that you complete this step before you deploy the DB VM group.
4.
Deploy the DB VM group.
See “Deploy the DB VM Group (CLI)” on page 232.
Deploy the DB VM Group (CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Identify the VMgroupID for the profile.
List the DB VM group profiles, locate the profile that you just created, and make note of the
VMgroupID number. The number is used to deploy the DB VM group.
All existing DB VM group profiles are listed.
% mcmu tenant -P -l
Listing DB VM Group Profile..
Status : Active
EditStatus :
232
Oracle MiniCluster S7-2 Administration Guide • March 2017
Deploy the DB VM Group (CLI)
Description : Initial DB VM Group
- NORMAL redundancy
- Shared Storage
- CIS
deletable : True
progress : False
VMgroupName : dbgp1
editable : True
VMgroupID : 1
3.
Deploy the DB VM group.
Syntax:
mcmu tenant -G -D VMgroupID
where VMgroupID is the ID of the DB VM group profile that you just created.
Caution - Ensure that you use the uppercase D option for the command. Using the lowercase d
option for this command deletes that VM group.
Example:
% mcmu tenant -G -D 1
Setting ssh timeout before carrying out further operations. Please wait..
[INFO
] Log file path : /var/opt/oracle.minicluster/setup/logs/
tenant_cli_082316_040823.log
Aug 23 04:08:23 mccn su: 'su root' succeeded for mcinstall on /dev/pts/2
Deploying DB VM Group...
[23/Aug/2016 04:08:28] INFO [dbzonegroup_install:122] Added zonegroup to action data.
updated message, old: Initializing with Insert IP Mapping
[23/Aug/2016 04:08:28] INFO [dbzonegroup_install:1467] Add zonegroup and operation type
to action.
.
<some output omitted>
.
updated message, old: Finish adding zonegroup information to database. with GI Post
Installation Finished.
[23/Aug/2016 05:23:22] INFO [dbzonegroup_install:93] Method: do performed
[23/Aug/2016 05:23:22] INFO [dbzonegroup_install:132] Add Node to GRID Cluster ends...
updated message, old: GI Post Installation Finished. with Add Node to GRID Cluster
ends...
[23/Aug/2016 05:23:22] INFO [dbzonegroup_install:98] Action Ends at: 2016-08-23 12:23:22
[23/Aug/2016 05:23:22] INFO [dbzonegroup_install:100] Elapsed Time: 1277.46536207 (secs)
[23/Aug/2016 05:23:22] INFO [dbzonegroup_install:102] Performing method: do finished
Status: 0
Message: Deploying DB VM Group Profile succeed
Configuring DB VMs (CLI)
233
Create DB Homes (CLI)
4.
Create DB Homes in the VMs.
See “Create DB Homes (CLI)” on page 234.
Create DB Homes (CLI)
Create at least one DB home in each DB VM. You can create multiple DB homes, each with
specific version of the Oracle Database.
1.
Create DB home installations in each deployed DB VM.
This command enables you to select the version of the Oracle Database that you want installed,
then installs the DB software in the DB home directory that you specify. Homes are created in
each DB VM.
Respond to each prompt:
% mcmu tenant -H -c
[INFO
] Log file path : /var/opt/oracle.minicluster/setup/logs/
tenant_cli_082316_184339.log
Database Home Profile Description
Listing DB VM Group Profile..
Status : Active
EditStatus :
Description : DB MVM Group 1 - NORMAL - SHARED - CIS
deletable : True
progress : False
VMgroupName : dbgp1
editable : True
VMgroupID : 1
Select Database VMgroupID [1] (1): 1
Select Database Version [11.2.0.4/12.1.0.2] (12.1.0.2): 12.1.0.2
INFO Cannot find any database home under given zone. Will return default recommended
name.
INFO:MCMU.controllers.dbzonegroup.update.update:Cannot find any database home under
given zone. Will return default recommended name.
Enter Oracle Home Directory Name (dbhome_1): dbhome_12c
Select Database Home Patch Level [12.1.0.2.160419] (12.1.0.2.160419): 12.1.0.2.160419
List of Inputs for DB Home Creation:
Database VM Group: dbgp1 (ID: 1)
Database Version: 12.1.0.2
234
Oracle MiniCluster S7-2 Administration Guide • March 2017
Create DB Homes (CLI)
Database Patch Level: 12.1.0.2.160419
Oracle Home Path: /u01/app/oracle/product/12.1.0/dbhome_12c
Do you want to change the inputs?
Enter Y/N (N): N
Creating DB Home...
INFO Initializing Database Home Management Utility
.
<some output omitted>
.
INFO Database home on node: dbgp1-vm1-mc3-n1 with home path of /u01/app/oracle/
product/12.1.0/dbhome_12c has been saved to MCMU database.
INFO:MCMU.controllers.dbzonegroup.update.database.database_home:Database home on node:
dbgp1-vm1-mc3-n1 with home path of /u01/app/oracle/product/12.1.0/dbhome_12c has been
saved to MCMU database.
INFO Database home on node: dbgp1-vm2-mc3-n1 with home path of /u01/app/oracle/
product/12.1.0/dbhome_12c has been saved to MCMU database.
INFO:MCMU.controllers.dbzonegroup.update.database.database_home:Database home on node:
dbgp1-vm2-mc3-n1 with home path of /u01/app/oracle/product/12.1.0/dbhome_12c has been
saved to MCMU database.
INFO Database home on node: dbgp1-vm1-mc3-n2 with home path of /u01/app/oracle/
product/12.1.0/dbhome_12c has been saved to MCMU database.
INFO:MCMU.controllers.dbzonegroup.update.database.database_home:Database home on node:
dbgp1-vm1-mc3-n2 with home path of /u01/app/oracle/product/12.1.0/dbhome_12c has been
saved to MCMU database.
INFO Database home on node: dbgp1-vm2-mc3-n2 with home path of /u01/app/oracle/
product/12.1.0/dbhome_12c has been saved to MCMU database.
INFO:MCMU.controllers.dbzonegroup.update.database.database_home:Database home on node:
dbgp1-vm2-mc3-n2 with home path of /u01/app/oracle/product/12.1.0/dbhome_12c has been
saved to MCMU database.
INFO Add database home information to MCMU database successfully.
INFO:MCMU.controllers.dbzonegroup.update.database.database_home:Add database home
information to MCMU database successfully.
updated message, old: Start adding database home information to MCMU database.
with Database home on node: dbgp1-vm2-mc3-n2 with home path of /u01/app/oracle/
product/12.1.0/dbhome_12c has been saved to MCMU database.
updated operation, old: Create DB Home with Create DB Home
status: 0
message: Database home installation succeeded.
2.
(If desired) Repeat Step 1 to install another version of the Oracle Database in the
DB VMs.
For example, f you originally installed Oracle Database 12c in /u01/app/oracle/
product/12.1.0/dbhome_12c, you can then install Oracle Database 11g in another home, such
as /u01/app/oracle/product/12.1.0/dbhome_11g.
3.
List the status of the DB homes.
Configuring DB VMs (CLI)
235
Create DB Instances (CLI)
In this example, two DB homes are active in each VM.
% mcmu tenant -H -l 1
[INFO
] Log file path : /var/opt/oracle.minicluster/setup/logs/
tenant_cli_082316_203949.log
LIST OF DB HOMES IN DB VM GROUP 1
ID:
ID:
ID:
ID:
ID:
ID:
ID:
ID:
4.
1,
5,
2,
6,
3,
7,
4,
8,
VM_ID:
VM_ID:
VM_ID:
VM_ID:
VM_ID:
VM_ID:
VM_ID:
VM_ID:
1,
1,
2,
2,
3,
3,
4,
4,
TYPE:
TYPE:
TYPE:
TYPE:
TYPE:
TYPE:
TYPE:
TYPE:
RAC,
RAC,
RAC,
RAC,
RAC,
RAC,
RAC,
RAC,
STATUS:
STATUS:
STATUS:
STATUS:
STATUS:
STATUS:
STATUS:
STATUS:
Active
Active
Active
Active
Active
Active
Active
Active
Create DB instances.
Go to “Create DB Instances (CLI)” on page 236.
Create DB Instances (CLI)
Create at least one instance in each DB VM. You can create multiple DB instances for each
DB Home. The total number of instances you can create is limited by the amount of disk space
available.
1.
Type.
% mcmu tenant -I -c
2.
When prompted, enter the requested information.
In this example, a RAC instance is selected, so mcmu prompts you to select one VM from each
node.
Database Instance Profile Description
Select Database Instance Type [SINGLE/RAC/RACONE] : rac
Select Database Instance Template: Data Warehouse(DW) / Online Transaction Processing
(OLTP) [DW/OLTP] : dw
List of Character Set
[1] AL32UTF8
[2] AR8ADOS710
[3] AR8ADOS710T
[4] AR8ADOS720
[5] AR8ADOS720T
[6] AR8APTEC715
[7] AR8APTEC715T
[8] AR8ARABICMACS
[9] AR8ASMO708PLUS
[10] AR8ASMO8X
[11] AR8HPARABIC8T
[12] AR8ISO8859P6
[13] AR8MSWIN1256
[14] AR8MUSSAD768
[15] AR8MUSSAD768T
236
Oracle MiniCluster S7-2 Administration Guide • March 2017
Create DB Instances (CLI)
[16] AR8NAFITHA711
[17] AR8NAFITHA711T
[19] AR8NAFITHA721T
[20] AR8SAKHR706
[22] AR8SAKHR707T
[23] AZ8ISO8859P9E
[25] BG8PC437S
[26] BLT8CP921
[28] BLT8MSWIN1257
[29] BLT8PC775
[31] CDN8PC863
[32] CEL8ISO8859P14
[34] CL8ISOIR111
[35] CL8KOI8R
[37] CL8MACCYRILLICS
[38] CL8MSWIN1251
[40] EE8MACCES
[41] EE8MACCROATIANS
[43] EE8PC852
[44] EL8DEC
[46] EL8MACGREEKS
[47] EL8MSWIN1253
[49] EL8PC851
[50] EL8PC869
[52] HU8ABMOD
[53] HU8CWI2
[55] IS8PC861
[56] IW8ISO8859P8
[58] IW8MSWIN1255
[59] IW8PC1507
[61] JA16EUCTILDE
[62] JA16SJIS
[64] JA16VMS
[65] KO16KSC5601
[67] KO16MSWIN949
[68] LA8ISO6937
[70] LT8MSWIN921
[71] LT8PC772
[73] LV8PC1117
[74] LV8PC8LR
[76] N8PC865
[77] NE8ISO8859P10
[79] RU8BESTA
[80] RU8PC855
[82] SE8ISO8859P3
[83] TH8MACTHAIS
[85] TR8DEC
[86] TR8MACTURKISHS
[88] TR8PC857
[89] US8PC437
[91] VN8MSWIN1258
[92] VN8VN3
[94] WE8DG
[95] WE8ISO8859P1
[97] WE8ISO8859P9
[98] WE8MACROMAN8S
[100] WE8MSWIN1252
[101] WE8NCR4970
[103] WE8PC850
[104] WE8PC858
[106] WE8ROMAN8
[107] ZHS16CGB231280
[109] ZHT16BIG5
[110] ZHT16CCDC
[112] ZHT16HKSCS
[113] ZHT16MSWIN950
[115] ZHT32SOPS
[116] ZHT32TRIS
Select Character Set Number (1): 98
List of National Character Set
[1] AL16UTF16
[2] UTF8
Select National Character Set Number (1): 2
Listing DB VM Group Profile..
[18] AR8NAFITHA721
[21] AR8SAKHR707
[24] BG8MSWIN
[27] BLT8ISO8859P13
[30] BN8BSCII
[33] CL8ISO8859P5
[36] CL8KOI8U
[39] EE8ISO8859P2
[42] EE8MSWIN1250
[45] EL8ISO8859P7
[48] EL8PC437S
[51] ET8MSWIN923
[54] IN8ISCII
[57] IW8MACHEBREWS
[60] JA16EUC
[63] JA16SJISTILDE
[66] KO16KSCCS
[69] LA8PASSPORT
[72] LT8PC774
[75] LV8RST104090
[78] NEE8ISO8859P4
[81] RU8PC866
[84] TH8TISASCII
[87] TR8MSWIN1254
[90] UTF8
[93] WE8DEC
[96] WE8ISO8859P15
[99] WE8MACROMAN8S
[102] WE8NEXTSTEP
[105] WE8PC860
[108] ZHS16GBK
[111] ZHT16DBT
[114] ZHT32EUC
[117] US7ASCII
Status : Active
EditStatus :
Description : DB MVM Group 1 - NORMAL - SHARED - CIS
deletable : True
progress : False
VMgroupName : dbgp1
editable : True
VMgroupID : 1
Configuring DB VMs (CLI)
237
Create DB Instances (CLI)
Select Database VMgroupID [1] (1):
List of All Active VMs in VM Group dbgp1
Getting DB VM Group...
status : Active
name : dbgp1-vm1-mc3-n1
globalName : mc3-n1
id : 1
memory : 522496
cores : 4
status : Active
name : dbgp1-vm2-mc3-n1
globalName : mc3-n1
id : 2
memory : 522496
cores : 3
status : Active
name : dbgp1-vm1-mc3-n2
globalName : mc3-n2
id : 3
memory : 522496
cores : 0
status : Active
name : dbgp1-vm2-mc3-n2
globalName : mc3-n2
id : 4
memory : 522496
cores : 0
Select Database VM ID [1/2/3/4] : 1
List of All Active DB home in zone dbgp1-vm1-mc3-n1
Listing DB Home...
status : Active
VM_id : 1
version : 12.1.0.2
home : /u01/app/oracle/product/12.1.0/dbhome_12c
type : RAC
238
Oracle MiniCluster S7-2 Administration Guide • March 2017
Create DB Instances (CLI)
id : 1
status : Active
VM_id : 1
version : 11.2.0.4
home : /u01/app/oracle/product/11.2.0/dbhome_11g
type : RAC
id : 5
Select Database Home ID [1/5] : 1
Select one VM from the other compute node
status : Active
name : dbgp1-vm1-mc3-n2
globalName : mc3-n2
id : 3
memory : 522496
cores : 0
status : Active
name : dbgp1-vm2-mc3-n2
globalName : mc3-n2
id : 4
memory : 522496
cores : 0
Select Secondary Database VM ID [3/4] : 3
Enter Container Database [True/False] (false): false
Enter PGA (Program Global Area) in MB (2560): 5120
Enter SGA (System Global Area) in MB (6400): 12800
Enter Database Instance Name : dw12rac
List of Inputs for DB Instance Creation:
Database Instance Type: RAC
Database Instance Template: DW
VM: dbgp1-vm1-mc3-n1,dbgp1-vm1-mc3-n2 (ID: 1,3)
Database Home: /u01/app/oracle/product/12.1.0/dbhome_12c (ID: 1)
PGA (Program Global Area) in MB: 5120
SGA (System Global Area) in MB: 12800
Database Instance Name: dw12rac
Character Set: WE8MACROMAN8S
National Character Set: UTF8
Configuring DB VMs (CLI)
239
Create DB Instances (CLI)
Container Database : false
Do you want to change the inputs?
Enter Y/N (N): N
Creating DB Instance...
INFO Collecting node information for creating instance.
.
<some output omitted>
.
3.
Repeat this procedure to create one or more DB instances on each DB VM.
4.
Verify the creation and status of instances.
This example lists the details of all DB instances in the specified home ID.
% mcmu tenant -I -l 1
Setting ssh timeout before carrying out further operations. Please wait..
[INFO
] Log file path : /var/opt/oracle.minicluster/setup/logs/
tenant_cli_082416_162942.log
LIST OF DB INSTANCES IN DB VM GROUP 1
ID:
ID:
ID:
ID:
ID:
ID:
ID:
ID:
3, NAME: dw12rac, VM_ID: 1, DBHOME_ID: 1, TYPE: RAC, STATUS: Active
12, NAME: ol11rac1, VM_ID: 1, DBHOME_ID: 5, TYPE: RACONENODE, STATUS: Active
14, NAME: ol12sinC, VM_ID: 2, DBHOME_ID: 2, TYPE: SINGLE, STATUS: Active
7, NAME: dw11rac, VM_ID: 2, DBHOME_ID: 6, TYPE: RAC, STATUS: Active
4, NAME: dw12rac, VM_ID: 3, DBHOME_ID: 3, TYPE: RAC, STATUS: Active
11, NAME: ol11rac1, VM_ID: 3, DBHOME_ID: 7, TYPE: RACONENODE, STATUS: Active
8, NAME: dw11rac, VM_ID: 4, DBHOME_ID: 8, TYPE: RAC, STATUS: Active
16, NAME: dw11sin, VM_ID: 4, DBHOME_ID: 8, TYPE: SINGLE, STATUS: Active
This example lists the details about all the zones.
% mcmu status -Z -a
[INFO
] Log file path : mc3-n1:/var/opt/oracle.minicluster/setup/logs/
mcmu_082416_170213.log
[INFO
] Zone status on node1
ID NAME
STATUS
PATH
BRAND
IP
0 global
running
/
solaris
shared
2 acfskz
running
solaris-kz excl
7 dbgp1-vm1-mc3-n1 running
/mcpool/dbgp1-vm1-mc3-n1zroot solaris
excl
8 dbgp1-vm2-mc3-n1 running
/mcpool/dbgp1-vm2-mc3-n1zroot solaris
excl
11 avm1-vm1-mc3-n1 running
/mcpool/avm1-vm1-mc3-n1zroot solaris
excl
14 avm2-vm1-mc3-n1 running
/mcpool/avm2-vm1-mc3-n1zroot solaris
excl
17 avm4-vm1-mc3-n1 running
/mcpool/avm4-vm1-mc3-n1zroot solaris
excl
20 avm5-vm1-mc3-n1 running
/mcpool/avm5-vm1-mc3-n1zroot solaris
excl
- appzonetemplate installed /mcpool/appzonetemplate
solaris
excl
- dbzonetemplate installed /mcpool/dbzonetemplate
solaris
excl
240
Oracle MiniCluster S7-2 Administration Guide • March 2017
Update a DB VM Group (CLI)
[INFO
] Zone status on node2
ID NAME
STATUS
0 global
running
2 acfskz
running
7 dbgp1-vm1-mc3-n2 running
8 dbgp1-vm2-mc3-n2 running
11 avm1-vm1-mc3-n2 running
14 avm2-vm1-mc3-n2 running
17 avm6-vm1-mc3-n2 running
20 avm7-vm1-mc3-n2 running
- appzonetemplate installed
- dbzonetemplate installed
PATH
BRAND
IP
/
solaris
shared
solaris-kz excl
/mcpool/dbgp1-vm1-mc3-n2zroot solaris
excl
/mcpool/dbgp1-vm2-mc3-n2zroot solaris
excl
/mcpool/avm1-vm1-mc3-n2zroot solaris
excl
/mcpool/avm2-vm1-mc3-n2zroot solaris
excl
/mcpool/avm6-vm1-mc3-n2zroot solaris
excl
/mcpool/avm7-vm1-mc3-n2zroot solaris
excl
/mcpool/appzonetemplate
solaris
excl
/mcpool/dbzonetemplate
solaris
excl
Update a DB VM Group (CLI)
Use this procedure to perform either of these changes to a DB VM group:
■
■
1.
Increase the number of VMs in the group.
Increase or decrease the number of cores in VMs.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Run the profile update command to enter VM updates.
In this example, the number of VMs on node 1 and 2 are increased from two VMs per node
to three VMs per node. The new VMs are VM5 and VM6. The mcmucommand prompts for
VM parameters for the new VMs. Responding with Return accepts the default value, which is
displayed in parentheses.
Note - When this command completes, the updates are saved, but not applied.
% mcmu tenant -P -u
Listing DB VM Group Profile..
Status : Active
EditStatus :
Description : DBVM Group 1 - NORMAL - SHARED - CIS
deletable : True
progress : False
VMgroupName : dbgp1
editable : True
VMgroupID : 1
Configuring DB VMs (CLI)
241
Update a DB VM Group (CLI)
Enter ID of the VM Group Profile that you want to edit[1] (1): 1
Do you want to "[E]dit & Save the changes"?
Enter Y/N (Y): Y
Getting DB VM Group Profile...
Edit Database Virtual Machine Group Profile Description
Virtual Machine Group
Enter Number of VM(s)
Enter Number of VM(s)
Enter Description (DB
Profile Name : dbgp1
on Node 1, between(2,4) (2): 3
on Node 2, between(2,4) (2): 3
MVM Group 1 - NORMAL - SHARED - CIS): <Return>
Virtual Machine Group Profile Name : dbgp1
ASM Disk Group Redundancy : NORMAL
PCI DSS Security Setting Enabled: No
Number of Disks : None
Number of VM(s) on Node 1 : 3
Number of VM(s) on Node 2 : 3
Description : DBVM Group 1 - NORMAL - SHARED - CIS
Virtual Machines Information
Node 1 : mc3-n1
Virtual Machine 1
CURRENT VM STATUS: active
Public Hostname mc3-n1vm1-z1
Public IP: 10.129.115.196
Private Hostname mc3-n1vm1-z1-priv
Private IP: 192.168.10.66
Virtual Hostname mc3-n1vm1-z1-vip
Virtual IP: 10.129.115.197
Enter Cores [0 to max 7] (4): <Return>
242
Oracle MiniCluster S7-2 Administration Guide • March 2017
Update a DB VM Group (CLI)
Virtual Machine 2
CURRENT VM STATUS: active
Public Hostname mc3-n1vm1-z2
Public IP: 10.129.115.198
Private Hostname mc3-n1vm1-z2-priv
Private IP: 192.168.10.67
Virtual Hostname mc3-n1vm1-z2-vip
Virtual IP: 10.129.115.199
Enter Cores [0 to max 3] (3): <Return>
Virtual Machine 3
Enter
Enter
Enter
Enter
Enter
Enter
Enter
Public Hostname (dbgp1-vm3-mc3-n1): mc3-n1vm1-z3
Public IP (To be generated): <Return>
Private Hostname (mc3-n1vm1-z3-priv): <Return>
Private IP (To be generated): <Return>
Virtual Hostname (mc3-n1vm1-z3-vip): <Return>
Virtual IP (To be generated): <Return>
Cores [0 to max 0] (0): <Return>
Node 2: mc3-n2
Virtual Machine 1
CURRENT VM STATUS: active
Public Hostname mc3-n2vm1-z1
Public IP: 10.129.115.200
Private Hostname mc3-n2vm1-z1-priv
Private IP: 192.168.10.68
Virtual Hostname mc3-n2vm1-z1-vip
Virtual IP: 10.129.115.201
Enter Cores [0 to max 12] (0): <Return>
Virtual Machine 2
Configuring DB VMs (CLI)
243
Update a DB VM Group (CLI)
CURRENT VM STATUS: active
Public Hostname mc3-n2vm1-z2
Public IP: 10.129.115.202
Private Hostname mc3-n2vm1-z2-priv
Private IP: 192.168.10.69
Virtual Hostname mc3-n2vm1-z2-vip
Virtual IP: 10.129.115.203
Enter Cores [0 to max 12] (0):
Virtual Machine 3
Enter
Enter
Enter
Enter
Enter
Enter
Enter
Public Hostname (dbgp1-vm3-mc3-n2): mc3-n2vm1-z3
Public IP (To be generated): <Return>
Private Hostname (mc3-n2vm1-z3-priv): <Return>
Private IP (To be generated): <Return>
Virtual Hostname (mc3-n2vm1-z3-vip): <Return>
Virtual IP (To be generated): <Return>
Cores [0 to max 12] (0): <Return>
Cluster Information
SCAN name : dbgp1-scan
SCAN IPs :10.129.115.204,10.129.115.205,10.129.115.206
.
<some output omitted>
.
status: 0
message: Updating DB VM Group Profile succeeded
Getting DB VM Group Profile...
PROFILE INFORMATION
VMGroupName : dbgp1
SCAN_name : dbgp1-scan
SCAN_ip : 10.129.115.204,10.129.115.205,10.129.115.206
VM DEFINITIONS
VM 1
name : dbgp1-vm1-mc3-n1
globalName : mc3-n1
public_ip : 10.129.115.196
public_hostname : mc3-n1vm1-z1
244
Oracle MiniCluster S7-2 Administration Guide • March 2017
Update a DB VM Group (CLI)
virtual_ip : 10.129.115.197
virtual_hostname : mc3-n1vm1-z1-vip
VM 2
name : dbgp1-vm2-mc3-n1
globalName : mc3-n1
public_ip : 10.129.115.198
public_hostname : mc3-n1vm1-z2
virtual_ip : 10.129.115.199
virtual_hostname : mc3-n1vm1-z2-vip
VM 3
name : dbgp1-vm1-mc3-n2
globalName : mc3-n2
public_ip : 10.129.115.200
public_hostname : mc3-n2vm1-z1
virtual_ip : 10.129.115.201
virtual_hostname : mc3-n2vm1-z1-vip
VM 4
name : dbgp1-vm2-mc3-n2
globalName : mc3-n2
public_ip : 10.129.115.202
public_hostname : mc3-n2vm1-z2
virtual_ip : 10.129.115.203
virtual_hostname : mc3-n2vm1-z2-vip
VM 5
name : dbgp1-vm3-mc3-n1
globalName : mc3-n1
public_ip : 10.129.115.215
public_hostname : mc3-n1vm1-z3
virtual_ip : 10.129.115.216
virtual_hostname : mc3-n1vm1-z3-vip
VM 6
name : dbgp1-vm3-mc3-n2
globalName : mc3-n2
public_ip : 10.129.115.217
public_hostname : mc3-n2vm1-z3
virtual_ip : 10.129.115.218
virtual_hostname : mc3-n2vm1-z3-vip
Please insert the IP-mappings in the DNS Server if not already done.
Aug 24 17:17:29 mccn su: 'su root' succeeded for mcinstall on /dev/pts/2
Setting ssh timeout before exiting. Please wait..
mcinstall@mc3-n1:/var/home/mcinstall %
Configuring DB VMs (CLI)
245
Update a DB VM Group (CLI)
mcinstall@mc3-n1:/var/home/mcinstall %
mcinstall@mc3-n1:/var/home/mcinstall %
3.
Enter the new public IP addresses and public hostnames into your DNS.
4.
Run the command again to apply the changes.
When prompted to edit, save, or apply, specify A for apply.
% mcmu tenant -P -u
Setting ssh timeout before carrying out further operations. Please wait..
[INFO
] Log file path : /var/opt/oracle.minicluster/setup/logs/
tenant_cli_082416_171912.log
Listing DB VM Group Profile..
Status : Active
EditStatus : edited
Description : DB MVM Group 1 - NORMAL - SHARED - CIS
deletable : True
progress : False
VMgroupName : dbgp1
editable : True
VMgroupID : 1
Enter ID of the VM Group Profile that you want to edit[1] (1): <Return>
Do you want to "[E]dit & Save" or "[A]pply previously saved changes"?
Enter E/A (E): A
.
<some output omitted>
.
INFO:MCMU.controllers.dbzonegroupmanager:Zonegroup is updated with profile changes.
status: 0
message: Updating DB VM Group succeeded.
Getting DB VM Group Profile...
.
<some output omitted>
.
5.
Verify the changes.
In this example, VMs with ID 23 (one on each node) are new DB VMs displayed with a status
of running.
% mcmu status -Z -a
[INFO
] Log file path : mc3-n1:/var/opt/oracle.minicluster/setup/logs/
mcmu_082416_180834.log
[INFO
] Zone status on node1
246
Oracle MiniCluster S7-2 Administration Guide • March 2017
Update a DB VM Group (CLI)
ID NAME
STATUS
0 global
running
2 acfskz
running
7 dbgp1-vm1-mc3-n1 running
8 dbgp1-vm2-mc3-n1 running
11 avm1-vm1-mc3-n1 running
14 avm2-vm1-mc3-n1 running
17 avm4-vm1-mc3-n1 running
20 avm5-vm1-mc3-n1 running
23 dbgp1-vm3-mc3-n1 running
- appzonetemplate installed
- dbzonetemplate installed
[INFO
] Zone status on node2
ID NAME
STATUS
0 global
running
2 acfskz
running
7 dbgp1-vm1-mc3-n2 running
8 dbgp1-vm2-mc3-n2 running
11 avm1-vm1-mc3-n2 running
14 avm2-vm1-mc3-n2 running
17 avm6-vm1-mc3-n2 running
20 avm7-vm1-mc3-n2 running
23 dbgp1-vm3-mc3-n2 running
- appzonetemplate installed
- dbzonetemplate installed
6.
PATH
BRAND
IP
/
solaris
shared
solaris-kz excl
/mcpool/dbgp1-vm1-mc3-n1zroot solaris
excl
/mcpool/dbgp1-vm2-mc3-n1zroot solaris
excl
/mcpool/avm1-vm1-mc3-n1zroot solaris
excl
/mcpool/avm2-vm1-mc3-n1zroot solaris
excl
/mcpool/avm4-vm1-mc3-n1zroot solaris
excl
/mcpool/avm5-vm1-mc3-n1zroot solaris
excl
/mcpool/dbgp1-vm3-mc3-n1zroot solaris
excl
/mcpool/appzonetemplate
solaris
excl
/mcpool/dbzonetemplate
solaris
excl
PATH
BRAND
IP
/
solaris
shared
solaris-kz excl
/mcpool/dbgp1-vm1-mc3-n2zroot solaris
excl
/mcpool/dbgp1-vm2-mc3-n2zroot solaris
excl
/mcpool/avm1-vm1-mc3-n2zroot solaris
excl
/mcpool/avm2-vm1-mc3-n2zroot solaris
excl
/mcpool/avm6-vm1-mc3-n2zroot solaris
excl
/mcpool/avm7-vm1-mc3-n2zroot solaris
excl
/mcpool/dbgp1-vm3-mc3-n2zroot solaris
excl
/mcpool/appzonetemplate
solaris
excl
/mcpool/dbzonetemplate
solaris
excl
Create DB instances on the new DB VMs:
If you didn't add DB VMs, this step doesn't apply.
a.
List the current instances.
Note, the new VMs do not show up in the list. After the new instances are created, you can
compare this list with a new list. See Step 7.
% mcmu tenant -I -l 1
Aug 24 18:10:01 mccn su: 'su root' succeeded for mcinstall on /dev/pts/2
LIST OF DB INSTANCES IN DB VM GROUP 1
ID: 3, NAME: dw12rac, VM_ID: 1, DBHOME_ID: 1, TYPE: RAC, STATUS: Active
ID: 12, NAME: ol11rac1, VM_ID: 1, DBHOME_ID: 5, TYPE: RACONENODE, STATUS:
Active
ID:
ID:
ID:
ID:
14, NAME: ol12sinC, VM_ID: 2, DBHOME_ID: 2, TYPE: SINGLE, STATUS: Active
7, NAME: dw11rac, VM_ID: 2, DBHOME_ID: 6, TYPE: RAC, STATUS: Active
4, NAME: dw12rac, VM_ID: 3, DBHOME_ID: 3, TYPE: RAC, STATUS: Active
11, NAME: ol11rac1, VM_ID: 3, DBHOME_ID: 7, TYPE: RACONENODE, STATUS:
Active
Configuring DB VMs (CLI)
247
Update a DB VM Group (CLI)
ID: 8, NAME: dw11rac, VM_ID: 4, DBHOME_ID: 8, TYPE: RAC, STATUS: Active
ID: 16, NAME: dw11sin, VM_ID: 4, DBHOME_ID: 8, TYPE: SINGLE, STATUS: Active
b.
Create the instances.
You are prompted to provide instance parameters.
% mcmu tenant -I -c
Database Instance Profile Description
Select Database Instance Type [SINGLE/RAC/RACONE] : rac
Select Database Instance Template: Data Warehouse(DW) / Online Transaction
Processing(OLTP) [DW/OLTP] : oltp
List of Character Set
[1] AL32UTF8
[2] AR8ADOS710
[3] AR8ADOS710T
.
<some output omitted>
.
[112] ZHT16HKSCS
[113] ZHT16MSWIN950
[114] ZHT32EUC
[115] ZHT32SOPS
[116] ZHT32TRIS
[117] US7ASCII
Select Character Set Number (1): 115
List of National Character Set
[1] AL16UTF16
[2] UTF8
Select National Character Set Number (1): <Return>
Listing DB VM Group Profile..
Status : Active
EditStatus :
Description : DB MVM Group 1 - NORMAL - SHARED - CIS
deletable : True
progress : False
VMgroupName : dbgp1
editable : True
VMgroupID : 1
Select Database VMgroupID [1] (1):
List of All Active VMs in VM Group dbgp1
Getting DB VM Group...
status : Active
name : dbgp1-vm1-mc3-n1
globalName : mc3-n1
id : 1
memory : 522496
cores : 4
status : Active
248
Oracle MiniCluster S7-2 Administration Guide • March 2017
Update a DB VM Group (CLI)
name : dbgp1-vm2-mc3-n1
globalName : mc3-n1
id : 2
memory : 522496
cores : 3
status : Active
name : dbgp1-vm1-mc3-n2
globalName : mc3-n2
id : 3
memory : 522496
cores : 0
status : Active
name : dbgp1-vm2-mc3-n2
globalName : mc3-n2
id : 4
memory : 522496
cores : 0
status : Active
name : dbgp1-vm3-mc3-n1
globalName : mc3-n1
id : 13
memory : 522496
cores : 0
status : Active
name : dbgp1-vm3-mc3-n2
globalName : mc3-n2
id : 14
memory : 522496
cores : 0
<<=== NEW VM
<<=== NEW VM
Select Database VM ID [1/2/3/4/13/14] : 13
List of All Active DB home in zone dbgp1-vm3-mc3-n1
Listing DB Home...
<<=== ID of New VM
status : Active
VM_id : 13
version : 12.1.0.2
home : /u01/app/oracle/product/12.1.0/dbhome_12c
Configuring DB VMs (CLI)
249
Update a DB VM Group (CLI)
type : RAC
id : 9
status : Active
VM_id : 13
version : 11.2.0.4
home : /u01/app/oracle/product/11.2.0/dbhome_11g
type : RAC
id : 11
Select Database Home ID [9/11] : 9
Select one VM from the other compute node
status : Active
name : dbgp1-vm1-mc3-n2
globalName : mc3-n2
id : 3
memory : 522496
cores : 0
status : Active
name : dbgp1-vm2-mc3-n2
globalName : mc3-n2
id : 4
memory : 522496
cores : 0
status : Active
name : dbgp1-vm3-mc3-n2
globalName : mc3-n2
id : 14
memory : 522496
cores : 0
Select Secondary Database VM ID [3/4/14] : 14
second node
Enter Container Database [True/False] (false):
Enter PGA (Program Global Area) in MB (2560): 5120
Enter SGA (System Global Area) in MB (6400): 12800
Enter Database Instance Name : ol12rac
List of Inputs for DB Instance Creation:
250
Oracle MiniCluster S7-2 Administration Guide • March 2017
<<=== ID of new VM on
Deleting DB VM Group Components (CLI)
Database Instance Type: RAC
Database Instance Template: OLTP
VM: dbgp1-vm3-mc3-n1,dbgp1-vm3-mc3-n2 (ID: 13,14)
Database Home: /u01/app/oracle/product/12.1.0/dbhome_12c (ID: 9)
PGA (Program Global Area) in MB: 5120
SGA (System Global Area) in MB: 12800
Database Instance Name: ol12rac
Character Set: US7ASCII
National Character Set: AL16UTF16
Container Database : false
Do you want to change the inputs?
Enter Y/N (N): N
Creating DB Instance...
.
<some output omitted>
.
7.
List the DB instances to verify the presence and status of the new DB VM
instances.
% mcmu tenant -I -l 1
Aug 24 18:43:12 mccn su: 'su root' succeeded for mcinstall on /dev/pts/2
LIST OF DB INSTANCES IN DB VM GROUP 1
ID:
ID:
ID:
ID:
ID:
ID:
ID:
ID:
ID:
ID:
3, NAME: dw12rac, VM_ID: 1, DBHOME_ID: 1, TYPE: RAC, STATUS: Active
12, NAME: ol11rac1, VM_ID: 1, DBHOME_ID: 5, TYPE: RACONENODE, STATUS: Active
14, NAME: ol12sinC, VM_ID: 2, DBHOME_ID: 2, TYPE: SINGLE, STATUS: Active
7, NAME: dw11rac, VM_ID: 2, DBHOME_ID: 6, TYPE: RAC, STATUS: Active
4, NAME: dw12rac, VM_ID: 3, DBHOME_ID: 3, TYPE: RAC, STATUS: Active
11, NAME: ol11rac1, VM_ID: 3, DBHOME_ID: 7, TYPE: RACONENODE, STATUS: Active
8, NAME: dw11rac, VM_ID: 4, DBHOME_ID: 8, TYPE: RAC, STATUS: Active
16, NAME: dw11sin, VM_ID: 4, DBHOME_ID: 8, TYPE: SINGLE, STATUS: Active
19, NAME: ol12rac, VM_ID: 13, DBHOME_ID: 9, TYPE: RAC, STATUS: Active
20, NAME: ol12rac, VM_ID: 14, DBHOME_ID: 10, TYPE: RAC, STATUS: Active
Deleting DB VM Group Components (CLI)
These topics describe how to delete database VM group Components:
■
■
■
“Delete a DB VM Group Profile (CLI)” on page 252
“Delete a DB VM Group (CLI)” on page 253
“Delete a DB Home (CLI)” on page 253
Configuring DB VMs (CLI)
251
Delete a DB VM Group Profile (CLI)
■
“Delete a DB Instance (CLI)” on page 254
Delete a DB VM Group Profile (CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Use this syntax:
% mcmu tenant -P -d VMgroupID
where VMgroupID is the ID of the DB VM group profile that you want to delete.
For example, to delete a DB VM group profile with an ID of 1, type:
% mcmu tenant -P -d 1
Setting ssh timeout before carrying out further operations. Please wait..
[INFO
] Log file path : /var/opt/oracle.minicluster/setup/logs/
tenant_cli_082316_034336.log
Status : Needs Mapping
VMgroupName : dbgp1
Description : DB VM Group 1 - Normal - CIS - SHARED
VMgroupID : 1
Are you sure you want to delete this DB VM Group Profile?
Enter Y/N (Y): y
Deleting DB VM Group Profile...
INFO Start freeing ipaddress and core table
INFO:MCMU.controllers.zones.dbzonemanager:Start freeing ipaddress and core table
INFO Removing GI data.
INFO:MCMU.controllers.zones.dbzonemanager:Removing GI data.
INFO Free Disk & Partitions.
INFO:MCMU.controllers.zones.dbzonemanager:Free Disk & Partitions.
INFO Deleting zone data.
INFO:MCMU.controllers.zones.dbzonemanager:Deleting zone data.
INFO Deleting zonegroup data.
INFO:MCMU.controllers.zones.dbzonemanager:Deleting zonegroup data.
INFO Complete zonegroup profile deletion.
INFO:MCMU.controllers.zones.dbzonemanager:Complete zonegroup profile deletion.
updated message, old: Initializing with Profile deletion succeeded.
Successfully deleted DB VM profile
3.
252
Verify the deletion.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Delete a DB VM Group (CLI)
For example:
% mcmu tenant -P -l
Setting ssh timeout before carrying out further operations. Please wait..
[INFO
] Log file path : /var/opt/oracle.minicluster/setup/logs/
tenant_cli_082316_034511.log
Listing DB VM Group Profile..
No VM Group Profiles available yet
Delete a DB VM Group (CLI)
Caution - Deleting a DB VM group deletes all the VMs, applications, and data associated with
the VM group. The deletion cannot be undone. Proceed with caution.
Type:
% mcmu tenant --dbvmgroup -d VMgroupID
where VMgroupID is the ID of the DB VM group that you want to delete.
For example, to delete a DB VM group with an ID of 1, type:
% mcmu tenant --dbvmgroup -d 1
Delete a DB Home (CLI)
Caution - Deleting a DB home cannot be undone. Proceed with caution.
Type:
% mcmu tenant --dbhome -d home_ID
where home_ID is the ID of the DB home that you want to delete.
For example, to delete a DB home within a DB VM with an ID of 3, type:
% mcmu tenant --dbhome -d 3
Configuring DB VMs (CLI)
253
Delete a DB Instance (CLI)
Delete a DB Instance (CLI)
Caution - Deleting a DB instance cannot be undone. Proceed with caution.
Type:
% mcmu tenant --dbinstance -d home_ID
where home_ID is the ID of the DB home that is associated with the DB instance that you want
to delete.
For example, to delete a DB instance that is associated with a DB home with an ID of 3, type:
% mcmu tenant --dbinstance -d 3
254
Oracle MiniCluster S7-2 Administration Guide • March 2017
Configuring Application VMs (CLI)
For information about planning for VMs, see “Planning to Create VMs” on page 61.
These topics provide CLI procedures for configuring App VM groups and VMs:
Description
Links
(If needed) Add IP addresses to the system for
future VMs.
“Add IP Addresses for Future VMs (CLI)” on page 227
Create App VMs.
“Create an APP VM Group (CLI)” on page 255
“Deploy an App VM Group (CLI)” on page 257
Update an App VM group.
“Update an App VM Group (CLI)” on page 258
Toggle the shared storage that is used by App
VMs.
“Toggle Shared Storage for an App Group (CLI)” on page 260
Delete App VMs.
“Delete an App VM Group (CLI)” on page 260
Create an APP VM Group (CLI)
Use this procedure to create and deploy App VMs.
The process of creating App VMs involves creating an App VM group. Each group can contain
one or two App VMs. Once the groups are created, you deploy the groups, which makes the
App VMs available for use.
For details about the information you provide when creating App VMs, see “App VM Group
Parameters” on page 78.
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Create the App VM group:
% mcmu tenant -A -c
Configuring Application VMs (CLI)
255
Create an APP VM Group (CLI)
For example:
% mcmu tenant -A -c
Application Virtual Machine Group Profile Description
Enter Virtual Machine Group Profile Name : avm1
Enter Description : Drama App VM Group
Enter Type [Single,Multiple] (Multiple): multiple
Shared Storage [Yes,No] (No): yes
CIS Equivalent Security Settings are default.Do you want to enable PCI DSS Security
Settings [Yes,No] (No)? yes
Define Virtual Machines
mc3-n1
Virtual Machine 1
Enter Cores [0 to max 5] (0): 2
Enter Public Hostname (avm1-vm1-mc3-n1): mc3-n1vm2-az1
mc3-n2
Virtual Machine 1
Enter Cores [0 to max 12] (0): <Return>
Enter Public Hostname (avm1-vm1-mc3-n2): mc3-n2vm2-az1
Creating APPVM Group Profile...
.
<output omitted>
.
Successfully Created Application VM Group Profile
Getting APP VM Group...
PROFILE INFORMATION
VMGroupName : avm1
VM DEFINITIONS
VM 1
name : avm1-vm1-mc3-n1
globalName : mc3-n1
public_ip : 10.129.115.207
public_hostname : mc3-n1vm2-az1
VM 2
name : avm1-vm1-mc3-n2
256
Oracle MiniCluster S7-2 Administration Guide • March 2017
Deploy an App VM Group (CLI)
globalName : mc3-n2
public_ip : 10.129.115.208
public_hostname : mc3-n2vm2-az1
Please insert the IP-mappings in the DNS Server if not already done.
Aug 23 16:32:12 mccn su: 'su root' succeeded for mcinstall on /dev/pts/2
3.
Make note of the App VM names and public IP addresses.
4.
(If desired) Repeat Step 2 to create additional App VMs.
5.
Enter all new app VM names and public IP addresses into your DNS.
6.
Deploy the App VM group.
See “Deploy an App VM Group (CLI)” on page 257.
Deploy an App VM Group (CLI)
Use this procedure to an deploy App VM group. Once deployed, the VMs are available for
configuration and use.
1.
Deploy the app VM group.
Caution - Ensure that you use the uppercase D option. Using the lowercase d option deletes that
VM group.
Use this syntax:
mcmu tenant -V -D VMgroupID
where VMgroupID is the App VM group profile ID that was assigned by mcmu when the group
was created. To determine the VMgroupID, see “List a Summary of All App VM Group Profiles
(CLI)” on page 197.
For example:
% mcmu tenant -V -D 2
Setting ssh timeout before carrying out further operations. Please wait..
[INFO
] Log file path : /var/opt/oracle.minicluster/setup/logs/
tenant_cli_082316_164849.log
Creating APP VM Group...
.
Configuring Application VMs (CLI)
257
Update an App VM Group (CLI)
<some output omitted>
.
INFO Finish adding zonegroup information to database.
INFO:MCMU.controllers.zones.appzonemanager:Finish adding zonegroup information to
database.
updated message, old: Start adding data to MCMU database. with Application zonegroup
creation completed.
Status: 0
Message: Deployment of APP VM Group succeeded.
2.
If you have additional App VM groups to deploy, repeat Step 1.
Update an App VM Group (CLI)
You can change parameters such as the number of cores assigned to each VM. You can also
mount an NFS. For undeployed VM groups, you can change IP addresses and hostnames.
For details about the information you provide when creating App VMs, see “App VM Group
Parameters” on page 78.
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Type:
% mcmu tenant -A -u
For example:
% mcmu tenant -A -u
Listing APP VM Group...
Status : Active
EditStatus :
Description :
deletable : True
progress : False
VMgroupName : ff18
editable : True
VMgroupID : 2
Enter ID of the VM Group Profile that you want to edit[2] (2): 2
Do you want to "[E]dit & Save the changes"?
Enter Y/N (Y): Y
Getting APP VM Group...
258
Oracle MiniCluster S7-2 Administration Guide • March 2017
Update an App VM Group (CLI)
APP Virtual Machine Group Profile Name : appg500
Enter Description :
Security Profile: DISA-STIG
Add External NFS
Existing External NFS
ID: 1
Mount: /test-mountpoint
xx.xxx.73.130
Share: /my_directory
Server IP:
Do you want to "[A]dd or [D]elete MountPoints or [Q]uit and Save from here"?
Enter A/D/Q (A): Q
Virtual Machines Information
Node 1 : mc5qt-n1
Enter Cores [0 to max 28] (0):2
public_hostname : ff18-vm1-mc5qt-n1
private_hostname : ff18-vm1-mc5qt-n1-priv
public_ip : 10.129.104.61
private_ip : 192.168.10.62
Node 2 : mc5qt-n2
Enter Cores [0 to max 28] (0):2
public_hostname : ff18-vm1-mc5qt-n2
private_hostname : ff18-vm1-mc5qt-n2-priv
public_ip : 10.129.104.62
private_ip : 192.168.10.63
Updating APP VM Group Profile...
start to update profile
status: 0
message: Update APP VM Group Profile succeeded.
Getting APP VM Group...
PROFILE INFORMATION
VMGroupName : ff18
VM DEFINITIONS
VM 1
name : ff18-vm1-mc5qt-n1
globalName : mc5qt-n1
Configuring Application VMs (CLI)
259
Toggle Shared Storage for an App Group (CLI)
public_ip : 10.129.104.61
public_hostname : ff18-vm1-mc5qt-n1
VM 2
name : ff18-vm1-mc5qt-n2
globalName : mc5qt-n2
public_ip : 10.129.104.62
public_hostname : ff18-vm1-mc5qt-n2
Please insert the IP-mappings in the DNS Server if not already done.
Toggle Shared Storage for an App Group (CLI)
Use this procedure to enable or disable shared storage for the App group. To see the current
state of shared storage, use the MCMU BUI, and see “Enable or Disable Shared Storage
(BUI)” on page 135.
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Use this syntax:
% mcmu tenant -V -t VMgroupID
where VMgroupID is the ID of the App VM group that you want to delete. To determine the
VMgroupID, see “List a Summary of All App VM Group Profiles (CLI)” on page 197.
Delete an App VM Group (CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
To delete an App VM group, type:
% mcmu tenant -A -d VMgroupID
where VMgroupID is the ID of the App VM group that you want to delete. To determine the
VMgroupID, see “List a Summary of All App VM Group Profiles (CLI)” on page 197.
For example, to delete an App VM group with an ID of 2, type:
% mcmu tenant -A -d 2
260
Oracle MiniCluster S7-2 Administration Guide • March 2017
Managing MCMU User Accounts (CLI)
You can use the MCMU CLI to manage MCMU user accounts: If you use the CLI to create a
user account, the subsequent user approvals must be performed using the CLI.
Note - To manage user accounts using the MCMU BUI, see “Managing MCMU User Accounts
(BUI)” on page 37. MCMU user concepts are covered in this BUI section.
■
■
■
■
■
■
■
“Create a New MCMU User (CLI)” on page 261
“Approve a New MCMU User (CLI)” on page 262
“Reject a New MCMU User (CLI)” on page 263
“List MCMU User Approval and Rejection Status (CLI)” on page 264
“Delete an MCMU User (CLI)” on page 265
“Change an MCMU User Password (CLI)” on page 266
“Edit a User Profile (CLI)” on page 266
Create a New MCMU User (CLI)
If you use the CLI to create a user account, the subsequent user approvals must be performed
using the CLI.
Note - For additional information about MCMU user concepts, see “Managing MCMU User
Accounts (BUI)” on page 37.
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Create a new user with this syntax:
% mcmu user -c -u username -e email -n fullname -p phonenumber -r role
Managing MCMU User Accounts (CLI)
261
Approve a New MCMU User (CLI)
where:
■
■
■
■
■
username is a unique name for the new user. The name cannot be root or mcadmin. It must
start with an alpha character. The name can contain alpha and numeric characters, and can
include , '.', '-' or '_' characters.
email is the email address for the new user.
fullname is the first and last name for the new user.
phonenumber is the new user's phone number (digits only. No special characters).
role is one of these values:
■
■
■
■
primary
secondary
tenant_admin
auditor
For role descriptions, see “User Roles” on page 37.
For example:
% mcmu user -c -u jsmith -e joe.smith@acme.com -n Joe Smith -p 8881112222 -r primary
[INFO
] Log file path : mc3-n1:/var/opt/oracle.minicluster/setup/logs/
mcmu_082216_193715.log
[INFO
] User jsmith has been created, please ask the admin and supervisor to run the
command in New User Approval Request email to approve
An email is sent to the primary admin and supervisor accounts. The email contains a secure key
that is required to approve the new user.
Note - The user account is created, but not activated until the primary admin and the supervisor
approves the new user.
3.
Consider your next action.
■
■
■
Approve the new user, see “Approve a New MCMU User (CLI)” on page 262.
Reject the new user, see “Reject a New MCMU User (CLI)” on page 263.
Check the approval and rejection status of new users, see “List MCMU User Approval and
Rejection Status (CLI)” on page 264.
Approve a New MCMU User (CLI)
When a user is created using the CLI, the MCMU admin and supervisor are sent an email that
includes a command line with a secure approval key. In most cases, the approver can log into
262
Oracle MiniCluster S7-2 Administration Guide • March 2017
Reject a New MCMU User (CLI)
the mcmu CLI and paste the command line into mcmu to immediately approve the user. If that
doesn't work, perform this task.
Both the primary admin and the supervisor must approve the new user before the user account
is activated.
To see the status of approvals and rejections, see “List MCMU User Approval and Rejection
Status (CLI)” on page 264.
1.
From the primary admin’s or supervisor's email account, obtain the secure key.
Open the email and copy the secure key. The email is sent from mcinstall@company-name.
2.
Log into the MCMU CLI.
See “Log in to the MCMU CLI” on page 29.
3.
Type:
% mcmu user --approve -r role -u username -k key
where:
■
role is the role of the person approving the user. Specify one of these values:
■
admin
■
■
■
supervisor
username is the name of the new user who is seeking approval.
key Paste the secure key string that was sent to the admin and supervisor as part of the
preliminary approval process.
This is an example of the admin approving the new user jsmith.
% mcmu user --approve -r admin -u jsmith -k q4pruavlauerp-8ujf;queroja
The jsmith user account still requires the approval of the supervisor before the account is
activated.
Reject a New MCMU User (CLI)
When a user is created using the CLI, the MCMU admin and supervisor are sent an email
requesting approval of the user. The admin and supervisor must both approve the new user for
the account to be activated. If the admin or supervisor fail to approve, or reject the new user, the
account is not activated. Once a new account is rejected, it cannot be approved.
Managing MCMU User Accounts (CLI)
263
List MCMU User Approval and Rejection Status (CLI)
To see the status of approvals and rejections, see “List MCMU User Approval and Rejection
Status (CLI)” on page 264.
1.
From the primary admin's or supervisor's email account, obtain the secure key.
When a new user account is created, MCMU emails the primary admin and supervisor an email
that contains a secure key which is needed to approve or reject the user. The email is sent from
mcinstall@company-name.
Open the email and copy the secure key.
2.
Log into the MCMU CLI.
See “Log in to the MCMU CLI” on page 29.
3.
Type:
% mcmu user --reject -r role -u username -k key
where:
■
role is the role of the person rejecting the new user. Specify one of these values:
admin
secondary
username is the name for the new user that you are rejecting.
key is the secure key string that was emailed to the admin and supervisor. Paste the string
into the command line
■
■
■
■
In this example, the supervisor rejects the user bbaker.
% mcmu user --reject -r supervisor -u bbaker -k q4pruavlauerp-8ujf;queroja
List MCMU User Approval and Rejection Status (CLI)
Use this task to view the status of approvals and rejections of users.
Note - Do not use this procedure to view all users because as soon as a user is approved by the
admin and supervisor, the user is removed from the list. To see a list of approved users, use the
MCMU BUI. See “Display MCMU Users (BUI)” on page 40.
264
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
List users that have pending approvals.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Delete an MCMU User (CLI)
This example shows three user accounts that are waiting for approvals or rejections from the
admin and supervisor.
% mcmu user -l
[INFO
] Log file path : mc3-n1:/var/opt/oracle.minicluster/setup/logs/
mcmu_082216_194010.log
username
--------jsmith
bbaker
tenadm
admin_approved
-------------0
0
0
super_approved
-------------0
0
0
admin_rejected
-------------0
0
0
super_rejected
-------------0
0
0
In this example, the user jsmith is no longer in the list because the jsmith user has been
approved by the admin and supervisor. The user bbaker is approved by the supervisor, but is
waiting for approval from the admin. tenadm has been rejected by the admin and supervisor.
% mcmu user -l
[INFO
] Log file path : mc3-n1:/var/opt/oracle.minicluster/setup/logs/
mcmu_082316_011656.log
username
---------bbaker
tenadm
admin_approved
-------------0
0
super_approved
-------------1
0
admin_rejected
-------------0
1
super_rejected
-------------0
1
Delete an MCMU User (CLI)
Use this procedure to delete a user account. The primary admin and supervisor must approve
the deletion though email sent from MCMU.
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Type:
% mcmu user --delete -u username
where username is the user name of the user that you are deleting from the system.
For example:
% mcmu user --delete -u jsmith
Once the deletion request is approved by the primary admin and supervisor, the account is
deleted.
Managing MCMU User Accounts (CLI)
265
Change an MCMU User Password (CLI)
Change an MCMU User Password (CLI)
Use this procedure to change an MCMU user's password. The new password is governed by the
password policies. See “MCMU Password Policies” on page 39.
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Type:
% mcmu user --changepswd -u username
where username is the user name for the user whose password you want to change.
For example:
% mcmu user --changepswd -u jsmith
[INFO
] Log file path : mc3-n1:/var/opt/oracle.minicluster/setup/logs/
mcmu_082516_164544.log
Enter new password for user jsmith:
Re-enter new password for jsmith:
[INFO
] Password has been changed
Edit a User Profile (CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Type:
% mcmu user -E -u username
where username is the user name for the profile you want to change.
The utility prompts you for changes. For parameters you do not want to change, press Return.
For example:
% mcmu user -E -u user500
User Information Summary
Username:
user500
Email address: ray.ray@company.com
Full Name:
Raymond Ray
Phone Number: 123456789
266
Oracle MiniCluster S7-2 Administration Guide • March 2017
Edit a User Profile (CLI)
Title:
Organization:
Department:
Address:
Type of User: Primary Admin
Supervisor Username:
mc-super
Supervisor FullName:
Mr Smith
Supervisor email:
mr.smith@company.com
Do you want to edit the user information? [yes/no] (no): yes
Please press ENTER to keep current value, or provide new value if you want to update
Enter email address [ray.ray@company.com]:
Enter full name [Raymond Ray]:
Enter phone number [123456789]: 408777888
Enter title []:
Enter organization []:
Enter department []:
Enter address []:
Enter supervisor username [mc-super]:
Enter supervisor full name [Mr Smith]:
Enter supervisor email address [mr.smith@company.com]:
[INFO
] User profile has been successfully updated
Managing MCMU User Accounts (CLI)
267
268
Oracle MiniCluster S7-2 Administration Guide • March 2017
Managing Networks (CLI)
This section provides this topic:
■
“Configure Additional Networks” on page 269
Configure Additional Networks
Use one of these network interfaces to connect to the client access network:
■
■
Through the 10GbE NIC, using the first two ends of the four-ended splitter cable, or
Through the NET 2 and NET 3 ports
You can now configure additional networks on unused network interface slots for existing VMs,
either in the same subnet or on a different subnet.
1.
Determine what network interface slots are unused and are therefore available
for you to configure as an additional network.
The network interface slots that are available for you to configure as an additional network
depends on how your MiniCluster is connected to the client access network:
■
If your MiniCluster is connected through the 10GbE NIC, using either a QSFP to 4x
SFP+ or MPO to 4x LC duplex splitter cable — You have the first two ends of the splitter
cable (labeled A and B, or 1 and 2) connected to the client access network through 10GbE
switches. The following network interface slots are therefore available on both compute
nodes for you to configure as additional networks:
The other two ends of the splitter cable (labeled C and D, or 3 and 4) connected to the
10GbE NIC
■ The NET 2 and NET 3 ports
If your MiniCluster is connected through the NET 2 and NET 3 ports — You are using
those two ports on both compute nodes to connect to the client access network through
10GbE switches. The P 0 port (rightmost port, or port A) on the 10GbE NIC is therefore
available for you to configure as additional networks. You can connect a QSFP to 4x SFP+
or an MPO to 4x LC duplex splitter cable to the P 0 port on the 10GbE NIC, which enables
■
■
Managing Networks (CLI)
269
Configure Additional Networks
you to connect the four ends of the splitter cable (labeled A through D, or 1 through 4) to
the additional network.
Refer to the Oracle MiniCluster S7-2 Installation Guide for more information on the connection
options for the client access network.
2.
Make the physical connections to the additional network, depending on which
network interface slots are available to configure as an additional network.
Make one of the following pairs of connections to the additional network to provide high
availability:
■
From the 10GbE NIC:
The first two ends of the splitter cable (A and B, or 1 and 2), if not already used to
connect to the client network
■ The second two ends of the splitter cable (C and D, or 3 and 4)
From the NET 2 and NET 3 ports, if not already used to connect to the client network
■
■
3.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
4.
Determine the VMgroupID of the VM group for the new network.
Perform one of these commands:
■
For DB VM groups, type:
In this example, the VMgroupID is 1.
% mcmu tenant -G -l
Listing DB VM Group...
Status : Active
Description :
VMgroupName : dbzg2
editable : True
deletable : True
progress : False
VMgroupID : 1
■
For App VM groups, type:
In this example, the VMgroupID is 2.
% mcmu tenant -A -l
270
Oracle MiniCluster S7-2 Administration Guide • March 2017
Configure Additional Networks
Listing APP VM Group...
Status : Active
EditStatus :
Description : Drama App VM Group
- shared
- multiple
- CIS
deletable : True
progress : False
VMgroupName : avm1
editable : True
VMgroupID : 2
5.
Enter this CLI command to begin the configuration process for the additional
network.
% mcmu network -a tenant
6.
Select the VM group where you want to configure an additional network.
Specify the VMgroupID number.
Select ID [1] (1): 1
The VMs available in that VM group are listed:
ID | NAME
| GLOBALZONE | HOSTNAME
---+---------------------+------------+----------------------1 | mc1dbzg1-vm1-mc1-n1 | mc1-n1
| mc1dbzg1-zone-1-mc1-n1
2 | mc1dbzg1-vm1-mc1-n2 | mc1-n2
| mc1dbzg1-zone-1-mc1-n2
7.
Select the VMs where you want to configure an additional network.
Enter comma separated list of VM ID(s) ID [1,2] : 1,2
The available (unused) network interface pairs are listed:
Select any of the interface pairs to configure a network
ID: 1
Interfaces: net4,net5
ID: 2
Interfaces: net6,net7
8.
Select the network interface pairs that you want to use for the additional
network.
Managing Networks (CLI)
271
Configure Additional Networks
Select ID [1/2] (1):
These are the network interface pairs that you can choose from:
■
■
9.
From the NET 2 and NET 3 ports — net2,net3
From the 10GbE NIC:
■
The first two ends of the splitter cable (A and B, or 1 and 2) — net4,net5
■
The second two ends of the splitter cable (C and D, or 3 and 4) — net6,net7
Enter the remaining necessary information for the additional network.
Enter IP addresses for virtual_machine:
Enter Netmask in CIDR form (valid range: 8-28):
Do you want to input Gateway(Router) address?
Enter Y/N (N):
Enter Default Gateway Address:
Do you want to input DNS Servers and Domain name values?
Enter Y/N (N):
VLAN ID is optional. Do you want to input this value?
Enter Y/N (N):
Enter CAN HA type (IPMP/AGGR):
A series of messages appear after you enter all the remaining necessary information for the
additional network, providing information on the additional network that is being configured.
The following message appears at the conclusion, which confirms that the additional network
was configured successfully.
[INFO
10.
] Network successfully configured on all the VM(s)
Configure a second additional network, if necessary.
At this point, you used one of the unused network interface pairs to configure an additional
network. Repeat these instructions to configure a second additional network using the
remaining unused interface pair, if necessary.
272
Oracle MiniCluster S7-2 Administration Guide • March 2017
Managing the Security Configuration (CLI)
You can run these compliance commands:
■
■
■
■
■
“Show Compliance Information (CLI)” on page 273Show all compliance information for
the system
“Schedule a Compliance Run (CLI)” on page 274Schedule a compliance run
“Set SSH Key Options (CLI)” on page 274
“Show Encryption Keys (CLI)” on page 275
“Back Up the Encryption Keystore (CLI)” on page 277
Show Compliance Information (CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Type:
% mcmu compliance -l
INFO SSH login to mc2-n1 successfully.
.
<output omitted>
.
INFO SSH login to mc2-n1 successfully.
INFO:MCMU.controllers.common.pexpect_util:SSH login to mc2-n1 successfully.
Compliance reporting method:
Administration VMs:
Application and Database VMs:
id node
remarks
-- ------------------11 mc2-n1
12 mc2-n1
zonename
DISA-STIG
DISA-STIG
benchmark
score
dateTime
-------------------- --------------- ---------- ---------------global
dbzg2-vm1-mc2-n1
disa-stig
disa-stig
87.96
88.83
Managing the Security Configuration (CLI)
-
273
Schedule a Compliance Run (CLI)
13
14
15
16
mc2-n1
mc2-n2
mc2-n2
mc2-n2
app1-vm1-mc2-n1
global
dbzg2-vm1-mc2-n2
app1-vm1-mc2-n2
disa-stig
disa-stig
disa-stig
disa-stig
96.94
87.96
88.83
96.94
-
Schedule a Compliance Run (CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Use this syntax:
% mcmu compliance --schedule -n nodex -z VMname -t time -f frequency
where:
■
■
■
■
nodex is the node (node1 or node2).
VMname is the VM name. To determine VM names, see “List Details of an App Group
Profile (CLI)” on page 199. Note – Compliance benchmarks are not supported on the kernel
zones.
time is the time that you want the compliance benchmark to run, in 24-hour format (for
example, 13:01). The default is the current time.
frequency is the frequency that you want the compliance benchmark to run (once or
monthly).
Set SSH Key Options (CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
To set the key file type, type:
% mcmu sshkey --type=keytype
where keytype is default or rekey.
3.
To set the source zone that the key file is copied from, type:
% mcmu sshkey --source=source_VM
where source_VM is the source VM that the key is copied from.
4.
274
To set the destination zone that the key file is copied to, type:
Oracle MiniCluster S7-2 Administration Guide • March 2017
Show Encryption Keys (CLI)
% mcmu sshkey --dest=desination_VM
where desination_VM is the destination VM that the key is copied to, separated by commas.
Show Encryption Keys (CLI)
Use this procedure to list all the encryption keys on a node.
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Use this syntax:
% mcmu security -l nodex
where nodex is node1 or node2.
For example:
% mcmu security -l node1
NODENUM | HOSTNAME | DATASET
| KEYLABEL
| ENCRYPTKEY | ENCRYPTSTATUS | KEYSOURCE | CREATEDATE
|
REKEYDATE | KEYSTATUS
--------+----------+------------------------------------------------------+-------------------------+-------------+---------------+-----------+-----------------------+-----------+---------1
| mc2-n1 | rpool/common
| gz_mc2n1_zw;pinfile
| aes-256-ccm | ON
| raw,pkcs11 | Thu Sep 29 17:16 2016 | | available
1
| mc2-n1 | rpool/audit_pool
| gz_mc2n1_zw;pinfile
| aes-256-ccm | ON
| raw,pkcs11 | Thu Sep 29 17:16 2016 | | available
1
| mc2ss01 | rpool/common
|
kz_mc2ss01_zw;pinfile | aes-256-ccm | ON
| raw,pkcs11 | Thu Sep 29 14:39
2016 | | available
1
| mc2ss01 | rpool/audit_pool
|
kz_mc2ss01_zw;pinfile | aes-256-ccm | ON
| raw,pkcs11 | Thu Sep 29 14:39
2016 | | available
1
| mc2ss01 | rpool/u01
|
kz_mc2ss01_zw;pinfile | aes-256-ccm | ON
| raw,pkcs11 | Thu Sep 29 14:39
2016 | | available
1
| mc2-n1 | mcpool/dbzg2-vm1-mc2-n1u01
| dbzg2-vm1mc2-n1-id-key | aes-256-ccm | ON
| raw,pkcs11 | Fri Sep 30 9:17 2016 | | available
Managing the Security Configuration (CLI)
275
Show Encryption Keys (CLI)
1
| mc2-n1 | mcpool/dbzg2-vm1-mc2-n1zroot
| dbzg2-vm1mc2-n1-id-key | aes-256-ccm | ON
| raw,pkcs11 | Fri Sep 30 9:17 2016 | | available
1
| mc2-n1 | mcpool/dbzg2-vm1-mc2-n1zroot/rpool
| dbzg2-vm1mc2-n1-id-key | aes-256-ccm | ON
| raw,pkcs11 | Fri Sep 30 9:17 2016 | | available
1
| mc2-n1 | mcpool/dbzg2-vm1-mc2-n1zroot/rpool/ROOT
| dbzg2-vm1mc2-n1-id-key | aes-256-ccm | ON
| raw,pkcs11 | Fri Sep 30 9:17 2016 | | available
1
| mc2-n1 | mcpool/dbzg2-vm1-mc2-n1zroot/rpool/ROOT/solaris-0
| dbzg2-vm1mc2-n1-id-key | aes-256-ccm | ON
| raw,pkcs11 | Fri Sep 30 9:17 2016 | | available
1
| mc2-n1 | mcpool/dbzg2-vm1-mc2-n1zroot/rpool/ROOT/solaris-0/var | dbzg2-vm1mc2-n1-id-key | aes-256-ccm | ON
| raw,pkcs11 | Fri Sep 30 9:17 2016 | | available
1
| mc2-n1 | mcpool/dbzg2-vm1-mc2-n1zroot/rpool/VARSHARE
| dbzg2-vm1mc2-n1-id-key | aes-256-ccm | ON
| raw,pkcs11 | Fri Sep 30 9:17 2016 | | available
1
| mc2-n1 | mcpool/dbzg2-vm1-mc2-n1zroot/rpool/export
| dbzg2-vm1mc2-n1-id-key | aes-256-ccm | ON
| raw,pkcs11 | Fri Sep 30 9:17 2016 | | available
1
| mc2-n1 | mcpool/dbzg2-vm1-mc2-n1zroot/rpool/export/home
| dbzg2-vm1mc2-n1-id-key | aes-256-ccm | ON
| raw,pkcs11 | Fri Sep 30 9:17 2016 | | available
1
| mc2-n1 | mcpool/app1-vm1-mc2-n1u01
| app1-vm1mc2-n1-id-key | aes-256-ccm | ON
| raw,pkcs11 | Fri Sep 30 11:26 2016 | | available
1
| mc2-n1 | mcpool/app1-vm1-mc2-n1zroot
| app1-vm1mc2-n1-id-key | aes-256-ccm | ON
| raw,pkcs11 | Fri Sep 30 11:26 2016 | | available
1
| mc2-n1 | mcpool/app1-vm1-mc2-n1zroot/rpool
| app1-vm1mc2-n1-id-key | aes-256-ccm | ON
| raw,pkcs11 | Fri Sep 30 11:26 2016 | | available
1
| mc2-n1 | mcpool/app1-vm1-mc2-n1zroot/rpool/ROOT
| app1-vm1mc2-n1-id-key | aes-256-ccm | ON
| raw,pkcs11 | Fri Sep 30 11:26 2016 | | available
1
| mc2-n1 | mcpool/app1-vm1-mc2-n1zroot/rpool/ROOT/solaris-0
| app1-vm1mc2-n1-id-key | aes-256-ccm | ON
| raw,pkcs11 | Fri Sep 30 11:26 2016 | | available
1
| mc2-n1 | mcpool/app1-vm1-mc2-n1zroot/rpool/ROOT/solaris-0/var | app1-vm1mc2-n1-id-key | aes-256-ccm | ON
| raw,pkcs11 | Fri Sep 30 11:26 2016 | | available
1
| mc2-n1 | mcpool/app1-vm1-mc2-n1zroot/rpool/VARSHARE
| app1-vm1mc2-n1-id-key | aes-256-ccm | ON
| raw,pkcs11 | Fri Sep 30 11:26 2016 | | available
1
| mc2-n1 | mcpool/app1-vm1-mc2-n1zroot/rpool/export
| app1-vm1mc2-n1-id-key | aes-256-ccm | ON
| raw,pkcs11 | Fri Sep 30 11:26 2016 | | available
276
Oracle MiniCluster S7-2 Administration Guide • March 2017
Back Up the Encryption Keystore (CLI)
1
| mc2-n1 | mcpool/app1-vm1-mc2-n1zroot/rpool/export/home
| app1-vm1mc2-n1-id-key | aes-256-ccm | ON
| raw,pkcs11 | Fri Sep 30 11:26 2016 | | available
Back Up the Encryption Keystore (CLI)
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Type:
% mcmu security -b
Managing the Security Configuration (CLI)
277
278
Oracle MiniCluster S7-2 Administration Guide • March 2017
Managing Storage (CLI)
These topics describe how to use the mcmu CLI to manage system storage.
Description
Links
Enable or disable shared storage for a VM group.
“Enable or Disable Shared Storage (CLI)” on page 279
Add an External NFS to an App VM.
“Add External NFS (CLI)” on page 282
Enable a new storage array.
“Configure an Added Storage Array (CLI)” on page 284
Manage the replacement of a drive.
“Prepare a Drive for Removal (CLI)” on page 287
“Reattach a Replaced Disk (CLI)” on page 290
Enable or Disable Shared Storage (CLI)
Use this procedure to enable or disable access to the shared storage and NFS for a DB VM
group or an App VM group. For more details about this administrative task, see “Enable or
Disable Shared Storage (BUI)” on page 135.
The shared storage provides storage space for any storage purpose, and is available to all VMs
within a group.
Caution - Systems deployed in highly secured environments should disable shared storage.
For more information, refer to the Oracle MiniCluster S7-2 Security Guide at http://docs.
oracle.com/cd/E69469_01.
1.
To see if shared storage is currently enabled or disabled, view the DB VM group
or App VM group in the BUI.
■
■
For a DB VM group – Go to Database → Virtual Machine Group Profile.
For an App VM group – Go to Application → Virtual Machine Group Profile.
Note - You can also enable or disable the shared storage from those BUI pages.
Managing Storage (CLI)
279
Enable or Disable Shared Storage (CLI)
2.
Log into the mcmu CLI as a primary admin such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
3.
Identify the VMgroupID for the group you plan to enable or disable shared storage.
Perform one of these commands:
■
To obtain the VMgroupID for an App VM group, type:
% mcmu tenant -A -l
Listing APP VM Group...
Status : Active
EditStatus :
Description :
deletable : True
progress : False
VMgroupName : ff18
editable : True
VMgroupID : 2
■
To obtain the VMgroupID for a DB VM group, type:
% mcmu tenant -P -l
Listing DB VM Group Profile..
Status : Active
EditStatus :
Description : Initial DB VM Group
- NORMAL redundancy
- Shared Storage
- CIS
deletable : True
progress : False
VMgroupName : dbgp1
editable : True
VMgroupID : 1
4.
Enable or disable the shared storage.
When you perform this step, the mcmu CLI toggles the setting. In other words, if shared storage
is enabled, this command disables it. If it is disabled, this command enables it.
Use this syntax:
280
Oracle MiniCluster S7-2 Administration Guide • March 2017
Enable or Disable Shared Storage (CLI)
mcmu tenant -X -t VMgroupID
where:
■
■
X – is either G for a DB VM group, or V for an app VM group.
VMgroupID – is the VM group ID that you identified in the previous step.
% mcmu tenant -V -t 2
Getting APP VM Group...
Shared Storage Enabled: True
Are you sure you want to toggle shared storage for this VM Group?
Enter Y/N (N): Y
INFO SSH login to mc5qt-n1.us.oracle.com successfully.
INFO:MCMU.controllers.common.pexpect_util:SSH login to
mc5qt-n1.us.oracle.com successfully.
INFO su to user root successfully.
INFO:MCMU.controllers.common.pexpect_util:su to user root successfully.
INFO zlogin to ff18-vm1-mc5qt-n1 successful.
INFO:MCMU.controllers.common.pexpect_util:zlogin to ff18-vm1-mc5qt-n1
successful.
INFO SSH login to mc5qt-n2.us.oracle.com successfully.
INFO:MCMU.controllers.common.pexpect_util:SSH login to
mc5qt-n2.us.oracle.com successfully.
INFO su to user root successfully.
INFO:MCMU.controllers.common.pexpect_util:su to user root successfully.
INFO zlogin to ff18-vm1-mc5qt-n2 successful.
INFO:MCMU.controllers.common.pexpect_util:zlogin to ff18-vm1-mc5qt-n2
successful.
toggle operation completed successfully
5.
To verify the change, repeat Step 1.
6.
To access the shared file system, log into the VM and perform Oracle Solaris
commands.
To access the file system:
% cd /sharedstore
List contents of the directory:
Note - The /sharedstore directory is empty until you put software in the directory.
% ls /sharedstore
Managing Storage (CLI)
281
Add External NFS (CLI)
Downloads
Videos
Music
Pictures
Presentations Templates
Texts
Related Information
■
Securing Files and Verifying File Integrity in Oracle Solaris 11.3 (https://docs.oracle.
com/cd/E53394_01/html/E54827/index.html)
■
Managing File Systems in Oracle Solaris 11.3 (http://docs.oracle.com/cd/E53394_01/
html/E54785/index.html)
■
Oracle Solaris 11.3 Information Library (https://docs.oracle.com/cd/E53394_01/)
Add External NFS (CLI)
Use this procedure to add a network file system (NFS) to a DB VM group or an App VM
group.
The NFS service must be NFSv4.
The NFS that you add can be any whole or partial directory tree or a file hierarchy, including a
single file that is shared by and NFS server.
When you add external NFS to a group, the remote file system is immediately accessible to all
the VMs in the group.
External NFS is only made available to VMs in a group if shared storage is enabled. See
“Enable or Disable Shared Storage (BUI)” on page 135.
1.
Log into the mcmu CLI as a primary admin such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
(If needed) Check what the NFS server is sharing:
a.
Ensure that an NFS is available form a server in your environment.
There are a variety of ways to perform this step, depending on the type of server. This is an
example of an Oracle Solaris command that shows what file systems a server is sharing:
% /usr/sbin/showmount -e NFSserver_name_or_IPaddress
b.
To check the version of the NFS service provided by the NFS server, type:
% rpcinfo -p NFSserver_name_or_IPaddress | egrep nfs
100003
4 tcp 2049 nfs
282
Oracle MiniCluster S7-2 Administration Guide • March 2017
Add External NFS (CLI)
The second column displays the version number. You might see several lines of output.
One of them must report version 4.
3.
Edit the App VM group profile.
This command displays any existing external NFS and prompts you to add additional external
NFS or delete the existing external NFS.
% mcmu tenant -A -u
Add External NFS
External NFS
ID 1
Mount: A_mountpoint
Share: data01
Server IP: 10.129.xx.xxx
Do you want to "(A)dd a MountPoint, (D)elete a MountPoint or (C)ontinue editing the VM
Group Profile"?
Enter A/D/C: A
Enter Mount: my_mountpoint
Enter Share: data02
Enter Server IP address: 10:129:xx.xxx
Do you want to "(A)dd a MountPoint, (D)elete a MountPoint or (C)ontinue editing the VM
Group Profile"?
Enter A/D/C: A
Enter Mount: another_mountpoint
Enter Share: data02
Enter Server IP address: 10:129:xx.xxx
Do you want to "(A)dd a MountPoint, (D)elete a MountPoint or (C)ontinue editing the VM
Group Profile"?
Enter A/D/C: C
4.
Respond to the remaining prompts until the command is complete.
Related Information
■
Securing Files and Verifying File Integrity in Oracle Solaris 11.3 (https://docs.oracle.
com/cd/E53394_01/html/E54827/index.html)
■
Managing File Systems in Oracle Solaris 11.3 (http://docs.oracle.com/cd/E53394_01/
html/E54785/index.html)
■
Oracle Solaris 11.3 Information Library (https://docs.oracle.com/cd/E53394_01/)
Managing Storage (CLI)
283
Configure an Added Storage Array (CLI)
Configure an Added Storage Array (CLI)
Use this procedure to configure a storage array that is added to the system after the initial
installation. You can connect the additional storage array and run this procedure on a system
that is running.
Note - When MiniCluster is installed, the installation process automatically detects all attached
storage (including multiple storage arrays), configures the storage, and makes the storage
available for use. This procedure is intended for situations when a storage array is added to the
system after the installation.
When this procedure is complete, the added storage is immediately available for use.
1.
Ensure that the additional storage array is physically connected to MiniCluster.
For details on connecting storage array hardware, refer to the Oracle MiniCluster S7-2
Installation Guide. For the location of documentation, see “Product Documentation
Library” on page 13.
You can verify storage array hardware connectivity through the MCMU BUI Hardware
Topology page. See “View the Hardware Topology (BUI)” on page 174.
2.
Log into the mcmu CLI as a primary admin such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
3.
Type:
% mcmu diskutil -e
For example:
% mcmu diskutil -e
[INFO
] Log file path : mc12-n1:/var/opt/oracle.minicluster/setup/logs/
mcmu_100416_160829.log
[INFO
] Log file path : /var/opt/oracle.minicluster/setup/logs/
omc_diskutil_functionality_100416_160830.log
[INFO
] Log file path : mc12-n1:/var/opt/oracle.minicluster/setup/logs/
omc_fmdservice_100416_160830.log
[INFO
] Ensure that fmd Service is Functional and the System Utilities have
consistent view of JBODs ..
[INFO
] Ensure that fmd Service is Functional succeeded.
[INFO
] Cross-check the number of disks reported by diskinfo and format utilities
succeeded.
[INFO
] Compare the disks in all JBODs across both compute nodes succeeded.
284
Oracle MiniCluster S7-2 Administration Guide • March 2017
Configure an Added Storage Array (CLI)
[INFO
] Ensure that fmd Service is Functional and the System Utilities have
consistent view of JBODs .. Completed
Oracle Corporation
SunOS 5.11
11.3
June 2016
Minicluster Setup successfully configured
Unauthorized modification of this system configuration strictly prohibited
[INFO
] Invoked by OS user: mcinstall
[INFO
] Find log at: mc12-n1:/var/opt/oracle.minicluster/setup/logs/
omc_node1exec_100416_160835.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 : mc12-n2:/var/opt/oracle.minicluster/setup/logs/
omc_fmdservice_100416_160836.log
[INFO
] Ensure that fmd Service is Functional and the System Utilities have
consistent view of JBODs ..
[INFO
] Ensure that fmd Service is Functional succeeded.
[INFO
] Cross-check the number of disks reported by diskinfo and format utilities
succeeded.
[INFO
] Ensure that fmd Service is Functional and the System Utilities have
consistent view of JBODs .. Completed
[INFO
] Executing Script on the 2nd Node succeeded.
[INFO
] Executing Script on the 2nd Node Completed
[INFO
] Log file path : mc12-n1:/var/opt/oracle.minicluster/setup/logs/
omc_partitiondisk_100416_160845.log
[INFO
] Partitioning disk..
[INFO
] Labelling and resetting the size of disks..
[INFO
] Log file path : mc12-n1:/var/opt/oracle.minicluster/setup/logs/
omc_verify_jbods_100416_160856.log
[INFO
] Verifying the JBOD(s)..
[INFO
] Verifying number and size of disks in all JBOD(s)...
--------- DISK VERIFICATION------
DISK
CATEGORY STATUS
c0t5000CCA23B0B3508d0
HDD-8 OK
c0t5000CCA23B0BA71Cd0
HDD-8 OK
c0t5000CCA23B0BB1D4d0
HDD-8 OK
c0t5000CCA23B0BA6E0d0
HDD-8 OK
c0t5000CCA23B0BA768d0
HDD-8 OK
c0t5000CCA23B0B906Cd0
HDD-8 OK
REASON
Managing Storage (CLI)
285
Configure an Added Storage Array (CLI)
c0t5000CCA0536C9078d0
SSD-1.6 OK
c0t5000CCA0536CAB44d0
SSD-1.6 OK
c0t5000CCA0536CAA48d0
SSD-1.6 OK
c0t5000CCA0536CA7D0d0
SSD-1.6 OK
c0t5000CCA0536CB368d0
SSD-1.6 OK
c0t5000CCA0536CB530d0
SSD-1.6 OK
c0t5000CCA0536C90D4d0
SSD-1.6 OK
c0t5000CCA0536CAB70d0
SSD-1.6 OK
c0t5000CCA0536C8BB0d0
SSD-1.6 OK
c0t5000CCA0536CB510d0
SSD-1.6 OK
c0t5000CCA0536CB518d0
SSD-1.6 OK
c0t5000CCA0536CB3A8d0
SSD-1.6 OK
c0t5000CCA0536CB498d0
SSD-1.6 OK
c0t5000CCA0536C90FCd0
SSD-1.6 OK
c0t5000CCA04EB4A994d0
SSD-200 OK
c0t5000CCA04EB47CB4d0
SSD-200 OK
c0t5000CCA04E0D6CD4d0
SSD-200 OK
c0t5000CCA04E0D65E4d0
SSD-200 OK
[INFO
] Verifying the JBOD(s).. Completed
[INFO
] Log file path : mc12-n1:/var/opt/oracle.minicluster/setup/logs/
omc_partitiondisk_100416_160906.log
[INFO
] Partitioning disk..
[INFO
] Erasing the disks, creating EFI labels,setting volume name...
[INFO
] Creating partitions...
[INFO
] Partitioning disk.. Completed
Storage alias for JBOD ORACLE-DE3-24C:1621NMQ005 was already created. Skipping ..
Creating alias JBODARRAY2 for JBOD ORACLE-DE3-24C.1539NMQ00D ..
286
Oracle MiniCluster S7-2 Administration Guide • March 2017
Prepare a Drive for Removal (CLI)
Log file location: /var/opt/oracle.minicluster/setup/logs/omccrstoragealias.20161004.1609.log
Oracle Corporation
SunOS 5.11
11.3
June 2016
Minicluster Setup successfully configured
Unauthorized modification of this system configuration strictly prohibited
[INFO
] Invoked by OS user: mcinstall
[INFO
] Find log at: mc12-n1:/var/opt/oracle.minicluster/setup/logs/
omc_node1exec_100416_161002.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
Storage alias for JBOD ORACLE-DE3-24C:1621NMQ005 was already created. Skipping ..
Creating alias JBODARRAY2 for JBOD ORACLE-DE3-24C.1539NMQ00D ..
Log file location: /var/opt/oracle.minicluster/setup/logs/omccrstoragealias.20161004.1610.log
[INFO
[INFO
] Executing Script on the 2nd Node succeeded.
] Executing Script on the 2nd Node Completed
Prepare a Drive for Removal (CLI)
This procedure only applies to drives in the storage arrays.
Use this procedure to logically remove a storage array drive from the system before you
physically remove the drive.
The length of time that it takes to complete this procedure before you can physically remove the
drive depends on the type of drive you are removing:
■
■
1.
SSD – The detach operation completes quickly and the drive can be removed immediately.
HDD – The detach operation takes several minutes to complete. Do not remove the drive
before the detach operation competes.
Log into the mcmu CLI as a primary admin such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Identify the drive name.
You might be able to get the drive name from the error message or log file that led to the plan to
replace the drive.
Managing Storage (CLI)
287
Prepare a Drive for Removal (CLI)
You can use a command such as diskinfo. Make note of the long drive name (such as
c0t5000CCA23B0BF34Cd0) for use with this procedure. Also make note of the shorter name
(such as HDD8) for use with the followup task when you reattached the replaced drive.
Also note that the storage array drives are identified by a JBODARRAY string.
For example:
% diskinfo
D:devchassis-path
---------------------------------/dev/chassis/SYS/HDD0/disk
/dev/chassis/SYS/HDD1/disk
/dev/chassis/SYS/HDD2/disk
/dev/chassis/SYS/HDD3/disk
/dev/chassis/SYS/HDD4/disk
/dev/chassis/SYS/HDD5/disk
/dev/chassis/SYS/HDD6
/dev/chassis/SYS/HDD7
/dev/chassis/SYS/MB/EUSB-DISK/disk
/dev/chassis/JBODARRAY1/HDD0/disk
/dev/chassis/JBODARRAY1/HDD1/disk
/dev/chassis/JBODARRAY1/HDD2/disk
/dev/chassis/JBODARRAY1/HDD3/disk
/dev/chassis/JBODARRAY1/HDD4/disk
/dev/chassis/JBODARRAY1/HDD5/disk
/dev/chassis/JBODARRAY1/HDD6/disk
/dev/chassis/JBODARRAY1/HDD7/disk
/dev/chassis/JBODARRAY1/HDD8/disk
/dev/chassis/JBODARRAY1/HDD9/disk
/dev/chassis/JBODARRAY1/HDD10/disk
/dev/chassis/JBODARRAY1/HDD11/disk
/dev/chassis/JBODARRAY1/HDD12/disk
/dev/chassis/JBODARRAY1/HDD13/disk
/dev/chassis/JBODARRAY1/HDD14/disk
/dev/chassis/JBODARRAY1/HDD15/disk
/dev/chassis/JBODARRAY1/HDD16/disk
/dev/chassis/JBODARRAY1/HDD17/disk
/dev/chassis/JBODARRAY1/HDD18/disk
/dev/chassis/JBODARRAY1/HDD19/disk
/dev/chassis/JBODARRAY1/HDD20/disk
/dev/chassis/JBODARRAY1/HDD21/disk
/dev/chassis/JBODARRAY1/HDD22/disk
/dev/chassis/JBODARRAY1/HDD23/disk
3.
c:occupant-compdev
--------------------c0t5000CCA02D1EE2A8d0
c0t5000CCA02D1E7AACd0
c0t5000CCA02D1EDCECd0
c0t5000CCA02D1ED360d0
c0t5000CCA02D1EE6D8d0
c0t5000CCA02D1EE6CCd0
c1t0d0
c0t5000CCA25497267Cd0
c0t5000CCA2549732B8d0
c0t5000CCA254974F28d0
c0t5000CCA254965A78d0
c0t5000CCA254978510d0
c0t5000CCA254964E3Cd0
c0t5000CCA0536CA5E4d0
c0t5000CCA0536CA7B0d0
c0t5000CCA23B0BF34Cd0
c0t5000CCA0536CB828d0
c0t5000CCA0536CB308d0
c0t5000CCA0536CAF2Cd0
c0t5000CCA0536CABE4d0
c0t5000CCA0536CB684d0
c0t5000CCA0536CA870d0
c0t5000CCA0536CAB88d0
c0t5000CCA0536CA754d0
c0t5000CCA0536CAD10d0
c0t5000CCA0536CAEF8d0
c0t5000CCA0536CA83Cd0
c0t5000CCA04EB272E8d0
c0t5000CCA04EB27234d0
c0t5000CCA04EB27428d0
c0t5000CCA04EB272A0d0
Use this syntax to detach the disk prior to removing the disk:
% mcmu diskutil -d diskname
288
Oracle MiniCluster S7-2 Administration Guide • March 2017
Prepare a Drive for Removal (CLI)
where diskname is the disk identifier of the drive you plan to remove.
For example:
% mcmu diskutil -d c0t5000CCA23B0BF34Cd0
.
<output omitted>
.
INFO:MCMU.controllers.common.pexpect_util:su to user oracle successfully.
[INFO
] logged into the zone f18-vm1-mc5qt-n1 as oracle
[INFO
] disk alias found to be RECO_0003
[INFO
] dropping disk c0t5000CCA23B0BF34Cd0s1
[INFO
] ['', 'Diskgroup altered.', '']
[INFO
] ASM rebalance complete in diskgroup RECO in zonegroup f18
[INFO
] disk alias found to be DATA_0003
[INFO
] dropping disk c0t5000CCA23B0BF34Cd0s4
[INFO
] ['', 'Diskgroup altered.', '']
[INFO
] ASM still initializing, please retry in a few minutes to check the progress
by running
'mcmu diskutil -p'
[INFO
] Disk should NOT be detached until rebalance is complete.
[INFO
] disk alias found to be SYSTEM_0003
[INFO
] dropping disk c0t5000CCA23B0BF34Cd0s5
[INFO
] ['', 'Diskgroup altered.', '']
[INFO
] ASM rebalance in progress in the zonegroup f18.
Estimated time of completion is 61.
[INFO
[INFO
[INFO
[INFO
[INFO
.
<output
.
[INFO
[INFO
4.
]
]
]
]
]
Disk should NOT be detached until rebalance is complete.
exiting surplus
Partitions to be dropped: [1]
Removing disk from zones...
Modifying zones: [u'f18-vm1-mc5qt-n1'] on node: mc5qt-n1
omitted>
] Running.. exit
] Disk {disk} being detached from Minicluster.
Check the status of the detach operation.
If you want to check the status, but the detach operation is still running, login to the mcmu CLI in
another window.
Type:
% mcmu diskutil -p
Managing Storage (CLI)
289
Reattach a Replaced Disk (CLI)
[INFO
.
<output
.
[INFO
.
<output
.
[INFO
5.
] Checking asm rebalance progress
omitted>
] ASM Rebalance successfully complete. Attempting to remove disk from zones.
omitted>
] Disk successfully removed from Minicluster.
When the ASM rebalance is complete, you can remove the drive.
After the new drive is installed, reattach the drive. See “Reattach a Replaced Disk
(CLI)” on page 290.
Reattach a Replaced Disk (CLI)
This procedure only applies to drives in the storage arrays.
Use this procedure to reattach a drive that was detached using mcmu diskutil -d before it was
replaced.
1.
Log into the mcmu CLI as a primary admin such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Identify the full disk name of the replaced drive.
You can use a command such as diskinfo.
In this example, HDD8 was replaced, and diskinfo shows that the full drive name for HDD8 is
c0t5000CCA0536CA710d0.
Also note that the storage array drives are identified by a JBODARRAY string.
% diskinfo
D:devchassis-path
---------------------------------/dev/chassis/SYS/HDD0/disk
/dev/chassis/SYS/HDD1/disk
/dev/chassis/SYS/HDD2/disk
/dev/chassis/SYS/HDD3/disk
/dev/chassis/SYS/HDD4/disk
/dev/chassis/SYS/HDD5/disk
/dev/chassis/SYS/HDD6
/dev/chassis/SYS/HDD7
/dev/chassis/SYS/MB/EUSB-DISK/disk
290
c:occupant-compdev
--------------------c0t5000CCA02D1EE2A8d0
c0t5000CCA02D1E7AACd0
c0t5000CCA02D1EDCECd0
c0t5000CCA02D1ED360d0
c0t5000CCA02D1EE6D8d0
c0t5000CCA02D1EE6CCd0
c1t0d0
Oracle MiniCluster S7-2 Administration Guide • March 2017
Reattach a Replaced Disk (CLI)
/dev/chassis/JBODARRAY1/HDD0/disk
/dev/chassis/JBODARRAY1/HDD1/disk
/dev/chassis/JBODARRAY1/HDD2/disk
/dev/chassis/JBODARRAY1/HDD3/disk
/dev/chassis/JBODARRAY1/HDD4/disk
/dev/chassis/JBODARRAY1/HDD5/disk
/dev/chassis/JBODARRAY1/HDD6/disk
/dev/chassis/JBODARRAY1/HDD7/disk
/dev/chassis/JBODARRAY1/HDD8/disk
/dev/chassis/JBODARRAY1/HDD9/disk
/dev/chassis/JBODARRAY1/HDD10/disk
/dev/chassis/JBODARRAY1/HDD11/disk
/dev/chassis/JBODARRAY1/HDD12/disk
/dev/chassis/JBODARRAY1/HDD13/disk
/dev/chassis/JBODARRAY1/HDD14/disk
/dev/chassis/JBODARRAY1/HDD15/disk
/dev/chassis/JBODARRAY1/HDD16/disk
/dev/chassis/JBODARRAY1/HDD17/disk
/dev/chassis/JBODARRAY1/HDD18/disk
/dev/chassis/JBODARRAY1/HDD19/disk
/dev/chassis/JBODARRAY1/HDD20/disk
/dev/chassis/JBODARRAY1/HDD21/disk
/dev/chassis/JBODARRAY1/HDD22/disk
/dev/chassis/JBODARRAY1/HDD23/disk
3.
c0t5000CCA25497267Cd0
c0t5000CCA2549732B8d0
c0t5000CCA254974F28d0
c0t5000CCA254965A78d0
c0t5000CCA254978510d0
c0t5000CCA254964E3Cd0
c0t5000CCA0536CA5E4d0
c0t5000CCA0536CA7B0d0
c0t5000CCA0536CA710d0
c0t5000CCA0536CB828d0
c0t5000CCA0536CB308d0
c0t5000CCA0536CAF2Cd0
c0t5000CCA0536CABE4d0
c0t5000CCA0536CB684d0
c0t5000CCA0536CA870d0
c0t5000CCA0536CAB88d0
c0t5000CCA0536CA754d0
c0t5000CCA0536CAD10d0
c0t5000CCA0536CAEF8d0
c0t5000CCA0536CA83Cd0
c0t5000CCA04EB272E8d0
c0t5000CCA04EB27234d0
c0t5000CCA04EB27428d0
c0t5000CCA04EB272A0d0
Use this syntax to attach a disk:
% mcmu diskutil -a diskname
where diskname is the name of the disk you want to attach.
For example:
% mcmu diskutil -a c0t5000CCA0536CA710d0
Managing Storage (CLI)
291
292
Oracle MiniCluster S7-2 Administration Guide • March 2017
Administering the Virtual Tuning Assistant (CLI)
These topics describe how to use the MCMU CLI to check the status of mctuner (the virtual
tuning assistant).
Note - For instructions on how to use the MCMU BUI to obtain virtual tuning information, see
“Checking the Virtual Tuning Status (BUI)” on page 155.
■
■
“Configure the mctuner Notification Email Address (CLI)” on page 293
“View Virtual Tuning Assistant Status (CLI)” on page 294
Configure the mctuner Notification Email Address (CLI)
By default, the virtual tuning assistant is enabled on the system to ensure that the system is
running with optimal tuning parameters. If the tuning assistant detects any issues, it sends email
notifications to the email address that is configured for the tuning assistant.
Note - For the most thorough notifications, configure the tuning assistant email address in the
global and kernel zones on both nodes.
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Check the current email address that is configured in the tuning assistant.
In this example, the address is configured as root@localhost, which is the factory default, and
should be changed to an email address of an administrator.
% svcprop mctuner | grep -i email
mctuner_vars/EMAIL_ADDRESS astring root@localhost
mctuner_vars/EMAIL_MESSAGES boolean true
3.
Configure the email address for the global zone.
In this example, the email address is configured for the global zone on node 1.
Administering the Virtual Tuning Assistant (CLI)
293
View Virtual Tuning Assistant Status (CLI)
% mcmu mctuner -P -n node1 -z global -k EMAIL_Address -v admin01@company.com
[INFO
] Log file path : mc3-n1:/var/opt/oracle.minicluster/setup/logs/
mcmu_082916_191031.log
INFO SSH login to mc3-n1 successfully.
INFO:MCMU.controllers.common.pexpect_util:SSH login to mc3-n1 successfully.
INFO su to user root successfully.
INFO:MCMU.controllers.common.pexpect_util:su to user root successfully.
[INFO
] mctuner property EMAIL_ADDRESS in zone global on node1 has been set to
admin01@company.com
4.
Configure the email address for the kernel zone.
In this example, the email address is configured for the kernel zone on node 1.
% mcmu mctuner -P -n node1 -z acfskz -k EMAIL_Address -v admin01@company.com
[INFO
] Log file path : mc3-n1:/var/opt/oracle.minicluster/setup/logs/
mcmu_082916_191031.log
INFO SSH login to mc3-n1 successfully.
INFO:MCMU.controllers.common.pexpect_util:SSH login to mc3-n1 successfully.
INFO su to user root successfully.
INFO:MCMU.controllers.common.pexpect_util:su to user root successfully.
[INFO
] mctuner property EMAIL_ADDRESS in zone acfskz on node1 has been set to
admin01@company.com
5.
Repeat Step 3 and Step 4 for node 2.
View Virtual Tuning Assistant Status (CLI)
This procedure shows the mctuner status for all enabled mctuner instances on the system.
1.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
2.
Type:
In this example, the status of mctuner is online for the global and kernel zones on both nodes.
% mcmu mctuner -S
[INFO
] Log file path : mc3-n1:/var/opt/oracle.minicluster/setup/logs/
mcmu_082216_172246.log
INFO SSH login to mc3-n1 successfully.
INFO:MCMU.controllers.common.pexpect_util:SSH login to mc3-n1 successfully.
Aug 22 17:22:50 mccn su: 'su root' succeeded for mcinstall on /dev/pts/2
INFO su to user root successfully.
INFO:MCMU.controllers.common.pexpect_util:su to user root successfully.
294
Oracle MiniCluster S7-2 Administration Guide • March 2017
View Virtual Tuning Assistant Status (CLI)
INFO zlogin to acfskz successful.
INFO:MCMU.controllers.common.pexpect_util:zlogin to acfskz successful.
INFO SSH login to mc3-n2 successfully.
INFO:MCMU.controllers.common.pexpect_util:SSH login to mc3-n2 successfully.
INFO su to user root successfully.
INFO:MCMU.controllers.common.pexpect_util:su to user root successfully.
INFO zlogin to acfskz successful.
INFO:MCMU.controllers.common.pexpect_util:zlogin to acfskz successful.
node
zone
status
issues
notices
---------- ---------- ---------- ------------------------------ ---------mc3-n1
global
Online
mc3-n1
acfskz
Online
mc3-n2
global
Online
mc3-n2
acfskz
Online
Administering the Virtual Tuning Assistant (CLI)
295
296
Oracle MiniCluster S7-2 Administration Guide • March 2017
Updating MiniCluster Software (CLI)
These topics are described in this section:
■
■
■
“View Software Component Versions (CLI)” on page 297
“Update the MCMU Component (CLI)” on page 299
“Update Other MiniCluster Software Components (CLI)” on page 302
View Software Component Versions (CLI)
Use this procedure to display the version status of the components through the CLI.
Alternatively, you can use the BUI. The BUI provides component version numbers, the CLI
does not. See “View Software Component Versions (BUI)” on page 160.
1.
Ensure that the Patch Bundle is downloaded to MiniCluster.
The latest Patch Bundle provides the system with the latest component versions, and is used
to determine if updates are available for the components. These procedures describe how to
administer the Patch Bundle:
a.
Download the Patch Bundle.
See “Check for and Obtain the Latest Updates” on page 162.
b.
Unzip and extract the bundle.
See “Extract the Patch Bundle” on page 164.
2.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
3.
Upload the latest component versions.
Using the upload option moves the contents of the Patch Bundle to the /var/opt/
oracle.minicluster/sfw directory. This is necessary for the list option in Step 4 to report the
correct component status.
This example uploads all the components. It can run for five minutes or more.
Updating MiniCluster Software (CLI)
297
View Software Component Versions (CLI)
% mcmu patch -p upload
[INFO
] Actions to execute: upload
[INFO
] mcpatch: 0 % Executing strategy of Main level
[INFO
] Running plugins: ['upload', 'check_be', 'check_jbod', 'check_ilom',
'check_omctoolkit', 'check_acfs',
'check_repo', 'check_solaris_gz', 'check_solaris_kz',
'check_tenants']
<output omitted>
[INFO
] mcpatch: 100 % Done.
[INFO
] See log file for details: /var/opt/oracle.minicluster/setup/logs/
mc_patch_021617_140513.log
[INFO
] Completed successfully
This example uploads one component:
% mcmu patch -p check_ilom
[INFO
] Actions to execute: check_ilom
[INFO
] mcpatch: 0 % Executing strategy of Main level
[INFO
] Running plugins: ['check_ilom']
[INFO
] mcpatch: 0 % Started: Check system firmware version of Executing plugins
strategy
[INFO
] mcpatch: 0 % Finished: Check system firmware version of Executing plugins
strategy
[INFO
] mcpatch: 90 % Executing plugins strategy of Executing strategy
[INFO
] mcpatch: 90 % Executing strategy of Main level
[INFO
] mcpatch: 100 % Executing strategy of Main level
[INFO
] Command execution statistics: pexpect.run=10, task=0
[INFO
] mcpatch: 100 % Done.
[INFO
] See log file for details: /var/opt/oracle.minicluster/setup/logs/
mc_patch_021617_140656.log
[INFO
] Completed successfully
mcinstall@mc5qt-n1:/var/home/mcinstall % exit
4.
Display the update status of the components.
As shown in the example:
■
CURRENT – Indicates the component is up-to-date.
■
UPGRADE_NEEDED – Indicates that a newer version is available for the component .
■
NEWER – (Not shown) Indicates that a component's version is newer than what is in /var/
opt/oracle.minicluster/sfw.
% mcmu patch -l
COMPONENT-------------------------------- | STATUS-------MiniCluster Configuration Utility
| CURRENT
Storage Tray firmware
| CURRENT
298
Oracle MiniCluster S7-2 Administration Guide • March 2017
Update the MCMU Component (CLI)
Shared Filesystem software
Operating System package repository
Shared Storage Operating System
Compute Nodes Operating System
Compute Node firmware
Grid Infrastructure
Oracle db home /u01/.../11.2.0.4/dbhome_3
Oracle db home /u01/.../11.2.0.4/dbhome_4
Oracle db home /u01/.../12.1.0.2/dbhome_1
Oracle db home /u01/.../12.1.0.2/dbhome_2
5.
|
|
|
|
|
|
|
|
|
|
CURRENT
CURRENT
CURRENT
CURRENT
UPGRADE_NEEDED
CURRENT
CURRENT
CURRENT
UPGRADE_NEEDED
UPGRADE_NEEDED
Consider your next action.
■
■
Update the MCMU component, see “Update the MCMU Component
(CLI)” on page 299.
Update any of the other components, see “Update Other MiniCluster Software Components
(CLI)” on page 302 or “Update MiniCluster Software (BUI)” on page 167.
Update the MCMU Component (CLI)
Use this procedure to update the MCMU software on a fully installed MiniCluster. This
procedure only updates the MCMU software. To update other software components, see
“Update Other MiniCluster Software Components (CLI)” on page 302.and “Update
MiniCluster Software (BUI)” on page 167.
The system can be updated while DB and App VMs are running.
Caution - The MCMU component must be updated before you update any other component.
(see “Update the MCMU Component (CLI)” on page 299).
Caution - For systems running MCMU v1.1.21 and earlier, you must update the MCMU
software through the MCMU CLI as described in this procedure. Do not attempt to update
MCMU through the BUI because the update might fail. If you experience this problem, follow
the instructions in the MiniCluster Release Notes (Doc ID 2214746.1) available at http://
support.oracle.com, under the heading Upgrading Fully Configured MiniCluster to 1.1.21.4.
To review an overview of the update process, see “Component Update Process
Overview” on page 159.
Updating MiniCluster Software (CLI)
299
Update the MCMU Component (CLI)
Note - For the latest information about what updates are available, refer to the MiniCluster
Release Notes document that is available in MOS Doc ID 2153282.1 at: http://support.
oracle.com.
1.
Ensure that the correct bundles are downloaded on MiniCluster.
These procedures must be performed prior to updating the MCMU software:
a.
Ensure that the Patch Bundle and Component Bundle are downloaded to
MiniCluster.
See “Check for and Obtain the Latest Updates” on page 162.
b.
Ensure that the Patch Bundle is unzipped and extracted in the /var/opt/
oracle.minicluster/patch directory.
See “Extract the Patch Bundle” on page 164.
Note – You can install the Component Bundle before performing this procedure, or at the
end of this procedure. For instructions, see “Install the Component Bundle” on page 165.
2.
Log into the MCMU CLI on compute node 1 as a primary admin, such as
mcinstall.
See “Log in to the MCMU CLI” on page 29.
3.
Display the current version of MCMU.
% mcmu -V
Oracle MiniCluster Configuration Utility
MCMU v1.1.18
4.
Update the MCMU software component.
Note that the patch_omctoolkit option cannot be combined with any other mcmu patch
options.
Syntax:
mcmu patch -p update_omctoolkit [path_to_omctoolkit.p5p]
By default, this command expects to find the omctoolkit.p5p file in the /var/opt/
oracle.minicluster/sfw directory.
■
300
If you ran the mcmu patch -p upload command (a command listed in “View Software
Component Versions (CLI)” on page 297), perform this command:
Oracle MiniCluster S7-2 Administration Guide • March 2017
Update the MCMU Component (CLI)
% mcmu patch -p update_omctoolkit
■
If you did not run the mcmu patch -p upload command, you must specify the path to the
omctoolkit.p5p file.
First, identify the patch-version_no directory name where the Patch Bundle was untarred.
In this example, patch-1.1.21.4 is the directory name needed. Your directory name might
be different.
% cd /var/opt/oracle.minicluster/patch
% ls
README.txt
mc-1.1.21.4-patch.tar.ac
omc
beadm.py
mc-1.1.21.4-patch.tar.ad
patch-1.1.21.4
mc-1.1.21.4-patch.tar.aa
mc-1.1.21.4-patch.tar.ae
patch.
json
mc-1.1.21.4-patch.tar.ab
mc_patch.py
scripts
In this command line, replace patch-version_no with the directory name you identified.
% mcmu patch -p update_omctoolkit /var/opt/oracle.minicluster/patch/patch-version_no/mcmu/omctoolkit.p5p
Note - When the MCMU component is updated, web services are restarted and you might need
to refresh the browser cache (shift-reload) to use the MCMU BUI.
5.
Verify the updated version of MCMU.
% mcmu -V
Oracle MiniCluster Configuration Utility
MCMU v1.1.21.4
6.
(Version dependent) Clear the Apache service.
Only perform this step if you are updating a system that started at version 1.1.21 or lower.
% su - root
# svcadm clear apache22
# exit
%
7.
(Version dependent) Set the Supervisor password.
Only perform this step if you are updating a system that started at version 1.1.18 or lower.
Log into the MCMU BUI as the supervisor. MCMU requires you to set the password for the
supervisor. Until the supervisor password is set, you cannot login to the MCMU as an admin
such as mcinstall. See “Log in to the MCMU BUI” on page 26.
Updating MiniCluster Software (CLI)
301
Update Other MiniCluster Software Components (CLI)
8.
Install the Component Bundle.
The Component Bundle contains important components that need to be updated when the
MCMU component is updated.
If you already installed the Component Bundle, skip this step.
If not, perform this procedure now. See “Install the Component Bundle” on page 165.
Update Other MiniCluster Software Components (CLI)
Use this procedure to update any software component that has an update available, except for
the MCMU component (use “Update the MCMU Component (CLI)” on page 299 instead).
Alternatively, you can perform the same updates using the BUI, which is less prone to human
error. See “Update MiniCluster Software (BUI)” on page 167.
The system can be updated while DB and App VMs are running.
This tables lists mcmu patch syntax for various components.
Note - The components and options differ from version to version. To see the full list of patch
options for your particular version, perform the help command: mcmu patch -p -h.
Component
Syntax
Storage array firmware
mcmu patch -p update_jbod
GI and ACFS in kernel zones
mcmu patch -p update_acfs
OS repository
mcmu patch -p update_repo
(used to install and update VMs and global zones)
Kernel zone OS
mcmu patch -p update_kz
Compute node OS (both nodes)
mcmu patch -p update_gz
Oracle ILOM on the compute nodes
mcmu patch -p update_ilom
(both nodes)
Note - Depending on the POST configuration,
this update can take 40 - 50 minutes to complete.
GI in DB VMs
mcmu patch -p update_gi -z DBgroup_name
Oracle DB home
mcmu patch -p update_oh -z DBgroup_name --oh DBhome_full_path
1.
Ensure that the Patch Bundle is downloaded to MiniCluster.
These procedures must be performed prior to updating the software components:
302
Oracle MiniCluster S7-2 Administration Guide • March 2017
Update Other MiniCluster Software Components (CLI)
a.
Download the Patch Bundle.
See “Check for and Obtain the Latest Updates” on page 162.
b.
Unzip and extract the bundle.
See “Extract the Patch Bundle” on page 164.
2.
Log into the MCMU CLI as a primary admin, such as mcinstall.
See “Log in to the MCMU CLI” on page 29.
3.
Display the help output to see which update options are available on your
system.
% mcmu patch -h
4.
Update one or more components.
Key points:
■
■
■
■
Some component update options can be included on a single command line, separated with
commas.
These component options can only be updated individually (not combined on a command
line): update_gz, update_ilom, and update_omctoolkit
A system reboot (one node at a time) is automatically performed after updating each of
these component options: update_gz and update_ilom
Some component options require additional command line arguments, as shown in the
examples.
Examples:
■
Example of updating the compute node firmware:
% mcmu patch -p update_ilom
■
Example of updating the GI in VM group called mc5dbzg1:
The first command in this example (describe in “List a Summary of All DB VM Groups
(CLI)” on page 188) displays the DB VM group name that is needed for the mcmu patch
command.
% mcmu tenant -G -l
Listing DB VM Group...
Status : Active
Description :
VMgroupName : mc5dbzg1
Updating MiniCluster Software (CLI)
303
Update Other MiniCluster Software Components (CLI)
editable : True
deletable : True
progress : False
VMgroupID : 1
% mcmu patch -p update_oh -z mc5dbzg1
■
Example of updating the DB in VM group called mc5dbzg1 for the DB home at /u01/app/
oracle/product/12.1.0.2/dbhome_1:
The first two commands display the DB VM group name and the full path of the DB home
that are needed for the mcmu patch command. These commands are described in “List a
Summary of All DB VM Groups (CLI)” on page 188 and “List Details for a DB Home
(CLI)” on page 195.
% mcmu tenant -G -l
Listing DB VM Group...
Status : Active
Description :
VMgroupName : mc5dbzg1
editable : True
deletable : True
progress : False
VMgroupID : 1
% mcmu tenant -H -L 2
DB HOME INFORMATION
ID: 2
VM_ID: 2
VMGROUP_ID: 1
DB_HOME: /u01/app/oracle/product/12.1.0/db_12c
VERSION: 12.1.0.2
TYPE: RAC
PATCH: 12.1.0.2.160419
STATUS: Active
% mcmu patch -p update_oh -z mc5dbzg1 --oh /u01/app/oracle/product/12.1.0.2/dbhome_1
■
Example of updating multiple components (GI and OS in the kernel zone, and the storage
array firmware) on one line:
% mcmu patch -p update_acfs,update_kz,update_jbod
5.
304
Consider your next action.
Oracle MiniCluster S7-2 Administration Guide • March 2017
Update Other MiniCluster Software Components (CLI)
To verify the new versions, use one of these procedures:
■
■
“View Software Component Versions (BUI)” on page 160
“View Software Component Versions (CLI)” on page 297
Updating MiniCluster Software (CLI)
305
306
Oracle MiniCluster S7-2 Administration Guide • March 2017
Index
A
accessing
administration resources, 17
MCMU BUI, 26
MCMU CLI, 29
MCMU user registration page, 41
My Oracle Support (BUI), 177
Oracle Engineered Systems Hardware
Manager, 150
the system, 25
adding a DB VM to a group (BUI), 108
adding IP addresses, 56
administering system security (BUI), 143
administration resources, 15, 17
App Virtual Machine Group Profile Summary
page, 119
App Virtual Machine Group Profile tab, 119
App VM
overview, 21
App VM cores, changing, 128
App VM group
configuration parameters, 78
overview, 21
App VM group profile, creating, 121
App VM groups
deleting (BUI), 131, 132
deploying (BUI), 126
viewing, 119
App VMs
configuring (BUI), 119
creation task overview, 120
editing (BUI), 128
planning worksheets, 77
approving
new users (BUI), 43
new users (CLI), 262
ASM redundancy, 66
assigning disk redundancy, 87
B
booting the system, 49
bundles, 162
C
calibrating drives, 174
certificates and ports used by Oracle Engineered
Systems Hardware Manager, 153
changing
App VM cores, 128
DB VM cores, 105
MCMU passwords (CLI), 266
changing passwords
passwords (BUI), 44
character sets, 77
CIS Equivalent security profiles, 66
CLI, using the MCMU, 183
compliance benchmark
configuration information, 56
compliance benchmarks
overview, 143
Component bundle, 162
component passwords for Oracle Engineered Systems
Hardware Manager, 151
configuration parameters
App VM group, 78
DB home, 72
307
Index
DB instance, 73
DB VM group, 65
DB VMs, 69
configuring
App VMs (BUI), 119
DB VMs (BUI), 83
Oracle ASR client (BUI), 179
storage (BUI), 135
container DB, 76
core usage, 54
creating
a DB VM group profile (BUI), 87
App VM group profiles (BUI), 121
DB group (CLI), 229
DB homes (BUI), 99
DB homes (CLI), 234
DB instance (CLI), 236
DB instances (BUI), 101
MCMU users, 41
new users (CLI), 261
D
Database Virtual Machine Group page, 99
Database Virtual Machine Group Profile Summary
page, 83
Database Virtual Machine Group Summary page, 83,
101
DB components, deleting (BUI), 111
DB home
configuration parameters, 72
DB homes
creating (BUI), 99
deleting (BUI), 113
DB instance
configuration parameters, 73
DB instances
deleting (BUI), 111
viewing (BUI), 83
DB instances, creating
creating (BUI), 101
DB VM
overview, 21
308
Oracle MiniCluster S7-2 Administration Guide • March 2017
DB VM cores, changing, 105
DB VM group
configuration parameters, 65
deleting (BUI), 115, 116
deploying (BUI), 96
overview, 21
viewing (BUI), 83
DB VM group profile, creating, 87
DB VMs
adding a DB VM (BUI), 108
configuration parameters, 69
configuring (BUI), 83
creation task overview, 85
editing the group profile (BUI), 105
planning worksheets, 62
defining
App group profiles (BUI), 121
DB group profile (BUI), 87
deleting
a DB VM group (BUI), 115, 116
App VM groups (BUI), 131, 132
App VM groups (CLI), 258, 260
DB components (BUI), 111
DB homes (BUI), 113
DB homes (CLI), 253
DB instances (BUI), 111
DB instances (CLI), 254
DB VM group (CLI), 253
DB VM group profile (CLI), 252
users (CLI), 265
deploying
a DB VM group (BUI), 96
App VM groups (BUI), 126
App VM groups (CLI), 257
Deployment Review page, 96
DISA STIG security profiles, 66
disabling MCMU user accounts, 46
displaying
full help (CLI), 184
MCMU users, 40
MCMU version (BUI), 53
MCMU version (CLI), 188
partial help (CLI), 185
Index
downloads, 162
drives
preparing for removal, 287
reattaching , 290
drives, calibrating, 174
K
E
L
edit user profile (BUI), 47
editing
App VMs (BUI), 128
DB VM group profile (BUI), 105
encryption keys, showing, 275
encryption keystore, backing up, 277
external NFS
adding (BUI), 137
deleting (BUI), 140
F
Factory Reset ISO, 162
G
global zones overview, 19
kernel zone
checking the status of the GI (CLI), 210
kernel zones overview, 19
listing
all instances (CLI), 196
App group profiles (CLI), 197, 200
App VM groups (CLI), 255
DB home details (CLI), 195
DB homes (CLI), 195
DB instance details (CLI), 197
DB VM group details (CLI), 189
DB VM group profile details (CLI), 188
IP and hostname entries (CLI), 202
setup steps (CLI), 221
logging into the
MCMU BUI, 26
MCMU CLI, 29
VM, 30, 31, 33, 35
logging out of the
MCMU BUI, 29
MCMU CLI, 29
VM, 32, 34, 36
H
Home tab, 27, 54
home_ID, determining, 195
hostname, viewing (BUI), 56
I
IDs, VM, 83, 119
import existing instance, 74
initialization steps, reviewing and rerunning, 58
instance name, 77
instance type, 74
instance_ID, determining, 196
IP addresses and hostnames, listing (CLI), 202
IP addresses, viewing and adding (BUI), 56
M
managing
MCMU user accounts (BUI), 37
managing user accounts (CLI), 261
mcinstall user account, 38
MCMU
overview, 15
MCMU BUI
accessing, 26
App Virtual Machine Group Profile Summary
page, 119
App Virtual Machine Group Profile tab, 119
Application Virtual Machine Group Profile
Summary page, 121
309
Index
Application Virtual Machine Group Profile
tab, 126
Current Action Queue page, 60
Database tab, 87
Database Virtual Machine Group page, 99
Database Virtual Machine Group Profile Summary
page, 83, 87
Database Virtual Machine Group Summary
page, 83, 101
Deployment Review page, 96, 126
Home tab, 27, 54
logging into, 26
logging out of, 29
overview, 27
registration page, 41
Software and OS Information page, 54
System Information page, 56
System Setup tab, 58
System Status page, 27, 54
Tasks tab, 60
user approval page, 43
User Input Summary tab, 56
viewing IP address allocations, 56
Viewing running tasks, 60
viewing the version of, 54
Virtual Machine Group Profile tab, 83, 96
Virtual Machine Instances tab, 83, 99, 101
MCMU CLI
accessing, 29
approving new users, 262
backing up the encryption keystore, 277
changing MCMU passwords, 266
checking a kernel zone, 210
creating a DB group, 229
creating a DB homes, 234
creating a DB instance, 236
creating App VM groups, 255
creating new users, 261
deleting a DB home, 253
deleting a DB instance, 254
deleting a DB VM group, 252, 253
deleting App VM groups, 258, 260
deleting users, 265
310
Oracle MiniCluster S7-2 Administration Guide • March 2017
displaying full help, 184
displaying partial help, 185
listing all DB homes, 195
listing all instances, 196
listing App group profiles, 197, 200
listing DB home details, 195
listing DB instance details, 197
listing DB VM group details, 189
listing DB VM group profile details, 188
listing IP and hostname entries, 202
listing setup steps, 221
logging into, 29
logging out of, 29
managing user accounts, 261
patching the system before initial setup, 299
rejecting new users, 263
running setup steps, 223
scheduling a security compliance run, 274
setting SSH Key options, 274
setting up the system, 221
showing encryption keys, 275
showing mctuner status, 294
showing security compliance information, 273
showing the DB GI status, 208
showing the kernel zone GI status, 206
showing the kernel zone status, 209
showing the system status, 205
showing the VM status, 210
starting a kernel zone, 215
starting a VM, 216
starting all VMs in a group, 216
starting the grid infrastructure for application VM
groups, 217
starting the grid infrastructure for the DB VM
group, 217, 218
stopping a DB VM, 219
stopping a kernel zone, 219
stopping all VMs in a group, 219
stopping the grid infrastructure for an application
VM group, 218
toggling shared storage, 260
verifying the system setup, 224
MCMU CLI procedures
Index
displaying the MCMU version, 188
performing, 183
MCMU user accounts, 38
MCMU user accounts (BUI)
managing, 37
MCMU users
approval process, 39
approving, 43
changing passwords, 44
creating, 41
disabling, 46
displaying, 40
rejecting, 43
resetting passwords, 44
MCMU version, displaying, 53
MiniCluster
resources, 15
tuning, 155
updating MCMU software, 159
My Oracle Support, accessing, 177
N
network information (BUI), viewing, 56
new instance, 74
NFS
adding (BUI), 137
deleting (BUI), 140
number of App VMs, 79
number of cores, 70, 81
Number of DB VMs on each node, 67
O
obtaining system information, 53
ORAchk overview, 16
Oracle ASR, configuring, 179
Oracle Database versions, 72
Oracle Engineered Systems Hardware Manager
accessing, 150
account passwords, 152
component passwords, 151
configuring, 149
configuring certificates and ports, 153
overview, 149
starting (services), 178
overview
MCMU, 15
MCMU BUI, 27
MCMU user accounts, 38
ORAchk, 16
Oracle Engineered Systems Hardware
Manager, 149
user approval process, 39
P
password
default for MCMU, 38
policies, 39
passwords
changing, 44
changing (CLI), 266
resetting, 44
Patch Bundle, 162
patching
the system before initial setup, 299
PCI-DSS security profiles, 66
performing
MCMU CLI procedures, 183
readiness checks (BUI), 173
support tasks (BUI), 177
system checks (BUI), 173
PGA memory space, 77
planning for VMs, 61
planning VM configurations, 61
power cycling
the system, 50
primary admin account, 38
privileges, 37
public hostname, 69
R
readiness checks, performing, 173
rejecting
311
Index
MCMU users (BUI), 43
rejecting new users (CLI), 263
resetting
the system, 50
resetting passwords
passwords (BUI), 44
resources for administrators, 17
reviewing initialization steps (BUI), 58
roles for MCMU user accounts, 37
running setup steps (CLI), 223
S
SCAN name, 70
scheduling a security compliance run (CLI), 274
security
administering (BUI), 143
compliance benchmarks, 143
viewing benchmark reports (BUI), 145
viewing information (BUI), 144
security profiles, 66, 80
setting
SSH key options (CLI), 274
setting up the system (CLI), 221
SGA memory space, 77
shared storage, 66, 79
enabling or disabling (BUI), 135
shared storage, selecting, 121
showing
the DB GI status (CLI), 208
the kernel zone GI status (CLI), 206
the kernel zone status (CLI), 209
the security compliance information (CLI), 273
the system status (CLI), 205
the VM status (CLI), 210
showing mctuner status (CLI), 294
shutting down
the system, 50
Software and OS Information page, 54
software for MiniCluster, 15
software versions
updating (BUI), 167
viewing (CLI), 297
312
Oracle MiniCluster S7-2 Administration Guide • March 2017
viewing BUI), 160
software, obtaining the latest versions, 162
software, updating, 159
SSDs, 23
starting
a kernel zone (CLI), 215
a single VM (CLI), 216
all VMs in a group (CLI), 216
grid infrastructure for application VM groups
(CLI), 217
grid infrastructure for the DB VM group
(CLI), 217, 218
the system, 49, 49
stopping
all VMs in a group (CLI), 219
DB VMs (CLI), 219
grid infrastructure for the DB VM group
(CLI), 218
kernel zones (CLI), 219
the system, 49
storage
adding an external NFS (BUI), 137
configuring (BUI), 135
deleting an external NFS (BUI), 140
overview, 23
storage array
configuring additional storage arrays, 284
storage, managing, 279
supervisor account, 38
support tasks, performing, 177
system checks, performing, 173
system information, obtaining, 53
System Setup tab, 58
System Status page, 27, 54
T
Tasks tab, 60
tasks, viewing the status of, 60
template type, 74
tenant admin account, 38
time zone, viewing (BUI), 56
toggling shared storage
Index
App VM groups (CLI), 260
topology, viewing, 174
tuning MiniCluster, 155
U
updating
MCMU software (BUI), 167
updating MCMU software, 159
user accounts, 38
changing, 47
roles, 37
User Input Summary tab, 56
V
verifying the system setup (CLI), 224
version, viewing, 54
versions
viewing (BUI), 160
viewing (CLI), 297
viewing
App VM groups and VMs (BUI), 119
DB VM groups and VMs (BUI), 83
network information (BUI), 56
security benchmark reports (BUI), 145
software versions (BUI), 160
software versions (CLI), 297
system information (BUI), 54
system security information (BUI), 144
the status of running tasks, 60
topology (BUI), 174
Virtual Machine Group Profile tab, 83, 96
Virtual Machine Instances tab, 83, 99, 101
virtual tuning assistant
overview, 155
virtual tuning assistant (CLI), 293
VM
logging into, 30, 31, 33, 35
logging out of, 32, 34, 36
VM configuration planning overview, 61
VM group profile name (APP VMs), 79
VM group profile name (DB VMs), 65
VM groups, overview, 21
VM public hostname, 81
VMgroupID (application), determining, 197, 200
VMgroupID(DB), determining, 188
VMgroupID, determining, 189
VMs
ID, viewing, 83, 119
online status, 54
planning for, 61
W
worksheets
for App VMs, 77
for DB VMs, 62
Z
zones overview, 19
313
314
Oracle MiniCluster S7-2 Administration Guide • March 2017
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising