Hi,
don't know it is the right place here but here is a request: The BPDU-Protection feature comes handy to avoid network loops, especially if users try to help themselves and mess something up. Unfortunately, the BPDU Protection ind DNOS 6.x and 9.x shuts down the affected port permanently, which requires network crew intervention. Also, as far as I know there is not trap saying "Port #X was shut down by BPDU protection", it just traps "Link down"
Other vendors, like HP Procurve also lack this kind of traps, but have a timeout in BPDU protection. This also comes extremely handy. Here is the flow with Procurve:
Link up
Send Link up trap
Wait <BPDU interval> for BPDU on the port
BPDU received
Shut down port
Send link down trap
Start timer for BPDU-Protection timeout and keep the port down until it expires
Link up
....
As STP packet are the first packages to be send or received on a port, even before starting forwarding any traffic, this save. The user just see his link going up for a second and then going down immediately. If the loop persists, the port will keep going up and down in, say, 1 minute interval. But for the admin, the port looks like it's flapping. Every NMS will recognize this as an error condition and report, yet there is no need to reconfigure the switch, Just remove the condition that led to triggering BPDU protection and off you go.
Alternatively, please implement a "BPDU protection triggered on port $1" trap.
Thanks in advance, looking forward for your comments