Some platforms have broken MIBs relating to VLANs creating off-by-one
errors that we have to work around.
That's probably something similar happening here. No one uses these MIBs
except us, so these issues sit for ages.
It's also possible we're hypercorrecting an issue that doesn't exist on
I don't know about 4097, but 4096 is what you used to tag on a vswitch port
to pass a full copy of your uplink port to a VM (i.e. to pass all tagged
vlans). It would be the same as configuring a dvportgroup of type 'vlan
trunk' and setting '0-4096' in the 'vlans' field.
Cheers,
DG
On Mon, 6 May
They're special broadcom tags for letting you know your network belongs to
them.
On Mon 6 May 2024, 1:08 PM grendel--- via observium, <
observium@lists.observium.org> wrote:
> Observium 23.9.13005 Community Edition
>
> shows under PORTS --> VLANs
> two VLAN which are out of IEEE 802.1Q Range (0-
