AudioCodes Mediant 1000 User Manual page 113

SIP User's Manual
rules may be specified in the Routing table ('Configuring the IP Routing Table' on page
118).

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).

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 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
traffic from the interface which VLAN ID equals to the 'Native' VLAN ID are tagged
with VLAN ID 0 (priority tag).

Quality of Service parameters specify the priority field for the VLAN tag (IEEE 802.1p)
and the DiffServ field for the IP headers. These specifications relate to service
classes.

When booting using BootP/DHCP protocols, the address received from the
BootP/DHCP server acts as a temporary OAMP address, regardless of the address
specified in the Multiple Interface table. This configured address becomes available
when booting from flash.

Network Configuration changes are offline. The new configuration should be saved
and becomes available at the next startup.
Upon system start up, the Multiple Interface 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 interface and
no VLANs. Ensure that you view the Syslog messages that the device sends in system
startup to see if any errors occurred.
Note:
10.3.1.1.5 Troubleshooting the Multiple Interface Table
If any of the Multiple Interface table guidelines are violated, the device falls back to a "safe
mode" configuration, consisting of a single IPv4 interface without VLANs. For more
information on validation failures, consult the Syslog messages.
Validation failures may be caused by one of the following:

One of the Application Types (OAMP, CONTROL, MEDIA) is missing in the IPv4
interfaces.

There are too many interfaces with "Application Types" of OAMP. Only one interface
defined but the "Application Types" column is not set to "OAM + Media + Control"
(numeric value 6).
Version 6.4
When configuring the device using the Web interface, it is possible to perform
a quick validation of the configured Multiple Interface table and VLAN
definitions, by clicking the Done button in the Multiple Interface Table Web
page. It is highly recommended to perform this when configuring Multiple
Interfaces and VLANs, using the Web Interface to ensure the configuration is
complete and valid.
113
10. Network
March 2012