Writer instructions | |
|---|---|
Page title | For most spaces, this page must be titled Space announcements. For spaces with localized content, this page must be titled Space announcements l10n. |
Purpose | Provide an announcement banner on every page of your space. |
Location | Move this page outside of your home branch. |
Guidelines | |
Solaris Zone (ZONE)
The ZONE application class, along with the POOL application class, supports the Solaris virtualization feature called Solaris Containers. Solaris Containers are composed of Solaris Zones, which allows the user to create and run one or more isolated virtual environments on a single physical server running as completely independent systems.
The ZONE application class enables you to view configuration data for a non-global zone in a global zone, projects in a global or non-global zone, and global zone CPU consumption metrics for Solaris Zones.
The global zone is the original instance of the Solaris operating system, and is used mainly for system administration activities. The non-global zones are created and managed from the global zone only. The global zone uses the DCM collection method along with the Perform Collector to gather information for application classes and to control the poll time and status, and to monitor the collection process.
This application class enables you to monitor the resident set size (RSS) of a zone. It displays the statistics requested by you such as the virtual memory size and the paging statistics for the zone.
A separate instance is created for each zone that reports data for a set of parameters. Solaris non-global zones are completely isolated from each other and are unaware of any of the other non-global zones configured on the server. The global zone is the parent zone that keeps track of the non-global zones.
The non-global zones use the XPC based collection mechanism in addition to the existing PSL collection mechanism to gather information for application classes. A stand-alone executable (PUKSERVER.XPC) communicates with the BMC PATROL Agent to fetch the non-global zone statistics.
InfoBox Information
For information on how to access an application class InfoBox, refer to Accessing-KM-Commands-and-InfoBoxes.
Item | Definition |
|---|---|
History Retention | The length of time history is retained |
Worst parameter | The name of the application parameter that is having the most problems; if more than one parameter is in a warning or an alarm state, the parameter with the most severe problems is shown |
Default username | The default PATROL user name, if any |
Application class | The name of the object class |
State | The current state of the object |
Icon type | The type of icon selected (computer, application, container, parameter) |
Zone Name | The name of the zone |
Zone ID | The unique identifier of the zone |
UNIX KM Version | The version number for the installed PATROL KM for UNIX |
Zone Node | The name of the node of the zone |
RSS Cap | The RSS cap that has been set for the zone |
CPU Cap | The limit that has been set for CPU utilization by the non-global zone |
UNIX KM Version | Displays the version number for the installed PATROL KM for UNIX |
Attributes (parameters)
The following attributes are available for this monitor type: