Initialization Process; Configuration Stages - AudioCodes Mediant 3000 User Manual

interfaces to the redundant 6310 blade in the front panel's Slot 3. The redundant blade
is not connected to the external network. It only has an internal link with the active
blade. In other words, the user doesn't interact directly with the redundant blade. This
link controls the HA feature and is automatically and internally configured.
Two GbE links can be connected to each VoP blade through their corresponding RTMs
(i.e., for TP-6310: RTM-6310 for the active TP-6310; RTM-6310 Redundant for the
redundant TP-6310). At least one link per VoP blade must be connected, but two links are
recommended for LAN redundancy. After system initialization is complete, network access
is available only to the active blade. The redundant GbE links have no network access.
Each blade (Active and Redundant) has its own private, local IP address (acquired from
BootP/DHCP), which is used only for maintenance. This private address is also used as a
fallback in case of major system problem which prevents the system from working in HA
mode. Typically, this IP address is configured only once (on first time installation of the
system). Afterwards, it can be changed only through BootP/DHCP.
For normal operation, the HA device uses "global" IP address(es). These are the IP
addresses that are used by the Active blade for Media, OAMP and Control interfaces.
These IP addresses are configured in the Multiple Interface table.
1.1.1

Initialization Process

If both VoP blades are already installed when the device powers up, the VoP blade in Slot
1 always initially serves as the active blade, while the VoP blade in Slot 3 serves as the
redundant blade. The active blade is identified by its ACT LED being lit green. If only one
blade is installed, (no matter which slot it occupies), it always assumes the active blade. If
at a later time, a second VoP blade is added, this second blade serves as the redundant
blade.
Synchronization between active and redundant VoP blades may take several minutes in
which the active blade forwards to the redundant blade all its current configuration data.
This data includes files such as voice prompt, call progress tone, and even its software
(cmp file). If necessary, a second boot of the redundant blade is issued to apply the new
configuration.
After the synchronization is complete, the redundant blade is identified by a blinking yellow
light in the ACT LED.
Note: When the active blade synchronizes with the redundant blade, all configuration
1.1.2

Configuration Stages

For the device to be configured for HA, the following installation stages must be performed:

Hardware configuration setup (refer to Mediant 3000 and IPmedia 3000 Installation
Manual). The system can be set up initially with only one VoP blade and one SA/M3K
blade. However, HA mode is only functional when a second VoP blade and a second
SA/M3K blade are added.

Software Upgrade Key includes the HA feature and is installed on both VoP blades
(see 'Loading Software Upgrade Key' on page 493). (If the HA feature is specified at
the time the system was purchased, then it's already included on both blades).

The device's global IP addresses (i.e., Control, Media, and OAMP) are defined (using
the Multiple Interface table) for the active blade to a valid IP address that is different to
that of the local IP addresses of the blades. In the HA system, when the blades are
initially configured using BootP, the BootP communicates with the two blades using
two different local IP addresses: one for the active and one for the redundant blade.
SIP User's Manual
changes (e.g., parameter modifications and uploading of files) are blocked
until this process completes and the system is in High Availability mode.
20
Mediant 3000
Document #: LTRT-89712