Beruflich Dokumente
Kultur Dokumente
Keep Going
Release 2.5
March 2011
Preface
Access to Oracle Support
Provision an OS
About OS Provisioning
OS Images
OS Profiles
Importing OS Images and FLARs
Before You Begin
To Import an OS Image or a FLAR
To Monitor an OS Image Job
Loading OS Images From CD or DVD
To Load an OS Image From CD or DVD
To Monitor an OS Image Job
Downloading OS Images
To Download an OS Image
To Monitor an OS Image Job
Viewing the Available OS Images
To View the Available OS Images
Editing OS Image Information
To Edit OS Image Information
Deleting OS Images
To Delete an OS Image
Creating OS Profiles for Solaris Systems
Before You Begin
To Create an OS Profile for Solaris Systems
Creating OS Profiles for Linux Systems
Before You Begin
To Create an OS Profile for Linux Target Systems
Importing JET Templates
Before You Begin
To Import a JET Template
To View the Available OS Profiles
Editing an OS Profile
Before You Begin
To Edit an OS Profile
To Clone an OS Profile
Deleting an OS Profile
To Delete an OS Profile
Installing JET Modules
JET Resources and Documentation
To Check for Installed JET Modules
To Install a JET Module
JET Module Parameters
JET base_config Module Parameters
Preparing to Provision an OS
Discovering Target Systems
Disabling System Monitoring
Configuring DHCP Services
Identifying Available Ethernet Interfaces
To Configure DHCP Services by Using the BUI
To Configure DHCP Services by Using the proxyadm Command
Troubleshooting Known Solaris DHCP Issues
OS Provisioning for a Single System
Before You Begin
To Provision an OS on a Single System
Summary
Utilization
Libraries
OS Details
To Change Thresholds of OS Monitoring Variables
To Change File System Thresholds for an OS
Networks
Charts
Jobs
Configuration
Managing and Monitoring Zones Created Using Ops Center
Summary
Console
OS Details
To Change Monitoring Variables Threshold
To Change File System Thresholds for an OS
Network
Storage
Charts
Jobs
Configuration
Managing and Monitoring Existing Zones Through Ops Center
OS Details
To Change the Monitoring Variables Threshold
Console
Network
Charts
Jobs
Configuration
Performing Zone Tasks
Booting a Zone
To Boot a Zone
Rebooting a Zone
To Reboot a Zone
Adding Libraries to the Global Zone
To Associate a Library With the Global Zone
Disassociating Libraries From Global Zone
To Disassociate Libraries From Global Zone
Adding File Systems to Zones
To Add a File System to a Zone
Adding Storage to Zones
To Add Storage to Zones
Managing Zone Networks
Assigning Networks to a Global Zone
To Assign a Network to a Global Zone
Removing a Network From a Global Zone
To Unbind a Network From a Global Zone
Connecting Networks to Zones
To Connect a Network to a Zone
Disconnecting a Network From a Zone
To Disconnect a Network From a Zone
Cloning a Zone
To Clone a Zone
Attaching to Zone Console
To Attach to a Zone Console
Disabling the Zone Console Connection
To Disable a Zone Console Connection
Accessing the Serial Console
Before You Begin
Serial Console for Zones and Logical Domains
To Access the Serial Console
Troubleshooting the Access to Serial Console
Migrating Zones
Migrating a Zone to a Different Machine
To Reboot an OS
Managing Boot Environments
Displaying BE and ABE Details
To Display BE and ABE Details
Synchronize Boot Environments
To Synchronize Boot Environments
Activate a Boot Environment
To Activate a Boot Environment
Managing and Monitoring Hardware
Accessing the Serial Console
Before You Begin
Serial Console for Zones and Logical Domains
To Access the Serial Console
Troubleshooting the Access to Serial Console
Monitoring Hardware Health
States of Hardware Health
Managing and Monitoring M-Series Servers
Features Monitored
Managing Locator Lights
To Activate a Locator Light
To Deactivate a Locator Light
To Manage Locator Lights in a Group
Managing and Monitoring Server Power States
To Power On a Server or Chassis
To Power Off a Server or Chassis
Monitoring Power Utilization
Checking Power Capability
Power Utilization Graphs
To View Power Utilization Charts
To Export Power Utilization Charts
Monitoring Hardware Variables
Monitoring Connectivity
Resetting a Server
To Reset a Server
Monitoring Job Information
To View Current or Historical Jobs
Libraries
About Libraries
OS Provisioning Library
Firmware Provisioning Library
Updates Library
Storage Libraries
Updates Library
Managing Profiles
Managing Policies
Managing Components and Local Content
Adding a Local Category
To Add a Local Category
Deleting a Local Component
To Delete a Local Component File
Editing a Local Component File
To Edit Local Component Files
Uploading a Local Action
To Upload a Local Action
Uploading a Local Configuration File
To Upload a Local Configuration File
Uploading a Local Software Package
To Upload a Local Software Package
Uploading Local Software in Bulk
To Upload Local Software in Bulk
Uploading Software in Disconnected Mode
To Upload Software in Disconnected Mode
Viewing Bulk Upload Results
To View Bulk Upload Results
Viewing Component Details
Routing Modes
No Dynamic Routing Mode
Dynamic Routing On Mode
Automatic Routing Mode
Changing the Routing Mode
Adding a Static Route for the Network
To Add a Static Route for the Network
Editing the Network Attributes
To Edit the Network Attributes
Editing the Network Services
To Edit the Network Services
Deleting a Network
Before You Begin
To Delete a Network
Guests and Networks
Connecting Guests to a Network
Before You Begin
To Connect Guests to a Network
Disconnecting a Guest From a Network
To Disconnect a Guest From a Network
Viewing the Virtualization Hosts and Guests Using the Network
Virtual Pools and Networks
Assigning a Network to Virtual Pools
To Assign a Network to Virtual Pools
Dissociating a Network from a Virtual Pool
Viewing the Networks in a Virtual Pool
Enterprise Controller Administration
Configuring the Local Agent
To Configure the Local Agent
Unconfiguring an Enterprise Controller
To Unconfigure an Enterprise Controller
Adding a Product Alias
To Add a Product Alias
Changing the HTTP Proxy
To Change the HTTP Proxy
Authentications
To Edit Authentications
Configuring an Enterprise Controller for Updates
Before You Begin
Manually Enabling the Co-Located Proxy Controller
Manually Enabling a Ops Center Agent
Viewing Service Status
To View Service Status
Viewing Agent Controllers
To View Agent Controllers
Updating Agent Controllers
To Update Agent Controllers
Viewing Logs
To View Logs
Proxy Controller Administration
Unconfiguring and Uninstalling a Proxy Controller
To Unconfigure and Uninstall a Proxy Controller
To Unconfigure a Proxy Controller From the Command Line
Setting a Proxy Controller as Default
To Set a Proxy Controller as Default
Clearing a Proxy Controller's Default Status
To Clear a Proxy Controller's Default Status
DHCP Configuration
To Configure DHCP Services
To Monitor a DHCP Configuration Job
Subnets
Specifying IP Address Ranges
To Configure a Subnet
External DHCP Servers
Preface
This document is intended for all levels of Oracle Enterprise Manager Ops Center administrators, as well as operating system,
virtualization, hardware, and storage administrators using Oracle Enterprise Manager Ops Center to monitor and maintain their IT
infrastructure.
Provision an OS
Operating system (OS) provisioning enables you to use Ops Center to automatically install operating systems onto systems that
are attached to your network. In most circumstances, OS provisioning requires no manual interaction with the system that you
want to install. You initiate these OS installations from a centralized location, using the Ops Center BUI, rather than from the
systems that you want to install.
Check Supported Operating Systems for the list of operating systems that you can provision with Ops Center.
OS provisioning involves three main tasks:
Creating and Managing OS Images
Creating and Managing OS Profiles
Provisioning Operating Systems
Creating OS images and creating OS profiles are one-time tasks for each OS configuration that you want to provision. After an OS
image and associated OS profile exist in Ops Center, you can provision the OS onto systems that are attached to your network.
Ops Center enables OS provisioning on single systems, groups of systems, or a combination of the two. OS provisioning for
groups of systems requires using homogeneous groups, as described in Creating a Group and Adding Assets to a Group.
About OS Provisioning
Operating system (OS) provisioning enables you to use Ops Center to automatically install operating systems onto systems that
are attached to your network. In most circumstances, OS provisioning requires no manual interaction with the system that you
want to install. You initiate these OS installations from a centralized location, using the Ops Center BUI, rather than from the
systems that you want to install.
Check Supported Operating Systems for the list of operating systems that you can provision with Ops Center.
Before you can provision an OS, you must have the following in Ops Center:
OS Images
OS Profiles
Creating OS images and creating OS profiles are one-time tasks for each OS configuration that you want to provision. After an OS
image and associated OS profile exist in Ops Center, you can provision the OS onto systems that are attached to your network.
Ops Center enables OS provisioning on single systems, groups of systems, or a combination of the two. OS provisioning for
groups of systems requires using homogeneous groups, as described in Creating a Group and Adding Assets to a Group.
OS Images
You use OS images as the source of data used to install operating systems onto systems on your network. OS provisioning
requires that you import an OS image into Ops Center, and then associate the OS image with a customized OS profile.
To use OS images in Ops Center, you can:
Import an OS image from an existing ISO file
Import a Solaris Flash archive (FLAR) and associate it with an OS image
Load (copy) an image from physical CD or DVD installation media
Download an OS image from Sun Microsystems
You can obtain an OS image from the following sources:
CDs (Linux only)
DVDs (Solaris, Linux)
ISO files made from CDs (Linux only)
ISO files made from DVDs (Solaris, Linux)
Sun public server (Solaris only)
Check Supported Operating Systems for the list of operating systems that you can provision with Ops Center.
OS Profiles
An OS profile specifies how to configure an OS as it installs onto a set of target systems. An OS profile specifies configuration
options, including what OS to install, what software groups to install, and what disk partitions and network settings to use. Each
OS profile is associated with a specific OS image. Each OS profile describes how to install and configure one OS image, or one
FLAR associated with one OS image.
OS profiles used for the Solaris OS are similar to Sun JumpStart Enterprise Toolkit (JET) templates. Solaris OS profiles use JET
technology to provision the operating system. A Ops Center Proxy Controller installation includes the SUNWjet and JetFLASH
packages, which provide the base_config, custom, and flash JET modules. These JET modules provide the core JET functions
required by Ops Center. If you want to use additional JET modules, you must manually install them on the Proxy Controllers where
they will be needed. Refer to Installing JET Modules for more information about installing JET modules.
You can create a Solaris OS profile in one of the following ways:
Create an OS profile without providing any specific JET information.
Create an OS profile exclusively from a JET template.
Create an OS profile that includes parameters associated with additional JET modules.
OS profiles for RHEL and SLES do not use JET parameters, but they do require parameters that are specific to those operating
systems.
For Linux and Solaris software, you can use System Catalogs to create profiles.
4. In the Image Name field, enter the name that you want to assign to the ISO image or FLAR that you will import.
5. In the Description field, enter a description of the file that you will import.
6. Select either the ISO or FLAR image type, depending on the type of file that you will import.
If you select the FLAR file type, the Parent ISO field is displayed.
Select the OS image that you want to use as the parent ISO for the FLAR that you will import.
7. Click Browse to display the Browse Server panel.
8. Use the Browse Server panel to navigate to the directory that holds the ISO or FLAR that you want to import. You can
use the Refresh button to refresh the display of your current directory.
9.
9. Select the ISO or FLAR that you want to import, then click Add Files.
The file that you selected is displayed in the Files list in the Import OS Image panel.
10. When the list of files that you want to import is complete, click Import.
Downloading OS Images
You can download OS images and Solaris Flash archives (FLARs) from Sun Microsystems for use in Ops Center. After you
download an OS image, you can then create an OS profile to provision the OS onto systems on your network.
OS images and FLARs that you download are automatically associated with the OS Provisioning library. If an OS image is
appropriate for use with a profile, a default profile is generated.
Note You must download OS images in connected mode. There is no support for image download in disconnected mode.
If update is configured in disconnected mode, there is no connectivity to the Sun knowledge base (KB). You cannot download ISO
images from the local KB because they are not included in the harvester bundle.
To Download an OS Image
1. Click Libraries in the Navigation panel.
2. Click OS Images.
A list of OS images is displayed in the center panel.
3. Click Download OS Image in the Actions panel.
The Download OS Image wizard is displayed.
4. In the Select OS Image list, select the OS image or FLAR that you want to download. OS images that have associated
FLARs display a plus ( + )icon.
To select an OS Image, click the radio button for the OS image that you want to download.
To select a FLAR, click the plus icon for the associated OS image, then click the radio button for the FLAR that
you want to download.
5. If a license is associated with the OS image or FLAR that you selected, complete the following actions:
Click View License to display the associated license.
Click Accept License and Download to start the download process.
6. If a license is not associated with the OS image or FLAR that you selected, click Download to start the download process.
3. Select an OS image or FLAR to display the OS Image Details and Files panels for that image or FLAR.
The OS Image Details panel lists the following information about the OS Image or FLAR that you selected:
Field
Description
Image
Name
Image
Type
Description
OS Type
Identifies the operating system that the OS image or FLAR represents, for example, Solaris or Red Hat.
Version
HVM
Capable
PV Capable
Parent ISO
FLARs must be associated with a parent OS image to be used for OS provisioning. This field identifies the image
name of the parent ISO OS image that is associated with the FLAR.
The Files panel lists the path name of the OS image or FLAR on the Enterprise Controller.
Deleting OS Images
You can delete an OS image or Solaris Flash archive (FLAR) from its library in Ops Center.
You cannot delete an OS image or FLAR that is currently part of an OS profile. If you attempt to do so, a message is
displayed that indicates that the OS Image or FLAR is currently in use.
To Delete an OS Image
1. Click Libraries in the Navigation panel.
2. Click OS Images.
A list of OS images is displayed in the center panel.
3. Select an OS image or FLAR that you want to delete.
4. Click the Delete OS Image icon.
5. Click Delete in the confirmation message to delete the OS Image or FLAR.
OS profile names can consist of up to 100 characters and may include numbers, letters, and some special symbols. The
following special symbols are prohibited: comma, asterisk, single quote, double quote, parenthesis, question mark, equal
sign, and newline.
For Solaris target systems, if you want to use JET modules other than the base_config, custom, and flash modules
that are installed in Ops Center by default, you must install those additional modules on the Proxy Controllers that will
use them. Refer to Installing JET Modules for more information about installing JET modules.
You must install any additional JET modules before you use them within an OS profile for Solaris target systems.
Scripts must exist in a directory that the Ops Center Enterprise Controller can access. Scripts may be located in a local
directory of the Enterprise Controller, or in a directory that the Enterprise Controller mounts using NFS.
When you create a password, the password must contain at least one character. You cannot create an OS profile that
uses a space as a password.
The Create OS Profile wizard presents different panels depending on the operating system contained in the OS image that you
select. Ops Center provides OS provisioning services for Solaris and Linux. Use the following procedures to create OS profiles for
the Solaris operating system.
This selection adds the JET Parameters panel to the list of configuration panels in the Create OS Profile wizard.
This selection only applies to OS profiles that are used to provision the Solaris OS.
Click Next.
If you selected Specify JET Parameters in the Define Profile panel, the JET Parameters panel is displayed.
Continue to the next step.
If you did not select Specify JET Parameters in the Define Profile panel, and you did not select a FLAR from the
OS Image list, the Specify Distribution panel is displayed. Skip the next step.
5. If the JET Parameters panel is displayed, provide the following information:
JET Modules
Enter a comma-separated list of JET module names. Enter the names of any additional JET modules that you have
installed on the Proxy Controller that will perform the OS provisioning operations described by this OS profile.
The base_config, custom, and flash JET modules are always installed, and you do not need to specify them
here. Refer to Installing JET Modules for more information about JET module names.
Jet Parameters
Use the Add icon in the Jet Parameters list to add JET name-value pairs. In the Name field, enter the name of the
JET parameter that you want to add. In the Value field, enter the value that you want to assign to the JET
parameter. Refer to Installing JET Modules for more information about JET parameters.
Click Next.
The Specify Distribution panel is displayed if you did not select a FLAR from the OS Image list.
6. In the Specify Distribution panel, select the distribution types that you want to use from the Available list, and add them
to the Selected list. For Solaris OS profiles, select only one distribution type. Click Next.
Caution The Core distribution in Solaris 10 and Solaris 8 OS does not contain the SSH package by
default. Hence, Ops Center cannot provision the agent after OS Provisioning. The workaround is to
manually provision the agent on the system. See Installing Agents Manually.
9.
Select this option if you want the target system to run as an LDAP client after OS provisioning is complete.
LDAP Server IP
Enter the IP address of the LDAP server for the domain that you enter in the Domain Name field.
Domain Name
Enter the name of the LDAP domain that the target system will use.
Click Next. The panel that is displayed next depends on the options that you selected in the Specify Parameters
panel.
10. If you selected Add Scripts in the Specify Parameters panel, the Add Scripts panel is displayed after either the Specify
Parameters, NIS Settings, or LDAP Settings panels. Click the Add icon to add scripts to run on the target system. The
Browse Server icon enables you to locate scripts by browsing the file systems that are available to the Enterprise
Controller.
For each script that you add, choose one of the following three script types:
post
Indicates that the script will run after the OS installation completes on the target system.
pre
Indicates that the script will run before the OS installation begins on the target system.
postnochroot
Indicates that the script will run after the OS installation completes on the target system, and that chroot
(1M) functions are disallowed. The postnochroot type is only applicable to Red Hat target systems.
Click Next.
The Define Partitions panel is displayed.
11. In the Define Partitions panel, define the disk partitions and file systems that you want to create on the target system.
Click the Add icon to define a new partition. The root (/) and a swap file system are defined by default.
For each partition that you define, provide the following information:
Mount Point
Enter a directory to use as a mount point for partitions that use the ufs or unnamed file system type. Swap file
systems disable this field.
Device
Enter the rootdisk keyword and a slice value to describe a partition on the target system's boot disk, for
example, rootdisk.s0, or enter the logical device name, for example, c1t0d0s0, of the partition that you
want to create.
File System
Select a file system type: ufs, unnamed, swap, or zfs.
Specify Size
Select this option to specify a specific size for a partition. If you want a single partition to use all of the
remaining space on the disk, deselect this option.
Size (MB)
With the Specify Size option selected for a partition, enter the size that you want to assign to the partition,
expressed in MBytes.
Click Next.
The Summary panel is displayed.
12. The Summary page displays the information that you specified in all of the preceding panels in the Create OS Profile
wizard. If the summary information is correct, click Save OS Profile.
7.
8.
9.
10.
Confirm Password
Re-enter the password that you specified in the previous field.
Specify NIS Settings
Select this option if you want systems that are provisioned using this profile to be configured as NIS clients. This
selection adds the NIS Settings panel to the list of configuration panels in the Create OS Profile wizard. You
cannot use this option with the Specify LDAP Settings option.
Specify LDAP Settings
Select this option if you want the systems that are provisioned using this profile to be configured as LDAP
clients. This selection adds the LDAP Settings panel to the list of configuration panels in the Create OS Profile
wizard. You cannot use this option with the Specify NIS Settings option.
Add Scripts
Select this option if you want to run specific scripts on the target system. This selection adds the Add Scripts
panel to the list of configuration panels in the Create OS Profile wizard.
Click Next.
The panel that is displayed next depends on the options that you selected in this panel.
If you selected Specify NIS Settings in the Specify Parameters panel, the NIS Settings panel is displayed. Provide the
following information to configure the target system as an NIS client:
Enable NIS
Select this option if you want the target system to run as an NIS client after OS provisioning is complete.
Domain Name
Enter the name of the NIS domain to which the target system will bind.
NIS Server IP
If this field is active, enter the IP address of the NIS server to which the target system will bind.
Click Next.
The panel that is displayed next depends on the options that you selected in the Specify Parameters panel.
If you selected Specify LDAP Settings in the Specify Parameters panel, the LDAP Settings panel is displayed. Provide the
following information to configure the target system as an LDAP client:
Enable LDAP
Select this option if you want the target system to run as an LDAP client after OS provisioning is complete.
LDAP Server IP
Enter the IP address of the LDAP server for the domain that you enter in the Domain Name field.
Domain Name
Enter the name of the LDAP domain that the target system will use.
Click Next.
The panel that is displayed next depends on the options that you selected in the Specify Parameters panel.
If you selected Add Scripts in the Specify Parameters panel, the Add Scripts panel is displayed after either the Specify
Parameters, NIS Settings, or LDAP Settings panels. Click the Add icon to add scripts to run on the target system. The
Browse Server icon enables you to locate scripts by browsing the file systems that are available to the Enterprise
Controller.
For each script that you add, choose one of the following script types:
post
Indicates that the script will run after the OS installation completes on the target system.
pre
Indicates that the script will run before the OS installation begins on the target system.
postnochroot
(Red Hat target systems) Indicates that the script will run after the OS installation completes on the target
system, and that chroot (1M) functions are disallowed.
Click Next.
The panel that is displayed next depends on the Linux OS image that you selected at the beginning of this
procedure.
If you selected a Red Hat OS image, the Specify Red Hat Preferences panel is displayed. Provide the following
information:
Installation Number
(Optional) Enter the installation number used to allow installation of all of the Red Hat software that is included
in your subscription.
Partition Action
Choose how you want to affect the disk partitions on the target system:
Remove all Linux Partitions
Select this option to remove any existing Linux partitions, establish new partitions according to your
specifications, and retain non-Linux partitions.
Preserve all existing partitions
Select this option to preserve all existing partitions. You will need to define partitions, outside of the
partitions that exist, in which to install the OS.
Remove all partitions
Select this option to remove all existing partitions and establish new partitions according to your
specifications.
MD5 Checksum
Select this option to use MD5 encryption for user passwords.
Initialize Disk Label
Select this option to initialize labels on new disks. This option creates labels that are appropriate for the target
system architecture.
Clear Master Boot Record
Select this option to clear all invalid partition tables.
Reboot System After Installation
Select this option to reboot the target system after the OS installation completes.
Use Shadow Passwords
Select this option to use an /etc/shadow file to store passwords on the target system.
Click Next.
The Define Partitions panel is displayed.
11. If you selected a SUSE Linux OS image, the Specify SUSE Preferences panel is displayed. Provide the following
information:
FTP Proxy Server
Enter the name of the FTP proxy server if one is needed to support FTP services.
HTTP Proxy Server
Enter the name of the HTTP proxy server if one is needed to support HTTP services.
Enable Proxy Servers
Select this option if you want to enable the FTP and HTTP proxy servers that you specified in the FTP Proxy
Server and HTTP Proxy Server fields.
Reboot System After Installation
Select this option if you want the target system to reboot after the OS installation completes.
Click Next.
The Define Partitions panel is displayed.
12. In the Define Partitions panel, define the disk partitions and file systems that you want to create on the target system.
Click the Add icon to define a new partition. The root (/) and swap file systems are defined by default. For each
partition that you define, provide the following information:
Mount Point
Enter a directory to use as a mount point for partitions that use any file system type except swap. Swap file
systems disable this field.
Device
Enter the logical device name, for example, sda or /dev/sda, of the partition that you want to create.
File System
Select a file system type. Red Hat Linux profiles list vfat, ext2, ext3, or swap file system types. SUSE Linux
profiles list jfs, xfs, reiser, ext2, ext3, and swap file system types.
Specify Size
Select this option to specify a specific size for a partition. If you want a single partition to use all of the
remaining space on the disk, deselect this option.
Size (MB)
When you select the Specify Size option, enter the size that you want to assign to the partition, expressed in
MBytes.
Click Next.
The Summary panel is displayed.
13. The Summary page displays the information that you specified in the preceding panels in the Create OS Profile wizard. If
the summary information is correct, click Save OS Profile.
Editing an OS Profile
You can edit existing OS profiles. When you import an OS image into Ops Center, a default OS profile is created automatically. In
many cases, you must edit this default profile to match your specific system and configuration requirements. In addition, your OS
provisioning requirements might change, which might cause you to change information within your OS profiles.
The following procedure describes all of the panels that the Edit OS Profile wizard might present, including the panels that are
specific to Solaris and to Red Hat and SUSE Linux profiles. When editing an OS profile, you only need to edit the specific fields
that contain information that you want to change. Leave alone any field that you do not want to change.
To Edit an OS Profile
1. Click Libraries in the Navigation panel.
2. Click OS Profiles.
2.
A list of OS profiles is displayed in the center panel.
3. Select an OS profile from the OS Profiles list.
The OS Profile Details for the OS profile that you selected are displayed.
4. Click the Edit OS Profile icon.
The Define Profile panel of the Edit OS Profile wizard is displayed. The Edit OS Profile wizard presents the same panels as
the Create OS Profile wizard. Refer to Creating OS Profiles for Solaris Systems for more information about the
information required to create OS profiles.
5. In the Define Profile panel, you cannot change the OS Image or Profile Type selections. You can change the following
information in the Define Profile panel:
Profile Name
Enter a name for the OS profile.
Description
Enter a description for the OS profile.
Specify JET Parameters
(Solaris OS profiles only) If the profile that you are editing has additional JET parameters that you
want to change, select Specify JET Parameters. The JET Parameters panel is displayed, where you
can make your desired changes. If you do not select this option, the JET Parameters panel is not
displayed, and no change is made to any additional JET parameters that are associated with this
OS profile.
Click Next.
If you selected Specify JET Parameters in the Define Profile panel, the JET Parameters panel is displayed.
If you did not select Specify JET Parameters in the Define Profile panel, the Specify Distribution panel is
displayed.
6. If the JET Parameters panel is displayed, you can change the following information:
JET Modules
Enter a comma-separated list of JET module names. Enter the names of any additional JET modules
that you have installed on the Proxy Controller that will perform the OS provisioning operations
described by this OS profile. The base_config, custom, and flash JET modules are always
installed, and you do not need to specify them here. Refer to Installing JET Modules for more
information about JET module names.
Jet Parameters
Use this list to add or remove JET name-value pairs.
To add a name-value pair, click the Add icon. In the Name field, enter the name of the
JET parameter that you want to add. In the Value field, enter the value that you want to
assign to the JET parameter.
To remove a name-value pair, select the row for the name-value pair, then click the
Remove icon.
Refer to Installing JET Modules for more information about JET parameters.
Click Next.
The Specify Distribution panel is displayed.
7. In the Specify Distribution panel, you can use the Add, Add All, Remove, or Remove All buttons to select the distribution
types that you want to use from the Available list, and add them to the Selected list.
(Solaris OS profiles) Select only one distribution type.
(Red Hat and SUSE Linux OS profiles) Select all distribution types that are appropriate for the desired
installation.
8. Click Next.
The Specify Parameters panel is displayed.
9. In the Specify Parameters panel, you can change the following information:
Language
Select a language from the list.
Time Zone
Select a time zone from the list.
Root Password
Enter a password for the root user on systems provisioned using this OS profile.
Confirm Password
Re-enter the password that you specified in the previous field.
Specify NIS Settings
Select this option if you want the systems that are provisioned using this profile to be configured
as NIS clients, or if you want to change the NIS settings that are specified in this OS profile. This
selection adds the NIS Settings panel to the list of configuration panels in the Create OS Profile
wizard. You cannot use this option with the Specify LDAP Settings option.
Specify LDAP Settings
Select this option if you want the systems that are provisioned using this profile to be configured
as LDAP clients, or if you want to change the LDAP settings that are specified in this OS profile.
This selection adds the LDAP Settings panel to the list of configuration panels in the Create OS
Profile wizard. You cannot use this option with the Specify NIS Settings option.
Add Scripts
Select this option if you want to run specific scripts on the target system, or if you want to change
the script details that are specified in this OS profile. This selection adds the Add Scripts panel to
the list of configuration panels in the Create OS Profile wizard.
If you deselect any of the options in this panel, the values that were previously specified for those options remain
unchanged.
Click Next.
The panel that is displayed depends on the options that you selected in this panel.
10. If you selected Specify NIS Settings in the Specify Parameters panel, the NIS Settings panel is displayed. In the NIS
Settings panel, you can change the following information to configure the target system as an NIS client:
Enable NIS
Select this option if you want the target system to run as an NIS client after OS provisioning is
complete.
Domain Name
Enter the name of the NIS domain to which the target system will bind.
Find a NIS Server
Select this option to cause the target system to identify an NIS server in the domain that you
specified in the Domain Name field.
Specify a NIS Server
Select this option to activate the NIS Server IP field.
NIS Server IP
If this field is active, enter the IP address of the NIS server to which the target system will bind.
Click Next.
The panel that is displayed depends on the options that you selected in the Specify Parameters panel.
11. If you selected Specify LDAP Settings in the Specify Parameters panel, the LDAP Settings panel is displayed. In the LDAP
Settings panel, you can change the following information to configure the target system as an LDAP client:
Enable LDAP
Select this option if you want the target system to run as an LDAP client after OS provisioning is
complete.
Server IP
Enter the IP address of the LDAP server for the domain that you enter in the Domain Name field.
Domain Name
Enter the name of the LDAP domain that the target system will use.
Click Next.
The panel that is displayed depends on the options that you selected in the Specify Parameters panel.
12. If you selected Add Scripts in the Specify Parameters panel,the Add Scripts panel is displayed after the Specify
Parameters, NIS Settings, or LDAP Settings panels. In the Add Scripts panel, use the Scripts list to add or remove scripts
for this OS profile.
To add a script to run on the target system, click the Add icon. The Browse Server icon enables you to locate scripts by
browsing the file systems that are available to the Enterprise Controller.
For each script that you add, choose one of the following script types:
post
Indicates that the script will run after the OS installation completes on the target system.
pre
Indicates that the script will run before the OS installation begins on the target system.
postnochroot
(Red Hat target systems) Indicates that the script will run after the OS installation completes on
the target system, and that chroot (1M) functions are disallowed.
To remove a script, select the row for the script, then click the Remove icon.
Click Next.
For Solaris OS profiles, the Define Partitions panel is displayed.
For Red Hat and SUSE Linux OS profiles, the panel that is displayed depends on the Linux OS image that is
associated with the OS profile.
13. If the OS profile is associated with a Red Hat OS image, the Specify Red Hat Preferences panel is displayed. In this panel,
you can change the following preferences:
Installation Number
(Optional) Enter the installation number used to allow installation of all of the Red Hat software
that is included in your subscription.
Partition Action
Choose how you want to affect the disk partitions on the target system:
Remove all Linux Partitions
Select this option to remove any existing Linux partitions, establish new partitions
according to your specifications, and retain non-Linux partitions.
Preserve all existing partitions
Select this option to preserve all existing partitions. You will need to define new
partitions in which to install the OS.
Remove all partitions
Select this option to remove all existing partitions and establish new partitions according
to your specifications.
MD5 Checksum
Select this option to use MD5 encryption for user passwords.
Initialize Disk Label
Select this option to initialize labels on new disks. This option creates labels that are appropriate
for the target system architecture.
Clear Master Boot Record
Select this option to clear all invalid partition tables.
Reboot System After Installation
Select this option to reboot the target system after the OS installation completes.
Use Shadow Passwords
Select this option to use an /etc/shadow file to store passwords on the target system.
Click Next.
The Define Partitions panel is displayed.
14. If the OS profile is associated with a SUSE Linux OS image, the Specify SUSE Preferences panel is displayed. In the Specify
SUSE Preferences panel, you can change the following preferences:
FTP Proxy Server
Enter the name of the FTP proxy server if one is needed to support FTP services.
HTTP Proxy Server
Enter the name of the HTTP proxy server if one is needed to support HTTP services.
Enable Proxy Servers
Select this option if you want to enable the FTP and HTTP proxy servers that you specified in the
FTP Proxy Server and HTTP Proxy Server fields.
Reboot System After Installation
Select this option if you want the target system to reboot after the OS installation completes.
Click Next.
The Define Partitions panel is displayed.
15. In the Define Partitions panel, you can change the disk partitions and file systems that you want to create on the target
15.
system. Click the Add icon to define a new partition. The root (/) and a swap file system are defined by default.
For each partition that you define, provide the following information:
Mount Point
Enter a directory to use as a mount point for partitions that use any file system type except swap.
Swap file systems disable this field.
Device
(Solaris OS profiles) Enter the rootdisk keyword and a slice value to describe a partition on the
target system's boot disk, for example, rootdisk.s0, or enter the logical device name, for
example, c1t0d0s0 of the partition that you want to create.
(Red Hat or SUSE Linux OS profiles) Enter the logical device name, for example, sda or
/dev/sda, of the partition that you want to create.
File System
Select a file system type:
(Solaris OS profiles) ufs, unnamed, or swap
(Red Hat Linux profiles) vfat, ext2, ext3, or swap
(SUSE Linux profiles) jfs, xfs, reiser, ext2, ext3, and swap
Specify Size
If you want to enter a specific size for a partition, select this option.
If you want a partition to use all of the remaining space on the disk, you can deselect this
option for only one partition.
Size (MB)
When you select the Specify Size option, enter the size that you want to assign to the partition,
expressed in MBytes.
Click Next.
The Summary panel is displayed.
16. The Summary page displays the information that you specified in the preceding panels in the Edit OS Profile wizard. The
Summary page also displays existing OS profile information from panels that you chose not to view. If the summary
information is correct, click Save OS Profile.
To Clone an OS Profile
You can create a copy of an existing OS profile, and use it as a basis for further customization. Copying an OS profile is referred
to as cloning an OS profile.
1. Click Libraries in the Navigation panel.
2. Click OS Profiles.
A list of OS profiles is displayed in the center panel.
3. Select an OS profile from the OS Profiles list.
The OS Profile Details for the OS profile that you selected are displayed.
4. Select the Clone OS Profile icon.
The Clone OS Profile dialog box is displayed.
5. Enter a name for the clone in the New Profile Name field, and click Clone.
The new OS profile displays in the OS Profiles list.
6. If you want to customize the new OS profile, follow the procedure described in Editing an OS Profile.
Deleting an OS Profile
You can delete an existing OS profile. However, you cannot delete an OS profile that is currently being used to provision an
operating system.
To Delete an OS Profile
1. Click Libraries in the Navigation panel.
2. Click OS Profiles.
A list of OS profiles is displayed in the center panel.
3.
JET Package
Installed
by
Default
Description
base_config
SUNWjet
Yes
Provides the standard installation configuration for the client, including the
information required to set up the JumpStart server to allow the client to boot and
build
custom
SUNWjet
Yes
explo
JetEXPLO
No
flash
JetFLASH
Yes
Adds the ability for the JumpStart server to deliver Solaris images in Solaris Flash
format
n/a
JetISO
No
Adds JET utilities to manage lofi mounting and sharing of ISO images
jass
JetJASS
Yes
Adds the ability for the JumpStart server to install, configure, and execute JASS
ldom
JetLDOM
Yes
N/A
JetRBAC
No
Enables non-root users to run JET using the Role Based Access Control (RBAC)
facility
san
JetSAN
No
Installs and patches the SAN Foundation kit and SNIA packages, and configures
STMS
sbd
JetSBD
No
sds
JetSDS
No
vts
JetVTS
No
Adds support for installation of the Sun VTS software under the JumpStart
framework
N/A
JetWanBoot
No
zfs
JetZFS
No
zones
JetZONES
No
N/A
SUNWjetd
No
Description
JET Portal
on
BigAdmin
This page presents the JET disclaimer, and links to blogs and JET downloads.
Sun
Downloads
This link gets you to the Sun Downloads listing, indexed for the alphabetic group that includes the datastream
package, jet.pkg for the JumpStart Enterprise Toolkit. The latest version available at this time (November, 2008)
is 4.4.7.
JET User
Guide
Complete
JET User
Guide
This document describes how to create a PDF version of the JET User Guide, or to print the guide as a whole.
# cd /opt/SUNWjet/Products
# ls
base_config custom
flash
#
# *pkginfo -d jet.pkg*
application JetEXPLO
application JetFLASH
application JetISO
application JetJASS
application JetLDOM
application JetRBAC
application JetSAN
application JetSBD
application JetSDS
application JetVTS
application JetWanBoot
application JetZFS
application JetZONES
application SUNWjet
application SUNWjetd
#
3. Use the pkgadd command to install the package that delivers the module that you want to add to the Proxy Controller.
For example:
base_config_sysidcfg_root_password
base_config_sysidcfg_security_policy
base_config_sysidcfg_protocol_ipv6
The following table describes the parameters that are associated with the base_config JET module. These parameters provide
basic operating system configuration information. Values for many of these parameters use the term targetableComponent to
represent the target system.
Parameter Name
Description
Default Value
base_config_client_allocation
base_config_ClientArch
[targetableComponent:kernel_arch
base_config_ClientEther
[targetableComponent:ethernet_ma
base_config_ClientOS
base_config_dedicated_dump_device
base_config_defaultrouter
base_config_disable_sysid_probe
yes
base_config_dns_disableforbuild
base_config_dns_domain
base_config_dns_nameservers
base_config_dns_searchpath
base_config_dumpadm_minfree
base_config_enable_altbreak
base_config_enable_rootftp
base_config_enable_rootlogin
base_config_enable_savecore
yes
base_config_grub_append
base_config_ipmp_networkifs
base_config_networkifs
base_config_nfs_mounts
base_config_nfsv4_domain
base_config_noautoshutdown
pm_disabled
base_config_nodename
base_config_notrouter
base_config_ntp_servers
base_config_patchdir
base_config_poweroff_afterbuild
base_config_productdir
base_config_products
base_config_profile
base_config_profile_add_clusters
base_config_profile_add_geos
base_config_profile_add_locales
base_config_profile_add_packages
base_config_profile_additional_disks
base_config_profile_cluster
SUNWCreq
base_config_profile_del_clusters
base_config_profile_del_geos
base_config_profile_del_locales
base_config_profile_del_packages
base_config_profile_dontuse
base_config_profile_root
free.
base_config_profile_s3_mtpt
base_config_profile_s3_size
base_config_profile_s4_mtpt
base_config_profile_s4_size
base_config_profile_s5_mtpt
/var
base_config_profile_s5_size
base_config_profile_s6_mtpt
/usr
base_config_profile_s6_size
base_config_profile_s7_mtpt
/opt
base_config_profile_s7_size
base_config_profile_swap
256
base_config_profile_usedisk
rootdisk
base_config_shutup_sendmail
yes
base_config_sysidcfg_default_route
base_config_sysidcfg_ip_address
[targetableComponent:etherne
base_config_sysidcfg_nameservice
NIS
base_config_sysidcfg_netmask
[targetableComponent:etherne
base_config_sysidcfg_network_interface
NONE
base_config_sysidcfg_protocol_ipv6
no
base_config_sysidcfg_root_password
base_config_sysidcfg_security_policy
NONE
base_config_sysidcfg_system_locale
base_config_sysidcfg_terminal
vt100
base_config_sysidcfg_timeserver
base_config_sysidcfg_timezone
base_config_sysidcfg_x86_kdmfile
base_config_ufs_logging_filesys
all
base_config_update_terminal
yes
base_config_x86_confflags
base_config_x86_console
base_config_x86_disable_acpi
base_config_x86_disable_kdmconfig
base_config_x86_nowin
yes
base_config_x86_safetoreboot
Preparing to Provision an OS
Using Ops Center to provision operating systems requires some preparation, including:
Importing, loading, or downloading an OS image to use to install the OS onto target systems. Importing OS Images and
FLARs, Loading OS Images From CD or DVD, and Downloading OS Images describe three ways to bring OS images into
Ops Center.
Creating an OS profile appropriate for the target systems. Creating OS Profiles for Solaris Systems, Importing JET
Templates, and Editing an OS Profile describe three ways to create OS profiles that are appropriate for your target
systems.
Discovering the service processor of the target systems. Discovering Target Systems describes a simple custom discovery
procedure. Asset Management contains links to additional procedures for discovering assets. See Custom Discovery for
more information about custom asset discovery.
Disabling monitoring for servers that you plan to provision. This step is useful to avoid generating events or errors
related to a monitored system going offline during the OS provisioning process.
Configuring DHCP services on Ops Center Proxy Controllers.
5. In the Enter Server Credential panel, enter the SSH user name and associated password for the root or privileged user
on the target system. Select one of the two options that control how the credentials that you enter apply to the listed
assets:
Use the Same SSH Username and Password for All Assets Listed Below
Use Different SSH Username and Password for All Assets Listed Below
6. Click Next.
The Unmanage/Delete panel is displayed.
7. In the Unmanage/Delete panel, verify that the correct system to unmanage is listed. Click Next.
The Summary panel is displayed.
8. Click Unmanage/Delete Asset to submit the job to unmanage and delete the selected asset.
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 172.20.25.230 netmask fffffc00 broadcast 172.20.27.255
ether 8:0:20:e9:35:b9
qfe0: flags=1000802<BROADCAST,MULTICAST,IPv4> mtu 1500 index 3
inet 0.0.0.0 netmask 0
ether 8:0:20:e9:35:b9
qfe1: flags=1000802<BROADCAST,MULTICAST,IPv4> mtu 1500 index 4
inet 0.0.0.0 netmask 0
ether 8:0:20:e9:35:b9
qfe2: flags=1000802<BROADCAST,MULTICAST,IPv4> mtu 1500 index 5
inet 0.0.0.0 netmask 0
ether 8:0:20:e9:35:b9
qfe3: flags=1000802<BROADCAST,MULTICAST,IPv4> mtu 1500 index 6
inet 0.0.0.0 netmask 0
ether 8:0:20:e9:35:b9
#
This example lists five external Ethernet interfaces, hme0, qfe0, qfe1, qfe2, and qfe3. The loopback interface lo0 is not used
for DHCP or OS provisioning services. Choose the Ethernet interface that is attached to the network that you want to use for OS
provisioning operations.
Stop the Proxy Controller services before you configure DHCP services, then start the Proxy Controller services again. For
example:
# /opt/SUNWxvmoc/bin/proxyadm stop -w
# /opt/SUNWxvmoc/bin/proxyadm configure -D isc -I hme0
# /opt/SUNWxvmoc/bin/proxyadm start -w
1.
Oracle Enterprise Manager Ops Center
the installed OS, are displayed in the Assets panel list. The Provision OS action only is displayed when you select the icon
that represents the system hardware or service processor.
2. Select Provision OS from the Actions list.
The Specify OS Profile panel of the Provision OS wizard is displayed.
3. In the Specify OS Profile panel, select an OS profile from the OS Profile list. Only the OS profiles that match the
architecture of the target system are displayed in the OS Profile list. For example, if you select a SPARC processor-based
target system, only profiles that you can use for SPARC systems are displayed.
4. Click Next.
The Configuration panel is displayed. The panel displayed below applies to Solaris systems.
The Target field in this panel identifies the target system for the OS provisioning action. Note that when the target of the
OS provisioning action includes only one system, the Provision OS wizard skips the Select Target panel, which otherwise
is displayed before the Configuration panel.
5. In the Configuration panel, enter the information that is required for your target system and selected OS profile.
Different fields are displayed, depending on the type of OS profile that you select. The Configuration panel fields that
relate to any single system, except for a virtualization host, are described below. Refer to OS Provisioning for Multiple
Systems and Provisioning a Guest Domain for OS provisioning procedures for groups of target systems, and for
provisioning virtualization hosts.
Manual Net Boot
Select this option to enable manual control of network boot operations for the target system. You must select
this option for the target system that does not have a service processor because Ops Center cannot remotely
control the network boot process on these systems. When the NetbootTask of OS Provisioning job is successful,
log in to the service processor of the target system(s). You must manually initiate the network boot process
from the target system(s) by typing boot net:dhcp - install.
Register with Ops Center
Select this option if you want to register the target system with your Ops Center instance.
Network Protocol
Select Static IP or DHCP. This determines the method used to assign an IP address to the target system's
provisioning network interface, after the system is provisioned. The DHCP network protocol is only available for
OS profiles that install Linux operating systems. If you select DHCP protocol for Linux operating systems, you
need to set up an external DHCP server in the same subnet as the Proxy Controller. This external DHCP server
will provide DHCP data to the system after provisioning is completed. You can also set up DHCP server on the
Proxy Controller through Subnets with a range of IP addresses to assign to systems on that subnet.
Install Protocol
For Linux provisioning, select HTTP or NFS.
IP Address
Enter the IP address for the target system. This field is displayed only if you select Static IP in the Network
Protocol field, and is a required field when it is displayed. Use IP addresses that are not defined as part of a
subnet that is managed by the DHCP server on a Proxy Controller. See Subnets for more information.
Boot IP
For Linux provisioning, enter the IP address of the network interface that the target system will use for OS
provisioning. This is a required field when it is displayed.
Netmask
Enter the netmask value that the target system will use after the OS has been installed.
Gateway
Enter the gateway value that the target system will use after the OS has been installed.
Host Name
Enter the host name that the target system will use after the OS has been installed.
Name Server
Enter the IP address or host name of the name server that the target system will use after the OS has been
installed.
Console Serial Port
To monitor the installation using a serial connection, select the correct console serial port device.
Console Baud Rate
To monitor the installation using a serial connection, select the correct serial port device baud rate.
Network Device
Select the device for the network interface that the target system will use after the OS has been installed.
Typically you only need to manually specify this value if it is not automatically determined.
Boot Netmask
For Linux provisioning, enter the netmask value that of the network interface that the target system will use for
OS provisioning, if required.
Boot Gateway
For Linux provisioning, enter the IP address of the gateway for the network interface that the target system will
use for OS provisioning, if required.
Boot Host Name
For Linux provisioning, enter the host name that the target system will use for OS provisioning, if required.
Boot Name Server
For Linux provisioning, enter the IP address or host name of the name server that the target system will use for
OS provisioning, if required.
Kernel Parameters
For Linux provisioning, enter kernel parameters for the GRUB menu of the target system, if necessary.
Domain Name
For Solaris provisioning, enter the DNS domain name that the target system will use, if required.
Boot Path
For Solaris provisioning, select a physical device name from the Boot Path list, if the target system requires that
you specify it manually.
6. In the Configuration panel, click Next.
The Summary panel is displayed.
7. Click Provision to submit the OS provisioning job.
A message indicates that the OS provisioning job has been submitted. Click OK to dismiss the message.
The Provision OS wizard will give an error message if the Boot IP address is not in the subnet of any of the Proxy
interfaces or DHCP subnets.
You can view the status of the provisioning job from the Jobs panel.
Install Protocol
For Linux provisioning, select HTTP or NFS.
IP Address
Enter the IP address for the target system. This field is displayed only if you select Static IP in the Network
Protocol field, and the target consists of a single system. This is a required field when it is displayed. Use IP
addresses that are not defined as part of a subnet that is managed by the DHCP server on a Proxy Controller.
See Subnets for more information.
IP Address Ranges
Enter the IP address ranges for the target. This field is displayed only if you select Static IP in the Network
Protocol field, and the target consists of multiple systems. You can specify IP addresses as a comma-separated
list, and address ranges using two IP addresses separated by a dash, for example, 10.5.3.10-10.5.3.20. This
is a required field when it is displayed. Use IP addresses that are not defined as part of a subnet that is managed
by the DHCP server on a Proxy Controller. See Subnets for more information.
Boot IP
For Linux provisioning, enter the IP address of the network interface that the target system will use for OS
provisioning. This field displays only if the target consists of a single system. This is a required field when it is
displayed. Use IP addresses that are not defined as part of a subnet that is managed by the DHCP server on a
Proxy Controller. See Subnets for more information.
Boot IP Ranges
For Linux provisioning, enter the IP address range of the network interface that the target systems will use for
OS provisioning. This field displays only if the target consists of a multiple systems. You can specify IP addresses
as a comma-separated list, and address ranges using two IP addresses separated by a dash, for example,
10.5.3.10-10.5.3.20. This is a required field when it is displayed. Use IP addresses that are not defined as
part of a subnet that is managed by the DHCP server on a Proxy Controller. See Subnets for more information.
Netmask
Enter the netmask value that the target will use after the OS has been installed.
Gateway
Enter the gateway value that the target will use after the OS has been installed.
Host Name
Enter the host name that the target system will use after the OS has been installed. This field is active only if the
target consists of a single system.
Name Server
Enter the IP address or host name of the name server that the target will use after the OS has been installed.
Console Serial Port
To monitor the installation using a serial connection, select the correct console serial port device from the
Console Serial Port list.
Console Baud Rate
To monitor the installation using a serial connection, select the correct serial port device baud rate from the
Console Baud Rate list.
Network Device
Select the device for the network interface that the target will use after the OS has been installed. Typically you
only need to manually specify this value if it is not automatically determined.
Boot Netmask
For Linux provisioning, enter the netmask value of the network interface that the target will use for OS
provisioning, if required.
Boot Gateway
For Linux provisioning, enter the IP address of the gateway for the network interface that the target will use for
OS provisioning, if required.
Boot Host Name
For Linux provisioning, enter the host name that the target system will use for OS provisioning, if required. This
field is active only if the target consists of a single system.
Boot Name Server
For Linux provisioning, enter the IP address or host name of the name server that the target will use for OS
provisioning, if required.
Kernel Parameters
For Linux provisioning, enter kernel parameters for the GRUB menu of the target, if necessary.
Domain Name
For Solaris provisioning, enter the DNS domain name that the target will use, if needed.
Boot Path
For Solaris provisioning, select a physical device name from the Boot Path list, if the target system requires that
you specify it manually. This field is displayed only if the target consists of a single system.
7. In the Configuration panel, click Next.
With more than one target to provision, and with Configure the Targets One at a Time selected, the Provision
OS wizard selects the next target which requires configuration information. Specify configuration information
for all targets, and click Next. The Summary panel is displayed.
7.
Oracle Enterprise Manager Ops Center
With only one target to provision, or with Configure All Targets selected, the Summary panel is displayed.
8. Click Provision to submit the OS provisioning job.
A message indicates that the OS provisioning job has been submitted. Click OK to dismiss the message.
The Provision OS wizard will give an error message if the Boot IP address is not in the subnet of any of the Proxy
interfaces or DHCP subnets.
You can view the status of the provisioning job from the Jobs panel.
i. Console Serial Port To monitor the installation using a serial connection, select the correct console serial port
device.
j. Console Baud Rate To monitor the installation using a serial connection, select the correct serial port device
baud rate.
k. Network Device Select the device for the network interface that the target system will use after the OS has
been installed. Typically you only need to manually specify this value if it is not automatically determined.
l. Domain Name Enter the DNS domain name that the domain will use, if required.
m. Boot Path Select a physical device name from the Boot Path list, if the target domain requires that you specify
it manually.
6. In the Configuration panel, click Next.
The Summary panel is displayed.
7. Click Provision to submit the OS provisioning job.
A message indicates that the OS provisioning job has been submitted. Click OK to dismiss the message.
Provision Firmware
Ops Center automates firmware provisioning at a single chassis or system level, and at data center level. The provisioning process
is similar, regardless of the hardware, operating system, or underlying technology that you are deploying.
Firmware provisioning enables you to install firmware updates on a server by using firmware images and firmware profiles.
At a high level, provisioning firmware involves the following steps:
1. Importing a firmware file with the associated metadata into the Firmware Library.
2. Creating firmware profiles based on one or more firmware images.
3. Updating firmware based on the profile and its associated firmware images or by applying updates based on the output
of a Firmware Compliance report.
Firmware Images
This section describes how to create, edit, view, and delete firmware images as well as how to determine firmware metadata and
locate the default image location on the Enterprise Controller.
To determine if the system needs to be powered off prior to updating the firmware:
a)To update the Sun System Firmware, the system must be powered off
(i.e. in standby mode).
Based on the preceding information, you would provide the following metadata information for the firmware update:
Available platforms Sun Fire T2000
Type VBSC
Version 1.1.1
Require power off Yes
For this example, the VBSC firmware subcomponent/type with version 1.1.1 was used. You can use any of the other types such as
ALOM-CMT:1.1.2 or OBP:4.20.0. However, you must ensure that the version specified is always the firmware subcomponent/type.
Failure to do so may result in the firmware update operation failing or not being performed.
Firmware Profiles
This section describes how to create, edit, view, and delete firmware profiles.
Firmware Updates
You can use a profile or a Firmware Compliance report to provision or update your firmware. Most firmware updates to the
Service Processor require that the server be shut down prior to the firmware update. If the firmware image has the power off
option selected, this is a hard shutdown of the system and you must gracefully bring down the OS prior to attempting updating
the firmware.
Updating Firmware
Firmware profiles are used to update your firmware. Most firmware updates to the Service Processor require that the server be
shut down prior to the firmware update. If the firmware image has the power off option selected, this is a hard shutdown of the
system and you must gracefully bring down the OS prior to attempting updating the firmware.
The hardware component is unavailable for service during the firmware update. If a network failure occurs during the update,
you must update the firmware again. Failure to do so might result in display of an incomplete firmware inventory list.
To Update Firmware
1. Expand All Assets in the Navigation panel.
2. Click on Systems or Chassis.
3. Click Update Firmware in the Actions panel.
The Update Firmware wizard is displayed.
4. In the Select a firmware profile window, select a firmware profile and click Next.
5. Select the targets for updating the firmware, then click Next.
6. Review the details in the Summary screen and click Update to update the firmware.
7. To track the progress of the firmware update, go to the Jobs section of the BUI and view the job status.
8. Reset the server after the Update Firmware job completes.
Note Automatic reboot of the hardware component upon completion of the firmware update is not supported.
In the XSCF service processor, create a user that has platadm privileges.
Use the user name and password that have the platadm permissions when managing the servers.
Manually configure the domains.
Create a group for the SPARC Enterprise M-Series servers and add the servers to the group.
Assign the Ops Center Admin role to the group.
6. Discover the SPARC Enterprise M-Series Server to discover the server in Ops Center.
7. Power off the domains before doing a firmware upgrade from the Ops Center BUI.
Note To successfully perform M-Series discovery and firmware provisioning, the XSCF service processor account must have a
user with platadm privilege.
{FF}XCP{VVVV}.tar.gz
{DC}XCP{VVVV}.tar.gz
{IK}XCP{VVVV}.tar.gz
2. If required, uncompress any files that provide the specific firmware file and its associated README. These files may be
stored on the local file system or an NFS mounted file system.
3. Check the firmware update's README file for metadata.
4. Create a firmware image through the BUI.
a. Click Libraries in the Navigation panel.
b. Click Firmware Images.
c. Click Create Firmware Image in the Actions panel.
The Create Firmware Image wizard is displayed.
d. Type the firmware image name and description.
The image name must be the same as the firmware file name, for example, FFXCP1080.tar.gz.
e. Select the firmware image file from the Enterprise Controller, then click Next. If you do not have the image file
in the Enterprise Controller, upload the image file from your local system to the Enterprise Controller.
f. Select the supported platforms for the firmware image, then click Next.
g. Specify the type and version of the firmware image.
Note The firmware image version must match the version number in the firmware image file.
For example, if you create a firmware image for the image file FFXCP1080.tar.gz, the version number
entered from BUI must be 1080.
h. Select the firmware images that this firmware image depends on.
Note XCP firmware upgrades do not require a hard shutdown of SPARC Enterprise M-Series platform. XCP
firmware upgrades can be performed with running domains. After upgrading the firmware, reboot the domains.
i. Review the details in the Summary screen and click Finish to create a firmware image.
To Update Firmware
1. Expand All Assets in the Navigation panel, then click Chassis.
2. Click M-Series.
3. Click Update Firmware in the Actions panel.
The Update Firmware wizard is displayed.
4. In the Select a firmware profile, select a firmware profile and click Next.
5. Select the targets for updating the firmware, then click Next.
6. Review the details in the Summary screen and click Update to update the firmware.
7. To track the progress of the firmware update, go to the Jobs section in the BUI and view the job status.
8. Reset the server after the Update Firmware job completes.
Note Automatic reboot of the hardware component upon completion of the firmware update is not supported.
Update an OS
Ops Center enables you to update, or patch, the following operating systems:
Solaris software
Linux
Windows
Several update reports and methods of patching are available, depending on the OS type. In some cases, you can use profiles and
policies to define how patches are applied and how the update job runs. You can also create, modify, and compare system
catalogs, and create a profile from a system catalog. The reports and update methods are discussed in detail in the OS-specific
update sections.
About Updating an OS
Using Ops Center, operating systems are secure and current. You can patch the following operating systems:
Solaris 8, 9, and 10 (SPARC)
Solaris 10 (x86)
Red Hat Linux Advanced Server 3, 4, and 5
SUSE Linux Enterprise 8, 9, and 10
Microsoft Windows
The processes for installing patches on Solaris and Linux operating systems are very similar. The process for updating Windows is
different. Detailed information is available in each OS-specific section.
Managing Systems
Before you can use Ops Center to patch and update an OS, you must discover the OS to gather identification for each operating
system and then you must manage the OS to install the agent controller software. The agent controller software allows Ops
Center to check the current condition of the operating system and to perform update operations.
When you manage an OS, the following actions occur:
1. The Agent is registered. This might take five minutes. Until the agent is registered, you cannot perform any update
functions.
2. A Notification is displayed when the agent OS update functionality is enabled. The agent is registered and the Target
Selector is enabled.
3. The agent runs an inventory check and creates an OS Update Catalog for the system.
4. A notification is displayed when the OS Update Catalog is available. The OS Update Catalog actions are enabled.
Obtaining Patches
By default, Ops Center software downloads patches and new software using Internet access. The Enterprise Controller is
connected to the Internet and to the Solaris Knowledge Services database. You can configure Ops Center to connect to third
party vendors, such as Red Hat, and provide authentication details. When you run an update job, the patches are downloaded
from the corresponding site. For example, Solaris OS patches are available from the SunSolve web site and Red Hat patches are
available from the Red Hat site.
Ops Center downloads only signed patches from SunSolve or EIS DVD. The patches must be in the jar or jar.gz format or in the
patch directory.
If your data center cannot have direct Internet access, configure the software to operate in Disconnected mode. In this mode, the
Enterprise Controller is not connected to the Internet and you must upload all content, such as patches, to the Enterprise
Controller. To obtain the patches and packages, you must run the harvester script on a system outside of the data center that
does have Internet access. You then save the downloaded information to a portable media device, such as a CD or DVD, and bring
it to your data center for manual upload. The uploaded software is stored in the Local Content section of the Updates Library.
Another option is to run your Enterprise Controller in Disconnected Mode until you need to download patches or packages. You
then change the Enterprise Controller's mode to Connected only to download the required patches and packages, and then
change back to the Disconnected mode.
Reports
Several OS Update reports are available. Reports are OS-specific, but many reports check for new patches and security advisories.
You can get a general report, or test a system or installed package for available fixes. For auditing purposes, you can create a Ops
Center job history report.
Detailed information is available in each OS-specific section. When you create a report, you select the criteria that are relevant to
you, such as a list of hosts that have a specific patch or a list of hosts that do not have a specific patch. You can export the results
of most reports to a CSV format.
For Solaris Baseline Analysis Reports, you can run the report much quicker if you run a patch simulation and do not download the
patches.
The BUI supports column-based sorting in the Report Results section for all the OS Update reports except for Job History Report
and Baseline Analysis Report. Clicking on any field in the header part of the results table in the center panel will sort the results of
that column.
Update Job
Ops Center contains the following options in an update job to maintain control and consistency across your data center:
Groups Help you to organize the display of assets in the user interface and act as targets for many types of jobs.
Roles Enable you to determine the tasks that a user can perform on a specific asset, or a group of assets.
Update Profiles Define what you will allow, or not allow, to be installed on a target. You can select from a list of
predefined profiles, your existing custom profiles, or you can create a new profile by modifying an existing profile.
Update Policies Define how a job is performed and sets the automation level of the job. You can select from a list of
Solaris OS Patching
The following package and patch services and features are supported for patching the Solaris OS in Ops Center:
Recommended patch clusters
Solaris baseline reports
Custom packages
Active dependency rules
Patch analysis
Job simulation
Job scheduling
Rollback and recovery
You can use Solaris Live Upgrade to update your Solaris software or you can update your Solaris Containers and zones.
Linux OS Patching
The following package and RPM installation services and features are supported for patching Linux systems in Ops Center:
Linux Red Hat Package Manager (RPM)
Custom packages
Active dependency rules
Patch analysis
Job simulation
Job scheduling
Rollback and recovery
Windows OS Patching
The following features are supported for patching Windows systems in Ops Center:
Patch analysis
Job scheduling
Using Profiles and Policies to define and control the job (Solaris and Linux only)
Solaris and Linux OS use profiles and policies to manage update jobs, use your own files and scripts in Ops Center, and create
snapshots (known as system catalogs.)
OS Update Capability
Service
Solaris OS
Linux
Windows
Zones
Branded Zones
Patch analysis
Yes
Yes
Yes
Yes
Yes
Job simulation
Yes
Yes
No
Yes
Yes
Job scheduling
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Custom packages
Yes
Yes
No
Yes
Yes
Yes
Yes
No
Yes
Yes
OS Update Reports
Several predefined OS Update reports are available. The reports enable you to check for new patches and security advisories. You
can get a general report, or test a system or installed package for available fixes. For auditing purposes, you can create a Ops
Center job history report.
When you create a report, you select the criteria that are relevant to you, such as a list of hosts that have a specific patch or a list
of hosts that do not have a specific patch. You can export the results of most reports to a CSV format.
Reports
Solaris OS
Linux
Windows
Zones
Branded Zones
Baseline Reports
Yes
No
No
Yes
Yes
Yes
Yes
No
Yes
Yes
Yes
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
Yes
Yes
Yes
No
Yes
Yes
No
Yes
No
Yes
Yes
Enables You To
Admin
Update
Update Sim
Provision
Manage
An Admin can assign a user role for a specific asset, such as the Enterprise Controller, or an asset group. When a user is assigned
a group role, the user also has the same permissions to all subgroups.
To update multiple operating systems with a single job, you must use a homogeneous OS group as the target. See Using Groups
for information about how to create a group and add operating systems to the group. Homogeneous groups contain the same
release of an OS.
To update a Linux OS, you must provide your Red Hat or SuSe login credentials. Ops Center uses the credentials to log in to the
third-party site and download the patches or packages. To provide or update your SunSolve or third-party vendor credentials, see
Authentications.
Admin Authorization
Task
Admin
Non-Admin
Reports
Yes
Yes
Yes
Yes
Yes
Yes, if you have the Update or Update Sim role for the OS
targets
Yes
Yes
Job Submission
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes, if you have the Update or Update Sim role for the OS
targets
Yes
Answer questions
Yes
Yes, if you have the Update or Update Sim role for the job
targets
Rerun job
Yes
Yes, if you have the Update or Update Sim role for the job
targets
Yes
Yes
Profile/Policy Management
Create Profile/Policy
Yes
No
Yes
Edit Profile/Policy
Yes
Delete Profile/Policy
Yes
View Profile/Policy
Yes
Yes
Yes
Yes
Administration
Edit Authentications
Yes
No
Yes
No
Yes
No
Note You must have root permissions to view system profiles/policies. You cannot view system defined profile/policy from job.
OS Update Profiles
Profiles specify which components are to be installed and which are prohibited, and the action to be performed on a system. A
profile defines the component configuration of the systems that you want to manage.
Use profiles to accomplish the following:
Manage multiple systems in a consistent manner
Automate repetitive administration jobs
Record the requirements of your enterprise
Automatically create servers and workstations
Manage dependencies and ensure consistency
The profile settings Required, Not Allowed, and Upgrade affect a managed host only during the actual deployment of the profile.
After deploying a profile, you could run another job that contradicts the settings of the profile; therefore, you should thoroughly
understand your system settings and requirements.
Note If a conflict occurs between a profile and policy, the profile overrides the policy.
Predefined Profiles
Predefined profiles are provided to perform common system-wide checks and to automate the operating system updates. These
profiles cannot be edited or deleted. When creating a new job with a predefined profile, you must also include a policy. The
policy determines the trends and automation of the deployment of the complete profile.
The predefined profiles in Ops Center are shown here.
Perform Reboot + Reconfigure Restarts the selected system and performs specific post-installation configurations.
Upgrade All Components Checks the installed component against the Enterprise Controller of the selected distribution
to see if the installed components can be upgraded.
As components are added to the profile, Profile Contents shows the Component Name, Distribution, and type of action.
To remove a component from the list, select the component from Profile Contents list and click Remove from Profile.
Note The user interface should not allow you to select an illegal combination of actions; for example you cannot mark the same
package as both Required and Uninstalled. However, this does not guarantee that the set of actions in the Profile has a legal
solution. The UI does not check for dependencies or conflicts, this is handled by the Dependency Resolver on the target when the
job is processed.
As stated earlier, profiles cannot be nested or combined. It is possible to import the actions from another profile by selecting the
profile and clicking Required, but it must be stressed that this causes the actions from that profile to be copied into the current
profile. Future edits to the other profile will not affect this one.
To Edit a Profile
1.
2.
3.
4.
5.
6.
To Delete an OS Profile
1.
2.
3.
4.
5.
Note This marks the profile as deleted in the database; it can no longer be accessed through the UI and will not appear in the
lists. Completely removing the profile, or recovering a deleted profile, is a task for a database administrator and is beyond the
scope of these instructions.
OS Update Policies
When an OS Update job is executed, the dependency resolver examines the profile to determine what actions to take and in what
order. Often there will be dependencies on other components, actions that must be performed in single user mode, a
requirement to reboot the target operating system, etc. By default the user will be prompted to confirm or reject each of these
steps during a question and answer exchange. The user can provide answers to the questions in advance by supplying a policy.
A policy is a list of actions that are explicitly approved or denied. They can be created by the user in advance of submitting a job;
alternatively the question and answer exchange when a job is executed can be saved as a policy for future re-use.
As with profiles, policies can contain actions relating to more than one operating system.
There are a number of system policies which can be used to automate the update jobs.
Policy settings are hierarchical; if there is not a policy setting for a component then the policy for that component's parent
applies, and so on. For example, it is possible to create a policy that allows the system to install a given component but prohibits
installation of certain specific versions of that component, or vice versa.
Note The policy only applies to actions that are implicitly generated by the dependency resolver. If a conflict occurs between a
profile and policy, the profile overrides the policy.
Parameter
Ask Me
Yes
No
Install or
Uninstall
Upgrade
from or
Downgrade
from
Apply Fix
Ignore File
Conflict
A file conflict will occur if the selected component provides a file that cannot be installed on a machine with a file provided by
another component that is already installed. If both components are certified, the rules of the knowledge base handle
deployment without conflicts. If one or both are local components that are not in the knowledge base, the conflict will cause the
job to fail.
Note Do not set the Ignore File Conflict setting to Yes unless you know the conflict.
If a policy has the Ask Me action, the job pauses for confirmation before continuing. The user will receive a notification that there
is a job waiting for an answer. Click Jobs to view the job status. If a job is paused, the Waiting User Input icon appears in the
status column. Click the icon to answer the questions.
4. A default policy name is provided. Edit the policy name and add a brief OS Policy Description.
5. Select the distribution from which you want to select a component.
6. Select a category or component.
6.
Expand a category to display the available components.
7. Click on the component for which you want to specify policy values
8. Set the policy values for each action.
Once an action has been set for a component that component will appear in the Policy Contents area.
9. Repeat for additional components.
10. Click Save as Named Policy.
The policy appears in the OS Update Policies Summary page.
Note It is important to know that policy value changes apply to the component currently selected in the component tree. To
make additional changes to a component, it is necessary to find that component in the tree again. Selecting the entry under
Policy Contents has no effect.
System Catalogs
A system catalog is a list of OS software components that are installed on a particular managed system. An initial catalog is
created after the system is discovered and managed.
Once an operating system is available and selected, catalogs can be viewed and modified, and historical catalogs (snapshots of the
system) of the component can be created.
Modifying a catalog is an alternate option for running an OS update job to install, uninstall, or upgrade a component. Modifying a
catalog does not require an OS update profile to run the update job. It is a quick way of changing the component configuration
in a system.
System catalogs of two managed systems can be compared. You can view the summary of the comparison and also have the
option to make the target system the same as the source system.
Catalogs provide the capability to directly manipulate the installed software components on a single operating system or a group
of operating systems. Alternatively, a catalog can be saved as a profile, and then an OS update job can be run using this profile.
Use the Compare Catalogs option to change the software components of a particular operating system to that of the source
system.
Note If you have an alternate boot environment (ABE), you cannot create and compare catalogs until you activate the ABE. By
default only the catalogs of the active BE are compared.
To view differences between a target and one of its ABEs, perform the following tasks:
1. Create a snapshot of the current BE.
2. Activate the ABE.
3. Wait for the Activate job to finish and for the catalog of the ABE to be reported. Check the notification alerts. When the
activation is completed, an OS Update Inventory is Available message appears.
4. Select the snapshot created in step 1 as the source.
5. Select the new BE (previous ABE) to compare as the target.
Tasks to Make Target Like Source - Creates the list of components that needs to be installed on the target system. Select
Include for the components that you want to install on the target system.
a. Click Create Job to Copy the source to the Target.
The New Job wizard is displayed.
b. Complete the job information in the wizard.
c. Either click Run Now to run the job immediately or click Next to schedule the job to run later.
To View a Catalog
1. Select Assets from the Navigation panel.
2. Select an OS from Assets section. You can restrict the display of assets to only operating systems by using the View pane.
The center panel displays summary, connectivity, file system monitoring, charts, and jobs information.
3. Select View/Modify Catalog from the Actions panel.
The View/Modify Catalog window is displayed. The current catalog is displayed by default.
4.
The installed components are displayed.
To Modify a Catalog
1. Select Assets from the Navigation panel.
2. Select an OS from the Assets section.
The center panel displays summary, connectivity, file system monitoring, charts, and jobs information.
3. Select View/Modify Catalog from the Actions panel.
The View/Modify Catalog window is displayed.
4. Select a catalog from the Catalog list.
The components that are installed on the system are displayed.
5. Select the component for which you want to modify the action.
The available actions are No Action, Required, Uninstall and Upgrade. The actions that are available for the selected
component are enabled accordingly.
6. Select the action for the component that you want to modify.
7. Click Launch Modification Job.
A New Job wizard is displayed.
8. Complete the job Information details as required.
9. Either click Run Now to run the job immediately or click Next to schedule the job later.
Updating a Solaris OS
You can update a Solaris operating system after you have discovered it and managed it. A managed asset has Ops Center agent
software installed on it.
To keep your systems current, use the System Catalogs and Solaris OS Update Reports to determine which patches, updates,
software, and actions apply to your system.
2. Select an OS instance.
3. Click New Update OS Job from the Center or Actions panel.
3.
The New Update OS Job wizard is displayed. The Job Information window is displayed first.
4. Enter a name for the update job.
5. Select the Target Setting:
Use the same Targets for all tasks in the job
Use different Targets for each task in the job
6. Select a Run type:
Simulation Enables you to run a job simulation without downloading patches.
Download Click the Download check box to download the patches as part of the job simulation.
Actual Run Enables you to download the patches and run the update job.
7. Select the Task Execution Order:
Sequential
Parallel
8. Select the Task Failure Policy:
Complete as much of job as possible
Stop at failure and notify
9. If you want to use an alternate boot environment (ABE) and run ABE pre-action scripts, see the procedures in Updating
With Solaris Live Upgrade.
10. Click the Add ( + ) icon to add more tasks to the update job.
You can define the profile, policy, and target for each task. If the target setting is a different target for each task in the
job, then the new task includes the Select Targets button. Click Select Targets to select the target for the task.
11. To change the profile or policy, click the appropriate cell for the target to display a drop-down menu. Select the profiles
and policies from the menus.
Note If there is a conflict between a profile and policy, the profile overrides the policy.
12. To change the selected target system, select the row and click Edit Targets.
The Select Targets window is displayed. Select the targets on which you want to run the update job. You can select more
than one target.
13. Determine how you want to run the job:
To schedule the job to run later, click Next.
To run the job immediately, click Run Now.
14. Select a schedule option.
Now Starts the update job immediately.
Start Date Enables you to define a start date.
On a Recurring Schedule Enables you to create a recurring schedule.
15. Click Next to display the Job Summary. Click Finish to run the update job according to the defined configuration and
schedule.
4.
5. Enter a name and description for the update job in the Job Information window.
6. Select the Run Type for the job. It can be either Simulation or Actual Run.
7. Make your selections for the following:
Task Execution Order
Target Setting
Task Failure Policy
Boot Environment Type
Run ABE Pre-action Script
8. Select the profile and policy from the pull-down menu under the Profile and Policy columns in the Tasks table.
9. Click on the link below the Targets column in the Task table to select the target for the task.
The Select Targets window is displayed. Select the target on which you want to run the update job and click Add to
Target List. You can select more than one target.
10. Click Select in the Select Targets window.
11. Click Run Now to run the job immediately or click Next to schedule the job to run later.
Solaris baselines contain a list of dated baselines. This report helps to check the compliance of your systems against the newly
releases baselines.
Refer to Baseline Analysis Report to generate a BAR. After you submit the job to run the report, the report result is displayed in
the Report Results of the Update Reports Summary window.
3. (Optional) Click Export to CSV to export the report result in CSV format.
4. Select the host for which you want to view the result.
The report for the host is displayed.
The report lists the patch number, the operation required (install or uninstall), and the link to patch information in the
SunSolve web site.
5. Click Run Compliance Job to update the patches.
The New Job wizard is displayed.
6. Select the job information as required.
7. Click Run Now to run the job immediately or click Next to schedule the job to run later.
The job is submitted and updates the managed system to the selected baseline.
environment.
Maintain multiple boot environments with different images. For example, you can create one boot environment that
contains all current patches and another that contains only security patches.
Description
Boot Environments
Describes how Solaris Live Upgrade uses and shares file systems.
Provides a list of required patches and packages needed to use Solaris Live Upgrade.
Describes the special patching instructions needed to use Live Upgrade with Solaris
8 OS.
Boot Environments
A boot environment is the set of all file systems and devices that are unique to a Solaris OS instance on a system. A dual boot
environment consists of a live boot environment (BE) and an inactive alternate boot environment (ABE).
Disk Requirements
File Systems
Displaying Boot Environment Details
Synchronizing Boot Environments
Disk Requirements
In general, you must follow the general disk space requirements for an upgrade.
When you create a boot environment, the space requirements are calculated. You can estimate the file system required to create
a boot environment by starting to create a new boot environment and then canceling the process after the space requirements
are calculated.
The disk on the new boot environment must be able to serve as a boot device. Some systems restrict which disks can serve as a
boot device. Refer to your system's documentation to determine if any boot restrictions apply.
The disk might need to be prepared before you create the new boot environment. Check that the disk is formatted properly:
Identify slices large enough to hold the file systems to be copied.
Identify file systems that contain directories that you want to share between boot environments rather than copy. If you
want a directory to be shared, you need to create a new boot environment with the directory put on its own slice. The
directory is then a file system and can be shared with future boot environments. For more information about creating
separate file systems for sharing, see Guidelines for Selecting Slices for Shareable File Systems in the Solaris Live Upgrade
documentation.
File Systems
When using alternate boot environments with Solaris Live Upgrade, file systems are categorized into the following types:
Critical File Systems
Shareable File Systems
Swap
Reconfiguring a Disk
You can reslice, or partition, the disk before creating the new boot environment and put the shareable file system on its own
slice. For example, if the root ( / ) file system, /var, and /home are on the same slice, reconfigure the disk and put /home on its
own slice. When you create any new boot environments, /home is shared with the new boot environment by default.
If you want to share a directory, the directory must be split off to its own slice. The directory is then a file system that can be
shared with another boot environment. You can use the lucreate command with the -m option to create a new boot
environment and split a directory off to its own slice. But, the new file system cannot yet be shared with the original boot
environment. You need to run the lucreate command with the -m option again to create another boot environment. The two
new boot environments can then share the directory.
Swap
Swap depends on the type of file system:
For UFS file systems, swap is a special shareable volume. Like a shareable file system, all swap slices are shared by default.
If you specify a destination directory for swap, the swap slice is copied.
For ZFS file systems, swap and dump volumes are shared within the pool.
must boot into the alternate boot environment to get an accurate comparison.
The following types of information is available for associated boot environments:
Name and description
Status
Active The current boot environment
Inactive Alternate boot environments that are available for activation and use
Invalid The ABE is not available for activation.
File System location and description
Device size, mount location and options
Date and time that the ABE was last synchronized
From this panel you can choose which ABE to activate and schedule when to activate it. You can also choose to synchronize (also
known as sync) the boot environments.
Reconfiguring a Disk
You can reslice, or partition, the disk before creating the new boot environment and put the shareable file system on its own
slice. For example, if the root ( / ) file system, /var, and /home are on the same slice, reconfigure the disk and put /home on its
own slice. When you create any new boot environments, /home is shared with the new boot environment by default.
If you want to share a directory, the directory must be split off to its own slice. The directory is then a file system that can be
shared with another boot environment. You can use the lucreate command with the -m option to create a new boot
environment and split a directory off to its own slice. But, the new file system cannot yet be shared with the original boot
environment. You need to run the lucreate command with the -m option again to create another boot environment. The two
new boot environments can then share the directory.
Swap
Swap depends on the type of file system:
For UFS file systems, swap is a special shareable volume. Like a shareable file system, all swap slices are shared by default.
If you specify a destination directory for swap, the swap slice is copied.
For ZFS file systems, swap and dump volumes are shared within the pool.
In the following example, a swap slice is specified. The new boot environment contains the root ( / ) file system on
c0t1d0s0. A new swap file system is created on c0t1d0s1. No swap slice is shared between the current and new boot
environment.
In the following example, a swap slice is added and another swap slice is shared between the two boot environments.
The new boot environment contains the root ( / ) file system on c0t1d0s0. A new swap slice is created on c0t1d0s1.
The swap slice on c0t0d0s1 is shared between the current and new boot environment.
-m -:/dev/dsk/c0t1d0s1:swap
Note A boot environment creation will fail if the swap slice is being used by any boot environment except for the current boot
environment. If the boot environment was created using the -s option, the alternate-source boot environment can use the swap
slice, but not any other boot environment.
Required Patches
The list of required patches is channel-specific. Additional patches are required for a system that is running zones.
Note You cannot use Solaris Live Upgrade to patch your boot environments if you created or migrated a zone in Ops Center, or
if the global zone contains zones in separate zpools.
The latest list of required patches is available on SunSolve. This page contains information about Solaris Live Upgrade that is not
relevant to patching in Ops Center. The relevant information is located in the section titled Patch Lists for full Live Upgrade
Feature Support.
The following patch is required in addition to the Solaris Live Upgrade patches detailed in SunSolve:
125952-1 Fixes a webconsole bug (CR 6751843) in Solaris which causes shutdown, and the live update activation
operation, to hang for a couple of hours.
Required Packages
The following packages are required to successfully upgrade a system using an ABE.
SUNWadmap
SUNWadmlib-sysid
SUNWadmr
SUNWlibC
SUNWgzip (only for Solaris 10 3/05)
SUNWj5rt (Required if you upgrade and use CD media)
If you installed Solaris 10 using any of the following software groups, you should have the required packages:
Entire Solaris Software Group Plus OEM Support
Entire Solaris Software Group
Developer Solaris Software Group
End User Solaris Software Group
If you install one of these Software Groups, then you might not have all the required packages:
Core System Support Software Group
Reduced Network Support Software Group
% pkginfo package_name
3. Install the new Solaris Live Upgrade packages from the release to which you are upgrading. For instructions, see Installing
Solaris Live Upgrade.
4. Before running Solaris Live Upgrade, install the required patches to ensure that you have all the latest bug fixes and new
features in the release. Search for the info doc 206844 (formerly 72099) on the SunSolve web site to get the latest list of
patches.
If you are storing the patches on a local disk, create a directory such as /var/tmp/lupatches and download
the patches to that directory.
From the SunSolve web site, obtain the list of patches.
Change to the patch directory.
# cd /var/tmp/lupatches
# patchadd patch_id
patch_id is the patch number or numbers. Separate multiple patch names with a space.
Note The patches need to be applied in the order that is specified in info doc 206844.
Reboot the system if necessary. Certain patches require a reboot to be effective.
x86 only: Rebooting the system is required or Solaris Live Upgrade fails.
# init 6
You now have the packages and patches necessary for a successful migration.
Reports
You can run all available reports for the active BE, including compliance reports. Reports are generally not available for the ABE,
and any reports are typically outdated.
To view a current report for an ABE, you must reboot into it to make it the active BE and then manually take a snapshot. The
snapshot does not maintain an association with the active or alternate boot environment. To maintain an accurate historical
record, add details about the snapshot and boot environment in the description field.
Catalogs
An update catalog is an OS inventory of your OS and is automatically created when you manage a system. When you have a dual
boot environment, the OS Update catalog displays the name and description of the active boot environment.
The catalog is the inventory of the active boot environment. To view the current inventory of an ABE, you must make it the active
boot environment and create a historical catalog (snapshot).
When you create the snapshot, manually specify the system. The snapshot is of the current active boot environment and does not
indicate that the system might be an ABE.
Viewing and updating an OS Update catalog for a boot environment is the same as other OS catalog.
If you do not specify a swap slice, the swap slices belonging to the current boot environment are configured for the new
boot environment.
If you specify one or more swap slices, these slices are the only swap slices that are used by the new boot environment.
The two boot environments do not share any swap slices.
You can specify to both share a swap slice and add a new slice for swap.
The following examples show the three ways of configuring swap. The current boot environment is configured with the root {{ / }}
file system on c0t0d0s0. The swap file system is on c0t0d0s1.
Creating an ABE
To create an alternate boot environment (ABE), you must use the lucreate command, which is part of a suite of commands
that make up the Live Upgrade feature of the Solaris software. If you use Ops Center to create the ABE, the script must return 0
on success and non-zero on failure. See the lucreate man page for the available options and examples.
These methods are available to create an ABE:
Upload an lucreate script as Local Content in Ops Center. Run an OS update job and specify a pre-action which runs
the lucreate script. You can select multiple compatible targets and create an ABE for each target using the same script
at the same time.
Upload an lucreate script as Local Content in Ops Center, create an OS Profile, and then run an OS Update job.
Use an lucreate script from the command line to create the ABE. In this option, you must log in to each agent and run
the script to create the ABE.
When you create the ABE with an OS Update job, You can choose to run the job immediately, or you can schedule the job to run
during your maintenance window. In all methods, the new boot environment is automatically discovered and a new Boot
Environment tab will appear in the center panel for OS management.
This task describes how to run a New OS Update job to create the ABE. Although it is a New OS Update job, the sole purpose of
the job is to create an ABE. The job will use the lucreate that you uploaded to Local Content to create a duplicate of your boot
environment.
Note Do not use Live Upgrade on your Enterprise Controller or Proxy Controllers. Live Upgrade does not synchronize all of the
files that are required for these Ops Center components.
To Create an ABE
1. Upload a script as a pre-action.
a. Click Libraries in the Navigation panel.
b. Click Local Content in the Solaris/Linux OS Updates library.
c. Click Upload Local Action.
The Upload Local Action window is displayed.
d. Type a name and description for the action. The name should be clearly understood. For example,
ABE_Create_S10_5/09_SPARC.
e. Select the Pre-Actions Action type.
f. Select the Distribution.
g. In File to Upload, browse for and select the create script to upload, then click Upload.
2. Create a profile and define the ABE create script as the pre-action.
a. Click Update Profiles in the Updates Library.
b. Click New Profile from the Actions panel.
The New OS Update Profile window is displayed.
c. Type a name and brief description of the new profile.
d. Select the OS Distribution from the drop-down list.
e. Search for your ABE create script, or expand Local in the OS Update Components tree and select the script from
the Pre-actions category.
f. Click Required.
g. Click Save as Named Profile.
3. Create a new OS Update job that uses your pre-action script and the ABE profile that you created in the previous step.
4. Click New Update OS Job in the Actions panel.
The New Update OS Job wizard is displayed. The Job Information window is displayed first.
8. When the job completes, the ABE is created and associated with the OS. To verify that the ABE was created, click the OS
in the Assets panel. The Boot Environment tab appears in the center panel. Click the Boot Environment tab to display the
new ABE, as specified in the lucreate script. An OS can have multiple associated ABEs.
8.
Note The Boot Environment tab is only displayed if there is at least one ABE associated with the OS.
Updating an ABE
You can create a customized update job, including the option to use an alternate boot environment (ABE) to perform a live
upgrade of your Solaris 10 OS. With Live Upgrade, you create an inactive ABE, update and patch the ABE, synchronize the ABE
and BE, and then switch boot environments. When you switch boot environments, the patched and tested ABE becomes the active
boot environment.
Note Do not use Live Upgrade on your Enterprise Controller or Proxy Controllers. Live Upgrade does not synchronize all of the
files that are required for these Ops Center components.
You must run a separate update job for systems that use an ABE from those that do not use an ABE. When creating a job, you
need to define the following job parameters:
Name and description of the update job.
Alternate Boot Environment.
Profile Defines what updates are to be installed, uninstalled, or updated on an OS. Select a profile from the list of
predefined and customized profiles.
Policy Defines how a job is performed and sets the automation level of the job. Select a policy from the list of available
policies. You can also create your own policies.
Target Settings Defines whether the target should be different or similar for each task in the job.
Actual Run Defines whether this job is in simulation mode. You can choose to deploy the job, or to run a job
simulation. A job simulation determines the actions and results of a job, and estimates how much time is required to
complete the job. A job simulation also indicates whether your policy and profile responses will enable the job to
succeed.
Task Execution Order Specifies whether the tasks should be run in parallel or sequentially.
Task Failure Policy Specifies what action should be taken if a task fails.
Targets Select one or more target hosts for this job.
To Update an ABE
1. Click Assets in the Navigation panel.
2. Expand All Assets, or use the All Assets filter to locate the Solaris 10 OS instance.
8.
9.
10.
11.
To change the policy for the new profile, click the Policy cell and select a new policy from the drop-down menu.
If you chose the parameter to use a different target for each task, click the Targets cell to display the Select
Targets page. Select one or more target from the list of Available Items, then click Select to include the asset in
the Target List. Click Add to Target List to close the page.
Click Next.
If you selected chose to create an ABE as part of the job, the Create ABE page appears.
If you have only one ABE, the Boot Environment Workflow page appears, go to step 10. If you have multiple alternate
boot environments, the ABE Selection page appears.
One or more of the targets has more then one possible associated ABE. Select the ABE from the drop-down
menu for each of the Targets. You can use the Select ABE field to filter for the ABE name.
Click Next.
The Boot Environment Workflow page is displayed.
If you selected Simulation in the job parameters, the boot environment workflow cannot be edited, Click Next. Skip to
step 12.
If you selected Actual Run in the job parameters, you can edit the pre-actions and post-actions in the workflow.
Updating Zones
Ops Center enables you to update the global and non-global zones of your Solaris systems. You can run a patch job on the global
zone and update all zones without using the -G command.
The concepts that relate to updating global and non-global zones and the procedures to update the zones are described on this
section.
Content
Description
Action
SUNW_PKG_ALLZONES
If the value is true, the package is installed on all zones, both global and non-global.
SUNW_PKG_HOLLOW
If the value is true, the package information is propagated to the non-global zones, but the package
is not installed.
SUNW_PKG_THISZONE
3. Set the -G parameter to true for the action that you want to perform.
4. Save and close the file.
5. For this change to take effect, restart the services using the following commands:
SUNW_PKG_THISZONE
SUNW_PKG_HOLLOW
Impact
Impact with -G
configuration
False
False
False
True
False
False
True
False
True
False
True
False
Patches are simply sets of updates to packages. When you install a patch, the patch will be installed on the global zone and the
non-global zones, depending on the package parameters as shown in the previous table.
Note Use caution while enabling the -G option on a host with sparse zones. Packages that are inherited from the global zone,
which are not SUNW_ALL_ZONES, cannot be patched within a sparse zone.
As a zone administrator, you can install packages and patches on non-global zones. The patchadd and pkgadd command
should be used without any options. Do not configure the -G switch to the commands while updating the non-global zones.
Refer to the following table when you are updating a non-global zone. The results shown in the table determine whether the
update job will be successful, depending on the package information.
Note The -G switch does not have any impact on installing packages or patches in a non-global zone.
SUNW_PKG_ALLZONES
SUNW_PKG_THISZONE
SUNW_PKG_HOLLOW
Impact
False
False
False
True
False
False
True
False
True
False
True
False
Patches are simply sets of packages that need to be installed. If any one of the packages has the SUNW_PKG_ALLZONES set to
true, then the patch installation fails. For a successful patch installation, ensure that none of the packages have
SUNW_PKG_ALLZONES set to true.
Note Packages that deliver to read-only inherit directories will fail to install to sparse root zones. Such packages should be
installed from the global zone with the -G switch disabled. If such a package has the parameter SUNW_PKG_THISZONE=true, it
will not appear as installed from the sparse zone and the software might not function correctly. In this case, a whole root zone
should be used. In general, packages with SUNW_PKG_THISZONE=true should not deliver to read-only inherit directories.
Solaris Baselines
A Solaris baseline is a dated collection of Solaris patches, patch metadata, and tools. Sun releases Solaris baselines on a monthly
basis. When you install the patches of a baseline on a host, that system is considered to be compliant with that baseline.
Using Solaris baselines enables you to easily identify the patch level of your hosts. For example, you install some test hosts with a
particular baseline. Then, you test these hosts for a period of time to see whether the patches in this baseline are stable enough
to be used on your production hosts. When the testing reveals that this baseline is stable, you can install the same baseline on
your production hosts.
Baseline information is available in the following locations in the BUI:
View/Modify Catalog
Profile Editor
Baseline Analysis Report
Each dated baseline contains these patch sets:
Full Includes all Solaris patches
Recommended Includes Solaris recommended patches and security patches
Security Includes only Solaris security patches
All baselines include patches for a specific time frame. However, the Full baseline often contains Solaris OS patches that are not
included in the Recommended baseline. The Full baseline includes additional patches based on feedback from various customer
support groups within Sun. These patches are not always included in the Recommended baseline.
To install the Recommended and Security baselines, you either need to deploy two jobs, or have a job that includes multiple tasks.
This might result in multiple reboots, for example, if both tasks (baselines) include patches that have Single User mode
requirements.
Ops Center's Knowledge Base (KB) is updated with the details of the baselines. This is done a few days after the official release of
baselines by Sun.
Note The Solaris 8 OS was placed into End of Service Live (EOSL) on March 31, 2009. Solaris 8 OS baselines are available
through March, 2009. The KB might contain artificial baselines after that date. Do not use baselines dated after March, 2009.
White List
A white list is the list of patches that you want to install, uninstall, or upgrade. To establish a white list, create a profile using the
Required setting. You can also specify a white list when generating a Baseline Analysis report.
For example, establishing a list of Solaris OS patch IDs that must be applied to a specific system involves the following:
1. Creating a profile with the patches that need to be installed.
2. Creating a job with the selected profile.
As another example, baseline B includes patches X, Y, Z, and the white list has patches U, V, and W. When your Baseline Analysis
Report is created, the host is marked compliant only when all six patches X, Y, Z, U, V, and W are present.
Black List
A black list is a list of patches that you do not want installed. You create a black list by creating a policy with the specified action
for the patches. You can select a black list option when you create a Baseline Analysis Report. Select the black list either from the
created policy or as a text file that you can create. In the text file, enter the patch IDs separated by new lines.
If a particular patch in the profile is set with the policy component setting as Never for install action, then the patch will not be
installed. If the patch is already installed, it will not be uninstalled or removed.
For example, if baseline A has patches X, Y, and Z, and the black list specifies only Y and Z, the system is compliant as long as X is
installed. Even if the patches Y and Z are installed, they will not get uninstalled if you run a compliance job from the report
results.
6. Select one or more distributions by clicking them and clicking Add or by clicking Add All, then click Next.
The Select Updates page is displayed.
7. Select one or more updates by clicking them or clicking Select All, then click Next.
The Select Packages page is displayed.
8. Select one or more packages by clicking them or clicking Select All, then click Next.
The Select CVE page is displayed.
9. Select one or more CVEs by clicking them or clicking Select All, then click Next.
The Summary page is displayed.
10. (Optional) Click Save Report to save the report for future use. This returns you to the Reports tab, where you can run the
report by selecting it from the Saved Reports section and clicking Re-run Report.
11. Click Run Report.
The report is displayed.
12. (Optional) Select one or more incidents by clicking them or by clicking Select All, then click Execute Job to launch a job
to update them.
13. (Optional) Click Export to CSV to export the report.
14. Click Done to close the report.
Updating a Linux OS
You can update a Linux operating system after you have discovered it and managed it. A managed asset has Ops Center agent
software installed on it.
To keep your systems current, use the System Catalogs and Linux OS Update Reports to determine which patches, updates,
software, and actions apply to your system.
There are different methods for running an update job. This section describes the update feature in Ops Center, how to
customize an update job, updating in disconnected mode, using profiles and policies for Linux updates, and managing local
contents.
4.
5.
6.
7.
Enter a name and description for the update job in the Job Information window.
Select the Actual Run for the job. It can be either Simulation or Actual Run.
Select the Profile and Policy from the list.
If you want to change the selected target system, select the row and click Edit Targets icon.
The Select Targets window is displayed. Select the targets on which you want to run the update job. You can select more
than one target.
8. Click Add icon to add more tasks to the update job.
You can define the profile, policy and target for each task. If the target setting is a different target for each task in the
job, then the new task includes the Select Targets button. Click Select Targets to select the target for the task.
9. Select the task execution order and failure policy for the job.
10. Click Run Now to run the job immediately or click Next to schedule the job to run later.
5.
6.
7.
8.
Enter a name and description for the update job in the Job Information window.
Select the Actual Run for the job. It can be either Simulation or Actual Run.
Select the Profile and Policy from the list.
Click Select Targets to select the target for the task.
The Select Targets window is displayed. Select the targets on which you want to run the update job. You can select more
than one target. To change the target, select the task and click the Edit Targets icon.
9. Click the Add icon to add more tasks to the update job.
You can define the profile, policy, and target for each task.
10. Select the task execution order and failure policy for the job.
11. Click Run Now to run the job immediately or click Next to schedule the job to run later.
You can run a host compliance report to determine whether the hosts are complaint with security and bug fix incidents.
10. If you selected Filter Updates as the criteria, the Select CVE page is displayed. Select one or more CVEs by clicking them
and clicking Add or by clicking Add All, then click Next.
The Summary page is displayed.
11. (Optional) Click Save Report to save the report for future use. This returns you to the Reports tab, where you can run the
report by selecting it from the Saved Reports section and clicking Re-run Report.
12. Click Run Report.
The report is displayed.
13. (Optional) Select one or more incidents by clicking them or by clicking Select All, then click Install Fix(es) to install the
recommended patches.
14. (Optional) Click Export to CSV to export the report.
15. Click Done to close the report.
4.
5.
6.
7.
8.
9.
10.
11.
12.
Status The compliance status that the report will cover. Select either compliant or noncompliant.
Level Select Security or Bug Fix.
Click Next.
The Select Targets page is displayed.
Add one or more targets by selecting them in the list on the left and clicking Add to Target List, then click Next.
The Select Packages page is displayed.
Select one or more packages by clicking them or clicking Select All, then click Next.
The Summary page is displayed.
(Optional) Click Save Report to save the report for future use. This returns you to the Reports tab, where you can run the
report by selecting it from the Saved Reports section and clicking Re-run Report.
Click Run Report.
The report is displayed.
(Optional) Select one or more packages by clicking them or by clicking Select All, then click Install Package(s) to launch a
job to install them.
(Optional) Click Export to CSV to export the report.
Click Done to close the report.
Updating a Windows OS
Ops Center enables you to update your managed Windows operating systems. You need to discover and manage the assets that
you want to update. See Asset Management for information about how to discover a system. Ops Center uses Microsoft System
Center Configuration Manager (SCCM) for updating the Windows operating systems. The Windows Update functionality depends
on the SCCM's agent installed on the managed systems. You can configure SCCM to install agents on your managed Windows
systems either automatically or through a manual process.
To ensure that your managed systems are up to date, you need to determine which patches, updates, and actions to apply to your
system. The Windows Updates Reports help you determine the patches that are applicable to your systems and how many of the
applicable patches are compliant or not compliant for the selected systems.
Reports
Several predefined OS Update reports are available. The reports enable you to check for new patches and and update your
systems. You can get a general report, or test a system for available fixes.
When you create a report, you select the criteria that are relevant to you, such as Category, Severity, Superseded, and Release
Date of the update patches. You can also select specific updates on which to run the compliance reports.
Update Job
Ops Center contains the following options in an update job to maintain control and consistency across your data center:
Groups Help you to organize your assets in the user interface, and act as targets for many types of jobs.
Roles Enable you to determine the tasks that a user can perform on a specific piece of asset or a group of assets.
Reports Enable you to run compliance reports and create update jobs from the compliance reports.
You can define the following job parameters while creating a New Windows Update Job:
Name and Description Identifies the name of the report against which you want to create a new Windows OS update
job. A detailed description is helpful in clearly identifying the job in the historical record.
Reboot behavior Lets you select the reboot behavior if a reboot is required after the new update job is executed. You
can select whether you want the system to reboot immediately following the update operation or whether you want to
reboot the system at the default setting of the SCCM server.
License Terms Lets you review the license terms and either accept or decline it. The License Terms window appears only
when the updates in the report require License Terms that need to be reviewed.
Schedule Lets you decide how you want to schedule the execution of the new update job.
2.
4.
A compliance report details window is displayed.
5. Click Make Targets Compliant.
The Create New Windows Update Job wizard is displayed.
6. Enter a name and description for the update job in the Job Information window.
7. Select one of the two options under Reboot.
Select whether you want the system to reboot immediately following the update operation, or whether you want to
reboot the system at the default setting of the SCCM Server. Click Next.
When you click Next, either the License Terms window or the Schedule window is displayed. The License Terms window is
displayed only when the updates in the report require license terms to be reviewed.
8. Review and accept the Software License Terms for the updates that require license terms.
The table shows only the updates for the license terms that have not been accepted or declined before. Under Search,
you can choose Select All to include a bulletin ID, article ID, title, and license terms in your search, or you can select
specific fields to narrow your search. Click Next.
9. Select the schedule for the the new Windows software update job from the following options:
Now (immediately)
Start Date and Start Time
On a Recurring Schedule by specifying Month, Days, Earliest Job Start Time, and Latest Job Start Time
Click Next.
10. Verify the details in the Summary window. Click Finish to execute the new Windows software update job.
You can delete a Windows report from the list of reports under the Report Results tab.
Virtualization
Virtualization maximizes your use of resources and has become an important technology across all aspects of the IT environment.
Ops Center can manage assets and resources even if they are virtual assets and resources. The Virtualization Controller manages
and monitors the agent software on a virtual asset or storage resource as if it were a physical component.
Ops Center supports the following virtualization technology:
Solaris OS virtualization
SPARC server virtualization
Logical Domains
Logical Domains, or LDoms, technology is part of a suite of methodologies for consolidation and resource management for
SPARC Chip Multi Threading (CMT) systems. This technology allows you to allocate a system's various resources, such as
memory, CPU threads, and devices, into logical groupings and create multiple discrete systems. These discrete systems have their
own operating system, resources, and identity within a single system. By careful architecture, an LDoms environment can help you
achieve greater resource usage, better scaling, and increased security and isolation.
Ops Center supports management of LDoms that are created through the Ops Center BUI. LDom provisioning through Ops
Center installs the Solaris OS, control domain, and agent freshly on the target system. This provisioning action removes everything
that was present prior to provisioning, including the guest domains.
Note Using Ops Center, you can discover the LDoms that were created through the native CLI ( ldm(1M)) and display them in
the Assets tree. However, you cannot use Ops Center to perform any actions on those domains.
This diagram shows a control domain and three guest domains. The first guest deploys a financial application; the second guest
deploys a database application; the third guest deploys a web application. CPU threads and memory resources are assigned to
each guest depending on the requirements.
The control domain looks after the LDoms environment and communicates with the processes and firmware to create the
required guests.
The hypervisor is a firmware layer on the flash PROM of the motherboard. The hypervisor is a thin software layer between the OS
and the hardware. The hypervisor implements a stable sun4v interface. The hypervisor provides a set of support functions to the
OS, so that the OS does not need the details of how to perform functions with the hardware. This allows the OS to simply call the
hypervisor with calls to the sun4v platform.
Hardware Requirements
The following hardware is supported for LDoms.
Hardware Type
Supported Hardware
OS Requirements
The following operating systems are supported for LDoms.
Domain Type
Supported OS
Control domain
Guest domain
OS Patch Requirements
The following patches need to be installed on supported operating systems.
Patches
Supported OS
141778-02, 139983-04
Solaris 10 5/09
139555-08
Solaris 10 10/08
139555-08
Solaris 10 5/08
Firmware Requirements
The firmware requirements are based on the hardware that is used for LDoms. The first public release of firmware to include
LDoms support is System Firmware Version 6.4.x. The correct firmware ensures that the hardware and hypervisor can
communicate correctly.
When you perform the steps to provision the control domain, a firmware check is done in the background to determine if the
target system has the required system firmware version installed. A warning or error message is displayed if the required system
firmware version is not present on the target system. The error message also contains the required system firmware version and
the required firmware patch for that target system.
The following system firmware patches are required for use with LDoms on supported servers.
System Firmware Version
Patches
Supported Servers
6.7.4
139434-03
6.7.4
139435-03
6.7.4
139436-02
6.7.4
139437-02
6.7.4
139438-03
7.2.2
139439-04
7.2.2
139440-03
7.2.2
139442-06
7.2.2
139441
7.2.2
139444-03
7.2.2
139445-04
7.2.2
139446-03
7.2.2
139448-02
Control Domain
The LDom host runs in the control domain, allowing you to create and manage other LDoms and allocate virtual resources to
other domains. There can be only one control domain for each server. The initial domain created when installing LDoms software
is a control domain and is named the primary domain. The control domain contains the SUNWldm packages, including the LDom
host application and the LDom host daemon (ldmd) process required for managing LDoms. If you have OS and other software
running on a server, that server becomes your control domain once you install the LDom software.
Note Zones are not supported in the control domain. You must not run user applications in the control domain and you cannot
migrate, delete, or shut down a control domain.
Guest Domain
The guest domain is a complete virtualized environment that has no ownership of physical I/O or virtual devices. This domain is
managed by the control domain and uses services from the I/O and service domains. The guest domain must run an OS that
understands both the sun4v platform and the virtual devices presented by the hypervisor.
Service Domain
The service domain provides virtual device services such as a virtual network switch, a virtual console concentrator, or a virtual
disk service, to other domains.
I/O Domain
The I/O domain has direct ownership of and direct access to physical I/O devices, such as a network card in a PCI Express
controller. This domain shares the devices with others in the form of virtual devices when the I/O domain is also the control
domain. The number of I/O domains that you can have is dependent on your platform architecture. For example, if you are using
an UltraSPARC T1 processor, you can have a maximum of two I/O domains, one of which also must be the control domain.
Note In Ops Center 2.5, control, service, and I/O domains are in the same domain.
Virtualization Hosts
Hardware virtualization enables you to create multiple virtual machines on a single piece of physical hardware. Unlike Solaris
Containers, where the operating system is the same, virtual machines can run on full instances of different operating systems, or
different versions of the same operating system. These instances are called guests.
The software uses a control domain, or virtualization host, to create and manage the guests and allocate virtual resources to other
domains.
Logical Domains
Logical Domains (LDoms) enable server virtualization on SPARC platforms. The software enables you to create and manage
multiple virtual machines instances simultaneously on a single compatible SPARC machine.
With Ops Center, you can monitor and manage all of the virtual machines from a single browser user interface. You can use
virtual pool technology to automatically balance the load of a number of servers to maximize capacity without overloading a
server. Load balancing enables you to move a virtual machine from one physical system to another, from the user interface. You
can set parameters that enable the software to automatically balance the load, or you can elect to receive email notification and
then decide if you want to balance the load.
1. Importing an OS Image
2. Creating a Logical Domain Profile
3. Provisioning the Control Domain
CPU Threads
System CPUs
Less than 16
16 to 64
Greater than 64
Crypto Units
Crypto units are the cryptographic resources on the supported platforms that provide high-performance, dedicated cryptographic
engines. These can be used for tasks such as encrypting and decrypting network traffic that could occur between a Secure Socket
Layer (SSL) web server and an application server.
Each CPU core has one crypto unit and four or eight CPU threads. There are eight crypto units on eight-core platforms. As crypto
units are part of a core, they can be bound only to a domain that contains at least one thread from the parent core.
Crypto units cannot be split like CPU threads and must be aligned with a CPU core. For example, you have assigned the crypto
unit for the first CPU core to the control domain. If the new guest domain is assigning a thread from the first CPU core and the
crypto unit for that core is already assigned, the hypervisor cannot assign that crypto unit to the new guest.
You must assign at least one crypto unit to the control domain because the crypto unit is used to speed up domain migration.
Allocation of crypto units might not succeed, especially if a core is split between domains. An LDom host might allocate fewer
crypto units or none at all.
Example
In UltraSPARC T1 based servers, one core is four CPU threads. Therefore, assign one crypto unit and four CPU threads to the
control domain. These values are set in the LDom profile.
In UltraSPARC T2 and T2 Plus based servers, one core is eight CPU threads. Therefore, assign one crypto unit and eight CPU
threads to the control domain.
RAM
System RAM
Less than 8 GB
1 GB
8 GB to 16 GB
2 GB
16 GB to 64 GB
4 GB
Greater than 64 GB
8 GB
Additional Configurations
Apart from CPU threads, crypto units, and memory, the following additional configurations must be set up for the control
domain:
Virtual network switch
Virtual disk server
Virtual console concentrator
These configurations are performed during LDom provisioning.
Importing an OS Image
You can import OS images from existing ISO files. After you import an OS image, you can then create a profile for LDoms that
you use to provision the control domain onto systems on your network.
When you import an OS image, an OS profile is created by default. The OS profile is named using the image name that
you enter in the Import OS Image wizard. This default OS profile is intended for use as a template. You can modify the
default OS profile for your specific systems.
On the Ops Center Enterprise Controller, OS images are stored in the /var/opt/sun/xvm/images/os/iso
directory. The OS images that are stored on Proxy Controllers are temporary, and are used for the provisioning process.
OS image names that you specify must be unique, can consist of up to 100 characters, and may include numbers, letters,
and some special symbols. The following special symbols are prohibited: comma, asterisk, single quote, double quote,
parenthesis, question mark, equal sign, and newline.
Note You need to import at least the Solaris 10 5/09 OS SPARC ISO image for the LDoms feature to work.
To Import an OS Image
1. Click Libraries in the Navigation panel, then Click OS Provisioning.
The OS Images list and list of OS Provisioning Actions is displayed.
2.
3.
4.
5.
6.
7.
In the Image Name field, enter the name that you want to assign to the ISO image that you will import.
In the Description field, enter a description of the file that you will import.
Select the ISO image type.
Click Browse to display the Browse Server panel.
Use the Browse Server panel to navigate to the directory that holds the ISO image that you want to import. You can use
the Refresh button to refresh the display of your current directory.
8. Select the ISO that you want to import, then click Add Files.
The file that you selected is displayed in the Files list in the Import OS Image panel.
To add more files, repeat this step.
9. When the list of files that you want to import is complete, click Import.
Example of a Solaris OS image imported into Ops Center
See the recommended configurations for control domain at Configurations of Control Domain.
CPU Threads Specify the number of CPU threads that you want to assign to the control domain. The remaining
CPU threads are available for the guest domains.
Memory Specify the amount of memory that you want to assign to the control domain. The remaining
memory is available for the guest domains.
Crypto Units Specify the number of crypto units that you want to assign to the control domain. The remaining
crypto units are available for the guest domains.
Virtual Console Port Range Specify the minimum port and maximum port of the virtual console of the control
domain. The default port range for virtual console is 5000 to 6000.
Enable JASS Select this check box to harden the system by installing the SUNWjass package.
Enable Multiplexed I/O (MPxIO) Select this check box to enable Fibre Channel connectivity for the control
domain. This action enables Fibre Channel ports on the system that is configured for storage. Click Next.
The Define Partitions page is displayed.
11. In the Define Partitions panel, define the disk partitions and file systems that you want to create on the target system.
Click the Add icon to define a new partition. The root (/) and a swap file system are defined by default.
For each partition that you define, provide the following information:
Mount Point Enter a directory to use as a mount point for partitions.
Device Enter the rootdisk keyword and a slice value to describe a partition on the target system's boot disk,
for example, rootdisk.s0, or enter the logical device name, for example, c1t0d0s0, of the partition that
you want to create.
File System Select a file system type, either ufs, unnamed, or swap.
Specify Size Select this option to specify a specific size for a partition. If you want a single partition to use all of
the remaining space on the disk, deselect this option.
Size (MB) With the Specify Size option selected for a partition, enter the size that you want to assign to the
partition, expressed in MBytes. Click Next.
The Summary panel is displayed.
12. The Summary page displays the information that you specified in all of the preceding panels in the Create OS Profile
wizard. If the summary information is correct, click Finish to create a profile for LDoms.
Example of an LDom Profile
A model number check is also performed. To successfully provision the LDom Controller, the model name must be
available.
4. In the Configuration page, enter the information that is required for your target system and selected LDom profile.
The Configuration fields that relate to any single target system include:
Target This field identifies the target system for the control domain provisioning action. Note that when the
target of the control domain provisioning action includes only one system, the Provision OS wizard skips the
Select Target panel, which otherwise is displayed before the Configuration panel.
Manual Net Boot Select this option to enable manual control of network boot operations for the target
system. You must select this option for a target system that does not have a service processor because Ops
Center cannot remotely control the network boot process on these systems. When the NetbootTask of the
control domain provisioning job is successful, user intervention is required. Log in to the service processor of
the target system(s) and manually initiate the network boot process by typing boot net:dhcp - install.
Note If the target system is already up and running, type halt and then initiate the network boot process by
typing boot net:dhcp - install.
Network Protocol Static IP is selected as the network protocol by default. This means that a specific IP address
is assigned to the target system's provisioning network interface, after the system is provisioned.
IP Address Enter the IP address for the target system. This is a required field when it is displayed. Use IP
addresses that are not defined as part of a subnet that is managed by the DHCP server on a Proxy Controller.
See Subnets for more information.
Netmask Enter the netmask value that the target system will use after the OS has been installed.
Gateway Enter the gateway value that the target system will use after the OS has been installed.
Host Name Enter the host name that the target system will use after the OS has been installed.
Name Server Enter the IP address or host name of the name server that the target system will use after the OS
has been installed.
Console Serial Port To monitor the installation using a serial connection, select the correct console serial port
device.
Console Baud Rate To monitor the installation using a serial connection, select the correct serial port device
baud rate.
Network Device Select the device for the network interface that the target system will use after the OS has
been installed. Typically you only need to specify this value if it is not automatically determined.
Domain Name Enter the DNS domain name that the target system will use, if required.
Boot Path Select a physical device name from the Boot Path list, if the target system requires that you specify
it manually.
5. In the Configuration page, click Next.
The Summary panel is displayed.
6. Click Provision to submit the control domain provisioning job.
You can view the status of the provisioning job in the Jobs panel.
Note When the control domain is re-provisioned, any previous LDom configuration is removed from the service processor by
###############################################################################
# OS Provisioning
###############################################################################
# Default Timeout of OSP Job
osp.default_timeout=180
The value of the osp.default_timeout property is in minutes. You must restart the Enterprise Controller after changing the
value.
Summary
In the Summary tab, the following information about the LDom host is displayed:
Name
Description
Sun LDom Host Status
Reachable
Running Time
Tags
Virtual Pool (associated virtual pool)
Total and Available CPU threads
Total and Available Crypto Units
Total and Available Memory
The Available CPU threads, crypto units, and memory can be utilized by the guests.
The Sun LDom Control Domain Specification section in the Summary tab displays the CPU threads, memory, and crypto units
utilization percentages for the control domain. The Sun LDom Host Resource Utilization section in the Summary tab displays the
CPU threads and memory utilization percentages for all the domains including the control domain.
Ops Center collects data in five-minute intervals and displays the data in the form of charts. (Refer to Charts for detailed
information about collecting and calculating data for different intervals). For an LDom host, the following utilization data is
displayed:
CPU utilization
Memory utilization
Network utilization
The Virtual Guests table in the Summary tab displays the details of the guests that are running in the LDom host. The details
include the CPU threads, crypto units, memory, and state of the guests.
Libraries
The Libraries tab displays the libraries that are associated with this LDom host. The libraries represent the storage resources that
are available for this LDom host.
When you select a library, the guests that are associated with this library are listed under the Usage tab. You can also view the
contents of the library from the Contents tab.
From the Usage tab, you can perform the following operations:
Starting a guest
Shutting down a guest
Rebooting a guest
Migrating a guest
Connecting a guest to a network
Deleting a guest
Network
The Networks tab lists all the networks that are assigned to the LDom host and the guests that are using a selected network.
The following options are available in the Network tab to manage the networks:
Attach Network You can attach a network to a virtual pool.
Unbind Network from Virtual Pool-- You can remove a network from a virtual pool.
Modify Physical Connectivity-- You can modify the network interface properties such as the Address Allocation method.
Chart
Ops Center collects data in five-minute intervals and displays the data in the form of charts. (Refer to Charts for detailed
information about collecting and calculating data for different intervals.) For an LDom host, the following utilization data is
displayed:
CPU utilization
Memory utilization
Network utilization
Jobs
The Jobs tab lists the currently running and historical jobs of the LDom host. (Refer to Job Management for more information
about managing jobs.)
Configuration
The Configuration tab displays information such as remote logging, routing, NFS, and name service information for the LDom
host.
2.
A job is submitted to reboot the LDom host.
The page Shutting Down a Logical Domain Host does not exist.
Creating a Guest
You can create or provision a virtual system, or guest, in Ops Center.
5.
6.
7.
8.
2.
Managing a Guest
You can manage guest operating systems, or domains, in Ops Center.
Monitoring a Guest
When you select an LDom guest from the Assets panel, the following tabs display in the center panel of Ops Center:
Summary
OS Details
Console
Network
Storage
Chart
Jobs
In this section, the information on each tab is described in detail.
Summary
In the Summary tab, the following information about the guest is displayed:
Guest Name
Description
Status
Running Time
Operating System
Tag
Guest Image
Boot Device
CPU Threads
Crypto Units
Memory Size
OS Details
The following information about the OS is displayed in the OS Details tab:
OS Name and Details
OS Health
Notification status
OS Monitoring Variables
File System thresholds and usage
Hourly chart of CPU and Memory Utilization
Console
The Console tab allows you connect to the virtual console of the guest. Click Enable Console to activate the console.
Network
The Network tab displays the networks that are assigned to this guest. This tab displays details such as NIC Name, IP Address,
MAC Address, and Network.
Storage
Guests require virtual disks for storage. The total storage size of all the virtual disks that are associated with this guest is
displayed.
The Storage tab displays a table listing the virtual disks that make up the storage for the guest. These virtual disks can be from
NFS or local libraries, or LUNs from the Fiber Channel library. These virtual disks are defined and configured while creating the
guest. This table is read-only, which means that you cannot add additional virtual disks and you cannot delete any of the existing
virtual disks.
When you select a LUN in this table, additional details such as name, vendor, GUID, product, status, and revision are displayed.
Chart
Ops Center collects data in five-minute intervals and displays the data visually in the form of charts. (Refer to Charts for detailed
information about collecting and calculating data for different intervals.) For a guest, the following utilization data is displayed:
CPU utilization
Memory utilization
Jobs
The Jobs tab lists the currently running and historical jobs of the guest. (Refer to Job Management for more information about
managing jobs.)
You can edit the attributes of a guest. You can modify the resource assignments such as CPU threads and crypto units.
Note You must shut down the guest before you can edit the attributes.
1. In the Assets panel, select an LDom guest that you want to shut down.
2. In the Actions panel, click Shutdown Guest.
3. Click Shutdown Guest in the pop-up window that is displayed.
A job is submitted to shut down the guest.
Before you connect a guest to networks, ensure that the appropriate guest is in shutdown state.
Solaris Containers
Solaris Containers are an integral part of the Solaris 10 operating system (OS). Solaris Containers isolate software applications and
services using flexible software-defined boundaries. They enable you to create many private execution environments within a
single instance of the Solaris 10 OS. Each environment has its own identity that is separate from the underlying hardware. Each
environment behaves independently as if running on its own system, making consolidation simple, safe, and secure.
You can build Solaris Containers by using the following technologies:
Solaris Resource Manager
Solaris Zones partitioning technology
Content
Description
About Zones
Provides an overview of Solaris Zones, types of zones, how zones are supported, and
limitations for the support of zones
Creating Zones
About Zones
A zone is a virtualized operating system environment created within a single instance of the Solaris OS. With the zones feature,
the operating system is represented to the applications as virtual operating system environments that are isolated and secure. The
applications run in different zones with complete isolation, while the underlying operating system resources are centrally
managed and administered.
The Solaris operating system supports two types of zones:
Global zone
Non-global zone
The global zone is the default operating system and has control over all the processes. A global zone always exists even when no
other zones are configured.
Non-global zones, referred to simply as zones hereafter, are configured inside the global zone. Zones are isolated from the
physical hardware characteristics of the machine by the virtual platform layer.
See System Administration Guide: Solaris Containers-Resource Management and Solaris Zones for more information about Solaris
Containers.
Types of Zones
You can create the following types of zones using Ops Center:
Sparse Root Zone Contains a read/write copy of only a portion of the file system existing on the global zone (hence the
name sparse root) while other file systems are mounted read-only from the global zone as loop-back virtual file systems.
When a sparse root zone is created, the global administrator selects which file systems to share with the sparse root zone
(by default, the /usr, /lib, /sbin, and /platform directories are shared as read-only file systems). All packages that
are installed on the global zone are made available to the sparse root zone; a package database is created and all files in
the mounted file system are shared with the zone.
Whole Root Zone Contains a read/write copy of the entire file system existing on the global zone. When a whole root
zone is created, all packages that are installed on the global zone are made available to the whole root zone; a package
database is created and all files are copied onto the whole root zone for the dedicated and independent use of the zone.
Branded Zone Supports different versions of Solaris OS in the zones for running applications. For example, you can
install Solaris 8 or 9 in the branded zone on a system with the Solaris 8 or 9 Container products.
The following illustration provides a clear picture of how zones are supported in Ops Center. In the illustration, Zone 2 is created
using the CLI and the Ops Center provides the following support for Zone 2:
Boot zone
Shut down zone
Halt zone
Clone zone
Delete zone
Monitor zone resource utilization
The Zone 1 in the illustration is created using Ops Center. Ops Center provides the same support, and in addition, the following
benefits:
Edit zone configuration
Manage zone storage
Manage zone network
Migrate zone
You can clone zones that are discovered and managed in Ops Center such that a cloned zone is similar to a zone created using
Ops Center.
Limitations
Administering
Zones in Ops
Center
It is essential that the zones created through Ops Center must be administered only using Ops Center. You
must not make changes or perform zone tasks using other utilities such as CLI. If not, Ops Center will suspend
the management of the zones created through Ops Center.
Performing
Zone tasks
Zone management tasks such as Add File Systems, Add Storage, Connect Network and Edit Zone Configuration
are enabled only if the zone is in the shut down state. Whereas, the Migrate Zone and clone zone are enabled
even when the zone is running.
Live Upgrade
and Zones
If you use Live Upgrade to update the zones, then you cannot manage the zones using Ops Center. ABE is not
supported for zones that were created using Ops Center. When you migrate a zone, ABE is not supported.
Create Zones
You can configure and install zones using Ops Center.
Creating zones with Ops Center results in the following operations which run automatically in the background and are hidden
from the user:
The file systems of the zones are implemented as ZFS file systems.
Storage added to a zone is pooled in a zpool.
A zpool is created with the name of the zone metadata.
There is one zpool for each created zone in Ops Center 2.5.
You cannot edit or delete the storage added to the zone. However, you can add new storage to the zone which will be
added to the existing zpool.
The storage that is allocated to the zone is pooled in a zpool and used by all the file systems.
Note When you create or migrate a zone using Ops Center, you cannot use Solaris Live Upgrade and an alternate boot
environment (ABE) to update the zone.
# ls -d /export/home
/export/home: No such file or directory
# mkdir -p /export/home
# ftpconfig /export/home/ftp
Creating user ftp
Creating directory /export/home/ftp
Updating directory /export/home/ftp
4. Copy the Solaris 9 flash archive images to the anonymous FTP directory.
For example:
# cp /opt/ses/flar/solaris9-image.flar /export/home/ftp/pub
To Create a Zone
1. Expand the Assets section and select the global zone.
The Summary page of the selected global zone is displayed.
2. In the Actions panel, click Create Zone.
2.
The Create Zone wizard is displayed.
3. Select the type of zone that you want to create in the wizard.
To create a branded zone, provide the following information:
a. Specify the location of the image:
For the global zone, specify the image location as file:///path/to/the/image.flar.
For an HTTP server, specify the image location as http://path/to/the/image.flar.
For an FTP server, specify the image location as ftp://path/to/the/image.flar.
b. Select the brand type, either Solaris 8 or 9. The Solaris packages must already be installed.
Note After installing the packages, it takes at least five minutes for Ops Center to refresh the brand list.
c. (Optional) Specify the HostID if you want to run application that are associated with specific host IDs.
d. (Optional) Specify the Machine Type as Sun4u or Sun4v for Solaris 8 or 9 branded zones.
Click Next.
The next step of the Create Zone wizard is displayed.
4. Identify the zone. Enter a zone name and description for the zone.
5. Select one of the libraries associated with the global zone from the Library list.
The new zone metadata will be stored in the selected library. Click Next.
The next step of the Create Zone wizard is displayed.
7. Configure the language, time zone, terminal type, and root password for the zone. The zone name is taken as the host
name for the zone.
8. Set the boot properties of the zone as required.
You can set the boot properties so that the zone boots after creation and whenever the global zone boots. Click Next.
The next step of the Create Zone wizard is displayed.
Note Provide sufficient storage space to accommodate the file systems added to the zone. Ensure that you allocate 20%
more than the required storage space for a good performance.
Note If you provide local library for the zone storage, then you cannot migrate the zone.
The next step of the Create Zone wizard is displayed.
12. View the summary of your selections for the new zone. Click Finish to launch the job for creating a zone.
See System Administration Guide: Solaris Containers-Resource Management and Solaris Zones for configuring and installing zones.
Discovering Zones
Use the Custom Discovery method to discover zones. When you discover a global zone, Ops Center can identify that it is a global
zone
Note Discovering a global zone will automatically discover all the existing zones under it.
The already existing zones are identified by the
icon in the Assets tree. The representation of the zone under the global zone
in the Assets tree is shown in the following figure.
Managing Zones
You manage assets after you have discovered them. The Manage Assets option enables Ops Center to monitor and maintain
assets by installing agent software on the assets. When you manage an asset that is a zone, the agent is installed and configured
on the zone, by installing packages in directories such as the /usr directory. When you have an asset that is a global zone with
sparse root zones, you must first manage the global zone and then manage each sparse root zone. This order ensures that the
sparse root zone inherit the global zone's attributes.
Note This does not apply to the whole root zone because it does not inherit the directories from the global zone.
See Manage Assets for the procedure to manage an asset.
Unmanaging Zones
When you want to unmanage or delete a global zone, you must first unmanage or delete any subordinate zones and then
unmanage or delete the global zone. If you delete a global zone without deleting the zones under it, the job fails and the global
zone is not deleted.
To unmanage or delete a zone, follow the Unmanaging and Deleting Assets procedure.
Summary
In the Summary page, the following information of the global zone is displayed:
Name
Description
State
OS Version
Server name
Total CPUs
Total CPU Utilization
Total Memory Utilization
Zone under the global zone
From the Summary page, the following operations are available for the zones that are under the global zone:
Boot Zone
Shutdown Zone
Halt Zone
Connect Network
Add Storage to Zone
Replicate Zone
Reboot Zone
Migrate zone
Delete Zone
Depending on whether the zone is created through Ops Center, or discovered and managed through Ops Center, the zone
management icons are enabled accordingly.
Utilization
Extended accounting is enabled in the global zone. This gives CPU and memory utilization on a per-zone basis. The utilization of
each zone is the utilization of all the processes in each zone over the same interval.
The CPU resources for a zone could be dedicated or shared. Regardless of how CPU resources are utilized, the CPU usage
statistics for every five minutes interval is provided.
The memory utilization for virtual, physical, and locked memory usage are provided. The memory usage by each zone is polled in
five-minutes intervals.
Libraries
The libraries that are associated with the global zone are listed in this page. The libraries represent the storage resources that are
available for the global zone. The local storage, NAS storage, and Fiber Channel libraries that are associated with the global zone
are listed.
Select a local library or NAS storage library from the list. The zones that are associated with the selected library are listed under
the Usage tab. The Usage tab provides you with the same zone operations that are available in the Summary page. You can also
view the contents of the library, when you select the Contents tab. The Contents tab provides you with the following library
operations:
Upload ISO Image
Upload Appliance Image
Import Image
View Image Details
Edit Image Details
Delete Image Details
Move Image
Clone a Selected Template
When you select a Fiber Channel library from the associated library list, the LUNs tab is displayed. The LUNs tab lists the LUNs that
are allocated to the global zone. The following Fiber Channel library operations are available:
Add LUNs
Edit LUN Details
Delete LUN Details
The LUN information is displayed when you select a LUN.
Refer to Storage Libraries for more information about the procedures to manage the images in Libraries.
OS Details
In the OS Details page, the following information about the global zone OS is displayed:
OS Name
Server name
Health status
Notification status
OS monitoring variables
File system monitoring
Hourly charts of CPU, memory, and network usage
The different OS health states are as follows:
Good The server is working properly.
Unknown An error occurred while attempting to retrieve information about the health of the OS resource. The server
is connected but does not return any information.
Unreachable The server agent IP address cannot be contacted for the status of the health of the OS resource. This
indicates network problems or that the server is in standby mode.
Warning Failure A potential or impending fault condition has been detected on the server. Action should be taken to
prevent the problem from becoming more serious.
Critical Failure A fault condition has occurred on the server. Corrective action is required.
3.
Critical.
Use the Shift key to select more than one variable.
4. Click the Change Threshold icon.
The Change OS Monitoring Thresholds window is displayed with the selected variables.
5. Enter the Warning and Critical thresholds values as required.
For all the variables, the unit of measurement is displayed. The values depend on the number of processors in your
system and on the usage characteristics. If you enter an incorrect value, an error message is displayed.
6. Click Change Thresholds to submit the changes.
Ideally, the value of any given monitored OS health attribute is compared to a threshold value. Monitoring variable values are
compared against the thresholds at regular intervals. If the value of a monitored OS health attribute rises above the warning
threshold, notification is issued with the status of Warning Failure. If the value continues to increase and passes the critical
threshold, notification is issued with the status of Critical Failure.
Networks
The Networks tab lists all the networks that have been assigned to the global zone. When you select a network, the zones that are
using the network are displayed under the Zones Using tab. The following options are available in the Networks tab to manage
the networks:
Assign Network Click the Assign Network icon. The Assign Network to Global Zones wizard is displayed. Refer to
Assigning Networks to a Global Zone for detailed information.
Unbind Network You can remove a network that has been assigned to the global zone. Select a network and click the
Unbind Network icon.
Modify Physical Connectivity You can modify the network interface properties such as the Address Allocation method.
Charts
Ops Center collects data in five-minute interval and displays the data visually in the form of charts. Refer to Charts for detailed
information about collecting and calculating data for different intervals. For a global zone, the following charts are displayed:
CPU utilization You can display the CPU utilization for different CPU model such as shared CPU and dedicated CPU. If
you have zones that have dedicated CPUs, then all those zones will be displayed under Dedicated CPUs list. You can
select one or more zones from the list for which you want to display the chart. For Shared CPU, there could be more
than one resource pool. The shared CPU is listed for all the resource pools in the global zone. The shared CPU for a
default resource pool has the following cascading menu:
Total (Aggregate)
kernel
global
List of zones in the pool or pset(processor set)
You can select the chart plot (both X-axis and Y-axis) as per your requirement and it will be displayed as in the
sample figure.
Network utilization You can view charts for all the NICs present in the global zone. The following chart options are
available:
Total (Aggregate)
All the NICs in the system
Per-zone network utilization data is not available.
File System Utilization Whenever you create a zone, a zpool is created with the zone guest image name. All the zpools
under the global zone are listed in the file system list. You can select a file system and display the utilization rate for a
historical period. The current utilization data can be seen in the OS Details page. The OS Details page lists all the file
systems and the current utilization rate.
A sample chart is displayed as in the figure.
System Load The system load on the OS is displayed as a chart for the selected time period.
A sample chart is displayed as in the figure.
Jobs
The Jobs tab lists the jobs that are currently running on the global zone as well as the job that have been run before. Refer to Job
Management for more information about job management.
Configuration
The configuration tab displays the resources that are connected to the selected global zone. When you provision an agent, the
resource details are updated automatically.
You can select a resource from the list and click the Delete Access Point icon to delete the connection to the global zone. You
can also option to unmanage or delete an asset from this page. Select a resource from the list and click the Unmanage/Delete
Asset option in the Actions panel.
When you select a zone in the Assets section, the following tabs are displayed in the center panel:
Summary
Console
OS Details
Networks
Storage
Charts
Jobs
Configuration
If you have zones that have been already created using CLI, then you can discover and manage the zones using Ops Center. These
zones are distinguished in the Ops Center BUI with the
icon.
Summary
The Summary tab of the selected zone displays the following information:
Zone name and its state
Type of zone and the zone path
Zone library and storage size
CPU model and utilization
File systems allocated to the zone
Storage size and usage
Hourly utilization chart of CPU, network, and memory resources
Console
You can connect to the console of the zones that were created using Ops Center. Click the Enable the Console Connection icon to
invoke the zlogin to the zone. Log into the zone using the zone username and password. The zone console exists till you log
out of Ops Center, explicitly click the Disable the Console Connection icon, or the global zone is shut down.
You can click the Undock the Console icon to undock the console session from the Ops Center, making it available separately for
your use.
OS Details
This tab displays the following information about the OS:
OS name and details
OS health
Notification status
OS monitoring variables
File system thresholds and usage
Hourly utilization chart of CPU, memory and network resources
The different OS health states are as follows:
Good The server is working properly.
Unknown An error occurred while attempting to retrieve information about the health of the OS resource. The server
is connected but does not return any information.
Unreachable The server agent IP address cannot be contacted for the status of the health of the OS resource. This
indicates network problems or that the server is in standby mode.
Warning Failure A potential or impending fault condition has been detected on the server. Action should be taken to
prevent the problem from becoming more serious.
Critical Failure A fault condition has occurred on the server. Corrective action is required.
Network
The network tab lists all the networks that are assigned to the zone. You have the following options in the Network tab:
Connect Network
Disconnect Zone Network
Connect Network icon is enabled only when the zone is in the shutdown state, which is when you can assign a network to a zone.
To disconnect a zone network, select a network from the list and click the Disconnect Zone Network icon.
Storage
The Storage tab lists the root file system along with other file systems that were added to the zone. You cannot edit the read and
write access to the root file system, which is the default file system of the zone.
The storage tab also displays the virtual disks that make up the zpool, which is created when you create a zone. The zpool
comprises the virtual disks and LUNs that make up the storage. Ops Center creates one zpool per zone. File systems are
implemented as ZFS file systems and mapped to the storage.
The following options are provided in this page:
Add File Systems
Edit File System
Delete File System
Add Storage to Zone
Note You can add storage to the existing zpool, but you cannot remove or delete storage from the zpool.
Charts
Ops Center collects data in five-minutes interval and displays the data in the form of charts. Refer to Charts for detailed
information about collecting and calculating data for different time periods. For a zone, the following utilization data are
displayed:
CPU utilization You can display the CPU utilization for the zone. The per-zone utilization data is collected by the
Jobs
The jobs tab lists the jobs that are currently running on the zone and historical jobs that have run on the zone. Refer to Job
Management for more information about job management.
Configuration
The Configuration tab displays the zone configuration information. Depending on the type of CPU model, the configuration
details can vary.
The access points list the Proxy Controller through which the zone is connected to the Enterprise Controller. It also states the
connection health and the protocol through which it is connected.
This section describes the different options that are available for monitoring a zone OS.
When you select a zone in the Assets panel, the following tabs are displayed in the center panel :
OS Details
Console
Networks
Charts
Jobs
Configuration
OS Details
The OS Details tab displays the following information about the OS:
OS name and details
OS health
Notification status
OS monitoring variables
File system thresholds and usage
Hourly utilization chart of CPU, memory and network resources
The following procedure describes how to change the monitoring variables threshold:
1. Select the zone from the Assets section in the Navigation panel.
The OS Details page of the selected OS is displayed with the current values for the monitoring variables.
2. Select the variables for which you want to change the threshold values for Warning and Critical.
Use the Shift key to select more than one variable.
3. Click the Change Threshold icon.
The Change OS Monitoring Thresholds window is displayed with the selected variables.
4. Enter the Warning and Critical thresholds values as required.
For all the variables, the unit of measurement is displayed. The values depend on the number of processors in your
system and on the usage characteristics. If you enter an incorrect value, an error message is displayed.
5. Click Change Thresholds to submit the changes.
Ideally, the value of any given monitored OS health attribute is compared to a threshold value. Monitoring variable values are
compared against the thresholds at regular intervals. If the value of a monitored OS health attribute rises above the warning
threshold, notification is issued with the status of Warning Failure. If the value continues to increase and passes the critical
threshold, notification is issued with the status of Critical Failure.
Console
You can connect to the console of the zone. Click Enable Console to invoke the zlogin to the zone. Use the zone user name and
password to log into the zone. The zone console exists till you log out of Ops Center, or explicitly click Disable Console, or the
global zone is shut down.
You can undock the console session from the Ops Center, making it available separately for your use.
The console will not be available if it is in use by other user.
Network
The Network tab lists only the networks that are assigned to the zone. You do not have options to connect to a network or
disconnect from a network.
Charts
Ops Center collects data in five-minute interval and displays the data visually in the form of charts. Refer to Charts for detailed
information about collecting and calculating data for different intervals. For a zone, the following utilization data are displayed:
CPU utilization Displays the historic chart for a selected time period in the X-axis. The CPU usage for a zone is
calculated as the CPU time used by the zone as a percentage of the number of CPUs in the processor set (pset) or the
resource pool.
Network utilization Is enabled only when you select the chart option Display Selected Utilization Graphs as Thumbnail
Image. The graph displays the utilization of the network interfaces assigned to the zone.
Memory utilization Displays the number of bytes used as a percentage of total memory allocated for the zone.
File System utilization Lists the file systems that are mounted for this zone. You can view the historical consumption of
each file system.
System load The system load on the selected zone is displayed as a chart for the selected time period.
Jobs
The jobs tab lists the jobs that are currently running on the zone and historical jobs that have run on the zone. Refer to Job
Management for more information about job management.
Configuration
The Configuration tab displays the resources that are connected to the selected zone. When you provision an agent, the resource
details are updated automatically.
To delete the connection to a zone, select the resource from the list, then click the Delete Access Point icon. To unmnanage or
delete an asset from this page, select a resource from the list, then click the Unmanage/Delete Asset option in the Actions panel.
Booting a Zone
Booting a zone places the zone in the running state. The Boot Zone option is enabled only when the zone is in the ready or
installed state, but not in the running state. Booting a zone applies the changes that have been made to the zone configuration.
If you have set the autoboot properties during zone creation, then the zone will boot when the global zone boots.
To Boot a Zone
1. Select Assets from the Navigation panel.
2. Select a zone. Alternatively, you can select a global zone, then select the zone listed in the center panel of the Summary
page.
The Summary page of the zone and the corresponding actions are enabled in the Actions panel. The Boot Zone option
will be enabled if the zone is in the Ready or Installed state.
3. Click Boot Zone in the Actions panel or click the Boot Zone icon in the Zones pane.
4. Click Boot Now or click Boot Later.
5. If you chose Boot Later, schedule the boot job.
Rebooting a Zone
You can reboot a zone that is in the running state. This type of reboot is different from the zoneadm reboot command where
the zone is first halted then booted again. Instead, Ops Center handles the reboot gracefully, first shutting down the zone and
then booting it.
To Reboot a Zone
1. Select a zone from the Asset section in the Navigation panel. Alternatively, select the global zone from the Asset section,
then select the zone listed in the center panel.
The Summary page of the selected asset is displayed in the center panel.
2. Click Reboot Zone in the Actions panel or click the Reboot Zone icon in the zones content pane.
3. Click Reboot Now or Reboot Later.
4. Schedule the Reboot job.
The libraries that are not associated with the selected global zone are listed.
4. Select one or more libraries.
5. Click Associate Libraries.
A job is submitted to associate the libraries.
3. In Select Networks and IP Model page, select a network that you want to associate with the global zone.
In the Network list, the networks that are defined in the Ops Center and not assigned to the global zone are listed.
4. (Optional) To assign more networks to the global zone, Click the Add icon.
5. Select the IP mode for each selected network.
The IP mode could either be Shared or Exclusive. If you have selected Shared IP mode for a network, then you will be
directed to define the network interfaces of the network.
Note You cannot define the network interfaces for an exclusive IP mode.
6. Click Next. If you have Shared IP mode network, you would be directed to Specify Networks page. If you have only
Exclusive IP mode, you will be required to define the network interfaces for the zones while creating a zone or using
Connect Network to Zone option.
Cloning a Zone
Cloning allows you to copy an existing configured and installed zone on your system to rapidly provision a new zone on the same
system. Cloning a zone is analogous to creating a zone in Ops Center. When you clone a zone, you will be taken through a wizard
similar to creating a zone. Define the zone properties in the wizard for the new zone.
You can clone any type of zones in the Assets section.
To Clone a Zone
1. Select a zone from the assets section in the Navigation panel.
2. Click Replicate Zone in the Actions panel.
The Replicate Zone wizard is displayed.
3. Enter a zone name and description for the zone.
4. Select a library from the Library list.
The libraries that are associated with the global zone are listed in the Library list. The new cloned zone metadata will be
stored in the selected library.
5. Click Next to configure the CPU and memory thresholds.
The CPU shares that are already allocated for the source zone is displayed. As required, you can edit the changes.
6. Click Next to configure the language, timezone, terminal type, host name and root password for the zone.
7. Set the boot properties of the zone as required.
You can set the boot properties so that the new zone boots after creation and whenever the global zone boots.
8. Click Next to configure the zone file system.
The new zone will be created with a default root file system which is the zone path. You cannot delete this file system or
change its read and write access. The file systems that are added to the source zone are also listed. You can add more file
systems to the zone and define the size and access to the file system. You can enter the Reserved and Quota size for the
file system. Reserved is the size of the file system that the user can reserve. Quota is the maximum size that the file
system can utilize.
Note When you are modifying or adding new file systems to the new cloned zone, ensure that the new cloned zone has
enough required file system size to hold the source zone file system. For example, you cannot modify the root file sytem
of the new zone to a size lesser than the source zone root file system. This could result in incompatibility between the
new and the source zone, and the clone job can fail. Do not try to modify the system file system if they are already
defined in the source zone.
9. Click Next to configure the zone storage.
The libraries that are already associated with the source zone are listed. You can modify or associate libraries with the
new zone. The library can be either a NAS storage or Fiber Channel library. If the library is NAS storage, then specify the
virtual disk name and size of the disk. If the library is Fiber Channel, select a LUN from the available list of LUNs in the
library. The size of the selected LUN is displayed. You cannot change the size of the LUN.
The accumulated size of the storage is displayed as Currently Accumulated Storage. The required storage for the added
file system is displayed as Recommended Storage Size. You can click Next to proceed in the wizard, only when the
Currently Accumulated Storage size is equivalent to the Recommended Storage size.
10. Click the Add icon to configure more storage resources to the zone if the Currently Accumulated Storage is less than the
Recommended Storage Size.
11. Click Next to specify the network interfaces.
You need to assign at least one network to the zone. Select the zone IP type as Shared or Exclusive.
11.
Shared IP The networks that are assigned to the global zone with shared IP type are listed in the Networks list.
Select a network from the list. Each shared Network Interface Card (NIC) for the selected network is listed in the
NIC list. Select a NIC from the list. If the selected network has its defined IP range, then Auto Allocate IP is
displayed in the Management Interface. The Zone IP will be automatically populated with an IP in the defined
range. If the selected network does not have any IP range defined, then in the Management Interface, Use Static
IP is displayed. You must enter a valid IP address in the Zone IP field.
Exclusive IP The networks that are assigned to the global zone and not used by other zones are listed in the
Networks list. Select a network from the list. The NICs that are not bound to other networks are listed in the NIC
list. Select a NIC from the list. If the selected network has its defined IP range, then Auto Allocate IP is displayed
in the Management Interface. The Zone IP will be automatically populated with an IP in the defined range. If the
selected network does not have any IP range defined, there are two options in the Management Interface to
select. You can select Use Static IP and enter a valid IP address in the Zone IP field. If you have an external DHCP,
select the option Assigned by ext. DHCP. The Zone IP is automatically allocated by the DHCP external to Ops
Center. Automatically Allocated is displayed in the Zone IP field.
12. Click Next to view the summary of the selected parameters for replicating the zone.
13. Click Finish to launch the job for replicating a zone.
When the job successfully completes, the new zone will be displayed in the Assets section.
Migrating Zones
You can migrate a zone created using Ops Center. There are two methods by which you can migrate a zone in Ops Center:
Migrating a zone from one global zone to another global zone managed by Ops Center.
Migrating an existing Solaris system into a zone on a global zone. This is referred to as physical to virtual (P2V)
conversion.
Destination Global
Zone
Source Global
Zone
Solaris 10
8/07
Solaris 10
5/08
Solaris 10
10/08
Solaris 10
5/09
Solaris 10
10/09
Incompatible
Incompatible
Incompatible
Incompatible
Incompatible
Incompatible
Solaris 10 8/07
Incompatible
Compatible
Incompatible
Compatible
Compatible
Compatible
Solaris 10 5/08
Incompatible
Incompatible
Compatible
Compatible
Compatible
Compatible
Solaris 10 10/08
Incompatible
Incompatible
Incompatible
Compatible
Compatible
Compatible
Solaris 10 5/09
Incompatible
Incompatible
Incompatible
Incompatible
Compatible
Compatible
Solaris 10 10/09
Incompatible
Incompatible
Incompatible
Incompatible
Incompatible
Compatible
When you click the Migrate Zone option in the Actions panel, the Ops Center first checks for global zones that are compatible for
migration. If there are compatible global zones in the managed Assets list, then the Migrate Zone wizard is displayed. Otherwise, a
pop-up window is displayed, informing you that the zone cannot be migrated.
The zone migration will be carried out successfully only on following certain conditions:
There should be compatible global zones in Ops Center for the zone to be migrated.
The compatible global zones should have access to all the libraries associated with the zone.
The zone image is not stored in the global zone local library.
The zone should not use global zone local library for storage. It has to be associated with NFS or Fiber Channel library
for storage.
The Migrate Zone option is enabled only when the zone is in the running state.
You can migrate zones that were created only through Ops Center.
If you migrate a zone that was created using Ops Center, you cannot use an alternate boot environment (ABE) to
upgrade the zone.
patches and packages. You can use the Update OS Profiles to back out the patches and packages. Follow the steps in Ops Center
to backout the patches and packages:
1. Create an OS Update Profile with the list of patches and packages that need to be backed out.
For more information, see Creating an OS Update Profile to create an OS Update Profile.
2. Select the zone for which you want to backout the patches and packages.
3. Create a New Update OS Job with the OS Update Profile.
The OS Update job removes or downgrades the patches and packages of the zone. Then, you can run the migration job
on the zone. For more information, see Creating a Solaris OS Update Job to create an OS update job.
Updating Zones
Ops Center enables you to update the global and non-global zones of your Solaris systems. You can run a patch job on the global
zone and update all zones without using the -G command.
The concepts that relate to updating global and non-global zones and the procedures to update the zones are described on this
section.
Content
Description
Action
SUNW_PKG_ALLZONES
If the value is true, the package is installed on all zones, both global and non-global.
SUNW_PKG_HOLLOW
If the value is true, the package information is propagated to the non-global zones, but the package
is not installed.
SUNW_PKG_THISZONE
3. Set the -G parameter to true for the action that you want to perform.
4. Save and close the file.
5. For this change to take effect, restart the services using the following commands:
SUNW_PKG_THISZONE
SUNW_PKG_HOLLOW
Impact
Impact with -G
configuration
False
False
False
True
False
False
True
False
True
False
True
False
Patches are simply sets of updates to packages. When you install a patch, the patch will be installed on the global zone and the
non-global zones, depending on the package parameters as shown in the previous table.
Note Use caution while enabling the -G option on a host with sparse zones. Packages that are inherited from the global zone,
which are not SUNW_ALL_ZONES, cannot be patched within a sparse zone.
As a zone administrator, you can install packages and patches on non-global zones. The patchadd and pkgadd command
should be used without any options. Do not configure the -G switch to the commands while updating the non-global zones.
Refer to the following table when you are updating a non-global zone. The results shown in the table determine whether the
update job will be successful, depending on the package information.
Note The -G switch does not have any impact on installing packages or patches in a non-global zone.
SUNW_PKG_ALLZONES
SUNW_PKG_THISZONE
SUNW_PKG_HOLLOW
Impact
False
False
False
True
False
False
True
False
True
False
True
False
Patches are simply sets of packages that need to be installed. If any one of the packages has the SUNW_PKG_ALLZONES set to
true, then the patch installation fails. For a successful patch installation, ensure that none of the packages have
SUNW_PKG_ALLZONES set to true.
Note Packages that deliver to read-only inherit directories will fail to install to sparse root zones. Such packages should be
installed from the global zone with the -G switch disabled. If such a package has the parameter SUNW_PKG_THISZONE=true, it
will not appear as installed from the sparse zone and the software might not function correctly. In this case, a whole root zone
should be used. In general, packages with SUNW_PKG_THISZONE=true should not deliver to read-only inherit directories.
Halting a Zone
When you halt a zone, it removes both the application environment and the virtual platform for a zone. Halting a zone changes
the zone-ready state to installed state. When the zone is brought to halt state, all processes are killed, devices are unconfigured,
network interfaces are unplumbed, file systems are unmounted, and the kernel data structures are destroyed.
To Halt a Zone
1. Select a zone from the Assets section in the Navigation panel. Alternatively, you can select a global zone from the Asset
section and then select a zone from the Zone contents pane in the center panel.
2. Click Halt Zone in the Actions panel or click the Halt Zone icon in the center panel.
The Halt Zone window is displayed.
3. Click Halt Zone to halt the zone.
Deleting a Zone
When you delete a running zone, the zone is halted, uninstalled, then deleted from the global zone. When you delete a zone, the
following changes are also made:
Zone root file system is deleted.
Other file systems that were added to the zone deleted.
Zone metadata is deleted from the corresponding library.
The zpool corresponding to the zone are deleted and the storage is freed and made available.
Any exclusive IPs that were assigned to the zone are available for re-use
To Delete a Zone
1. Select a zone from the Assets section in the Navigation panel.
2. Select Delete Zone from the Actions panel.
The Delete Zone window is displayed.
3. Click Delete Zone to confirm whether you want to delete the zone.
The zone is deleted and removed from the Assets tree.
Monitor Assets
Ops Center enables you to monitor the following assets in your data center:
OS Monitoring
Hardware Monitoring
Note To manage and monitor an operating system, you must first use Ops Center to discover the OS, and then install agent
controller software. The agent supports the update, management, and monitoring operations.
OS Monitoring
Content
Description
About
Monitoring
Monitoring
an OS
Describes how to monitor the health of operating systems, and how to edit variables that control how OS
monitoring takes place
Monitoring a
Windows OS
Describes how to configure your Windows operating systems to enable remote monitoring, how to monitor the
health of your Windows operating systems, and how to edit variables that control how OS monitoring takes
place
Charts
Describes how to view and read the charts that Ops Center uses to visually present monitoring data
Rebooting an
OS
Managing
Boot
Environments
Hardware Monitoring
Content
Description
Describes how to access the serial console with the Ops Center software.
Describes different power states of a system and how to power on or power off
a system
Resetting a Server
Note You cannot perform any management or monitoring actions on the Ops Center Enterprise Controller or Proxies.
Monitor Assets
Ops Center enables you to monitor the following assets in your data center:
OS Monitoring
Hardware Monitoring
Note To manage and monitor an operating system, you must first use Ops Center to discover the OS, and then install agent
controller software. The agent supports the update, management, and monitoring operations.
OS Monitoring
Content
Description
About
Monitoring
Monitoring
an OS
Describes how to monitor the health of operating systems, and how to edit variables that control how OS
monitoring takes place
Monitoring a
Windows OS
Describes how to configure your Windows operating systems to enable remote monitoring, how to monitor the
health of your Windows operating systems, and how to edit variables that control how OS monitoring takes
place
Charts
Describes how to view and read the charts that Ops Center uses to visually present monitoring data
Rebooting an
OS
Managing
Boot
Environments
Hardware Monitoring
Content
Description
Describes how to access the serial console with the Ops Center software.
Describes different power states of a system and how to power on or power off
a system
Resetting a Server
Note You cannot perform any management or monitoring actions on the Ops Center Enterprise Controller or Proxies.
About Monitoring
Ops Center enables you to monitor the following assets in your data center:
Managed operating systems
Servers
Chassis
Note To manage and monitor an operating system, you must first use Ops Center to discover the OS, and then install agent
controller software. The agent supports the update, management, and monitoring operations.
OS Monitoring
You can monitor the health of your Solaris, Linux, and Windows operating systems. You can edit the variables that control how OS
monitoring takes place. You can also reboot your OS from the Ops Center BUI.
Hardware Monitoring
You can monitor and manage your servers and chassis from a central BUI, including the following:
Hardware health status
Manage and monitor the power states of a system and power systems on and off
Display and chart power usage:
ILOM based servers
ILOM based chassis
Monitor hardware variables and connectivity, including M-series servers
Reset a server
Display job status and job history
Use locator lights to locate assets
About Monitoring
Ops Center enables you to monitor the following assets in your data center:
Managed operating systems
Servers
Chassis
Note To manage and monitor an operating system, you must first use Ops Center to discover the OS, and then install agent
controller software. The agent supports the update, management, and monitoring operations.
OS Monitoring
You can monitor the health of your Solaris, Linux, and Windows operating systems. You can edit the variables that control how OS
monitoring takes place. You can also reboot your OS from the Ops Center BUI.
Hardware Monitoring
You can monitor and manage your servers and chassis from a central BUI, including the following:
Hardware health status
Manage and monitor the power states of a system and power systems on and off
Display and chart power usage:
ILOM based servers
ILOM based chassis
Monitor hardware variables and connectivity, including M-series servers
Reset a server
Display job status and job history
Use locator lights to locate assets
Description
Monitoring
an OS
Describes how to monitor the health of operating systems, and how to edit variables that control how OS
monitoring takes place.
Monitoring a
Windows OS
Describes how to configure your Windows operating systems to enable remote monitoring, how to monitor the
health of your Windows operating systems, and how to edit variables that control how OS monitoring takes
place.
Managing
Boot
Environments
Charts
Describes how to view and read the charts that Ops Center uses to visually present monitoring data.
Rebooting an
OS
Refer to Managing and Monitoring Zones for monitoring zones, and Monitoring a Logical Domain Host and Monitoring a Guest
for monitoring Logical Domains.
Description
Monitoring
an OS
Describes how to monitor the health of operating systems, and how to edit variables that control how OS
monitoring takes place.
Monitoring a
Windows OS
Describes how to configure your Windows operating systems to enable remote monitoring, how to monitor the
health of your Windows operating systems, and how to edit variables that control how OS monitoring takes
place.
Managing
Boot
Environments
Charts
Describes how to view and read the charts that Ops Center uses to visually present monitoring data.
Rebooting an
OS
Refer to Managing and Monitoring Zones for monitoring zones, and Monitoring a Logical Domain Host and Monitoring a Guest
for monitoring Logical Domains.
Monitoring an OS
Select the OS from the asset list in the Navigational panel to view the Summary page in the center panel. Each operating system
(OS) is monitored for the following characteristics:
Connectivity
File system status
Monitoring variables
CPU usage
Memory usage
Network usage
In the Summary page, the following information about the OS is displayed:
OS Name
Server name
Health status
Notification status
OS details
OS monitoring variables
1. Select the OS group from the Assets section in the Navigation panel.
The Summary page of the selected OS group is displayed.
2. In the Actions panel, select the option Change Monitoring Thresholds.
The Change OS Monitoring Thresholds For All Members of the Group window is displayed.
3. Edit the threshold variables as required.
Note Only the percentage values of the warning and critical thresholds of the monitoring variables can be changed.
4. Click Change Thresholds to set the newly entered values.
The new value will be set for all the members of the group.
OS Health States
The different OS health states are as follows:
Good The server is working properly.
Unknown An error occurred while attempting to retrieve information about the health of the OS resource. The server
is connected but does not return any information.
Unreachable The server agent IP address cannot be contacted for the status of the health of the OS resource. This
indicates network problems or that the server is in standby mode.
Warning Failure A potential or impending fault condition has been detected on the server. Action should be taken to
prevent the problem from becoming more serious.
Critical Failure A fault condition has occurred on the server. Corrective action is required.
Monitoring an OS
Select the OS from the asset list in the Navigational panel to view the Summary page in the center panel. Each operating system
(OS) is monitored for the following characteristics:
Connectivity
File system status
Monitoring variables
CPU usage
Memory usage
Network usage
In the Summary page, the following information about the OS is displayed:
OS Name
Server name
Health status
Notification status
OS details
OS monitoring variables
1.
2.
3.
4.
5.
6.
The Summary page of the selected OS is displayed. For Linux OS, the Summary page is displayed with the current values
for the monitoring variables.
Select the OS Details tab from the center panel.
Select the variables for which you want to change the threshold values for Warning and Critical.
Use the Shift key to select more than one variable.
Click the Change Threshold icon.
The Change OS Monitoring Thresholds window is displayed with the selected variables.
Enter the Warning and Critical thresholds values as required.
For all the variables, the unit of measurement is displayed. The values depend on the number of processors in your
system and on the usage characteristics.
Click Change Thresholds to submit the changes.
Ideally, the value of any given monitored OS health attribute is compared to a threshold value. Monitoring variable values are
compared against the thresholds at regular intervals. If the value of a monitored OS health attribute rises above the warning
threshold, notification is issued with the status of Warning Failure. If the value continues to increase and passes the critical
threshold, notification is issued with the status of Critical Failure.
Note You can set specific threshold values for different operating systems.
OS Health States
The different OS health states are as follows:
Good The server is working properly.
Unknown An error occurred while attempting to retrieve information about the health of the OS resource. The server
is connected but does not return any information.
Unreachable The server agent IP address cannot be contacted for the status of the health of the OS resource. This
indicates network problems or that the server is in standby mode.
Warning Failure A potential or impending fault condition has been detected on the server. Action should be taken to
prevent the problem from becoming more serious.
Critical Failure A fault condition has occurred on the server. Corrective action is required.
Monitoring a Windows OS
Ops Center enables you to manage and monitor your Windows, Solaris, and Linux operating systems from a single console. A
lightweight Java agent monitors key OS parameters such as CPU, memory, swap space, file system, I/O, and power information.
The monitoring capabilities are available when your Enterprise Controller is connected to the Internet, or in an environment
without an Internet connection (disconnected mode).
You can configure the thresholds to meet your data center guidelines. You are notified when a defined threshold is exceeded.
You choose how you want to receive the alert: by email or on the BUI. Event logging records all events for the monitored
attributes.
Comprehensive Monitoring
You can manage and monitor your Windows OS with Ops Center, including the following key OS parameters:
Connectivity
File system status
Monitoring variables
CPU usage
Memory usage
Network usage
Historical data includes CPU, memory, I/O and power data. You can store the data for future management analysis. Based on the
data collected, users can graph the historical data for trend analysis and forecasting.
Content
Description
Describes the attributes available for monitoring and how to display them in the BUI
Monitoring a Windows OS
Ops Center enables you to manage and monitor your Windows, Solaris, and Linux operating systems from a single console. A
lightweight Java agent monitors key OS parameters such as CPU, memory, swap space, file system, I/O, and power information.
The monitoring capabilities are available when your Enterprise Controller is connected to the Internet, or in an environment
without an Internet connection (disconnected mode).
You can configure the thresholds to meet your data center guidelines. You are notified when a defined threshold is exceeded.
You choose how you want to receive the alert: by email or on the BUI. Event logging records all events for the monitored
attributes.
Comprehensive Monitoring
You can manage and monitor your Windows OS with Ops Center, including the following key OS parameters:
Connectivity
File system status
Monitoring variables
CPU usage
Memory usage
Network usage
Historical data includes CPU, memory, I/O and power data. You can store the data for future management analysis. Based on the
data collected, users can graph the historical data for trend analysis and forecasting.
Content
Description
Describes the attributes available for monitoring and how to display them in the BUI
Windows OS Attributes
Ops Center can monitor the following OS attributes that are supported by WMI:
Status
Host name
CPU usage
File system usage
Description
CPU architecture
Memory usage
Swap usage
Interface information
System up time
Windows OS Operations
You can perform the following operations:
Shutdown
Reboot
Unconfigure and shutdown
Server Attributes
You can monitor the following server attributes from the BUI:
Boot device information
Status
CPU information
Ethernet port information
Manufacturer
Memory information
Model
Serial number
Server Operations
You can perform the following server operations from the BUI:
Reset
Shutdown
OS Health States
The following are definitions of the different OS health states:
Good The server is working properly.
Unknown An error occurred while attempting to retrieve information about the health of the OS resource. The server
is connected but does not return any information.
Unreachable The server agent IP address cannot be contacted for the status of the health of the OS resource. This
indicates network problems or that the server is in standby mode.
Warning Failure A potential or impending fault condition has been detected on the server. Action should be taken to
prevent the problem from becoming more serious.
Critical Failure A fault condition has occurred on the server. Corrective action is required.
Charts
Ops Center provides a variety of charts to help you optimize your data center resources. You can create the usage charts 24 hours
after you start to manage the gear. By default, Ops Center gathers information every five minutes and displays an hour of
utilization data in the Summary tab and OS Details page of any managed asset.
The table shows all of the available charts and the type of asset that uses the chart.
Chart
Description
Type of Asset
Power Utilization
Power usage
Servers
CPU Utilization
Memory Utilization
Memory usage
Network Utilization
Network usage
System Load
System load
OS
Note Charts are not displayed if the asset is not operating or is unreachable.
The data is retained for six months. However, after the fifth day, the data is compressed into larger time intervals as described in
the following table:
Age
Interval
Up to 5 days
Every 5 minutes
5 days to 3 weeks
3 weeks to 6 weeks
6 weeks to 6 months
6 months
Data is removed
To Display Charts
You can use the default format or change the charts to use a line, bar, or area format or to use different time intervals.
1. Select Assets from the Navigation panel.
2. Select an asset.
The Summary page is displayed in the center panel, which includes hourly charts of CPU, Network, and Memory
utilization.
3. Click the Charts tab in the center panel.
4. Select the plot type.
You can select the resources such as CPU, network, memory file system, and system load.
5. Select the Chart option to display the charts as thumbnail images or single charts.
When you select thumbnail images, you can accommodate all the resource utilization in one page.
6. Select the type of chart.
7. Select the time interval represented in the X-axis.
8. Select the utilization represented in terms of percentage or unit of measure in the Y-axis.
The following sample chart is for a managed OS asset.
Server
Chassis
CPU
System Load
Network
Memory
OS
Host
Allocated Memory
Power
Rebooting an OS
You can reboot an OS from Ops Center.
To Reboot an OS
1. In the Navigation panel, select the OS from the Asset section.
2. Select Reboot in the Actions panel.
A confirmation window is displayed.
3. Confirm the reboot action.
alternate boot environment. Before you activate an ABE, you can synchronize it with the live boot environment and capture those
applications.
3.
associated ABE, the Boot Environments tab appears in the center panel.
4. Click the Boot Environments tab in the center panel. All associated boot environments are displayed in the center panel.
The active boot environment appears first and shows an Active status. One or more alternate boot environments are
displayed below the active boot environment.
5. Click the inactive boot environment that you want to activate.
6. Click Activate Boot Environment and Reboot in the Actions panel.
To use console access for both the OS and service processor (SP), you must discover the OS and the SPs on the hardware, then
enable SSH access. This is done by performing a custom discovery of the assets.
If you have a managed asset that does not have SSH enabled, or the SP or OS are not discovered, you can run a new custom
discovery job to add capabilities. After successfully running the new custom discovery job, your managed asset is automatically
upgraded to include the new capabilities.
Note The console requires SSH access and the ability to reach the system.
Serial console access requires appropriate firewall and routing settings for the Enterprise Controller to connect to the Proxy
Controller or agent through ssh (on port 22).
Description
Good
Unknown
An error occurred while attempting to retrieve information about hardware health. The server is connected
but is not returning hardware health information.
Unreachable
The server cannot be contacted for information about the status of hardware health. This state is most often
caused by a network problem.
Warning Failure
A potential or impending fault condition has been detected on the server. Action should be taken to prevent
the problem from becoming more serious.
Critical Failure
Nonrecoverable
Failure
Faulted
The hardware declares that there is a fault. Contact service personnel to fix the hardware.
Features Monitored
The following monitoring features are available for the M-Series server:
Power on
Power off
CPU usage information
Memory usage information
Firmware information
Sensor information
Hardware variables, such as power supply and voltage, are not monitored.
The figure below is an example of monitored sensor information.
2.
Oracle Enterprise Manager Ops Center
In the group Summary page, the servers in the group are displayed under All Assets in Group. You can select a server or
a set of servers from the list.
Note You can manage the locator lights for homogeneous hardware groups only .
3. Select a server or a set of servers from the list in All Assets in Group.
When the servers are selected, the available action icons are highlighted.
4. Click the Locator Light On or Locator Lights Off icon as required.
The LED locator light on each physical server or blade will be switched on or off accordingly.
Description
On
Standby
Unknown
An error occurred while attempting to retrieve the power status of the hardware. The server is connected but is
not returning any information on power status.
Unreachable
The server cannot be contacted for information about its power state. This most often indicates a network
problem or that the server is in standby mode.
Ops Center collects power utilization data from ILOM systems that are capable of monitoring and reporting back the following
attributes:
available_ power
permitted power
actual_power
Power consumption of a system is the sum of the input power consumed by each power supply. To measure the input power, the
interfaces should be exposed and the service processors should be able to retrieve and report data with one-minute accuracy. The
input power is the power pulled in to the system's power supplies from an external resource. Output power is the amount of
power provided from the power supply to the system components, measured at the power supply output. Input power is
calculated from output power by applying an efficiency function to the output power from each power supply.
Calculating power compensation for the blades is difficult because the power supplies are shared. The blades give a report on the
power consumption of the local components, but this does not reflect the accurate power consumption of a blade.
Power Monitoring
ILOM
Version
Firmware
Version
Available
2.0.1.7
SW2.1
Available
2.0.4.15
SysFW 7.0.8
Sun SPARC Enterprise T5120 (SEC, Sun SPARC Enterprise T5220 (SED))
Available
2.0.4.6
SysFW 7.0.9
Sun SPARC Enterprise T5140 (SET), Sun SPARC Enterprise T5240 (SEU)
Available
2.0.4.x
SysFW 7.0.10
Available
2.0.4.x
SysFW 7.0.x
Available
2.0.4.x
SysFW 7.0.x
Available
2.0.4.x
SysFW 7.0.x
Available
2.0.2.10
SW1.x
Available
2.0.3.10
SW2.x
Available
2.0.3.9
SW1.0
Available
2.0.3.9
SW1.0
Sun Fire X4140 (1U) (B12), Sun Fire X4240 (2U) (B14)/Sun Fire X4440
(B16)
Available
2.0.3.10
SW1.x
x4600/x4600m2
Available
2.0.3.10
SW2.1
x4100/x4200
x4100m2/x4200m2
Available
(approximate
input)
2.0.3.10
SW2.1
Available
2.0.4.x
SysFW 7.1.x
Available
SW3.x
Available
SysFW 7.1.x
Available
SysFW 7.1.x
Lynx
Available
Available
Supernova
Bronze/Platinum/
Silver
Available
Available
Monitoring Connectivity
Connectivity is the network interface of the system. The Network Interface Card (NIC) information is displayed in the Connectivity
tab of the selected hardware in the Assets section.
NIC details such as name, connection status, MAC address, and the corresponding IP address are displayed.
Resetting a Server
You can reset a server or a set of servers.
To Reset a Server
1. Select a server or server group from the Assets in the Navigation panel.
2. Click Reset Server(s) to reset the system. For a group, select the list of servers from the group and click the Reset
Server(s) icon. A Reset pop-up window appears with the following options:
Reset
Force Reset
Reset with Network Boot
3. Click the appropriate option as required to reset the selected hardware.
You can view information about historical and current jobs for selected assets.
Current Jobs that are running. The status of each job is Running or Scheduled.
Historical jobs that have run previously and are completed.
Libraries
An Ops Center library stores and manages cached data, images, patches, and metadata for the use of virtualization hosts.
Content
Description
About Libraries
Describes how the hosts in a virtual pool get access to the resources in libraries.
Updates Library
Storage Libraries
About Libraries
Ops Center uses libraries to store and manage cached data, images, patches, and metadata. For images, the libraries store the
following types:
ISO image: operating system (OS) or other software applications
Appliance image: Pre-configured application and an operating system
Snapshot: Particular state of a virtual machine
Libraries are categorized by the type of content stored in them:
OS Provisioning Library: ISO images
Firmware Provisioning Library
Updates Library for Solaris and Linux
Storage Libraries
OS Provisioning Library
The OS Provisioning Library manages the ISO images, any FLAR files associated with an ISO image, and the profile for each ISO
image. The ISO images are used to provision one or more systems with an operating system. The OS profile describes how to
configure one OS image, or one FLAR associated with one OS image, when the OS image is installed on a set of target systems.
The library's files are located in the following directories of the Enterprise Controller:
/var/opt/sun/xvm/images/os/iso
/var/opt/sun/xvm/images/os/flars
During the provisioning process, the OS images and FLAR files are copied from the library to each Proxy Controller's
/var/opt/sun/xvm/proxyImageCache/os/iso directory.
To see the contents of the library, see Viewing the Available OS Images and Viewing the Available OS Profiles
To add images and FLARs to the library, see Importing OS Images and FLARs.
/var/opt/sun/xvm/images/firmWare
To see the contents of the library, see Displaying Firmware Images and Displaying a Firmware Profile.
To add images and profiles to the library, see Creating a Firmware Image and Creating a Firmware Profile.
See About Firmware Provisioning for an overview of the basic concepts.
See Provision Firmware for more information about managing firmware profiles and updating firmware.
Updates Library
Ops Center enables you to update, or patch, the following operating systems:
Solaris software
Linux
Windows
To see the contents of the Updates Library and to add to the contents, see Updates Library.
Storage Libraries
When a guest (virtual image) is created, the configuration information for its operating system, data, CPU, memory, and network
details are saved as metadata in a storage library. The data files reside in the same location as the metadata. Storage libraries are
of the following types, depending on the type of virtualization.
Fibre Channel Libraries for LDom hosts
Viewing the Contents of a Fibre Channel Library
Creating a Fibre Channel Library
Network Attached Storage (NAS) Storage Libraries for all types of virtualization data
Viewing the Contents of a NAS Storage Library
Creating a NAS Storage Library
Updates Library
The Updates library contains the policies and profiles used to upgrade an operating system. It also stores any local content your
organization requires such as files, scripts, executables, or binaries that are not known to the hosted tier.
Local content files typically include instructions that must be carried out before or after a job. For example, you might develop a
script to test managed hosts before running a job.
Local content files are stored in the Enterprise Controller and are not synchronized with Sun's knowledge base.
Use Ops Center to upload local content to the Updates library, to add categories for your content, to edit a component file, and
to delete a local component from your library.
Managing Profiles
The Solaris/Linux OS Updates library contains system-defined profiles and any custom profiles that have been created. See
OS Update Profiles for information on using and creating update profiles.
Managing Policies
The Solaris/Linux OS Updates library contains system-defined polices and any custom policies that have been created. See
OS Update Policies for information on using and creating update policies.
Description
Uploading Local
Software in Bulk
Describes how to upload (in bulk) patches, packages, and RPMs from either a directory or an OS
image.
Describes how to view the history and details of the software that you have uploaded in bulk.
Uploading a Local
Software Package
Uploading a Local
Configuration File
Uploading a Local
Action
Adding a Local
Category
Describes how to define your own sub-categories or to organize the files under a specific node.
Editing a Local
Component File
Describes how to edit the specific information associated with the file or to replace the file.
Deleting a Local
Component
Viewing Component
Details
Describes how to view details about your file including distribution, version, release, group, size URL,
who added and edited the file, as well as any summary and description information.
Uploading Software in
Disconnected Mode
Describes how to upload software while your environment is disconnected from the Enterprise
Controller (disconnected mode).
4.
5.
6.
7.
8.
You cannot edit or delete one of the default categories. However, you can edit and delete a subcategory and you can delete the
content in the subcategory. See Deleting a Local Component.
4. To specify the file, you can type its name or click the Browse button to navigate to the file.
If the file is a component of a different distribution, click Distribution to select the correct distribution. The files in the
the selected distribution are displayed.
5. Select either Edit existing file or Replace existing file.
If you choose to edit the file, make changes to the file and click Save.
If you choose to replace the file, browse for the replacement file and click Upload.
4.
5.
6.
7.
4. In Target path on server, type the full path to the directory on the managed hosts where the files must be installed.
5. In Version, type an identifying name for this version of the file. This value is appended to the file name when it is
displayed in a Components list.
6. Type a brief description of the file.
7. Select the Distribution to which this file is applied.
You can choose multiple distributions.
8. In Parent, accept the Configuration Files category or click Browse to locate a subcategory.
9. Click Browse to locate and select the configuration file.
10. Click Upload.
The file is uploaded to the selected distributions.
To create a configuration job, create a profile that includes this configuration file. See Creating OS Profiles for Solaris Systems and
Creating OS Profiles for Linux Systems.
3.
4.
5.
6.
7.
8.
Select Yes if the package is a security fix for a previous version of the software. Otherwise, select No.
Click the name of the distribution to which you want to add this package.
In Parent, click Local PKGs or click Browse to locate a subcategory.
In Files, select the software package.
Click Upload.
The software package is uploaded and listed under the Local Content.
To create a configuration job, create a profile that includes this package. See Creating OS Profiles for Solaris Systems and Creating
OS Profiles for Linux Systems.
The uploaded components list displays the name, description, status, and date for each component.
4. Select a component and click View Results.
The details of the uploaded components are displayed.
Storage Libraries
A storage library contains data and the metadata used by virtualization software so that both types of information are available to
hosts through Ops Center.
When a virtual image (guest) is created, the configuration information for its operating system,
data, CPU, memory, and network details are saved as metadata in a storage library. The data files reside in the same location as
the metadata: in local, NFS, or CIFS storage libraries. Storage libraries are also used to group raw block storage devices, such as
fibre channel SANs or NAS-hosted large-files.
Ops Center does not manage storage resources, that is, Ops Center does not create, modify or update LUs on disk arrays and it
does not manage NAS shares on NAS systems. Ops Center manages how hosts get access to the metadata by controlling access to
the storage libraries where the metadata resides. Hosts, which must have appropriate storage management utilities and services,
use NFS or CIFS services to attach to the storage libraries. For example, to get access to a CIFS storage library, the smbfs
filesystem must be available to the host.
In configurations that use virtual pools, the storage libraries are associated with the pool; any host in a virtual pool can get access
to the storage libraries that are associated with the virtual pool.
Storage libraries are identified by the type of storage and by the type of virtualization.
Type of Virtualization
Storage Requirements
Logical Domains
(LDom)
All types
The diagram shows how the storage libraries and types of virtualization interact with virtual disks.
SAN storage libraries expose data as logical units (LUNs), identified by their LUN GUIDs.
NAS storage libraries expose data as raw files and files in VMDK format.
The LUNs, raw files, and raw volumes store data and provide the metadata for the guests. The metadata for NAS virtual disks are
stored in the NAS Storage Library. Metadata for SAN virtual disks is persisted in the SAN Storage Library.
LUN
LUN is part of the address of the storage that you are presenting to a host. LUNs have a finite set of resources available, such as
the amount of data that can be stored, as well as the number of active commands that a device or LUN can process at one time.
Each LUN is of fixed size. You cannot modify the size. You cannot sub-divide LUNs among Logical Domain guests and zones. When
a LUN is assigned to a global zone or a Logical Domain guest, this LUN cannot be assigned to other guests. For example, you have
five LUNs in a fibre channel library. You have assigned the first LUN to a Logical Domain guest. In such a case, the first LUN
cannot be assigned to other guests.
Since LUNs cannot be sub-divided among hosts, the user needs to perform significant initial planning with respect to storage
optimization. The user has to ensure that the storage space in LUNs is utilized as much as possible. The user needs to analyze the
storage requirements of zones and Logical Domain guests and assign LUNs of appropriate size to them.
target A SCSI storage server which exposes logical units that can be accessed by SCSI initiators.
WWN (Word Wide Name) A globally unique identifier which is associated with SCSI initiators or targets.
Description
Describes the major steps in configuring storage for fibre channel libraries. This configuration
needs to be performed outside of Ops Center.
Log in to the fibre channel disk array using the service processor credentials.
Define volumes on the disk array with the required number of disks.
Initialize the volumes on the disk array.
Create LUNs (slices) from the volumes. These LUNs will be used by zones and Logical Domain guests.
Map the LUNs (slices).
Enable the Multipath support (MPxIO) on the fibre channel disk array for the fibre channel LUNs to be visible through
Solaris multipathing.
4. In the Identify Library panel, enter the name and description of the library. Click Next.
The Associate Library panel is displayed.
5. If you want to manually add LUNs to the library, see Adding LUNs to the Library Manually.
OR
If you want to select LUNs from the available LUNs, see Selecting LUNs from the Available LUNs.
2. Click the
icon and enter the GUID/WWN and name of the LUNs. You can add LUNs that are visible (mapped and not
masked) to the host that can access them. You must enter at least one LUN GUID to create a Fibre Channel library. Click
Next.
Note GUID is the Global Unique Identifier that is associated with each LUN. WWN is a unique identifier that is
associated with SCSI initiators or targets.
3. The Summary panel is displayed.
4. Review the details in the Summary panel. The Summary panel displays details such as name, description, LUN GUID, and
LUN Name.
5. Click Finish to create a Fibre Channel library.
1. In the Associate Library panel of the Create New Fibre Channel Library wizard, select Associate the new library with the
selected items.
The Associate Library panel is displayed.
A table is displayed that contains the name, description, and type of virtual pools, Logical Domain hosts, and global
zones.
2. Select at least one item from the table that you want to associate with the new library. You can view and select LUNs that
are accessible from the selected systems in the next step.
Click Next.
3. The Identify LUNs panel is displayed.
4. Select LUNs from the Available LUNs table. You must select at least one LUN from the Available LUNs table to create a
Fibre Channel library. Click Next.
5. Review the details in the Summary panel. The Summary panel displays details such as name, description, and LUNs with
size.
6.
6. Click Save.
Check Whether the Fibre Channel Host Bus Adaptors (HBAs) Are Configured
bash-3.00# fcinfo hba-port
HBA Port WWN: 21000003ba68a3ac
OS Device Name: /dev/cfg/c1
Manufacturer: QLogic Corp.
Model: 2200
Firmware Version: 2.01.145
FCode/BIOS Version: ISP2200 FC-AL Host Adapter Driver: 1.14 01/11/20
Serial Number: not available
Driver Name: qlc
Driver Version: 20080617-2.29
Type: L-port
State: online
Supported Speeds: 1Gb
Current Speed: 1Gb
Node WWN: 20000003ba68a3ac
Check Whether the Fibre Channel HBAs Are Connected to the Fabric
bash-3.00# cfgadm -l
Ap_Id
c0
c1
c2
usb0/1
usb0/2
usb0/3
usb0/4
Type
scsi-bus
fc- private
scsi-bus
unknown
unknown
unknown
unknown
Receptacle
connected
connected
connected
empty
empty
empty
empty
Occupant
configured
configured
unconfigured
unconfigured
unconfigured
unconfigured
unconfigured
Condition
unknown
unknown
unknown
ok
ok
ok
ok
You can see that fc-private indicates that it is not connected to the fabric.
Description
If the boot disk is on the NFS share, the LDOM guest cannot be rebooted.
The LDOM guest cannot be migrated.
If you use a local library to store metadata for a standalone zone or standalone LDOM guest, the local library remains available.
However, any guest with metadata in a local library cannot be migrated.
You can store metadata for all guests in one NAS storage library or you can store each guest's metadata in a separate storage
library. The benefit of using separate storage libraries is to increase the ease of access from different global zones or from LDOM
control domains, to increase capacity, and to increase performance.
Tab
Description
Summary
Lists all the images in the library by type and the size and date it was modified. The types of images include:
Appliance/Guest Template Image, Backup Image, ISO Image, LDom Guest Image, Guest Image, and Zone Guest
Image.
Usage
Lists all Guest images in the library and the current information for each one such as Name, Tag, Allocated Memory,
vCPU, vCPU Utilization, and Size.
Disks
Lists all disks in the library by name and description and shows the current use of each one by allocation and size.
2.
For an ISO image, the Image Name and Description are displayed.
For guest images, the Summary page is displayed as shown in the illustration.
Description
Describes how to add images into the storage library, by upload, import, or
move.
# groupadd -g 60 xvm
3. Create the directory that you want to share, and set its ownership and permission modes. For example:
3.
# mkdir -p /export/virtlib/lib0
# chown xvm:xvm /export/virtlib/lib0
# chmod 777 /export/virtlib/lib0
4. Edit the /etc/dfs/dfstab file on the NFS server, and add an entry to share the directory with the correct share
options. For example, to share a directory named /export/virtlib/lib0, create the following entry:
Replace <domain name> with the domain name that you specified in the /etc/default/nfs file.
If you want the NFS share to be accessible outside the domain, use the rw option to specify the optional domain list.
Replace the <domain name n> entries with the correct domain names.
5. Share the directory and verify that the directory is shared. For example:
# shareall
# share
-
/export/virtlib/lib0
rw,root=_<domain>_,anon=60
"Share 0"
The share now allows the xvm user account and root user on the NFS clients to have write privileges. The special
options set the directory to allow write access, the domain to allow access as the root user, and specifies that the
anonymous user is seen on the clients as the user with UID 60 (xvm).
Note -- Add the domain name to the /etc/nsswitch.conf file so that root=<domain name> is effective.
If possible, use DNS instead of Network Information Service (NIS). DNS maps the host names to the IP addresses. Change the host
line to DNS in the /etc/nsswitch.conf file.
After setting up a share on the NFS server, the NFS client has to be prepared to mount the share.
xvm:x:60:60:xVM User:/:
4.
5.
6.
7.
Content
Description
Import Images
4. Enter the name of the file in the Source of ISO File field or click Browse to select the ISO image.
5. Enter the name and description of the image.
6. Click Upload Image.
The progress of the upload to the Enterprise Controller is displayed.
After uploading, the image is copied to the storage library.
Import Images
To import an image into a library, the image must reside in a blobs directory on the NFS or the CIFS server. To make images
available for importing, use the following procedure:
1. On the NFS or CIFS server, create a blobs directory under the storage mountpoint. For example, if the NFS mountpoint is
xvmserver1/nfs_share/lib1, the new directory is xvmserver1/nfs_share/lib1/blobs.
2. Copy the ISO and the appliance images to the new directory.
3.
Oracle Enterprise Manager Ops Center
Note If there is no image in the blobs directory, the following message is displayed;
No images found for library <library_name>
4. Enter a name for the image and a description.
5. Select an image from the list of images available.
6. Click Import Image to copy the image to the library.
Moving an Image
You can move an image from one library to another library.
1.
2.
3.
4.
For an ISO image, the Image Name and Description are editable.
For guest images, the Summary page is displayed. An example of guest image edit option is shown.
3. Click Submit to submit the updates.
Deleting Images
The Library Summary tab lists all the images (guest images, ISO images and appliance images) that are stored in that library.
To Delete Images
Note: When you delete a server image or guest image, the corresponding guests are also deleted.
1. Select the image from the storage library.
2. Click the Delete Image Details icon to delete the image.
3. Click OK to confirm the delete action.
bash-3.00#
bash-3.00#
total 6
drwxrwxrwx
drwxr-xr-x
drwxr-xr-x
cd /var/mnt/virtlibs/1238622271388
ls -all
3 nobody nobody 512 Apr 1 12:53 .
5 root sys 512 Apr 1 15:50 ..
2 nobody nobody 512 Apr 1 10:51 blobs
If nobody is displayed in the permissions, the NFS configuration is incorrect. The permissions must be the account name created
for the share, for example xvm, for both the user and group. To resolve this error, verify that the domain name has been defined:
1.
2.
3.
4.
NFS Share
Verify the NFS share mount by mounting the NFS share on the NFS client manually. Be sure you unmount the NFS client after
verifying.
Ops Center manages networks so you can create a network one time but deploy it multiple times. Each network has its own
values for parameters such as an IP address, subnet, time server, NIS, DHCP information, and so on. The hosts in these networks
are hypervisor hosts. Guests in the network communicate with each other or with the Internet through these hosts.
The Ops Center-managed networks are defined only within Ops Center so you cannot manage the network connections for
servers and chassis.
Content
Description
About Networks
Managing Networks
About Networks
You can use networks to do the following:
Manage individual hosts
Connect hosts to the Proxy Controller
Allow guests to communicate with each other or with the Internet
Connect remote JMX with the public API
A managed network depends on the physical network interface card (PNIC) that is available the host. You can create one
managed network for each physical network interface card. If one host has two PNICs, it is a good practice to create two
managed networks: a management network and a data network. This configuration lets you place all the guests on the data
network, keeping them separated from the management network, which gives access to internal resources of the data center.
The following configuration shows how two hosts participate in two managed networks.
The actual network connection is made to the PNICs in the Virtualization Host.
Network A is connected to PNIC 1 of both hosts and Network B is connected to PNIC 2 of the hosts.
Creating a Network
Before You Begin
You need to have a physical network interface card that is not used.
Note Starting with Release 2, you can also specify a link aggregation.
The mandatory network parameters are:
IP address of the network
Netmask
If you use static IP addressing, the IP address of the management interface
If you use dynamic IP addressing, the range of allowed IP addresses and the gateway address
To Create a Network
1. From the Navigation panel, click Managed Networks.
A list of physical networks appears under the Managed Networks section.
2.
Type the network name, description, and tags for the network.
Click Next.
4. In the Configure Network panel, choose whether to use a DHCP server to assign IP addresses.
Type the range of IP addresses for the network in the Assignable IP range field.
Type the default gateway address in the Default Gateway field.
MTU specifies the size of the packet in bytes. The value of MTU is 1500 and cannot be changed.
Click Next.
5. In the Specify Static Routes panel, add the static routes for the network.
Note The static routes and the default gateway are not used if the host uses Dynamic Routing mode.
Type the destination IP, netmask, and the default gateway.
If you want to add additional static routes, click Add and type the required information.
Click Next.
6. In the Specify Network Service panel, specify the time server, WINS, DNS, and NIS services of the guest.
This information configures the DHCP server, if DHCP support has been enabled.
Type the NIS domain name before typing NIS servers. However, you can type the DNS servers without typing a DNS
domain name.
Click Next.
7. In the Assign Network panel, select the items for the new network, such as virtual pools or guests.
Note Although this panel includes global zones, you cannot select them. To assign a global zone to this network, see
Assigning Networks to a Global Zone after you complete this procedure.
Click Next.
8. In the Specify NICs panel, attach one or more hosts to the network. For each host, specify its network connection and its
8.
management interface.
Note Starting with Release 2, you can specify a link aggregation as the network connection.
In the NIC column, each list displays the available NICs and link aggregations. For each host, specify the network
connection.
For the management interface, choose either a static IP address or a dynamic IP address.
For a static IP address, type the IP address of the management interface in the Mgmt Int. IP/DHCP
Client ID field.
For a dynamic IP address, the DHCP server assigns the client ID and displays it in the Mgmt Int. IP/DHCP
Client ID field.
Click Next.
9. In the Summary panel, review the network specifications.
Click Save to create the new network.
The new network is listed in the Managed Networks section.
Routing Modes
Virtualization hosts use one of the following routing modes.
No Dynamic Routing Mode
Dynamic Routing On Mode
Automatic Routing Mode
You specify the host's routing mode during its initial configuration, if you do not accept the default mode, Automatic Routing.
You can change the routing mode subsequently.
Deleting a Network
Before You Begin
Ensure that the network that is being deleted is not associated with any guests and is not part of any virtual pool.
Note You cannot delete the last network.
To Delete a Network
1. From the Navigation panel, click Managed Networks.
A list of physical networks appear under the Managed Networks section.
2. Select a network to be deleted.
3. From the Actions panel, click Delete Network.
The Delete a Network pop-up window appears.
4. Click Delete Network.
The virtualization hosts that are attached to the network are detached from the network. The assigned resources such as
DHCP server are released from the network. The network is also dissociated from the virtual pools.
Description
Describes how to view the virtualization hosts, such as the LDom Hosts, and
guests that are using the network.
5.
The guests that are connected to a network are displayed in the Network Connections table of the network. A new guest
connection to the network is created and is effective when the guest is re-started.
Authentications
Authentications are necessary to download content such as updates from SunSolve or third-party sites.
You can add or edit authentications to access additional external resources.
To Edit Authentications
1. Click the Enterprise Controller in the Administration section of the Navigation Panel.
2. Click Edit Authentications in the Actions panel.
The Edit Authentications window is displayed.
3. Edit one or more of the authentications by editing the description, user name, and password.
4. Click Submit.
A job is launched to update the authentications.
2. Create an empty file named /var/tmp/xVM/mypasswd, and set its permission mode to 400.
# touch /var/tmp/xVM/mypasswd
# chmod 400 /var/tmp/xVM/mypasswd
3. Edit the /var/tmp/xVM/mypasswd file so that it contains the password of the user that you designated as the
3.
administrator of your Ops Center Enterprise Controller. The following echo command appends the password to the
/var/tmp/xVM/mypasswd file. (Replace password with the correct password.) For example:
# echo 'password' > /var/tmp/xVM/mypasswd
4. Use the proxyadm command to register the co-located Center Proxy Controller with the Enterprise Controller.
Solaris OS: Use the /opt/SUNWxvmoc/bin/proxyadm command.
RHEL OS: Use the /opt/sun/xvmoc/bin/proxyadm command.
The example command below uses the following options:
-s Specifies the host name of the Enterprise Controller with which to register the Proxy
Controller. In this case, the host name is that of the current system.
-u Specifies the user that you designated as the administrator of the Enterprise Controller.
-p Specifies the absolute path name of the file that contains the password for the user that you
specified with the -u option.
For more information about the proxyadm command, see the proxyadm man page.
5. Use the proxyadm command to start the Ops Center Proxy Controller services.
Solaris OS: Use the /opt/SUNWxvmoc/bin/proxyadm command.
RHEL OS: Use the /opt/sun/xvmoc/bin/proxyadm command.
For example:
# /opt/SUNWxvmoc/bin/proxyadm start -w
proxyadm: Starting proxy with SMF...
proxyadm: Proxy services have started
#
2. Create an empty file named /var/tmp/xVM/mypasswd, and set its permission mode to 400.
# touch /var/tmp/xVM/mypasswd
# chmod 400 /var/tmp/xVM/mypasswd
3. Edit the /var/tmp/xVM/mypasswd file so that it contains the password for the administrative user that exists on the
Enterprise Controller.
The following echo command appends the password to the /var/tmp/xVM/mypasswd file. Replace password with the
correct password. For example:
4. Use the agentadm configure command to associate the Ops Center agent with the co-located Ops Center Proxy
Controller.
Solaris OS: Use the /opt/SUNWxvmoc/bin/agentadm command.
RHEL OS: Use the /opt/sun/xvmoc/bin/agentadm command.
The example command below uses the following options:
1180654722
3
CN=amritsar_scn-proxy_ca
CN=amritsar_scn-proxy_agent
Thu Jun 19 15:45:21 MDT 1969
Thu Apr 19 15:45:21 MDT 2029
Certificate:
Serial Number:
Version:
Issuer:
Subject:
Not valid before:
Not valid after:
200039089
3
CN=amritsar_scn-proxy_ca
CN=amritsar_scn-proxy_ca
Thu Jun 19 15:45:18 MDT 1969
Thu Apr 19 15:45:18 MDT 2029
These services should not be disabled outside of Ops Center. To manage these services, use the satadm, proxyadm, and
agentadm commands.
Purpose
svc:/application/management/common-agent-container-1:scn-proxy
The management
container for the
java code
containing the
business logic for
the Proxy
Controller.
svc:/application/management/common-agent-container-1:default
The management
container for the
java code
containing the
business logic for
the Enterprise
Controller.
svc:/application/scn/reportdb:default
Manages the
data store for
Ops Center
charts and
graphs.
svc:/application/scn/db:default
Manages the
postgres
database for Ops
Center.
svc:/application/scn/console:default
svc:/application/scn/ajaxterm:default
Manages
software for the
remote serial
console feature.
svc:/application/scn/uce-scheduler:default
Handles the
launching of jobs
according to a
defined schedule.
svc:/application/scn/uce-server:default
Provides the
information that
the Agent needs
to execute a job.
DHCPD
svc:/application/scn/dhcpd:default
Provides DHCP
services for OS
Provisioning.
Viewing Logs
You can view logs to diagnose problems or examine Ops Center activities.
Note The update channel download log and the update channel error log will not be displayed. Select either of these logs to
display its location.
To View Logs
1. Click the Enterprise Controller in the Administration section of the Navigation Panel.
2. Click the Logs tab.
3. Select a log from the dropdown list.
Cacao log
UI log
DB transaction log
DB report log
Proxy log
Update error log
Update channel download log
Update channel error log
3. Use the proxyadm command and the unconfigure subcommand to unconfigure the Proxy Controller. The example
below uses the following option:
-s Unregisters the Proxy Controller from the Enterprise Controller.
/opt/SUNWxvmoc/bin/proxyadm unconfigure -s
DHCP Configuration
You can configure and enable DHCP services on a Proxy Controller. DHCP configuration configures and enables basic DHCP
services on the Proxy Controller to support OS provisioning operations in Ops Center. The Proxy Controller must be in the same
subnet as the target hosts for OS provisioning to work.
The DHCP Config action configures and enables either a Solaris DHCP server, or an Internet Standards Consortium (ISC) DHCP
server, on the Proxy Controller that you select.
The DHCP Config action requires that you specify the Ethernet interface through which the Proxy Controller will provide DHCP
services, for example bge0. Currently you may establish DHCP services on all the Ethernet interfaces in the proxy controller. The
Proxy Controller's Ethernet interface that you specify must be connected to the network where the target systems for OS
provisioning are connected.
Similarly, the Ethernet interface that you select in the Boot Network Device field of the Provision OS wizard must be connected to
the network where the Proxy Controller is providing DHCP services. See OS Provisioning for a Single System and OS Provisioning
for Multiple Systems for more information about the Provision OS wizard.
The DHCP Config and External DHCP Servers actions are mutually exclusive. Use only one of these two actions to configure DHCP
services to support OS provisioning operations. The DHCP Config action is more commonly used, and is simpler to implement.
The following diagram illustrates the basic DHCP configuration.
The Provision OS wizard supplies the specific identity information that the target system requests, using the basic DHCP services
that you establish on the Proxy Controller.
e1000g0
e1000g1
e1000g2
10.0.0.2
192.168.1.2
172.16.12.2
If you configure the DHCP server to listen to e1000g1 and e1000g2, then the target system must have the IP address in the range
of 192.168.1.0/24 or 172.16.12.0/24.
Subnets
You can configure subnets to use the DHCP server on a Proxy Controller for purposes in addition to OS provisioning, or to define
subnets that are used with external DHCP servers.
Configuring subnets is not required to establish the basic DHCP services that are required for OS provisioning, unless you are
using an external DHCP server.
Typically you would configure subnets for the following reasons:
To configure a subnet to provide IP address, DNS server, and router information to systems that may request them on
the same network where the Proxy Controller is providing basic DHCP services for OS provisioning;
If you choose to configure an external DHCP server instead of configuring a DHCP server on a Proxy Controller, you must
configure a subnet for each network from which you might receive relayed DHCP requests.
To Configure a Subnet
1. In the Administration panel, select the Proxy Controller where you want to configure a DHCP subnet. The Actions list
shows the available actions, including the Subnets action.
2. Select Subnets in the Actions panel.
The DHCP Subnets Configuration dialog box is displayed.
3. In the DHCP Subnets Configuration dialog box, provide the following information:
Subnet To create a new subnet on the selected Proxy Controller, select Create New Subnet. Select an existing
subnet from the pull-down list to modify its configuration. The Refresh button updates the list of subnets.
Subnet Name Enter the name of the subnet where you want to establish or modify DHCP services.
Network Enter the network address.
Netmask Enter the netmask for the network.
Router IP Adress Enter the IP address of the router that systems that on this subnet will use.
Low IP Address Enter the IP address to use as the lower limit of the IP address range that systems on this
subnet will use.
High IP Address Enter the IP address to use as the upper limit of the IP address range that systems on this
subnet will use.
Name Server Enter the IP addresses of the DNS servers that systems will use.
Domain Enter the names of the DNS domains that systems will use to resolve host names.
4. Click Create Subnet to create the subnet configuration that you specified. A message indicates that a job to create the
subnet was submitted. Click OK to dismiss the message.
The DHCP Config and External DHCP Servers actions are mutually exclusive. Use only one of these two actions to configure DHCP
services to support OS provisioning operations. The DHCP Config action is more commonly used, and is simpler to implement.
The following diagram illustrates DHCP configuration using External DHCP servers.
You run the scinstall_ext_dhcp.pl script on the External DHCP server to establish communication between the Proxy
Controller and the External DHCP server. The Subnets panel allows you to define subnets where DHCP relay traffic is expected.
The External DHCP Servers panel configures the Proxy Controller to relay DHCP configuration information that the Provision OS
wizard supplies. The Provision OS wizard supplies the specific identity information that the target system requests. The target
system makes its DHCP requests, which are relayed to the External DHCP server. The routers or other network asset that connects
the External DHCP server to the Proxy Controller must have DHCP relay capabilities enabled.
# wget http://proxy_ip:8004/pub/scninstall_ext_dhcp.pl
# chmod +x scninstall_ext_dhcp.pl
# ./scninstall_ext_dhcp.pl install
2.
Oracle Enterprise Manager Ops Center
./proxyadm stop
3. Use the satadm command with the backup subcommand to back up the Enterprise Controller. The satadm command
resides in the /opt/SUNWxvmoc/bin directory on a Solaris system, and in the /opt/sun/xvmoc/bin on a Linux
system. The example below uses the following flag:
-o Indicate the directory location of the backup file.
4. Use the proxyadm command to restart the co-located Proxy Controller. For example:
./proxyadm start
# cd /var/tmp/xVMSunOS_sparc/Product/installer
# ./install -e
3. Change to the directory where the satadm file is located on your system.
a. On Solaris systems, go to the /opt/SUNWxvmoc/bin/ directory.
b. On Linux systems, go to the /opt/sun/xvmoc/bin/ directory.
4. Enter the satadm command with the restore subcommand. The -i flag is required to restore the data from the
backup file. To use additional options, see the satadm man page.
5. For an Enterprise Controller with a co-located Proxy Controller, restart the co-located Proxy Controller using the
proxyadm command. The proxyadm command is in the same directory as the satadm command.
./proxyadm start -w
6. For an Enterprise Controller with a co-located Proxy Controller, use the Custom Discovery method to rediscover the
system after running the restore command. You do not need to re-register the assets.
Note After restoring the Enterprise Controller, the asset details might take several minutes to display completely in the
user interface.
Adding a User
Users with admin privileges can add other users to the list of users recognized by Ops Center. New user information, such as the
passwords for new users, will be pulled from the local authentication subsystem.
To Add a User
1. Select Administration in the Navigation panel.
2. Click the Users tab.
The Users page is displayed.
3. Click the Add User icon.
3.
The Add User window is displayed.
4. Enter the user name.
5. Click Add User.
The new user is created.
Deleting a User
A user with admin rights can delete other users, removing the user and their role from Ops Center.
To Delete a User
1. Select Administration in the Navigation panel.
2. Click the Users tab.
The Users page is displayed.
3. Select the user that you want to delete.
4. Click the Delete User icon.
The Delete User window is displayed.
5. Click Confirm.
The user is deleted.
Group Roles
An Enterprise Controller Admin can grant one or more of these roles to any user for any user-defined group:
Content
Description
Group Admin
This role allows the user to use administration actions such as adding or removing assets.
Group Provision
This role allows the user to provision new operating systems and firmware.
Group Update
Group Manage
This role allows the user to use management and monitoring actions.
Group Admin
An Enterprise Controller Admin can grant this role to any user for any user-defined group. This role allows the user to use
administration actions such as editing a group.
Task
Group Admin
Administration
Edit Authentications
No
No
Yes
No
No
Yes
Library Actions
No
No
Yes
Groups
Create Subgroups
No
Yes
Yes
No
Yes
Yes
Move Group
Yes
Yes
Yes
Edit Group
Yes
Yes
Yes
Delete Group
Yes
Yes
Yes
Management
Remove Asset
No
Yes
Yes
Reboot System
Yes
Yes
Yes
Access Console
Yes
Yes
Yes
Monitoring
Yes
Yes
Yes
Generate Reports
Yes
Yes
Yes
Discovery
Discover Assets
No
Yes
Yes
No
Yes
Yes
No
Yes
Yes
Group Manage
An Enterprise Controller Admin can grant this role to any user for any user-defined group. This role allows the user to use
management and monitoring actions.
Task
Manage
Administration
Edit Authentications
No
No
Yes
No
No
Yes
Library Actions
No
No
Yes
Management
Remove Assets
No
Yes
Yes
Reboot System
No
Yes
Yes
Access Console
Yes
Yes
Yes
Monitoring
Yes
Yes
Yes
Yes
Yes
Yes
Generate Reports
No
Yes
Yes
Group Provision
An Enterprise Controller Admin can grant this role to any user for any user-defined group. This role allows the user to provision
new operating systems and firmware.
Task
Provision
All Assets
Admin
Enterprise Controller
Admin
Administration
Edit Authentications
No
No
Yes
No
No
Yes
Library Actions
No
No
Yes
Create Profile/Policy
No
Yes
Yes
Yes
Yes
Edit Profile/Policy
Yes
Yes
Delete Profile/Policy
Yes
Yes
View Profile/Policy
Yes
Yes
Yes
Yes
Yes
Yes
Provisioning
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Answer questions
Yes
Yes
Yes
Rerun job
Yes
Yes
Yes
Yes
Yes
Yes
Group Update
An Enterprise Controller Admin can grant this role to any user for any user-defined group. This role allows the user to install
operating system patches and product updates.
Task
Update
All Assets
Admin
Enterprise Controller
Admin
Administration
Edit Authentications
No
No
Yes
No
No
Yes
No
No
Yes
Profile/Policy Management
Create Profile/Policy
No
Yes
Yes
Yes
Yes
Edit Profile/Policy
Yes
Yes
Delete Profile/Policy
Yes
Yes
View Profile/Policy
Yes
Yes
Yes
Yes
Yes
Yes
Job Submission
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Answer questions
Yes
Yes
Yes
Rerun job
Yes
Yes
Yes
Yes
Yes
Yes
Reports
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Note If you want to update multiple operating systems with a single job, you must use a homogeneous OS group as the target.
See Using Groups for information about how to create a group and add operating systems to the group.
To update a Linux OS, you must provide your Red Hat or SUSE login credentials. Ops Center uses the credentials to log in to the
third-party site and download the patches or packages. To provide or update your SunSolve or third-party vendor credentials, see
Authentications.
An Enterprise Controller Admin can grant this role to any user for any user-defined group. This role allows the user to run
simulated update jobs.
Task
Update Simulate
All Assets
Admin
Enterprise Controller
Admin
Administration
Edit Authentications
No
No
Yes
No
No
Yes
No
No
Yes
Profile/Policy Management
Create Profile/Policy
No
Yes
Yes
Yes
Yes
Edit Profile/Policy
Yes
Yes
Delete Profile/Policy
Yes
Yes
View Profile/Policy
Yes
Yes
Yes
Yes
Yes
Yes
Job Submission
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
Yes
Answer questions
Yes
Yes
Yes
Rerun job
Yes
Yes
Yes
Yes
Yes
Yes
Reports
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Note If you want to update multiple operating systems with a single job, you must use a homogeneous OS group as the target.
See Using Groups for information about how to create a group and add operating systems to the group.
To update a Linux OS, you must provide your Red Hat or SUSE login credentials. Ops Center uses the credentials to log in to the
third-party site and download the patches or packages. To provide or update your SunSolve or third-party vendor credentials, see
Authentications.
Assigning a Role
Roles grant users the ability to use the different functions of Ops Center. By giving a role to a user, an administrator can control
what functions are available to that user for specific groups. See Roles and Authorizations for a list of the available roles and their
functions.
An Enterprise Controller Admin can grant users different roles for the Enterprise Controller, the All Assets group, and any
user-defined groups. A user who is assigned a role for a group will receive the same role for all subgroups.
7.
8.
9.
10.
a. For each Virtualization Pool, select the severity of messages to be received through the BUI, email, and
pager.
b. For each Smart Group, select the severity of messages to be received through the BUI, email, and
pager.
c. For each Group, select the severity of messages to be received through the BUI, email, and pager.
If you chose to receive notifications by email, enter an email address and mail host.
The mail host specifies an external mail host through which messages are sent.
If you chose to receive notifications by pager, enter a pager address and mail host.
The mail host specifies an external mail host through which messages are sent.
(Optional) Click More Options to view additional options.
Enter a Mail User and Mail Password to specify credentials for the mail host.
Click Update Notification Profile.
Job Management
All major tasks within Ops Center, such as asset discovery or OS provisioning, create jobs.
From the Jobs tab, you can monitor and control current and historical jobs. You can see the status of all jobs and choose to view
detailed information about a specific job. You manage jobs by stopping, re-running, or deleting them.
Job Details
You can view detailed information about a job. This information includes:
Job ID
Run ID
If a job has been run multiple times, each run of the job will have a separate run ID.
Job Type
Start Date
Elapsed Time
Status
Creation Date
Description
Mode (Simulation or Actual Run)
Owner
Task Execution Order
Failure policy
Recurring job status and Next Scheduled Time
List of tasks
Task execution order
Task progress/results
Event logs
Event logs are generated by tasks as they progress.
Stopping a Job
You can stop a job that is currently running. The job will end; running tasks will be interrupted and tasks that have not yet started
will be aborted.
The completion status of the job will depend on the number tasks that have completed, been interrupted, and not started.
To Stop a Job
Note Only running jobs can be stopped.
1. Select Jobs in the Navigation panel.
2. Select the job ID that you want to stop.
3. Click the Stop Selected Jobs button.
A confirmation window is displayed.
4. Click Stop Job.
The job is now stopped.
Deleting a Job
Deleting a job removes it from the queue entirely. It cannot be re-run or resumed, and its job details will no longer be visible.
To Delete a Job
Note You cannot delete jobs that are running. See Stopping a Job for information about stopping a running job.
1. Select Jobs in the Navigation panel.
2. Select the job ID or IDs that you want to delete.
3. Click the Delete Selected Jobs button.
A confirmation window is displayed.
4. Click Delete Job.
The job is now deleted.
Re-running a Job
If a job is completed, you can re-run the job, repeating the job with a new Run ID.
To Re-Run a Job
You can re-run jobs on failed targets from the Job Details window.
1. Select Jobs in the Navigation panel.
2. Select the job ID or IDs that you want to re-run.
3. Click the Re-run Selected Job button.
A confirmation window is displayed.
4. Click Run Job.
The job runs again with a new Run ID.
Copying a Job
You can copy a job, using an old job as a template for a new job.
To Copy a Job
1. Select Jobs in the Navigation panel.
2. Select the job that you want to copy.
3. Click Copy Job.
The New Job wizard is displayed.
4. (Optional) Modify the job information for its new task.
5.
5. Click Next.
6. Select a schedule for the job and click Next.
7. Review the job information and click Submit Job.
The new job is submitted with a new Job ID.
Answering Questions
Some jobs might require your input.
To Answer Questions
1. Select Jobs at the bottom of the browser window to display the Jobs panel.
2. Select the job that requires input.
3. Click Answer Questions.
The Answer Pending Questions window is displayed. There may be multiple pages of questions.
4. (Optional) Click the page icon next to a component to display the component details.
5. Answer the pending questions. The following options are available:
Select Yes or No for each question using the buttons in the right column.
Click Yes to All to set the response for every question to yes.
Click No to All to set the response for every question to no.
Click Reset to set the response for every question back to the default value.
6. Click Submit.
The job will be resubmitted using the same Job ID and Run ID.
Messages
The Messages box at the top of the UI provides information about a number of global conditions in Ops Center.
The following information appears in the Messages box:
The number of unread notifications
The number of users logged in
The number of active systems
The number of Virtualization Hosts being managed
The power consumption of managed servers
To View Messages
1. Click the arrow buttons to the left and right of the alert window.
Messages will also cycle automatically.
Viewing Notifications
Ops Center generates notifications for all event operations and when the set thresholds are exceeded.
You can enable or disable the notifications for a server or blade, chassis, or OS. The status of notifications for the asset is
displayed in the asset's monitoring window.
To View Notifications
1. Open the notifications window.
Click the notifications icon in the center panel.
The messages box will also periodically show the number of unread notifications. Click this bulletin.
The notifications window is displayed.
2. (Optional) Use the search function in the upper right section of the window to search for specific notifications.
3. (Optional) Use the filter function in the upper right section of the window to filter the notifications. The following filters
are available:
Info: Shows only notifications that provide information.
Action Required: Shows only notifications of events that require action.
Show Only Unread: Shows only unread notifications.
Deleting Notifications
You can delete any notification. You can also delete all notifications.
To Enable Notifications
1. Select Assets in the Navigation panel.
2. Select the specific asset for which you want to enable notifications.
3. Choose Enable Notifications from the Actions menu.
A job is submitted to enable notifications for the asset.
To Disable Notifications
1. Select Assets in the Navigation panel.
2. Select the specific asset for which you want to disable notifications.
3. Choose Disable Notifications from the Actions menu.
A job is submitted to disable notifications for the asset.
2. From the All Managed Assets list, select the managed OS instance that is currently installed on the system from which
you want to remove the agent software.
Selecting the managed OS allows you to uninstall the Ops Center agent that is currently installed.
3. Click the Unmanage/Delete Assets icon.
The Introduction panel of the Unmanage and Delete Assets wizard is displayed.
4. Click Next.
The Enter Server Credential panel is displayed.
5. For this example, select Use the Same SSH Credentials for All Assets Listed Below.
6. Enter the access credentials using the following fields:
SSH Username Enter either the root user, or the name of the non-root administrative user to
use for ssh access.
SSH Password Enter the password for the user you specified in the SSH Username field.
Root Username If you specified the root user in the SSH Username field, leave this field blank.
If you specified a non-root administrative user in the SSH Username field, enter the root user
name.
Root Password Enter the password for the user you specified in the Root Username field.
7. Click Next.
The Unmanage/Delete panel is displayed.
8. In the Unmanage/Delete panel, verify that the correct system to unmanage is listed.
9. Click Next.
The Summary panel is displayed.
10. Click Close to close the Unmanage and Delete Assets wizard.
# /opt/SUNWxvmoc/bin/proxyadm
stop
2. Use the install -e command to uninstall the Proxy Controller software components from your system.
Within the parent installation directory, the install command exists in the following subdirectories:
Solaris OS, SPARC: SunOS_sparc/Product/installer
Solaris OS, x86: SunOS_i386/Product/installer
RHEL OS: Linux_i686/Product/installer
The example parent installation directory used throughout the installation procedures is /var/tmp/xVM. For
example:
# cd /var/tmp/xVM/SunOS_sparc/Product/installer
# ./install -e
Invoking uninstall
The install script displays a list of uninstallation tasks that automatically updates as the uninstallation
proceeds. For example:
[Not
[Not
[Not
[Not
[Not
[Not
[Not
[Not
[Not
When complete, the install script indicates that the Ops Center Proxy Controller has been uninstalled.
# /opt/SUNWxvmoc/bin/satadm stop
satadm: Shutting down satellite using SMF...
#
2. Use the install -e command to uninstall the Enterprise Controller software components from your system.
Within the parent installation directory, the install command exists in the following subdirectories:
Solaris OS, SPARC: SunOS_sparc/Product/installer
Solaris OS, x86: SunOS_i386/Product/installer
RHEL OS: Linux_i686/Product/installer
The example parent installation directory used throughout the installation procedures is /var/tmp/xVM. For
example:
# cd /var/tmp/xVM/SunOS_sparc/Product/installer
# ./install -e
Invoking uninstall
The install script displays a list of uninstallation tasks that automatically updates as the uninstallation
[Not
[Not
[Not
[Not
[Not
[Not
[Not
[Not
[Not
[Not
[Not
[Not
[Not
[Not
[Not
When complete, the install script indicates that the Ops Center Enterprise Controller has been uninstalled.
you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe,
backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any
damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective
owners.
AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license
and are trademarks or registered trademarks of SPARC International, Inc. UNIX is a registered trademark licensed through X/Open
Company, Ltd.
This software or hardware and documentation may provide access to or information on content, products, and services from third
parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect
to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or
damages incurred due to your access to or use of third-party content, products, or services.