Monday, November 9, 2015

Brocade Switch: BPDU Guard

You really have to be careful where you implement BPDU guard on switches.  I have customers that need to have unmanaged switches, for whatever reason, in their network.  On the link-aggregation ports below (or "lag"), it sees a BPDU coming in from a downstream switch.  What does it do when you have "stp-bpdu-guard" enabled on the primary interface?  ERR-DISabled.  Now, I agree, that is what you want to happen to get rid of those unmanaged switches.  However, in some cases, you have to let them live.

Corp6610(config-if-e1000-1/1/14)#sh run int eth 1/1/14
interface ethernet 1/1/14
 port-name *** Switch Uplink ***

RSTP: Received BPDU on BPDU guard enabled Port 1/1/14 (vlan=15), errdisable Port 1/1/14

Corp6610(config-if-e1000-1/1/14)#no disable
Corp6610(config-if-e1000-1/1/14)#sh lag LAG05
Total number of LAGs:          5
Total number of deployed LAGs: 5
Total number of trunks created:5 (115 available)
LACP System Priority / ID:     1 / cc4e.243f.XXXX
LACP Long timeout:             120, default: 120
LACP Short timeout:            3, default: 3

=== LAG "LAG05" ID 5 (static Deployed) ===
LAG Configuration:
   Ports:         e 1/1/14 e 2/1/14
   Port Count:    2
   Primary Port:  1/1/14
   Trunk Type:    hash-based
Deployment: HW Trunk ID 3
Port    Link    State   Dupl Speed Trunk Tag Pvid Pri MAC             Name
1/1/14  ERR-DIS None    None None  5     No  15   0   cc4e.243f.XXXX  *** Switch Uplink
2/1/14  ERR-DIS None    None None  5     No  15   0   cc4e.243f.XXXX

No comments:

Post a Comment

Your comment will be reviewed for approval. Thank you for submitting your comments.