HPE7-A01 · Question #134
How do you allow a new VLAN 200 for downstream access switch with VSX pair using VSX LAG?
The correct answer is C. vlan trunk allowed all in LAG 1 multi-chassis. Option C is correct because HPE Aruba AOS-CX uses the multi-chassis keyword - not "MLAG" - to identify a VSX LAG interface, and the proper command verb for permitting VLANs on a trunk is vlan trunk allowed. Specifying allowed all permits all VLANs including the new VLAN 200 to…
Question
How do you allow a new VLAN 200 for downstream access switch with VSX pair using VSX LAG?
Options
- Avlan trunk allowed 200 in MLAG 1
- Bvlan trunk add 100 in MLAG1
- Cvlan trunk allowed all in LAG 1 multi-chassis
- Dvlan trunk add 100 in LAG1 multi-chassis
How the community answered
(25 responses)- A4% (1)
- B4% (1)
- C80% (20)
- D12% (3)
Explanation
Option C is correct because HPE Aruba AOS-CX uses the multi-chassis keyword - not "MLAG" - to identify a VSX LAG interface, and the proper command verb for permitting VLANs on a trunk is vlan trunk allowed. Specifying allowed all permits all VLANs including the new VLAN 200 to traverse the VSX LAG to the downstream access switch.
Why the distractors fail:
- A uses "MLAG" (an Arista/generic term) instead of Aruba's
multi-chassisdesignation, making it invalid syntax on AOS-CX. - B has two errors: it references the wrong VLAN (100, not 200) and again uses "MLAG" rather than
multi-chassis. - D uses the wrong VLAN number (100) and the wrong verb (
addinstead ofallowed), even though it correctly uses themulti-chassiskeyword.
Memory tip: On Aruba AOS-CX, remember "MAC" - Multi-chassis, Allowed, Correct". VSX LAGs always say multi-chassis; VLAN trunks always say allowed. If an answer says MLAG or uses add, it's wrong on Aruba gear.
Topics
Community Discussion
No community discussion yet for this question.