An 802.1Q trunk must interpret untagged frames consistently at both ends. Matching native VLAN configuration prevents an untagged frame from being mapped to different VLANs across the link. Also compare the allowed VLAN list, tagged/untagged treatment and whether the platform tags the native VLAN by explicit policy. Symmetric tagging may be valid as a separate design decision, but it is not a substitute for agreement on VLAN semantics. Test management and user reachability after any trunk change to detect silent VLAN leakage or blackholing. Native VLAN is a deliberate configuration, not something the switch dynamically chooses from broadcasts. Using different native VLANs can leak untagged traffic into unintended segments. Tagging the native VLAN on both sides is a separate compatible design, not the general consistency rule the question tests.
Official HPE references | Creating a VLAN Profile • Step 3—Configuring VLANs and Port Profiles | Study-guide topic: Managing Wired Networks with HPE Aruba Networking Central
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit