cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2633
Views
0
Helpful
1
Replies

NEAT x BPDUGuard

Juliano Luz
Level 1
Level 1

We are testing NEAT to provide network to some meeting rooms. BPDUGuard is globally enabled on authenticator switches. When supplicant switch is connected to a port, before the authentication completes, port is put in err-disable. If bpduguard is disabled on port everything works fine.

 

Authenticator is a 2960X running 15.0-2a.EX5.

 

Is this the expected behavior? Is there a way to get the port not being disabled without removing manually bpduguard?

 

 

1 Accepted Solution

Accepted Solutions

Francesco Molino
VIP Alumni
VIP Alumni
Hi

There is a bug detected in specific conditions:
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCup00390/?referring_site=bugquickviewredir

There is a way to avoid the port going to err-disable using the command "dot1x supplicant controlled transient". However this command works only if spanning-tree bpduguard is enabled on interfaces. If it's enabled globally this command won't have any effect.

Thanks
Francesco
PS: Please don't forget to rate and select as validated answer if this answered your question

View solution in original post

1 Reply 1

Francesco Molino
VIP Alumni
VIP Alumni
Hi

There is a bug detected in specific conditions:
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCup00390/?referring_site=bugquickviewredir

There is a way to avoid the port going to err-disable using the command "dot1x supplicant controlled transient". However this command works only if spanning-tree bpduguard is enabled on interfaces. If it's enabled globally this command won't have any effect.

Thanks
Francesco
PS: Please don't forget to rate and select as validated answer if this answered your question