Netgear CSM4532 Software Administration Manual - Page 82

Root Guard, 9.4.4., Loop Guard, 9.4.5., BPDU Protection

Page 82 highlights

3.9.4.3. Root Guard Enabling root guard on a port ensures that the port does not become a root port or a blocked port. When a switch is elected as the root bridge, all ports are designated ports unless two or more ports of the root bridge are connected together. If the switch receives superior STP BPDUs on a root-guard enabled port, the root guard feature moves this port to a root-inconsistent STP state, which is effectively equal to a listening state. No traffic is forwarded across this port. In this way, the root guard feature enforces the position of the root bridge. When the STP mode is MSTP, the port may be a designated port in one MSTI and an alternate port in the CIST, and so on. Root guard is a per-port configuration (not a per-port per-instance command), so that all the MSTP instances that this port participates in are not in a root role. 3.9.4.4. Loop Guard Loop guard protects a network from forwarding loops induced by BPDU packet loss. The reasons for failing to receive packets are numerous, including heavy traffic, software problems, incorrect configuration, and unidirectional link failure. When a non-designated port no longer receives BPDUs, the spanning-tree algorithm considers that this link is loop free and begins transitioning the link from blocking to forwarding. Once in forwarding state, the link may create a loop in the network. Enabling loop guard prevents such accidental loops. When a port is no longer receiving BPDUs and the max age timer expires, the port is moved to a loop-inconsistent blocking state. In the loop-inconsistent blocking state, traffic is not forwarded so the port behaves as if it is in the blocking state. The port will remain in this state until it receives a BPDU. It will then transition through the normal spanning tree states based on the information in the received BPDU. Note: Loop Guard should be configured only on non-designated ports. These include ports in alternate or backup roles. Root ports and designated ports should not have loop guard enabled so that they can forward traffic 3.9.4.5. BPDU Protection When the switch is used as an access layer device, most ports function as edge ports that connect to a device such as a desktop computer or file server. The port has a single, direct connection and is configured as an edge port to implement the fast transition to a forwarding state. When the port receives a BPDU packet, the system sets it to non-edge port and recalculates the spanning tree, which causes network topology flapping. In normal cases, these ports do not receive any BPDU packets. However, someone may forge BPDU to maliciously attack the switch and cause network flapping. BPDU protection can be enabled in RSTP to prevent such attacks. When BPDU protection is enabled, the switch disables an edge port that has received BPDU and notifies the network manager about it. NETGEAR M4500 Series Switches Software Administration Manual 82

  • 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
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251

NETGEAR M4500 Series Switches Software Administration Manual
82
3.9.4.3.
Root Guard
Enabling root guard on a port ensures that the port does not become a root port or a blocked port. When a
switch is elected as the root bridge, all ports are designated ports unless two or more ports of the root bridge
are connected together. If the switch receives superior STP BPDUs on a root-guard enabled port, the root
guard feature moves this port to a root-inconsistent STP state, which is effectively equal to a listening state.
No traffic is forwarded across this port. In this way, the root guard feature enforces the position of the root
bridge.
When the STP mode is MSTP, the port may be a designated port in one MSTI and an alternate port in the
CIST, and so on. Root guard is a per-port configuration (not a per-port per-instance command), so that all the
MSTP instances that this port participates in are not in a root role.
3.9.4.4.
Loop Guard
Loop guard protects a network from forwarding loops induced by BPDU packet loss. The reasons for failing to
receive packets are numerous, including heavy traffic, software problems, incorrect configuration, and
unidirectional link failure. When a non-designated port no longer receives BPDUs, the spanning-tree
algorithm considers that this link is loop free and begins transitioning the link from blocking to forwarding.
Once in forwarding state, the link may create a loop in the network.
Enabling loop guard prevents such accidental loops. When a port is no longer receiving BPDUs and the max
age timer expires, the port is moved to a
loop-inconsistent
blocking state
. In the
loop-inconsistent
blocking state,
traffic is not forwarded so the port behaves as if it is in the blocking state. The port will remain in this state
until it
receives a BPDU. It will then transition through the normal spanning tree states based on the
information in the received BPDU.
Note:
Loop Guard should be
configured
only on
non-designated
ports. These include ports in alternate or backup
roles. Root ports and designated ports should not have loop guard enabled so that they can forward traffic
3.9.4.5.
BPDU Protection
When the switch is used as an access layer device, most ports function as edge ports that connect to a device
such as a desktop computer or file server. The port has a single, direct connection and is configured as an edge
port to implement the fast transition to a forwarding state. When the port receives a BPDU packet, the
system sets it to non-edge port and recalculates the spanning tree, which causes network topology flapping. In
normal cases, these ports do not receive any BPDU packets. However, someone may forge BPDU to maliciously
attack the switch and cause network flapping.
BPDU protection can be enabled in RSTP to prevent such attacks. When BPDU protection is enabled, the
switch disables an edge port that has received BPDU and notifies the network manager about it.