
Multiple Instance
Troubleshooting an MSTP Configuration
ProCurve(config)# show
Status and Counters - MSTI Port(s) Debug Counters Information
MST Instance | ID : 2 |
|
|
Port : A15 |
|
|
|
Counter Name |
| Value | Last Updated |
MSGs | |||
0 |
| ||
Exceeded Max | Hops MSTI MSGs | 0 | 02/09/07 17:40:59 |
Topology Changes Detected | 1 | ||
Topology Changes Tx | 3 | 02/09/07 17:41:03 | |
Topology Changes Rx | 2 | 02/09/07 17:41:01 | |
MSTI MSGs Tx |
| 5 | 02/09/07 17:41:03 |
MSTI MSGs Rx |
| 173489 | 02/13/07 18:03:52 |
Figure
| Field Descriptions in MSTP Debug Command Output |
| Table |
| output of show |
Table | |
|
|
Field | Description |
|
|
Invalid BPDUs | Number of received BPDUs that failed standard MSTP |
| checks and were dropped. This counter is maintained by the CIST (default MST instance 0) |
| on a |
|
|
Errant BPDUs | Number of received BPDUs that were dropped on a port that is configured to not expect |
| BPDU packets. This counter is maintained by the CIST (default MST instance 0 in the |
| network) on a |
| a port configured with the BPDU filter to ignore incoming BPDU packets |
| |
| packets are received |
|
|