If ServerView Resource Orchestrator is running, stop it by executing the following command:
[Windows]
<ServerView Resource Orchestrator installation directory>\SVROR\Manager\bin\rcxmgrctlstop |
[Linux]
/opt/FJSVrcvmr/bin/rcxmgrctl stop |
If a Terminal Server has been installed, change the Terminal Services to Install mode by executing the following command:
CHANGE USER /INSTALL |
The system parameters must be tuned.
Tuning values for system parameters
Refer to the following tables for information on the system parameters that require tuning and their values:
Semaphores
For the semaphore settings, specify each parameter value using the following format:
kernel.sem = para1 para2 para3 para4
Parameter | Description | Value | Type |
|---|---|---|---|
para1 | Maximum number of semaphores per semaphore identifier | 1 | Maximum |
para2 | Number of semaphores for the entire system | 2 | Addition |
para3 | Maximum number of operators per semaphore call | 1 | Maximum |
para4 | Number of semaphore operators for the entire system | 2 | Addition |
Message queues
Parameter | Description | Value | Type |
|---|---|---|---|
kernel.msgmnb | Maximum number of messages that can be held in a single message queue | 106496 | Maximum |
kernel.msgmni | Maximum number of message queue IDs | 1024 | Addition |
Settings dependent on the parameter type
Set the parameters as below, depending on the "Type" shown in the table above.
If the Type is "Maximum":
If the value that has already been set (either the initial value or the previous setting) is equal to or greater than the value in the table above, there is no need to change the parameter value. If the current value is smaller than the value in the table, change the parameter to the value in the table.
If the Type is "Addition":
Add the value in the table above to the value that has already been set (either the initial value or the previous setting). Check the upper limit for the system before setting the parameter to the result of the addition, and if the result of the addition is greater than the upper limit for the system, then set the parameter to the upper limit for the system.
Refer to the Linux manuals and other documents for details.
Tuning procedure
Use the following procedure to perform tuning tasks:
Use the following command to check the current settings for the system parameters:
# /sbin/sysctl -a
Example
# /sbin/sysctl -a . . . (omitted) . . . kernel.sem = 250 32000 32 128 . . . kernel.msgmnb = 65536 kernel.msgmni = 16 . . . (omitted) . . .
Refer to "Tuning values for system parameters", and compare the current settings to the values in the tables above. Calculate an appropriate value for each parameter, taking into account the parameter type ("Maximum" or "Addition").
Edit the /etc/sysctl.conf file. Edit the file as shown in the following example:
Example
kernel.sem = 250 32002 32 130 kernel.msgmnb = 106496 kernel.msgmni = 1040
Use the following command to check that the changes have been applied to the /etc/sysctl.conf file:
# /bin/cat /etc/sysctl.conf
To enable the settings in Step 4 above, perform either of the following methods:
Apply the settings by rebooting the system.
# /sbin/shutdown -r now
Apply the settings by executing the "/sbin/sysctl -p" command.
# /sbin/sysctl -p /etc/sysctl.conf (*1)
*1: There is no need to reboot the system if this command is used.
The output of the following command can be used to check that the changes made to the system parameter settings have been applied:
# /sbin/sysctl -a
Example
# /sbin/sysctl -a . . . (omitted) kernel.sem = 250 32002 32 130 . . . kernel.msgmnb = 106496 kernel.msgmni = 1040 . . . (omitted) . . .
This product outputs logs to syslog. In order to output logs to syslog, check the following settings and adjust the settings if necessary.
Settings for syslog.conf or rsyslog.conf
It is recommended that the default settings for the operating system be used.
Systemwalker Software Configuration Manager outputs logs using local0 (facility). The following settings are required. If the following settings are missing even though syslog.conf or rsyslog.conf has already been edited, add the following settings to syslog.conf or rsyslog.conf.
Refer to the syslog.conf manuals for information on how to edit the syslog.conf file. Refer to the rsyslog.conf manuals for information on how to edit the rsyslog.conf file.
"/etc/syslog.conf" (for RHEL5)
Selector field (facility.priority) | Action field |
|---|---|
local0.info | /var/log/messages |
"/etc/rsyslog.conf" (for RHEL6)
<Rules>
Selector field (facility.priority) | Action field |
|---|---|
local0.info | /var/log/messages |
Point
There is no need to make modifications if "*.info" has been set for the selector field (facility.priority).
Enabling remote reception for syslog
Remote reception must be enabled in order to output logs to the syslog on the admin server from Systemwalker Software Configuration Manager.
Configure settings so that syslog automatically starts in remote reception mode when the operating system starts.
Edit the following files:
"/etc/sysconfig/syslog" (for RHEL5)
Add the "-r" option to SYSLOGD_OPTIONS.
Example:
SYSLOGD_OPTIONS="-r -m 0" |
"/etc/rsyslog.conf" (for RHEL6)
Enable $UDPServerRun.
$ModLoad imudp.so $UDPServerRun 514 |
Note that the port used for remote reception is "514/udp". Refer to "Appendix A Port Number List" for a list of ports used by Systemwalker Software Configuration Manager.
Restarting syslogd or rsyslogd
If the settings have been changed in "Settings for syslog.conf or rsyslog.conf" or "Enabling remote reception for syslog", restart syslogd or rsyslogd for the changes to take effect.
Refer to the syslogd manuals for information on syslogd. Refer to the rsyslogd manuals for information on rsyslogd.
"syslogd" (for RHEL5)
>/etc/init.d/syslog stop >/etc/init.d/syslog start |
"rsyslogd" (for RHEL6)
>/etc/init.d/rsyslog stop >/etc/init.d/rsyslog start |
