To enable a VLAN on a LAG-based inter-switch link named LAG256, which command correctly allows VLAN 100?

To enable a VLAN on a LAG-based inter-switch link named LAG256, which command correctly allows VLAN 100?

• A. vlan trunk allowed 100 in LAG256
• B. vlan trunk add 100 in LAG256
• C. vlan trunk allowed 100 in MLAG256
• D. vlan trunk add 100 in MLAG256

Answer: (A)

Allowing a VLAN on a trunk that spans a LAG is what lets that VLAN’s traffic pass between switches. On Aruba switches, you specify which VLANs the trunk will carry by using the command vlan trunk allowed <vlan-id> in <interface>. Applying this to the LAG interface named LAG256 explicitly tells the switch that VLAN 100 is permitted on that inter-switch link, so traffic for VLAN 100 can traverse the LAG. The alternative using add would modify an existing list of allowed VLANs, which isn’t the direct, explicit way to set the current allowed set for this trunk. And commands referencing MLAG256 target a different type of inter-switch linkage, not the LAG in question. So the correct command is vlan trunk allowed 100 in LAG256.

Allowing a VLAN on a trunk that spans a LAG is what lets that VLAN’s traffic pass between switches. On Aruba switches, you specify which VLANs the trunk will carry by using the command vlan trunk allowed in . Applying this to the LAG interface named LAG256 explicitly tells the switch that VLAN 100 is permitted on that inter-switch link, so traffic for VLAN 100 can traverse the LAG.

The alternative using add would modify an existing list of allowed VLANs, which isn’t the direct, explicit way to set the current allowed set for this trunk. And commands referencing MLAG256 target a different type of inter-switch linkage, not the LAG in question. So the correct command is vlan trunk allowed 100 in LAG256.