Cisco N5K-C5010P-BF Troubleshooting Guide - Page 46

Port stuck in STP blocking state with BLK*(Type_Inc), Possible Cause, show spanning-tree interface

Get Cisco N5K-C5010P-BF - Nexus 5010 Switch PDF manuals and user guides
UPC - 882658212208
View all Cisco N5K-C5010P-BF manuals
Add to My Manuals
Save this manual to your list of manuals

Page 46 highlights

Spanning Tree Protocol Chapter 3 Troubleshooting Layer 2 Switching Issues Send document comments to [email protected]. • If the source of the data frames, which are physically moving, is identified, then control the source to halt rapid and continuous moves. • By default, dynamic learning is opened after 180 seconds. At that point, any STP disputes or inconsistencies should be resolved. Port stuck in STP blocking state with BLK*(Type_Inc) A port is stuck in STP blocking state with BLK*(Type_Inc). Possible Cause A type inconsistency might exist on an access port when it is connected to a trunk port on the other end. The port becomes BLK*(Type_Inc) to indicate that there is an incorrect configuration on the link. Use the following commands to confirm the details of the STP port state for the port: • show spanning-tree interface detail • show spanning-tree interface Solution Check the switch port modes configured at both ends (ports) of the link. Ensure that they are in the same mode. Both should be in access or trunk mode. Once the modes are synchronized, the port moves out of the inconsistency state. Port stuck in STP blocking state with BLK*(PVID_Inc) A port is stuck in STP blocking state with BLK*(PVID_Inc). Possible Cause A PVID inconsistency may exist when there is a native VLAN mismatch across a trunk link. When this occurs, the port state becomes BLK* (PVID_Inc). Use the following commands to confirm the details of the STP port state for the port: • show spanning-tree interface detail • show spanning-tree interface Solution Check the native VLAN configured at both ends (ports) of the link. Ensure that they have the same native VLAN. Once the native VLANs are synchronized, the port moves out of the inconsistency state. Port stuck in STP blocking state with BLK*(Loop_Inc) A port is stuck in STP blocking state with BLK*(Loop_Inc). Possible Cause This situation occurs when the loop guard is configured on the port and the port stops receiving BPDUs. This is supposed to prevent loops when unidirectional link failures occur. However, the port is put into a BLK* (Loop_Inc) state. Use the following commands to confirm the details of the STP port state for the port: • show spanning-tree interface detail • show spanning-tree interface Cisco Nexus 5000 Series Troubleshooting Guide 3-4 OL-25300-01

  • 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
Send document comments to [email protected].
3-4
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 3
Troubleshooting Layer 2 Switching Issues
Spanning Tree Protocol
•
If the source of the data frames, which are physically moving, is identified, then control the source
to halt rapid and continuous moves.
•
By default, dynamic learning is opened after 180 seconds. At that point, any STP disputes or
inconsistencies should be resolved.
Port stuck in STP blocking state with BLK*(Type_Inc)
A port is stuck in STP blocking state with BLK*(Type_Inc).
Possible Cause
A type inconsistency might exist on an access port when it is connected to a trunk port on the other end.
The port becomes BLK*(Type_Inc) to indicate that there is an incorrect configuration on the link. Use
the following commands to confirm the details of the STP port state for the port:
•
show spanning-tree interface
<id>
detail
•
show spanning-tree interface
<id>
Solution
Check the switch port modes configured at both ends (ports) of the link. Ensure that they are in the same
mode. Both should be in access or trunk mode. Once the modes are synchronized, the port moves out of
the inconsistency state.
Port stuck in STP blocking state with BLK*(PVID_Inc)
A port is stuck in STP blocking state with BLK*(PVID_Inc).
Possible Cause
A PVID inconsistency may exist when there is a native VLAN mismatch across a trunk link. When this
occurs, the port state becomes BLK* (PVID_Inc). Use the following commands to confirm the details
of the STP port state for the port:
•
show spanning-tree interface
<id>
detail
•
show spanning-tree interface
<id>
Solution
Check the native VLAN configured at both ends (ports) of the link. Ensure that they have the same native
VLAN. Once the native VLANs are synchronized, the port moves out of the inconsistency state.
Port stuck in STP blocking state with BLK*(Loop_Inc)
A port is stuck in STP blocking state with BLK*(Loop_Inc).
Possible Cause
This situation occurs when the loop guard is configured on the port and the port stops receiving BPDUs.
This is supposed to prevent loops when unidirectional link failures occur. However, the port is put into
a BLK* (Loop_Inc) state. Use the following commands to confirm the details of the STP port state for
the port:
•
show spanning-tree interface
<id>
detail
•
show spanning-tree interface
<id>