System Watchdog Timer

The Oracle Communications Session Border Controller's watchdog timer ensures that the system will reset itself if it becomes unstable. If a set period of time elapses before the timer is reset by another process, the system will initiate a hardware reset. The watchdog timer expires after 31 seconds. This period is not configurable.

The watchdog process runs at a very high priority so that it is always active. As long as other essential processes are running, the watchdog timer will be reset before it expires. If an essential system process encounters a problem, forcing the system software to hang or enter into an unstable state, the watchdog timer will not be reset. As a consequence, the watchdog timer will expire, and the system will reboot.

Watchdog Timer Configuration

The watchdog timer has the following five configuration features:

The watchdog state is persistent across reboot.
The watchdog timer is disabled by default.
Changes to the watchdog timer state are activated in real time.
The watchdog timer state can only be changed from ACLI Superuser mode.
The watchdog timer state can be viewed from ACLI Superuser and User modes.

ACLI Example

The following template shows the usage of the watchdog command.

ORACLE# watchdog [enable | disable | fetch]

enable—enables the watchdog timer
disable—disables the watchdog timer
fetch—prints the current state of the watchdog timer to the screen
To enable the watchdog timer on your Oracle Communications Session Border Controller:

Enter the Superuser mode in the ACLI.
```
ORACLE#
```
Type watchdog <space> enable and press Enter to enable the watchdog timer.
```
ORACLE# watchdog enable
Watchdog timer started
ORACLE#
```
Type watchdog <space> fetch and press Enter to confirm that the watchdog timer has been enabled.
```
ORACLE# watchdog fetch
Watchdog timer is enabled
ORACLE#
```