What is true when describing HPE Aruba Networking VSX ISL to a new customer?
A.
The ISL traffic is always tagged with EF QoS markings.
B.
The traffic over the ISL is encapsulated as a GRE tunnel.
C.
The ISL LAG automatically includes all configured VLANs.
D.
The ISL LAG must allow all configured VLANs.
The Answer Is:
D
This question includes an explanation.
Explanation:
In VSX architecture, the Inter-Switch Link (ISL) is implemented as a Link Aggregation Group (LAG). To ensure proper forwarding and VLAN consistency, the ISL LAG must allow all configured VLANs. This allows VSX synchronization and data forwarding across all VLANs that span the two switches.
ISL traffic is not specifically tagged with EF QoS markings by default.
ISL traffic is not encapsulated in GRE tunnels.
The ISL LAG does not automatically include all VLANs; VLANs must be allowed on the LAG explicitly.
Hence, the LAG must be configured to allow all VLANs.