|
|
|
|
|
|
| Multiple Instance | ||||||
|
|
|
|
|
|
|
|
|
| Configuring MSTP | |||
|
| For example, to configure BPDU filtering on port a9, enter: |
|
|
| ||||||||
|
| ProCurve(config)# |
| ||||||||||
|
| Viewing BPDU Filtering. The | |||||||||||
|
| command displays the BPDU’s filter state. |
|
|
|
|
| ||||||
|
|
|
|
| |||||||||
ProCurve(config)# | show |
|
|
|
|
|
|
| |||||
| Column showing BPDU filter status |
|
| ||||||||||
... |
| Path | Prio | Admin | Auto | Admin | Hello | Root | TCN | BPDU | |||
Port | Type | ||||||||||||
Cost | rity | Edge | Edge | PtP | Time | Guard | Guard | Flt | |||||
+ | |||||||||||||
A9 | 100/1000T | Auto | 128 | No | Yes | True | Global No | No | Yes | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
BPDU filters per port are displayed as separate entries of the spanning tree category within the configuration file.
ProCurve(config)# show configuration
. . . | Rows showing ports with BPDU filters enabled |
|
. . .
FigureConfiguring BPDU Protection
BPDU protection is a security feature designed to protect the active STP topology by preventing spoofed BPDU packets from entering the STP domain. In a typical implementation, BPDU protection would be applied to edge ports connected to end user devices that do not run STP. If STP BPDU packets are received on a protected port, the feature will disable that port and alert the network manager via an SNMP trap as shown in Figure