VLAN failure errors can be seen in the logs when the CTP interface is configured for direct drive when VLANs are configured. 

The following errors can be seen repeatedly in the logs:

Nov 18 09:52:16 ctp-mdn ctpd:  9 Port State: te-0/0 VLAN failure
Nov 18 09:52:16 ctp-mdn ctpd: 10 Port State: te-0/0 Problem with driver UP
Nov 18 09:52:16 ctp-mdn ctpd: ioc_priv: Error on eth2.1011 socket operation cmd 2 - Operation not supported
Nov 18 09:52:16 ctp-mdn ctpd:  9 Port State: te-0/0 Cant IOCTL port

To resolve, you will have to set the interface to IPtables in order for this to work.  IPtables is the linux OS standard for forwarding and receiving packets on the IP stack.  Currently, you are using the proprietary CTP forwarding called “direct drive”.

To set IPtables on the interface you should do the following:

1. Choose the bundle in question bundle 0, port te-0/0
   From the operations menu of bundle 0, port te-0/0 
2. Choose – Config  
3. Disable for config = yes
4. Choose option 10) Advanced Options…
5. Choose option 13) Disable direct drive.
   Set that function to yes. This enables IPtables. 

The following are the limitations for VLANs:

1. First boot procedure would not allow VLAN configuration. Only default physical ethernet interface configuration is allowed.
2. VLAN should work with both Ipv4 and Ipv6 protocol.
3. VLAN should be able to support with virtual IP but not tested.
4. VLAN is not working with PBS.
5. VLAN is not officially supported with Satop.
6. VLAN will not work with direct drive.
7. Currently VLAN+VIP+Ethernet (total network interfaces) number should be equal or less than 64. It could be increased upon customer's request.

19-11-2025: Minor, non-technical edit