AudioCodes Mediant 600 - Multiple Network Interfaces and VLAN Parameters

SIP User's Manual 544 Document #: LTRT-83310
Mediant 600 & Mediant 1000
A.1.2 Multiple Network Interfaces and VLAN Parameters
The IP network interfaces and VLAN parameters are described in the table below.
Table A-2: IP Network Interfaces and VLAN Parameters
Parameter Description
Multiple Interface Table
Web: Multiple Interface Table
EMS: IP Interface Settings
[InterfaceTable]
This parameter table configures the Multiple Interface table for
configuring logical IP addresses. The format of this parameter is
as follows:
[InterfaceTable]
FORMAT InterfaceTable_Index =
InterfaceTable_ApplicationTypes,
InterfaceTable_InterfaceMode, InterfaceTable_IPAddress,
InterfaceTable_PrefixLength, InterfaceTable_Gateway,
InterfaceTable_VlanID, InterfaceTable_InterfaceName,
InterfaceTable_PrimaryDNSServerIPAddress,
InterfaceTable_SecondaryDNSServerIPAddress,
InterfaceTable_UnderlyingInterface;
[\InterfaceTable]
For example:
InterfaceTable 0 = 0, 0, 192.168.85.14, 16, 0.0.0.0, 1,
Management;
InterfaceTable 1 = 2, 0, 200.200.85.14, 24, 0.0.0.0, 200,
Control;
InterfaceTable 2 = 1, 0, 211.211.85.14, 24, 211.211.85.1, 211,
Media;
The above example, configures three network interfaces
(OAMP, Control, and Media).
Notes:
 For this parameter table to take effect, a device reset is
required.
 Up to 16 logical IP addresses with associated VLANs can be
defined (indices 0-15).
 Each interface index must be unique.
 Each interface must have a unique VLAN ID.
 Each interface must have a unique subnet.
 Subnets in different interfaces must not overlap (e.g.,
defining two interfaces with 10.0.0.1/8 and 10.50.10.1/24 is
invalid). Each interface must have its own address space.
 Upon device start up, this table is parsed and passes
comprehensive validation tests. If any errors occur during
this validation phase, the device sends an error message to
the Syslog server and falls back to a “safe mode”, using a
single IPv4 interface and without VLANs. Therefore, check
the Syslog for any error messages.
 When booting using BootP/DHCP protocols, an IP address is
obtained from the server. This address is used as the OAMP
address for this session, overriding the address configured
using the InterfaceTable. The address specified for OAMP
applications in this becomes available when booting from
flash again. This enables the device to work with a
temporary address for initial management and configuration
while retaining the address to be used for deployment.