1Y0-240 · Question #234
Scenario: A Citrix ADC is configured with Interface 1/1 and bound to VLAN 40. A Citrix Administrator has executed the following command: bind vlan 20 -ifnum 1/1 What is the result of executing the…
The correct answer is B. Interface 1/1 is bound to VLAN 20, and native VLAN is 20. https://support.citrix.com/article/CTX115575 VLANs 3 and 4 are tagged through the interface 1/1 even if the -tagall option is OFF: bind vlan 3 -ifnum 1/1 -tagged bind vlan 4 -ifnum 1/1 -tagged The preceding commands configures the NetScaler appliance to receive the VLAN frames…
Question
Scenario: A Citrix ADC is configured with Interface 1/1 and bound to VLAN 40. A Citrix Administrator has executed the following command:
bind vlan 20 -ifnum 1/1 What is the result of executing the command on the Citrix ADC?
Options
- AInterface 1/1 is bound to VLAN 20, and native VLAN is 1.
- BInterface 1/1 is bound to VLAN 20, and native VLAN is 20.
- CInterface 1/1 is bound to VLAN 20, and native VLAN is NOT changed.
- DInterface 1/1 is bound to VLAN 20, and native VLAN is 40.
How the community answered
(25 responses)- A12% (3)
- B80% (20)
- C4% (1)
- D4% (1)
Explanation
https://support.citrix.com/article/CTX115575 VLANs 3 and 4 are tagged through the interface 1/1 even if the -tagall option is OFF: bind vlan 3 -ifnum 1/1 -tagged bind vlan 4 -ifnum 1/1 -tagged The preceding commands configures the NetScaler appliance to receive the VLAN frames on VLAN 3 and 4 through interfaces with IEEE 802.1q tags. The NetScaler appliance uses the native VLAN for the high availability traffic, which includes the heartbeats packets, synchronization, and command propagation. Therefore, you must ensure that the native VLAN has connectivity through all connected interfaces. By default, the native VLAN, VLAN1, is bound to an interface if you do not explicitly bind the interface to a VLAN.
Topics
Community Discussion
No community discussion yet for this question.