A.5.1 CF Configuration

When the resource database is used

The table below shows the kernel parameter values that are required in the CF configuration when the resource database is used.

The kernel parameter values in /etc/system are automatically changed by the installer. Be sure to return the settings in /etc/system to their original state when you uninstall the package.

Note

For system expansion, if you increase the number of nodes and logical disks, you need to re-estimate the resources and restart each node in the cluster system. If you want to add nodes or logical disks to a cluster system after it is configured, it is necessary to set a kernel parameter in advance considering the number of the nodes and logical disks.

Kernel parameter	Characteristics	Value	Parameter description
semsys:seminfo_semmni	Addition	20	Maximum number of semaphore identifiers.
shmsys:shminfo_shmmax	Maximum value	4194304 *	Maximum size of the System V shared memory segment that can be created.
shmsys:shminfo_shmmni	Addition	30	Maximum number of the shared memory segments that can be created for the entire system.

4194304 is the minimum value that is required when the resource database is used.

You may need to change the value of shmsys:shminfo_shmmax depending on the number of cluster system resources.

Estimate the number of cluster system resources according to the following equation and change the value.

If the required value for the database is smaller than the default value (8388608), use the default value.

Number of resources = (a) + (b)

(a) Number of disks in shared system devices x (number of shared nodes + 1) x 2

(b) Total number of local disks (number of local disks in all cluster configuration nodes)

Value required for resource database = 1048576 + 2776 x number of resources

If the value calculated above is larger than the installation default value (8388608):
shmsys:shminfo_shmmax = Value required for resource database
If the value calculated above is smaller than the installation default value (8388608):
You do not need edit shmsys:shminfo_shmmax .
(The installation default value is used.)

RCI monitoring agent setup

When you set up asynchronous RCI monitoring, you must specify the timeout interval (kernel parameter) in /etc/system for monitoring via SCF/RCI. Kernel parameters vary depending on the server type. Then check your server type so you can set the appropriate timeout interval.

Note

This setting is not required in the following cases:

SPARC Enterprise M3000, M4000, M5000, M8000, and M9000 provided by companies other than Fujitsu in Japan
SPARC Enterprise M3000, M4000, M5000, M8000, and M9000 with logos of both Fujitsu and Oracle provided in other than Japan

Below table shows the server types that require setting of the monitoring timeout interval.

Server type	Model	Kernel parameter (driver name: scf_rdctrl_sense_wait)
SPARC Enterprise	M3000	scfd:scf_rdctrl_sense_wait
	M4000
	M5000
	M8000
	M9000
PRIMEPOWER	800	FJSVscf2:scf_rdctrl_sense_wait
	1000
	2000
	900	FJSVscf3:scf_rdctrl_sense_wait
	1500
	2500

Method for Calculating Monitoring Timeout Intervals
Calculate monitoring timeout intervals as follows:
- Up to 2 domains: 2 seconds
- 3 or more domains: 1 second + (0.5 x number of domains)
```
    Example:
     - 3 domains: 2.5 seconds
     - 4 domains: 3.0 seconds
```
Note
Calculate timeout intervals based on the number of domains in the server that contains the largest number of domains in the RCI network.
Method for Setting Timeout Intervals in /etc/system
Before setting up the initial cluster configuration, modify /etc/system for all nodes according to below procedure.
1. Make a backup of /etc/system.
  Example:
  Make a copy of /etc/system and save it under the filename /etc/system.org.
  # cp /etc/system /etc/system.org
2. Set the monitoring timeout interval in /etc/system.
  As the monitoring timeout interval is specified in microseconds, you have to multiply the seconds calculated in above item "a." by 1,000,000 for this setting.
  set driver name: scf_rdctrl_sense_wait = monitoring timeout interval [microseconds]
  Example:
  Setting a 2-second monitoring timeout interval for a SPARC Enterprise server with 2 domains.
  set scfd:scf_rdctrl_sense_wait = 2000000
3. Restart the node.
  Example:
  # /usr/sbin/shutdown -y -g0 -i6