Cisco 7206 Network Configuration Guide - Page 228

CFSoE, priority, delay restore, interfaces-vlan, show mac address-table, no cfs eth distribute

Page 228 highlights

Information About vPCs Chapter 7 Configuring vPCs Send document comments to [email protected] In addition, you can use the priority command in the if-hsrp configuration mode to configure failover thresholds for when a group state enabled on a vPC peer link is in standby or in listen state. You can configure lower and upper thresholds to prevent the interface from going up and down. VRRP acts similarly to HSRP when running on vPC peer devices. You should configure VRRP the same way that you configure HSRP. For GLBP, the forwarders on both vPC peer devices forward traffic. When the primary vPC peer device fails over to the secondary vPC peer device, the FHRP traffic continues to flow seamlessly. We recommend that you configure routing adjacency between the two vPC peer devices to act as a backup routing path. If one vPC peer device looses Layer 3 uplinks, vPC can redirect the routed traffic to the other vPC peer device and leverage its active Layer 3 uplinks. You can configure the inter-switch link for backup routing path in the following ways: • Create a Layer 3 link between the 2 vPC peer devices. • Use the non-VPC VLAN trunk with a dedicated VLAN interface. • Use vPC peer link with a dedicated VLAN interface. We do not recommend configuring the burnt-in MAC address option (use-bia) for HSRP or manually configuring virtual MAC addresses for any FHRP protocol in a vPC environment because these configurations can adversely affect the vPC load balancing. The hsrp use-bia is not supported on vPCs. When you are configuring custom MAC addresses, you must configure the same MAC address on both vPC peer devices. Beginning with Cisco NX-OS Release 4.2(1), you can configure a restore timer that will delay the vPC coming back up until after the peer adjacency forms and the VLAN interfaces are back up. This feature avoids packet drops when the routing tables may not be converged before the vPC is once again passing traffic. Use the delay restore command to configure this feature. To delay the VLAN interfaces on the restored vPC peer device from coming up, use the interfaces-vlan option to the delay restore command. See the Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 5.x, for more information on FHRPs and routing. CFSoE The Cisco Fabric Services over Ethernet (CFSoE) is a reliable state transport mechanism that is used to synchronize the actions of the vPC peer devices. CFSoE carries messages and packets for many features linked with vPC, such as STP and IGMP. Information is carried in CFS/CFSoE protocol data units (PDUs). When you enable the vPC feature, the device automatically enables CFSoE, and you do not have to configure anything. CFSoE distributions for vPCs do not need the capabilities to distribute over IP or the CFS regions. You need not configure anything for the CFSoE feature to work correctly on vPCs. The CFSoE transport is local to each VDC. You can use the show mac address-table command to display the MAC addresses that CFSoE synchronizes for the vPC peer link. Note Do not enter the no cfs eth distribute or the no cfs distribute command. You must enable CFSoE for vPC functionality. If you do enter either of these commands with vPC enabled, the system displays an error message. 7-26 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x OL-23435-03

  • 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]
7-26
Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x
OL-23435-03
Chapter 7
Configuring vPCs
Information About vPCs
In addition, you can use the
priority
command in the if-hsrp configuration mode to configure failover
thresholds for when a group state enabled on a vPC peer link is in standby or in listen state. You can
configure lower and upper thresholds to prevent the interface from going up and down.
VRRP acts similarly to HSRP when running on vPC peer devices. You should configure VRRP the same
way that you configure HSRP. For GLBP, the forwarders on both vPC peer devices forward traffic.
When the primary vPC peer device fails over to the secondary vPC peer device, the FHRP traffic
continues to flow seamlessly.
We recommend that you configure routing adjacency between the two vPC peer devices to act as a
backup routing path. If one vPC peer device looses Layer 3 uplinks, vPC can redirect the routed traffic
to the other vPC peer device and leverage its active Layer 3 uplinks.
You can configure the inter-switch link for backup routing path in the following ways:
Create a Layer 3 link between the 2 vPC peer devices.
Use the non-VPC VLAN trunk with a dedicated VLAN interface.
Use vPC peer link with a dedicated VLAN interface.
We do not recommend configuring the burnt-in MAC address option (use-bia) for HSRP or manually
configuring virtual MAC addresses for any FHRP protocol in a vPC environment because these
configurations can adversely affect the vPC load balancing. The hsrp use-bia is not supported on vPCs.
When you are configuring custom MAC addresses, you must configure the same MAC address on both
vPC peer devices.
Beginning with Cisco NX-OS Release 4.2(1), you can configure a restore timer that will delay the vPC
coming back up until after the peer adjacency forms and the VLAN interfaces are back up. This feature
avoids packet drops when the routing tables may not be converged before the vPC is once again passing
traffic.
Use the
delay restore
command
to configure this feature.
To delay the VLAN interfaces on the restored vPC peer device from coming up, use the
interfaces-vlan
option to the
delay restore
command.
See the
Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 5.x
, for more
information on FHRPs and routing.
CFSoE
The Cisco Fabric Services over Ethernet (CFSoE) is a reliable state transport mechanism that is used to
synchronize the actions of the vPC peer devices. CFSoE carries messages and packets for many features
linked with vPC, such as STP and IGMP. Information is carried in CFS/CFSoE protocol data units
(PDUs).
When you enable the vPC feature, the device automatically enables CFSoE, and you do not have to
configure anything. CFSoE distributions for vPCs do not need the capabilities to distribute over IP or the
CFS regions. You need not configure anything for the CFSoE feature to work correctly on vPCs.
The CFSoE transport is local to each VDC.
You can use the
show mac address-table
command to display the MAC addresses that CFSoE
synchronizes for the vPC peer link.
Note
Do not enter the
no cfs eth distribute
or the
no cfs distribute
command. You must enable CFSoE for
vPC functionality. If you do enter either of these commands with vPC enabled, the system displays an
error message.