Set Up High Availability Mode

Previous Next JavaScript must be enabled to correctly display this content

Set Up High Availability Mode

Use the following procedure to configure High Availability (HA) on a primary and secondary Oracle Enterprise Communications Broker (ECB).

Confirm that you own an HA license.

In the following procedure, enter y to discard any changes and quit the initialization. The system displays the root prompt.

The run setup command warns you that it overwrites (erases) the existing running configuration. If you want to back out of the setup process and not overwrite the current running configuration, you can enter q or enter No at the Erase config and proceed prompt. The root prompt displays.

Note:

For HA environments, running setup on the secondary system is also required to set the wancom0 address and secondary targetname. The targetname must match the same secondary targetname specified on the primary system.

To configure the primary ECB for HA :

In Superuser mode, type run setup, and press Enter.
```
ORACLE# run setup
```
Type yes to continue the setup process, and press Enter.

Type 2 to configure an HA device, and press Enter.

Enter choice [1 - standalone] 	:2

The system displays the following:

=========================================================
This ECB may be a standalone or part of a highly available redundant pair.
ECB role
	1. primary
	2. secondary
Enter choice [1-primary]		:
=========================================================

Enter 2, and press Enter.

Enter choice [1-primary]		:2

The system displays the following:

=========================================================
SBC SETTINGS
Unique target name of this ECB [ECB name>] 	:
=========================================================

Type a unique target name for the ECB (or keep the default in [ ]), , and press Enter.
```
Unique target name of this ECB [ECB1] 	:NNESD2
```
The system displays the following:
```
=========================================================
SBC SETTINGS
IP address on management interface [<ECB IP address>] :
=========================================================
```
Note:
The setup process provides default IP addresses for the HA primary and secondary peers (Redundancy interface address and Peer IP address ). These default addresses are link-local addresses as specified in RFC 3927, Dynamic Configuration of IPv4 Link-local addresses.
Type the IP address on the management interface of the secondary Web Server (or keep the default in [ ]), , and press Enter.
```
IP address on management interface [<ECB IP address>] 	: 164.30.85.52
```
The system displays the following:
```
Subnet mask [255.255.0.0] :
=========================================================
```

Type the subnet mask of the secondary Web Server (or keep the default in [ ]), , and press Enter.

Subnet mask [255.255.0.0] 	: 255.255.0.0

The system displays the following:

=========================================================
Gateway IP address [164.30.0.1] 	:
=========================================================

Type the gateway IP address of the secondary Web Server (or keep the default in [ ]), and press Enter.

Gateway IP address [<SBC gateway address>] 	: 164.30.0.1

The system displays the following:

=========================================================
AUTOMATIC CONFIGURATION
Acquire config from the Primary (yes/no) [yes]	:
=========================================================

Type y for the secondary HTTP Server to acquire the configuration from the primary Web Server during switchover, and press Enter.

Type s to save the configuration, and press Enter. Or, Select an item number from the summary view to modify the value for that item. Or, type q to exit.

Enter 1 - 16 to modify, 'd' to display summary, 's' to save, 'q' to exit. [s]	:s

The system displays the following:

=========================================================
Saving changes and quitting wizard. Are you sure?  [y/n]?	:
=========================================================

Type y to verify you want to save the configuration, and press Enter.

he system displays the following:

=========================================================
Running configuration is backed up as 'bkup_setup_wizard_Mar__7_13_58_26_545.gz'
******************************************************
Deleting configuration
Erase-Cache received, processing.
waiting 1200 for request to finish
Request to 'ERASE-CACHE' has Finished,
Erase-Cache: Completed
Request to 'RESTORE-CONFIG' has Finished,
Restore Backup Completed Successfully
checking configuration
Save-Config received, processing.
waiting for request to finish
Request to 'SAVE-CONFIG' has Finished,
Save complete
Currently active and saved configurations do not match!
To sync & activate, run 'activate-config' or 'reboot activate'.
---------------------------------------------------------------------
Verification successful! No errors nor warnings in the configuration
Activate-Config received, processing.
waiting for request to finish
Request to 'ACTIVATE-CONFIG' has Finished,
Activate Complete
You may access the GUI via http://164.30.85.52:80/ after reboot.
=========================================================

You have completed the run setup .

Run run setup on the secondary peer of the HA pair.