PVID, VLAN don't working after migrating from standalone to nebula cloud

meigor

Hello everyone,

I recently migrated my GS1920-24HP switch from standalone mode to Nebula Cloud management. After the migration, I noticed an issue with VLAN assignments for the management IPs:

The switch itself is set to use Management VLAN 30, but it still receives its IP address from the default LAN DHCP (VLAN 1) instead of the correct VLAN 30.

Similarly, my two NWA130BE access points (APs) previously received their management IPs from VLAN 30 but now only get IPs from the LAN DHCP (default VLAN 1).

I didn't changed anything on the (opnSense) Firewall side.

Current Configuration:
The management VLAN on the switch is set to 30.

Switch ports connecting the APs are configured as trunk and allow all VLANs.
(APs handle multiple SSIDs with different VLANs.)

The uplink port to the router is also configured as a trunk and should allow all VLANs.

VLAN tagging is working fine for client traffic on the APs (different SSIDs for different VLANs), but the switch and AP management traffic seem to fallback to VLAN 1.

My Questions:
Is there a misconfiguration in how the management VLAN is handled in Nebula Cloud?

Should I explicitly block VLAN 1 for management traffic, or configure the switch/APs differently to force management traffic to VLAN 30?

Are there any specific settings on the uplink port or trunk ports that need adjustment in Nebula for this setup?

Does the migration require additional steps for VLAN management?

Switch:

Uplink & AP port:

AP:

Zyxel_Tina

Hi @meigor,

Thanks for reaching out. After reviewing the information and the screenshots you provided, we have identified a misconfiguration on the uplink port that is causing this issue.

To resolve this, we recommend changing the PVID of the uplink port to a value other than 10, 20, 30, or 40, or simply setting it to PVID 1. This will make VLAN 30 traffic to be properly tagged as it exits the switch, allowing your router to manage the VLANs as intended.

Zyxel_Tina

Hi @meigor,

Thanks for reaching out. After reviewing the information and the screenshots you provided, we have identified a misconfiguration on the uplink port that is causing this issue.

To resolve this, we recommend changing the PVID of the uplink port to a value other than 10, 20, 30, or 40, or simply setting it to PVID 1. This will make VLAN 30 traffic to be properly tagged as it exits the switch, allowing your router to manage the VLANs as intended.

meigor

Thankyou now its working.