| Oracle® Enterprise Manager Ops Center Feature Reference Guide 12c Release 1 (12.1.1.0.0) Part Number E27511-04 |
|
|
PDF · Mobi · ePub |
| Oracle® Enterprise Manager Ops Center Feature Reference Guide 12c Release 1 (12.1.1.0.0) Part Number E27511-04 |
|
|
PDF · Mobi · ePub |
This chapter provides and overview of the operating system (OS) management features that are available in Oracle Enterprise Manager Ops Center.
The following information is included:
See Chapter 13, "Operating System Updates" for information about patching and updating your operating systems.
Oracle Enterprise Manager Ops Center provides comprehensive lifecycle management for Oracle Solaris, Oracle Linux, SUSE Linux, Red Hat Linux, and Microsoft Windows operating systems in your datacenter.
The discovery feature makes adding operating systems and other assets quick and easy. After the operating systems are added, they are considered managed and you can begin using the monitoring, analytics, OS provisioning, and update features to gather information and perform tasks.
Your managed operating systems are visible in the All Assets section of the user interface. The operating system appears under the service processor and hardware, as shown in Figure 12-1.
Figure 12-1 Managed System and Operating System
The OS is also added to the appropriate platform-specific group in the Operating Systems view, as shown in Figure 12-2.
You can create user-defined groups and subgroups to refine your administration tasks. For example, you might want to create groups for Critical Systems, Training, Region 1 and Region 2. This is useful when you want to organize the systems to apply different monitoring standards, implement update requirements, or job scheduling times. You can create rules for your groups to automatically add existing and newly managed operating systems to the correct group or subgroup. See Chapter 2, "Asset Management" for details on using the discovery feature to add assets and for more information on creating user-defined groups.
The monitoring feature provides extensive monitoring capabilities that are enabled as soon as you begin managing an operating system. A series of three escalating status levels notifies you when something is not operating as expected. The first level is informational, then warning, and finally a critical status. A set of default monitoring attributes and alert triggers are included with the software. You can tune the monitoring thresholds and triggers to define what you want to generate an alert and when. You can create custom monitoring rule sets and alert parameters and apply the customized monitoring rules to a specific operating system, a group of homogeneous operating systems, or a group that you define, such as critical systems or regional systems.
The Analytics feature provides extensive information about a specific operating system in one location so that you can maximize performance and utilization. The Analytics information includes process details, defined monitoring thresholds for operating systems, metrics and historical information on the top consumers, and a extensive list of metrics data. The Summary contains details on the top five consumers for CPU, memory, network, and I/O utilization. Use the graphical representation to quickly view utilization trends and high resource consumers. You can drill down to get detailed utilization and process information, and kill a process that is consuming too many resources.
The following features are available for operating systems:
Monitoring – A series of monitoring rules and parameters monitor your managed assets. Alerts and incidents are raised for components that are not performing as expected.
Performance – Analytics provides you with a detailed view into OS performance.
System resource graphs, processes information, and a view of the top consumers
Resource usage of virtualized OS instances
Provisioning – Install Oracle Solaris or Linux operating systems onto your systems, making it easy to install one system or many servers simultaneously.
Manage Oracle Solaris Boot Environments – Create and manage Oracle Solaris boot environments in a repeatable and consistent manner from a single user console.
OS Updates – Apply update packages to keep your operating systems up-to-date. See Chapter 13, "Operating System Updates" for information.
Reports and Snapshots – A variety of reports are available for your operating systems. See Chapter 10, "Reports" for OS reports. See Chapter 13, "Operating System Updates" for information on how to use the System Catalogs to maintain snapshots of your operating system.
Two types of OS management are available: agent managed and agentlessly managed. In some cases, the features and actions that you can perform on an operating system are determined by how the OS is managed.
Table 12-1 lists the tasks that are discussed in this section and the role required to complete the task. An administrator with the appropriate role can restrict privileges to specific targets or groups of targets. Contact your administrator if you do not have the necessary role or privilege to complete a task. See the Oracle Enterprise Manager Ops Center Administration Guide for information about the different roles and the permissions they grant.
Table 12-1 OS Management Roles and Permissions
| Task | Role |
|---|---|
|
Reboot an OS |
Asset Admin |
|
Charts and Utilization |
Asset Admin Cloud Admin |
|
Analytics |
Read Asset Admin |
|
Kill action in Analytics |
Operating System Management |
|
Update Management Credentials |
Security Admin |
|
Any Actions related to changing credentials |
Security Admin |
|
Import image |
Storage Admin |
|
Upload image |
Storage Admin |
|
Unconfigure, SCCM Configuration |
Oracle Enterprise Manager Ops Center Admin |
|
Reboot, upgrade Agent Controller |
Asset Admin |
|
Edit Tags |
Asset Admin |
|
Edit Attributes |
Asset Admin |
|
View Boot Environment |
Read Asset Admin Update Admin |
|
Create Boot Environment |
Asset Admin Update Admin |
|
Update an Alternate Boot Environment |
Update Admin |
|
Activate and Reboot a Boot Environment |
Asset Admin Update Admin |
|
Synchronize Boot Environments |
Asset Admin Update Admin |
|
Delete an Alternate Boot Environment |
Asset Admin Update Admin |
|
Monitor Boot Environment Attributes |
Asset Admin |
You can manage an operating system in one of two modes: agent managed or agentless managed. The management mode determines the features that are enabled for your operating system.
The more robust management mode is agent managed because the Agent enables a greater level of communication with the Proxy Controller and Enterprise Controller than the agentless managed operating systems. You can use the features and perform the actions described in this chapter with an agentless managed operating system, but OS update functionality requires an agent managed operating system. You can manage your operating systems by installing an Agent Controller on the OS or by using SSH to perform tasks. See Agent-Managed and Agentlessly-Managed Operating Systems for more details.
See Chapter 2, "Asset Management" for details on using the discovery feature to add assets and for more information on creating user-defined groups.
After you manage your assets, you can perform the following actions:
Monitor your physical and virtual operating systems
View OS utilization for Oracle Solaris and Linux operating systems
Provision Oracle Solaris and Linux operating systems
Manage Oracle Solaris boot environments
When you manage a physical or virtual operating system, it appears under the associated server in the All Assets view, as shown in Figure 12-3 and it appears in a special pre-defined operating system group, as shown in Figure 12-4.
Operating systems are automatically added to a homogenous group of operating systems. The group contains directories for each release. In Figure 12-4, the list of Oracle Solaris 10 operating systems includes physical operating systems, virtual hosts, and zones. You can add user-defined groups and create rules to automatically add newly discovered assets to that group, or you can manually add them at any time. See Using Groups for details.
To view information about a specific OS, select the OS from the Assets pane. OS details appear in the tabs across the center pane.
Table 12-2 Location of Operating System Information in the UI
| To Display: | Select: |
|---|---|
|
Managed operating systems |
Expand the Assets pane. Each operating system appears in the Assets tree under the system on which it is installed. To only view operating systems, click the drop-down next to All Assets and select Operating Systems. The systems are grouped by platform. |
|
Operating system details for a specific operating system |
Select an operating system in the Assets pane, then click the Summary tab. |
|
Operating system details for a group of operating systems |
Select an operating system in the Assets pane, then click the drop-down next to All Assets and select Operating Systems. Select a group, then click the Summary tab. |
|
Unresolved incidents and alerts for a specific operating system |
Select an operating system in the Assets pane, then click the Incidents tab. The details are in the Unresolved Incidents and Alert subtabs. |
|
Unresolved incidents and alerts for a group of operating systems |
Expand the Assets pane, then click the drop-down next to All Assets and select Operating Systems.Select a group, then click the Incidents tab. The details are in the Unresolved Incidents and Alert subtabs. |
|
Monitoring Rules for a specific operating system |
Select an operating system in the Assets pane, then click the Monitoring tab. |
|
Monitoring Rules for a group of operating systems |
Select an operating system in the Assets pane, then click the drop-down next to All Assets and select Operating Systems. Select a group, then click the Monitoring tab. |
|
Analytics |
Select an operating system in the Assets pane, then click the Analytics tab. |
|
OS Provisioning |
Select a Provision OS plan in Plan Management. |
|
Boot environments |
Select an operating system in the Assets pane, then click the Boot Environments tab. |
The following categories of OS Management profiles are available:
OS Provisioning
Monitoring Profile
Oracle Solaris Zone
Boot Environments
Two management modes are available, agent-managed and agentlessly-managed. An agent managed operating system has an Agent Controller installed to gather information for the Enterprise Controller and is required for some OS-specific features. When you do not want an Agent Controller installed, you can agentlessly manage your operating systems. To gather information on an agentlessly managed operating system, the Proxy Controller uses SSH to perform certain tasks and periodically check on the operating system.
The current management mode of an operating system appears on the Dashboard for the operating system, as shown in Figure 12-5 and Figure 12-6.
When you install the Agent Controller on the operating system, the following actions occur:
The Agent Controller is registered with the Enterprise Controller. It takes at least five (5) minutes for the software to register the Agent Controller. After registered, you can update the operating system.
The software sends you a notification when it has enabled the update function for the operating system.
The Agent Controller checks the inventory of patches and packages and creates the System Catalog. The catalog lists the patches and packages, and the versions that are currently installed on the operating system.
Some features are not available when the operating system is managed agentlessly. Table 12-3 shows the information that are available for each management type.
Table 12-3 Information Available for Agent Managed and Agentlessly Managed Assets
| Tab or Feature | Agent Managed | Agentlessly Managed |
|---|---|---|
|
Dashboard |
Yes |
Yes |
|
Summary |
Yes |
Yes |
|
Libraries |
Yes |
No |
|
Storage |
Yes |
No |
|
Utilization |
Yes |
Yes |
|
Analytics |
Yes |
Limited |
|
Virtualization Analytics for Oracle VM Server |
Yes, if the guest is agent-managed |
No |
|
Virtualization Analytics for Oracle Solaris 10 Zones |
Yes, if the global zone is agent-managed or if the non-global zone is agent-managed. |
No |
|
Networks |
Yes |
No |
|
Incidents |
Yes |
Yes |
|
Monitoring |
Yes |
Yes |
|
Charts |
Yes |
Yes |
|
Reports |
Yes |
No |
|
System Catalogs |
Yes |
Oracle Solaris 11 – Yes Oracle Solaris 8-10, Linux, Windows – No |
|
Terminal |
Yes |
No |
|
Jobs |
Yes |
Yes |
|
Configuration |
Yes |
Yes |
|
OS update |
Yes |
Oracle Solaris 11, Windows – Yes Oracle Solaris 8-10, Linux – No |
|
OS provisioning |
Yes |
No |
|
Zone management, including create, read, update, and delete zones |
Yes |
No |
You can change the agent management mode:
Unmanage the agent, then rediscover the operating system using a profile with the alternative mode.
Use the Switch Management Access feature.
The Switch Management feature enables you to move back and forth from agentlessly managed to agent managed. When the operating system is agent managed and you use this action, the agent is removed and the operating system is managed agentlessly. Select or create new credentials for the Proxy Controller to use to obtain information from the asset.
To Use Switch Management Access
Select the operating system from the Assets drawer. You can view the current management status in the Dashboard tab.
Click Switch Management Access in the Actions pane.
Add or select the credentials for the system, then click Finish.
To create a new set of credentials, click New and complete the Create Credentials wizard, then click OK.
To select from a list of existing credentials, click Select, highlight the credentials from the list of available credentials, then click OK.
Figure 12-8 Switch Management Access Credentials
The software monitors the status of your operating systems as soon as the asset is managed, using the default rules and thresholds Monitoring rules state the values and boundaries for an asset's activity. A monitoring policy is a set of rules. You can change the rules or thresholds to adjust the type and level of monitoring you want. Analytics provides details on operating system activity and utilization.
A monitoring policy defines alert configurations to be performed on one or more managed resources. A policy is for a specific type of resource, such as operating systems. A more specific policy might apply to all Oracle Solaris operating systems. Each monitoring policy contains several alert monitors for a specific type of resource. Alert monitors watch the state of managed resources and their attributes and raise an alert when the state is outside the pre-defined thresholds.
Applying a monitoring policy to all the assets enforces consistency. Each monitoring policy contain rules for threshold levels. Default policies for monitoring hardware, operating systems, and Oracle Solaris Clusters are included in the software. You can use the default policies, but you cannot edit them. To edit or add monitoring rules to a monitoring policy, you must make a copy. Modifying a monitoring rule for a specific asset creates a custom set of monitoring rules for the asset.
See Chapter 4, "Monitoring Rules and Policies" for information about how to change the threshold limits and how to change the deactivate or activate the auto delete policy. See Chapter 9, "Incidents" for details about how incidents are generated, severity badges, how to assign and close an incident.
The Analytics feature provides a view into operating system performance and status. The charts, reports, and utilization data provide details of an individual eligible OS. You can use the information to analyze the behavior of an OS to aid in peak performance and to diagnose and correct incidents.
The OS Analytics view provides information for the following agent-managed platforms:
Linux
Oracle Solaris 11 and 10 OS
Oracle Solaris 10 non-global zone, when the global zone or non-global zone is agent-managed
Oracle Solaris 11 non-global zone, when the global zone is agent-managed
When your operating system is agentlessly-managed, information is not available for zones and less information is available for Linux and Oracle Solaris 10 and 11 operating systems. Table 12-4 shows a list of features and whether the feature is supported on an agent managed or agentlessly managed asset.
Table 12-4 Supported Analytics Information
| Feature | Supported on Agent Managed OS | Supported on an Agentlessly Managed OS |
|---|---|---|
|
Yes |
Yes |
|
|
Virtualization Analytics for Oracle VM Server |
Yes, if the guest is agent-managed |
No |
|
Virtualization Analytics for Oracle Solaris 10 Zones |
Yes, if the global zone is agent-managed or if the non-global zone is agent-managed. |
No |
|
Services |
Yes |
Yes |
|
Processes |
Yes, if the guest, global zone, or non-global zone is agent-managed |
No |
|
Threshold |
Yes |
Yes |
|
History |
Yes, if the guest, global zone, or non-global zone is agent-managed |
No |
|
Metrics |
Yes |
Yes |
The current management mode appears in the Dashboard Summary page for the operating system. See Agent-Managed and Agentlessly-Managed Operating Systems for details and for the steps to switch the management mode.
For each operating system, the information appears in the Analytics tab in the center pane. The information appears in several views.
Note:
Monitoring uses the Agent Controller to gather information. When an operating system is an agentless managed system or Microsoft Windows, the software uses an SSH connection from a Proxy Controller to perform remote monitoring. Remote monitoring over an SSH connection limits the available metric information. The Summary view, Process view, Historical view and Virtualization Analytics are not available for these operating systems.The following sections discuss the diagnostic pages for an agent-managed operating system:
Analytics view
System resource graphs
Top-consumers views
Processes information
View historical data and set thresholds
Virtualization Analytics view
Virtualized OS instance
Breakdown of resource usage of the physical server
Running OS instance
View historical data and set thresholds
The Analytics view contains current and historical information about an operating system's use of resources, including CPU, Network, disk I/O, memory, alert history, and total thread and process counts. Information presented in this section assumes that the operating system is agent managed. See Table 12-4 for the list of supported features for an agentlessly managed OS.
The information appears in a series of charts in the following subtabs:
Summary – View a high-level overview of the top consumers, by process, for the CPU, memory, network, and disk I/O resources
Processes – View process-specific details
Services – View and monitor Oracle Solaris 10 and 11 SMF services
Thresholds – View and edit the threshold limits for a selected monitored attribute
History – View a history for the top consumers
Metrics – View specific details an operating system element, such as the percentage of memory used
Charts – You can create a variety of utilization charts, define the coordinates, and export the chart data to CSV or XML output
You can view analytics information for all supported and managed operating systems, both physical and virtual. The information presented varies, depending on the data available for the OS. For example, when the System Tap is not installed on a Linux operating system, information about the top network and I/O consumers might not be available. Also, the top consumers for I/O data might not be available with some versions of the Linux kernel.
When an agent-managed operating system is on a virtualization platform, you can view the information in the Analytics view of the virtualization platform. See Virtualization Analytics View for information about analytics for virtualized platforms.
The default display is the resource usage data. You can change the display settings for each view and choose which system resource graphs and details to display. The changes made on a given analytics screen affects the views of all analytics screens for the same OS or virtualized OS.
To change the analytics information displayed on the page, click the Settings Menu icon in the center pane.
The Summary view provides details for an individual operating system. The Summary provides a graphical representation and a list of the top five (5) resource usage consumers, by process, for the CPU, memory, network, and disk I/O resources. The following details appear in the Summary view:
CPU Utilization – A graph of the percentage of CPU Utilization over time and a detailed list of the top five (5) CPU processes. The list includes the process identification number (PID), name, and CPU Usage %. Click the View icon for a row to display process details.
Memory Utilization – A graph of the top 5 memory processes, including the PID, the process name, and the percentage of memory used.
Network Utilization– A graph of the top 5 network processes, including the PID, the process name, and the network usage in Kilobytes (KB) per second.
I/O Utilization– A graph of the top 5 I/O processes, including the PID, the process name, and the I/O usage per second.
The information is refreshed every five (5) seconds. Each list has an icon before the PID column for each process. Click an icon to view details of the process. The type of resource determines the available details.
Process Details – Includes the contract ID, Service FMRI, creator, elapsed time, project name, project ID, and a process tree.
Thread Information – Includes the thread's light-weight process (LWP) ID, the number of threads (NLWP), the user, the priority, the state (such as sleeping), the percentage of CPU used, the CPU time, the percentage of memory used, how much memory the process has marked for allocation (VSZ memory), the processors, and the command.
Handles – Includes the port details, such as the family, local address, local port, the protocol, remote address, remote port, device, and node.
Process Environment – Includes details about the environment, such as the arguments, data model, and flags.
Memory Information – Includes physical, virtual, and anonymous memory and dirty page details. Details include the virtual address and the number of KB in the virtual mapping size, the resident physical memory, the anonymous memory, and the dirty pages. The lock status, permissions, and mapping name details are displayed, when available.
Process Details, Thread Information, Handles (port bindings and file descriptors), Process Environment, and Memory Information.
When the icon that looks like a wrench appears on a page with graphs, you can click the icon to configure the graphs or change the graphs that appear on the page. Figure 12-9 shows an example where you can choose the system resource graphs that display on the Summary page.
You can drill down to display process-specific data, based on current data from the operating system. Some data, such as CPU usage, might also be available in the History view.
The following details are available in the Process view:
Process ID (PID)
Process Name
User
State
CPU Usage %
Memory Usage %
Physical Memory size in MB
Virtual memory size
Target
When you click a process in the Processes table, two icons are enabled in the center pane, one to view more details and the other to kill the process.Figure 12-9 shows an example where you can click check boxes to select or deselect system resource graphs from displaying on the Summary page.
When the software is configured to work with Oracle Enterprise Manager Cloud Control, information about available Oracle Enterprise Manager Cloud Control targets appears in the Process view.
The Services tab provides a view of Oracle Solaris 10 and 11 Service Management Facility (SMF) services. The Oracle Solaris SMF feature defines the relationships between applications, or services, and is a method of managing them by providing a framework for startup scripts, init run levels, and configuration files. Each service is identified by a Fault Managed Resource Identifier (FMRI).
The Services tab contains SMF service instances, state, dependencies, and severity information. You can drill down to see specific service details, including the configuration, dependencies, and the processes that are in the service contract.
You can perform the following actions in the Services tab:
View a list of services currently installed and their states
View a list of dependencies and dependents for FMRI
View the relationship between services and processes
View details about why a service is not available
Obtain logs for debugging
Clear faults for FMRI
Invoke the disable, enable, and restart actions on FMRI
Read configuration files
Services information is available for agent managed and agentlessly managed Oracle Solaris 10 and 11 operating systems, including global and non-global zones.
The Thresholds tab contains information about all monitored attributes for the selected operating system, including per-instance attributes such as File System Usage for each file-system on the asset. Figure 12-10 shows a partial list of the monitored attributes available for display.
Charts for the historical data of those attributes show the alert monitor threshold levels, if configured, for that attribute. Figure 12-11 shows the chart for the System Load Average - 5 minutes. The time frame selected is Live. Under the chart are the severity levels for this monitored attribute (SystemLoad.average15MinutePerCpuCore), the operator, and the threshold values. Instead of editing the thresholds in the Monitoring tab, you change the values on this page. You can either add values in the New Value column or click Suggest Thresholds to populate the fields with suggested values. Click Apply Thresholds to change the existing thresholds.
Note:
When the threshold monitor is modified, the asset is removed from the default monitoring profile and a custom profile created.The History tab contains the history for the top consumers. By default, the current date displays. The time selection box is used to select a time of day for which the top consumer processes are listed. It does not affect the chart, which can only show discrete intervals of 1 hour, 1 day, 5 days, 3 weeks, 6 weeks, and 6 months. The history chart displays the most applicable chart interval for the selected date and time. Figure 12-12 is an example of a Top Consumer History chart. Click the wrench icon to select from a list of options to chart.
The Metrics tab provides you with specific details about various operating system statistics, such as the percentage of memory used, and view graphs. When monitoring thresholds are enabled for an element, you can reset the thresholds. When an element does not have a monitoring threshold, you can configure a new monitoring threshold.
Click the Metrics tab to see OS-specific components. The following list are the categories of component details available for an agent-managed Oracle Solaris OS:
Load
File Systems
Networks
Users
Buffer Activity
Disk Usage
Paging Activity
Message Activity
Tables Status
TTY Activity
Kernel Memory
DNLC
IPC Message Queue
IPC Shared Memory
IPC Semaphore Usage
CPU Detail
File Access
Disk Errors
Memory Utilization
Expand a component to view the available elements. Click an element to view the details. In Figure 12-13, the Load component is expanded and the elements, such as percentage of memory used, CPU utilization percentage, CPU core count, and system update options are available in the Load list. Memory Used % is selected and the details and a graph are visible.
The type of resource determines the available details. Figure 12-14 is an example of the details and graph for the Memory Used % element. This example shows a system in trouble. The Details shows the last known value memory usage at 95.59111 percent and the established monitoring parameters. A warning incident is generated at 80 percent and a critical incident is generated when the used memory reaches 95 percent.
View the bar graph to see how the memory usage has trended over the selected time period. The yellow and red horizontal lines indicate the warning and critical thresholds.
Figure 12-14 Memory Used % Details and Graph
The wrench icon appears above the graph. For this graph, you can click the icon to change the graph style to line, bar, or area. You can also change the definition of the X axis from 1 day to 1 hour, 5 days, 3 weeks, 6 weeks, or 6 months. The export icon enables you to export the graph to file in CSV or XML format.
You have the opportunity to reset the threshold values for the monitoring rule from this page, or to view recommended threshold values based on past performance. When you click the Set Thresholds button, you are taken to the Thresholds tab, where you can enter new threshold values. When the Thresholds tab appears, the drop-down menu contains the name of the monitored attribute from the metrics view, and the associated chart is displayed. Editing a threshold value will create a custom set of monitoring rules for the asset. See Chapter 4, "Monitoring Rules and Policies" for more information about editing individual monitoring rule parameters and creating a custom monitoring policy.
The Virtualization Analytics view displays resource usage of the physical server for each running operating system instance, showing the physical resources consumed by the control domain (global zone or Oracle VM Server), and each non-global zone or guest. Metrics for Oracle VM Server for x86 are available through the Oracle VM Manager.
Virtualization Analytics Summary
Virtualization Analytics Zones or Virtualization Analytics Guests
Virtualization Analytics History
The information is refreshed every 20 seconds for a guest running on a virtualization server container, including global zones, Oracle VM Server for SPARC, and Oracle VM Server for x86.
Oracle Enterprise Manager Ops Center collects information every five minutes on every managed asset and displays the last hour of data on the asset's Summary tab and OS Details page. Use the following charts to see utilization data over longer periods of time, up to six months:
Power Utilization: Servers, chassis
CPU Utilization: Operating system, operating system for a virtualization host, virtual host, server pool
Memory Utilization: Operating system, virtual host, server pool
Network Utilization: Operating system, operating system for a virtual machine, virtualization host, server pool
File System Utilization: Oracle Solaris OS and Linux OS
System Load: Oracle Solaris OS and Linux OS
For the first five days of operation, the software collects data every five minutes. After the fifth day, the reported data is an average, according to the following:
Five days to three weeks: Average for each hour
Three weeks to six weeks: Average for each 12-hour period
Six weeks to six months: Average for each 24-hour period
The data is automatically deleted after six months.
The following figure is a sample chart for a managed OS asset.
Figure 12-15 Sample Chart for an Managed OS
In addition to displaying charts for individual assets, you can see charts for a group of assets: the five most-utilized assets and the five least-utilized assets in the group. In the Summary page of a group, hourly usage appears in a bar chart. You can create the following charts for the managed groups:
Server Group
Power
Chassis Group
OS Group
CPU Utilization
Network Utilization
System Load
Memory Utilization
Host Group
CPU Utilization
Network Utilization
Allocated Memory
Power
You can create charts 24 hours after you first manage the asset. The asset must be operating and the Enterprise Controller must be able to get access to the asset. You can use the default format or change the charts to use a line, bar, or area format or to use different time intervals.
By default, the graphs show one day of data. Click the Live button in the graph's toolbar to change to Live mode, which reports new information every 5 seconds. You can also change the graph to one of the following periods:
One hour (1H) – One point for every 5 minutes
One day (1D) – One point for every 5 minutes
Five days (5D – One point for every 5 minutes
Three weeks (3W) – One point every hour
Six weeks (6W) – One point every 12 hours
Six months (6M) – One point for every day To make a graph with the minimum of two points, a system must have been managed for at least 10 minutes to view a one-hour graph and for at least two days to view the six-months graph.
The software stores the data for these time periods separately. For example, when a server is managed for two hours and you select the 6W view, the graph does not display because only one point of data of that type is available; the second point has not yet occurred. When you select the 1D view, the graph displays 24 points of data (120 minutes in 5-minute intervals). However, the graph displays these points over a 24-hour period and not over the actual two-hour period. For the most accurate representation of the data, choose a time period that is less than or equal to the time that the selected server has been managed.
You can export the data for either the current view or all available data to a file in either CSV or XML format. Use the Export Chart Data tool bar icon to choose options for exporting the data.
When the graph is blank for a server, one of the following conditions has occurred:
Server does not have the appropriate ILOM version.
Server has not been discovered through the ILOM driver.
Server is unreachable.
The provisioning feature provides a method of automatically and consistently installing operating systems on managed systems from the Oracle Enterprise Manager Ops Center user interface.
You can provision the following operating systems:
Oracle, SuSE, and Red Hat Linux
Oracle Solaris (SPARC or x86)
Oracle VM Server for SPARC
Oracle VM Server for x86
Oracle Solaris Clusters
Note:
To provision Oracle Solaris 11, both the Enterprise Controller and Proxy Controller must be installed on a system that is running Oracle Solaris 11.To provision Oracle Solaris 9 and 10, you can use a Proxy Controller that is installed on a system that is running either Oracle Solaris or Linux.
Automated OS provisioning is performed through a managed service processor. You can provision the OS on a single system, one or more groups of systems, or a combination of systems that are attached to your network.
OS provisioning is handled by a profile and an associated deployment plan. The profile defines the image and the plan defines the tasks to perform and the targets to provision. Some plans are simple single step plans, others are multi-step plans where OS provisioning is a step in a larger plan.
You have many options available when you provision an operating system. The following steps are needed to complete a basic provisioning job:
Determine how you will import the OS image files, with either Dynamic Host Configuration Protocol (DHCP) or a WAN boot.
Import a file with the OS image into a Software Library. A provisioning profile is automatically created when you import the OS image. You can use this profile, edit the profile, or create a new profile. See Images and Images for OS Provisioning for details on importing images. See OS Provisioning Profiles for the types of profiles you can create.
Create or configure a deployment plan that includes your profile.
Manage the service processor for one or more systems to provision. See Discovering and Managing Assets for details.
Apply the deployment plan on the targets. When you choose a group as a target, it must be an homogeneous group where all members are the same.
After you import the OS images and create the OS profiles, you can reuse the profiles in a variety of plans that have OS provisioning as a step.
DHCP dynamically assigns IP addresses to devices on a network. A typical OS provisioning job requires an installation server and a DHCP server on the same subnet as that of the client systems. A JumpStart boot server must be on the same subnet as that of the client systems.
Before you can provision, you must configure DHCP services on the Proxy Controllers. You can use basic DHCP services, with or without defined subnets, or an external DHCP server. See the Administration Guide for information about how to configure DHCP and subnets for OS provisioning.
The WAN boot installation method enables you to boot and install software over a wide area network (WAN) by using HTTP. By using WAN boot, you can install the Solaris OS on SPARC based systems over a large public network where the network infrastructure might be untrustworthy. You can use WAN boot with security features to protect data confidentiality and installation image integrity.
WAN boot is the default connection for Oracle Solaris 11 provisioning. Oracle Solaris 11 provisioning does not use a Flash Archive (FLAR) image.
Oracle Solaris 10 provisioning can use a WAN boot or DHCP connection. With a WAN boot connection, Oracle Solaris 10 provisioning enables you to provision a FLAR image on a SPARC system using an HTTP web server. WAN boot installation is useful when DHCP does not meet your organization's security policies or you have SPARC-based systems that are located in geographically remote areas and you need to install servers or clients that are accessible only over a public network. Because WAN boot uses an HTTP server, it will work across your corporate firewall and does not require DHCP or a JumpStart boot server to be on the same network as the client systems.
The WAN boot installation method uses port 5555 and HTTP to boot and install software on SPARC-based ILOM, ALOM, or M-series systems over a wide area network (WAN). The WAN boot security features protect data confidentiality and installation image integrity over a large public network where the network infrastructure might be untrustworthy. You can use private keys to authenticate and encrypt data. You can also transmit your installation data and files over a secure HTTP connection by configuring your systems to use digital certificates. See "Security Configurations Supported by WAN Boot" in the Oracle Solaris 10 10/09 Installation Guide: Network-Based Installations document for more information about secure WAN boot installation configuration.
The following are required to use WAN boot with Oracle Enterprise Manager Ops Center:
Oracle Solaris 11
The target is a SPARC ALOM-CMT, ILOM-SPARC or M-Series platform that has a supported OBP or XCP. See Checking Your Client OBP for WAN Boot Support for how to check your client OBP. For M-Series, the XCP version should be at least version 1082.
The Enterprise Controller is installed on an Oracle Solaris operating system. You can use a SPARC or x86 platform for the Enterprise Controller.
WAN boot is enabled for Oracle Solaris 11 in Administration. See Disabling and Enabling WAN Boot.
Note:
When the target does not have the required OBP firmware version, Oracle Solaris 11 provisioning is disabled.Oracle Solaris 10
The target is a SPARC (ALOM-CMT, ILOM-SPARC or M-Series) and has the minimum OBP or XCP version
A FLAR image is used
The Enterprise Controller is installed on an Oracle Solaris operating system. You can use a SPARC or x86 platform for the Enterprise Controller.
WAN boot is enabled for Oracle Solaris 10 in Administration. See Disabling and Enabling WAN Boot.
Note:
When the target does not have the required OBP firmware version, Oracle Solaris 10 provisioning will revert to a DHCP connection.To determine if your client system has a WAN boot-enabled PROM, see Checking Your Client OBP for WAN Boot Support.
To determine if your client system has a WAN boot-enabled PROM, perform the following to check the client Open Boot PROM (OBP) for WAN boot support.
Log into a terminal window as root.
Type the following to check the OBP configuration variables for WAN boot support:
# eeprom | grep network-boot-arguments
The OBP supports WAN boot installations when the variable network-boot-arguments is displayed, or when the command returns the output network-boot-arguments: data not available. For example:
# eeprom | grep network-boot-arguments
network-boot-arguments: data not available
If the command in Step 2 does not return any output, the OBP does not support WAN boot installations. See your system documentation for information about how to update the OBP.
When Oracle Enterprise Manager Ops Center is installed on an Oracle Solaris operating system, the Enterprise Controller is automatically configured to be a WAN boot server.
Oracle Solaris 11 uses WAN boot. For earlier versions of Oracle Solaris, WAN boot is the default connection for provisioning when the requirements are met and you choose to use a FLAR image. When you launch an OS provisioning on an eligible SPARC-based system and you choose a FLAR image, the software automatically uses WAN boot. If you have a group of systems to provision, the software determines whether to use WAN boot or DHCP for each system.
WAN boot is automatically installed and enabled when the Enterprise Controller is running on an Oracle Solaris operating system. You can check the status, disable, or enable WAN boot in the Enterprise Controller configuration file. WAN boot is enabled when the value for the property is set to true in the Enterprise Controller configuration file. See the Oracle Enterprise Manager Ops Center Administration Guide for information about how to check the status, disable or enable the WAN boot connection.
Expand the Administration section in the Navigation pane, then click Enterprise Controller.
Click the Configuration tab.
Select OS Provisioning from the Subsystem menu.
For Oracle Solaris 11, see the following property: usesS11WANBoot.
For Oracle Solaris 10, see the following property: usesS10WANBoot.
To disable WAN boot, change the value for the property to false.
To enable WAN boot, change the value for the property to true.
Import your OS images into the Software Library before you can start a provisioning job. You can save the images in a Local Software Library on the Enterprise Controller or in a Network Attached Storage (NAS) Software Library that is created on an NFS server that the Enterprise Controller can access. See Creating a Software Library for details.
The provisioning profiles collects all the information such as type of target, OS image, time zone and language setup, required JET modules, disk partitions, naming services and network details. Depending on the type of operating system you are provisioning, include its parameters in the profile that installs the operating system.
Specify the following parameters:
Installation number – The number that enables you to install all of the Linux software that is included in your subscription.
Partition action – Use this parameter when you want to change the disk partition of the system.
You can opt to remove all the existing Linux partitions and retain the non-Linux partitions. You can provide specification for the new partitions.
You can opt to preserve all the existing partitions. You must define new partitions, outside of the partitions that exist, in which to install the OS.
You can opt to remove all the existing partitions. Define specification for the new partitions.
Install protocol – Specify HTTP or NFS as the install protocol.
Kernel parameters – Enter kernel parameters for the GRUB menu of the target system, when needed.
MD5 Checksum – Select this option to use MD5 encryption for user passwords.
Reboot action – Select whether you want to reboot the target system after OS installation.
Disk label initialization – Select this option to initialize labels on new disks. This option creates labels that are appropriate for the target system architecture.
Shadow passwords – Select this option to use an /etc/shadow file to store passwords on the target system.
Clear master boot record – Select this option to clear all invalid partition tables.
Linux packages – You can specify the Linux packages to include or exclude during provisioning. To include a package, enter the package name in a line. To exclude any package, enter the package name preceded by a dash (-).
To create a profile that installs the SuSE Linux OS, specify the following parameters:
FTP proxy server – Enter the name of the FTP proxy server to support FTP services.
HTTP proxy server – Enter the name of the HTTP proxy server to support HTTP services.
Install protocol – Specify HTTP or NFS as the install protocol.
Enable proxy servers – Select this option to enable the FTP and HTTP proxy servers that you specified in the FTP Proxy Server and HTTP Proxy Server fields.
Kernel parameters – Enter kernel parameters for the GRUB menu of the target system, when necessary.
Reboot action – Select whether you want to reboot the target system after OS installation.
Linux packages – You can specify the Linux packages to include or exclude during provisioning. To include a package, enter the package name in a line. To exclude any package, enter the package name preceded by a dash (-).
Each profile is defined by the OS image that is either in the Software Library, or is imported into the Software Library. When you import an OS image into the software library, a default provisioning profile is automatically created. You can edit the default profile or you can create a new profile.
For each profile, you specify the setup parameters, file system parameters, the management mode, and the naming service for the operating system. For Oracle Solaris only, you can optionally use JET Modules to specify additional Installation Parameters. To learn more about JET and how to use JET in a profile, see JumpStart Enterprise Toolkit (JET) for Oracle Solaris.
When you choose the agent managed mode, you can perform software updates and create operating system reports.When you choose agentlessly managed, SSH credentials are required to monitor the operating system. You can change the management mode after the OS is provisioned.
A provisioning profile, requires a DHCP-enabled network interface for the boot interface. You can add multiple networks, as long as the networks are available and defined in the Enterprise Controller. You can select a NIC from the list of available logical interfaces for each network or, as shown in Figure 12-16, you can use the Address Allocation Method for the selected networks. You cannot use the Address Allocation method for the boot interface. When you use a static IP address, you must provide the IP address when you apply a deployment plan that uses the profile. The IP address is assigned to the target system after provisioning.
By default, the profile reboots the OS. You can choose the Manual Net Boot option to enable manual control of network boot operations for the target system.
Note:
The Enterprise Controller cannot remotely control the network boot process on systems that do not have a service processor. When your target system does not have a service processor, you must select the Manual Net Boot option.To create a profile that installs an Oracle VM Server Control Domain, define the following parameters:
CPU Threads
Memory
Crypto Units
Virtual Console Port Range
Enable JASS
Enabling JASS results in installation of SUNWJass package to harden the system when installing Oracle VM Server 1.2 or lower versions. JASS is not supported for Oracle VM Server for SPARC 1.3 or higher versions. When you select Enable JASS in the profile that is installing Oracle VM Server for SPARC version 1.3 or 2.0, the software disregards this option and JASS is not enabled.
Enable Multiplexed I/O
Enabling multiplexed I/O on a system used for storage enables the Fibre Channel ports on the system.
JumpStart Enterprise Toolkit (JET) provides a framework to simplify and extend the JumpStart functionality provided within the Oracle Solaris operating system. The SUNWjet and JetFLASH packages are installed on the Proxy Controller during installation.
Using JET provides more options for defining the Jumpstart parameters. When you install JET on a JumpStart server, you have the following advantages:
Install multiple versions of Oracle Solaris
Deploy flash archives
Utilize multiple boot methods
Install recommended patches
Configure all your network interfaces
Note:
You cannot define IPMP groups or link aggregation for a JET template profile.Table 12-5 describes the JET modules that are installed on the Proxy Controller.
Table 12-5 JET Modules and Associated Packages
| JET Module Name | JET Package | Description |
|---|---|---|
|
base_config |
SUNWjet |
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 |
Adds functionality to the JumpStart framework to handle packages, patches, scripts, and files. |
|
flash |
JetFLASH |
Adds the ability for the JumpStart server to deliver Solaris images in Solaris Flash format. |
See Appendix D, "JumpStart Enterprise Toolkit" for a list of SUNWjet parameters.
To create a profile that uses the JumpStart Enterprise Toolkit (JET), select a JET template that defines all the parameters for OS provisioning.
Place the JET template on a directory that the Enterprise Controller can access. You can also create a JET template on the Enterprise Controller in the directory /opt/SUNWjet/Templates, using the following command:
./make_template template_name
A sample template is provided. You can make a copy and change the values in the JET template as required. During provisioning, the OS provisioning parameters are read from the template. After you create the JET templates you want and save them on the Enterprise Controller, you can use them in your Oracle Solaris provisioning profiles.
When you create a profile, the default action creates a deployment plan and associates the plan with the profile. To provision an OS, you must have an OS image. Importing OS images and creating OS profiles are one-time tasks for each OS-target combination. After an OS image and an associated OS profile are created, you can use deployment plan to provision the operating system onto one or more managed systems at the same time.
Note:
It is a good practice to place the systems that you are going to provision in Maintenance Mode so that you can take the system offline without generating alerts and incidents.The following is the general workflow for provisioning an OS:
Import a file with the OS image into a Software Library. The import process creates a profile that specifies the name and location of the OS image.
Use a deployment plan that includes the profile, either the default one, or one that you create.
Apply the deployment plan on the targets. Oracle Enterprise Manager Ops Center enables OS provisioning on single systems, groups of systems, a combination of the single systems and groups, or Oracle Solaris Clusters. OS provisioning for groups of systems requires using homogeneous groups.
To provision an operating system on an Oracle Solaris Cluster, you provision the same operating system on all nodes of a cluster. The Cluster OS Profile profile handles the pre-action and post-action operations. See the Oracle Solaris Cluster documentation and Appendix B, "Oracle Solaris Cluster" for how to install a new Oracle Solaris Cluster and to maintain existing Oracle Solaris Clusters.
Using the provisioning profiles created for different targets, create a deployment plan with the associated profile. Several multi-step and complex plans use an OS provisioning profile and plan as a step in the larger plan. Provisioning an Oracle Solaris 11 operating system is a different procedure from provisioning earlier versions.
The following deployment plans include a step to provision an operating system:
Provision an Oracle Solaris or Linux OS
Provision an Oracle Solaris 11 OS
Provision and Update Logical Domains
Provision an OS on an Oracle Solaris Cluster
You can create OS profiles for provisioning Linux OS on x86 systems or Oracle Solaris on x86 or SPARC systems. See Provisioning Oracle Solaris 11 for details on provisioning Oracle Solaris 11.
Perform the following before you provision the operating system:
Import the OS image. A default OS provisioning profile for the image is automatically created. Uploading the packages from Oracle to the library can take several hours.
(Optional) Edit an existing OS provisioning profile or create a new profile.
Discover the service processors of the target systems.
Verify that the Dynamic Host Configuration Protocol (DHCP) services are enabled on Proxy Controllers. You cannot create a profile or assign any network if the DHCP services are not enabled. The Install Server option to provision OS on a server is not enabled if the DHCP is not enabled on any of the interfaces.
Verify that any scripts the profile uses are in a directory that the Enterprise Controller can access. You can save scripts in a local directory of the Enterprise Controller, or in a directory that the Enterprise Controller mounts using NFS.
When you are provisioning a dynamic system domain of an M-Series server, the domain must have an IP address.
Disable monitoring for the target systems to prevent events related to a system going offline. See Maintenance Mode for more information.
Complete the following steps to provision an operating, system:
Verify that the OS image and profile are available and configured with the parameters you want to use.
Discover the service processors of the target systems.
Place the asset in Maintenance Mode to prevent events related to a system going offline
Select the OS Provisioning plan, or a plan that uses OS Provisioning as a step.
Define the targets for the plan, make any last minute changes in the plan, then submit the job.
Oracle Solaris 11 uses a new OS provisioning technology, called the Automated Installer. This feature replaces the older JumpStart Enterprise Toolkit technology that Oracle Enterprise Manager Ops Center uses to provision earlier versions of Oracle Solaris.
Oracle Enterprise Manager Ops Center reduces the complexity by using a local copy of the Oracle Solaris 11 Software Library on the Enterprise Controller and creating an Automated Installer server on the Proxy Controller for your use.
Note:
To provision an Oracle Solaris 11 operating system, the Enterprise Controller and Proxy Controller must both be running on an Oracle Solaris 11 operating system. The repository resides on the Enterprise Controller and the Automated Installer server resides on the Proxy Controller. When the Enterprise Controller and Proxy Controller are not running on Oracle Solaris 11, the Oracle Solaris 11 library and OS provisioning actions are not available.Oracle Solaris 11 uses the following components for provisioning an operating system:
Oracle Solaris 11 Software Library – A local version of the software package repository. You can update the Oracle Solaris 11 Software Library, as needed, and then provision multiple systems without using a network connection to Oracle for each provisioning job. See Chapter 5, "Software Libraries" for more information about adding content to libraries.
Installation manifest – Defines the system configuration, including what software to install and details on the virtualized environments to provision. A default manifest is included with each Image Packaging System (IPS) software repository.
DCHP or WAN boot connection
x86 client – Requires a DHCP connection.
SPARC client – Requires a DHCP or WAN boot connection. Oracle Enterprise Manager Ops Center automatically sets up WAN boot connection.
Note:
Oracle Solaris 11 only supports a ISC DHCP Server. Oracle Solaris DHCP Server is not supported.You can provision Oracle Solaris 11 zones as part of the OS installation. After a system is bootstrapped with a minimized operating system, the operating system is installed from the Oracle Solaris 11 Software Update Library in Oracle Enterprise Manager Ops Center. The zones are provisioned during the initial system reboot after the base operating system is installed.
You can create multiple profiles to respond to subtle variations in hardware attributes, software profiles, or your organization's requirements.
Before you can create provisioning profiles, verify that the Oracle Solaris 11 Software Library is configured on the Enterprise Controller and the package you want is available in the library.
When you create an Oracle Solaris 11 OS provisioning profile, you select the architecture, either SPARC or x86, to display the boot image and distribution for your architecture. You must provide non-root user credentials and root user credentials. You can only use non-root user credentials to login or SSH to the client after install.
The boot image has several associated software groups. You must select one of the following software groups:
large-server
small-server
desktop
The boot image might have additional Software groups that you can select, such as storage-server and NAS attached. You can select one or more of these groups. Each group has a tool tip that provides a description of the group.
To install the OS to an iSCSI disk, select the Use iSCSI Disk option when you create the profile, then specify the iSCSI disk settings. When you use this option, you must provide the following parameters when you deploy the OS Provisioning plan:
Storage server IP
SCSI disk LUN
The following are the main steps to provision an Oracle Solaris 11 operating system:
Create an Oracle Solaris 11 OS provisioning profile.
From the Library section, initialize the Oracle Solaris 11 Software Update Library.
From the Plan Management section, create a Solaris 11 x86 or SPARC profile (the Solaris 11 images are pre-imported as part of MSR creation.
Target the plan to an x86 server or WAN boot-capable SPARC server.
Boot environments are a feature of Oracle Solaris. A boot environment is an instance of a bootable Oracle Solaris image plus additional software packages that are installed onto the image, and the set of all file systems and devices (disk slices and mount points) that are required to operate an Oracle Solaris OS instance. You can have disk slices, also known as partitions, on the same disk or distributed across several disks.
A dual boot environment consists of a live, or active, boot environment (BE) and one or more inactive alternate boot environments (ABE). A system can have only one active boot environment, which is the booted environment. An alternate boot environment is an inactive environment that is not currently booted. A system can have many inactive boot environments. You can activate an alternate boot environment at any time.
You can use a dual boot environment within Oracle Enterprise Manager Ops Center to manage your Oracle Solaris software. A dual boot environment is often used to manage updates because it can significantly reduce the service outage time that is usually associated with patching. Maintaining multiple boot environments also enables quick and easy rollback to a version before the patches were applied, if needed. The boot environment technology enables you to duplicate a boot environment and perform the following tasks without affecting the currently running system:
Run an Oracle Solaris software update simulation on the inactive boot environment. You can run the simulation with or without downloading the patches.
Update your Oracle Solaris OS on the inactive boot environment and test the update before deploying it as your active 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.
The boot environment feature changed beginning with Oracle Solaris 11, including the supported file systems, file system requirements, zone support, and how boot environments are created.
Oracle Solaris 11 Boot Environments use the beadm utility and ZFS file systems to create and manage boot environments. You do not need to create boot environments ahead of time. The software creates them automatically. You can use an agent-managed or agentless-managed operating system with the Oracle Solaris 11 Boot Environments feature.
Oracle Solaris 10 and earlier use the Live Upgrade feature with lucreate scripts and ZFS or UDFS file systems to create alternate boot environments. You must use an agent-managed operating system with the Oracle Solaris Live Upgrade feature.
The Boot Environments profile defines the boot environment for the OS update deployment plans. The Oracle Solaris release determines how the profile is used:
Oracle Solaris 11 – The profile indicates the policy that is used when an OS update plan is executed. Use this profile to define the creation policies and as a step in an OS update deployment plan.
Oracle Solaris 8, 9, and 10 – The profile defines the lucreate script that is used to create your alternate boot environments. Use this profile to specify how to create alternate boot environments for the eligible operating systems in your data center, create alternate boot environments, synchronize and activate boot environments, and as a step in an OS update deployment plan.
The user interface assists you in easily navigating the differences in the boot environments features and provides a unified view whenever possible. See Oracle Solaris 11 Boot Environments and Oracle Solaris 10 and Earlier Boot Environments for detailed version-specific information.
Monitoring rules and thresholds are defined in the Monitoring tab. The following rules apply to boot environments:
Number of Boot Environments – Defines the number of boot environments in the selected zone.
Boot Env Usage Percent in a ZPool – Defines the percentage disk utilization on the boot environments in any of the zpools.
Each rule has two defined thresholds:
Warning – Generates a warning alert and displays the yellow warning badge in the asset tree. A warning alert contains a suggested action.
Critical – Generates a critical alert and displays the red critical badge in the asset tree. By default, a critical alert contains an automated action.
See Monitoring Operating Systems for more information.
To Clear a Boot Environment Incident
Perform the following steps to manually clear the disk space and close the incident:
Click an OS in the Asset tree to view the Boot Environment in the center pane, then click the Incidents tab.
Delete one or more boot environments to clear the disk space.
Select one or more incidents, then click the Close Incident(s) icon in the center pane.
See Chapter 4, "Monitoring Rules and Policies" for details on how monitoring rules and policies work in the software and see Chapter 9, "Incidents" for information on how to manage and close an incident.
The active boot environment is identified in the Boot Environments tab and in the Summary tab. Inactive boot environments appear in the Boot Environments tab for each operating system. For global zones, the Boot Environments tab displays the relationship between the associated zones and existing boot environments.
Note:
If there are no alternate boot environments, the Boot Environments tab is not displayed in the center pane.Boot environment support for Oracle Zones is available beginning with Oracle Solaris 11, enabling boot environments from the non-global zone to appear in the asset tree.
The Summary tab provides the name of the active boot environment, the zpool utilization of all zpools for the selected OS and the amount of zpool utilization attributed to the boot environments. Details are available in the Boot Environments tab.
Click an OS or zone in the Asset tree. Details about the active boot environment appear in the Summary tab.
Non-bootable snapshots are available beginning with Oracle Solaris 11. When a boot environment has one or more associated non-bootable snapshots, the snapshots appear in the Snapshots subtab, as shown in Figure 12-17.
Figure 12-17 Boot Environment Tab and Snapshots Subtab
Click the Boot Environments tab in the center pane to see details about the associated alternate boot environments.
If the tab is disabled, no alternate boot environments exist for that OS in the zone or non-global zone.
To display file system details, click the boot environment in the table, then click the File Systems subtab:
Oracle Solaris 11 – Mount point information, boot environment file systems, zone boot environment information, and non-global zones in the selected boot environment. When a global zone boot environment is selected, the zone boot environment details are listed separately, a zone per row. You can expand all rows to display a complete view of all zone boot environments under the selected global zone boot environment.
Oracle Solaris 10 – Mount point information and boot environment file systems.
To display associated zone boot environment details, click the boot environment in the table, then click the Associated Zone BEs subtab:
Oracle Solaris 11 – Mount point information, boot environment file systems, zone boot environment information, and non-global zones in the selected boot environment. When a global zone boot environment is selected, the zone boot environment details are listed separately, a zone per row. You can expand all rows to display a complete view of all zone boot environments under the selected global zone boot environment.
Oracle Solaris 10 – Mount point information and boot environment file systems.
Monitoring rules and thresholds are defined in the Monitoring tab.
You can view all available boot environments for a system, and choose to activate an alternate boot environment or delete inactive environments.
Activating a boot environment makes an inactive or alternate boot environment the active boot environment. You can activate a single boot environment, or you can select an OS group and activate an alternate boot environment for each operating system.
To Activate a Single Boot Environment
Information about boot environments appears in the Boot Environments tab for each operating system.
Perform the following steps to activate a single boot environment:
Click an Oracle Solaris 11 global or non-global zone or an Oracle Solaris 10 global zone in the Asset tree.
Click the Boot Environments tab.
Existing boot environments for the OS appear in the center pane.
To Activate Boot Environments for All Members of a Group
You can activate an alternate boot environment for all members of a group. If each OS in the group has a single alternate boot environment, all operating systems are booted into the alternate boot environment. When some systems have more than one alternate boot environment, you are prompted to select the alternate boot environment.
Perform the following steps to activate boot environments for all members of an operating system group:
Select an Oracle Solaris 11 or an Oracle Solaris 10 Operating system group from the Assets section in the Navigation pane.
Click Activate Boot Environment and Reboot in the Actions pane.
For systems with multiple alternate boot environments, select the one that you want to boot into. A Filter ABE by name option is available to identify similarly named alternate boot environments across multiple targets.
When you delete a boot environment, you delete all associated snapshots and unshared file systems. A snapshot is a non-bootable copy of a boot environment. If there are non-global zone boot environments associated with the global zone boot environment, they are deleted too. Shared file systems are not deleted.
You cannot delete the active boot environment.
Click an Oracle Solaris 11 global or non-global zone, or an Oracle Solaris 10 global zone in the Asset tree.
Click the Boot Environments tab.
Select one or more boot environments or snapshots that you want to remove, then click the Delete icon. Figure 12-18 shows a snapshot selected for deletion.
Figure 12-18 Delete an Oracle Solaris 11 Snapshot
Oracle Solaris 11 uses ZFS file systems, where the swap and dump volumes are shared within the pool. For unshared file systems, ZFS is the only supported file system for boot environments on Oracle Solaris 11. With the ZFS-based boot environment, the boot environments are clones of the existing ZFS partitions. This saves disk space and you do not need to reserve disk partitions for additional boot environments. The create and activate boot environment functionality is much faster than in previous versions.
Oracle Solaris 11 boot environments are managed through the beadm utility. A new boot environment is created whenever the kernel or system packages are installed or updated. This can result in high disk space utilization levels. By default, Oracle Enterprise Manager Ops Center monitors the disk (zpool) utilization of boot environments. If the utilization levels exceed defined thresholds, you can delete unwanted boot environments.
When a boot environment is created in the global zone, the following occurs:
A Boot Environment of the source boot environment is created (the boot environment from which it is cloned).
The currently active boot environment in all of the non-global zones is cloned and it is associated with the global zone boot environment that was just created.
When a global zone boot environment is activated, the active boot environment data set that is associated with that boot environment in each non-global zone is mounted and activated. Only one non-global zone boot environment that is associated with a global zone boot environment can be active.
When a global zone boot environment is deleted, all corresponding zone-specific boot environments are also deleted.
When a non-global zone is deleted, all corresponding boot environments are deleted. The boot environments for other zones are not deleted.
The Oracle Solaris 11 Boot Environments tab provides you with a large amount of information about the boot environments that are associated with the selected physical or virtual Oracle Solaris 11 operating system. This is particularly valuable since Oracle Solaris 11 boot environments are automatically created and they can quickly consume valuable resources. The following information is available:
The first section in the Boot Environments tab is Total ZPools Utilization. It is compressed by default. Use the arrow to expand the table. The amount of resources used by the zpool appears in this section, as shown in Figure 12-19.
Figure 12-19 Oracle Solaris 11 Total ZPools Utilization
All boot environments that are associated with the physical or virtual operating system that is selected in the Asset tree appear in the Boot Environments table. As shown in Figure 12-20, the active status, size, and when the boot environment was created appear in this section. A green check mark icon next to the boot environment name identifies the boot environment as active. A green check mark with a green circle and white x indicates that this is the boot environment that is active upon reboot. When you see two green check marks in the Active column, the boot environment is active and is the active boot environment upon reboot.
Figure 12-20 Oracle Solaris 11 Boot Environments Tab
The lower section of the page has three tabs that provide details about the boot environment that you select in the Boot Environments table.
A snapshot is a point-in-time image of a Volume. It is a non-bootable copy of a boot environment that uses much less disk space than a boot environment. You can create a boot environment from a snapshot.
Non-bootable snapshots are available beginning with Oracle Solaris 11. Select a boot environment in the Boot Environments table to see all associated non-bootable snapshots in the Snapshots tab. You can select a snapshot in this tab and click the icon to create a boot environment from the snapshot.
Figure 12-21 Oracle Solaris 11 Boot Environment Snapshots
The File Systems tab provides file system details for the boot environment, or alternate boot environment, that you select in the Boot Environments tab. As shown in Figure 12-22, the file system name, type, size and mount location appear in this table. You can also see if the file system is shared or not.
Figure 12-22 Oracle Solaris 11 Boot Environments File Systems
The Associated Zone BEs tab is populated with the boot environment details for a selected zone's boot environment. The zone might have multiple boot environments. The table shows whether the boot environment selected is active. You can see the boot environment name, the zone name, the size and when the boot environment was created. As shown in Figure 12-23, when you select an operating system that is not a zone, No Data appears in the table.
Figure 12-23 Oracle Solaris 11 Boot Environments Associated Zone BEs
A Boot Environments plan and profile for Oracle Solaris 11 operating systems identifies and defines how the boot environment is updated and activated. You can use an agent-managed or agentless-managed operating system.
Use the profile for Oracle Solaris 11 to perform the following tasks:
Create a Boot Environments profile that defines the creation policies
Create an OS update deployment plan, specifying a Boot Environments profile and an OS update profile
You can create profiles with different policy options. The following options are available for Oracle Solaris 11:
Create a new boot environment only when needed, such as when the OS update operation requires a reboot.
Always create a new boot environment
Never create a new boot environment
Activate and reboot
To Create a Boot Environments Profile for Oracle Solaris 11
Click Plan Management in the Navigation pane, then scroll down to the Profiles and Policies directory and click Boot Environments.
The Boot Environments Profiles page appears in the center pane.
Click Create Profile in the Actions pane.
Identify the profile by typing a unique profile name, provide a description, and select the Oracle Solaris 11 subtype.
Choose the boot environment policy for this profile:
Create a new boot environment when needed
Always create a new boot environment
Never create a new boot environment
Click the check box to activate boot environment and reboot when the job is completed.
Choose to have the software automatically create a unique name or enter a specific boot environment name in the field provided, then click Finish.
To Copy an Oracle Solaris 11 Boot Environments Profile
Copying a boot environment profile makes a copy of an existing profile.
Click Plan Management in the Navigation pane, then scroll down to the Profiles and Policies directory and click Boot Environments.
The Boot Environments Profiles page appears in the center pane.
Select the profile to copy, then click the Copy Profile icon in the center pane.
Identify the profile by typing a unique profile name and description.
Change the boot environment parameters, as needed, then click Finish.
A new alternate boot environment is automatically created when you install or update the operating system's kernel or system packages.
You can create a bootable or non-bootable copy an existing boot environment. A non-bootable copy is call a snapshot. You can create a boot environment from a snapshot.
To Create an Oracle Solaris 11 Boot Environment
You can create a bootable or non-bootable (snapshot) copy of an Oracle Solaris 11 boot environment.
Click an Oracle Solaris 11 OS, a global or non-global zone, in the Asset tree, then click the Boot Environments tab.
Select the boot environment to copy, then click the Create icon.
Select the option, either the Create a Snapshot or Create a BE option, and select the boot environment to use as the source. Type a unique name for the boot environment and provide a description that includes the purpose of the boot environment and the name of the source boot environment, then click Create.
Figure 12-24 Create Boot Environment for Oracle Solaris 11
When the job finishes, refresh the Boot Environment table to see the new boot environment.
If you have a group that contains only Oracle Solaris 11 operating systems and you select the OS group as the target, a new boot environment is created for every active boot environment in the group. You can assign a common name for all of the boot environments. If you do not assign a common name, default names are assigned.
Boot environments in Oracle Solaris 8, 9, and 10 are managed through the Live Upgrade feature. A boot environment is created by using a script that contains the lucreate command and options.
The Live Upgrade feature is available on the following operating systems:
Oracle Solaris 10 OS for x86 platform versions through Oracle Solaris 10 5/09 – Update alternate boot environments for physical systems.
Oracle Solaris 10 OS for SPARC through Oracle Solaris 10 5/09 – Update alternate boot environments for physical and virtual machines, including Oracle Solaris Zones and Oracle VM Server for SPARC (formerly known as Logical Domains).
Oracle Solaris 9 OS SPARC – Update alternate boot environments for physical machines using a UFS file system.
Oracle Solaris 8 OS SPARC – Update alternate boot environments for physical machines using a UFS file system.
Note:
Do not use Oracle Solaris Live Upgrade on your Enterprise Controller or Proxy Controllers. It does not synchronize all of the files that are required for these Oracle Enterprise Manager Ops Center components.To create and update alternate boot environments, install the latest Oracle Solaris Live Upgrade packages and patches. This ensures that you have all the latest bug fixes and features. In addition, verify that the disk space and format are sufficient for an alternate boot environment.
Live Upgrade packages and patches are available for each Oracle Solaris software release beginning with Oracle Solaris 9 OS. Use the packages and patches that are appropriate for your software instance. To use Live Upgrade with Oracle Solaris 8 OS, follow the special patching instructions.
If you installed Oracle Solaris 10 using any of the following software groups, have the required packages:
Entire Oracle Solaris Software Group Plus OEM Support
Entire Oracle Solaris Software Group
Developer Oracle Solaris Software Group
End User Oracle Solaris Software Group
When you install one of these Software Groups, verify that you have all of the required packages:
Core System Support Software Group
Reduced Network Support Software Group
For detailed requirements to install and use the Live Upgrade feature, see the Oracle Solaris 10 Installation Guide: Solaris Live Upgrade and Upgrade Planning. For information on other releases, see the Oracle Solaris Documentation Library. Review and verify that all the packages and patches that are relevant to your system are installed and that the disk is formatted properly before creating a new boot environment.
For Oracle Solaris 9 and 10 alternate boot environments, file systems are categorized into the following types:
Critical File Systems – Non-shareable file systems that are required by the Oracle Solaris OS, such as root (/), /usr, /var, and /opt. These file systems are separate mount points in the vfstab of the active and inactive boot environments and are always copied from the source to the inactive boot environment.
Shareable File Systems – User-defined files, such as /export, that contain the same mount point in the vfstab in both the active and inactive boot environments. Updating shared files in the active boot environment also updates data in the inactive boot environment. When you create a boot environment, shareable file systems are shared by default. If you specify a destination slice, also known as a partition, the file systems are copied.
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.
When creating a new boot environment in Oracle Solaris 9 or 10, the entire contents of a slice is copied to the designated new boot environment slice. You might want some large file systems on that slice to be shared between boot environments rather than copied to conserve space and copying time. File systems that are critical to the OS such as root (/) and /var must be copied. File systems such as /home are not critical file systems and could be shared between boot environments. Shareable file systems must be user-defined file systems and on separate swap slices on both the active and new boot environments. You can reconfigure the disk several ways, depending your needs.
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 systems, /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. To share a directory, the directory must be split off to its own slice.
The following requirements are needed to use the Live Upgrade feature with zones:
Agent managed operating system
At least Oracle Solaris 10 5/09 (update 7) operating system
Storage library used to house the zones cannot be part of the root pool; you must create a separate pool on a shared file system
You cannot use the -p option to create alternate boot environments
The -p option, which copies between two root pools on ZFS configuration, is not supported with the lucreate command.
Note:
If you plan to use alternate boot environments with zones, you must designate sufficient zone storage space. When you create the zones and configure the zone storage, specify twice the size of the zone file system for the root file system of the zone. For example if your zone root file system was configured as 8 GB, the storage used to back up the zone must be at least 16 GB.See Update Zones for how to update Oracle Solaris Zones without using a dual boot environment.
The Oracle Solaris 10 Boot Environments tab provides you with a large amount of information about the boot environments that are associated with the selected Oracle Solaris operating system. A Boot Environments tab is not available for Oracle Solaris 10 non-global zones. The following information is available:
Total ZPools Utilization for Oracle Solaris 10 and Earlier Boot Environments
File Systems for Oracle Solaris 10 and Earlier Boot Environments
The first section in the Boot Environments tab is Total ZPools Utilization. It is compressed by default, use the arrow to expand the table. The amount of resources used by the zpool appears in this section, as shown in Figure 12-25.
Figure 12-25 Oracle Solaris 10 and Earlier Total ZPools Utilization
All boot environments that are associated with the physical or virtual operating system that is selected in the Asset tree appear in the Boot Environments table. As shown in Figure 12-26, the active status, size, description, and when the boot environment was created or synchronized appear in this section. A green check mark icon next to the boot environment name identifies the boot environment as active. A green check mark with a green circle and white x indicates that this is the boot environment that is active upon reboot. When you see two green check marks in the Active column, the boot environment is active and is the active boot environment upon reboot.
Figure 12-26 Boot Environments for Oracle Solaris 10 and Earlier
The lower section of the page the File Systems tab that provide details about the boot environment that you select in the Boot Environments table.
The File Systems tab provides file system details for the boot environment, or alternate boot environment, that you select in the Boot Environments tab. As shown in Figure 12-27, the file system name, type, size and mount location appear in this table. You can also see if the file system is shared or not.
Figure 12-27 Oracle Solaris 10 Boot Environments File Systems
You can use an alternate boot environment that was created outside of Oracle Enterprise Manager Ops Center; however, the preferred method is to create a Boot Environment profile and use the associated plan to create a boot environment. In either case, the operating system must be an agent-managed asset in the Oracle Enterprise Manager Ops Center software.
Use the profile for Oracle Solaris 10 and earlier releases to perform the following tasks:
Create a Boot Environments profile to specify how to create boot environments across all your managed system, using lucreate scripts
Create your boot environments using the action in the action panel for your assets. This is typically a one time operation, as you'll probably reuse the alternate boot environment.
Create a Boot Environments profile to always sync (and possibly) activate. Use this profile for OS update deployment plans.
Create an OS update deployment plan specifying the boot environment in step 3 and any OS update profile
Depending on the Oracle Solaris version that you are using, several methods are available for creating alternate boot environments. The Oracle Enterprise Manager Ops Center software uses Boot Environments profiles to help standardize and simplify the process.
Perform the following tasks before creating a Boot Environments profile:
Each Boot Environments profile can have a different boot environment policy. The following options are available:
For Oracle Solaris 11
Create a new boot environment, as needed
Always create a new boot environment
Never create a new boot environment
Activate and reboot the boot environment
For Oracle Solaris 8, 9, or 10
Activate Boot Environment and reboot on job completion
Synchronize existing Boot Environment before submitting a job
For Oracle Solaris 8, 9 and 10 only, determine the file system and swap requirements and the lucreate command options that you want to use. If you are using ZFS, create a zpool. See the Oracle Solaris documentation for more information about the requirements and command options for the Live Upgrade feature.
You can create an operational plan that includes your script, or you can enter the lucreate options directly in the Boot Environments profile without creating a script.
The following is a high-level overview of how to create an alternate boot environment for Oracle Solaris 10 and earlier releases.
Create an Boot Environments profile.
The profile identifies and defines how the boot environment is created and activated, including defining the target type, the options used to create the boot environment, and the activation parameters. Review the Oracle Solaris 10 Live Upgrade documentation for more details on the requirements:
Define your file system and swap requirements.
Determine the lucreate command options. You can enter the options in the Boot Environments profile, or you can create an operational profile that contains a script with the lucreate command and options. If you are specifying a variable boot environment name in the script passed to the operational profile, make sure the variable is called BEName. If you use this as the variable name, the operational plan will pass on the BE name entered during plan execution to the lucreate script.
Determine your boot environment policies
Create a deployment plan.
The Boot Environment deployment plan defines the failure policy and is associated with a single Boot Environments profile. You can add a Boot Environments profile as a task, or step, within a complex deployment plan. See Plan Management for information about complex plans.
Execute the deployment plan.
After the deployment plans are created, a user with the appropriate role and privileges can choose from a list of plans to quickly and consistently create an alternate boot environment.
Create and deploy an OS Update plan to update the inactive boot environment. See Update an Oracle Solaris Boot Environment for the steps to create and deploy the OS Update plan.
For information about system administration tasks such as managing file systems, mounting, booting, and managing swap space, see the Oracle Solaris System Administration Guide: Devices and File Systems in the Oracle Solaris 10 Documentation Library.
Oracle Solaris Live Upgrade scripts are used to create an alternate boot environment. To create a replica of your boot environment, run the script in Oracle Enterprise Manager Ops Center.
The following methods are available to create the alternate boot environment:
Copy an existing boot environment.
Execute a Boot Environments deployment plan.
The deployment plan must reference an Boot Environments profile.
Run an operational plan that contains the lucreate script.
Upload an Oracle Solaris Live Upgrade script as Local Content in Enterprise Manager Ops Center.
Run an OS update job and specify a pre-action which runs the script. You can select multiple compatible targets and create an alternate boot environment for each target using the same script at the same time.
Create an OS profile, and then run an OS Update job. The profile enables you to define the components and the actions to be performed every time you use the profile to create an alternate boot environment.
Run an Oracle Solaris Live Upgrade script from the command line. With this method, you must log in to each agent and then run the script to create the boot environment.
When you create the alternate boot environment 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 Environments tab appears in the center pane for OS management.
This task describes how to run a New OS Update job to create the alternate boot environment. Although it is a New OS Update job, the sole purpose of the job is to create an alternate boot environment. The job uses the Live Upgrade script that you uploaded to Local Content to create a duplicate of your boot environment.
To create boot environments for Oracle Solaris 10, you can define the options in an Boot Environments profile or you can add a script to an operational profile. The software enables you to store the scripts and parameters and provides a couple of methods of deploying the scripts.
As a profile
As part of a plan
As part of an update job
The scripts use the lucreate command to create an alternate boot environment. To see a complete list of options, see the Oracle Solaris 10 OS Live Upgrade lucreate(1M) documentation. The following are some commonly used options:
-m option to create a boot environment and split a directory off to its own slice.
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 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 must run the lucreate command with the -m option again to create another boot environment. The two new boot environments can then share the directory.
-s option to force a synchronization.
-p specifies the ZFS pool in which a new boot environment will reside.
This option is not required if the source and target boot environments are within the same pool. This option does not support the splitting and merging of file systems in a target boot environment that is supported by the -m option.
Existing boot environments appear in the hierarchy in the Boot Environments tab for a global zone. You can create the boot environment with Oracle Enterprise Manager Ops Center or outside of the software.
You can only create a boot environment from a global zone in Oracle Solaris 10. The boot environments on Oracle Solaris non-global zones are tightly coupled with the corresponding boot environment on the global zone and cannot be managed independently.
For Oracle Solaris 10, the boot environment is created from the default alternate boot environment profile. You can override the applicable parameters in the profile.
Click an Oracle Solaris 10 OS global zone in the Asset tree to view the Boot Environment in the center pane.
Click the Boot Environment tab.
Existing boot environments for the OS appear in the center pane.
To create a copy, or clone, of the existing active boot environment, click the Create icon.
The plan for execution that uses the default Boot Environments profile for Oracle Solaris 10 is launched.
Type a unique name for the boot environment and provide a description. The text describes what the boot environment and from what source it was created. Edit the applicable parameters in the Alternate Boot Environment profile, then click Confirm.
When the job finishes, refresh the Boot Environment table to see the new boot environment.
An operational profile contains a single script and can define variables. The profile is launched by an associated plan. An operational plan is associated with a specific version of an operational profile. By default, creating a profile also creates an operational plan.
You can create the boot environments using this script from a few different contexts:
Simple BE Operational profile
Boot Environments profile using BE Operational profile from the plan context
Create Boot Environment from the asset context
You can save a shell script on the Enterprise Controller and download it into the plan, or you can enter the script in a text field when you create the plan. Both types of shell scripts are executed by the user. They differ in the location, either on the Enterprise Controller or on the remote Agent, and the user credentials needed to execute the profile. See Operational Profiles and Plans for more information about operational profiles and plans and the variables you can use.
Click Plan Management in the Navigation pane, then click Operational Profiles. The Operational Profiles appear in the center pane.
Click Create Operational Profile. The Create Profile - Operation page appears.
Type a name for the new plan and a description of its purpose or role.
Select an asset type from the Subtype list.
Click Next.
Select the Operation Type from the drop-down menu, either EC Shell or Remote Shell.
If you selected EC Shell, browse to the location of the script in the Script File field, then click Load Script.
If you selected Remote Shell, type your script in the Script field.
Enter a numeric value in the Timeout field, then select Minutes or Seconds. The default is 60 minutes.
(Optional) Click View System Variables to view the default variables.
Click Next.
(Optional) Specify Additional Variables. You can specify any variable you want. For example, add Alarm_ID$ to add the incident identifier number for easier incident management.
You can use an Update profile to create and update a boot environment.
Expand Plan Management, then click Update Profiles in the Navigation pane.
Click New Profile in the Actions pane.
Provide a name and description for the profile.
Select Script from the Type drop-down menu.
Select an OS channel from the Distribution drop-down menu.
Select Local from the Category drop-down menu.
Choose the options that you want from the View and the Version drop-down menus.
Highlight Local RPMs in the Available Packages / Patches table, click the Apply to all applicable distributions check box.
Click Profile Contents and select an item, then click Create OS Update Profile.
You can use an Update profile to create and update a boot environment.
Click an Oracle Solaris 10 OS global zone in the Asset tree to view the Boot Environment in the center pane.
Click the Boot Environment tab.
Existing boot environments for the OS appear in the center pane.
To create a copy, or clone, of the existing active boot environment, click the Create icon.
The plan for execution that uses the default Boot Environments profile for Oracle Solaris 10 is launched.
Type a unique name for the boot environment and provide a description. The text describes what the boot environment and from what source it was created. Edit the applicable parameters in the Alternate Boot Environment profile, then click Confirm.
When the job finishes, refresh the Boot Environment table to see the new boot environment.
Oracle Solaris Live Upgrade contains a suite of script commands. To create an alternate boot environment with Enterprise Manager Ops Center, use the lucreate command to write one or more Oracle Solaris Live Upgrade scripts, add the scripts to the Local Content library in Enterprise Manager Ops Center, then run an OS Update job and select the ABE options.
When you use Enterprise Manager Ops Center to create the alternate boot environment, the scripts must meet the following requirements:
The script cannot contain parameters.
The alternate boot environment name must be hard-coded into the script itself or otherwise be provided outside of Enterprise Manager Ops Center.
The alternate boot environment name defined in the script must match the alternate boot environment name that you use when you run the update job to create the alternate boot environment.
The script must return 0 on success and non-zero on failure.
For detailed instructions and examples for using the lucreate command to create a boot environment, see Oracle Solaris 10 9/10 Installation Guide: Solaris Live Upgrade and Upgrade Planning available at: http://www.oracle.com/technetwork/indexes/documentation/index.html
Expand Libraries in the Navigation pane.
Click Local Content in the Solaris/Linux OS Updates library.
Click Upload Local Action in the Actions pane.
Type a name for the file.
Enter a brief description of the purpose of the action.
In the Action list, click the Pre-action type of action to run the script on the managed host before job tasks are carried out.
Click the name of the distribution that uses the action in the Distribution list. The Parent field shows the category, based on the type of Action.
Click Browse to locate and select the file.
Click Upload. The file is uploaded to the selected distribution.
To Create a Boot Environment With an OS Update Job
Click New Update OS Job in the Update section of the Actions pane. The New Update OS Job wizard is displayed.
Complete the following Job Information parameters:
Type a job name.
Select Actual Run, which creates the alternate boot environment when you specify in Step 5.
Select the Sequential task execution order.
Select the Target Setting: Use the same Targets for all tasks in the job.
Select a Task Failure Policy:
Complete as much of the job as possible
Stop at failure and notify
Click the Boot Environment Type check box.
Click the Run ABE Pre-action Script check box.
(Optional) To add tasks to the job, click the Add Task icon. To edit, click the Profile and Policy fields. Click Next.
Type the name of the alternate boot environment, as defined in the script. Select a script, then click Next.
(Optional) Complete the Boot Environment Workflow, then click Next.
To synchronize the alternate boot environment with the current boot environment before the alternate boot environment is mounted, click the Sync ABE check box.
To edit the description to describe the state of the Boot Environment, click Modify Current BE, and add text to the Description field.
To edit the description to describe the state of the alternate boot environment, click Modify Alternate BE, and add text to the Description field.
To switch boot environments after update, click the Activate and Reboot ABE check box.
Schedule the job, then click Next.
Run Now starts the job immediately after you click Finish in the Job Summary.
Start Date enables you to select a date and time to start the job.
On a recurring schedule enables you to run the same job on a monthly or daily scheduled time.
Review the Job Summary, then click Finish to run the job as scheduled in the previous step.
When the job completes, the alternate boot environment is created and associated with the OS. To verify that the alternate boot environment is created, click the OS in the Assets pane. The Boot Environments tab appears in the center pane. Click the Boot Environments tab to display the new boot environment, as specified in the Live Upgrade script. An OS can have several associated alternate boot environments.
Note:
The Boot Environments tab is only displayed if there is at least one alternate boot environment associated with the OS.You can synchronize, or sync, an active Oracle Solaris 10 global zone boot environment with an inactive boot environment on the same system. Synchronizing boot environments makes the inactive boot environment the same as the currently running boot environment.
For instructions in performing actions or to learn more about the role of this feature, go to one of the following resources.
For end-to-end examples, see the How To library at http://www.oracle.com/pls/topic/lookup?ctx=oc121&id=howto
See Operating System Updates for information about patching, or updating, your operating systems.
See Oracle Solaris Zones for information about zones and how you can use Oracle Enterprise Manager Ops Center to efficiently manage all phases of zones lifecycle.
See Monitoring Rules and Policies for information on how monitoring rules and policies work in the software.
For in-depth information about these products, see the following Oracle documentation:
Oracle Linux at http://www.oracle.com/us/technologies/linux/index.html
Oracle Solaris 11 at http://www.oracle.com/technetwork/documentation/solaris-11-192991.html
Oracle Solaris 10 at http://www.oracle.com/technetwork/documentation/solaris-10-192992.html
Oracle Solaris 8 and 9 at http://www.oracle.com/technetwork/documentation/legacy-solaris-192993.html
For more information about JET resources and documentation, see Solaris 10 10/09 Installation Guide: Custom JumpStart and Advanced Installations available at http://www.oracle.com/technetwork/indexes/documentation/index.html
|
 Copyright © 2007, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
