Top
Systemwalker Service Quality Coordinator User's Guide (Dashboard Edition)
Systemwalker

3.2.1 Before Installation [UNIX]

In order to use the Dashboard Server, you must first tune the system parameters for the common resources that the individual pieces of software will use. The following chart shows the system parameters that need to be tuned and the values for each. In some cases values need to be added to existing (default) values, while in other cases two values are compared and the highest (maximum) of the two is used. (Be sure to check system upper limits when adding values.) The "Type" column in the tables below tells you which method is used for each of the values.

Refer to Solaris and Linux manuals for further details.

For Solaris

The Dashboard Server runs under the following projects:

Tuning values of system parameters
[Shared memory]

Parameters

Description

Value

Type

Privileges

project.max-shm-memory

Maximum size of shared memory segment

108388350

Add

Privilege level

project.max-shm-ids

Maximum number of shared memory identifiers

70

Add

Privilege level

[Semaphore]

Parameters

Description

Value

Type

Privileges

project.max-sem-ids

Number of semaphore identifiers

1468

Add

Privilege level

process.max-sem-nsems

Maximum number of semaphores per semaphore identifier

512

Maximum

Privilege level

process.max-sem-ops

Maximum number of operations at each semaphore call

50

Maximum

Privilege level

[Message queue]

Parameters

Description

Value

Type

Privileges

process.max-msg-qbytes

Maximum number of bytes in queue

65536

Maximum

Privilege level

project.max-msg-ids

Number of message waiting identifiers

529

Add

Privilege level

process.max-msg-messages

Maximum number of messages in message queue

1024

Add

Privilege level


Point

Specify "privileged" in the /etc/project file to set the privilege level.

Tuning procedure

Edit the /etc/project file to tune the system parameters.

Note

Before setting system parameters, first confirm the initial values of the system and the upper limits of the values that can be set. The following is an example of how to check these values:

  1. Use the following command to check the values currently set on the system for the relevant parameters in the above table:

    # projects -l

    Confirmation command execution example:

    # projects -l
    system
    projid : 0
    comment: "System account"
    users : (none)
    groups : (none)
    attribs:
    user.root
    projid : 1
    comment: "root user"
    users : root
    groups : root
    attribs:
    noproject
    projid : 2
    comment: ""
    users : (none)
    groups : (none)
    attribs:
    default
    projid : 3
    comment: "Default project setting"
    users : (none)
    groups : (none)
    attribs: 
    # newtask -p default
    # prctl $$
    process: 1000: sh
    NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT
    process.max-port-events
    privileged 65.5K - deny -
    system 2.15G max deny -
    process.max-msg-messages
    privileged 8.19K - deny -
    system 4.29G max deny -
    system 16.8M max deny -
    *
    

  2. Refer to the "Tuning values of system parameters" table (above), compare the values in the table to the current system parameter values and then calculate the appropriate values, taking into account the type (either maximum or add), for each parameter. Edit the /etc/system file based on the results of these calculations.


Note

  • Put each value on its own line for each project.

  • Make the settings for tuning the parameters for both the system and the superuser.

Checking system parameters

After making the above settings, use the following command to check the settings.

# projects -l

Confirmation command execution example:

# projects -l
system
projid : 0
comment: "System account"
users : (none) 
groups : (none) 
attribs: project.max-msg-ids=(privileged,527,deny)
    <- Check that the project file settings are replicated in "attribs" 
       (Settings have been successfully changed if the values calculated 
in step 2 are shown for each variable) process.max-msg-qbytes=(privileged,162972,deny) process.max-sem-nsems=(privileged,512,deny) process.max-sem-ops=(privileged,50,deny) project.max-sem-ids=(privileged,829,deny) project.max-shm-memory=(privileged,3398861600,deny) user.root projid : 1 comment: "root user" users : root groups : root attribs: project.max-msg-ids=(privileged,527,deny) process.max-msg-qbytes=(privileged,162972,deny) process.max-sem-nsems=(privileged,512,deny) process.max-sem-ops=(privileged,50,deny) project.max-sem-ids=(privileged,829,deny) project.max-shm-memory=(privileged,3398861600,deny) noproject projid : 2 comment: "" users : (none) groups : (none) attribs: default projid : 3 comment: "Default project setting" users : (none) groups : (none) attribs:

For Linux

Tuning values of system parameters
[Shared memory]

Parameters

Description

Value

Type

shmmax

Maximum segment size of shared memory

57413492

Maximum

shmmni

Maximum number of shared memory segments

71

Add

[Semaphore]

Parameters

Description

Value

Type

para1

Maximum number of semaphores per semaphore identifier

512

Maximum

para2

Number of semaphores in the system

6287

Add

para3

Maximum number of operators per semaphore call

50

Maximum

para4

Number of semaphore identifiers in entire system

1468

Add

[Message queue]

Parameters

Description

Value

Type

msgmax

Maximum size of message

16384

Maximum

msgmnb

Maximum value that can be held in one message queue

32768

Maximum

msgmni

Maximum value of message queue ID

527

Add

Tuning procedure

Edit the /etc/sysctl.conf file to tune the system parameters.

  1. Use the following command to check the values currently set on the system for the relevant parameters in the above table:

    #/sbin/sysctl -a

  2. Refer to the "Tuning values of system parameters" table (above), compare the values in the table to the current values and then calculate the appropriate values, taking into account the type (either maximum or add), for each parameter.


  3. Edit /etc/sysctl.conf.

    Tune the system parameters by editing the /etc/sysctl.conf file based on the results calculated in step 2.


  4. Use the following command to confirm that the changes you made to /etc/sysctl.conf were saved in the file:

    #/bin/cat /etc/sysctl.conf

  5. Do one of the following to put the above settings into effect:

    Method 1: Restart system to make the settings effective

    # cd /
    # /sbin/shutdown -r now

    Method 2: Use /sbin/sysctl -p to make the settings effective

    # /sbin/sysctl -p /etc/sysctl.conf

  6. Use the output from the following command to confirm that the changes made to the system parameters were implemented:

    # /sbin/sysctl -a

    Confirmation command execution example:

    # /sbin/sysctl -a
          
          
        (omitted)
          
          
    kernel.sem = 738 54761 60 3898
    kernel.msgmnb = 44237
    - 8 -
    kernel.msgmni = 1911
    kernel.msgmax = 19815
    kernel.shmmni = 4298
    kernel.shmall = 2097152
    kernel.shmmax = 139986287
          
          
        (omitted)