Hitachi

JP1 Version 12 for UNIX Systems JP1/Performance Management - Agent Option for Platform Description, User's Guide and Reference


2.3.15 Data that can be collected with virtualized systems that use zones

Organization of this subsection

(1) Zone functionality

Unlike the logical resource partitioning functions implemented in other OSs (for example, LPAR in AIX and VMware), the zone functionality installed in Solaris provides an application workspace. Accordingly, the positioning of a virtualized system based on zones slightly differs from that of virtualized systems on other OSs. Despite the difference, however, zones are used like similar functions in other OSs (for example, for the implementation of multiple OSs in a single system).

(2) Structure of the zone functionality

There are two types of zones: a global zone and a non-global zone. The global zone has almost the same meaning as the entire system, whereas a non-global zone represents an application workspace provided by the system.

In an ordinary virtualized system, resources are completely separated from the system when viewed by the user. In a virtualized system based on the zone functionality, resources other than disks are basically owned by the global zone.

PFM - Agent for Platform can collect information about the global zone and non-global zones. Some information cannot be collected using records in non-global zones. For details, see Table 2-10 When PFM - Agent for Platform is installed in the non-global zone in an environment in which zones have been created in 2.3.22(1)(a) Zone environment.

Figure 2‒7: Concept of an ordinary virtualized system and the zone functionality

[Figure]

In a non-global zone, the zone functionality operates by using a single file system as seen from the global zone.

Part of the file system of the global zone is shared in the non-global zone.

In the following example, the entities of sbin and usr under zone a, zone b, and zone c are sbin and usr under /.

Figure 2‒8: Example of a zone configuration

[Figure]

(3) Monitoring processes in the global zone

When PFM - Agent for Platform is running in the global zone, you can set the ALL Zone Collection for Process property to select the zone for which process information is collected. You can set either of the following values for the ALL Zone Collection for Process property.

Yes

Collect process information for the global zone and non-global zones.

No

Collect process information for the global zone.

The ALL Zone Collection for Process property is set to Yes by default.

The following figure shows process information that is collected when PFM - Agent for Platform is running in the global zone.

Figure 2‒9: Process information collected for the global zone

[Figure]

(4) Monitoring processes in a non-global zone

When PFM - Agent for Platform is running in a non-global zone, information only about that non-global zone is collected regardless of the setting of the ALL Zone Collection for Process property. The following figure shows the process information that is collected when PFM - Agent for Platform is running in a non-global zone.

Figure 2‒10: Process information collected for a non-global zone

[Figure]