To install and run the provisioning system, you must configure your systems as described in the following sections.
A Solaris system that is running the Master Server requires the following /etc/system settings.
If you are using the Solaris 9 or Solaris 10 OS, you cannot change the values for shmsys:shminfo_shmmin and shmsys:shminfo_shmseg. If you are using the Solaris 10 OS, you cannot change the values for shmsys:shminfo_shmmax, shmsys:shminfo_shmmni, semsys:seminfo_semmns, and semsys:seminfo_semvmx.
The default values for these settings are acceptable. All values specified in the Minimum Value column refer to megabytes (MBs).
For more instructions to change the /etc/system settings, see Solaris Tunable Parameters Reference Manual.
In the Solaris 10 environment, the /etc/system settings are replaced by resource controls in the context of the user who owns the installation. The following table defines the minimum values:
Table 2–3 Solaris 10 Resource Controls Settings
Variable |
Minimum Value |
---|---|
project.max-shm-memory |
512 |
project.max-sem-ids |
32 |
process.max-sem-nsems |
17 |
Determine the project ID.
$ id -p |
Verify the current values of project.max-shm-memory, project.max-sem-ids, and process.max-sem-nsems.
# prctl -P -n project.max-shm-memory -i project ID-of-sps-owner # prctl -P -n project.max-sem-ids -i project ID-of-sps-owner # prctl -P -n process.max-sem-nsems -i process $$ |
Where ID-of-sps-owner refers to the owner of the provisioning system project. You can determine the owner of the project by checking the /etc/projects file.
Set resource controls.
If the current values do not meet the minimum settings required, you can use either the prctl command or the projmod command. Changes made with the prctl command are good only until system reboot. The projmod command should be used to make changes that persist across reboot.
Using the prctl command:
# prctl -n project.max-shm-memory -v 536870912 -r -i project ID-of-sps-owner # prctl -n project.max-sem-ids -v 32 -r -i project ID-of-sps-owner # prctl -n process.max-sem-nsems -v 17 -r -i process $$ |
Using the projmod command:
# projmod -a -K "project.max-shm-memory=(priv,512mb,deny)" default # projmod -a -K "project.max-sem-ids=(priv,32,deny)" default # projmod -a -K "process.max-sem-nsems=(priv,17,deny)" default |
The bc command must be in the user's path when you install the Sun N1 Service Provisioning System. Without the bc command, the installation exits and requests that bc be installed. Install the bc-1.06-5.rpm package or a later version of the package.
When you install the Sun N1 Service Provisioning System on an NFS mounted directory on a SUSE Linux 8 server and you want to use SSH or SSL for secure connections, configure the NFS client with nolocks or the NFS server to allow locks. If neither the NFS client nor the NFS server is configured properly, the Sun N1 Service Provisioning System application will not start.
The Linux Master Server installation program checks the following system parameters and exits with an error if the minimum values are not met.
Table 2–4 Linux Master Server System Settings (32–bit, 64–bit)
System Parameter |
Minimum Value |
shmall in /proc/sys/kernel/shmall |
536870912 (512Mb) |
shmmax in /proc/sys/kernel/shmmax |
536870912 (512Mb) |
Additionally, for the Linux 64–bit platform the semaphore settings should be changed in the /proc/sys/kernel/sem file to the following values:
4000 512000 512 4096 |
These numbers equate to the following four values:
SEMMSL – number of semaphores in a semaphore set
SEMMNS – number of semaphores in the system
SEMOPM – number of operations per semop call
SEMMNI – number of semaphore identifiers