This topic discusses on how to enable support for VLAN trunking to the SE virtual machine in a vSphere environment.

For more information on Virtual Guest Tagging (VGT) mode, see VLAN Configuration.

Configuring VLAN Interface

The number of VLAN interfaces allowed to be configured on a SE is increased from 224 to 1000 (this feature is supported only in VMware no-orchestrator mode). As the number of VLAN interfaces increases, memory usage increases significantly. The additional memory required for configuring 1000 VLAN interfaces is approximately 550MB. If there are configurations such as virtual services on those interfaces, then more memory is required.

If the memory runs low when you add a VLAN interface, the configuration is accepted but the interface is put into a fault state. You can confirm this by using the show serviceengine < > vnicdb command and checking if there is a fault entry for the concerned interface.

The following is the sample output with fault entry:

Field

Value

vnic[2]

if_name

avi_eth2.999

linux_name

eth2.999

mac_address

00:50:56:81:2f:ec

pci_id

PCI-eth2.999

mtu

1496

dhcp_enabled

TRUE

enabled

TRUE

connected

TRUE

network_uuid

Unknown

nw[1]

ip

100.3.231.0/24

mode

STATIC

nw[2]

ip

fe80::250:56ff:fe81:2fec/64

mode

DHCP

is_mgmt

FALSE

is_complete

TRUE

avi_internal_network

FALSE

enabled_flag

TRUE

running_flag

TRUE

pushed_to_dataplane

FALSE

consumed_by_dataplane

FALSE

pushed_to_controller

FALSE

can_se_dp_takeover

TRUE

vrf_ref

global

vrf_id

1

ip6_autocfg_enabled

TRUE

fault

uuid

00:50:56:81:2f:ec-eth2.999
The following are the reason and recommendation details: 
| reason          | Insufficient memory to apply configuration                                   |
| recommendation  | Free up resources on this SE[se-00505681a639] and then do configure and save |
Note:

550MB memory is required to configure 1000 VLAN interfaces. If there are configurations such as virtual services on those interfaces, more memory is required.