hello,
I have noticed some issues on a vlan Default when it is untagged and
protected by EAPS.
The issue is, that on a link that is blocked, a switch (x450-24x)
running summitX-12.4.5.3-patch1-2.xos still has something in fdb related
to port on blocked link.
Only on vlan Default, only when it is untagged.
It causes i.e. blackouts in communitation with some switches that are
managed via vlan default. clearing FDB helps for a while, until
particular MAC is rewritten over "blocked" port.
Is it some known issue or something new ?
Or it is a common good practice not to use untagged Default in core ?
Regrds,
Marcin
_______________________________________________
extreme-nsp mailing list
extreme-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/extreme-nsp
I have noticed some issues on a vlan Default when it is untagged and
protected by EAPS.
The issue is, that on a link that is blocked, a switch (x450-24x)
running summitX-12.4.5.3-patch1-2.xos still has something in fdb related
to port on blocked link.
Only on vlan Default, only when it is untagged.
It causes i.e. blackouts in communitation with some switches that are
managed via vlan default. clearing FDB helps for a while, until
particular MAC is rewritten over "blocked" port.
Is it some known issue or something new ?
Or it is a common good practice not to use untagged Default in core ?
Regrds,
Marcin
_______________________________________________
extreme-nsp mailing list
extreme-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/extreme-nsp