This chapter explains how to configure monitoring information.
Use the following procedure to configure the monitoring information.
In the ROR console server resource tree, right-click the target physical OS and the VM hosts, and select [Modify]-[Monitoring Settings] from the popup menu.
The [Configuring monitoring settings] dialog is displayed.
Set the following items:
When using the ping command to monitor the admin LAN for the target physical OS or the VM host, and recovery for the error detection is enabled, select the checkboxes.
Information
When performing these settings, use ping monitoring if the server status becomes "unknown".
When the following conditions are satisfied for the physical OS and the VM host for which ping monitoring is enabled, message number 69111 will be output to the event log and recovery triggered. For details on the above message, refer to "Message number 69111" in "Messages".
- The status of the primary server is "unknown"
- The period with no response to the ping command is over the time-out value
- The active server has not been placed into maintenance mode
- The power of the chassis is not OFF (when using PRIMERGY BX servers)
Note
As this setting uses ping monitoring on the admin LAN, recovery may be triggered even when operations are being performed.
With target servers, if another Resource Orchestrator operation is being performed when recovery is triggered, recovery will not take place and monitoring will recommence.
If the configured recovery process occurs and restoration is not possible, monitoring of the server will be suspended temporarily. After that, when the status of the server becomes "normal", monitoring will recommence.
For VMware ESXi, this function is not supported.
If server switchover is performed during recovery, even if a memory dump was set to be collected in the event of an OS failure, the memory dump will not be collected.
The time-out period for ping monitoring should be set as a value between 5 and 3,600 seconds.
One of conditions for recovery is that the amount of time for which there is no response to the "ping" command exceeds the specified time-out value.
Select a recovery operation from the following:
Reboot
Perform reboot.
Reboot (Forced)
Perform forced reboot.
Switchover (*)
Perform a switchover operation based on the spare server settings.
Reboot+Switchover (*)
First, perform reboot.
Reboot operations are only performed the number of times specified in the Number of reboots, and recovery operations end if it is recovered during the reboot cycle.
Perform switchover if recovery is not successful even after rebooting the specified number of times.
If a spare server has not been set, only rebooting will take place.
Reboot(Forced)+Switchover (*)
First, perform forced reboot.
Forced reboot operations are performed only the number of times specified in the Number of reboots, and recovery operations end if it is recovered during the reboot cycle.
Perform switchover if recovery is not successful even after forced rebooting the specified number of times.
If a spare server has not been set, only forced rebooting will take place.
Specify the number of reboots or forced reboots as a number between one and three. When specifying twice or more, recovery will not be implemented when restoring.
Click the [OK] button.
* Note: Recovery operations including server switchover cannot be performed with PRIMEQUEST, SPARC Enterprise partition models with divided areas, or SPARC M10/M12 in Building Block configurations.
