Cisco N7K-C7010 Configuration Guide - Page 133

Cisco Nexus 7000 Series NX-OS Unicast, Routing Configuration Guide, Release 5.x, BFD supports IPv4.

Page 133 highlights

Chapter 5 Configuring Bidirectional Forwarding Detection Guidelines and Limitations Send document comments to [email protected] Guidelines and Limitations BFD has the following configuration guidelines and limitations: • BFD supports BFD version 1. • BFD supports IPv4. • BFD supports single-hop BFD. • BFD for BGP supports single-hop EBGP and iBGP peers. • BFD supports keyed SHA-1 authentication beginning with Cisco NX-OS Release 5.2. • BFD supports the following Layer 3 interfaces-physical interfaces, port channels, subinterfaces, and VLAN interfaces. • BFD depends on a Layer 3 adjacency information to discover topology changes, including Layer 2 topology changes. A BFD session on a VLAN interface (SVI) may not be up after the convergence of the Layer 2 topology if there is no Layer 3 adjacency information available. • Port channel configuration limitations: - For Layer 3 port channels used by BFD, you must enable LACP on the port channel. - For Layer 2 port channels used by SVI sessions, you must enable LACP on the port channel. • SVI limitations: - An ASIC reset will cause traffic disruption for other ports. This event could possibly cause SVI sessions on other ports to flap. Some triggers for an ASIC reset are port moves between VDCs, reloading a VDC, or if the carrier interface is a virtual port channel (vPC), BFD is not supported over the SVI interface. - When you change the topology (for example, add or delete a link into a VLAN, delete a member from a Layer 2 port channel, and so on), the SVI session could be affected. It may go down first and then come up after the topology discovery is finished. Tip If you do not want the SVI sessions to flap and you need to change the topology, you can disable the BFD feature before making the changes and reenable BFD after the changes have been made. You can also configure the BFD timer to be a large value (for example, 5 seconds), and change it back to a fast timer after the above events complete. • BFD over VLAN interfaces that have member ports only on a N7K-F132XL-15 module are not supported. You should disable BFD over any VLAN with member ports only on a N7K-F132XL-15 module. Note If you enable BFD at the router level (for example, from OSPF), any BFD sessions over a N7K-F132XL-15 linecard will not come-up. See the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 5.x for information about OSPF and other routing protocols. • When you configure the BFD Echo function on the distributed Layer 3 port channels, reloading a member module flaps the BFD session hosted on that module, which results in a packet loss. If you connect the BFD peers directly without a Layer 2 switch in between, you can use the BFD per-link mode as an alternative solution. OL-23435-03 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 5-5

  • 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
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308

Send document comments to [email protected]
5-5
Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x
OL-23435-03
Chapter 5
Configuring Bidirectional Forwarding Detection
Guidelines and Limitations
Guidelines and Limitations
BFD has the following configuration guidelines and limitations:
BFD supports BFD version 1.
BFD supports IPv4.
BFD supports single-hop BFD.
BFD for BGP supports single-hop EBGP and iBGP peers.
BFD supports keyed SHA-1 authentication beginning with Cisco NX-OS Release 5.2.
BFD supports the following Layer 3 interfaces—physical interfaces, port channels, subinterfaces,
and VLAN interfaces.
BFD depends on a Layer 3 adjacency information to discover topology changes, including Layer 2
topology changes. A BFD session on a VLAN interface (SVI) may not be up after the convergence
of the Layer 2 topology if there is no Layer 3 adjacency information available.
Port channel configuration limitations:
For Layer 3 port channels used by BFD, you must enable LACP on the port channel.
For Layer 2 port channels used by SVI sessions, you must enable LACP on the port channel.
SVI limitations:
An ASIC reset will cause traffic disruption for other ports. This event could possibly cause SVI
sessions on other ports to flap. Some triggers for an ASIC reset are port moves between VDCs,
reloading a VDC, or if the carrier interface is a virtual port channel (vPC), BFD is not supported
over the SVI interface.
When you change the topology (for example, add or delete a link into a VLAN, delete a member
from a Layer 2 port channel, and so on), the SVI session could be affected. It may go down first
and then come up after the topology discovery is finished.
Tip
If you do not want the SVI sessions to flap and you need to change the topology, you can disable
the BFD feature before making the changes and reenable BFD after the changes have been made.
You can also configure the BFD timer to be a large value (for example, 5 seconds), and change
it back to a fast timer after the above events complete.
BFD over VLAN interfaces that have member ports only on a N7K-F132XL-15 module are not
supported. You should disable BFD over any VLAN with member ports only on a N7K-F132XL-15
module.
Note
If you enable BFD at the router level (for example, from OSPF), any BFD sessions over a
N7K-F132XL-15 linecard will not come-up. See the
Cisco Nexus 7000 Series NX-OS Unicast
Routing Configuration Guide, Release 5.x
for information about OSPF and other routing
protocols.
When you configure the BFD Echo function on the distributed Layer 3 port channels, reloading a
member module flaps the BFD session hosted on that module, which results in a packet loss.
If you connect the BFD peers directly without a Layer 2 switch in between, you can use the BFD
per-link mode as an alternative solution.