Assigning An Ip Address For Mediant 3000 Ha - AudioCodes Mediant 3000 User Manual

Voip media gateway
Hide thumbs Also See for Mediant 3000:
Table of Contents

Advertisement

SIP User's Manual
2.4

Assigning an IP Address for Mediant 3000 HA

This section describes how to assign IP addresses to the Mediant 3000 HA, using BootP
and the Web interface (refer to 'Using the Web Interface' on page 32), or using
AudioCodes EMS management tool (refer to 'Using the EMS' on page 34).
The Mediant 3000 HA houses two TP-6310 or TP-8410 blades (one active, the other
redundant). These two blades each have a private IP address (different from one another)
used for initial configuration, maintenance, or fallback in case of major device problem
which prevents it from operating in HA mode. When initially configuring the blades (using
BootP/DHCP), the BootP server communicates with the blades using these two IP
addresses.
In addition to the private IP addresses, the device has "global" (public) IP addresses, used
by the active blade for communicating with the IP network (i.e., OAMP, Media, and Control
interfaces). These global IP addresses can be configured using the ini file, Web, or EMS
management tools.
The global IP addresses are valid IP addresses that are different to that of the private IP
address of each blade. From the perspective of the WAN interface (e.g., proxy server), the
two blades have the same IP address (global IP address) and the redundant blade is a
transparent entity.
Parameter
Private IP Addresses
Subnet Mask
Global IP Address
Notes:
Version 6.4
Table 2-1: Default IP Addresses
Blade in Slot 1: 10.1.10.10
Blade in Slot 3: 10.1.10.11
255.255.0.0
0.0.0.0
Ensure that both blades are connected to the network.
Ensure that your IP addressing scheme does not include the blades'
default private IP addresses. These are internal, default IP addresses
reserved for the two blades. You must assign a new private IP address to
each blade according to your organization's IP addressing scheme.
The global IP addresses must be different from the private IP addresses
of the blades.
It is recommended to define the private IP addresses of the blades in the
same subnet as the device's OAMP interface. This allows the blades to
send reports to a Syslog server in case of major device failure..
You can also assign private IP addresses to the blades using CLI, as
described in 'Using CLI' on page 27.
2. Assigning the VoIP LAN IP Address
Default Value
31
November 2011

Advertisement

Table of Contents
loading

Table of Contents