| Multiple Instance |
| Troubleshooting an MSTP Configuration |
|
|
Field | Description |
|
|
RST BPDUs Tx | Number of (802.1w) RST BPDUs that are transmitted through the port. This counter is |
| maintained by the CIST (default MST instance 0) on a |
|
|
RST BPDUs Rx | Number of (802.1w) RST BPDUs that are received on the port. This counter is maintained |
| by the CIST (default MST instance 0) on a |
|
|
MST BPDUs Tx | Number of (802.1s) MST BPDUs that are transmitted through the port. This counter is |
| maintained by the CIST (default MST instance 0) on a |
|
|
MST BPDUs Rx | Number of (802.1s) MST BPDUs that are received on the port. This counter is maintained |
| by the CIST (default MST instance 0) on a |
|
|
MSTI MSGs Tx | Number of times that a configuration message for a specific MSTI was encoded in (802.1s) |
| MST BPDUs that are transmitted through the port. This counter is maintained on a |
| |
|
|
MSTI MSGs Rx | Number of times that the MSTI detected a configuration message destined to the MSTI in |
| (802.1s) MST BPDUs received on the port. This counter is maintained on a |
| port basis. |
|
|
Troubleshooting MSTP Operation
TableProblem | Possible Cause |
|
|
Duplicate packets on a VLAN, or packets not | The allocation of VLANs to MSTIs may not be identical among all |
arriving on a LAN at all. | switches in a region. |
|
|
A switch intended to operate in a region does | An MSTP switch intended for a particular region may not have the same |
not receive traffic from other switches in the | configuration name or region revision number as the other switches |
region. | intended for the same region. The MSTP configuration name (spanning- |
| tree |
| |
| switches intended for the same region. |
| Another possible cause is that the set of VLANs and VLAN |
| mappings |
| switch may not match the set of VLANs and VLAN |
| configured on other switches in the intended region. |
|
|