How do I configure a new switch in Nebula with a management VLAN other than 1?

JeffRyer

I'm unable to configure a different management VLAN (other than default VLAN 1) on a new switch in Nebula (without a lot of pain).

Note that I first updated the firmware to the latest and then restored back to factory.

I configured the switch in Nebula as follows:

• Management VLAN as 41
• Uplink Port 48 configured as PVID 41 Trunk (and management VLAN access)
• For simplicity, let's say the rest of the ports 1-47 are Access PVID 11. (no ports are onVLAN1)

I then turn on the switch and plug in Port 48 into the uplink.

The switch comes online and connects briefly to Nebula, then goes offline. At this point the switch is operational with the correct VLAN port assignment but is unreachable on the network and Nebula. It never changed the management VLAN as configured.  The management VLAN is still set to 1 and is now unreachable on the network with the uplink port at PVID41.  It seems that Nebula first changes the VLAN of the ports before changing the management VLAN, resulting in the switch going offline. (I've confirmed that it's still on management VLAN1 in the switch event logs and on the uplink device MAC table.)

How do I configure a new switch in Nebula with a VLAN other than 1?

My workaround is to temporarily configure port 47 on VLAN 1 and plug the uplink in there until after Nebula initially configures the VLANs on the ports.  I then notice that, even though I had configured management VLAN as 41, that Nebula reset it back to VLAN 1.  I then change the management VLAN back to 41and plug the uplink into Port 48.  Wait for it to come back online in Nebula and then I can reconfigure Port 47 back to the desired VLAN. 

But now if we ever have an issue and need to reset back to factory then we have to repeat this whole process. I don't think it should be this complicated. It makes me wonder if I'm the only one with this issue? Am I the only one changing the management VLAN from the default? Or, more likely, maybe I'm doing something wrong?

PeterUK

I too change the management VLAN but don't use Nebula their is no simple way when you reset back to factory to then apply the config from defaults.

Zyxel_Lynn

Hi @JeffRyer,

As for the problems you just encountered, I have also reproduced the similar issue and my result shows that when my switch’s trunk port is set to be PVID 41, the switch would send an untagged traffic and occupies the firewall’s LAN1 interface. However, my switch does not go offline, it can still access the internet via the DHCP server in Lan 1. In addition, my switch also applies the settings. That is, the switch has changed the management setting and the trunk port setting. By the way, I am wondering how you verify the management VLAN of your offline switch?

However, I have some concerns regarding your trunk port’s PVID. I would recommend you to alter trunk port’s PVID setting from 41 to 1. I change my trunk port’s PVID from 41 to 1 and the result shows that my switch can successfully access the internet and occupies the VLAN 41 subnet in the firewall.

Let me know if this helps. Please feel free to update this post if you have any further concerns.

Sincerely,

Lynn