...
| Table of Contents | ||
|---|---|---|
|
VLAN Tagging allows an individual port or interface on the IMG to be part of multiple VLANs. When configured, each outgoing packet is tagged before leaving the IMG with a VLAN ID tag compliant to IEEE 802.1Q VLAN specifications. The VLAN Aware Ethernet Switch or router extracts the tag and routes the packet into the correct VLAN Group. Feature F-5601 Support for VLAN allows a user the choice of whether or not packets leaving the IMG have a VLAN ID tag inserted in its header. Through the GCEMS application the user can specify the VLAN 16 bit Tag Control Information (TCI) that will be assigned to either each individual interface (CTRL/SIG/DATA) or each individual IP address. All packets leaving either the specific interface or with a specific IP address will have a VLAN tag with the TCI information inserted in the ethernet header. Refer to the information below and the topics in the Related Items section below for more information on this feature.
...
After configuring the VLAN ID, a new field labeled VLAN Priority appears in the VoIP module object being created. Select from drop down menu the priority being given to this VLAN Tag. The priority given will indicate a priority level that will be given to the packet. A priority of 7 is highest and priority of 0 is the lowest. These values can be used to prioritize different classes of traffic (voice, video, data, etc). See screen capture below of configured VoIP Module using the Data Interface with a VLAN tag of 123.
Right click on the IP Network object again and select New IP Address. Modify the CPU - Data object so the Data interface is used again but the CPU is now in the Physical Interface field. The VLAN ID for this is ID:314 and the priority is 3. See screen capture below
The VLAN tag configuration for the diagram is now complete. This procedure can be used on any interface/ip address to add a VLAN Tag to the ethernet packets leaving the interface using a specific IP address.
...
A maximum of 20 VLANs can be created over the three interfaces on the rear of IMG.
If an IP Address object is configured with an external VLAN Tag, all packets with this source IP address will have the configured VLAN Tag inserted in the Ethernet header.
If a Logical Interface object is configured with an External VLAN Tag, all packets that leave this interface will have the configured VLAN Tag inserted in the Ethernet Header.
If a Logical Interface is configured with a VLAN ID, all IP Networks connected to that interface will use that VLAN ID. Refer to the object for more information on this object.
If the VLAN tag assigned to the IP address object is different from the VLAN Tag assigned to the Logical Interface, the VLAN Tag assigned to the IP Address object overrides VLAN tag assigned to the Logical Interface.
Refer to the screen capture below
When the VLAN tag is configured on the IMG, a VLAN Tag is inserted as shown in screen capture above. The tag is inserted between the Source Address and Ethernet Type information.
The Tag Protocol Identifier (TPID) is set to 0x8100 (default) in order to identify the frame as an IEEE 802.1Q tagged frame.
The priority of the tag is set through the ClientView application using the VLAN Priority field. The priority is set up through IEEE 802.1Q and is a way for administrators of a network to prioritize each packet being sent.
The Canonical Format Indicator (CFI) will always have a value of zero. Zero indicates data is going over ethernet.
VLAN ID is the ID configured in the VLAN ID field in the Web GUI application.
VLAN ID's cannot be shared across interfaces. For example, a VLAN ID of (2) cannot be configured on both the Data and Signaling interface.
VLAN ID's can be shared on the same interface. For example, multiple IP addresses can be configured on the Data Interface and they can all have the same VLAN ID.
A VLAN ID of 0 identifies the VLAN tagging functionality as disabled.
When configuring the Logical Interface object (IP Network -> Logical Interface), the VLAN Tag field is not selectable when Control is selected as the interface. Doing so could create a situation where GCEMS loses communication with the IMG. However, configuring a VLAN tag on the individual Control Interface when configuring the IP Address object (IP Network -> IP Address) in ClientView is allowed.