AudioCodes Mediant 3000 User Manual page 117

SIP User's Manual
10.3.1.1.5 Multiple Interface Table Configuration Summary and Guidelines
Multiple Interface table configuration must adhere to the following rules:

Up to 32 different interfaces may be defined.

The indices used must be in the range between 0 and 31.

Each interface must have its own subnet. Defining two interfaces with addresses in
the same subnet (i.e. two interfaces with 192.168.0.1/16 and 192.168.100.1/16) is
illegal.

Subnets in different interfaces must not be overlapping in any way (i.e. 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.

The Prefix Length replaces the dotted decimal Subnet Mask presentation. This column
must have a value of 0-30 for IPv4 interfaces and a value of 64 for IPv6 interfaces.

Only one OAMP interface must be configured, and this must be of address type IPv4.
This OAMP interface can be combined with Media and Control interfaces.

At least one IPv4 interface with CONTROL "Application Types" must be configured.

At least one IPv4 interface with MEDIA "Application Types" must be configured.

One or more IPv6 interface with CONTROL "Application Types" may be configured.
One or more IPv6 interface with MEDIA "Application Types" may be configured.

The application types may be mixed, for example:
•
One IPv4 interface with "Application Types" OAMP, MEDIA & CONTROL plus
one IPv6 interface with "Application Types" MEDIA & CONTROL (without
VLANs).
•
One IPv4 interface with "Application Types" OAMP, one other or more IPv4
interfaces with "Application Types" CONTROL, and one or more IPv4 interfaces
with "Application Types" MEDIA (with VLANs).
•
One IPv4 interface with "Application Types" OAMP & MEDIA, one other or more
IPv4 interfaces with "Application Types" MEDIA & CONTROL, zero or more IPv6
interfaces with "Application Types" MEDIA & CONTROL (with VLANs).
•
Other configurations are also possible while keeping to the above-mentioned rule.

Each network interface may be defined with a default gateway. This default gateway
address must be in the same subnet as the associated interface. Additional routing
rules may be specified in the Routing table ('Configuring the IP Routing Table' on page
130).

The Interface Name column may have up to 16 characters. This column allows the
user to name each interface with an easier name to associate the interface with. This
column must have a unique value to each interface and must not be left blank.

Primary and Secondary DNS server address may be configured for each interface.
Note: Currently, the device supports DNS configuration for only one interface.

For IPv4 interfaces, the "Interface Mode" column must be set to "IPv4 Manual"
(numeric value 10). IPv6 Interfaces "Interface Mode" can be set to either "IPv6
Manual" (numeric value 4) or "IPv6 Manual Prefix" (numeric value 3).

When defining more than one interface of the same address family, VLANs must be
enabled (the VlanMode should be set to 1).

VLANs become available only when booting the device from flash. When booting
using BootP/DHCP protocols, VLANs are disabled to allow easier maintenance
access. In this scenario, multiple network interface capabilities (including IPv6) are
unavailable.

The Native' VLAN ID may be defined using the 'VlanNativeVlanId' parameter. This
relates untagged incoming traffic as if reached with a specified VLAN ID. Outgoing
Version 6.4 117
10. Network
November 2011