[FAQE] USG FLEX H Series VLAN Assignment to LAG Interface [uOS 1.32] – Why does the new UI approach allow configuration of unsupported features?

Q: Why can I assign a VLAN to a LAG (Link Aggregation Group) interface in the UI when the feature isn't supported yet on the device?

A:
This is due to a forward-compatible approach adopted in the current firmware and UI design. The VLAN-to-LAG assignment feature has been integrated into the device’s configuration interface ahead of full backend implementation. This means:

• The UI allows users to view and configure VLAN assignments for LAG interfaces.
• However, the feature is not yet functionally supported in the device's firmware at this stage.
• Any configurations applied will not take effect on the device, even if they appear saved or valid in the UI.

This design choice is intentional and stems from the goal of:

• Preparing the system architecture for upcoming firmware updates.
• Allowing testers, partners, and internal QA to familiarize themselves with the UI layout in advance.
• Reducing the development-to-release delay when the feature is officially supported.

Expected Behavior:
If you configure a VLAN on a LAG interface now:

• It will appear in the UI as if it’s been configured correctly.
• But it will not influence actual network behavior.
• Logs or CLI diagnostics may show the feature as unavailable or unsupported.

Recommendation:
Avoid relying on VLAN-to-LAG configurations until official firmware support is released. Keep an eye on the release notes or firmware changelogs for updates regarding the activation of this feature.