Rebooting the SBC
The reboot command is used to reboot the Oracle Communications Session Border Controller system. There are three modes you can use to reboot your Oracle Communications Session Border Controller. Different modes determine which configurations are used to boot your system.
reboot activate
The reboot activate command reboots the system with the last saved current configuration. This command is useful if changes have been made and saved to the system configuration but that configuration has not yet been activated and the system goes out of service.
In terms of making the current configuration into the running configuration, using this command is the same as using the activate-config command.
reboot fast
On VM/server-based platforms, the fast argument has been added to the reboot command. The reboot fast (VM only) command reboots the system using the last running configuration and does not reinvoke the bootloader.
reboot force
The reboot force command reboots the system using the last running configuration. This command does not require you confirm the reboot directive. The boot sequence begins immediately after issuing this command.
reboot force activate
The reboot force activate command reboots the system using the last saved current configuration. This command does not require you confirm the reboot directive. The boot sequence begins immediately after issuing this command.
Like the reboot activate command, reboot force activate allows you to activate the current configuration that has been saved but not previously activated. Reboot force activate is the same as issuing the activate-config command and then a reboot force.
| reboot Subcommand | Description |
|---|---|
| reboot activate | This subcommand reboots the Oracle Communications Session Border Controller and activates the newly saved configuration. |
| reboot force | This subcommand reboots the Oracle Communications Session Border Controller and loads the last running configuration without confirmation. |
| reboot force activate | This subcommand reboots the Oracle Communications Session Border Controller and activates the newly saved configuration without confirmation. |
Reboot Safeguards
The ACLI's reboot command has safeguards to prevent it from being executed in one ACLI session when certain key processes are in progress in another ACLI session.
Attempting to reboot the Oracle Communications Session Border Controller while a key process is in progress in another ACLI session will result in a warning and notification message that appears on the console. The message informs you that another ACLI session is manipulating the system configuration if any of the following commands/processes are executed:
- save-config
- backup-config
- restore-backup-config
- delete-backup-config
- delete-config
Reboot Status File
The delete-status-file command removes the taskcheckdump.dat and statsDump.dat files on the Oracle Communications Session Border Controller. These files contains information from Oracle Communications Session Border Controller system failures.
The system writes status information to the statsDump.dat file before the system reboots itself. Oracle uses the status file to gather information about why a system rebooted itself for debugging and/or technical service purposes. To carry out this command, type delete-status-file into the command line and press Enter.
Warning on Reboot
The Oracle Communications Session Border Controller issues a warning when you attempt to reboot the system without having saved configuration changes. If you encounter this warning, you can simply save your configuration (using the ACLI save-config command), and then proceed with the reboot. If you want to reboot without saving changes, you can confirm to the reboot but any changes to the configuration (made since the last save) will be lost).