QNAP QSW M5216-1T - need VLAN for in-band management, NTP not working

Hi

I need to use a VLAN for my local network in this switch to segregate it from other networks (DMZ and storage).

When I changed the LAN to use VLAN, I lost in-band access to the management interface. Luckily there were still some ports configured on the switch for untagged access to this VLAN (for other switch connection) so I was able to connect to another device to get access to the switch management interface again. I set it to out of band, and plugged the back port into my LAN switch.

Many switches for a long time allowed in-band management interface to specify a VLAN ID. Will QNAP add this in future?

Also, I find that some things work using the OOB interface (such as checking for updates), but NTP does not work any more, and I have to manually set the time.

Also, are there any plans for an SSH interface?

edit: firmware version 1.6.0.3288478

Hi,

Thank you for reaching out to QNAP Support and providing detailed feedback regarding your setup.

Regarding the behaviors and questions you mentioned for your current switch (firmware 1.6.0.3288478), please find our explanations below:

  1. In-Band Management Interface & VLAN ID

    The behavior you experienced is operating according to the original system specification for this model. As this model belongs to an earlier generation, its architecture differs from our current flagship switch line, and there are currently no plans to add configurable In-band Management VLAN ID support for this specific hardware platform.

  2. NTP Synchronization over Out-of-Band (OOB) Interface

    Regarding the NTP issue in OOB mode, by system design, the OOB interface on this model does not support NTP Server communications. Therefore, when operating under the OOB interface, system time must be set manually through the Web GUI.

  3. SSH Support Plans

    There are currently no plans to introduce an SSH management interface to this model series.

【Next-Gen QSS v4.x Managed Switches】

If your network environment strictly requires features such as customizable Managed VLANs, NTP synchronization support over OOB, or advanced management protocols, we kindly invite you to consider our latest generation of switches running QSS v4.x:

  • 10G Series: QSW-M3212R-8S4T, QSW-M3216R-8S8T, QSW-IM3216-8S8T, QSW-M3224-24T

  • 10G/25G Series: QSW-M5218-6F12T, QSW-M5218P-6F12T

  • 10G/25G/100G Series: QSW-M7230-2X4F24T, QSW-M7230P-2X4F24T

  • 25G/100G Series: QSW-M7308R-4X

We appreciate your understanding and thank you for your continued support of QNAP products. Please feel free to reach out to us if you have any further questions or suggestions.

Hi Ronald

Thanks for your reply.

It’s a shame you won’t fix this bug in the firmware for the existing switch, and instead say it’s a designed feature. I will continue to hope that someone will fix this in an upcoming patch release. If you could please simply make the developers know about this issue, then perhaps it can be resolved.

The alternative switches are not suitable, because of the port configuration, noise level, and the fact that I have to pay money for them where I already own a switch that should be able to be fixed.

Adrien

It doesn’t sound like any of these issues are “bugs.” They may be features you wish your model had, but it doesn’t have them and as it’s an older generation switch, it’s not going to get them. Sorry, but that’s just the way it is.

NTP doesn’t work.

VLANs for everything. Except management interface.

“not a bug”.

Yeah right.

These “features” and “design decisions” were not advertised, why is that?

Successor model

--

:raised_back_of_hand::persevering_face:

qss 1.x

outdated hw sw 5hit

qss 2.x

some entry level basic function models

qss 3.x

--

qss 4.x

current sw dev focus models