System Boot
Whenever your Oracle Enterprise Communications Broker boots, the following information about the tasks and settings for the system appear in your terminal window.
- System boot parameters
- From what location the software image is being loaded: an external device or internal flash memory
- Requisite tasks that the system is starting
- Log information: established levels and where logs are being sent
- Any errors that might occur during the loading process
After the loading process is complete, the ACLI login prompt appears.
Note:
You can set boot parameters using the ACLI or the GUI. Boot parameter definitions, which help you understand what you should set them to, are provided below.Oracle Enterprise Communications Broker Boot Parameters
Boot parameters specify the information that your Oracle Enterprise Communications Broker uses at boot time when it prepares to run applications. The Oracle Enterprise Communications Broker’s boot parameters:
- Allow you to set the IP address for the management interface (wancom0).
- Allow you to set a system prompt. The target name parameter also specifies the title name displayed in your web browser and SNMP device name parameters.
- Determine the software image to boot and from where the system boots that image.
- Sets up the username and password for network booting from an external FTP server.
In addition to providing details about the Oracle Enterprise Communications Broker’s boot parameters, this section explains how to view, edit, and implement them.
When displaying the boot parameters, your screen shows a help menu and the first boot parameter (boot device). Press Enter to continue down the list of boot parameters.
Upload the Stage 3 Boot Loader and System Image
Whenever you upgrade the software image, upload the Stage 3 boot loader and the new system image file to the system.
The Stage 3 boot loader is generally backward compatible with previous releases, but Oracle recommends that you install the Stage3 boot loader from the same Major.Minor version as the system image. It is not normally necessary to update the boot loader when installing a maintenance or patch release when the Major.Minor release is the same.
System upgrades typically consist of transferring the new system
image and Stage 3 boot loader to the system and setting boot parameters to the
new system software. To ensure compatibility, copy the Stage 3 boot loader to
/boot/bootloader
before you update the boot parameters to use the new software image file. You
must name the boot loader file
/boot/bootloader on
the target system with no file extension. When upgrading an HA pair, you must
perform the upgrade procedure on each HA node.
Use the following procedure to upload the Stage 3 boot loader and system image.
- Obtain the Stage 3 boot loader image file (*.boot).
-
Upload the Stage 3
boot loader image file (*.boot) as
/boot/bootloaderto your system using an SSH File Transfer Protocol (SFTP) client. - Upload the new system software image (*.bz) to /boot/.
- Validate the boot loader by rebooting the Oracle Enterprise Communications Broker after renaming the boot loader.
[Downloads]$ ls -la total 148820 drwxr-xr-x 2 bob src 4096 Jun 17 15:16 . drwxr-xr-x 28 bob src 4096 May 21 14:17 .. -rw-r--r-- 1 bob src 10164527 Jun 17 15:15 nnPCZ300.64.boot -rw-r--r-- 1 bob src 73849839 Jun 17 15:15 nnPCZ300.64.bz [Downloads]$ sftp admin@123.45.67.890 admin@123.45.67.890's password: Connected to 123.45.67.890. sftp> cd /boot sftp> put nnPSCZ300.64.boot Uploading nnPCZ300.64.boot to /boot/nnPCZ300.64.boot nnPCZ300.64.boot 100% 9926KB 9.7MB/s 00:01 sftp> rm /boot/bootloader sftp> rename nnPCZ300.64.boot /boot/bootloader sftp> put nnPCZ300.64.bz Uploading nnPCZ300.64.bz to /boot/nnPCZ300.64.bz nnPCZ300.64.bz 100% 70MB 14.1MB/s 00:05 sftp> bye Received disconnect from 123.45.67.890: 11: Logged out. [Downloads]$
Note:
The Stage 3 boot loader is ready for operation after upload and filename change, but validating it before booting the new system software is good practice.Boot Parameter Changes
You can access and edit boot parameters by using either the ACLI or by interrupting the system boot process.
Note:
Changes to boot parameters do not go into effect until you reboot the Oracle Enterprise Communications Broker.- directly a part of your LAN for management port 0
- accessible through management port 0
Set Boot Parameters Wizard
The Oracle Enterprise Communications Broker (OECB) requires you to enter the necessary parameters to boot the system in your deployment.
You can set the OECB boot parameters from the Set Boot Parameters Wizard on the Web GUI in either Basic mode or Expert mode.
Change Boot Parameters by Interrupting a Boot in Progress
To access and change boot parameters by interrupting a boot in progress:
Set Management IP Address
You must manually set your management IP address within the Oracle Enterprise Communications Broker's boot parameters.
To set your management interface IP, access the boot parameters using a serial console connection within the context of one of the methods described above.
- Type the letter c (change) to start boot parameter editing.
- Press Enter until you reach the parameter named IP Address.
- Type in the desired IP address.
- Press Enter until you reach the end of the boot parameter list.
- Reboot your Oracle Enterprise Communications Broker.
After being set, the management interface IP address provides access to your system via ssh and the web GUI. You can verify the status of this interface using the following command to display the address and status of wancom0.
Oracle ECB# show interfaces brief Slt Prt Vlan Interface IP Gateway Adm Oper Num Num ID Name Address Address Stat Stat --- --- ---- ---------- ---------------------- ------------------- ---- ---- - - - lo 127.0.0.1 - up up - - - wancom0 122.30.204.127/16 - up up 0 0 0 M00 122.170.1.200/16 0.0.0.0 up up ---------------------------------------------------------------------------- Oracle ECB#
