Configuring VLANs manually on switch ports is still a daily business for all network admins.
Support by OS to detect errors is very helpful.
EXOS can detect VLAN mismatch configuration (with EDP - Extreme Discovery Protocol) but with some bad limits:
- till 30.3 EXOS can only detection which VLANs are exists on the neighbor switch (no information about tag or untagged)
- since EXOS 30.3 it can also show which VLAN is native (UT) and which are tagged (better)
- it can detect on a neighbor link (ISL) that are different untagged VLANs are mapped and can generate an alarm (because in most cases this is an error). But an error message occurs only one time during the switch is running, no further alarm will generated
As we know that from other vendors this can and needed to be solved in a better way.
Therefore we need enhancement that EXOS vlan mismatch detection can do this:
- detect not only native vlan mismatch, detect also tagged VLAN mismatch on a ISL
- generate Alarms if this is detected
- Alarms needed as syslog entry in switch Log and also as SNMP trap to XMC
- Alarm rate have to be customizeable (not only one during switch booted up)
rate should configureable - one alarm event per minute / per hour / per day - during configuration state alarming should have to be disabled globally (easily)
- Alarming have to be enabled/disabled on a per port base:
Alarming on Uplink is very interesting otherwise on a special ports, where VLAN translation is configured, Alarming have to be turned off
BR,
Matthias
