E57420.pdf

[1] Oracle® Exalogic Runbook for Exalogic Elastic Cloud,

Release 2.0.6.x

E57420-01

September 2014

Oracle Exalogic Runbook for Exalogic Elastic Cloud, Release 2.0.6.x

E57420-01

Copyright © 2014, Oracle and/or its affiliates. All rights reserved.

Primary Author: Albert Leigh

Contributing Author:

Contributor: Bharath K.Reddy, Rachid Benkreira, Andrew Gregory, Mark Mundy, John Bigane, Gavin Parish, Holger Leister, Miguel Angel Lopez, Dev Prabhu, Sachin Pikle, Raja Mukherjee, Eugene Bogaart

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, 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 failsafe, 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 on 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. 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.

iii

Contents

Preface ................................................................................................................................................................ vii

Audience...................................................................................................................................................... viiDocumentation Accessibility .................................................................................................................... viiConventions ................................................................................................................................................ vii1.1 Exalogic Elastic Cloud Software ............................................................................................... 1-11.2 Exalogic System Components ................................................................................................... 1-21.3 Exalogic Networks...................................................................................................................... 1-32.1 IP Addresses of Physical Components .................................................................................... 2-12.2 IP Addresses of Virtual Components ...................................................................................... 2-22.3 System and Cloud Management URLs.................................................................................... 2-23.1 Physical Components ................................................................................................................. 3-13.1.1 Compute Node..................................................................................................................... 3-13.1.1.1 Summary of Compute Node Host Networks.......................................................... 3-33.1.2 Storage Node ........................................................................................................................ 3-33.1.3 InfiniBand Switch ................................................................................................................ 3-43.1.4 Cisco Switch.......................................................................................................................... 3-43.1.5 Power Distribution Unit (PDU) ......................................................................................... 3-43.2 Virtual Servers ............................................................................................................................. 3-43.2.1 Control Stack vServers ........................................................................................................ 3-43.2.2 Guest vServers...................................................................................................................... 3-53.2.3 How to Log in to a vServer ................................................................................................ 3-64.1 Startup and Shutdown Procedures .......................................................................................... 4-14.1.1 Startup Sequence.................................................................................................................. 4-14.1.2 Shutdown Sequence ............................................................................................................ 4-24.1.3 ZFS Storage Appliance Power On and Off Procedure ................................................... 4-34.1.4 Procedures to Start up or Shutdown Exalogic, Control Stack, and Guest vServers .. 4-44.1.4.1 References to Startup and Shutdown Exalogic Machine........................................ 4-44.1.4.2 References to Startup and Shutdown Exalogic Control.......................................... 4-44.1.4.3 References to Startup and Shutdown Guest Virtual Servers ................................. 4-44.2 Management and Monitoring ................................................................................................... 4-44.3 Restrictions and Guidance......................................................................................................... 4-54.3.1 Exalogic and other Engineered Systems .......................................................................... 4-54.3.1.1 Exalogic and Exadata – IB Switches Configuration ................................................ 4-54.3.1.2 Exalogic and SuperCluster .......................................................................................... 4-54.3.1.3 Exalogic and BDA, Exadata/SSC/Expansion Rack ................................................ 4-54.3.2 Storage Considerations ....................................................................................................... 4-6

iv

4.4 Security ......................................................................................................................................... 4-64.4.1 Exalogic Credentials Management.................................................................................... 4-64.4.2 Security and Compliance.................................................................................................... 4-65.1 Post ECU Cloud Administration Tasks ................................................................................... 5-15.2 Consideration for Creating vServers........................................................................................ 5-25.3 How to Customize a Guest vServer ......................................................................................... 5-25.4 How to Create a vServer Template .......................................................................................... 5-36.1 Instrumentation........................................................................................................................... 6-16.2 Auto Service request (ASR) ....................................................................................................... 6-16.3 Lifecycle Management Tools..................................................................................................... 6-26.4 ExaChk.......................................................................................................................................... 6-26.5 ExaLogs ........................................................................................................................................ 6-36.6 Patching........................................................................................................................................ 6-36.6.1 Patching Recommendation ................................................................................................ 6-36.6.2 Patching Considerations..................................................................................................... 6-46.7 Troubleshooting and Action Plan............................................................................................. 6-46.8 Service Requests .......................................................................................................................... 6-49.1 Exalogic Documents ................................................................................................................... 9-19.2 Important MOS Notes ................................................................................................................ 9-19.3 Exalogic Trainings and Certifications ...................................................................................... 9-2

v

List of Figures

1–1 Exalogic Internal and External Networks ............................................................................... 1-42–1 Enterprise Manager Ops Center Login Screen ....................................................................... 2-32–2 Oracle VM Manager Login Screen ........................................................................................... 2-42–3 Storage Browser Login Screen .................................................................................................. 2-42–4 Oracle ILOM Login Screen ........................................................................................................ 2-52–5 Power Distribution Unit............................................................................................................. 2-53–1 Compute Node Access - Management Network.................................................................... 3-23–2 Compute Node Access - InfiniBand Network ........................................................................ 3-23–3 IP Address on EoIB Network .................................................................................................... 3-6

vi

List of Tables

2–1 Exalogic Physical Components ................................................................................................ 2-12–2 Exalogic Control Stack vServers .............................................................................................. 2-22–3 Exalogic Management URLs .................................................................................................... 2-23–1 Compute Node Host’s Networks ............................................................................................ 3-36–1 Exalogic Tools and Features ..................................................................................................... 6-2

vii

Preface

This guide describes how to set up, administer and manage the Oracle Exalogic Elastic Cloud environment.

AudienceThis document is intended for Oracle Exalogic customers who are operators and users of Exalogic machine and cloud administration.

Documentation AccessibilityFor 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 SupportOracle customers 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.

ConventionsThe following text conventions are used in this document:

Convention Meaning

boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

viii

1

Introduction 1-1

1Introduction

[2] This document provides essential information and guidelines to operate and maintain the Exalogic virtualized environment installed with Exalogic Elastic Cloud Software 2.0.6.x version.

As the owner or operator of Exalogic, you must be familiar with the following references:

■ Oracle Exalogic Elastic Cloud Administrator’s Guide at http://docs.oracle.com/cd/E18476_01/doc.220/e25258/toc.htm

■ Oracle Exalogic Elastic Cloud Machine Owner’s Guide at http://docs.oracle.com/cd/E18476_01/doc.220/e18478/toc.htm

■ Oracle Exalogic Elastic Cloud Release Notes at http://docs.oracle.com/cd/E18476_01/doc.220/e18480/toc.htm

This chapter contains the following topics:

■ Section 1.1, "Exalogic Elastic Cloud Software"

■ Section 1.2, "Exalogic System Components"

■ Section 1.3, "Exalogic Networks"

1.1 Exalogic Elastic Cloud SoftwareExalogic Elastic Cloud Software (EECS) is required to operate the Exalogic machine. The principal components of the software include the Exalogic Base Image, Oracle Traffic Director, and Exalogic System Utilities. There are few variations of EECS 2.0.6.x:

■ Exalogic X4-2 machine with fresh install of 2.0.6.1 version and subsequent application of PSUs.

■ Exalogic X3-2 and Exalogic X2-2 machine with fresh install of 2.0.6 version and subsequent application of PSUs.

■ Exalogic X3-2 and Exalogic X2-2 machines that are upgraded from 2.0.1.x and 2.0.4.x to 2.0.6 version, and subsequent application of PSUs.

http://docs.oracle.com/cd/E18476_01/doc.220/e25258/toc.htm




Note: The Exalogic Control vServers are different between freshly installed 2.0.6.x version and upgraded version. For freshly installed 2.0.6.x version, the vServers are named as:

■ Exalogic Control

■ ExalogicControlOpsCenter PC1


When you upgrade from 2.0.4.x to 2.0.6.0, the Exalogic Control vServers are named as:

■ ExalogicControlOVMM



The database, Oracle VM Manager (OVM) and Enterprise Controller are consolidated in a vServer and hence named as ExalogicControlOVMM.

Exalogic System Components

1-2 Oracle Exalogic Runbook for Exalogic Elastic Cloud Software

■ Inter-generational racks that contain Exalogic X4-2, X3-2, and X2-2 compute nodes running 2.0.6 and 2.0.6.1 versions, and subsequent application of PSUs.

Note: Exalogic X4-2 compute nodes are imaged with 2.0.6.1 version base image while Exalogic X3-2 and X2-2 compute nodes are imaged with 2.0.6 version base image.

Use the imageinfo command on the compute nodes to query the details of your Exalogic Base Image.

1.2 Exalogic System ComponentsYou have access to the following Exalogic system components:

■ All physical components

– Compute nodes

– Storage appliance (2 heads and 1 disk-shelf (JBOD))

– InfiniBand (IB) Switches

– Power Distribution Units (PDUs)

– Cisco Ethernet switch

■ All virtual components

– Exalogic Control vServers (EECS 2.0.6.x)

* Enterprise Controller vServer, that hosts the Enterprise Controller, OVM Manager, and database.

* Proxy Controller vServers.

Note: In EECS 2.0.4 and earlier versions, there were five Exalogic Control vServers. In 2.0.6 version, the number of Exalogic Control vServers is consolidated to three.

Exalogic Networks

Introduction 1-3

1.3 Exalogic NetworksThe Exalogic Machine has three distinct networks as shown in Figure 1–1. For more details, refer to “Understanding Exalogic Networks” section in Oracle Exalogic Cloud Administrator’s Guide at http://docs.oracle.com/cd/E18476_01/doc.220/e25258/netw.htm.

■ 1 GbE management network (via the Exalogic’s Cisco switch)

– To access all physical components and ILOMs

– To perform system administration and life cycle management

– Used by the Exalogic Control stack

■ IPoIB networks that are internal to the Exalogic InfiniBand fabric

– To communicate between compute nodes

– To access the internal Oracle ZFS Storage Appliance and other Engineered Systems on the fabric

– To communicate between vServers

– InfiniBand partitions and memberships provide network isolation and security

■ Ethernet-over-InfiniBand (EoIB) Networks

– EoIB External Management Network on a vLAN

– The IP address provided in the ECU spreadsheet

Created by the ECU configuration process

– Used for Cloud Administration via Exalogic Control

– EoIB user access networks on separate vLANs

– Created by the Exalogic Administrator at post-Exalogic installation

– Used to access guest vServers and their application services

http://docs.oracle.com/cd/E18476_01/doc.220/e25258/netw.htm

http://docs.oracle.com/cd/E18476_01/doc.220/e25258/netw.htm

Exalogic Networks


Figure 1–1 Exalogic Internal and External Networks

2

System Information 2-1

2System Information

[3] This chapter describes the system information such as IP addresses, host names and URLs after the initial installation of the Exalogic systems.

The installation and configuration of Exalogic involve connecting the Exalogic rack to the data center network and power grids, and running the Exalogic Configuration Utility (ECU) and the ECU spreadsheet that contains your data center network configuration information. On successful installation of Exalogic and completion of the Exalogic Elastic Cloud software configuration, the installer generates the Exalogic Deployment Summary that contains the system environment information. The summary includes IP addresses, host names, URLs, and pertinent system environment information after the initial installation.

Request your installer to provide a copy of the Deployment Summary in the following directory of the Oracle ZFS Storage Appliance:

/export/common/general/DeploymentSummary


■ Section 2.1, "IP Addresses of Physical Components"

■ Section 2.2, "IP Addresses of Virtual Components"

■ Section 2.3, "System and Cloud Management URLs"

2.1 IP Addresses of Physical ComponentsIn the Physical Network Information section of the Deployment Summary, you can locate the following information (on the 1 GbE management network) listed in Table 2–1. This is the same information provided in the Physical Configuration tab of the ECU spreadsheet.

Table 2–1 Exalogic Physical Components

Component Host NameHost IP Address

ILOM Host Name

ILOM IP Address

Compute Nodes Yes Yes Yes Yes

Storage Nodes Yes Yes Yes Yes

InfiniBand Switches Yes Yes N/A N/A

Cisco Switch Yes Yes N/A N/A

PDUs Yes Yes N/A N/A

IP Addresses of Virtual Components


2.2 IP Addresses of Virtual ComponentsThis section covers only the virtual components pertaining to the Exalogic Control stack for system and cloud administration. In the Virtual Servers section of the Deployment Summary, you can locate the following information as listed in Table 2–2 including the IP addresses for Enterprise Controller (EC) vServer on the EoIB-external-management network and the IP addresses for the Exalogic Control vServers on the 1 GbE management network.

There is difference between freshly installed Exalogic 2.0.6.x version and upgraded environment. In a freshly installed 2.0.6.x version, the Exalogic Control vServers are ECVM, PC1 and PC2. Whereas, in the upgraded environment, it is OVMM, PCI and PC2. In the upgraded environment, the database, Oracle VM Manager and Enterprise Controller are consolidated in a Exalogic Control vServer and hence named as OVMM.

Table 2–2 Exalogic Control Stack vServers

Exalogic Control vServers Host Name

EoIB External Management Network

1 GbE Management Network

ECvServer Yes Yes Yes

PC1 Yes N/A Yes

PC2 Yes N/A Yes

2.3 System and Cloud Management URLsUsing the IP addresses of the physical and virtual components, access the web-based consoles to manage the Exalogic system.

Table 2–3 Exalogic Management URLs

Component URL Comments

EM Ops Center (EMOC)

See Figure 2–1.

https:// <ECVM_IP_ADDRESS>/emoc

Main entry to Exalogic system and cloud administration. Use EC vServer IP address on the EoIB external management network.

OVM Manager (OVMM)

See Figure 2–2.

https:// <ECVM_IP_ADDRESS>:7002/ovm/console

OVM Manager console must be used under the guidance from Oracle Support Services and MOS. It uses the same IP address as EMOC.

ZFS Storage Appliance

See Figure 2–3.

https:// <SN1_IP_ADDRESS >:215

https:// <SN2_IP_ADDRESS >:215

ZFSSA is active or passive and the active head owns the pool (Configuration>Cluster). Use the IP address of the storage head on the 1 GbE management network.

Compute Node ILOM

See Figure 2–4.

https://<CN_ILOM_IP_ADDRESS>

Web-based console for Integrated Lights Out Manager (ILOM). Use the compute node ILOM’s IP address on the 1 GbE management network.

System and Cloud Management URLs


The following figures provide the sample login screen shots of the above services:

Figure 2–1 Enterprise Manager Ops Center Login Screen

Storage Node ILOM

(SN)

See Figure 2–4.

https://<SN_ILOM_IP_ADDRESS>

Same look-and-feel of the login screen as the compute node ILOM. Use the storage head ILOM’s IP address on the 1 GbE management network.

InfiniBand Switches

(IB)

See Figure 2–4.

https://<IBSWITCH_IP_ADDRESS>

Same look-and-feel of the login screen as the compute node ILOM. Use the IB switch’s IP address on the 1 GbE management network.

PDU

See Figure 2–5.

http://<PDU_IP_ADDRESS> Web-based console to monitor PDU. Use PDU’s IP address on the 1 GbE management network.

Table 2–3 (Cont.) Exalogic Management URLs

Component URL Comments



Figure 2–2 Oracle VM Manager Login Screen

Figure 2–3 Storage Browser Login Screen



Figure 2–4 Oracle ILOM Login Screen

Figure 2–5 Power Distribution Unit



3

System Access 3-1

3System Access

[4] This chapter describes how to access the physical and virtual Exalogic components.

To access Exalogic system components, physical or virtual, get the correct IP address on the specific network (for example, 1 GbE management network versus EoIB external management network as described in Section 2.1, "IP Addresses of Physical Components" and Section 2.2, "IP Addresses of Virtual Components") and security credentials (user ID/password). In some cases, you can use the URL associated with the system access as described in Section 2.3, "System and Cloud Management URLs".


■ Section 3.1, "Physical Components"

■ Section 3.2, "Virtual Servers"

3.1 Physical ComponentsAll Exalogic physical system components are accessible from the 1 GbE management network via the Exalogic’s internal Cisco switch. Compute and storage nodes have access to the internal InfiniBand network.

3.1.1 Compute NodeECU configures all compute nodes to be on the 1 GbE management and IPoIB internal networks.

There are two IP addresses associated with each compute node on this network:

■ Host (that is the OVS) also known as NET0, eth-admin, xenbr0, or bond0

$ ssh root@<CN HOST IP Address>

■ Integrated Lights Out Manager (ILOM)

$ ssh root@<CN ILOM IP Address>

Note: From the ILOM prompt, you can access the host console using start, SP, or console command. To return from the host console back to the ILOM prompt, press ESC (, that is the "Esc" and open parenthesis keys in immediate succession.

ILOM also provides web console that can be accessed via the following URL from a browser:

https://<CN ILOM IP Address>

Physical Components


Each compute node has one 1 GbE connection to the Cisco switch (blue CAT-5 cable). With sideband management enabled, the two IP addresses for Host and ILOM are configured on the NET0 port.

Figure 3–1 Compute Node Access - Management Network

Every compute node (and also storage node) has a Host Channel Adapter (HCA) that enables communication on the InfiniBand fabric. The HCA has two ports that are configured as active and stand-by. Each port is connected to a different InfiniBand switch (NM2-GW) within the Exalogic to provide redundancy. The active-standby connections are then created as a bonded interface. On the InfiniBand network, there are multiple partitioned InfiniBand networks for the virtualized environment. The default partition always exists. EoIB networks are provisioned in vServers as required.

Figure 3–2 Compute Node Access - InfiniBand Network

Physical Components

System Access 3-3

3.1.1.1 Summary of Compute Node Host NetworksThese networks are configured by ECU and you must not make any changes.

Table 3–1 Compute Node Host’s Networks

Network Interface Network Name Purpose

xenbr0

(on bond0)

<hostname>-eth-admin To access the compute node host

bond1 IPoIB-default To access the ZFS storage

bond2 IPoIB-admin For all internal communication between the Exalogic Control components

bond3 IPoIB-storage To access the ZFS storage

bond4 IPoIB-virt-admin For EMOC to manage the guest vServers that have been created

bond5 IPoIB-ovm-mgmt For OVM Manager to manage compute nodes in the pools

bond6 IPoIB-vserver-shared-storage For guest vServers to access the ZFS storage

3.1.2 Storage NodeThe Oracle ZFS Storage Appliance has two storage heads. One storage head is Active and the other is Stand-by – configured as an HA Cluster. You cannot configure both the storage nodes in active mode and it is not supported in Exalogic. The access mechanism to a storage node is similar to compute node access. There are two IP addresses associated with each storage head:

■ Host (that is the ZFS appliance shell)

$ ssh root@<SN NET0 IP Address>

■ Integrated Lights Out Manager (ILOM) – provides SSH and HTTP access

$ ssh root@<SN ILOM IP Address>

Additionally, Oracle ZFS Storage Appliance provides web-based management console:

https://<SN01 NET0 IP Address>:215 or https://<SN02 NET0 IP Address>:215

ZFS shares can also be provisioned and accessed via the HTTP or HTTPS protocol:

http://<ACTIVE STORAGE NODE IP Address>/shares/export/…

To mount ZFS shares on compute nodes and vServers, use the appropriate IPoIB address of the ZFS storage. These IPoIB addresses automatically float to the active storage head:

■ IPoIB-default: The default IPoIB network where compute nodes are on.

■ IPoIB-storage: Used by all Exalogic Control vServers and compute nodes to access storage.

■ IPoIB-vserver-shared-storage: Used by any user created guest vServers to access storage.

Virtual Servers


3.1.3 InfiniBand SwitchTo manage the IB switches, login to the IB switch using the IP address on the 1 GbE management network:

$ ssh root@<IB Switch IP Address>

$ ssh ilom-admin@<IB Switch IP Address>

Each IB Switch has a web-based management console. You can access the console via its URL (that is through the fabric monitor):

https://<IB Switch IP Address>/

3.1.4 Cisco SwitchTo manage the Cisco switch, login to the switch using the IP address on the 1 GbE management network:

$ ssh admin@<Cisco Switch IP Address>

3.1.5 Power Distribution Unit (PDU)To manage the PDU, login to the web console using the IP address on the 1 GbE management network. There are two PDUs on an Exalogic, namely PDU-A and PDU-B.

http://<PDU IP Address>

3.2 Virtual ServersIn the current Exalogic Elastic Cloud Software, virtual machines are called virtual servers or vServers. There are 3 Exalogic Control vServers required to perform system and cloud administration functions. They are created during the ECU configuration process.

All user created vServers are based on the Exalogic Guest Base Template (EGBT) or any customized templates that are based upon the supported versions of EGBT.

■ Supported Templates

– EGBT from EECS 2.0.6 and 2.0.4 versions

– Customized templates based on the above EGBT versions including Oracle Application templates from Oracle Technology Network (OTN) (for example, EBS and PeopleSoft VM Templates)

– Templates created from vServers that are at the July 2014 PSU level.

Note: The following templates are not supported on EECS 2.0.6.x:

■ Generic OVM templates

■ EECS 2.0.1 based templates

3.2.1 Control Stack vServersIn EECS 2.0.6.x, Exalogic Control is a built-in management facility that provides virtual Data Center (vDC) management, system management, and monitoring functions. The 3 Exalogic Control vServers are:

■ 1 Exalogic Control vServer (ECVM)

Virtual Servers

System Access 3-5

– 1 GbE management network IP

– 10 GbE EoIB management network IP

■ 2 Proxy Controller vServers

– 1 GbE management network IP

Note: The networks where these vServers can be accessible from are called out in the above list. Use the appropriate IP address in the URL provided in the section Section 2.3, "System and Cloud Management URLs". You can access the vServer consoles from the compute nodes that hosts them. For example, ECVM and PC1VM on CN01, and PC2VM on CN02.

Note: You cannot modify the Exalogic Control vServers.

3.2.2 Guest vServersDepending on the application requirements, you can build guest vServers, and provision compute resources (vCPUs, memory, and disks) and appropriate EoIB (routable) or IPoIB networks (not routable) available to your account. The vServer access varies upon its available networks.

■ EoIB user access networks

– Used for accessing the guest vServer and its application services from the data center network

– One or more of these networks on separate vLANs

– Cannot use the system cloud management network, EoIB-external-management as it is not supported

■ Private vNet

– Created within the account by Cloud User or Admin

– Used for vServer to vServer communications within the account

■ vserver-shared-storage network

– Provision this network to any vServer that needs to access ZFSSA directly (that is the NFS mount of ZFS shares)

– Oracle recommendation is to use NFSv4 instead of NFSv3. See Section 4.3.2, "Storage Considerations" for more information.

■ IPoIB-default (for example, to connect to a DB on an Exadata on the IB fabric or to an Exalytics)

– After the ECU install process, log in as eladmin to EMOC and edit the IP address range for IPoIB-default to reserve necessary number of addresses.

Networks -> IPoIB-default -> Action Pane -> Edit Managed IP Range

– You must also exclude all compute and storage nodes, PC1, PC2 and Exadata or Exalytics consumed IP addresses on IPoIB-default network.

Virtual Servers


3.2.3 How to Log in to a vServerYou must first determine the access of a vServer. For example, you can obtain its IP address on the EoIB user access network from the EMOC Browser User Interface (BUI). In Figure 3–3, it is the EoIB-Public-Client network for the selected vServer.

■ Select vDC Management -> <User Account> -> <vServer Name>.

■ Locate the vServer and click the Network tab in the center pane.

■ Retrieve the IP address on the correct network as highlighted in Figure 3–3.

Figure 3–3 IP Address on EoIB Network

Login using the IP address on the correct network:

$ ssh <user_id>@<VM IP_ADDRESS> or <HOSTNAME>

4

System Administrative Procedures 4-1

4System Administrative Procedures

[5] This chapter provides guidelines for Exalogic system administrative procedures.

Additional information is available in Oracle Exalogic Elastic Cloud Machine Owner’s Guide at http://docs.oracle.com/cd/E18476_01/doc.220/e18478/toc.htm.


■ Section 4.1, "Startup and Shutdown Procedures"

■ Section 4.2, "Management and Monitoring"

■ Section 4.3, "Restrictions and Guidance"

■ Section 4.4, "Security"

4.1 Startup and Shutdown ProceduresIt is important to follow the proper sequence in order to startup and shutdown Exalogic and its components.

■ Section 4.1.1 provides the start up sequence order

■ Section 4.1.2 provides the shutdown sequence order

■ Section 4.1.3 provides the storage appliance power on and off procedure

■ Section 4.1.4 provides additional procedures to start up or shutdown Exalogic, Control stack, and guest vServers

4.1.1 Startup SequenceStartup in the following sequence:

1. Power on the PDUs of the Exalogic rack

2. Network switches


Note: Ensure that the switches have had power applied for a few minutes to complete the power-on configuration before starting the storage nodes and compute nodes.

On the rear side of the InfiniBand Gateway switch (the side on which the InfiniBand cables are plugged in), there are status LEDs. The "OK" LED on the right bottom (above the USB port) must be steady green. This implies that the gateway is functional without any fault.

You can also SSH one of the InfiniBand switches and ensure that ibswitches shows all the InfiniBand Gateway switches.

Startup and Shutdown Procedures


3. Storage nodes

4. Compute nodes

5. Exalogic Control stack vServers and services

6. All guest vServers and user application services

4.1.2 Shutdown SequenceFollow the steps to shutdown:

1. All user application services first

2. All guest vServers

3. All control Stack services

4. Exalogic Control vServers

5. Power off the host (OVS) of all compute nodes

6. Storage nodes

1. First shutdown and power off the standby node

2. Then power off the active storage node

Note: Determine the active Storage.

The following is an example for how to determine the active and standby node via CLI. In this example, SN01 is the active storage node and SN02 is the standby storage node:

el01sn01:> configuration cluster showProperties:state = AKCS_OWNERdescription = Active (takeover completed)peer_asn = 1947f008-dd89-e477-949c-b03ec759f3dbpeer_hostname = el01sn02peer_state = AKCS_STRIPPEDpeer_description = Ready (waiting for failback)

Determining SN02 is the standby storage node:

el01sn02:> configuration cluster showProperties:state = AKCS_STRIPPEDdescription = Ready (waiting for failback)peer_asn = 5d484818-5184-6f17-976c-aab1ec380a31peer_hostname = el01sn01peer_state = AKCS_OWNERpeer_description = Active (takeover completed)

Startup and Shutdown Procedures


7. Network switches

8. PDUs

4.1.3 ZFS Storage Appliance Power On and Off ProcedureTo power off the ZFS appliance, perform the following sequence on the storage nodes:

1. Shutdown and power off the stand-by storage node.

2. Shutdown and power off the active node.

This avoids unnecessary failover of network and storage back and forth.

Power Off:

■ From CLI: > maintenance system poweroff

■ From BUI: Click the Poweroff appliance icon

Power On:

To power on the storage nodes:

■ Push controller power button

■ ILOM: > start /SYS

Note: Do not use the Solaris shutdown command on the ZFS storage nodes to power off as described in Oracle Exalogic Elastic Cloud Machine Owner’s Guide at http://docs.oracle.com/cd/E18476_01/doc.220/e18478/intro.htm#CEGBHCJG.

http://docs.oracle.com/cd/E18476_01/doc.220/e18478/intro.htm#CEGBHCJG


Management and Monitoring


4.1.4 Procedures to Start up or Shutdown Exalogic, Control Stack, and Guest vServers

4.1.4.1 References to Startup and Shutdown Exalogic Machine■ Refer to section "Operational Procedures for Exalogic Machine" in Oracle Exalogic

Elastic Cloud Machine Owner’s Guide at http://docs.oracle.com/cd/E18476_01/doc.220/e18478/intro.htm#CEGBHCJG.

– Non-emergency power procedure

– Emergency power-off considerations

– Cautions and warnings

■ Refer to "Steps To Shut Down or Power Off, and Start Up or Power On an Exalogic Machine (Doc ID 1533391.1)" at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1533391.1

4.1.4.2 References to Startup and Shutdown Exalogic Control■ ExaBR provides convenient way to stop and start the control stack. You must first

install the Exalogic Lifecycle toolkit. Refer to Section 6.3, "Lifecycle Management Tools" for more information.

./exabr stop control-stack

./exabr start control-stack

■ For manual procedure, refer to "How To Stop and Start the Entire Exalogic Control Stack In An Exalogic EECS v2.0.6.0.0 and later Virtual releases (Doc ID 1594223.1)" at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1594223.1

4.1.4.3 References to Startup and Shutdown Guest Virtual Servers■ Always start and stop the guest vServers via Enterprise Manager Ops Center. Use

either the BUI or IaaS CLI as described in Oracle Exalogic Elastic Cloud Administrator’s Guide at http://docs.oracle.com/cd/E18476_01/doc.220/e25258/proc.htm#BABDCBHC.

Note: It is important to start and stop vServers under vDC Management rather than from the Assets accordion in the EMOC UI.

■ Do not use the xm commands.

■ Do not use OS level shutdown command. Otherwise, vServers that are marked HA will be restarted by EMOC automatically.

4.2 Management and MonitoringFor managing the Exalogic Rack, refer to the Oracle Exalogic Elastic Cloud Machine Owner’s Guide at http://docs.oracle.com/cd/E18476_01/doc.220/e18478/toc.htm.

Use the Exalogic Control facility, the EMOC, for all management activities of the Exalogic virtualized environment. EMOC provides management and monitoring capabilities. Refer to the Oracle Exalogic Elastic Cloud Administrator’s Guide at http://docs.oracle.com/cd/E18476_01/doc.220/e25258/toc.htm.

The following MOS notes for Enterprise Manager and Exalogic are available:

http://docs.oracle.com/cd/E18476_01/doc.220/e25258/proc.htm#BABDCBHC

http://docs.oracle.com/cd/E18476_01/doc.220/e25258/proc.htm#BABDCBHC



https://support.oracle.com/epmos/faces/DocumentDisplay?id=1594223.1




Restrictions and Guidance


■ "Exalogic EMCC/EMOC Master Note (Doc ID 1492609.1)" at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1492609.1

■ "How To Monitor Exalogic Virtual Environments through Enterprise Manager Cloud Control (EMCC) (Doc ID 1910452.1)" at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1910452.1

4.3 Restrictions and GuidanceFollow the rules below unless instructed by a qualified Oracle engineer or an official Exalogic MOS note.

■ Ensure that the Oracle ZFS Storage Appliance has one node active and the other node in stand-by mode. The nodes must never be in Active-Active configuration.

■ Do not use the OVM Manager console.

■ Do not use the Xen commands (for example, xm) from OVS.

■ Do not enter the Solaris shell on the Oracle ZFS Storage Appliance.

■ Do not turn on/off services (factory setting) on the storage appliance.

■ Do not manually edit any vm.cfg files that define vServers.

■ Do not turn on the CPU cap feature. See http://docs.oracle.com/cd/E18476_01/doc.220/e25258/advproc.htm#BABCFGHC for more information.

4.3.1 Exalogic and other Engineered SystemsExalogic can be interconnected with other Oracle Engineered systems on the InfiniBand fabric. You must follow the rules as described in this section.

4.3.1.1 Exalogic and Exadata – IB Switches Configuration For a virtualized Exalogic and an Exadata on the same IB fabric, consider the following rules with respect to IB switches:

■ IB firmware on Exalogic IB switches must be greater than or equal to Exadata IB switches

■ SM master must run only on Exalogic NM2-GW switches (EMOC constraint)

■ SM Priority settings on IB switches

SM Priority

High for Exalogic 5

Low for Exadata 2

4.3.1.2 Exalogic and SuperClusterFor Exalogic and SuperCluster specifically, refer to the MOS note "Interconnecting an Oracle SuperCluster and Virtual Exalogic Cloud Machine together over InfiniBand (Doc ID 1598479.1)" at https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?id=1598479.1.

4.3.1.3 Exalogic and BDA, Exadata/SSC/Expansion RackFor Exalogic and BDA, Exadata, SuperCluster, or Expansion Rack, refer to the MOS note “Setting up the subnet manager in a multirack configuration containing



https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?id=1598479.1

http://docs.oracle.com/cd/E18476_01/doc.220/e25258/advproc.htm#BABCFGHC

http://docs.oracle.com/cd/E18476_01/doc.220/e25258/advproc.htm#BABCFGHC

Security


Exalogic/BDA and Exadata/SSC/Expansion Rack (Doc ID 1682501.1)” at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1682501.1.

4.3.2 Storage ConsiderationsThe storage considerations are as follows:

■ Oracle recommends NFS v4 for remote mount of ZFS shares for lock performance. Refer to the section "Configuring NFS Version 4 (NFSv4) on Exalogic” of Oracle Exalogic Elastic Cloud Machine Owner’s Guide at http://docs.oracle.com/cd/E18476_01/doc.220/e18478/nfs.htm.

NFS v3 has locking issues. Refer to the MOS note "Migration from NFSv3 to NFSv4 (Doc ID 457201.1)" at https://support.oracle.com/epmos/faces/DocumentDisplay?id=457201.1 for more information.

■ Provision IPoIB-vserver-shared storage network in guest vServers to mount ZFS shares with NFS v4. Refer to http://docs.oracle.com/cd/E18476_01/doc.220/e18480/eecs.htm#A1093070.

■ vServer volumes are less performant than NFS shares.

NFSv4 requires a name service such as NIS or LDAP.

■ Refer to the MOS Note "Oracle Exalogic Elastic Cloud - Setting Up LDAP Service for NFSv4 (Doc ID 1599868.1)" at https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?id=1599868.1.

Note: This is an internal MOS note. Request the Exalogic Product Management to access the document.

■ Refer to the MOS Note "Configure NIS Master, Slave And Client Configuration In Exalogic Virtual Environment (Doc ID 1516025.1) at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1516025.1.

4.4 SecurityThis section describes about the Exalogic credentials management and compliance.

4.4.1 Exalogic Credentials ManagementTo change the passwords of Exalogic components, use the ExaPasswd tool available in "Exalogic Life Cycle (ELLC) 14.2 Toolkit (Doc ID 1912063.1)" at https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?id=1912063.1.

Additional reference is available for manually changing the passwords in "Oracle Exalogic Elastic Cloud – Credentials Management Guide (Doc ID 1594316.1)" at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1594316.1.

4.4.2 Security and Compliance■ STIG Compliance

To harden guest vServers and physical Oracle Linux nodes on Exalogic, STIGfix tool is available in "Exalogic Life Cycle (ELLC) 14.2 Toolkit (Doc ID 1912063.1)" at https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?id=1912063.1 to make them compliant with STIGs (Security Technical Implementation Guides).


http://docs.oracle.com/cd/E18476_01/doc.220/e18480/eecs.htm#A1093070

http://docs.oracle.com/cd/E18476_01/doc.220/e18480/eecs.htm#A1093070






http://docs.oracle.com/cd/E18476_01/doc.220/e18478/nfs.htm


Security


■ "Security For Oracle Exalogic Elastic Cloud Software (Doc ID 1470903.2)" at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1470903.2.

■ "Exalogic Security White Paper" at http://www.oracle.com/us/products/middleware/exalogic-security-1561688.pdf.

■ "Exalogic and PCI Compliance" at http://www.oracle.com/us/products/middleware/exalogic/exalogic-and-pci-compliance-1859213.pdf.

http://www.oracle.com/us/products/middleware/exalogic-security-1561688.pdf

http://www.oracle.com/us/products/middleware/exalogic-security-1561688.pdf

http://www.oracle.com/us/products/middleware/exalogic/exalogic-and-pci-compliance-1859213.pdf

http://www.oracle.com/us/products/middleware/exalogic/exalogic-and-pci-compliance-1859213.pdf


Security


5

Getting Started With Cloud Administration 5-1

5Getting Started With Cloud Administration

[6] This chapter provides guidelines for getting started with cloud administration.

After Exalogic is configured using ECU, the state of your Exalogic machine is as follows:

■ Compute nodes, switches, and storage appliance configured with network interfaces

■ InfiniBand partitions configured for six networks created by ECU (one EoIB external management network, and five IPoIB administration networks)

■ Default Virtual Data Center (vDC) set up on Exalogic

■ Exalogic Control stack running on the machine


■ Section 5.1, "Post ECU Cloud Administration Tasks"

■ Section 5.2, "Consideration for Creating vServers"

■ Section 5.3, "How to Customize a Guest vServer"

■ Section 5.4, "How to Create a vServer Template"

5.1 Post ECU Cloud Administration TasksAs an Exalogic Administrator, you must set up the system for cloud users.

Note: As part of the Exalogic installation process, the installer is required to validate the newly configured system. Therefore, some of the following steps might have been already executed. For example, EGBT may have been downloaded, imported and registered in Enterprise Manager Ops Center.

Also see Task Overview and Basic Concepts in the Oracle Exalogic Elastic Cloud Administrator’s Guide at http://docs.oracle.com/cd/E18476_01/doc.220/e25258/taskintro.htm. Refer to the Oracle Exalogic Elastic Cloud Administrator’s Guide for the following sections:

■ Create Cloud Admin and Users at http://docs.oracle.com/cd/E18476_01/doc.220/e25258/roles.htm

■ Create User Access EoIB Networks at http://docs.oracle.com/cd/E18476_01/doc.220/e25258/proc.htm

http://docs.oracle.com/cd/E18476_01/doc.220/e25258/taskintro.htm

http://docs.oracle.com/cd/E18476_01/doc.220/e25258/taskintro.htm

http://docs.oracle.com/cd/E18476_01/doc.220/e25258/roles.htm

http://docs.oracle.com/cd/E18476_01/doc.220/e25258/roles.htm

http://docs.oracle.com/cd/E18476_01/doc.220/e25258/proc.htm


Consideration for Creating vServers


■ Create vServer Types at http://docs.oracle.com/cd/E18476_01/doc.220/e25258/proc.htm

■ Create Account (Cloud Resource Quotas/User Assignment/Tenancies) at http://docs.oracle.com/cd/E18476_01/doc.220/e25258/advproc.htm

■ Download EECS 2.0.6 EGBT from http://edelivery.oracle.com

■ Import Server Template at http://docs.oracle.com/cd/E18476_01/doc.220/e25258/app_vdc_cli.htm

■ Create Custom Template at http://docs.oracle.com/cd/E18476_01/doc.220/e25258/appendix.htm

■ Create Private vNets at http://docs.oracle.com/cd/E18476_01/doc.220/e25258/proc.htm#BABEJCJD

■ Create Distribution Groups at http://docs.oracle.com/cd/E18476_01/doc.220/e25258/proc.htm#BABDDFED

■ Create vServers at http://docs.oracle.com/cd/E18476_01/doc.220/e25258/proc.htm#CHDIHDEI

5.2 Consideration for Creating vServersPlan and provision the virtual resources carefully for guest vServers as once you complete creating a vServer, the following attributes of it cannot be changed:

■ CPU

■ Memory

■ Networks

The only way to change these attributes at this point is to:

■ Save the vServer as a template as described in the section Section 5.4, "How to Create a vServer Template".

■ Use the new template to provision a new vServer with required resources (for example, more or less CPUs, memory and networks).

Note: Enterprise Manager Ops Center provides options to change the vServers attributes from the Assets accordion. It is not supported in Exalogic and must not be used to resize the vServers.

A maximum of three storage volumes can be attached to a guest vServer in addition to the built-in disk inherited from the template.

5.3 How to Customize a Guest vServerYou can create a vServer and customize it to meet your application requirements. For example, you can:

■ Install and configure an application in a running vServer and create a template based upon this customization.

■ Add or remove some RPMs. Some RPMs cannot be modified or removed, refer to Oracle Exalogic Elastic Cloud Administrator’s Guide at http://docs.oracle.com/cd/E18476_01/doc.220/e25258/app_vm.htm.



http://docs.oracle.com/cd/E18476_01/doc.220/e25258/advproc.htm

http://edelivery.oracle.com

http://docs.oracle.com/cd/E18476_01/doc.220/e25258/app_vdc_cli.htm

http://docs.oracle.com/cd/E18476_01/doc.220/e25258/app_vdc_cli.htm

http://docs.oracle.com/cd/E18476_01/doc.220/e25258/appendix.htm


http://docs.oracle.com/cd/E18476_01/doc.220/e25258/proc.htm#BABEJCJD

http://docs.oracle.com/cd/E18476_01/doc.220/e25258/proc.htm#BABEJCJD

http://docs.oracle.com/cd/E18476_01/doc.220/e25258/proc.htm#BABDDFED

http://docs.oracle.com/cd/E18476_01/doc.220/e25258/proc.htm#BABDDFED

http://docs.oracle.com/cd/E18476_01/doc.220/e25258/proc.htm#CHDIHDEI

http://docs.oracle.com/cd/E18476_01/doc.220/e25258/proc.htm#CHDIHDEI

http://docs.oracle.com/cd/E18476_01/doc.220/e25258/app_vm.htm

How to Create a vServer Template

Getting Started With Cloud Administration 5-3

■ Update the OS to a newer version of Oracle Linux 5, as described in "Exalogic Virtual Environment - Guest vServer Upgrade to Oracle Linux v5.10 (Doc ID 1594674.1)" at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1594674.1.

■ Add disks or increase storage size.

■ Modify swap space.

All vServers based upon one of the Exalogic Guest Base Templates (EGBT) are listed as follows:

■ EECS 2.0.6 EGBT that has LVM based virtual disk

– In this version, you can also use the following command:

# imagehistory

– The LVM based vServer’s disks can be customized with the procedure given in "Appendix F Managing LVM Partitions on Guest vServers" of Oracle Exalogic Elastic Cloud Administrator’s Guide at http://docs.oracle.com/cd/E18476_01/doc.220/e25258/app_lvm.htm.

– A better alternative is to use the newly available tool called ModifyLVMImg in "Exalogic Life Cycle (ELLC) 14.2 Toolkit (Doc ID 1912063.1)" at https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?id=1912063.1.

■ EECS 2.0.4 EGBT that has static virtual disk

– To verify this version of the template, use the following command:

# cat /usr/lib/init-exalogic-node/.template_version

– The static disk based vServers can be customized (for example, you can add disks, and modify disk or swap size) using the modifyjeos utility as described in "Appendix E Customizing Guest vServer Images" of Oracle Exalogic Elastic Cloud Administrator’s Guide at http://docs.oracle.com/cd/E18476_01/doc.220/e25258/app_vm.htm.

Guest vServers can be also be upgraded to the latest Oracle Linux version as described in Guest vServer Upgrade to Oracle Linux 5.10 (Doc ID 1594674.1) at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1594674.1.

5.4 How to Create a vServer TemplateA supported procedure to create a template from an existing guest vServer is described in the MOS note “Script: To Create a Template from an Existing Guest vServer (Doc ID 1596209.1)" at https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?id=1596209.1.

Note: This MOS note is an updated procedure to the one defined in the "Appendix G Creating Server Templates from vServers” of Oracle Exalogic Elastic Cloud Administrator’s Guide at http://docs.oracle.com/cd/E18476_01/doc.220/e25258/appendix.htm.

http://docs.oracle.com/cd/E18476_01/doc.220/e25258/app_lvm.htm

http://docs.oracle.com/cd/E18476_01/doc.220/e25258/app_lvm.htm










How to Create a vServer Template


6

Maintenance Procedures 6-1

6Maintenance Procedures

[7] This chapter provides guidelines for Exalogic system maintenance procedures.


■ Section 6.1, "Instrumentation"

■ Section 6.2, "Auto Service request (ASR)"

■ Section 6.3, "Lifecycle Management Tools"

■ Section 6.4, "ExaChk"

■ Section 6.5, "ExaLogs"

■ Section 6.6, "Patching"

■ Section 6.7, "Troubleshooting and Action Plan"

■ Section 6.8, "Service Requests"

6.1 InstrumentationInstrumentation refers to tools that help to collect, inform, diagnose, or automate configuration or transactional data.

Refer to "Master Note On Exalogic Instrumentation (ASR, Exachk, Exalogs, ELLC, OCM, OSWatcher, RDA, VMPinfo3) (Doc ID 1506224.1)" at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1506224.1.

6.2 Auto Service request (ASR)Oracle Auto Service Request (ASR) is a feature of Oracle Premier Support for Systems and Oracle/Sun Limited Warranty that is designed to automatically request Oracle service when specific hardware faults occur. ASR is designed to enable faster problem resolution by eliminating the need to initiate contact with Oracle services for hardware failures, reducing both the number of phone calls needed and overall phone time required.

For more information on ASR refer to following documentation links.

■ http://www.oracle.com/technetwork/systems/asr/documentation/asrud-323492.pdf

■ http://www.oracle.com/technetwork/systems/asr/documentation/asr-qualified-exalogic-497964.html


http://www.oracle.com/technetwork/systems/asr/documentation/asrud-323492.pdf



http://www.oracle.com/technetwork/systems/asr/documentation/asr-qualified-exalogic-497964.html

http://www.oracle.com/technetwork/systems/asr/documentation/asr-qualified-exalogic-497964.html

Lifecycle Management Tools


6.3 Lifecycle Management ToolsOracle Exalogic Lifecycle (ELLC) toolkit is a collection of tools that simplify, automate, and standardize lifecycle management on an Oracle Exalogic Elastic Cloud machine.

Refer to the "Exalogic Lifecycle Toolkit 14.2 (Doc ID 1912063.1)" at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1912063.1

The ELLC toolkit currently includes tools for platform patching, backup and recovery, health checks, and diagnostics.

Table 6–1 Exalogic Tools and Features

Exalogic Tools New Features and Enhancements

EMAgent PreSetup A new tool to prepare the Exalogic rack for Enterprise Manager 12c discovery and monitoring.

ExaBR EECS 2.0.4 Support

STIG-hardened Linux Compute Nodes

All-ILOM Target

ExaPatch Improved platform patching

ExaLogs Solaris Support

Credentials (access) option

Network Usage Order

ExaPasswd A new tool to automate password changes to Exalogic system components

STIGfix A new tool to make Exalogic guest vServers and Physical Linux Nodes STIG compliant

ModifyLVMImg A new tool to resize LVM-based vServers (root/swap volumes), and add or remove Linux RPMs

ExaChk Enhanced Exalogic Health Check tool

Support for No DNS

Revised scoring

Diff comparison

6.4 ExaChkExachk is a health-check tool that is designed to audit important configuration settings in an Exalogic machine:

■ Suggestion

– Run every quarter according to the PSU cycle

– Before and after a maintenance

– Attach Exachk report to the Service Request and save time

■ "Exachk Health-Check Tool for Exalogic (Doc ID 1449226.1)" at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1449226.1

■ "Exalogic Exachk Diagnostic Information and Suggested Actions (Doc ID 1463157.1)" at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1463157.1

■ "Exalogic Exachk Health-Check Tool Known Issues (Doc ID 1478378.1)" at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1478378.1





Patching

Maintenance Procedures 6-3

6.5 ExaLogsExaLogs is a command-line tool for gathering logs, diagnostics, environment and configuration information and other data from key components in an Exalogic physical or virtual configuration.

■ It is bundled in the Exalogic Lifecycle Toolkit 14.2 (Doc ID 1912063.1) available at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1912063.1

■ Run ExaLogs before and after patching (PSUs), upgrades, or when a problem arises

■ ExaLogs are required to open up an SR.

6.6 PatchingOracle Elastic Exalogic Cloud Software Recommended Patches are available within My Oracle Support. Exalogic Patch Set Updates (PSU) are a collection of Oracle recommended patches. The PSUs are cumulative and released on quarterly schedule.

6.6.1 Patching RecommendationTo ensure that the Exalogic system continues to perform optimally, Oracle periodically provides comprehensive and well-tested patches to the system as a whole. An Exalogic Patch Set Update (PSU) is released quarterly (January, April, July, and October) with the following features:

■ The PSU is a single download that contains patches for all Exalogic components (firmware, software and OS) as necessary.

■ The PSU is a highly recommended update for all Exalogic customers.

■ In addition to patches or updates for the Exalogic Infrastructure components (on-node components such as Operating System, ILOM, InfiniBand and RAID controller cards, and off-node components such as InfiniBand switches and ZFS Storage Appliance), patches for middleware components (WLS, Coherence, JDK) are also included.

Exalogic customers should ensure that they align their systems with Oracle’s Exalogic releases and recommended patch levels, and should refrain from applying patches which are outside of recommendations for Exalogic. For instance, if a new version of the Oracle ZFS Storage Appliance software is released and is not part of an Exalogic recommended patch or PSU, you must not update the racks with the patch. Applying patches that are not recommended can adversely affect not only the functionality but also the performance of the Exalogic system.

For systems that are in production or in late testing stages before production:

■ Plan to periodically adopt more current patch releases

■ Not required or necessary to install every new patch release

■ A patch should be installed on a production system only after it has been validated in a proper test environment

Systems that are in the early stages of testing before production or proof-of-concept should adopt new releases and patches when they are made available as indicated in the following MOS Note:

■ "Oracle Exalogic Elastic Cloud Supported System Configurations (Doc ID 1368307.1)" available at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1368307.1.



Troubleshooting and Action Plan


■ "Oracle Internal Sun EXALOGIC X2-2 , X3-2 , X4-2 Current Product Patches & Firmware (Doc ID 1432636.1)" available at https://mosemp.us.oracle.com/epmos/faces/DocumentDisplay?id=1432636.1 provides version numbers of all software and firmware components.

6.6.2 Patching ConsiderationsThis section describes the patching considerations.

■ PLATINUM Support

– Oracle Platinum Services helps you maximize the availability and performance of Oracle Engineered systems such as Exalogic with 24/7 remote fault monitoring, industry-leading response times, and patch deployment services at no additional cost.

■ Self-service patching

– Customers should leverage the Platinum Service

■ "Exalogic PSU Master Note (Doc ID 1314535.1)" available at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1314535.1 provides the descriptions of all available patches for the Exalogic platform.

■ ExaPatch is the recommended tool to apply PSUs. Refer to "Exalogic Infrastructure PSU Upgrade - ExaPatch Guide (Doc ID 1568441.1)" available at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1568441.1 for how to run ExaPatch.

6.7 Troubleshooting and Action PlanThe following MOS note provides information on most common Exalogic outages and restoration steps to recover from those outages for Exalogic Platinum customers. Each outage is categorized as either partial or complete outage. The MOS note also provides information about troubleshooting steps to debug the problem and post issue RCA data collection needed for root cause analysis of outage.

"Exalogic Platinum Customer Outage Classifications and Restoration Action Plans (Doc ID 1492461.1)" available at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1492461.1

6.8 Service RequestsTo open SR for Exalogic, refer to "Assistant: My Oracle Support - Service Request (SR) Issues (Doc ID 1600291.2)" available at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1600291.2. Attach ExaLogs, ExaChk reports, and any pertinent information to the SR.






7

Backup and Recovery Procedures 7-1

7Backup and Recovery Procedures

[8] This chapter provides guidelines for Exalogic system backup and recovery procedures.

Recovery Point Objective (RPO) and Recovery Time Objective (RTO) determine the frequency of backups. They are critical factors in an effective business continuity plan. Refer to the following documents:

■ "Backup and Recovery Guide For Exalogic Elastic Cloud Software (Doc ID 1546047.1)" at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1546047.1

■ "Backup and Recovery using ExaBR" at http://docs.oracle.com/cd/E18476_01/doc.220/e36329/toc.htm

■ Oracle Exalogic Elastic Cloud Backup and Recovery Guide Release EL X2-2 and X3-2 (E40226) at http://docs.oracle.com/cd/E18476_01/doc.220/e40226/toc.htm

■ "ZFS Snapshot for Backup and Recovery of the Exalogic Control Repository and Stack" at http://docs.oracle.com/cd/E18476_01/doc.220/e40226/vservers.htm

■ ZFS Snapshots for back up of shares on the ZFS Storage Appliance at http://docs.oracle.com/cd/E27998_01/html/E48433/shares__shares__snapshots.html

– Browser User Interface (BUI)

– Taking manual snapshots (BUI)

– Create a project level snapshot

– Create a share/LUN level snapshot

– Destroying a snapshot (BUI)

– Rolling back to a snapshot (BUI)

– Cloning a snapshot (BUI)

– Scheduled snapshots (BUI)

– Command Line Interface (CLI)

– Listing snapshots (CLI)

– Taking manual snapshots (CLI)

– Renaming a snapshot (CLI)

– Destroying a snapshot (CLI)

– Rolling back to a snapshot (CLI)






http://docs.oracle.com/cd/E18476_01/doc.220/e40226/vservers.htm

http://docs.oracle.com/cd/E27998_01/html/E48433/shares__shares__snapshots.html

http://docs.oracle.com/cd/E27998_01/html/E48433/shares__shares__snapshots.html

7-2 Product Title/BookTitle as a Variable

– Cloning a snapshot (CLI)

– Scheduled snapshots (CLI)

– Setting the scheduled snapshot label (CLI)

8

Disaster Recovery Procedures 8-1

8Disaster Recovery Procedures

[9] This chapter provides guidelines for Exalogic disaster recovery procedures.

Refer to the following documents:

■ "Disaster Recovery for Exalogic" at http://www.oracle.com/technetwork/database/availability/maa-exalogic-dr-401789.pdf

■ "What are the Steps to Configure Reverse Replication for Disaster Recovery on Exalogic (Doc ID 1684964.1)" at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1684964.1

http://www.oracle.com/technetwork/database/availability/maa-exalogic-dr-401789.pdf

http://www.oracle.com/technetwork/database/availability/maa-exalogic-dr-401789.pdf



9

Related Resources 9-1

9Related Resources

[10] This chapter provides related resources for Oracle Exalogic systems.


■ Section 9.1, "Exalogic Documents"

■ Section 9.2, "Important MOS Notes"

■ Section 9.3, "Exalogic Trainings and Certifications"

9.1 Exalogic Documents■ "Oracle Exalogic Document Library" at http://docs.oracle.com/cd/E18476_

01/index.htm

■ "Oracle Exalogic Elastic Cloud Machine Owner's Guide" at http://docs.oracle.com/cd/E18476_01/doc.220/e18478/toc.htm

■ "Oracle Exalogic Elastic Cloud Administrator’s Guide" at http://docs.oracle.com/cd/E18476_01/doc.220/e25258/toc.htm

9.2 Important MOS Notes■ "Master Note for Oracle Exalogic (Doc ID 1301247.1)" at


– "Exalogic FAQs (Doc ID 1374890.1)" at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1374890.1

– "Exalogic Virtualization Release FAQs (Doc ID 1502322.1)" at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1502322.1

– "Exalogic 7320 Storage Appliance FAQs (Doc ID 1511881.1)" at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1511881.1

■ "Oracle Exalogic Elastic Cloud Supported System Configurations (Doc ID 1368307.1)" at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1368307.1

■ "Master Note On Exalogic Instrumentation (ASR, Exachk, Exalogs, ELLC, OCM, OSWatcher, RDA, VMPinfo3) (Doc ID 1506224.1)" at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1506224.1

■ "Exalogic Patch Set Updates (PSU) Master Note (Doc ID 1314535.1)" at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1314535.1

http://docs.oracle.com/cd/E18476_01/index.htm

http://docs.oracle.com/cd/E18476_01/index.htm










Exalogic Trainings and Certifications


■ "Exalogic EMCC/EMOC Master Note (Doc ID 1492609.1)" at https://support.oracle.com/epmos/faces/DocumentDisplay?id=1492609.1

9.3 Exalogic Trainings and Certifications■ "Oracle Exalogic Elastic Cloud 2.x: System Administration" at

http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getCourseDesc?dc=D86356

■ "Oracle Exalogic Elastic Cloud 2.x: Cloud Management" at http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getCourseDesc?dc=D79133

■ "Oracle Exalogic Elastic Cloud 2014 Implementation Specialist Certification" at http://www.oracle.com/partners/en/most-popular-resources/exalogic-elastic-cloud-x3-exam-page-2004915.html

■ "OU Learning Stream's Exalogic topics" at http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=724&get_params=streamId:22,p_searchWords:exalogic,p_pageNumber:1

■ Oracle Learning Library

■ Oracle By Example






http://www.oracle.com/partners/en/most-popular-resources/exalogic-elastic-cloud-x3-exam-page-2004915.html

http://www.oracle.com/partners/en/most-popular-resources/exalogic-elastic-cloud-x3-exam-page-2004915.html

http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=724&get_params=streamId:22,p_searchWords:exalogic,p_pageNumber:1

http://education.oracle.com/pls/web_prod-plq-dad/db_pages.getpage?page_id=724&get_params=streamId:22,p_searchWords:exalogic,p_pageNumber:1