In a one-arm Citrix ADC deployment with tagall enabled and VLANs 20, 30, and 40 configured, which VLANs are tagged on the interface?

In a one-arm Citrix ADC deployment with tagall enabled and VLANs 20, 30, and 40 configured, which VLANs are tagged on the interface?

• A. VLANS 20, 30, and 40 are tagged on the interface
• B. VLANS 1, 20, 30, 40 and HA packets are tagged on the interface
• C. VLANS 1, 20, 30 and 40 are tagged on the interface
• D. VLANS 20, 30, 40 and HA packets are tagged on the interface

Answer: (C)

Tagall makes every packet leaving the ADC on that interface carry a VLAN tag, even traffic that would normally use the native VLAN. In this one-arm setup the interface has VLANs 20, 30, and 40 configured, and the native VLAN is 1. With tagall enabled, frames for all these VLANs—1, 20, 30, and 40—are tagged on the interface. HA or management traffic that rides on VLAN 1 is carried as tagged frames as well, but the key point is that the interface ends up tagging the native VLAN plus the configured VLANs. Hence VLANs 1, 20, 30 and 40 are tagged on the interface.

Tagall makes every packet leaving the ADC on that interface carry a VLAN tag, even traffic that would normally use the native VLAN. In this one-arm setup the interface has VLANs 20, 30, and 40 configured, and the native VLAN is 1. With tagall enabled, frames for all these VLANs—1, 20, 30, and 40—are tagged on the interface. HA or management traffic that rides on VLAN 1 is carried as tagged frames as well, but the key point is that the interface ends up tagging the native VLAN plus the configured VLANs. Hence VLANs 1, 20, 30 and 40 are tagged on the interface.