IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Prepare for installation > Linux or UNIX installation considerations
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Install into Solaris zones
Big local zones share no resources with other zones, so there are no limitations on installing into a Big Local zone. For local zones that share resources, there are the following limitations:
- Anything installed outside of $CandleHome must:
- Be installed in the global zone, OR
- Grant local zone write access to the global zone directory tree
- Any devices used by an agent to obtain statistics must be linked to the Local zone.
- During installation of the Tivoli Enterprise Monitoring Server, the GSKit library can be installed from an alternate directory within the local zone. To accomplish this, edit the ms.ini file for the monitoring server, and add the extra library path to the LD_LIBRARY_PATH concatenation.
GSKit, the Global Security Toolkit, provides SSL (Secure Sockets Layer) processing within protocols such as SPIPE and HTTPS.
The following sections describe the types of zones and the installation possibilities for each.
Global Zone
The main administration zone. Both local and remote installation is possible. GSKit installs into the standard location for Solaris, and the links are created in the standard location for Solaris.
Big Local Zone
A local zone with no shared file system resources. Local and remote installation is possible. GSKit installs into the standard location for Solaris, and the links are created in the standard location for Solaris. These locations are local to this zone and not shared with any other zone.
Small Local Zone
A local zone with some shared file system resources. Local and remote installation is possible if /opt is not a shared resource. GSKit installs into the standard location for Solaris, but the links are created in the new default location of $CANDLEHOME/gsklinks. These locations are local to this zone and not shared with any other zone.
Default Small Local Zone
A local zone with the default set of shared file system resources. This is a Small Local Zone with /sbin /lib /usr and /export directories shared with global zone. These directories are read-only file systems in local zone. Local and remote installation is possible. GSKit installs into the standard location for Solaris, but the links are created in the new default location of $CANDLEHOME/gsklinks. These locations are local to this zone and not shared with any other zone.
Small Local Zone with /opt directory shared
Local and remote installation is not possible. Tivoli Monitoring installation always requires read-write access to the /opt directory. This is not only a GSKit issue. Even if CANDLEHOME is specified as the nondefault directory, read-write access to /opt/IBM/ITM/tmaitm6/links is still needed.
In all supported Small Local Zone configurations, the Tivoli monitoring interactive command-line installation prompts you for the parent directory where the links will be created. For example, if you enter /tmp for the directory, the links will be created in the /tmp/usr/lib and /tmp/usr/bin directories. The default directory for this prompt is $CANDLEHOME/gsklinks. During remote installation, the default directory is always used.
It is very difficult to predict all the possible shared-resource policies for small local zones and the possible side effects. It is the responsibility of the system administrator to create these policies without causing unintentional side effects between different zones and software installed.
Parent topic:
Linux or UNIX installation considerations