Solaris Handbook

Dutch Bangla Bank Limited

TABLE OF CONTENTS

Document History........................................................................................................................................................5

1|P a g e
 Revision History....................................................................................................................................................... 5
Review..................................................................................................................................................................... 5
ABOUT FZ TECHNOLOGY.............................................................................................................................6
Product Summery........................................................................................................................................................ 7
Training Session:..........................................................................................................................................................9
Product Handover......................................................................................................................................................12
Implementation and Operations Guide:....................................................................................................................15
Introduction....................................................................................................................................................16
PDU IP Address Setup................................................................................................................................................ 18
Connect an Enhanced PDU to a Static IP Address Network Through a SER MGT Port....................................19
Enterprise Manager Ops Center Installation..............................................................................................................20
Get Started with Installation..................................................................................................................................20
Planning the Installation........................................................................................................................................20
Installing and Configuring Oracle Enterprise Manager Ops Center........................................................................21
Introduction to Quick Start....................................................................................................................................22
Getting Ready.........................................................................................................................................................22
What You Need..................................................................................................................................................22
Running the OCDoctor to Identify Prerequisites................................................................................................23
Acquiring the Software.......................................................................................................................................24
Platform-specific software bundles are located on the Oracle Technology Network..........24
Installing and Configuring the Software.................................................................................................................25
Installing the Software...........................................................................................................................................25
Configuring the Software.......................................................................................................................................27
Adding Assets.........................................................................................................................................................33
Add Hardware....................................................................................................................................................34
Add Operating System.......................................................................................................................................36
Viewing Analytics...................................................................................................................................................38
Viewing Services.................................................................................................................................................39
Viewing Thresholds............................................................................................................................................40
Viewing Metrics.................................................................................................................................................41
Monitoring Assets..................................................................................................................................................44
How Monitoring Works......................................................................................................................................44
How to Create an Alert and Incident..................................................................................................................45
How to View and Assign Incidents.....................................................................................................................45

2|P a g e
 Where to Go From Here.........................................................................................................................................46
Related Articles and Resources..............................................................................................................................46
Documentation Accessibility..................................................................................................................................46
Identifying Components:............................................................................................................................................46
Server Front Component:.......................................................................................................................................47
Server Rear Components (SPARC M8-8 and SPARC M7-8 Servers)........................................................................47
CMIOU Chassis Front Components :......................................................................................................................48
CMIOU Chassis Rear Components..........................................................................................................................49
CMIOU Chassis Cooling Zones................................................................................................................................50
Component Fault Tolerances.................................................................................................................................51
SPARC M8 and SPARC M7 Servers Administration Guide..........................................................................................53
Log in to Oracle ILOM.............................................................................................................................................53
To set the locator on or off....................................................................................................................................54
Check faulty from ILOM:........................................................................................................................................54
Get WWN info from LIVE ISO.................................................................................................................................54
..........................................................................................................................................................60
Installing Oracle Solaris 11

How to Change the Time Zone and Locale.............................................................................................................72

General User and root Role................................................................................................................................73
Multipath enable step:.......................................................................................................................................74
Changing the Root Pool Configuration...............................................................................................................74
Configuring the Network:...........................................................................................................................................76
Activate the LDoms Manager and check your factory configuration..................................................................77
Configuring I/O Domains:...........................................................................................................................................77
ISO Mount for Install OS in LDOM or Guest Domain:.............................................................................................81
Dedicated LDOM Creation:........................................................................................................................................83
Creating and Registering a Local Repository..............................................................................................................84
Configuring an IPS local repository.....................................................................................................................84
Getting ready............................................................................................................................................84
Setting Up Local Repository - Solaris 11.4..............................................................................................................84
Preconditions:...........................................................................................................................................85
Step 1: Download the base repository files:..............................................................................................................85
1. First download the repository files and setup the base repository.........................85
Step 2: Setting up the base repository:........................................................................................86

3|P a g e
 Note: Ensure file sol-11_4-repo_digest.txt is available in the same directory. This is required when compering
the checksum of zip files........................................................................................................................................87
Install the repository:.............................................................................................................................................87
Step 3: Applying the support incremental updates....................................................................................................87
Step 4: Install the support updates to the base repository...............................................88
Step 5: Publish the repository locally.............................................................................................88
Step 6: Update the OS to latest patch-set...................................................................................89
Solaris11-How to Manage Boot ENVIRONMENTS?........................................................................90
Updating the Firmware..............................................................................................................................................95
Update the Firmware from Oracle ILOM......................................................................................................96
Update the Server SP or CMM Firmware Image........................................................................................97

4|P a g e
DOCUMENT HISTORY

REVISION HISTORY

Version/Revision Date Author/Modified Brief Description

By of changes
1.0 3rd April 2022 Ashis Chandra Das Initial Draft
2.0 12th April 2022 Ashis Chandra Das OPS center
installation steps
add
3.0 18th April 2022 Mahbub Alam Jewel Addition of Solaris
configuration
4.0 8th May 2022 Ashis Chandra Das Adding rest steps
and Formatting the
Document
5.0 15th May 2022 Asraful Azim Al Final Update &
Khalil review

REVIEW

Sl No Reviewer’s Name Designation Date

1 Md. Mazharul Islam Babu Head of Services 16th May 2022

ABOUT FZ TECHNOLOGY

5|P a g e
F-Z Technologies Limited is a diversified IT solution and service provider company in
Bangladesh. F-Z Technologies are Oracle Gold Partner, Microsoft CSP Partner, DELL, HP,
CISCO, Palo Alto, F5 Inc., Symantec registered partner with a state-of-the-art, ready-made,
enterprise solution for Banks, Non-Banking Financial Institutes (NBFIs), Micro Finance
Institutions (MFIs), Macro-Finance Banks (MFBs), Large Multi-branch retailers, Hospitals,
recruitment Firms, customized solution for Government Projects.

The company has created positive brand image and won a large valued project
(approximately USD 3.5 Million) in 2016, USD 3 Million & USD 6.5 Million Approx. in 2018 &
2019. Moreover, F-Z has been able to keep up the good work and also won the AMC for the
USD 3.5 Million project.

Now, the company is targeting for financial, power and other profitable organizations in the
private and public sector. In next two year, F-Z Technologies limited is targeting to sale
Oracle software, hardware and cloud products to public sector organizations worth of 10
million USD. F-Z Technologies Limited thinks there is abundant opportunity for selling Oracle
Engineered Systems, DELL, HP enterprise servers, Security Products of such OEM (Palo Alto,
F5 and Fortinet) who are the leader or challenger in Gartner and NSS Lab current report,
Identity Management Software and Database software in the public organizations of
Bangladesh since the Government of Bangladesh has taken huge initiatives for achieving
SDG (Sustainable Development Goal) by 2030.

WE ARE THE AUTHORIZED SOLUTIONS PARTNER OF

6|P a g e
 ORGANI ORGANI
LOGO LINK LOGO LINK
ZATION ZATION

www.oracle.c PALOALT www.paloaltone

ORACLE om O tworks.com

www.microsof DELL www.dellemc.co

MICROSO t.com EMC m
FT

F5 www.f5.com VM WARE www.vmware.c

om

HP www8.hp.com WIZERTE www.wizertech.

CH com

CISCO www.cisco.co LEVTECH www.levtechco

m nsulting.com

TECH www.techmah NCINGA www.ncinga.co

MAHINDR indra.com m
A

PRODUCT SUMMERY

PRODUCT SUMMARY
Dutch - Bangla Bank Limited

Head Office: 47, PO Ref.: DBBL/100/55/2021/89

Motijheel Commercial/Area, Dhaka-1000
PO Date: October 06, 2021

Delivery at Dumni, Khilkhet, Dhaka.

Items Product Summary Product Sl. No Qty

Processor: Oracle SPARC M8-8 2141NM2004, 2141NM2005, 2141NM2006, 6

7|P a g e
 Core: 128x6=768
RAM: 768x24= 18,432 GB
Database Server 2141NM2007, 2141NM2008, 2141NM2009
Dual Port 10G (SFP+) Card =6 (with SFP+
Transceiver)
Dual Port 32G HBA Card=6 (with SFP+
Transceiver)
Processor: Oracle SPARC M8-8
Core: 160x4=640
RAM: 640x24= 15,360 GB 2141NM200A, 2141NM200B, 2141NM200C,
Application Server 2141NM200D 4
Dual Port 10G (SFP+) Card =7 (with SFP+
Transceiver)
Dual Port 32G HBA Card=7 (with SFP+
Transceiver)
Processor: Oracle SPARC M8-8
Core: 160x3=480
2141NM2001, 2143NM2001, 2144NM2001
RAM: 480x24= 11,520 GB
UAT Server 3
Quad Port 10G (RJ45) Card =7
Dual Port 32G HBA Card=8 (with SFP+
Transceiver)
465136N+2101092G5G, 465136N+2101092G5P,
465136N+2101092G7E, 465136N+2101092G5F,
465136N+2101092G8H, 465136N+2101092G8M,
Model: Oracle Rack Cabinet 1242 for 465136N+2101092G92, 465136N+2101092G62,
Rack 13
SPARC M8-8 server 465136N+2101092G67, 465136N+2101092G6B,
465136N+2101092G7L, 465136N+2101092G8G,
465136N+2101092G8K

Model: Oracle Server X8-2

Processor: 2 x Intel Xeon Gold 5218
Core: 2x16=32 2142XLB00X, 2142XLB00Y, 2142XLB010
System Monitoring
Memory: 128 GB
Server
HDD: 1.2 TB x 3
Dual Port HBA Card: 02 (Ports: 04)
Dual Port 10G (SFP+) Card: 01 (Ports: 02)

8|P a g e
 TRAINING SESSION:

FZ Technologies are arranged Solaris Training with Oracle partner for Dutch Bangla Bank Engineer’s up
and running faster, increase their knowledge and boost their performance.

9|P a g e
Here is the few moments of Training session.

10 | P a g e
11 | P a g e
 PRODUCT HANDOVER

12 | P a g e
We delivered the products on 15th February 2022 to Dutch Bangla Bank as per direction of the principle
and we have performed a powerup of all of the components which led to the handover process of those
products.
After a good amount of knowledge transfer sessions, we have completed the handover of those products.
Product Delivery Date: 15th, February 2022

13 | P a g e
14 | P a g e
 Oracle Solaris 11
IMPLEMENTATION AND OPERATIONS GUIDE:

INTRODUCTION

15 | P a g e
Oracle Solaris is one of the most widely deployed UNIX-based operating systems in
industries today, perfect for critical environments, high-performance professionals,
and nonstop infrastructures.
This book gives an in-depth coverage on every important feature in the Oracle
Solaris 11 operating system. Starting with how to manage the IPS repository and
make a local repository, you will proceed to create your own IPS package. Then you
will learn about handling boot environments, configuring and managing ZFS
frameworks, and ZFS shadowing. You will cruise ahead to implement I/O domain,
Guest domain and resources proper utilization, create boot environment configure,
automated package installer which is part of the new software deployment
architecture introduced in Oracle Solaris 11.
You will advance through role-based access control (RBAC) and least privileges. You
will then learn how to configure and administer resource manager, and finally you
will be introduced to Oracle Solaris performance tuning.

Preface :

 Purpose
- This document presents methods of building and operating Oracle Solaris11.
 Audience

This book can benefit anyone who wants to learn more about Oracle Solaris 11. It is
written to be particularly accessible to system administrators who are new to Solaris
—
people who are perhaps already serving as administrators of Linux, Windows, or
other
UNIX systems.

- People who have a basic knowledge of Oracle Solaris

- People who are referring to the Oracle Solaris 11 Overview and Design Guide
 Notes
- The contents of this document are based on Oracle Solaris 11.3. For the latest
information on Oracle Solaris 11, see the manuals from Oracle.
⁃ Oracle Solaris 11 Documentation
http://www.oracle.com/technetwork/documentation/solaris-11-192991.html
- Fujitsu M10 is sold as SPARC M10 Systems by Fujitsu in Japan. Fujitsu M10 and
SPARC M10 Systems are identical products.

 Positioning of documents
⁃ Oracle Solaris 11

16 | P a g e
Product Documentation Library

Documentation and resources for this product and related products are available at
http://www. oracle.com/goto/m8/docs and http://www.oracle.com/goto/m7/docs.

Feedback Provide feedback about this documentation at support@fz-

technologies.com

Preface 2/2

Computer virtualization has become a core component of the server industry; many

organizations use virtualization in more than 75% of their servers. The portion of

workloads running in virtual environments has increased in tandem with the

maturity,

number, and flexibility of virtualization options. Further, virtualization has become a

required enabler of cloud computing.

Oracle® Solaris 11 System Virtualization Essentials presents the multiple

technologies that the Oracle Solaris operating system uses to virtualize and
consolidate

computing resources, from hardware partitioning to virtual machines and

hypervisors to

operating system virtualization, commonly called “containers.” The intent of

Oracle®

Solaris 11 System Virtualization Essentials is to discuss computer virtualization in

general and to focus on those system virtualization technologies provided by, or

that

provide support to, the Oracle Solaris operating system. Oracle Solaris 11 supports
a

rich collection of virtualization technologies:

 Physical domains
 Oracle VM Server for SPARC (previously called Logical Domains)
 Oracle VM VirtualBox
 Oracle Solaris Zones (previously called Solaris Containers)

Virtualization offers a tremendous opportunity to add computing workloads while

controlling operational costs and adding computing flexibility. For the system

17 | P a g e
administrator, this new knowledge area requires skills with new technologies such
as

hypervisors, which create virtual machines on a single hardware machine, and

containers (also known as zones), which create virtual operating systems running
on a

single complete operating system.

Oracle® Solaris 11 System Virtualization Essentials describes the factors that affect

your choice of technologies. Along the way, it explains how to achieve the following

goals:

 Use physical domains to maximize workload isolation on Oracle SPARC

systems.
 Use Oracle VM Server for SPARC to deploy different Oracle Solaris 11
environments on SPARC systems.
 Use Oracle VM VirtualBox to develop and test software in heterogeneous
environments.
 Use Oracle Solaris Zones to maximize the efficiency and scalability of
workloads.
 Use Oracle Solaris Zones to migrate Solaris 10 workloads to new hardware
systems.
 Mix virtualization technologies so as to maximize workload density

- The following table lists terms that may be abbreviated.

18 | P a g e
 PDU IP ADDRESS SETUP

Connect an Enhanced PDU to a Static IP Address Network Through a SER MGT Port

1. If you have already connected the PDU's power input leads to the AC power source, disconnect
the power input leads to power off the PDU.
2. Connect an RS-232 cable between the SET MGT port and the host.
3. Connect all the PDU power input leads to the AC power source.
4. Configure the host's terminal or terminal emulator.
5. At the terminal device, log in to the PDU metering unit as admin.
6. After successful login, type.
7. login user: admin
8. password: adm1n
9. set net_ipv4_enable=On
10. set net_ipv4_dhcp=Off
11. pducli -> set net_ipv4_ipaddr=172.31.229.33
12. pducli -> set net_ipv4_subnet=255.255.255.128
13. pducli -> set net_ipv4_gateway=172.31.229.1
14. pducli -> set net_ipv4_dns1=xxx.xxx.xxx.xxx
15. pducli -> set net_ipv4_dns2=xxx.xxx.xxx.xxx
16. pducli -> reset=yes
17. To verify that the settings are correct, connect an Ethernet cable between the NET MGT and the
network.
18. Type the IP address in a browser window.

If the network configuration was successful, the browser displays the Metering Overview page.

19 | P a g e
 19. Click on the Net Configuration link found in the upper left side of the page to view the IP settings.

ENTERPRISE MANAGER OPS CENTER INSTALLATION

20 | P a g e
GET STARTED WITH INSTALLATION

You can install and configure Oracle Enterprise Manager Ops Center.

This chapter includes the following sections:

 Preparing Your Environment: Explains how to prepare an environment for

installation, including planning the installation and verifying that prerequisites
are met.

 Installing with Enterprise Controller High Availability : Explains how to install and
configure an environment with Enterprise Controller High Availability, and how to
install Proxy Controllers as part of the Enterprise Controller configuration.

 Installing with ac Single Enterprise Controller : Explains how to install and

configure a single Enterprise Controller, and how to install Proxy Controllers as
part of the Enterprise Controller configuration.

 Installing Proxy Controllers: Explains how to install additional Proxy Controllers

through the user interface or from the command line.

 Installing the Java Version Manually: Explains how to install the Java version
manually from the command line.

PLANNING THE INSTALLATION

Before you start with the installation procedure, you must perform some of the tasks to
prepare the system for installation.

The following are typical sequences of tasks when installing Oracle Enterprise Manager
Ops Center:

1. Review the system requirements to determine what equipment you need.

2. Prepare a set of systems for software installation, including installing operating

systems and verifying that adequate system resources are available.

3. Install and configure an Enterprise Controller. If you are using a High Availability
configuration, install and configure at least two Enterprise Controller nodes.

4. Install and configure at least one Proxy Controller. This can be the co-located
Proxy Controller, which is installed with the Enterprise Controller.

The first two tasks are described in the Preparing Your Environment chapter. The third
task is discussed in the Installing with Enterprise Controller High Availability and
Installing with a Single Enterprise Controller chapters. The final task is described in the
Installing Proxy Controllers chapter.

21 | P a g e
Figure 1-1 shows the steps involved in an Oracle Enterprise Manager Ops Center
installation.

Figure 1-1 Site Preparation, Installation and Configuration

Description of "Figure 1-1 Site Preparation, Installation and Configuration"

Enterprise Controllers and Proxy Controllers can be installed on Oracle Solaris 10, Oracle
Solaris 11, Oracle Linux, or Red Hat Enterprise Linux.

INSTALLING AND CONFIGURING ORACLE ENTERPRISE MANAGER OPS CENTER

Once you have fully prepared the systems, you install and configure Oracle Enterprise
Manager Ops Center.

An Oracle Enterprise Manager Ops Center installation has three components:

 An Enterprise Controller: The Enterprise Controller directs Oracle Enterprise

Manager Ops Center actions and generates the user interface. If you are using
high availability, you install multiple Enterprise Controllers, but only one is active
at a time.

 One or more Proxy Controllers: Proxy Controllers store Oracle Enterprise Manager
Ops Center data and route jobs to managed systems.

 Agent Controllers for managed systems: Agent Controllers communicate

monitoring data, help run jobs, and enable software update support on managed
systems. Agent Controllers can be installed when a system is discovered and
managed.

You can install and configure Proxy Controllers in one of four ways:

 Configure the co-located Proxy Controller that was automatically installed with
the Enterprise Controller

 Remotely deploy one or more Proxy Controllers as part of the Enterprise

Controller configuration

22 | P a g e
  Remotely deploy one or more Proxy Controllers using the Deploy Proxy Wizard

 Manually install and configure one or more Proxy Controllers

Once the Enterprise Controller and Proxy Controllers are installed and configured,
Oracle Enterprise Manager Ops Center is functional.

INTRODUCTION TO QUICK START

Oracle Enterprise Manager Ops Center is an enterprise-level datacenter automation

software tool. This guide walks you through how to quickly install and configure the
software for a basic monitoring setup. After you configure the software, you can add
assets, view the operating system analytics, monitor assets, and view alerts and
incidents.

This configuration is not practical for larger datacenters, but it does get you started with
the software. You can update or change the configuration at any time to add remote
Proxy Controllers for a larger scale deployment and to enable other features, such as OS
provisioning and updates.

The following topics are covered in this guide:

 Getting Ready

 Installing and Configuring the Software

 Adding Assets

 Viewing Analytics

 Monitoring Assets

 Where to Go From Here

For an overview of the software and features, see the Oracle Enterprise Manager Ops
Center Concepts Guide.

GETTING READY

Many configurations are possible, but we have simplified it for a quick start. This guide
describes how to install and configure an Enterprise Controller with a colocated Proxy
Controller that uses a local database.

This procedure configures the Enterprise Controller to run in disconnected mode. You
can change the connection mode to connect the Enterprise Controller to the Internet
after you configure the software. The Internet connection, either directly or through an
HTTP proxy, provides the most efficient and direct method of obtaining operating
system and software updates. You can also view service requests and configure
automated service requests when you are in connected mode.

23 | P a g e
A lightweight utility, called the OCDoctor, verifies that your system meets the
requirements to successfully install and run the software.

WHAT YOU NEED

You need the following for a simple installation and configuration:

1. A system to run the software:

 SPARC or x86 platform that is running a supported Oracle Solaris or Linux OS,
such as Oracle Solaris 11, Oracle Solaris 10 9/10, or Oracle Linux 5.5.

Note:
To provision and update Oracle Solaris 11 operating systems, Oracle Enterprise
Manager Ops Center must be installed on Oracle Solaris 11.

 87 GB of disk space.

 6 GB Swap Space.

 6 GB Memory.

 Root access.

2. One or more systems to monitor:

 Root access to a SPARC or x86 platform that is running a recent operating

system version, such as Oracle Solaris 10 or 11, or Oracle Linux 5.5.

 A newer Oracle Sun server (at least 2006).

 Enable the SSH services on the OS and know the port number (the default is 22).

3. OCDoctor utility to test for requirements.

See Running the OCDoctor to Identify Prerequisites for where to download the
file.

4. The Oracle Enterprise Manager Ops Center 12c software.

See Acquiring the Software for where to download the software bundle.

5. An e-mail address for a My Oracle Support (MOS) user account. This is needed for
the service request, automated service request, provisioning, and update
features.

6. (Optional) An Internet connection.

24 | P a g e
RUNNING THE OCDOCTOR TO IDENTIFY PREREQUISITES

The OCDoctor quickly identifies potential issues before you download and install the
software. In some cases, it provides a fix. New versions of the OCDoctor are released
regularly. Be sure to get the latest version.

To check the computer compatibility before downloading the software:

1. Go to http://java.net/projects/oc-doctor/downloads and download the

OCDoctor-LATEST.zip file to the /var/tmp/OC directory on the system.

2. Unzip the file and run the utility with the --ec-prereq option.

The utility checks for conditions and returns an OK or Warning.

For example:

# ./OCDoctor.sh --ec-prereq

Ops Center Doctor version 4.11 (Aug 31 2012 [Build 648])

========== Checking Enterprise Controller Requirements ...

====================

OK: Size of Main Memory: 8192 MB

OK: Size of swap space: 8197 MB

OK: Found enough disk space on /var/opt/sun/xvm (114G)

OK: Installed Solaris Package Cluster: SUNWCall

OK: Solaris 10 found

OK: Solaris 10 u9 found

<Output omitted>

3. If you receive any warnings, fix them before installing the software.

For example, a warning appears when you use NIS and you have a groupip 60 in
your NIS group. To temporarily bypass, comment out the NIS entries during the
installation.

passwd: files # nisgroup: files # nis

ACQUIRING THE SOFTWARE

PLATFORM-SPECIFIC SOFTWARE BUNDLES ARE LOCATED ON THE ORACLE
TECHNOLOGY NETWORK.

25 | P a g e
 1. Make a /var/tmp/OC directory on your system.

2. Go to the Oracle Technology

Network http://www.oracle.com/technetwork/indexes/downloads/index.html
. Scroll down to find the link to the Oracle Enterprise Manager Ops Center
Downloads site. Read and accept the license at the top of the page.

3. Download the Enterprise Controller for your OS platform and save the bundle on
the directory you created in step 1.

Description of the illustration download.png

4. Unzip the bundle.

Downloading the Database Installation Bundles

Before you install Oracle Enterprise Manager Ops Center with an embedded database,
you must download the required Oracle Database 11g Enterprise Edition version
11.2.0.3 installation bundles.

Note:
This procedure requires a valid My Oracle Support (MOS) account, which must be associated with a
Customer Service Identifier (CSI) with a software contract.

1. Create a /var/tmp/downloads directory on the Enterprise Controller system.

2. Navigate to http://support.oracle.com , click Sign In, and sign in with your

My Oracle Support (MOS) credentials.

3. Click the Patches & Updates tab.

4. Enter 10404530 in the field next to Patch Name or Number.

5. Click the Add Filter icon, then select your Enterprise Controller system's
operating system and architecture in the drop-down menu next to Platform.

6. Click Search.

26 | P a g e
 The Oracle Database 11g Enterprise Edition version 11.2.0.3 patch set is
displayed.

7. Click Download.

The file download popup is displayed.

8. Download the first two files. These files end with _1of6.zip and _2of6.zip for
Oracle Solaris systems, and end with _1of7.zip and _2of7.zip for Linux systems.

9. Copy or move the downloaded installation bundles to

the /var/tmp/downloads directory on the Enterprise Controller system.

INSTALLING AND CONFIGURING THE SOFTWARE

The software is easy to install, just launch the script. Once installed, open the
application in a browser and answer the configuration questions about how you want to
run the software, then you are ready to start adding assets to monitor.

You are prompted to provide a My Oracle Support (MOS) account during setup. The MOS
account is required to fully enable all capabilities. The account is not required for
installation or basic monitoring. You can provide a MOS account in the UI after the
installation is complete to enable other features.

INSTALLING THE SOFTWARE

1. Go to the /var/tmp/OC/xvmoc_full_bundle directory and run the install script.

# ./install

2. The Oracle Configuration Manager installation starts. Enter a MOS e-mail address
to associate with Oracle Enterprise Manager Ops Center.

27 | P a g e
 Description of the illustration start_install.jpg

3. The installer takes about 15 minutes to run and updates as the steps are
completed, as shown below. When all items are completed, you are prompted to
configure the software.

4. Ops Center Enterprise Controller Installer

5. (version 12.1.2.2140 on SunOS)

6.

7. 1. Check for installation prerequisites. [Completed]

8. 2. Configure file systems. [Completed]

9. 3. Install prerequisite packages. [Not Completed]

10. 4. Install Agent components. [Not Completed]

11. 5. Create Deployable Proxy Bundles. [Not Completed]

12. 6. Install application packages. [Not Completed]

13. 7. Run postinstall tasks. [Not Completed]

14. 8. Install Expect. [Not Completed]

15. 9. Install IPMI tool. [Not Completed]

16. 10. Set database credentials. [Not Completed]

17. 11. Install and configure Oracle Database. [Not Completed]

18. 12. Install Service container components. [Not Completed]

19. 13. Install Core Channel components. [Not Completed]

28 | P a g e
 20. 14. Install Proxy Core components. [Not Completed]

21. ..........................

22. 19. Initialize and start services. [Not Completed]

23. (2 of 19 Completed)

24. Executing current step: Install prerequisite packages...

CONFIGURING THE SOFTWARE

A simple deployment configures the Proxy Controller on the Enterprise Controller

system. This configuration does not set up the image and update libraries or DHCP
services that are required for provisioning and updating your operating systems.

In this procedure, the Enterprise Controller is configured to run in disconnected mode,

which means that it is not connected to the Internet.

1. To log into the software, go to https://<system name>:9443.

2. Enter the system's root user name and password. Select Ops Center local as the
default database source. Click Log In.

Description of the illustration login.png

3. If the Prerequisite Checklist appears, your system might not meet the minimum
requirements.

29 | P a g e
 Description of the illustration prereq_checklist.png

 If the checklist indicates system changes are required, cancel the configuration
and make the suggested changes.

 To continue, click Next.

4. Click Next to accept the following default values on the Enterprise Controller
Setup page:

 EC Name – The default is the system that the Enterprise Controller is installed
on. This name appears in the UI masthead. You can change the name for better
identification.

 Administrative User – Set the currently logged in User as the Administrative

User. This is the only user that the software recognizes until you add other
users. The Administrative User has the Enterprise Controller Admin and All
Assets Admin roles.

 Colocated Proxy – Installs the Proxy Controller on the same system as the
Enterprise Controller.

30 | P a g e
 Description of the illustration ec_setup.png

The Proxy Controller configuration job is launched. Close the window when the
configuration is complete.

5. Verify that the Proxy Controller you installed and configured is online, then
click Next.

31 | P a g e
 Description of the illustration pc_status.png

6. On the Connection Mode page, select the Disconnected Mode option, then
click Next.

Description of the illustration disconnect_mode_setup.png

7. On the Create Software Libraries page, accept the default locations for the
libraries, then click Next to configure the Update libraries.

32 | P a g e
 Description of the illustration config_sw_lib_setup-a.png

The Software Libraries store firmware images, ISO images, and flash archives.
The Linux and Oracle Solaris 8-10 Software Update Library and the Oracle Solaris
11 Software Update Library store the OS images. The Oracle Solaris 11 Software
Update Library is only created when you install the Enterprise Controller on an
Oracle Solaris 11 operating system.

8. The Linux/Oracle Solaris 8-10 Software Bundle page appears, click Next to skip
this step.

9. To perform OS provisioning, you must configure DHCP on the Proxy Controller.

Click Next to skip this step.

33 | P a g e
 Description of the illustration dhcp_config.png

10. Click Finish.

Description of the illustration summary_install_config.png

11. If you are going to manage Oracle Solaris 11 operating systems, upgrade the
Oracle Solaris 11 Agent Controller. See the Oracle Enterprise Manager Ops
Center Administration Guide for how to upgrade the Agent Controller from the UI.

34 | P a g e
Congratulations! You completed the installation and configuration. You can now add
your systems to the UI and begin monitoring them.

ADDING ASSETS

Discovery profiles define the assets that you want to begin managing. The profiles are
based on the type of asset, such as Oracle Solaris operating systems and server
hardware with ILOM service processors.

You need at least two Discovery profiles, one for server hardware and another for
operating systems. You can add the IP ranges and discovery credentials when you
create the profile or when you use the profile to add assets. In this procedure, the
profile does not contain IP addresses or credentials. The details to add specific assets
are supplied when you apply the plan to the targets.

Create at least two Discovery profiles, the first to define the hardware and the other to
define the operating system. Generally, the discovery order does not matter, but a good
practice is to discover the chassis first, then blades, and finally the operating system.

Create Discovery Profiles

1. In Plan Management, scroll down to Profiles and Policies, then click Discovery.

Description of the illustration nav_discover.png

2. Click Create Profile in the Actions pane.

3. Enter a name for the discovery profile. Select the asset type, either the Server
Hardware or the Operating Systems. Expand the asset type to further define
the type. This example is for a system with an ILOM service processor.
Click Next.

35 | P a g e
 Description of the illustration disc_ilom_1.png

4. On the Tags page, click Next to skip adding tags in this procedure.

5. On the IP Ranges page, click Next to skip this step. This information is added
later.

6. On the Discovery Credentials page, click Next to skip this step. This information
is added later.

7. Click Finish to create the profile. The new profile appears in the center pane.

Repeat this procedure until you have at least one service processor-specific
hardware discovery profile and one OS-specific operating system discovery
profile.

ADD HARDWARE

Use the hardware discovery profile that you created earlier to add the hardware to the
UI.

1. Open Assets in the Navigation pane, then click Add Assets in the Actions pane.

36 | P a g e
 Description of the illustration all_assets.png

2. In Add Assets, select the first option to add and manage various types of assets.
Click Next.

Description of the illustration add_assets.png

3. Select the Discovery Profile that you created earlier. When you select the profile,
the page expands to include fields for the host name or IP address and discovery
credentials.

a. Enter the name or IP address of the service processor. You can use a comma
delimited list to add more names or IP addresses.

b. Select Automatic from the Network list.

c. The credentials that you created earlier appear at the bottom of the page. To
change them, click New and complete the Create Credentials page.

d. Click Add Now.

37 | P a g e
 A job is launched to discover and manage the asset. You can use the same
profile to discover other systems with ILOM service processors.

ADD OPERATING SYSTEM

Use the OS discovery profile that you created earlier to add the operating system to the
UI.

1. Open Assets in the Navigation pane, then click Add Assets in the Actions pane.

Description of the illustration all_assets.png

2. Select the first option to add and manage various types of assets. Click Next.

38 | P a g e
 Description of the illustration add_assets.png

3. Select the OS discovery profile that you created. Click Next.

4. Click Next to skip adding tags in this procedure.

5. Do not specify IP addresses now. Click Next.

6. Define the discovery credentials and management option.

 To use previously defined credentials, click Select and choose from the list.

 To create a new set of credentials, click New to launch a pop-up wizard.

Description of the illustration discovercreds.png

 For new credentials, enter a name and description that identifies the credential.
Enter the root user name and password for the system, then click OK to return
to the Discovery Credentials page.

39 | P a g e
 In the Management section of the Discovery Credentials page, select Deploy
Agent Controller to install the Agent Controller on the asset.

Description of the illustration discovercreds.png

A job is launched to discover and manage the asset. When the job completes
successfully, expand Servers in Assets to see the hardware and associated OS.

VIEWING ANALYTICS

The Analytics feature provides details on operating system and zone performance. The
charts, reports, and utilization data provide details of an individual operating system.
You can use the information to improve performance and diagnose issues.

The most robust data is available when the operating system is agent managed. The
Summary provides an overview of CPU, memory, network, and I/O utilization, as shown

40 | P a g e
in Figure 1. Next to the graph is a table of the top five processes, or consumers, for
each type of utilization. You can drill down to view greater details about one of the top
five processes, or you can click the Processes tab to view details or to kill a process.

Figure 1, "OS Analytics Summary Page" shows the OS Analytics Summary page.

Figure 1 OS Analytics Summary Page

Description of "Figure 1 OS Analytics Summary Page"

VIEWING SERVICES

The Services tab provides a view of Oracle Solaris 10 and 11 Service Management
Facility (SMF) services. The Oracle Solaris SMF feature defines the relationships between

41 | P a g e
applications, or services. SMF is a method of managing services by providing a
framework for startup scripts, init run levels, and configuration files. Each service is
identified by a Fault Managed Resource Identifier (FMRI).

The Services tab contains SMF service instances, state, dependencies, and severity
information. You can drill down to see specific service details, including the
configuration, dependencies, and the processes that are in the service contract.

You can perform the following actions in the Services tab:

 View a list of services currently installed and their states

 View a list of dependencies and dependents for FMRI

 View the relationship between services and processes

 View details about why a service is not available

 Obtain logs for debugging

 Clear faults for FMRI

 Invoke the disable, enable, and restart actions on FMRI

 Read configuration files

Services information is available for agent managed and agentlessly managed Oracle
Solaris 10 and 11 operating systems, including global and non-global zones.

VIEWING THRESHOLDS

The Thresholds tab contains information about all of the monitored attributes for the
selected operating system. Monitored attributes include per-instance attributes, such as
File System Usage for each file-system on the asset. Figure 2 shows a partial list of the
monitored attributes available for display.

Figure 2, "CPU Usage" shows the CPU usage view.

Figure 2 CPU Usage

42 | P a g e
 Description of "Figure 2 CPU Usage"

Charts for the historical data of those attributes show the alert monitor threshold levels,
when configured, for that attribute. Figure 3 shows the chart for the System Load
Average - 15 minutes. The time frame selected is Live. Beneath the chart are the
severity levels for this monitored attribute (SystemLoad.average15MinutePerCpuCore),
the operator, and the threshold values. Instead of editing the thresholds in the
Monitoring tab, you can change the values on this page. You can either add values in
the New Value column or click Suggest Thresholds to auto populate the fields with
suggested values. Click Apply Thresholds to change the existing thresholds.

Figure 3, "Thresholds" shows the Thresholds view.

Note:
When the threshold monitor is modified, the asset is removed from the default monitoring profile and
a custom profile created.

Figure 3 Thresholds

43 | P a g e
Description of "Figure 3 Thresholds"

VIEWING METRICS

The Metrics tab provides you with specific details about various operating system
elements, such as the percentage of memory used, and view graphs. When monitoring
thresholds are enabled for an element, you can reset the thresholds.

Click the Metrics tab to see OS-specific components. The following list are the types of
component details available for an agent-managed Oracle Solaris OS:

 Load

 File Systems

 Networks

 Users

44 | P a g e
  Buffer Activity

 Disk Usage

 Paging Activity

 Message Activity

 Tables Status

 TTY Activity

 Kernel Memory

 DNLC

 IPC Message Queue

 IPC Shared Memory

 IPC Semaphore Usage

 CPU Detail

 File Access

 Disk Errors

 Memory Utilization

Expand a component to view the available elements. Click an element to view the
details. In Figure 4, the Load component is expanded and the elements, such as
percentage of memory used, CPU utilization percentage, CPU core count, and system
uptime options are available in the Load list. Memory Used % is selected and the details
and a graph are visible.

Figure 4, "Component Navigation" shows the Component Navigation view.

Figure 4 Component Navigation

45 | P a g e
Description of "Figure 4 Component Navigation"

The type of resource determines the available details. Figure 5 is an example of the
details and graph for the Memory Used % element. This example shows a system in
trouble. The Details shows the last known value memory usage at 95.59111 percent
and the established monitoring parameters. A warning incident is generated at 80
percent and a critical incident is generated when the used memory reaches 95 percent.

View the bar graph to see how the memory usage has trended over the selected time
period. The yellow and red horizontal lines indicate the warning and critical thresholds.

Figure 5, "Memory Used % Details and Graph" shows the Memory Used Percentage
Details and Graph.

Figure 5 Memory Used % Details and Graph

46 | P a g e
Description of "Figure 5 Memory Used % Details and Graph"

The wrench icon appears above the graph. For this graph, click the icon to change the
graph style to line, bar, or area. You can change the definition of the X axis from 1 day

47 | P a g e
to 1 hour, 5 days, 3 weeks, 6 weeks, or 6 months. The export icon enables you to export
the graph to file in CSV or XML format.

You have the opportunity to reset the threshold values for the monitoring rule from this
page, or to view recommended threshold values based on past performance. When you
click the Set Thresholds button, you can modify the monitoring rule for this operating
system. Doing this creates a custom set of monitoring rules for the asset.
See Monitoring Rules and Policies for more information about editing individual
monitoring rule parameters and creating a custom monitoring policy.
MONITORING ASSETS

The software has a set of default monitoring rules for many types of assets. When you
discover and manage an asset, such as an operating system, the software begins
monitoring the status based on the default rules.

HOW MONITORING WORKS

Many assets have a default monitoring profile. Different types of monitoring profiles are
available, depending on the asset type. Some profiles contain individual monitoring
rules, thresholds and alert levels. These alert levels are editable for Critical, Warning,
and Informational incident notification. Some profiles, such as system-defined rules, are
not editable but you can disable them. You can customize the alerts and monitoring
profiles for each asset or group of assets.

To view or edit the default monitoring rules for an asset, click a managed asset in the
navigation tree, then click the Monitoring tab in the center pane.

Description of the illustration monitoring.png

48 | P a g e
The icons at the top of the center pane enable you to add, edit, enable, disable, or
delete rules.

When an asset first meets or exceeds a monitoring threshold or state, an alert and an
incident are generated. Subsequent alerts are aggregated under the existing incident.

HOW TO CREATE AN ALERT AND INCIDENT

An easy way to generate an alert and incident is to shutdown a monitored system. The
shutdown generates a critical status alert. The System Down incident appears in the
Message Center.

HOW TO VIEW AND ASSIGN INCIDENTS

You can see the incidents that are unassigned, assigned to you, and assigned to others
the Message Center.

Description of the illustration message_center_1.png

Details appear in the center pane. The details include a bar chart, a list of incidents by
category and severity, and a detailed list of the individual incidents.

49 | P a g e
Description of the illustration message_center.png

You can also see incidents and the associated alerts for each asset in the Incidents tab.

WHERE TO GO FROM HERE

The initial setup uses a disconnected mode without registering your MOS account and
without creating the software libraries. You can edit the configuration at any time to
change the connection mode, create the DHCP and software libraries, and register a My
Oracle Support (MOS) account. You must register your MOS account and create the
software libraries before you can use the Service Request, Automated Service Request,
provisioning, and update features.

What You'll Need When the Enterprise Controller is on Oracle Solaris 11

When you have the Enterprise Controller installed on an Oracle Solaris 11, you might
need the following:

 If you use an HTTP proxy to connect to the Internet, you must set
the http_proxy and https_proxy environment variables to specify the proxy
server to use.

50 | P a g e
  The location of the key and certificate files for Oracle Solaris 11. If you do not
have key and certificate files, go to https://pkg-register.oracle.com/ and
log in using your MOS credentials to download them.
RELATED ARTICLES AND RESOURCES

The documentation is available at http://www.oracle.com/pls/topic/lookup?

ctx=oc121.

See the platform-specific Installation Guide for a more complex installation.

See end-to-end examples at http://docs.oracle.com/cd/E27363_01/nav/howto.htm.

See the Oracle Enterprise Manager Ops Center Concepts Guide for an introduction to
the product and an overview of the features. See the Oracle Enterprise Manager Ops
Center Feature Reference Guide for more information about the features.

See the Oracle Enterprise Manager Ops Center Administration Guide for details about
connection modes and editing authentications to add a MOS user account.

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

IDENTIFYING COMPONENTS:

SERVER FRONT COMPONENT:

SERVER REAR COMPONENTS (SPARC M8-8 AND SPARC M7-8 SERVERS)

51 | P a g e
CMIOU CHASSIS FRONT COMPONENTS :

Access these components from the front of the server. These components are not part of the chassis. You must
remove these components to access the chassis

52 | P a g e
CMIOU CHASSIS REAR COMPONENTS

Access these components from the rear of the server. These components are not part of the chassis. You must
remove these components to access the chassis

53 | P a g e
1. Rear indicator panel (1) This component is part of the power module.

■ Bottom CMIOU chassis: ROPNL0

■ Top CMIOU chassis: ROPNL2

2. AC inputs (1 strip, 6 outlets per CMIOU chassis) This component is part of the power module.

■ Bottom CMIOU chassis, top to bottom: AC5–AC0 ■ Top CMIOU chassis, top to bottom: AC15–AC10

3. CMIOUs (8)

■ Bottom CMIOU chassis, top to bottom: CMIOU_7–CMIOU_0

■ Top CMIOU chassis, top to bottom: CMIOU_15–CMIOU_8

4. PCIe x16 carriers (up to 24 cards per CMIOU chassis)

5. SPs (2), bottom CMIOU chassis, left to right (SPARC M8-8 and SPARC M7-8 servers): SP0,SP1 SPPs (4, SPARC M7-
16 server):

■ Bottom CMIOU chassis, left to right: SPP0,SPP1

■ Top CMIOU chassis, left to right: SPP2,SPP3

6. PDECBs (8)

■ Bottom CMIOU chassis, top to bottom: PDECB7–PDECB0

■ Top CMIOU chassis, top to bottom: PDECB21–PDECB14

7 SP tray (1)

CMIOU CHASSIS COOLING ZONES

The CMIOU chassis has two cooling zones. In one cooling zone, eight fan modules push air through the CMIOUs
from the front of the server and exhaust it at the rear of the server. In the other cooling zone, six fan modules push
air through the power supplies and exhaust it through the chimney to the SPs and directly out the rear of the
chassis.

54 | P a g e
COMPONENT FAULT TOLERANCES

This topic describes the level of fault tolerance for specific components and provides guidelines for replacing these
components when a fault occurs.

■ CMIOUs. Remove a faulty CMIOU only when a replacement CMIOU is available. Install the new CMIOU as quickly
as possible, within 10 minutes, if possible. You must prepare a CMIOU before removing it from the server.

■ DIMMs. If a DIMM is diagnosed to be faulty while the system is running, the memory will dynamically switch
from 16-way to 15-way interleave by distributing the contents of the faulty DIMM into the other 15 DIMMs

■ Fan modules (CMIOU chassis). The CMIOU chassis has eight fan modules. The server will continue to operate at
full capacity with seven fan modules installed in the CMIOU chassis. The server will not operate with fewer than

55 | P a g e
seven fans. If the server is operating with seven fan modules and one or more of those fans fails, the server might
power down to keep from overheating.

■ Fan modules (switch chassis). The switch chassis has 36 fan modules. Each switch unit has six dedicated fan
modules. The server will continue to operate at full capacity with five of the six fans operating for each switch unit.
If one of the five operating fans fails, the server might power down to keep from overheating.

■ PCIe cards. If the PCIe card is assigned to an I/O domain on a logical domain, you must prepare the card for
removal to avoid a configuration that is unsupported.

■ Power supplies. The power supplies for the CMIOU and switch chassis are 2N redundant. If a power supply fails
in either a switch or CMIOU chassis, the server can operate normally with only three power supplies in the switch
chassis or five power supplies in the CMIOU chassis. There are no restrictions into which slots the power supplies
have to be installed. You can install them in any of the power supply slots as long as all power supplies are
installed.

■ SPs. Replace one SP in the server at a time. You must prepare an SP before removing it from the server.

■ Switch units. Switch units are configured to work together as a single unit. If a switch unit fails, the server will
operate in degraded mode. At least five switch units must be functioning for the server to operate. You must
prepare a switch unit before removing it from the server

Front Indicator Panel Controls and LEDs

On SPARC M8-8 and SPARC M7-8 servers, the front indicator panel is located on the CMIOU chassis. On the SPARC
M7-16 server, the front indicator panel is located on the switch chassis.

56 | P a g e
SPARC M8 AND SPARC M7 SERVERS ADMINISTRATION GUIDE

LOG IN TO ORACLE ILOM

-> start /SP/console -- start the SP-console

-> show /SP/sessions -- see the currently active sessions
-> stop /SP/console -- to stop any user session

57 | P a g e
TO SET THE LOCATOR ON OR OFF

set /SYS LOCATE=on

set /SP/network/ACTIVE_SP/ pendingipaddress=172.31.237.205
set /SP/network/SP0/ pendingipaddress=172.31.237.182
set /SP/network/SP1/ pendingipaddress=172.31.237.183
set /SP/network/HOST0/ pendingipaddress=172.31.237.180
set /SP/network pendingipgateway=172.31.237.1
set /SP/network pendingipnetmask=255.255.255.0
set /SP/network commitpending=true

CHECK FAULTY FROM ILOM:

At the Oracle ILOM prompt start the fault management shell, and then
type fmadm faulty.

-> start /SP/faultmgmt/shell

Are you sure you want to start /SP/faultmgmt/shell (y/n)? y
faultmgmtsp> fmadm faulty

GET WWN INFO FROM LIVE ISO

1: stop automatic boot from active sp

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

2: go to host mode from sp

start -f /HOST0/console

58 | P a g e
3: Load live iso image from ILOM remote console

Please login ilom IP (user:root password:changeme)

change to domain mode

go to remote control

select redirection

launch serial redirection

preference add Imageconnect

59 | P a g e
60 | P a g e
61 | P a g e
4.reset-all from ok prompt

5.boot rcdrom -v

6.login using user:jack/ Password:jack

7. su -

pass: solaris

8. prtdiag -v ( all info hardware)

9.Find the device path and wwn from live image

prtpicl -v -c scsi-fcp|egrep '(port-wwn|devfs-path)'

prtconf -vc /devices/scsi_vhci |grep dev_link.*s2

10. alternate way to discover wwn

fcinfo hba-port | grep -i wwn

11. reboot

12. probe-scsi-all ( scan for new luns)

LUN ID will show with details ID .

13. reset-all

14. load os image from ilom-> domain 0

boot rcdrom -v

62 | P a g e
63 | P a g e
 INSTALLING ORACLE SOLARIS 11

This chapter describes the procedure for installing Solaris 11 (solaris-large server

64 | P a g e
group package) by performing a text install (interactive).

Flow of Installing Oracle Solaris 11

 Installation method and settings presented in this document

- The installation method is text install from OS media (DVDs).
- The disk label at installation is the SMI label.

 Text install

(1) Configure the installation environment.

(2) Select a disk detection method.
(3) Select a disk for installation.
(4) Select a slice for installation.
(5) Enter a host name.
(6) Set network information.
(7) Select a name service.
(8) Select a time zone.
(9) Select a locale.
(10) Set the root password and user account.
(11) Set support information.
(12) Start installation.

Text Install 1/12 - Configure the Installation Environment –

65 | P a g e
Text Install 2/12 - Select a Disk Detection Method

 Select a detection method for disks for installing Solaris 11.

* This new item has been supported since Solaris 11.1.

66 | P a g e
Text Install 3/12 - Select a Disk for Installation -
 Select a disk for installing Solaris

67 | P a g e
Text Install 4/12 – Select a Slice for Installation –

Select a slice for installing Solaris 11

68 | P a g e
Text Install 5/12 – Enter a Host Name -
 Enter a host name to identify the host on the network.

69 | P a g e
Text Install 6/12 - Set Network Information

Select a method (Automatically, Manually, etc.) for configuring the network.

* When manually setting the information, enter an IP address, subnet mask, etc.

Text Install 7/12 - Select a Name Service

 Select the name service to use.

70 | P a g e
Text Install 8/12 – Select a Time Zone -
 Select a time zone (region/country).

71 | P a g e
Text Install 9/12 – Select a Locale –

 Select a locale (character code).

72 | P a g e
Text Install 10/12 – Set the root Password -

73 | P a g e
74 | P a g e
Text Install 11/12 - Set Support Information -

 Set Email (optional) and My Oracle Support (optional).

* This new item has been supported since Solaris 11.1.

75 | P a g e
 Text Install 12/12 – Install -

 Install Solaris 11.

HOW TO CHANGE THE TIME ZONE AND LOCALE

76 | P a g e
- In Solaris 11, you can change the time zone and locale in the SMF service property
settings.
The /etc/default/init file will reflect the set values at the reload timing of the SMF
service.
* You cannot edit the conventional /etc/default/init file.

GENERAL USER AND ROOT ROLE

 Role assignment to a general user
- You will need to assign, in advance, the root role to the general users authorized
to accept
the role.

77 | P a g e
==================================================
============================

MULTIPATH ENABLE STEP:

stmsboot -e ( it will reboot the OS)

CHANGING THE ROOT POOL CONFIGURATION

Overview of Changing the Root Pool Configuration
 What is a root pool?
- The area where the Solaris 11 OS is installed is called the "root pool" (rpool).
- Root pool mirroring (disk redundancy) must be configured manually.

 Adding a mirror disk

- Root pool mirroring is accomplished using the ZFS function.
- Add a disk to the root pool to change to a mirror configuration.

3 Mirroring : Prepare the second disk to attach to the root pool as follows:

78 | P a g e
rpool attach -f rpool <olddisk> <newdisk>

Adding a Mirror Disk

 Add one physical disk to change the root pool to a dual-mirror configuration

zpool attach -f rpool c0t60060E802252FD00504152FD00006000d0

c0t60060E802252FC00504152FC00007000d0

if you want to boot with 2nd disk, please find bootpath for 2nd disk and GO OBP boot
and run

boot -v /pci@315/pci@1/SUNW,qlc@0,1/fp@0,0/disk@w50060e802252fd30,2:a

CONFIGURING THE NETWORK:

79 | P a g e
 ----------------IPMP ---------------

# dladm show-phys
LINK MEDIA STATE SPEED DUPLEX DEVICE
net1 Ethernet unknown 0 unknown bge1
net0 Ethernet up 1000 full bge0
net2 Ethernet unknown 1000 full e1000g0
net3 Ethernet unknown 1000 full e1000g1

# ipadm create-ip net0

# ipadm create-ip net4
#ipadm create-ipmp ipmp0
# ipadm add-ipmp -i net0 -i net4 -i ipmp0
# ipadm create-addr -T static -a X.X.X.X/24 ipmp0/v4add1
#ipadm set-ifprop -p standby=on -m ip net4
# ipmpstat -g

## AGGRIGATION WITH VLAN TAG

ipadm create-ip net0

ipadm create-ip net3
dladm create-aggr -L active -l net0 -l net3 aggr1
dladm create-vlan -l aggr1 -v 337 ctlo
ipadm create-ip ctl0
ipadm create-addr -T static -a 10.0.0.1/27 ctl0/v4
#route add -p default GWip

80 | P a g e
ACTIVATE THE LDOMS MANAGER AND CHECK YOUR FACTORY CONFIGURATION.
# svcadm enable ldmd
Check the required services are online
# svcs -a | grep -i ldom
Example output for a T5220 with 4GB RAM:
# svcadm enable ldmd
# svcs -a|grep -i ldom
online Feb_01 svc:/ldoms/ldmd:default
online Feb_02 svc:/ldoms/vntsd:default
ldm start-reconf primary
ldm list
ldm add-vds primary-vds0 primary
svcadm enable vntsd
Telnet port need to be allow ::

ldm add-vcc port-range=5000-5100 primary-vcc0 primary

ldm add-vsw net-dev=net0 pri-service-vsw0 primary
ldm set-vcpu 8 primary
or
ldm set-core 1 primary
ldm set-memory 2G primary
ldm add-config initial
ldm list-config
shutdown -y -i6 -g0

CONFIGURING I/O DOMAINS:

### We will remove bus from primary to set secondary or I/O domain::

root@coreuatctrld:~# ldm ls-io

NAME TYPE BUS DOMAIN STATUS

---- ---- --- ------ ------

/SYS/CMIOU0/IOH/IOS0 BUS pci_0 primary IOV

/SYS/CMIOU0/IOH/IOS1 BUS pci_1 primary IOV

81 | P a g e
/SYS/CMIOU0/IOH/IOS2 BUS pci_2 primary IOV
/SYS/CMIOU0/IOH/IOS3 BUS pci_3 primary IOV
/SYS/CMIOU0/IOH/IOS4 BUS pci_4 primary IOV
/SYS/CMIOU1/IOH/IOS0 BUS pci_5
/SYS/CMIOU1/IOH/IOS1 BUS pci_6
/SYS/CMIOU1/IOH/IOS2 BUS pci_7 primary IOV
/SYS/CMIOU1/IOH/IOS3 BUS pci_8 primary IOV
/SYS/CMIOU1/IOH/IOS4 BUS pci_9 primary IOV
/SYS/CMIOU2/IOH/IOS0 BUS pci_10 primary IOV
/SYS/CMIOU2/IOH/IOS1 BUS pci_11 primary IOV
/SYS/CMIOU2/IOH/IOS2 BUS pci_12 primary IOV
/SYS/CMIOU2/IOH/IOS3 BUS pci_13 primary IOV
/SYS/CMIOU3/IOH/IOS0 BUS pci_15 primary IOV
/SYS/CMIOU3/IOH/IOS1 BUS pci_16 primary IOV
/SYS/CMIOU3/IOH/IOS2 BUS pci_17 primary IOV
/SYS/CMIOU3/IOH/IOS3 BUS pci_18 primary IOV

/SYS/CMIOU4/IOH/IOS0 BUS pci_20 primary IOV

/SYS/CMIOU4/IOH/IOS1 BUS pci_21 primary IOV
/SYS/CMIOU4/IOH/IOS2 BUS pci_22 primary IOV
/SYS/CMIOU4/IOH/IOS3 BUS pci_23 primary IOV
/SYS/CMIOU0/PCIE2 PCIE pci_0 primary OCC
/SYS/CMIOU0/PCIE3 PCIE pci_1 primary OCC
/SYS/CMIOU0/PCIE1 PCIE pci_3 primary OCC
/SYS/CMIOU1/PCIE2 PCIE pci_5 UNK
/SYS/CMIOU1/PCIE3 PCIE pci_6 UNK
/SYS/CMIOU1/PCIE1 PCIE pci_8 primary OCC
/SYS/CMIOU2/PCIE2 PCIE pci_10 primary OCC
/SYS/CMIOU2/PCIE3 PCIE pci_11 primary OCC
/SYS/CMIOU2/PCIE1 PCIE pci_13 primary OCC
/SYS/CMIOU3/PCIE2 PCIE pci_15 primary OCC
/SYS/CMIOU3/PCIE3 PCIE pci_16 primary OCC
/SYS/CMIOU3/PCIE1 PCIE pci_18 primary OCC

82 | P a g e
/SYS/CMIOU4/PCIE2 PCIE pci_20 primary OCC
/SYS/CMIOU4/PCIE3 PCIE pci_21 primary OCC
/SYS/CMIOU4/PCIE1 PCIE pci_23 primary OCC
/SYS/CMIOU0/PCIE2/IOVNET.PF0 PF pci_0 primary
/SYS/CMIOU0/PCIE2/IOVNET.PF1 PF pci_0 primary
/SYS/CMIOU0/PCIE2/IOVNET.PF2 PF pci_0 primary
/SYS/CMIOU0/PCIE2/IOVNET.PF3 PF pci_0 primary
/SYS/CMIOU0/PCIE3/IOVFC.PF0 PF pci_1 primary

root@coreuatctrld:~# ldm rm-io pci_11 primary

------------------------------------------------------------------------------

Notice: The primary domain is in the process of a delayed reconfiguration.

Any changes made to the primary domain will only take effect after it reboots.

------------------------------------------------------------------------------

root@coreuatctrld:~# ldm rm-io pci_12 primary

------------------------------------------------------------------------------
Notice: The primary domain is in the process of a delayed reconfiguration.
Any changes made to the primary domain will only take effect after it reboots.
------------------------------------------------------------------------------
root@coreuatctrld:~#
root@coreuatctrld:~# ldm rm-io pci_13 primary

root@coreuatctrld:~# ldm add-domain secondary

root@coreuatctrld:~# ldm add-core 2 secondary
root@coreuatctrld:~# ldm ls
NAME STATE FLAGS CONS VCPU MEMORY UTIL NORM UPTIME
primary active -n-cv- UART 64 32G 0.0% 0.0% 9m
ldom01 inactive ------ 6 4G
secondary inactive ------
root@coreuatctrld:~# ldm add-core 2 secondary
root@coreuatctrld:~# ldm add-memory 32G secondary

83 | P a g e
root@coreuatctrld:~# ldm ls
NAME STATE FLAGS CONS VCPU MEMORY UTIL NORM UPTIME
primary active -n-cv- UART 64 32G 0.0% 0.0% 10m
ldom01 inactive ------ 6 4G
secondary inactive ------ 16 32G
root@coreuatctrld:~# ldm set-core 2 primary
root@coreuatctrld:~# ldm ls

NAME STATE FLAGS CONS VCPU MEMORY UTIL NORM UPTIME

primary active -n-cv- UART 16 32G 5.5% 5.4% 10m

ldom01 inactive ------ 6 4G

secondary inactive ------ 16 32G

Save The details Configuration::

root@coreuatctrld:~# ldm add-config 23-03-22

root@coreuatctrld:~# ldm bind secondary

root@coreuatctrld:~# ldm start secondary

ISO MOUNT FOR INSTALL OS IN LDOM OR GUEST DOMAIN:

oot@coreuatctrld:~# cd /iso

root@coreuatctrld:/iso# ls

sol-11_4_42_113_1-text-sparc.iso

84 | P a g e
root@coreuatctrld:/iso# ldm add-vdsdev options=ro /iso/sol-11_4_42_113_1-text-
sparc.iso solaris11.4.42@primary-vds0

root@coreuatctrld:/iso# ldm stop secondary

ldm add-vdisk solaris11.4.42 solaris11.4.42@primary-vds0 secondary

root@coreuatctrld:/iso# ldm set-var auto-boot\?=false secondary

root@coreuatctrld:/iso# ldm start secondary

root@coreuatctrld:/iso# ldm ls

NAME STATE FLAGS CONS VCPU MEMORY UTIL NORM UPTIME

primary active -n-cv- UART 16 32G 0.1% 0.1% 20m

secondary active -t---- 5000 16 32G 0.0% 0.0% 0s

ldom01 inactive ------ 6 4G

root@coreuatctrld:/iso# telnet 0 5000

Trying 0.0.0.0...

Connected to 0.

Escape character is '^]'.

enabling multipath:

stmsboot -e

Determine if multipath device information is available on the system:

prtconf -vc /devices/scsi_vhci |grep dev_link.*s2

Now check New LUN disk is visible or not for IO Domain or any Ldom .

echo | format

#mpathadm list LU | grep c0t600144F08666DED300005CECD5B4000E

If not visible please use below command for disk inititalization .

cfgadm -al -o show_SCSI_LUN

fcinfo hba-port | grep fc

85 | P a g e
After visible LUN .........>

#ldm add-vdsdev mpgroup=secondary-os

/dev/rdsk/c0t600144F0F515EF6000005F71CD1C000Ed0s2 secondary-os@primary-
vds0

#ldm add-vdsdev mpgroup=secondary-os

/dev/rdsk/c0t600144F0F515EF6000005F71CD1C000Ed0s2 secondary-
os@secondary-vds0

#ldm add-vdisk secondary-os secondary-os@primary-vds0 secondary

root@coreuatctrld:/iso# telnet 0 5000

Trying 0.0.0.0...

Connected to 0.

Escape character is '^]'.

Connecting to console "secondary" in group "secondary" ....

Press ~? for control options ..

NOTICE: Entering OpenBoot.

NOTICE: Fetching Guest MD.

NOTICE: Starting slave cpus.

NOTICE: Initializing LDCs.

NOTICE: Probing PCI devices.

ok devalias

ok Boot

86 | P a g e
DEDICATED LDOM CREATION:
ldm add-domain dedicatedldom1
ldm add-vcpu 4 dedicatedldom1
ldm add-memory 4G dedicatedldom1
ldm add-vnet dedicatedldom1-pri-vnet0 pri-dd-vsw0 dedicatedldom1
ldm add-vnet dedicatedldom1-sec-vnet1 sec-dd-vsw0 dedicatedldom1

ldm add-vdsdev mpgroup=dedicatedldom1-os1-mg

/dev/rdsk/c0t60060E802252FD00504152FD00006100d0s2 dedicatedldom1-
os1@primary-vds0
ldm add-vdsdev mpgroup=dedicatedldom1-os1-mg
/dev/rdsk/c0t60060E802252FD00504152FD00006100d0s2 dedicatedldom1-
os1@secondary-vds0
ldm add-vdisk os-disk1 dedicatedldom1-os1@primary-vds0 dedicatedldom1
ldm add-vdisk solaris11.4.42 solaris11.4.42@primary-vds0 sharedldom2
ldm bind-domain dedicatedldom1
ldm set-var auto-boot\?=false dedicatedldom1
ldm start-domain dedicatedldom1
ldm add-config final
ldm list-config
telnet localhost 5000

{0} ok devalias
{0} ok boot <Iso>

87 | P a g e
CREATING AND REGISTERING A LOCAL REPOSITORY

CONFIGURING AN IPS LOCAL REPOSITORY

It is convenient to install packages from the official Oracle repository, but access to
the Internet could become very intensive if in the company, there are a lot of
installed machines with Oracle Solaris 11 that repeat the same routine to install
packages. In this case, it is very handy to create a local IPS repository with the
same packages from the official repository but have them available on a local
network.

GETTING READY
To follow this recipe, it's necessary that we have a machine (physical or virtual)
running Oracle Solaris 11; we log in to the system as the root user and open a
terminal. Additionally, our system must be able to access the Internet. There are
further requirements, such as extra disk (physical or virtual), to create a Z File
System (ZFS), and we have to download the repository image.

SETTING UP LOCAL REPOSITORY - SOLARIS 11.4

THIS ARTICLE CONTAINS THE FOLLOWING TOPICS:

 Step 1: Download the base repository files:

 Step 2: Setting up the base repository:

 Step 3: Applying the support

 Step 4: Install the support updates to the base repository

 Step 5: Publish the repository locally

 Step 6: Update the OS to latest patch-set

 Step 7: Publish Solaris 11 IPS repository using HTTP service

For an Organization to keep the Solaris 11 x86 and SPARC servers updated with
latest OS patches a Solaris 11 IPS repository is required. Please note that the

88 | P a g e
instructions below are for setting up local repositories and are not related to
JetPatch functionality.

Setting up the repository has 3 phases:

1. Building the base repository (est. 1-2 hours.)

2. Applying the support incremental patch-set (est. 1-2 hours)
3. Publish the repository and configure a client (est. 10-20 minutes)

PRECONDITIONS:

Create a ZFS file system/repo with sufficient space to host the repository

STEP 1: DOWNLOAD THE BASE REPOSITORY FILES:

1. FIRST DOWNLOAD THE REPOSITORY FILES AND SETUP THE BASE

REPOSITORY

 Link to download
base repository files: https://www.oracle.com/solaris/solaris11/downloads/
local-repository-downloads.html
 Download these files:

89 | P a g e
2. Copy the files to one of the Solaris11 x86 or SPARC servers where you
wanted to configure the repository.

Create /var/repository/s11u4 and copy the files.

root@titan:~# mkdir -p /var/repository/s11u4

Copy the files from your desktop to /var/repository/s11u4 of the repository

server.

Verify all files are copied

root@titan:/var/repository/s11u4# ls -lrt
total 18817566
-rw-r--r-- 1 root root 1814619737 Jan 11 10:03 sol-11_4-repo_2of5.zip
-rw-r--r-- 1 root root 1968246581 Jan 11 10:13 sol-11_4-repo_1of5.zip
-rw-r--r-- 1 root root 2132702935 Jan 11 10:38 sol-11_4-repo_4of5.zip
-rw-r--r-- 1 root root 1772147401 Jan 11 10:52 sol-11_4-repo_3of5.zip
-rw-r--r-- 1 root root 1939943920 Jan 11 11:01 sol-11_4-repo_5of5.zip
-rw-r--r-- 1 root root 12262 Jan 11 11:13 install-repo.ksh
-rw-r--r-- 1 root root 495 Jan 11 11:13 sol-11_4-repo_digest.txt

STEP 2: SETTING UP THE BASE REPOSITORY:

Set execute permissions to script install-repo.ksh

root@titan:/var/repository/s11u4# chmod 755 install-repo.ksh

90 | P a g e
NOTE: ENSURE FILE SOL-11_4-REPO_DIGEST.TXT IS AVAILABLE IN THE SAME DIRECTORY. THIS IS
REQUIRED WHEN COMPERING THE CHECKSUM OF ZIP FILES
INSTALL THE REPOSITORY:

root@titan:/var/repository/s11u4# ./install-repo.ksh -d /repo

Using sol-11_4-repo download.
Uncompressing sol-11_4-repo_1of5.zip...done.
Uncompressing sol-11_4-repo_2of5.zip...done.
Uncompressing sol-11_4-repo_3of5.zip...done.
Uncompressing sol-11_4-repo_4of5.zip...done.
Uncompressing sol-11_4-repo_5of5.zip...done.

Repository can be found in /repo.

STEP 3: APPLYING THE SUPPORT INCREMENTAL UPDATES

The next step is to apply the incremental patch-set update. Oracle will release
incremental patch-set updates regularly.

Downloaded Oracle Patches from http://myoraclesupport.com/

Login > Go to > Patches and Updates> Patch Search > Search for the latest update

Download the latest incremental IPS repository patch-set

Create a directory /var/repository/s11incr in the repository server

#mkdir /var/repository/s11incr

Copy the patch-set files to /var/repository/s11incr

Copy the install-repo.ksh file which you have downloaded along with base repository
files to /var/repository/s11incr/

91 | P a g e
root@titan:~# cd /var/repository/s11incr/

root@titan:/var/repository/s11incr# cp -p ../s11u4/install-repo.ksh .

Create digest file sol-11_4-repo_digest.txt for all the zip files

root@titan:/var/repository/s11incr# ls -lrt
total 10083540
-rwxr-xr-x 1 root root 12262 Jan 11 11:13 install-repo.ksh
-rw-r--r-- 1 root root 1564502926 Jan 11 12:34 p28932200_1100_Solaris86-
64_3of3.zip
-rw-r--r-- 1 root root 1864407149 Jan 11 12:48 p28932200_1100_Solaris86-
64_2of3.zip
-rw-r--r-- 1 root root 1730048283 Jan 11 12:49 p28932200_1100_Solaris86-
64_1of3.zip
root@titan:/var/repository/s11incr# digest -v -a sha256 p28932200_1100_Solaris86-
64_3of3.zip > sol-11_4-repo_digest.txt
root@titan:/var/repository/s11incr# digest -v -a sha256 p28932200_1100_Solaris86-
64_2of3.zip >> sol-11_4-repo_digest.txt

root@titan:/var/repository/s11incr# digest -v -a sha256 p28932200_1100_Solaris86-

64_1of3.zip >> sol-11_4-repo_digest.txt

STEP 4: INSTALL THE SUPPORT UPDATES TO THE BASE REPOSITORY

root@titan:/var/repository/s11incr# ./install-repo.ksh -d /repo

Using p28932200_1100_Solaris86-64 files for sol-11_4-repo download.
IPS repository exists at destination /repo
Current version: 11.4.0.0.1.15.0
Do you want to add to this repository? (y/n)[n]: y
Uncompressing p28932200_1100_Solaris86-64_1of3.zip...done.
Uncompressing p28932200_1100_Solaris86-64_2of3.zip...done.
Uncompressing p28932200_1100_Solaris86-64_3of3.zip...done.
Repository can be found in /repo.
Initiating repository rebuild.

STEP 5: PUBLISH THE REPOSITORY LOCALLY

root@titan:/var/repository/s11incr# pkg set-publisher -G '*' -M '*' -g /repo solaris

root@titan:/var/repository/s11incr# pkg publisher
PUBLISHER TYPE STATUS P LOCATION

solaris origin online F file:///repo/

STEP 6: UPDATE THE OS TO LATEST PATCH-SET

92 | P a g e
root@titan:/var/repository/s11incr#pkg update --license --accept

Packages to install: 35
Packages to update: 317
Mediators to change: 1
Create boot environment: Yes
Create backup boot environment: No

DOWNLOAD PKGS FILES XFER (MB) SPEED

Completed 352/352 15216/15216 277.7/277.7 --

Step 7: Publish Solaris 11 IPS repository using HTTP service

To publish the repository, you need to configure and

enable /application/pkg/server service in the repository server.

Set the inst_root for http server as repository file system, in our case it is /repo

svccfg -s application/pkg/server:solaris setprop pkg/inst_root=/repo/publisher/solaris

root@titan:~#svccfg -s application/pkg/server setprop pkg/readonly=true

Set the server port as 8080

root@titan:~# svccfg -s application/pkg/server setprop pkg/port=8080

Refresh and Enable the application/pkg/server

root@titan:~# svcadm refresh application/pkg/server

root@titan:~# svcadm enable svc:/application/pkg/server:default

Verify the service is online

root@titan:~# svcs -a|egrep application/pkg/server

online 15:09:07 svc:/application/pkg/server:default

93 | P a g e
Choose a different Solaris server to have access to the remote publisher and set its
publisher:

root@atlas:~# pkg set-publisher -G '*' -M '*' -g http://[SERVER-IP]:8080/ solaris

Update the OS (Optional)

root@atlas:~# pkg update --accept

SOLARIS11-HOW TO MANAGE BOOT ENVIRONMENTS?

Managing boot environments in Solaris11 is almost same as Solaris 10’s Live

upgrade.In Solaris 10,we will use lu commands like
lucreate,luactivate,lumount ,luumount and lustatus. But in Solaris 11, all the tasks
will be carried out using beadm command.

Here we will perform simple operations to understand beadm in Solaris11. First

thing is to create a new boot environment and add one sample package to that
environment.Then activate the new BE and verify whether the sample package is
installed or not.After that bring the system back to old boot environment by
activating the old BE.

1.List out the current boot environments. In active column, NR stands for active
Now(N) and active on Reboot(R).And also you can see there is no snapshot exist on
the system.

OS upgradation time you should always create boot environment to ensure

application run smooth with old OS patch . If new patch are not suitable with
application then you can activate old OS BE .

root@Unixarena-SOL11:~# date
Saturday, July 6, 2013 04:24:21 PM IST
root@Unixarena-SOL11:~# beadm list
BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
solaris NR / 2.37G static 2013-06-11 06:27
root@Unixarena-SOL11:~# zfs list |grep @
root@Unixarena-SOL11:~#

2.Clone the current BE to new BE called UA-NEW. Here unlike Solaris 10,snapshots
are kept in the background. So you can see only new BE’s datasets. The datasets
name with UA-NEW belongs to new boot environment.

94 | P a g e
root@Unixarena-SOL11:~# beadm create UA-NEW
root@Unixarena-SOL11:~# beadm list
BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
UA-NEW - - 61.0K static 2013-07-06 16:28
solaris NR / 2.37G static 2013-06-11 06:27
root@Unixarena-SOL11:~# beadm list -a UA-NEW
BE/Dataset/Snapshot Active Mountpoint Space Policy Created
------------------- ------ ---------- ----- ------ -------
UA-NEW
rpool/ROOT/UA-NEW - - 87.0K static 2013-07-16 23:31
rpool/ROOT/UA-NEW/var - - 1.0K static 2013-07-16 23:31
root@Unixarena-SOL11:~#

3. Mount the boot environment.

root@Unixarena-SOL11:~# mkdir /UA-NEW

root@Unixarena-SOL11:~# beadm mount UA-NEW /UA-NEW
root@Unixarena-SOL11:~# df -h /UA-NEW
Filesystem Size Used Available Capacity Mounted on
rpool/ROOT/UA-NEW 15G 3.9G 8.8G 31% /UA-NEW
root@Unixarena-SOL11:~# beadm list
BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
UA-NEW - /UA-NEW 88.0K static 2013-07-16 23:31
solaris NR / 5.24G static 2013-02-12 03:26
root@Unixarena-SOL11:~#

4.Now we will install new package on UA-NEW.

root@Unixarena-SOL11:~# pkg -R /UA-NEW verify -v diffstat

pkg verify: no packages matching 'diffstat' installed
root@Unixarena-SOL11:~# pkg -R /UA-NEW install diffstat
Packages to install: 1

Planning linked: 0/3 done; 1 working: zone:webunixarena1

Planning linked: 0/3 done; 1 working: zone:webunixarena1
Planning linked: 1/3 done; 1 working: zone:dbunixarena1
Planning linked: 2/3 done; 1 working: zone:newzone
Planning linked: 3/3 done
DOWNLOAD PKGS FILES XFER (MB) SPEED
Completed 1/1 6/6 0.0/0.0 0B/s

95 | P a g e
Downloading linked: 0/3 done; 1 working: zone:webunixarena1
Downloading linked: 1/3 done; 1 working: zone:dbunixarena1
Downloading linked: 2/3 done; 1 working: zone:newzone
Downloading linked: 3/3 done
PHASE ITEMS
Installing new actions 24/24
Updating package state database Done
Updating image state Done
Creating fast lookup database Done
Executing linked: 0/3 done; 1 working: zone:webunixarena1
Executing linked: 1/3 done; 1 working: zone:dbunixarena1
Executing linked: 2/3 done; 1 working: zone:newzone
Executing linked: 3/3 done
root@Unixarena-SOL11:~#

Note:You need to configure

5.Verify the package on UA-NEW.

root@Unixarena-SOL11:~# pkg -R /UA-NEW verify -v diffstat

PACKAGE STATUS
pkg://solaris/text/diffstat OK
root@Unixarena-SOL11:~# pkg -R /UA-NEW list diffstat
NAME (PUBLISHER) VERSION IFO
text/diffstat 1.51-0.175.1.0.0.9.0 i--
root@Unixarena-SOL11:~#
6.Activate the UA-NEW.

root@Unixarena-SOL11:~# beadm activate UA-NEW

root@Unixarena-SOL11:~# beadm list
BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
UA-NEW R /UA-NEW 5.39G static 2013-07-16 23:31
solaris N / 2.08M static 2013-02-12 03:26
root@Unixarena-SOL11:~#

7.Reboot the system to boot the system from UA-NEW.

root@Unixarena-SOL11:~# init 6

while rebooting system,you can see the below screen on X86 systems.

96 | P a g e
8.Verify whether system is boot from UA-NEW.

root@Unixarena-SOL11:~# beadm list

BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
UA-NEW NR / 5.79G static 2013-07-16 23:31
solaris - - 6.55M static 2013-02-12 03:26
root@Unixarena-SOL11:~#

Note:Look at the Active column to confirm BE state. N- Active Now; R- Active on

Reboot;
9.Verify the installed packages are available in current boot environment.

root@Unixarena-SOL11:~# pkg list diffstat

NAME (PUBLISHER) VERSION IFO
text/diffstat 1.51-0.175.1.0.0.9.0 i--
root@Unixarena-SOL11:~#

10.You can also do the verification on OLD-BE, whether the package is

available there are not.

root@Unixarena-SOL11:~# mkdir /old-be

root@Unixarena-SOL11:~# beadm mount solaris /old-be
root@Unixarena-SOL11:~# pkg -R /old-be list diffstat
pkg list: no packages matching 'diffstat' installed
root@Unixarena-SOL11:~#

97 | P a g e
Any time you can rollback the Solaris 11 to old boot environment using below
command.

# beadm create solaris-2

root@Unixarena-SOL11:~# beadm activate solaris

root@Unixarena-SOL11:~# beadm list
BE Active Mountpoint Space Policy Created
-- ------ ---------- ----- ------ -------
UA-NEW N / 341.97M static 2013-07-16 23:31
solaris R /old-be 5.26G static 2013-02-12 03:26
root@Unixarena-SOL11:~#

N- Active now
R- Active upon Reboot

2.Reboot the server using “init 6” .

root@Unixarena-SOL11:~# init 6

Shown below are examples of activating, renaming, and destroying BEs.

# beadm activate solaris-3

# beadm rename solaris-2 solaris-old
# beadm destroy solaris

UPDATING THE FIRMWARE

On these servers, you can update the firmware without impacting hosts that are running in the PDomains. For hosts
that are running, the firmware is automatically updated when the running system or PDomains are powered off and
then powered on.

98 | P a g e
If you try to update the firmware with a version that is incompatible with the firmware on the running system or
PDomains, you will be instructed to shut down the hosts with the incompatible version and then update to the new
firmware version. Optionally, to ensure that all SPs and hosts move to the new image at the same time, you must
power off all hosts.

In addition, Oracle ILOM ensures that the system is upgraded automatically to the correct firmware when swapping
SPs and powering hosts off then on.

The firmware image you install to update the system firmware includes all necessary firmware components, including
the Oracle ILOM firmware, OpenBoot PROM firmware, POST firmware, and miscellaneous files. The firmware image
is installed in the flash memory of the SP.

These topics describe how to update the system firmware and view current versions of firmware for these servers.

 Display the Firmware Version

 Update the Firmware from Oracle ILOM

UPDATE THE FIRMWARE FROM ORACLE ILOM

The Live Firmware update feature of the SPARC M8, M7, T8, T7, and S7 series servers supports updating Sun
System firmware while the SPARC host is powered on. The Oracle ILOM firmware update goes into immediate effect.
However, the host components update is delayed until the affected host(s) is power cycled. Because Oracle ILOM
can be updated while the host is powered on, this feature reduces the total system down time. On SPARC M8 and
M7 series servers, the firmware update can be done on a per-host basis as each PDomain can be restarted
independently.

99 | P a g e
 1. Check the current system firmware version. From the Oracle ILOM command prompt, type:
2. -> show /System system_fw_version
3. Download the latest available system firmware version from My Oracle Support.

See the web page Firmware Downloads and Release History for Oracle Systems
(http://www.oracle.com/technetwork/systems/patches/firmware/release-history-jsp-138416.html) for
links to firmware downloads for each server type.

The download is an archive file such as a zip file which you must extract to find the pkg file containing
the firmware image.

Place the firmware image in a shared location that the server can access, such as a local or network
share or on a TFTP, FTP, HTTP or HTTPS server.

4. Read the README file that accompanies the firmware image to be aware of any special release
notes or instructions.
5. Notify SP users of the scheduled firmware update and ask them to close all client sessions until
after the firmware update is complete. Do not perform any other Oracle ILOM tasks during the
firmware update.
6. Update the firmware through the Oracle ILOM CLI.

Log in to Oracle ILOM using an account with Admin privileges.

See Logging In to Oracle ILOM.

UPDATE THE SERVER SP OR CMM FIRMWARE IMAGE

The following procedure explains the firmware update process using the CLI and the web interface
Maintenance page

100 | P a g e
 1. To start the firmware update process for a server SP or CMM image, perform the following steps
using one of the Oracle ILOM interfaces:

Oracle To Start and Run Firmware Update for SP or CMM Procedure

ILOM
Interfac
e

Web 1. Click Maintenance > Firmware Upgrade.

2. Click the button for Enter Firmware Upgrade Mode, then click OK in
the upgrade confirmation dialog box to proceed.

The Firmware Upgrade page displays the property for uploading the
firmware image.

Note – If the firmware image has not been downloaded from the Oracle
product download web site, see these instructions to download the
updated image:

3. In the Firmware Upgrade page, perform one the following actions:

Click Browse to specify the firmware image to upload, then click the
Upload button.

- or -

Input a URL to upload the firmware image, then click the Upload
button.

Oracle ILOM validates the firmware image and then displays options in
the Firmware Verification page.

4. Click Start to start the update process.

5. Click OK to proceed through a series of prompts until the Update Status
page appears.
6. The system will either reboot or power-off when the Update Status
indicates 100%.

If your system powers off, refer to the documentation provided with

your system for instructions on how to power on the system.

Note - (x86 server SPs only) If you the server has a pending BIOS
upgrade, the power reset could take longer to complete. This is
expected behavior, as it is necessary to power cycle the server to
upgrade the BIOS firmware. If the upgrade includes an FPGA update,
the process can take as long as 26 minutes to complete.

CLI 7. To load the Oracle ILOM firmware image using the CLI, issue

101 | P a g e
 the load -source command followed by the path to locate the firmware
image you want to install.

For example:
load -
source protocol://username:password@server_ip/<path_to_image>/<
image.pkg>

Where the protocol can be: http, https, ftp, tftp, sftp, scp

A series of prompts appear.

8. Type y to load the image file, then type y to enable the applicable
options:
Preserve Configuration – Enable this option to save and restore the
existing Oracle ILOM firmware settings after the firmware update is
complete. For further details about this option, see Preserve Oracle
ILOM Configuration .
Preserve BIOS Configuration (x86 server SPs only) - Enable this
option to save and restore existing BIOS configurations after the update
process is complete. This option is not supported on all x86 servers.
Therefore, if this option is not presented, Oracle ILOM restores the
default BIOS settings after completing the upgrade process.
Delay BIOS Upgrade (x86 server SPs only) – Enable this option to
postpone the x86 BIOS upgrade until after the next time the system is
power-cycled.
Note. All firmware update options presented for your server are
enabled (y) by default when using a script (-script) to perform the
firmware update.
9. Oracle ILOM displays a status message when the firmware process is
complete.The system will either reboot or power-off to apply the new
firmware image.
If the system powers off, refer to the documentation provided with your
system for instructions on how to power on the system.
Note - (x86 server SPs only) If the server has a pending BIOS upgrade,
the power reset could take longer to complete. This is expected
behavior, as it is necessary to power cycle the server to upgrade the
BIOS firmware. If the upgrade includes an FPGA update, the process
can take as long as 26 minutes to complete.

102 | P a g e
Load the firmware image from the shared location. Type:
-> load -source protocol://username:password@server_ip_or hostname/path_to_image/image.pkg

-> load -source http://198.51.100.123/fw-downloads/Sun_System_Firmware-X_X_X.pkg

a. Type y to load the image file, then type y to preserve the existing configuration, which saves
the existing Oracle ILOM firmware settings and restores them after the firmware update is
complete.

Note - All firmware update options for your server are enabled (y) by default when using a script (-
script) to perform the firmware update.

b. Oracle ILOM displays a status message when the firmware process is complete. The system will
reboot to apply the new firmware image.

THE END

103 | P a g e