See Problem Management. See Monitoring Profiles and Rules for detailed information about setting monitoring actions. The Charts tab displays the CPU, memory and network utilization of the global zone. The data is collected in five-minute intervals and is displayed graphically. The utilization data is provided for different time intervals. See About Charts for more information about reading charts. The utilization data can be viewed in the following ways:. Network utilization — The chart displays the total utilization for the all the zones including the global zone.
Network usage is not available for each zone. Memory utilization — The memory utilization is the physical, virtual, and locked memory in use by each zone. File System Utilization —. The file system lists the root file system and other file systems corresponding to the zone paths in the global zone.
You can select a file system and display the utilization rate for a historical period. The Terminal tab give you access to the console for a zone. Click the Enable the Console Connection icon to invoke the zlogin to the zone. Log into the zone using the zone user name and password. The zone console exists until you log out of Enterprise Manager Ops Center, click the Disable the Console Connection icon, or the global zone is shut down.
You can click the Undock the Console icon to undock the console session from the Enterprise Manager Ops Center, making it available separately for your use. The Jobs tab lists the current and completed jobs for the global zone. See Job Management for more information about managing jobs. The Configuration tab lists the access points for the global zone.
Access points are the resources associated with the operating system and are created as a result of discovery or when the agent starts up. This tab lists the Proxy Controller that connects the global zone to the Enterprise Controller. It also shows the status of the connection and the protocol used for the connection. You have option to unmanage or delete the discovered resources. When you select a non-global zone in the Assets tree, Enterprise Manager Ops Center provides the following tabs in the center pane :.
The Console tab gives you access to the console of a zons. Log into the zone using the zone username and password. For a greenfield zone, the Network tab lists all the networks that are assigned to the zone. You have the option to connect a network to a zone in the shutdown state and disconnect networks from a zone. The associated IPMP groups are also listed for the zone. This information is not available for brownfield zones. For a greenfield zone, the Storage tab lists the root file system, the default file system of the zone.
It also lists other file systems that were added to the zone. You cannot edit the read and write access to the root file system.
The Storage tab also displays the virtual disks that make up the zpool, which is created when you create a zone. The zpool consists of the virtual disks and LUNs used for storage. File systems are implemented as ZFS file systems and mapped to the storage. From the Storage tab, you can add a file system to the zone and change an existing file system, delete a file system from the zone, and add more storage to a zone. The Problems tab lists out the unresolved problems that are reported for the zones and a graphical representation of the problem composition.
See Problem Management for more detailed information. For a zone, the following utilization data are displayed:. The per-zone utilization data is collected by the extended accounting in the global zone.
File System Utilization — Whenever you create a zone, a zpool is created with the zone guest image name. The file system lists the root file system and other file systems that are added to the zone. The OS Details page lists all the file systems and the current utilization rate. The Jobs tab lists the current and completed jobs for the zone. See Job Management about managing jobs.
The Configuration tab displays the information about the zone's configuration, depending on whether the zone is a greenfield zone or a brownfield zone. For brownfield zones, the Configuration tab shows the the access points for the zone. This tab lists the Proxy Controller that connects the non-global zone to the Enterprise Controller.
To convert a brownfield zone to a greenfield zone, adopt the brownfield zone. When you adopt a zone, you get access to the zone configuration data and greater ability to manage and monitor the zone. During the adoption process, the zone is shutdown and then rebooted after adoption. A new zpool is created for the zone and the existing file system is copied to the zpool. You cannot add or delete a file system during the adoption process.
Select a local library or a NAS library to save the zone's metadata. The metadata is the zone's configuration, the virtual image. If you want to allow the zone to be migrated, choose a NAS library. Click Next. Select a library from the list of libraries that are associated with the global zone. This library will store the data from the zone's operation. You can select the following types of library from the list. If you have the option to change the size, provide sufficient storage space to accommodate any new file systems added to the zone.
Local Library — It is the global zone's local storage disks. Select a local library and provide the virtual disk size. However, if you choose a local library for zone storage, the zone cannot be migrated. Local Device — These are disks that are connected to the system that is running the global zone. Select a disk from the list. The size of the disks cannot be changed. Define the size of the virtual disk.
You can modify the disk name. Fibre Channel — Select a Fibre Channel library from the list. Select a LUN from the list. You cannot modify the LUN size or create a new virtual disk image.
The Migrate Zone option is enabled only if the zone metadata and added storage are on the shared storage. You can modify the configuration of a zone to change the CPU or memory resources, scheduler, and the identity of the zone. When you modify the CPU and memory configuration, you must reboot the zone for the changes to take effect. You can also set the relative importance of the zone compared to other zones when contending for CPUs. Memory Caps — You can specify caps on various aspects of memory used by the zone.
You can modify the caps set for physical, swap, and locked memory. For a dedicated CPU model, you can set the following scheduler attributes:. Select the zone in the Assets section of the Navigation pane. The Dashboard of the zone is displayed in the center pane.
Select the Configuration tab in the center pane. The current configuration of the zone is displayed. Click Edit Configuration in the Actions pane. The Edit Zone Configuration window is displayed.
Edit the following zone attributs, as required:. You can add storage only to greenfield zones. The storage is added to the zpool that is created for the zone. You cannot delete storage from the zpool. Click Add Storage in the Actions pane.
The Add Storage to the Zone window is displayed. Select a library from the list. For a local and NAS library, enter a virtual disk name and specify the size of the disk. For local device library, select a disk from the Virtual Disk Name list. You cannot specify the size of the disk or the LUNs. The Additional Storage Specified shows the new total storage space.. You can associate one or more libraries with a global zone. The libraries are available to all non-global zones in the hierarchy of the global zone.
Select the global zone from the Assets section of the Navigation pane. The Dashboard of the global zone is displayed. Click Associate Libraries in the Actions pane. The Associate Library window lists the libraries that are not associated with the global zone. Select the global zone from the Assets section in the Navigation pane. The Dashboard of the selected global zone is displayed in the center pane. Select Libraries tab from the center pane.
The associated libraries with the global zone are listed. This section describes how to connect, modify, and disconnect networks from zones. You can create networks associated with an IPMP group.
Modifying the Network Interface of a Global Zone. Select the Networks tab in the center pane. The Networks tab lists the networks that are assigned to the global zone. Click the Modify Physical Connectivity icon. In Enterprise Manager Ops Center, networks are managed objects. You can identify and assign one or more networks to the global zone. These networks can then be used by the global zone's non-global zones.
When you assign a network to a global zone, you must define the mode of the network, either Shared IP or Exclusive IP:. In Shared IP mode, the network interface is used by more than one zone. You define the network interface when you you assign the global zone to the network. In Exclusive IP mode, the network interface is dedicated to the zone. An exclusive network must be declared for the global zone when you assign network to the global zone. Then you configure the IP configuration for the non-global zone.
A network that is assigned as shared on a global zone can be assigned as exclusive on another global zone. For a global zone, a network has only one mode. For non-global zones, a network that is used in a shared mode for one zone cannot be used in exclusive mode for another zone.
Select Assign Network in the Actions pane. The Assign Networks to Global Zone wizard is displayed. Select the network that you want to associate with the global zone from the list of networks that are not assigned to the global zone.
To assign more networks to the global zone, click the Add icon. Select the address allocation method. If you selected an IPMP group, address allocation is not required. Click Connect Network in the Actions pane or select the Networks tab in the center pane and click the Connect Network icon. The Connect Networks to Zone window is displayed. Select the networks that you want to connect to the zone. All networks assigned to the global zone with the same IP mode and not yet connected to the zone are listed.
Click the Add icon. You can assign an exclusive IP zone multiple times to a network. Click Finish to submit the job that assigns the network to the global zone..
When you unbind a network from a global zone, the global zone's non-global zones are also disconnected from the network. Select the global zone from the Assets tree in the Navigation pane. The boundaries can be changed dynamically to adapt to changing processing requirements of the applications running in the Zone.
The global zone encompasses the entire system and is comparable to a normal Solaris OS instance. It has access to the physical hardware and can see and control all processes. The administrator of the global zone can control the system as a whole. The global zone always exists, even when no other zones are configured. Inside the global zone are local zones.
These zones are isolated from the physical hardware characteristics of the machine by the virtual platform layer. This layer provides the zones with a virtual network interface, one or more file systems and a virtual console. There are two daemon processes associated with zones, zoneadmd and zsched. The zoneadmd daemon starts when a zone needs to be managed. An instance of zoneadmd will be started for each zone, so it is not uncommon to have multiple instances of this daemon running on a single server.
It is started automatically by SMF and is also shut down automatically when no longer required. The zoneadmd daemon carries out the following actions:.
The zsched process is started by zoneadmd and exists for each active zone a zone is said to be active when in the ready, running , or shutting down state. The job of zsched is to keep track of kernel threads running within the zone. It is also known as the zone scheduler. Before a zone can be installed and booted it has to be created and configured. This section deals with the initial configuration of a zone and describes the zone components.
A zone is configured using the zonecfg command. The zonecfg command is also used to verify that the resources and properties that are specified during configuration are valid for use on a Solaris system. The zonecfg command is used to configure a zone.
It can run interactively, on the command-line, or using a command-file. A command-file is created by using the export subcommand of zonecfg. When you enter zonecfg in interactive mode, the prompt changes to show that you are in a zonecfg session.
If you are configuring a zone called apps , then the prompt changes as follows:. This is known as the global scope of zonecfg.
When you configure a specific resource, the prompt changes to include the resource being configured. The command scope also changes so that you are limited to entering commands relevant to the current scope. You have to enter an end command to return to the global scope.
Print the configuration to stdout , or to a specified file name, which can be used as a command file. In the global scope, this command takes you to the specified resource scope. In the resource scope, it adds the specified property to the resource type. This is applicable only in the global scope and selects the resource of the specified type.
The scope changes to the resource, but you have to enter sufficient property name-value pairs to uniquely identify the required resource. In the global scope, remove the specified resource type. You have to enter sufficient property name-value pairs to uniquely identify the required resource. This is only available in the resource scope and ends the current resource specification.
This is only available in the resource scope. It ends the resource specification and returns to the global scope. Any partially specified resources are discarded. Destroy the specified configuration. You need to use the -F option to force deletion with this option. Display information about the current configuration. If a resource type is specified, then display information about the resource type.
Verify the current configuration to ensure all resources have the required properties specified. Commit the current configuration from memory to disk. A configuration must be committed before it can be used by the zoneadm command, described later in this chapter. Exit the zonecfg session. You can use the -F option with this subcommand to force the command to execute. The zonename identifies the zone and must be unique. It can't be longer than 64 characters. It's case-sensitive and must begin with an alpha-numeric character.
The name global and all names beginning with SUNW are reserved and not allowed. To restrict visibility to non-privileged users in the global zone, the permissions on the zonepath directory should be set to Each zone can mount file systems. This resource specifies the path to the file system mount point.
This type specifies directories that contain software packages that are shared with the global zone, or inherited from the global zone. The non-global zone only inherits read-only access. The packages associated with these directories are inherited in a read-only loopback file system mount by the non-global zone.
Each zone can have network interfaces that are plumbed when the zone transitions from the installed state to the ready state.
Network interfaces are implemented as virtual interfaces. Each zone can have devices that are configured when the zone transitions from the installed state to the ready state. This type is used for zone-wide resource controls. The controls are enabled when the zone transitions from the installed state to the ready state.
The zone-wide resource controls implemented in Solaris 10 are zone. Some of the resource types described in Table The following list describes the properties and the parameters, along with examples of usage :. The following code gives an example of how these properties are used.
The bold type indicates the keystrokes entered at the keyboard. The file system is of type ufs and a couple of mount options have been added too. This specifies the directory that is to be loopback mounted from the global zone. This specifies the setup of the network interface for the zone.
The following code example specifies an IP address of Exclusive IP. Shared IP In this case zone uses a shared interface which is already plumbed and being used in the global zone. Device We can also directly assign a physical device like disk to a non-global disk. Comments In case you want to add some comments like function of the non-global zone or anything else for that matter. Other Other settings like scheduling class of the CPU in the non-global zone can also be configured from the global zone.
Skip to primary navigation Skip to main content Skip to primary sidebar Skip to footer navigation. To reboot a zone : zoneadm -z reboot To halt a zone : zoneadm -z zone halt To uninstalling a zone : zoneadm -z zone uninstall -F To delete an uninstalled zone : zonecfg -z zone delete -F Get all configuration info : zonecfg -z zone info login into a zone in safe mode : zlogin -S zone prstat on all zones : prstat -Z prstat on a single zone : prstat -z zone.
0コメント