Hi, All as i said before on EXOS 22.3.1.4 for some unknown reasons ports configured with link-type edge are initiating topology changes, this happens because the operational edge goes from True to False and the port starts behaving has if there was no link-type edge configuration. Thanks to Nicolay i was informed that this would be corrected in the next patch.
Since there is no next patch yet for EXOS 22.3.1.4 i have taken the initiative to try the new EXOS release 22.4.1.4. After reading the resolved issues i was convinced that this issue was solved since CR xos0069755 is among the list of solved issues.
I would like to underline that i am not sure if CR xos0069755 relates to the issue i am experiencing even though the end result is the same, the port incorrectly trigger a topology change.
All the ports connected to end devices on my network have the following configuration
configure stpd s0 ports link-type edge 3:32 configure stpd s0 ports edge-safeguard enable 3:32 configure stpd s0 ports bpdu-restrict enable 3:32 this can be verified with the command "sh stpd s0 port 3:32 detail", the important lines from the output are as follows.
Edge Port Safe Guard : Enabled
Bpdu Restrict : Enabled
Operational Edge : TRUE
Auto Edge : OnAfter changing a port vlan the Operational Edge goes to FALSE and when the port links up a topology change is triggerd even though the port is still configured with the link-type edge. I have tried to disable the Auto Edge, but no luck.
Edge Port Safe Guard : Enabled
Bpdu Restrict : Enabled
Operational Edge : FALSE Auto Edge : On The only solution i have found for the moment, is uppon changing a port vlan, double check if Operational Edge is FALSE and if so the port must be reconfigured with the link-type edge command in the following order to bring the Operational EDGE to TRUE.
configure stpd s0 ports link-type edge 3:32 configure stpd s0 ports edge-safeguard enable 3:32 configure stpd s0 ports bpdu-restrict enable 3:32 Regards
Gonçalo Reis