10.9.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 and no 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 "O+M+C" (numeric value 6).
An IPv4 interface was defined with "Interface Type" different than "IPv4 Manual" (10).
Gateway column is filled in more than one row of the same address family.
Gateway is defined in an interface not having MEDIA as one of its "Application Types".
Two interfaces have the exact VLAN ID value, while VLANs are enabled.
Two interfaces have the same name.
Two interfaces share the same address space or subnet.
Apart from these validation errors, connectivity problems may be caused by one of the
following:
Trying to access the device with VLAN tags while booting from BootP/DHCP.
Trying to access the device with untagged traffic when VLANs are on and Native
VLAN is not configured properly.
Routing Table is not configured properly.
10.9.2 Routing Table
The routing table allows you to configure routing rules. You may define up to 25 different
routing rules, using the ini file, Web interface, and SNMP.
10.9.2.1 Routing Table Overview
The Routing Table consists of the following:
Destination
Prefix Length
201.201.0.0
202.202.0.0
203.203.0.0
225.225.0.0
SIP User's Manual
Table 10-8: Routing Table Layout
Subnet Mask
16
255.255.0.0
16
255.255.0.0
16
255.255.0.0
16
255.255.0.0
Gateway
192.168.0.1
192.168.0.2
192.168.0.3
192.168.0.25
462
Mediant 2000
Interface
Metric
0
1
0
1
0
1
0
1
Document #: LTRT-68809