| Skip Navigation Links | |
| Exit Print View | |
|
Oracle Solaris Cluster Data Service for DHCP Guide |
1. Installing and Configuring HA for DHCP
Overview of Installing and Configuring HA for DHCP
Planning the HA for DHCP Installation and Configuration
Restriction for the supported configurations of HA for DHCP
Restriction for the location of DHCP files
Required /etc/inet/dhcpsvc.conf parameters.
Installing and Configuring DHCP
How to Install and Configure DHCP
Verifying the Installation and Configuration of DHCP
How to Verify the Installation and Configuration of DHCP
Installing the HA for DHCP Packages
How to Install the HA for DHCP Packages
Registering and Configuring HA for DHCP
How to Register and Configure HA for DHCP
Verifying the HA for DHCP Installation and Configuration
How to Verify the HA for DHCP Installation and Configuration
How to Upgrade to the New Version of HA for DHCP
This section describes the HA for DHCP fault monitor probing algorithm or functionality, states the conditions, and recovery actions associated with unsuccessful probing.
For conceptual information on fault monitors, see the Oracle Solaris Cluster Concepts Guide.
The HA for DHCP fault monitor uses the same resource properties as resource type SUNW.gds. Refer to the SUNW.gds(5) man page for a complete list of resource properties used.
The HA for DHCP fault monitor is controlled by the extension properties that control the probing frequency. The default values of these properties determine the preset behavior of the fault monitor. The preset behavior should be suitable for most Solaris Cluster installations. Therefore, you should tune the HA for DHCP fault monitor only if you need to modify this preset behavior.
Setting the interval between fault monitor probes (Thorough_probe_interval)
Setting the timeout for fault monitor probes (Probe_timeout)
Setting the number of times the fault monitor attempts to restart the resource (Retry_count)
The HA for DHCP fault monitor checks within an infinite loop. During each cycle the fault monitor will perform a check and report either a failure or success.
If the fault monitor is successful it returns to its infinite loop and continues the next cycle of probing and sleeping.
If the fault monitor reports a failure a request is made to the cluster to restart the resource. If the fault monitor reports another failure another request is made to the cluster to restart the resource. This behavior will continue whenever the fault monitor reports a failure.
If successive restarts exceed the Retry_count within the Thorough_probe_interval a request to failover the resource group onto a different node or zone is made.
Test whether PNM (Public Network Monitoring) has changed the active interface for the network that DHCP is using. If this fails, then the probe will restart the DHCP resource.
|