SIP User's Manual 324 Document #: LTRT-65415
MediaPack Series
îš„ 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. Please be sure to follow the Syslog messages that the device sends in system
startup to see if any errors occurred.
Note: 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.
9.7.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, and 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).
îš„ An IPv4 interface was defined with "Interface Type" different than "IPv4 Manual" (10).
îš„ 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.
To Next Page
Loading...
Need help?
General
