HP 6120G/XG HP ProCurve Series 6120 Blade Switches Advanced Traffic Management - Page 168

Troubleshooting MSTP Operation, Table 4-2.

Page 168 highlights

Multiple Instance Spanning-Tree Operation Troubleshooting an MSTP Configuration Field RST BPDUs Tx RST BPDUs Rx MST BPDUs Tx MST BPDUs Rx MSTI MSGs Tx MSTI MSGs Rx Description 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 per-port basis. 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 per-port basis. 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 per-port basis. 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 per-port basis. 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 per-MSTI per-port basis. 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 per-MSTI perport basis. Troubleshooting MSTP Operation Table 4-2. Troubleshooting MSTP Operation Problem 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 not receive traffic from other switches in the region. An MSTP switch intended for a particular region may not have the same configuration name or region revision number as the other switches intended for the same region. The MSTP configuration name (spanningtree config-name command) and MSTP configuration revision number (spanning-tree config-revision command) must be identical on all MSTP switches intended for the same region. Another possible cause is that the set of VLANs and VLAN ID-to-MSTI mappings (spanning-tree instance vlan command) configured on the switch may not match the set of VLANs and VLAN ID-to-MSTI mappings configured on other switches in the intended region. 4-69

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222

4-69
Multiple Instance Spanning-Tree Operation
Troubleshooting an MSTP Configuration
Troubleshooting MSTP Operation
Table 4-2.
Troubleshooting MSTP Operation
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 per-port basis.
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 per-port basis.
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 per-port basis.
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 per-port basis.
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 per-MSTI
per-port basis.
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 per-MSTI per-
port basis.
Field
Description
Problem
Possible Cause
Duplicate packets on a VLAN, or packets not
arriving on a LAN at all.
The allocation of VLANs to MSTIs may not be identical among all
switches in a region.
A switch intended to operate in a region does
not receive traffic from other switches in the
region.
An MSTP switch intended for a particular region may not have the same
configuration name or region revision number as the other switches
intended for the same region. The MSTP configuration name (
spanning-
tree config-name
command) and MSTP configuration revision number
(
spanning-tree config-revision
command) must be identical on all MSTP
switches intended for the same region.
Another possible cause is that the set of VLANs and VLAN ID-to-MSTI
mappings (
spanning-tree instance vlan
command) configured on the
switch may not match the set of VLANs and VLAN ID-to-MSTI mappings
configured on other switches in the intended region.