VLAN ID is wrong - bug

[user46]

Hi,
on my alta fw, i am stuck and there is definitely a bug.
the 5th vlan i created is vlan 40. this is marked as vlan 5 everywhere and is tagged as 5 and devices see it as 5.
i create a new one after called 41, and then it is now 16.

[user46]

[jmszuch]

Just out of curiosity, are the devices on those VLANs receiving an IP from the correct subnet? I reported a similar issue to support recently where the VLANs displayed by the controller in the Devices view might be incorrect when third party switches are in the mix. At this particular site the issue is cosmetic, as the VLANs all behave properly otherwise, hence my question

Also sounds like it’s being worked on if the issue your seeing is the same as the one I reported.

[user46]

they get an ip on the correct vlan yes, 40, but show up as 5

[jmszuch]

That definitely sounds like the same behavior I’ve seen at my own site. I see from other post that your also using HPE Instant On switches, which are the same switches as well. Seems to me that how the controller is identifying VLANs to display is particularly hinky with the Instant On switches in the mix. I might flag down @Alta-Matt_v2 to see if he might be kind enough to elaborate, as he’s the one who responded to my support ticket on seeing this behavior

[pjtogher]

This issue is ongoing for a while I’m afraid. No sign of a lasting fix despite multiple users reporting it over at least 8 months.

VLAN id is sometimes displayed wrong under devices

On my route10 I have 4 vlans defined: 1-4. The three devices though on vlan 4, all show up as vlan 5 (which I don’t have defined) under devices. They all get assigned to the right subnet though and are otherwise as far as can tell behaving correctly. The only thing I can think of that’s unusual is that vlan is firewalled off from forwarding anything other than dhcp or ntp udp packets to the route10.

[user46]

if @Alta-Matt_v2 has time, i can provide full access to both instanton and alta

[Alta-Matt_v2]

Hi all,

No need for invitations, we have identified the bug and have been able to reproduce it. This is a low-level bug that occurs much more frequently when third party switches are employed. Unfortunately, we cannot put a timeframe on fixing it yet because it involves a large task of updating a vendor’s complete system. The good news is it’s solely aesthetic and doesn’t impact any functionality that we’re aware of.

We will get it resolved and we appreciate your patience while we work on fixing the display bug.

[richardvaughan]

Alta-Matt,

Given over 2 months have passed since this post, is the any update on this fix?

Thanks