Booting an Image

You can either boot your Oracle® Enterprise Session Border Controller from the system’s local storage or from an external device. Both locations can store images from which the system can boot. This section describes both booting methods.

For boot parameters to go into effect, you must reboot your Oracle® Enterprise Session Border Controller. Since a reboot stops all call processing, Oracle recommends performing tasks that call for a reboot during off-peak hours. If your Oracle® Enterprise Session Border Controllers are set up in an HA node, you can perform these tasks on the standby system first.

Boot Parameter Definitions

The system displays all boot parameters when you configure them after a boot interrupt. The system hides some boot parameters from the ACLI so that you do not attempt to configure them. If changed improperly, these parameters can cause the system to sop responding.

The following table defines each of the parameters that the system displays when you perform configuration after a boot interrupt.

Boot Parameter Description
Boot File The name and path of the software image you are booting. Include the absolute path for a local boot from the local /boot volume and for a net boot when a path on the FTP server is needed.
IP Address IP address of wancom0.
VLAN VLAN of management network over which this address is accessed.

Note: VLANs over management interfaces are not supported on the Acme Packet 4600, Acme Packet 3900, and Acme Packet 6xxx.

Netmask Netmask portion of the wancom0 IP Address.
Gateway Network gateway that this wancom0 interface uses.
IPv6 address Version 6 IP address/mask of wancom0. Configure the mask as a forslash (/) after the address followed by the mask in number of bits.
IPv6 Gateway Version 6 network gateway that this wancom0 interface uses.
Host IP IP Address of FTP server from which to download and execute a software image.
FTP Username FTP server username
FTP password FTP server password
Flags Codes that signal the system from where to boot. Also signals the system about which file to use in the booting process. This sequence always starts with 0x (these flags are hexadecimal).
Target Name Name of the Oracle® Enterprise Session Border Controller as it appears in the system prompt. For example, ORACLE> or ORACLE#. You need to know the target name if you are setting up an HA node.

This name must be unique among Oracle® Enterprise Session Border Controllers in your network. This name can be 63 characters or less.

Console Device Serial output device type, dependent on platform. COM1 applies to virtual serial consoles, VGA to virtual video console. VGA is the default on VMware and KVM. COM1 is the default on OVM .
Console Baud Rate The speed in bits per second which the console port operates at. It operates at 115200 BPS, 8 data bits, no stop bit, parity NONE.
Other Allows miscellaneous and deployment-specific boot settings.

Booting from Flash Memory

Once you have installed an image, you can boot your Oracle® Enterprise Session Border Controller from its flash memory. With the exception of testing an image before you install it on the flash memory, this is generally the method you use for booting.

To boot from your Oracle® Enterprise Session Border Controller flash memory:

  1. Confirm that the boot parameters are set up correctly, and make any necessary changes.

    You can check the boot configuration parameters by accessing the bootparam command from the configure terminal menu.

    ORACLE# configure terminal
    ORACLE# bootparam
  2. Change any boot configuration parameters that you need to change. It is especially important to change the file name boot configuration parameter. The file name parameter needs to use the /boot value so that the Oracle® Enterprise Session Border Controller boots from the flash.
  3. Reboot your Oracle® Enterprise Session Border Controller.
  4. You are be returned to the ACLI login prompt. To continue with system operations, enter the required password information.