|
[Watchdog]
|
Description
|
Factory value
|
|---|---|---|
|
AutoSwitch
|
If the AutoSwitch parameter is set to yes, the Watchdog automatically does the following:
If the Secondary server fails, then the Watchdog tells the Primary server to switch to PRIMARY ALONE state (rather than stay in PRIMARY UNCERTAIN) state.
If the Primary server fails, then the Watchdog automatically sends the commands:
'hsb switch primary' 'hsb set primary alone'
to switch the original Secondary to be the new Primary.
For example:
[Watchdog]
AutoSwitch = NO This parameter is optional.
|
Yes
|
|
Connect1
|
The Connect1 parameter in the [Watchdog] section enables the Watchdog application to connect to the Primary or Secondary server. This is a required parameter that defines the protocol and network address for the Connect1 server.
For example:
connect1 = tcp primarymachine 1313
|
None
|
|
Connect2
|
The Connect2 parameter in the [Watchdog] section enables the Watchdog application to connect to the Primary or Secondary server. This is a required parameter that defines the protocol and network address for the Connect2 server.
For example:
connect2 = tcp secondarymachine 1313
|
None
|
|
DualSecAutoSwitch
|
If DualSecAutoSwitch = Yes and both servers are secondary, then the Watchdog will automatically select one of the two secondaries to be a new primary and switch it to primary. If DualSecAutoSwitch = No then the system administrator must switch one server to be the primary. Note that DualSecAutoSwitch applies whether the Watchdog is in “normal” mode or “failure” mode.
|
Yes
|
|
NumRetry
|
The NumRetry parameter in the [Watchdog] section lets you specify the number of Watchdog attempts to connect to a Secondary or Primary server before the connection attempt is considered a response failure or error.
For example:
[Watchdog]
NumRetry = 3 The retries are in addition to the original try. If number of retries is set to 3, then the total number of attempts is 4. Note that the retries are immediate. The Watchdog does not wait for an interval of time (such as PingTimeout) in between retries when there is a failure.
This parameter is optional.
|
0
|
|
Password1 Password2
|
See the description of the Username1 and Username2 parameters below.
|
No factory value.
|
|
PingInterval
|
The PingInterval parameter in the [Watchdog] section lets you specify the interval in milliseconds between querying status connect information in normal Watchdog mode. To detect server failure, the Watchdog sends the hotstandby status connect command to both Primary and Secondary servers after every PingInterval milliseconds.
For example:
[Watchdog]
PingInterval = 5000 This parameter is optional.
Note that the PingInterval parameter for the Watchdog is different from the PingTimeout parameter for the servers.
CAUTION: Previous sample Watchdogs required that the PingInterval be specified in seconds, not milliseconds. If you are using an older solid.ini file, you should update it.
|
1000
(1 second)
|
|
Username1 Username2
|
The Username and Password parameters in the [Watchdog] section are optional. They specify the username and password that are authorized for using the connect1 server.
For example:
[Watchdog]
Username1 = Tom Password1 = dr17xy Username2 = Jerry Password2 = M89tvt If (for security reasons) these parameters are not specified in the solid.ini configuration file, the Watchdog will prompt for them when the Watchdog is started.
|
No factory value.
|
|
WatchdogLog
|
The WatchdogLog parameter in the [Watchdog] section lets you specify the file name of the Watchdog log. The Watchdog log is created in the current working directory. It is used to record Watchdog messages, alerting administrators of the need to issue Watchdog commands.
For example:
[Watchdog]
WatchdogLog = Watchdog.log Note that quotation marks around the file name are not required (as long as it does not contain special characters such as the blank or certain punctuation marks).
This parameter is optional.
|
Watchdog.log
|