2. Parameter details¶
This chapter describes the details of the parameters configured in EXPRESSCLUSTER.
This chapter covers:
2.1. Parameter settings¶
2.2. Cluster properties¶
In Cluster Properties, you can view and change the cluster's settings.
2.2.1. Info tab¶
You can view the cluster name, and enter or change a comment for this cluster.
Cluster Name
The cluster name is displayed. You cannot change the name here.
Changing the cluster name
click others, and then select Rename the cluster.
A dialog box to rename cluster is displayed.
Naming rules
Only alphanumeric characters, hyphen (-), underscore (_) and space are allowed for names.
Up to 31 characters (31 bytes)
Names cannot start or end with a hyphen (-) or space.
Comment (Within 127 bytes)
You can enter a comment for the cluster. Only alphanumeric characters are allowed.
Language
Select a language for cluster from the following. Set the language (locale) of OS on which the Cluster WebUI runs.
English
Japanese
Chinese
Cluster WebUI and the results of clpstat command are displayed in the language set in the Language settings on the cluster properties.
Note
Run the clpstat command in the environment where the font of the specified language can be displayed. On the console which is connected to a server directly, setting a frame buffer is required. When logging on to the server remotely using ssh, a terminal emulator which can display the specified language may be needed.
2.2.2. Interconnect tab¶
This tab allows you to set up network communication paths between cluster servers.
The Communication paths between servers list displays network communication paths between servers in the cluster.
Add
Adds a communication path. To specify the IP address of the communication path for each server, click a cell in each server's column, and then select or enter the address. If some servers are not connected on the communication path, leave the cells for all the unconnected servers empty.
Remove
Removes a communication path. Select the column of the communication path to remove, and then click Remove to remove the selected path.
Properties
Displays heartbeat properties window. This is only available only when the type is Witness.
Witness heartbeat properties
Target host
Sets the host address of the Witness server to be connected.
Service port
Sets the port number of the Witness server to be connected.
Use SSL
Configures whether or not to use SSL for communicating with the Witness server. When the checkbox is selected, SSL is used, and when the checkbox is not selected, it is not used.
Use OpenSSL for SSL.
To set libraries to be used, go to Cluster Properties -> the Encryption tab -> SSL Library and Crypto Library.
Use Proxy
Configures whether or not to use a proxy for communicating with the Witness server. When the checkbox is selected, the settings of the Proxy tab in the server properties become effective. When the checkbox is not selected, any proxy setting is not used even if the proxy is set in the server properties.
HTTP Timeout
Sets the timeout of receiving HTTP response.
Initialize
Resets the Witness heartbeat properties settings to default values.
Priority
When multiple interconnects are configured, the communication path with the smallest number in the Priority column is used preferentially for the internal communication among cluster servers. To change the priority, change the order of selected rows with the arrows.
It is recommended to specify a higher priority for the interconnect communication path than any other paths.
Note
Priority is used to decide on the priority of communication routes used for internal communication between the servers in the cluster. Heartbeat between the servers in the cluster is implemented on all communication routes that are set up for heartbeat, regardless of Priority.
Type
Select the path to be used for heartbeat from Kernel Mode, User Mode, DISK, Witness, or Mirror Communication Only
Kernel mode performs alive monitoring by using kernel mode LAN heartbeat resources.
User Mode performs alive monitoring by using LAN heartbeat resources.
DISK performs alive monitoring by using disk heartbeat resources.
Witness performs alive monitoring by using Witness heartbeat resources.
For details about the heartbeat resources, see "5. Heartbeat resources details"in this guide.
MDC
To use a communication path as the mirror disk connect, click MDC and then select Mirror Connect Disk.
The contents to be entered differ by type.
Kernel Mode, User Mode, Mirror Communication OnlySelect Mirror Disk Connect from the combo box.When the mirror disk connect is not used, select Do Not Use.Note
A combination of IPv4 and IPv6 is not allowed for the IP addresses that are used for mirror disk connects. Specify IP addresses in either IPv4 only or IPv6 only for all mirror disk connects.
DISK, WitnessThe mirror disk connect cannot be used.MDC automatically changes to Do Not Use and can no longer be edited.
Server column
Entry differs depending on the type.
Kernel Mode, User Mode, Mirror Communication OnlyEnter IP address. Set blank to the not used communication path. DISKEnter disk device. Set blank when not using DISK device. WitnessSelect Use or Do Not Use.Note
More than one IP addresses which belong to the same network address cannot exist in a single server. And also, inclusive relation cannot exist like the following relation.IP address:10.1.1.10, subnet mask:255.255.0.0IP address:10.1.2.10, subnet mask:255.255.255.0
Server down notification
When a server stops successfully (including a shutdown or reboot), the server is reported to be down to other servers in the cluster. You can perform failovers faster by reporting this in advance.
When there is a failure to deactivate groups when a server stops (including a shutdown or reboot), or when other abnormalities occur, other servers are not notified of the server that went down regardless of the server down notification settings.
When Follow the default dependence is selected:A server going down is reported. When Follow the default dependence is not selected:A server going down is not reported.Note
Do not use server down notification when using a hybrid disk resource.
Click Detailed Settings to configure the details of server reset notification.
Note
Making the settings effective requires the following:The check box of server down notification is checked.Kernel mode LAN heartbeat resources are set.Using a kernel newly supported by internal version 4.3.0-1 or later.
Server Reset Notification
This notification by the server means informing other servers of its stop due to Keepalive Reset or Keepalive Panic.
If the check box is checked:With the notification, its source server is regarded as down. If the check box is not checked:No reaction happens even with the notification.
Execute Server Alive Check
If you enable this option, a server which received the server reset notification checks whether the notification source server is down before the failover.
If the check box is checked:Whether the server is alive is checked before the failover. If the check box is not checked:Whether the server is alive is not checked before the failover.
Timeout
Specify a value for the timeout of checking whether the server is alive. If the value is larger than that for the heartbeat timeout, the latter timeout value is applied.
Even if the check is not completed by the time of the timeout occurrence, the failover is performed.
Tuning
Displays heartbeat I/F tuning property window.
Heartbeat I/F Tuning Properties
Open/Close Timing
- Only at Start/StopOpens device when a cluster starts and close it when a cluster stops. Performs only reads and writes of device at each heartbeat interval.
- Every Heartbeat IntervalOpens device when a cluster starts, and closes it when a cluster stops. Performs open, reads, writes and close of device at each heartbeat interval.
2.2.3. Fencing tab¶
Set up the network partition (NP) resolution method and the forced stop function.
2.2.3.1. NP Resolution¶
The network partition resolution interface used for EXPRESSCLUSTER is displayed on the NP Resolution List.
Add
Add network partition resolution I/F. Click the Type column cell and select the type of NP resolution (Ping or HTTP). If you select Ping, click the Ping target column cell and set the IP address. Click the cell of each server and set Use or Do Not Use.
Remove
Remove network partition resolution I/F. Select network partition resolution I/F to be removed and click Remove, then the selected network partition resolution I/F is removed.
Properties
Display the Ping NP Properties or the HTTP NP Properties window.
Ping NP Properties
Add Group List
Add group.
The maximum number of registered group is 16.
If two or more IP addresses are registered in one group
With a response from one of the IP addresses, no NP state is considered to have occurred.
With no response from any of the IP addresses, an NP state is considered to have occurred. Then the action selected in Action at NP Occurrence is performed.
If two or more groups are registered
With a response from one of the IP addresses in a group, the group is considered to be normal.
With no response from any of the IP addresses in a group, the group is considered to be abnormal.
With one of the groups abnormal, an NP state is considered to have occurred. Then the action selected in Action at NP Occurrence is performed.
Remove Group List
Remove the selected group.
Add IP Address List
Add IP address to the selected group.
The maximum number of registered IP address is 16.
Maximum 256 IP addresses are able to be registered to a single Ping NP, and 16 kinds of IP addresses can be registered. (The same IP addresses can be used.)
Remove IP Address List
Remove the selected IP address from the list.
Edit
Edit the selected IP address.
Interval
Set the Ping interval.
Timeout
Set the Ping timeout.
Retry Count
Set the retry count.
Initialize
Set the interval, timeout and retry count to the default values. Note that, when an interval and retry count are specified, the following conditional expression must be satisfied.If not satisfied, NP resolution processing cannot be performed normally.Conditional expression) Heartbeat timeout> (Ping NP Interval *Ping NP Retry Count) + Ping NP Timeout
HTTP NP Properties
Use Witness HB Resource SettingsUse the same target host and service port as those of Witness HB which has already been configured. Target HostSets the host address of the Web server to be connected. Request-URISets the request-URI of the Web server to be connected: the target host name followed by a string starting from "/". Service PortSets the port number of the Web server to be connected. Use SSLConfigures whether or not to use SSL for communicating the Web server. When the checkbox is selected, SSL is used, and when the checkbox is not selected, it is not used.Use OpenSSL for SSL.To set libraries to be used, go to Cluster Properties -> the Encryption tab -> SSL Library and Crypto Library. Use ProxyConfigures whether or not to use a proxy for communicating with the Web server. When the checkbox is selected, the settings of the Proxy tab in the server properties become effective. When the checkbox is not selected, any proxy setting is not used even if the proxy is set in the server properties. IntervalSets the interval for sending HTTP requests. TimeoutSets the timeout time from receiving an HTTP response to receiving the subsequent HTTP response. HTTP timeoutSets the timeout time from sending an HTTP request to receiving an HTTP response. InitializeResets the settings of HTTP NP Properties to default values.
Type
Set the type of network partition resolution I/F. Ping or HTTP is selectable.
Target
Enter the information depending on the type you chose.
PingEnter the IP address of the device where you send a ping. HTTPEnter the DNS name or IP address of the Web server where you send an HTTP request.
Server name
Select either Use or Do Not Use.
Tuning
Network Partition Resolution Tuning Properties window is displayed.
Network Partition Resolution Tuning Properties
Action at NP Occurrence
Stop the cluster serviceStop the cluster service of the server in network partition. Stop the cluster service and shutdown OSStops the cluster service of the server in network partition, and then shuts down the OS. Stop the cluster service and reboot OSStops the cluster service of the server in network partition, and then reboots the OS. Sysrq PanicPerforms a sysrq panic on the server in network partition. Keepalive ResetUse this on the server in network partition to perform an OS reset by using the clpkhb and clpka drivers. Keepalive PanicUse this on the server in network partition to perform an OS panic by using the clpkhb and clpka drivers. BMC ResetUse this on the server in network partition to perform a hardware reset of the server by using the ipmi command. BMC Power- OffUse this on the server in network partition to power off the server by using the ipmi command. The OS may be shut down depending on how the ACPI of OS is configured. BMC Power CycleUse this on the server in network partition to perform the Power Cycle (powering on/off) by using the ipmi command. The OS may be shut down depending on how the ACPI of OS is configured. BMC NMIUse this on the server in network partition to generate NMI in the server by using the ipmi command. The behavior after the generation of NMI depends on the OS setting.Note
When mirror disk resources or hybrid disk resources are used, it is not recommended that you set Stop the cluster service for Action at NP Occurrence.If Stop the cluster service is set, you might have to run the forcible mirror recovery at the time of recovery from NP occurrence.
Initialize
Set the actions at NP occurrence to the default settings.
2.2.3.2. Forced Stop¶
Type
Specify a type of forced stop resource to be used. If no forced stop resources are to be used, select Do Not Use.
Properties
Displays the properties window of a forced stop resource corresponding to the specified type.
BMC Forced Stop Properties
Configure the forced stop of a physical machine. The BMC Forced Stop Properties dialog box is displayed by selecting BMC as a type of forced stop resource and then clicking Properties.
Server List tab
Add
Adds, from available servers, a server to be configured. Selecting a server and clicking Add displays the Enter BMC dialog box.
IP Address (Within 80 bytes)Enter the IP address set for the LAN port for managing BMC. User Name (Within 255 bytes)Enter the name of a user with administrator privilege from the user names configured in BMC.If you do not enter anything, do not configure the user name argument when executing the ipmitool command.The length of the actually valid user name depends on the ipmitool command and the BMC specifications of the server. Password (Within 255 bytes)Enter the password of user configured above.The length of the actually valid user name depends on the ipmitool command and the BMC specifications of the server.For information on user name of IPMI and how to configure the password, refer to the manual of the server.Remove
Removes a server in use. Select an unnecessary server, then click Remove.
Edit
Use this for changing the settings of a server. Select a desired server, then click Edit. This displays the Enter BMC dialog box.
When configuring a cluster with different server models, exclude a server having no BMC. If you added such a server, the forced stop function would alert you to a failure in a periodical check on forcibly stopping the BMC.
Forced stop tab
Forced Stop Action
Specify an action of the forced stop.
BMC Power OffUse this to power off the server by using the ipmitool command.OS may be shut down depending on how the Power Options of OS is configured. BMC ResetUse this to perform a hardware reset of the server by using the ipmitool command. BMC Power CycleUse this to perform the Power Cycle (powering on/off) by using the ipmitool command.The OS may be shut down depending on how the ACPI of OS is configured. BMC NMIUse this to generate NMI by using the ipmitool command. The behavior after NMI is generated depends on the OS settings.Forced Stop Timeout (0 to 999)
Specify a value for the timeout of awaiting the completion of a forced stop in action.
Time to Wait for Stop to Be Completed (0 to 999)
Specify a value for awaiting the completion of a forced stop in action. During the specified time period from the time of requesting a forced stop, whether the forced stop is completed is checked.Specify this value with BMC Power Off selected for Forced Stop Action.Lead Time between a Stop Request and a Failover Start (0 to 999)
Specify a value for awaiting the start of a failover with a forced stop in action. The failover occurs after a forced stop is requested and the specified time passes.Specify this value with BMC Reset, BMC Power Cycle, or BMC NMI selected for Forced Stop Action.Disable Group Failover When Execution Fails
Suppresses group failover if a forced stop fails. Since the group is not started in the failover destination in this case, check the state of the failover source, then manipulate the group as needed.
vCenter Forced Stop Properties
Configure the forced stop of a virtual machine (guest OS). The vCenter Forced Stop Properties dialog box is displayed by selecting vCenter as a type of forced stop resource and then clicking Properties.
Server List tab
Add
Adds, from available servers, a server to be configured. Selecting a server and clicking Add displays the Input for Virtual Machine name dialog box.
Virtual Machine name (Within 80 bytes)Set the virtual machine (guest OS) name.Note
Do not use a double quotation mark (") or percent sign (%) in the virtual machine name.
Data Center (Within 80 bytes)Set the name of the data center that manages the virtual machine (guest OS).Note
Do not use a double quotation mark (") or percent sign (%) in the virtual machine name.
Remove
Removes a server in use. Select an unnecessary server, then click Remove.
Edit
Use this for changing the settings of a server. Select a desired server, then click Edit. This displays the Input for Virtual Machine name dialog box.
Forced stop tab
Forced Stop Action
Specify an action of the forced stop.
Power OffUse this to power off the server by using the vmcontrol command. ResetUse this to perform a hardware reset of the server by using the vmcontrol command.Forced Stop Timeout (0 to 999)
Specify a value for the timeout of awaiting the completion of a forced stop in action.
Time to Wait for Stop to Be Completed (0 to 999)
Specify a value for awaiting the completion of a forced stop in action. During the specified time period from the time of requesting a forced stop, whether the forced stop is completed is checked.Specify this value with Power Off selected for Forced Stop Action.Lead Time between a Stop Request and a Failover Start (0 to 999)
Specify a value for awaiting the start of a failover with a forced stop in action. The failover occurs after a forced stop is requested and the specified time passes.Specify this value with Reset selected for Forced Stop Action.Disable Group Failover When Execution Fails
Suppresses group failover if a forced stop fails. Since the group is not started in the failover destination in this case, check the state of the failover source, then manipulate the group as needed.
vCenter tab
Method of performing forced stop
Specify the Method of performing forced stop.
vSphere Automation APIPerform a forced stop by using the REST API. VMware vSphere CLIPerform a forced stop by using the VMware vSphere Command Line Interface.VMware vSphere CLI Installation Path (Within 1023 bytes)
Specify the installation path of the VMware vSphere CLI.This setting is required with VMware vSphere CLI specified as the method of performing a forced stop.Specification example:
/usr/lib/vmware-vcli
Host name (Within 255 bytes)
Specify the IP address of the virtual machine management tool.
User Name (Within 255 bytes)
Specify the user name of the virtual machine management tool.
Password (Within 255 bytes)
Specify the password for the virtual machine management tool.
Note
Do not use a double quotation mark (") in the password.
AWS Forced Stop Properties
Configure the forced stop of Amazon Web Services. The AWS Forced Stop Properties dialog box is displayed by selecting AWS as a type of forced stop resource and then clicking Properties.
Server List tab
Add
Adds, from available servers, a server to be configured. Selecting a server and clicking Add displays the Input of Instance dialog box.
Instance ID (Within 32 bytes)Specify the instance ID of AWS.Remove
Removes a server in use. Select an unnecessary server, then click Remove.
Edit
Use this for changing the settings of a server. Select a desired server, then click Edit. This displays the Input of Instance dialog box.
Forced stop tab
Forced Stop Action
Specify an action of the forced stop.
stopUses the AWS CLI to stop the instance. rebootUses the AWS CLI to reboot the instance.Forced Stop Timeout (0 to 999)
Specify a value for the timeout of awaiting the completion of a forced stop in action.
Time to Wait for Stop to Be Completed (0 to 999)
Specify a value for awaiting the completion of a forced stop in action. During the specified time period from the time of requesting a forced stop, whether the forced stop is completed is checked.Specify this value with stop selected for Forced Stop Action.Lead Time between a Stop Request and a Failover Start (0 to 999)
Specify a value for awaiting the start of a failover with a forced stop in action. The failover occurs after a forced stop is requested and the specified time passes.Specify this value with reboot selected for Forced Stop Action.Disable Group Failover When Execution Fails
Suppresses group failover if a forced stop fails. Since the group is not started in the failover destination in this case, check the state of the failover source, then manipulate the group as needed.
Azure Forced Stop Properties
Configure the forced stop of Microsoft Azure. The Azure Forced Stop Properties dialog box is displayed by selecting Azure as a type of forced stop resource and then clicking Properties.
Server List tab
Add
Adds, from available servers, a server to be configured. Selecting a server and clicking Add displays the Input for Virtual Machine name dialog box.
Virtual Machine name (Within 64 bytes)Specify an Azure virtual-machine name.Remove
Removes a server in use. Select an unnecessary server, then click Remove.
Edit
Use this for changing the settings of a server. Select a desired server, then click Edit. This displays the Input for Virtual Machine name dialog box.
Forced stop tab
Forced Stop Action
Specify an action of the forced stop.
stopUses the Azure CLI to stop the instance. rebootUses the Azure CLI to reboot the instance.Forced Stop Timeout (0 to 999)
Specify a value for the timeout of awaiting the completion of a forced stop in action.
Time to Wait for Stop to Be Completed (0 to 999)
Specify a value for awaiting the completion of a forced stop in action. During the specified time period from the time of requesting a forced stop, whether the forced stop is completed is checked.Specify this value with stop selected for Forced Stop Action.Lead Time between a Stop Request and a Failover Start (0 to 999)
Specify a value for awaiting the start of a failover with a forced stop in action. The failover occurs after a forced stop is requested and the specified time passes.Specify this value with reboot selected for Forced Stop Action.Disable Group Failover When Execution Fails
Suppresses group failover if a forced stop fails. Since the group is not started in the failover destination in this case, check the state of the failover source, then manipulate the group as needed.
Azure tab
User URI (within 2048 bytes)
Specify the user URI to log on to Microsoft Azure.
Tenant ID (within 36 bytes)
Specify the tenant ID to log on to Microsoft Azure.
File Path of Service Principal (within 1024 bytes)
Specify the full path to the file of a service principal (certificate) to log in to Microsoft Azure.
Resource Group Name (within 90 bytes)
Specify a Microsoft Azure resource group name.
OCI Forced Stop Properties
Configure the forced stop of Oracle Cloud Infrastructure. The OCI Forced Stop Properties dialog box is displayed by selecting OCI as a type of forced stop resource and then clicking Properties.
Server List tab
Add
Adds, from available servers, a server to be configured. Selecting a server and clicking Add displays the Input of Instance dialog box.
Instance ID (Within 255 bytes)Specify the instance ID of OCI.Remove
Removes a server in use. Select an unnecessary server, then click Remove.
Edit
Use this for changing the settings of a server. Select a desired server, then click Edit. This displays the Input of Instance dialog box.
Forced stop tab
Forced Stop Action
Specify an action of the forced stop.
stopUses the OCI CLI to stop the instance. rebootUses the OCI CLI to reboot the instance.Forced Stop Timeout (0 to 999)
Specify a value for the timeout of awaiting the completion of a forced stop in action.
Time to Wait for Stop to Be Completed (0 to 999)
Specify a value for awaiting the completion of a forced stop in action. During the specified time period from the time of requesting a forced stop, whether the forced stop is completed is checked.Specify this value with stop selected for Forced Stop Action.Lead Time between a Stop Request and a Failover Start (0 to 999)
Specify a value for awaiting the start of a failover with a forced stop in action. The failover occurs after a forced stop is requested and the specified time passes.Specify this value with reboot selected for Forced Stop Action.Disable Group Failover When Execution Fails
Suppresses group failover if a forced stop fails. Since the group is not started in the failover destination in this case, check the state of the failover source, then manipulate the group as needed.
Custom Forced Stop Properties
Make settings on the script for the forced stop. The Custom Forced Stop Properties dialog box is displayed by selecting Custom as a type of forced stop resource and then clicking Properties.
Server List tab
Add
Adds a server from available servers.
Remove
Removes a server in use. Select an unnecessary server, then click Remove.
Forced stop tab
Forced Stop Timeout (0 to 999)
Specify a value for the timeout of awaiting the completion of a forced stop in action.
Time to Wait for Stop to Be Completed (0 to 999)
Not to be specified for this function.
Lead Time between a Stop Request and a Failover Start (0 to 999)
Not to be specified for this function.
Disable Group Failover When Execution Fails
Suppresses group failover if a forced stop fails. Since the group is not started in the failover destination in this case, check the state of the failover source, then manipulate the group as needed.
Script tab
The default script file names, forcestop.sh, are listed on Scripts.
User Application
Use an executable file (executable shell script file or execution file) on the server as a script. For the file name, specify an absolute path or name of the executable file of the local disk on the server. If there is any blank in the absolute path or the file name, put them in double quotation marks ("") as follows.
Example: "/tmp/user application/script.sh"
Each executable file is not included in the cluster configuration information of the Cluster WebUI. They must be prepared on each server because they cannot be edited or uploaded by the Cluster WebUI.
Path (Within 1023 bytes)
Specify a script to be executed (executable shell script file or execution file) when you select User Application.
Script created with this product
Use a script file which is prepared by the Cluster WebUI as a script. You can edit the script file with the Cluster WebUI if you need. The script file is included in the cluster configuration information.
Add
Use this button to add a script other than forcestop.sh script when you select Script created with this product.
Note
Do not use 2-byte characters for the name of a script to be added.Do not use "&( ampersand)" or "= (equal sign)" for a script file name to be added.Remove
Use this button to delete a script when you select Script created with this product. The forcestop.sh script cannot be deleted.
View
Click here to display the script file when you select Script created with this product.
Edit
Click here to edit the script file when you select Script created with this product. Click Save to apply the change. You cannot modify the name of the script file.
Replace
Click here to replace the contents of a script file with the contents of the script file which you selected in the file selection dialog box when you select Script created with this product. You cannot replace the script file if it is currently displayed or edited. Select a script file only. Do not select binary files (applications), and so on.
2.2.4. Timeout tab¶
Specify values such as time-out on this tab.
Service Startup Delay Time (0 to 9999)
Specify how long starting the cluster service should be delayed in starting the OS.
Server Sync Wait Time (0 to 99)
For the time specified here, the server will wait at startup until other servers are started.
Heartbeat
Heartbeat interval and heartbeat time-out.
Interval (1 to 99)Interval of heartbeats Timeout (2 to 9999)A failed server is determined if there is no response for the time specified here.
This time-out should be longer than the interval.
To perform the shutdown monitoring (see Monitor tab), this time-out should be longer than the time it takes to shut down applications and the operating system.
When a hybrid disk resource is used, the time-out value must be longer than the value specified at the cluster partition I/O time-out in the mirror agent tab.
Server Internal Timeout (1 to 9999)
The timeout to be used in the EXPRESSCLUSTER Server internal communications that are performed while an EXPRESSCLUSTER command is executed, or an operation is performed or a screen is displayed by Cluster WebUI.
Note
It is recommended to use the default value.Setting this parameter to an extremely large value significantly affects, in case of a heartbeat loss, the time for executing the clpstat command or for displaying Cluster WebUI.
Initialize
Used for initializing the value to the default value. Click Initialize to initialize all the items to their default values.
2.2.5. Port No. tab¶
Specify TCP port numbers and UDP port numbers.
TCP
No TCP port numbers can be overlapped. When the Replicator is used, TCP port numbers on the Port No.(Mirror) tab and any mirror data port number of any mirror disk resources/hybrid disk resources cannot be overlapped.
Server Internal Port Number (1 to 65535 1)This port number is used for internal communication. Information Base Port Number (1 to 65535 1)This port number is used for cluster information management. Data Transfer Port Number (1 to 65535 1)This port number is used for transactions such as applying and backing up the cluster configuration data, sending and receiving the license data and running commands. WebManager HTTP Port Number (1 to 65535 1)This port number is used for a browser to communicate with the EXPRESSCLUSTER Server. API HTTP Port Number (1 to 65535 1)This port number is used when a Restful API client communicates with the EXPRESSCLUSTER Server. API Server Internal Port Number (1 to 65535 1)This port number is used for internal communication of Restful API.
UDP
No UDP port numbers can be overlapped. When the communication method for internal logs is UDP on the Port No.(Log) tab, UDP port numbers cannot be overlapped with the port numbers.
- 1(1,2,3,4,5,6,7,8,9)
It is strongly recommended not to use well-known ports, especially reserved ports from 1 to 1023.
Initialize
This is used for initializing the value to the default value. Click Initialize to initialize all items to their default values.
2.2.6. Port No. (Mirror) tab ~ For the Replicator/Replicator DR ~¶
Specify TCP port numbers.
TCP
No TCP port numbers can be overlapped. TCP port numbers on the Port No. tab and any mirror data port number of any mirror disk resources/hybrid disk resources cannot be overlapped.
Note
Port numbers are not used when mirror disk resource/hybrid disk resource is not used.
Mirror Agent Port Number (1 to 65535 2)Mirror agent is a user mode module for controlling mirror disk resource/hybrid disk resource.The Mirror Agent uses this port number to communicate with servers.
- 2
It is strongly recommended not to use well-known ports, especially reserved ports from 1 to 1023.
Initialize
Used for initializing the value to the default value. Click Initialize to initialize all the items to their default values.
2.2.7. Port No. (Log) tab¶
Specify the communication method for internal logs.
Communication Method for Internal Logs
UDPUse UDP for the communication method for internal logs. UNIX DomainUse UNIX Domain for the communication method for internal logs. Message QueueUse Message Queue for the communication method for internal logs.
Port Number (1 to 65535)
This is the port number used when UDP is selected for the communication method for internal logs.
Initialize
Used for initializing the value to the default value. Click Initialize to initialize all the items to their default values.
2.2.8. Monitor tab¶
Configure the settings for monitoring. For details about the shutdown monitor and reboot limit, see "4. Monitor resource details" in this guide.
Shutdown Monitor
Allows monitoring the operating system for stalling during its shutdown.The cluster service forcibly resets the operating system or performs a panic of the operating system if it determines the OS stall. Server panic can be set when the monitoring method is keepalive.
Always execute:If selected, the shutdown monitor is performed. For the heartbeat time-out, specify a longer time than the time required to shut down every application and the operating system (see "Timeout tab"). Execute when the group deactivation has been failed:The shutdown monitor is applied only when a group cannot be deactivated. For the heartbeat time-out, specify a longer time than the time required to shut down every application and the operating system (see "Timeout tab"). If you use shared disks or mirror disks, it is recommended to select Execute when the group deactivation has been failed. Not execute:If selected, the shutdown monitor is not performed.
Method
Select the shutdown monitor method from:
softdog
ipmi
keepalive
For details about the shutdown monitoring method, see "Shutdown monitoring " in "Shutdown monitoring method" in "8. Information on other settings" in this guide.
Operation at Timeout Detection
Selects the operation performed when the operating system is determined to be stalled.
RESETResets the server. PANICPerforms a panic of the server. This can be set only when the monitoring method is keepalive. NMINMI occur on the server. This can be set only when the monitoring method is ipmi.Enable SIGTERM handler
Select this to enable SIGTERM handler when performing the shutdown monitor.For details about the SIGTERM settings, see "Shutdown monitoring" in " Setting of SIGTERM " in "8. Information on other settings" in this guide.Note
If you select ipmi in Method and set Enable SIGTERM handler to Off, this may be reset even if the operating system is successfully shut down.
Use Heartbeat Timeout
Select this for heartbeat time-out to work in conjunction with shutdown monitoring time-out.
Timeout (2 to 9999)
Specify a time-out when the heartbeat time-out value is not used as shutdown monitoring time-out.A value equal to or smaller than the heartbeat timeout value must be specified to prevent both systems from activating when a failover occurs upon detection of a server down.
2.2.9. Recovery tab¶
Configure the settings for cluster recovery.
Action When the Cluster Service Process Is Failure
Specify the action when a cluster service process error occurs.
Shut down the OSShut down the OS. Reboot the OSReboot the OS. Sysrq PanicPerforms the sysrq panic. Keepalive ResetResets the OS using the clpkhb or clpka driver. Keepalive PanicPerforms the OS panic using the clpkhb or clpka driver. BMC ResetPerform hardware reset on the server by using the ipmi command. BMC Power OffPowers off the OS by using the ipmi command. OS shutdown may be performed due to the ACPI settings of the OS. BMC Power CyclePerforms the power cycle (powering on/off) of the server by using the ipmi command. OS shutdown may be performed due to the ACPI settings of the OS. BMC NMIUses the ipmi command to cause NMI occur on the server. The behavior after NMI is generated depends on the OS settings.
Recovery Action for HA Agents
Max Restart Count (0 to 99)Specify the max restart count when an HA Agent error has occurred. Recovery Action over Max Restart CountSpecify the action when an HA Agent error has occurred.
No operation
Stop the cluster serviceStops the cluster service of the server that detected an error. Stop the cluster service and shutdown OSStops the cluster service of the server that detected an error, and then shuts down the OS. Stop the cluster service and reboot OSStops the cluster service of the server that detected an error, and then reboots the OS.Note
The HA process is used with the system monitor resources, process resource monitor resource, JVM monitor resources, and the system resource information collection function.
Action at Group Resource Activation or Deactivation Stall
Specify the action to apply in the event of an activation/deactivation stall of a group resource.
Stop cluster service and shutdown OSStops the cluster service of the server that stalled, and then shuts down the OS. Stop cluster service and reboot OSStops the cluster service of the server that stalled, and then restarts the OS. Sysrq PanicPerforms a sysrq panic on the server that stalled. Keepalive ResetUse this on the server that stalled to perform an OS reset by using the clpkhb and clpka drivers. Keepalive PanicUse this on the server that stalled to perform an OS panic by using the clpkhb and clpka drivers. BMC ResetUse this on the server that stalled to perform a hardware reset of the server by using the ipmi command. BMC Power OffUse this on the server that stalled to power off the server by using the ipmi command. The OS may be shut down depending on how the ACPI of OS is configured. BMC Power CycleUse this on the server that stalled to perform the Power Cycle (powering on/off) by using the ipmi command. The OS may be shut down depending on how the ACPI of OS is configured. BMC NMIUse this on the server that stalled to generate NMI in the server by using the ipmi command. The behavior after the generation of NMI depends on the OS setting. No Operation (Operates as an activity or deactivity failure)Use this to perform recovery upon the detection of an activation/deactivation failure of a group resource. For details on the recovery operation, see "Recovery Operation tab" in "Resource Properties" in "3. Group resource details" in this guide.Note
If a stall occurs with "Nothing (handle a stall as an activation/deactivation failure)" specified, the effect on the group resources is undefined, so we do not recommend changing the setting to "Nothing (handle a stall as an activation/deactivation failure).".
If you do specify "Nothing (handle a stall as an activation/deactivation failure)", set the recovery operation upon the detection of an activation/deactivation failure of a group resource as described below.Activation/Deactivation Retry Threshold: 0Failover Threshold: 0Final Action: Action that accompanies the OS stop
Disable the Final Action when OS Stops Due to Failure Detection
Click Detailed Settings to set suppression of the final action which accompanies the OS stop caused by error detection.
Group Resource When Activation Failure DetectedIf the final action caused by an activation error detection in a group resource accompanies the OS stop, the final action is suppressed if all other servers are stopped. Group Resource When Deactivation Failure DetectedIf the final action caused by a deactivation error detection in a group resource accompanies the OS stop, the final action is suppressed if all other servers are stopped. Monitor Resource When Failure DetectedIf the final action caused by an error detection in a monitor resource accompanies the OS stop, the final action is suppressed if all other servers are stopped.Note
If errors were detected on multiple servers almost at the same time, and the final action was taken for those servers, the final action which accompanies the OS stop may be taken for all the servers even if the final action caused by an error detection in a monitor resource is set to be suppressed.
The eternal link monitor resource does not become the target for which the final action caused by error detection is suppressed.
The following situations lead to an OS stop during the final action when an activation/deactivation error is detected in a group resource and during the final action when a monitor resource error is detected.
Cluster service stop and OS shutdown
Cluster service stop and OS restart
sysrq panic
keepalive reset
keepalive panic
BMC reset
BMC power off
BMC power cycle
BMC NMI
Disable Shutdown When Multi-Failover-Service Detected
Click Detailed Settings to suppress the shutdown of all servers upon detection of both-system activation.
Server Group Survives When Multi-Failover-Service Detected
Select one server group. The shutdown of the server, which belongs to the server group selected when the both-system activation of the failover group was detected, is suppressed. When the both-system activation is detected among servers in the selected server group, both of the servers will be shut down. If you want to suppress the shutdown in this case, make the settings to disable shutdown when the following double activation is detected.
Server Survives When Multi-Failover-Service Detected
Select one server. The shutdown of the server, selected when the both-system activation of the failover group was detected, is suppressed.
If a server group to which shutdown is not executed when Multi-Failover is detected is set, it is possible to select only a server belonging to the set server group. If no server group is set, all the servers can be selected.
Note
When the both-system activation is detected, the group statuses will be inconsistent among the servers, and failover and failback operations will be able to fail.
If a group status mismatch occurs, the following alert log is output:
Type: WarningModule name: rcEvent ID: 503Message: A mismatch in the group %1 status occurs between the servers. A mismatch in the group %1 status occurs between the servers.
2.2.10. Alert Service tab¶
Configure the settings for the mail report function, the network warning light, alert report destination, and SNMP trap transmission.
To use the mail report function, register the Alert Service license.
To use the network warning light, register the Alert Service license.
Note
To use the mail report function and the network warning light, purchase the EXPRESSCLUSTER X Alert Service 5.2 for Linux.
Enable Alert Setting
Allows changing the alert destination from the default value. To change the destination, click Edit, then set a new destination in the Change Alert Destination dialog box.
By canceling Enable Alert Setting, the modified destination turns to the default value temporarily.
For details about the default alert destination, see "Messages reported by syslog, alert, mail, SNMP trap, and Message Topic" in "11. Error messages" in this guide.
E-mail Address (Within 255 bytes)
Enter the e-mail address to which the report is sent. If more than two e-mail addresses are set, delimit the address by semicolon.
Subject (Within 127 bytes)
Enter the subject title for the e-mail message.
Mail Method
Configure the methods to send mail.
To use SMTP as a mailing method, click SMTP Settings, then set the method in the SMTP Settings dialog box.
This method uses the mail command. Check that a mail is sent to the mail address by using the mail command in advance. SMTPThis method allows for sending mail by directly communicating with the P server.
Destination Settings
Configure the SNMP trap transmission function: Click Settings, then set an SNMP trap transmission destination in the Destination Settings dialog box.
Output Log Level to syslog
Add Log Level to the syslog messages which EXPRESSCLUSTER put out while it is in operation.
Use Network Warning Light
Specify whether to use a network warning light (specified by NEC) controlled by network. Enter an IP address in server properties.
Change Alert Destination
Click Edit to display the Change Alert Destination dialog box.
Add
Click this to select the event ID and the module type for which you want to customize the report destinations. Click Add to open the Enter the Message dialog box.
Category
Select a major category of the module type.
Module Type (Within 31 bytes)
Select the name of module type that you want to change the destination address.
Event ID
Enter the event type of the module type for which you want to change the destination address. For details about the event ID, see "Messages reported by syslog, alert, mail, SNMP trap, and Message Topic" in "11. Error messages" in this guide.
Destination
Select the destination.
System LogThis sends message to syslog of the OS. Alert LogsThis sends message to the alert log. Mail ReportThis sends message by using the mail report function. Message TopicThis sends message to Amazon SNS. Alert ExtensionThis sends message by the Alert Extension function. Modify the extension settings using Add and Edit.
Add
Add a command of the alert extension function. Click Add to open the Enter Command dialog box. Up to 4 commands can be registered with one event ID.
Command (Within 511 bytes)
Enter a command such as SNMP trap to execute reporting with the absolute path. The execution results of the specified command cannot be shown.
KeywordIf you specify %%MSG%%, the body message of the target event ID is inserted.You cannot specify multiple %%MSG%% for one command.Configure within 511 bytes including the description of %%MSG%%. Since blank characters can be included in %%MSG%%, if you specify this for an argument of commands, specify this as "%%MSG%%".Configuration example
/usr/local/bin/snmptrap -v1 -c HOME 10.0.0.2 0 10.0.0.1 1 0 '' 1 s "%%MSG%%"
Remove
Click this to remove a command of alert extension function. Select the command and then click Remove.
Edit
Click this to modify a command of alert extension function. Select the command and then click Edit.
SMTP Settings
Click SMTP Settings to display the SMTP Settings dialog box.
Mail Charset (Within 127 bytes)
Configure the character set of the e-mails sent for mail report.
Send Mail Timeout (1 to 999)
Configure the timeout value for communicating with the SMTP server.
Subject Encode
Select whether or not to encode the subject of e-mails.
SMTP Server List
Use this button to display a SMTP server that is configured. Four SMTP servers can be configured in this version.
Add
Use this button to add a SMTP server. Click Add to display the Enter the SMTP Server dialog box.
Remove
Use Remove to remove the SMTP server settings.
Edit
Use Edit to modify the SMTP server settings.
SMTP Server (Within 255 bytes)
Configure the IP address or host name of the SMTP server.
Use SSL
If you use SSL for communication with the SMTP server, select the checkbox; otherwise uncheck it.
When using SSL, go to the Encryption tab, then set SSL Library and Crypto Library.
For OpenSSL versions supporting this, see "Getting Started Guide" -> "Installation requirements for EXPRESSCLUSTER" -> "System requirements for EXPRESSCLUSTER Server" -> "Operation environment for enabling encryption".
Connection method
SMTPSUse SMTPS for communication with the SMTP server. STARTTLSUse STARTTLS for communication with the SMTP server.
SMTP Port (1 to 65535)
Configure the port number of the SMTP server.
Sender Address (Within 255 bytes)
Configure the address from which an e-mail of mail report is sent.
Enable SMTP Authentication
Configure whether or not to enable SMTP authentication.
Method
Select a method of SMTP authentication.
User Name (Within 255 bytes)
Configure the user name used for SMTP authentication.
Password (Within 255 bytes)
Configure the password used for SMTP authentication.
Destination
Displays the set SNMP trap transmission destinations. With this version, up to 32 SNMP trap transmission destinations can be set.
Add
Adds an SNMP trap transmission destination. Click Add to display the Change SNMP Destination dialog box.
Remove
Use Remove to remove the SNMP trap transmission destination settings.
Edit
Use Edit to modify the SNMP trap transmission destination settings.
Destination Server (Within 255 bytes)
Configure the name of the SNMP trap transmission destination server.
SNMP Port No. (1 to 65535)
Configure the port number of the SNMP trap transmission destination.
SNMP Version
Configure the SNMP version of the SNMP trap transmission destination.
SNMP Community Name (Within 255 bytes)
Configure the SNMP community name of the SNMP trap transmission destination.
2.2.11. WebManager tab¶
Use this tab to configure the settings for the WebManager Server.
Enable WebManager Service
Enables the WebManager Service.
When the check box is selected:The WebManager service is enabled. When the check box is not selected:The WebManager service is disabled.
Communication Method
HTTPNo encryption is used for communicating with a client. HTTPSEncryption is used for communicating with a client.
Number of sessions which can be established simultaneously (10 to 999)
Set the number of requests that can be simultaneously received from clients. If more requests than the number set here are generated, the excess requests will be discarded.
Control connection by using password
Click Settings to show the Password dialog box.
Cluster Password Method / OS Authentication Method
Choose a login method for Cluster WebUI from below.
Cluster Password MethodPerforms authentication with an operation/reference password you set. OS Authentication MethodPerforms authentication with user and password of OS .
Cluster Password Method
Password for OperationSet a password that must be entered to enable connection to the Cluster WebUI in operation mode, config mode, or simulate mode.Click Change to display the Enter Password dialog box. Password for ReferenceSet a password that must be entered to enable connection to the Cluster WebUI in reference mode. Click Change to display the Enter Password dialog box.
Old Password: (Within 255 bytes)Enter the current password. If the password is not set, leave it blank. New Password: (Within 255 bytes)Enter a new password. When deleting the old password, leave it blank. Password Confirmation: (Within 255 bytes)Enter the password again which you entered in New Password.Passwords can consist of one-byte upper- and lower-case letters, digits, symbols, and spaces (0x20 to 0x7E in ASCII code).
OS Authentication Method
Users must be registered to the server in advance to login to Cluster WebUI. More specifically, a group must be registered to the server and the users must belong to it as the control permission of a cluster is assigned per group,
Add
Used to add a group to Authorized Group List. The Group Name dialog box appears when Add is clicked. To add a group, the Operation checkbox must be selected.
Group name (Within 255 bytes)Enter a group name to which you want to give permission. The permission will be applied to the users belong to the group you entered. Groups must be registered to a server in advance.
Remove
Used to delete a group from Authorized Group List. Select a group you want to delete from Authorized Group List, and click Remove.
Edit
Used to edit a group. Select a group you want to edit from Authorized Group List, and click Edit. The Group Name dialog box with the selected group entered appears. The control permission does not change in this procedure.
Operation
Set control permission to a group registered in Authorized Group List.
When the checkbox is selected:Users belong to the group can control the cluster and view the status. When the checkbox is not selected:Users belongs to the group can view the status only.
Login Session Lifetime Period (0 to 52560)
Time frame of login session. If this value is set to zero (0), the period becomes limitless.
Automatic Logout Time Period (0 to 99999)
Sets wait time for automatic logout if there is no communication between Cluster WebUI and the WebManager server. If this value is set to zero (0), no automatic logout occurs.
Lockout Threshold (0 to 999)
Locks out a client IP address which fails to login continuously. The client cannot login until Lockout Time passes once a client is locked out. If this value is set to zero (0), no client IP address is not be locked out.
Lockout Time (1 to 99999)
Sets lockout time for a client IP address. Once the time passes, the lockout is automatically released.
Initialize
Restores the default value. If Initialize is clicked, the values of Login Session Lifetime Period, Automatic Logout Time Period, Lockout Threshold and Lockout Time are restored to the default values.
Control connection by using client IP address
If selected, accesses are controlled by client IP addresses.
When the check box is selected:Add, Remove and Edit are displayed. When the check box is not selected:Add, Remove and Edit are not displayed.
Add
Use Add to add an IP address in Connection Permit Client IP Address List. Click Add to display the IP Address dialog box. Newly added IP addresses have the rights for the operation.
IP Address (Within 80 bytes)
Specify a client IP address that can be connected.
IP address: 10.0.0.21
Network address: 10.0.1.0/24
Remove
Use Remove to remove an IP address from Connection Permit Client IP Address List. Select the IP address to be removed from Connection Permit Client IP Address List and then click Remove.
Edit
Use Edit to edit an IP address. Select the IP address you want to edit from Connection Permit Client IP Address List and then click Edit. A dialog box where the specified IP address is preset is displayed. The rights for operating the edited IP addresses remain the same.
Note
The Connection Permit Client IP Address List specified here are also used to restrict connections for external operations using clprexec.
Operation
Sets the operation rights for IP addresses that are registered in Connection Permit Client IP Address List.
When the check box is selected:A client can operate a cluster and display its status. When the check box is not selected:A client can only view the status of a cluster.
Output Cluster WebUI Operation Log
Allows you to output the operation log of Cluster WebUI.
For details, see "Maintenance Guide" - "The system maintenance information" - "Function for outputting the operation log of Cluster WebUI".
If the check box is checked:The operation log of Cluster WebUI is outputted. If the check box is not checked:The operation log of Cluster WebUI is not outputted.
Log output path (Within 255 bytes)
Specify the output destination directory of the Cluster WebUI operation log with an absolute path consisting of ASCII characters.If no directory is specified, the Cluster WebUI operation log is outputted to <installation path>/log.
File Size (1 to 10)
Specify the size of Cluster WebUI operation log.When the log data reaches the specified size, a rotation occurs. Up to five generations of the data are saved.
IP address for Integrated WebManager
Click Settings to open the IP address dialog box for the Integrated WebManager.
Add
Add IP addresses for the Integrated WebManager. Click the column cell of each server and select or enter IP address for the IP address of each server. For the communication path not connected to some server, set blank to the server cell of which the server is not connected.
Remove
Remove the communication path. Select the communication path to be removed and click Remove, then the selected path is removed.
Priority
When multiple IP addresses for Integrated WebManager are configured, the communication path with the smallest number in the Priority column is used preferentially for the internal communication among cluster servers. When changing the priority, click the arrows to change the order of the selected row.
Tuning
Use Tuning to tune the WebManager Server. Clicking Tuning displays the WebManager Tuning Properties dialog box.
Client Session Timeout (1 to 999)Specify the client session time-out. A time-out is determined if the time specified here elapses after the last communication between the WebManager Server and the Cluster WebUI. Reload Interval (0 to 999)Specify the screen data update interval. At this time interval, the Cluster WebUI screen is refreshed. Mirror Agent Timeout (1 to 999)Set the data waiting time output from the mirror agent. Time Limit For Keeping Log Files (60 to 43200)Specify the expiration period for deleting log collection information that is temporarily stored on a server. Log information on a server will be deleted if the expiration period is exceeded after the dialog box prompting saving log collection information is displayed. Use Time Info Display FunctionSpecify whether the time information display function is enabled or disabled.
When the check box is selected:The time information display function is enabled. When the check box is not selected:The time information display function is disabled.Initialize
Click Initialize to reset all settings on this dialog to default. Click Initialize to set all the items to their default values.
2.2.12. API tab¶
This tab allows you to set API services.
Enable API Service
Enables API services.
When the checkbox is selected:API services are enabled. When the checkbox is not selected:API services are disabled.
Communication Method
HTTP:Does not use encryption for client communication. HTTPS:Use encryption for client communication.
Control a privilege of operating clusters per group
Allows you to set and control a privilege of operating clusters per group.
If the check box is checked:Add, Remove, and Edit are displayed. If the check box is not checked:Add, Remove, or Edit is not displayed.Login users must be registered beforehand in the server which issues the request. More specifically, a group must be registered to the server and the users must belong to it as the control permission of a cluster is assigned per group.
If the server belongs to a work group:Register the same user name and group name in each of the servers which issues the request. If the server belongs to a domain:Register users and groups in the domain.
Add
Allows you to add a group to Authorized Group List. Clicking Add displays the Group Name dialog box. Any group added here has the Operation box checked.
Group name (up to 255 bytes)Enter the name of a group. Users belonging to the group are to be given the permission.The group must be registered to a server in advance.
Remove
Use this option to delete a group from Authorized Group List.From Authorized Group List, select a group to be deleted. Then, click Remove.
Edit
Use this option to edit a group. From Authorized Group List, select a group to be edited. Then click Edit. The Group Name dialog box appears with the selected group entered. Editing the group here does not change its operation right.
Operation
Set operation rights for any of the groups registered in Authorized Group List.
If the check box is checked:The users of the group can operate the cluster and obtain its status. If the check box is not checked:The users of the group can only obtain the status of the cluster.
Control connection by using client IP address
Controls connections using client IP addresses.
When the checkbox is selected:Add, Remove and Edit are displayed. When the checkbox is not selected:Add, Remove and Edit are not displayed.
Add
Use Add to add an IP address in Connection Permit Client IP Address List. Click Add to display the IP Address dialog box. Newly added IP addresses have the rights for the operation.
IP Address (Within 80 bytes)
Specify a client IP address allowed for the connection.
IP address: 10.0.0.21
Network address: 10.0.1.0/24
Remove
Use Remove to remove an IP address from Connection Permit Client IP Address List. Select the IP address to be removed from Connection Permit Client IP Address List and then click Remove.
Edit
Use Edit to edit an IP address. Select the IP address you want to edit from Connection Permit Client IP Address List and then click Edit. A dialog box where the specified IP address is preset is displayed.
Operation
Set operation rights for any of the IP addresses registered in Connection Permit Client IP Address List.
When the check box is selected:A client can operate a cluster and display its status. When the check box is not selected:A client can only view the status of a cluster.
Output API Service Operation Log
Allows you to output the operation log of API Services.
For details, see "Maintenance Guide" - "The system maintenance information" - "Function for outputting an API service operation log file".
If the check box is checked:The operation log of API Services is outputted. If the check box is not checked:The operation log of API Services is not outputted.
Log output path (Within 255 bytes)
Specify the output destination directory of the API Service operation log with an absolute path consisting of ASCII characters.If no directory is specified, the API Service operation log is outputted to <installation path>/log.
File Size (1 to 10)
Specify the size of API Service operation log.When the log data reaches the specified size, a rotation occurs. Up to five generations of the data are saved.
Tuning.
Adjusts API services. Click Tuning to display API Tuning Properties dialog box.
Authentication Lockout ThresholdSpecify the number that counts continuous HTTP server authentication failures. If the counts reach this threshold, lockout is performed. HTTP Server Start Retry CountSpecify the retry number that counts API services failed to start a HTTP server. HTTP Server Start IntervalSpecify the period of time between the time HTTP server start failure occurs and the time retry starts. InitializeUse Initialize to restore the default value. All the items restore the default values when Initialize is clicked.
2.2.13. Encryption tab¶
Sets files and libraries used for encryption of the cluster elated services.
Certificate File
Sets server certificate files used for connecting to a client. Server certificate files must be prepared at user side.
Private Key File
Sets private key files used for connecting to a client. Private key files must be prepared at user side.
SSL Library
Sets SSL library files used for encryption and selects SSL library files included in OpenSSL. Some settings such as installation locations need to be changed depending on the environment.
Crypto Library
Sets Crypto library files used for encryption and selects Crypto library files included in OpenSSL. Some settings such as installation locations need to be changed depending on the environment.
2.2.14. Alert Log tab¶
Configure the settings for the alert log.
Enable Alert Service
Select this to start alert service for the server.
When the check box is selected:Alert service is enabled. When the check box is not selected:Alert service is disabled.
Max. Number to Save Alert Records (1 to 99999)
Specify the maximum number of alert records that can be retained. Alert service for server can retain alert messages up to this number.
Enable a log file for investigation to be downloaded
Enable or disable downloading a log file for investigation through Cluster WebUI in response to the occurrence of a failure. For more information on the log file, see " Function for obtaining a log file for investigation" in " The system maintenance information" in the " Maintenance Guide".
When the check box is selected:The log file is downloadable through Cluster WebUI. When the check box is not selected:The log file is not downloadable through Cluster WebUI.
Alert Sync: Method
This communication mode is used for Alert Log synchronization. Only unicast is available in Method list box for this version.
Alert Sync: Communication Timeout (1 to 300)
Specify a communication time-out. A communication time-out is determined if the time specified here elapses after the last communication between Alert service and servers.
Initialize
Click Initialize to reset all settings on this tab to default. Click Initialize to set all the items to their default values.
2.2.15. Delay Warning tab¶
Configure the settings for Delay Warning on this tab. For details, see "Delay warning of monitor resources" in "Monitor resource" in "4. Monitor resource details" in this guide.
Heartbeat Delay Warning (0 to 100)
Set a percentage of heartbeat time-out at which the heartbeat delay warning is issued. If the time for the percentage passes without any heartbeat response, the warning will be produced in an alert log. If you set 100, the warning will not be issued.
Monitor Delay Warning (0 to 100)
Set a percentage of monitor time-out at which the monitor delay warning is issued. If the time for the percentage passes without any monitor response, the warning will be produced in an alert log. If you set 100, the warning will not be issued.
Note
If you specify 0% for the delay warning, an alert log is shown in every heartbeat interval and monitor interval. Setting 0% allows you to see the time spent for monitoring. This will be helpful particularly in a test operation. Make sure not to set low values such as 0% in the production environment.
2.2.16. Mirror Agent tab ~ For the Replicator/Replicator DR~¶
Configure the settings for the Mirror Agent on this tab.
Auto Mirror Recovery
When the check box is selected, the mirror recovery is automatically performed if there is any difference between mirror disks on both servers. In some cases, you cannot perform the auto-mirror recovery even if this is selected. For details, see "Automatically recovering from mirroring" in "10. Troubleshooting" in this guide.
When the check box is selected:The mirror recovery is automatically performed. When the check box is not selected:The mirror recovery is not automatically performed.
Receive Timeout (1 to 600)
Set the time-out for the Mirror Agent waiting to receive data after establishing the connection.
Send Timeout (1 to 600)
Set the time-out for the Mirror Agent to send data to the Mirror Agent of the other server and wait it to be processed.
Recovery Data Size (64 to 32768)
Specify the recovery data size.
Start wait time (10 to 600)
For using a hybrid disk resource in a shared disk, set the waiting time to synchronize the starts of the servers connected to the shared disk. If another server does not start within the time configured here, the current right is obtained temporarily.
Cluster partition I/O timeout (5 to 300)
For using hybrid disk resource, set the timeout value for accessing the cluster partition.
The time-out value must be smaller than the heartbeat time-out specified at the Timeout tab.
Recovery Limitation
Specify the retry count to perform mirror recovery again if the data has been updated during a mirror recovery.
On (1 to 100)The mirror recovery retry is performed the times specified on the box. OffWhen there is update data, mirror recovery is performed until there is no difference.
Initialize
This is used to reset the values to the default value. Clicking Initialize sets all the items to their default values.
2.2.17. Mirror driver tab ~ For Replicator/Replicator DR ~¶
Configure the settings for the mirror driver on this tab.
Max. Number of Request Queues (2048 to 65535)
Set the number of queues for mirror disk driver for queuing I/O requests from the upper system.
Difference Bitmap Size (1 to 5)
Users can specify the length of Record Area of the Difference Bitmap. Only when the mirror disk resource and/or hybrid disk resource do not exist in the cluster, the setting can be changed.
Difference Bitmap Refresh Interval (1 to 600)
Set the interval to check if the standby system writes the difference bitmap.
Mirror Recovery I/O size (4, 64)
Specify the size per I/O in the copy process of mirror recovery.
History Recording Area Size in Asynchronous Mode (1 to 200)
Specify the capacity of the mirror disk driver that, according to I/O requests from the upper system, stores data about unsent requests. Only when the mirror disk resource and/or hybrid disk resource do not exist in the cluster, the setting can be changed.
Operation at I/O Error Detection
Cluster PartitionSet an operation when an I/O error occurs in a cluster partition. Data PartitionSet an operation when an I/O error occurs in a data partition.
Initialize
Use Initialize to reset the values to the default value. Click Initialize to set all the items to their default values.
2.2.18. JVM monitor tab¶
Configure detailed parameters for the JVM monitor.
Note
To display the JVM monitor tab on the config mode of Cluster WebUI, you need to execute Update Server Info after the license for Java Resource Agent is registered.
Java Installation Path (Within 255 bytes)
Set the Java VM install path used by the JVM monitor. Specify an absolute path using ASCII characters. Do not add "/" to the end of the path. This setting becomes common for all servers in the cluster.Specification example: /usr/java/jdk-9
Maximum Java Heap Size (7 to 4096)
Set, in megabytes, the maximum Java VM heap size used by the JVM monitor (equivalent to -Xmx of the Java VM startup option). This setting becomes common for all servers in the cluster.
Java VM Additional Option (Within 1024 bytes)
Set the Java VM startup option used by the JVM monitor. However, specify -Xmx in the [Maximum Java Heap Size]. This setting becomes common for all servers in the cluster.Specification example: -XX:+UseSerialGC
Log Output Setting
Click the Settings button to open the Log Output Setting dialog box.
Resource Measurement Setting
Click the Settings button to open the Resource Measurement Setting dialog box.
Connection Setting
Click the Settings button to open the Connection Setting dialog box.
Action Timeout (30 to 300)
Set the timeout value of [Command] specified in each window of the JVM monitor. This setting becomes common for all the [Command] items.
Log Output Setting
Clicking Settings displays the Log Output Setting dialog box.
Log Level
Select the log level of the log output by the JVM monitor.
Generation (2 to 100)
Set the number of generations to be retained for log output by the JVM monitor. When Period is selected for Rotation Type, the rotation count is reset when cluster is suspended. Therefore, note that log files under the <EXPRESSCLUSTER_install_path>log\ha\jra increase per cluster suspend.
Rotation Type
Select a rotation type for the log output by the JVM monitor. If you select File Capacity as the rotation type, set the maximum size (200 to 2097151), in kilobytes, for each log file such as the JVM operation log. If you select Period as the rotation type, set the log rotation start time in "hh:mm" format (hh: 0 to 23, mm: 0 to 59) and the rotation interval (1 to 8784) in hours.
Initialize
Clicking Initialize returns the log level, generation, and rotation type items to their default values.
Resource Measurement Setting [Common]
Clicking Settings displays the Resource Measurement Setting dialog box. For details about the scheme for error judgment by the JVM monitor, see "Monitor resource details".
Retry Count (1 to 1440)
Set a resource measurement retry count to be applied if the JVM monitor fails in resource measurement.
Error Threshold (1 to 10)
Set the number of times abnormal judgment is performed when the usage of the Java VM or the application server resources collected by the JVM monitor via resource measurement continuously exceed the customer-defined threshold.
Memory Usage, Active Threads (15 to 600)
Set the interval at which the JVM monitor measures the memory usage and active thread count.
The time and count in Full GC (15 to 600)
Set the interval at which the JVM monitor measures the time and count in Full GC execution.
Initialize
Clicking Initialize returns the retry count, error threshold, and interval items to their default values.
Resource Measurement Setting [WebLogic]
Clicking Settings displays the Resource Measurement Setting dialog box. For details about the scheme for error judgment by the JVM monitor, see "Monitor resource details".
Retry Count (1 to 5)
Set the resource measurement retry count to be applied if the JVM monitor fails in resource measurement.
Error Threshold (1 to 10)
Set the number of times abnormal judgment is to be performed when the usage of the Java VM or the application server resources collected by the JVM monitor via resource measurement continuously exceed the customer-defined threshold.
The number of request (15 to 600)
Set the interval at which the JVM monitor measures the number of work manager or thread pool requests during WebLogic monitor.
The average number of the request (15 to 600)
Set the interval at which the JVM monitor measures the average number of work manager or thread pool requests during WebLogic monitor. Set a value that is an integer multiple of the value set in The number of request.
Initialize
Clicking Initialize returns the retry count, error threshold, and interval items to their default values.
Connection Setting
Clicking Settings displays the Connection Settings dialog box.
Management Port (1 to 65535)
Sets the port number internally used by the JVM monitor resource. Make sure not to set the port number that has been used by other functions or programs. This setting becomes common for all the servers in the cluster. Do not set 32768 to 61000.
Retry Count (1 to 5)
Set the retry count to be applied if connection to the monitor target Java VM fails.
Waiting time for reconnection (15 to 60)
Set the interval at which the JVM monitor retries connection if it fails in Java VM connection.
Initialize
Clicking Initialize sets the management port, retry count, and wait time for reconnection items to their default values.
2.2.19. Cloud tab¶
Configure functions for cloud environments.
Enable Amazon SNS linkage function
Enable or disable the Amazon SNS linkage function.
If the check box is checked:The Amazon SNS linkage function is enabled.Amazon SNS is used as a destination of EXPRESSCLUSTER messages.By default, the messages are sent as shown in "11. Error messages": the "o"-marked lines of the [5] column in the table of "11.2. Messages reported by syslog, alert, mail, SNMP trap, and Message Topic".To send other messages:Go to Cluster Properties -> the Alert Service tab -> Change Alert Destination -> Destination, and then select Message Topic. If the check box is not checked:The Amazon SNS linkage function is disabled.
TopicArn
Set TopicArn for the Amazon SNS linkage function.
Enable Amazon CloudWatch linkage function
Enable or disable the Amazon CloudWatch linkage function.
If the check box is checked:The Amazon CloudWatch linkage function is enabled.Amazon CloudWatch is informed of the monitoring process time taken by the monitor resource. If the check box is not checked:The Amazon CloudWatch linkage function is disabled.
Note
Using the Amazon CloudWatch linkage function requires turning on Enable Amazon CloudWatch linkage function, and enabling Send polling time metrics of the Monitor (common) tab for the target monitor resource.
Namespace
Set Namespace for the Amazon CloudWatch linkage function.
Interval for Sending Metrics
Set the frequency of informing Amazon CloudWatch of the monitoring process time taken by the monitor resource.
AWS CLI command line options
Clicking Settings displays a text box for each AWS service.For each AWS service, set AWS CLI command line options to be applied.
Environment variables at the time of performing AWS-related features
Clicking Settings displays a dialog box listing environment variables.
Environment variable List
Clicking Edit displays a dialog box to edit the selected environment variable.Clicking Add displays a dialog box to add a new environment variable.Clicking Remove* deletes the selected environment variable.
Enter environment variable
Enter the name and value of an environment variable.
Name (within 259 bytes)Specify the name of an environment variable. Value (within 2047 bytes)Specify the value of the environment variable.
2.2.20. Statistics tab¶
Configure the settings for statistics.
Cluster Statistics
You can collect and see data on the cluster operation such as the required time of a group failover and that of resource activation.For details, see " Cluster statistics information collection function" in " The system maintenance information" in the " Maintenance Guide".
When the check box is selected:The cluster statistical information is collected.
File Size (whose setting range depends on the type)Specify the size of the cluster statistical information file.When the collected information reaches the specified size, rotation occurs to save up to two generations of the data. When the check box is not selected:The cluster statistical information is not collected.Note
In Cluster Statistics, File Size can be specified as follows:
Heartbeat resource: 1 to 50 (MB) Group: 1 to 5 (MB) Group resource: 1 to 5 (MB) Monitor resource: 1 to 10 (MB)
Mirror Statistics
This function can be used to collect and reference information about the mirroring performance.For details, see " Mirror statistics information collection function" in " The system maintenance information" in the " Maintenance Guide".
When the check box is selected:Mirror Statistics Collection is performed. When the check box is not selected:Mirror Statistics Collection is not performed.
System Resource Statistics
Select whether to collect system resource information.System resource information is collected regularly so as to improve system operability. System resource information is useful for investigating the operation status of EXPRESSCLUSTER, and makes it easy to determine the cause of a failure attributable to a shortage of system resources.For details, see " System resource statistics information collection function" and " Process resource statistics information collection function" in " The system maintenance information" in the " Maintenance Guide".
When the check box is selected:System resource information related to the CPU, memory, processes, and others is collected regularly while the cluster is running.The collected system resource information are collected as a log by the clplogcc command or Cluster WebUI.Specify type 1 to collect the log by the clplogcc command; specify Pattern 1 to collect the log by the Cluster WebUI. For details about log collection, see "Collecting logs (clplogcc command)" in "9. EXPRESSCLUSTER command reference" in this guide, and the online manual.A disk area of 450 MB or more is required to store the resource information, depending on the system operating conditions such as the number of processes that are running.To use this feature, a zip (unzip) package tool is required on each server. When the check box is not selected:No system resource information is collected.
Initialize
Used for initializing the value to the default value. Click Initialize to initialize all the items to their default values.
2.2.21. Extension tab¶
Other cluster functions are set.
Reboot Limitation
If the final action at abnormality detection for group resources and monitor resources is specified with the setting accompanied by OS reboot, reboot may be repeated infinitely. By setting the reboot limit, you can prevent repeated reboots.
Max Reboot Count (0 to 99)Specify how many times the operating system can reboot. The number specified here is separately counted for group resource and monitor resource.With Max Reboot Count set to zero, the reboot can be unlimitedly repeated. Max Reboot Count Reset Time (0 to 999)When the max reboot count is specified, if the operation from the cluster startup keeps running normally for the time specified here, the reboot count is reset. The time specified here is separately counted for group resource and monitor resource.Note
If Max Reboot Count Reset Time is set to 0, the reboot count is not reset. If you want to reset the reboot count, use clpregctrl command.
Start Automatically After System Down
Set whether to prohibit automatic startup of the cluster service at the next OS startup when the server has been stopped by a means other than cluster shutdown or cluster stop, or when cluster shutdown or stop does not terminate normally.For the conditions to prohibit automatic startup of the cluster service after system down, see "Conditions for automatic startup prohibition" in "8. Information on other settings".
Exclude Mount/Unmount Commands
Set whether to exclude the mounting/unmounting of file systems for disk resources, mirror disk resources, and hybrid disk resources. Selecting the check box allows you to avoid problems such as a failure in the mount or unmount command, but leads to the mounting/unmounting of file systems in order. Therefore, for a configuration with many resources, it may take time to activate and deactivate them.
When the check box is selected:The exclusion is performed. When the check box is not selected:The exclusion is not performed.
Grace period of server group failover policy (0 to 99999)
Specify the time by which a failover start is delayed when the automatic failover is performed between the server groups. After a server failure is detected and then the specified time elapses, the failover is performed.If you specify 0, no delay occurs.
Change from OS Stop to OS Restart
Determine whether the OS stop action is collectively changed to OS restart action.
If the check box is checked:The action change is made. If the check box is not checked:The action change is not made.Note
If you want to make the action change, it is recommended to configure a network partition resolution resource or forced stop resource as well.
The changed action changes the following actions.No actions other than those below are changed.
Action for NP resolution
With Stop cluster service and shutdown OS selected:Changes to Stop cluster service and reboot OS. With BMC Power Off selected:Changes to BMC Power Cycle. Action with an abnormal cluster service process
With Shut down the OS selected:Changes to Reboot the OS. With BMC Power Off selected:Changes to BMC Power Cycle. Action in case of an activation/deactivation stall of a group resource
With Stop cluster service and shutdown OS selected:Changes to Stop cluster service and reboot OS. With BMC Power Off selected:Changes to BMC Power Cycle. Action in case of a split brain syndrome in a group
Emergency shutdown (unable to be changed)Changes to Reboot the OS after the emergency shutdown. Final action with the abnormal activation/deactivation of a group resource
With Stop cluster service and shutdown OS selected:Changes to Stop cluster service and reboot OS. With BMC Power Off selected:Changes to BMC Power Cycle. Final action with an abnormal monitor resource
With Stop cluster service and shutdown OS selected:Changes to Stop cluster service and reboot OS. With BMC Power Off selected:Changes to BMC Power Cycle.Note
The action change does not affect the following monitor resources:
Eternal link monitor resources
User mode monitor resources
Mirror disk connect monitor resources
Mirror disk monitor resources
Hybrid disk connect monitor resources
Hybrid disk monitor resources
Disable Cluster Operation
Group Automatic Startup
When the checkbox is selected:The group does not start automatically. When the checkbox is not selected:The group starts automatically. Recovery Operation when Group Resource Activation Failure Detected
When the checkbox is selected:The recovery operation is disabled. When the checkbox is not selected:The recovery operation is not disabled. Recovery Operation when Group Resource Deactivation Failure Detected
When the checkbox is selected:The recovery operation is disabled. When the checkbox is not selected:The recovery operation is not disabled. Recovery Action when Monitor Resource Failure Detected
When the checkbox is selected:The recovery action is disabled. When the checkbox is not selected:The recovery action is not disabled. Failover when server failure detected
When the checkbox is selected:The failover is disabled. When the checkbox is not selected:The failover is not disabled.Note
The Recovery action when a monitor resource error is detected feature does not support external monitor resources.
Settings of log storage period
Use log storage period featureRenames (not deletes) an old log file (whose name ends with .pre) in the following folders to <date and time when the file was last updated>_<type name>.log, when the file is rotated:
<installation path>/log <installation path>/perfThe log file renamed as above is compressed at a specified time, then saved as <date when the file was compressed_server name>.tar.gz to a given log storage destination. Store log (1 to 9999)Specify a log storage period (up to 9999 days). When this period elapses, the corresponding log files are automatically removed. Log storage destination (within 170 characters)Specify an absolute path (other than the installation path) to the storage folder, in ASCII characters.Make sure that free space and write performance are sufficiently available. Log storage timingSpecify a time at which the storage occurs every day, in the pop-up window opened by clicking the timepiece icon.
Initialize
Use Initialize to reset the values to the default value. Clicking Initialize sets all the items to their default values.
2.3. Server Common Properties¶
Configure setting information of all servers in Servers Properties.
2.3.1. Master server tab¶
Configure the priority order of the servers. All the registered servers are displayed. Master server is the server to keep the master of cluster configuration information. And also, it is the server of the highest priority order.
Order
Used when changing the priority order of the servers. Select the server to be changed from the server definition list, and Click the arrows selected row moves.
2.3.2. Server group tab¶
Set server groups.
Add
Add server groups. The wizard windows for adding the server group is displayed. For the details, see "Creating the cluster configuration data" in "Installation and Configuration Guide".
Remove
Then the selected server group is removed.
When the following conditions are matched, the server group cannot be removed.
Selected target
Conditions that the server group cannot be removed
Application method
Server group name
The server group is registered as the server group of the failover group.
Cluster stopMirror agent stopMirror agent startCluster start
Rename
The change server group name dialog box of the selected server group is displayed.
There are the following naming rules
Selected target
Naming rules
Application method
Server group name
There are naming rules that are the same as the host name of TCP/IP that can be set by the OS.
Up to 31 characters (31 bytes).
Names cannot start or end with a hyphen (-) or a space.
A name consisting of only numbers is not allowed.
Cluster stopMirror agent stopMirror agent startCluster startNames should be unique (case-insensitive) in the server group.
Properties
Display the properties of the selected server group.
Server Group Definition
Name
Display the server group name.
Add
Add the selected server in Available Servers to Servers that can run the Group.
Remove
Remove the selected server in Servers that can run the Group from the list.
Order
Used when changing the priority order of the server. Select the server to be changed from Servers that can run the Group and click the arrows. The selected row moves.
Servers
Display the server names which belong to the server group.
2.4. Server properties¶
Configure individual settings on each server constructing the cluster in Server Properties.
2.4.1. Info tab¶
You can display the server name and make a change to a comment on this tab.
Name
The selected server name is displayed. You cannot change the name here.
Changing the server name
click others, and then select Rename the server.
A dialog box to rename server is displayed.
Naming rules
There are naming rules that are the same as the host name of TCP/IP that can be set by the OS. It should be completely the same as the name set to the server.
Up to 255 characters (255 bytes)
Neither hyphen (-) nor space can be the first or last letter in names.
Underscores (_) cannot be used.
A name consisting of only numbers is not allowed.
"localhost" cannot be used as a server name.
Comment (Within 127 bytes)
You can specify a comment for the server. Only alphanumeric characters are allowed.
2.4.2. Warning Light tab¶
Set an IP address of warning light (specified by NEC) controlled by network.
Add
Use Add to add an interface. Clicking Add displays the Enter Alert Lamp dialog box.
Warning LightSelect the product number of the warning light you use. The products corresponding to each number are as follows.
Product Number
Product Name
DN-1000S/DN-1000R/DN-1300GL
DN-1000S/DN-1000R/DN-1300GL
DN-1500GL
DN-1500GL
NH-FB series/NH-FB1 series
NH-FB series/NH-FB1 series
NH-FV1 series
NH-FV1 series
IP Address (Within 80 bytes)Enter an IP address of the warning light.Note
One warning light is required per one server. Do not set an IP address of the same warning light to multiple servers.
Playback of an audio filePlayback of an audio file is enabled when DN1500GL or NH-FV1 series is selected as the warning light type.If you change the warning light type to other than DN1500GL or NH-FV1 series after playback of an audio file was enabled, playback of an audio file will be disabled.
Alert When Server Starts
When the check box is selected:Reproduces the audio file at server start. The audio file is reproduced only once. When the check box is not selected:Does not reproduce the audio file at server start.
Voice File No. (DN1500GL:01 to 20, NH-FV1 series: 01 to 70)
Set the number of the voice file to be played when the server starts
Alert When Server Stops
When the check box is selected:Reproduces the audio file at server stop. The audio file is continuously reproduced until it is stopped manually. When the check box is not selected:Does not reproduce the audio file at server stop.
Voice File No. (DN1500GL:01 to 20, NH-FV1 series: 01 to 70)
Set the number of the voice file to be played when the server stops.
Edit
Use Edit to edit the warning light setting.
Note
2.4.3. Proxy tab¶
Sets proxy information.
Proxy Scheme
Sets protocols you want to use.
None: Proxy is used.HTTP: HTTP is used.
Proxy Server
Sets the DNS host name (or IP address) you want to connect.
Proxy Port
Sets the port number you want to connect.
2.5. Group Properties¶
For more information, see "3. Group resource details" in this guide.
2.6. Group Resource Properties¶
For more information, see "3. Group resource details" in this guide.
2.7. Monitor Resource Properties¶
For more information, see "4. Monitor resource details" in this guide.
2.8. Parameters list¶
Parameters you can specify in the Cluster WebUI and their default values are listed below.
"How to change [1]-[12]" represents the way you apply changes of parameters on servers. Applicable method is marked with "✓."
Priority |
How to apply |
---|---|
1 |
Uploading data and shutting down, restarting a cluster |
2 |
Stopping a cluster, and stopping a mirror agent, and then uploading data |
3 |
Uploading data after stopping a cluster |
4 |
Uploading data after stopping a group |
5 |
Uploading data after stopping a resource |
6 |
Uploading data after suspending a cluster |
7 |
Uploading data after suspending a monitor |
8 |
Uploading data and restarting an Node Manager service |
9 |
Uploading data and restarting an Information Base service |
10 |
Uploading data and restarting WebManager Server |
11 |
Uploading data and restarting an API service |
12 |
Uploading data only |
When creating the cluster configuration data for the first time, see "Creating the Cluster configuration data" in the "Installation and Configuration Guide".
2.9. Upper limits of registration¶
version |
You can register up to |
|
---|---|---|
Cluster |
4.0.0-1 or later |
1 |
Server |
4.0.0-1 or later |
32 |
Server group |
4.0.0-1 or later |
9 |
Group |
4.0.0-1 or later |
128 |
Group resource (Per group) |
4.0.0-1 or later |
256 |
Monitor resource |
4.0.0-1 or later |
512 |
Heartbeat resource |
4.0.0-1 or later |
128 |
Witness heartbeat resource |
4.0.0-1 or later |
1 |
Network partition resolution resource |
4.0.0-1 or later |
64 |
Mirror disk resources and hybrid disk resources (Per cluster) in total |
4.0.0-1 or later |
32 |
Mirror disk connect |
4.0.0-1 or later |
16 |