AudioCodes Mediant 3000, User Manual

Page: 36 / 872

User's Manual 36 Document #: LTRT-89729
Mediant 3000
d. Power down the chassis.
e. Power up the chassis and wait about 20-30 seconds, and then power down and
power up the chassis once again within 15 seconds; both blades send a BootP
request to the network and the BootP server sends the new private IP addresses
to the blades.
f. In AcBootP, verify after about 15 seconds that both blades have received their
new private IP addresses.
2. Define the global IP address:
a. Access the Web interface with the IP address that you assigned to the blade in
Slot 1.
b. Open the Multiple Interface Table page ( Configuration tab > VoIP menu >
Network submenu > IP Settings ).
c. Click the Add Index button and define global IP addresses for the OAMP, Media,
and Control application types, as desired.
d. Click Apply , and then click Done to validate your settings.
e. Save your settings to the device's flash memory with a device reset; the new
global IP address is saved to flash memory and the device resets, entering HA
mode with active and redundant blades. Note that the Web interface session
terminates as it is no longer accessible through the blade's private IP address.
3. Re-access the Web interface with the new, global IP address that you assigned the
device for the OAMP interface; the device is now accessed through the active blade in
Slot 1.
Note: If at a later stage, you need to change the global IP address, and the current
and new global IP address are in different subnets, then it’s recommended to
also define the private addresses of the blades in the same subnet as the
new global IP address. This allows the blades to send reports to a Syslog
server in case of major device failure.
2.4.2 EMS
The procedure below describes how to initially assign a global IP address to Mediant 3000
HA using AudioCodes EMS management tool.

To initially assign a global IP address to Mediant 3000 HA using the EMS:
1. Power down the chassis.
2. Ensure that both blades are connected to the network.
3. Power up the chassis.
4. Assign new private IP addresses to the two blades:
a. Start a BootP server application and add a client configuration with the following
settings:
a. Create two entries, one for each blade, where each entry defines the new
private IP address of each blade.
b. Define the path to the .cmp file.
Note: When loading the device from BootP, the HA mode is disabled.