Cisco N7K-C7010 Configuration Guide - Page 169

LACP Offload to Fabric Extenders, LACP Fast Timers, Virtualization Support, High Availability

Page 169 highlights

Chapter 6 Configuring Port Channels Information About Port Channels Send document comments to [email protected] LACP Offload to Fabric Extenders To reduce the load on the control plane of the Cisco Nexus 7000 Series device, Cisco NX-OS provides the ability to offload link-level protocol processing to the Fabric Extender CPU. This is supported by LACP by default as soon as there is at least one LACP port-channel configured on a fabric extender. LACP Fast Timers You can change the LACP timer rate to modify the duration of the LACP timeout. Use the lacp rate command to set the rate at which LACP control packets are sent to an LACP-supported interface. You can change the timeout rate from the default rate (30 seconds) to the fast rate (1 second). This command is supported only on LACP-enabled interfaces. To configure the LACP fast time rate, see Configuring the LACP Fast Timer Rate, page 6-34. ISSU and stateful switchover cannot be guaranteed with LACP fast timers. Virtualization Support You must configure the member ports and other port channel-related configuration from the virtual device context (VDC) that contains the port channel and member ports. You can use the numbers from 1 to 4096 in each VDC to number the port channels and you can reuse these port channel numbers in different VDCs. For example, you can configure port channel 100 in VDC1 and also configure a different port channel 100 in VDC2. However, the LACP system ID is different for each VDC. For more information on LACP, see the "LACP Overview" section on page 6-8. Note See the Cisco Nexus 7000 Series NX-OS Virtual Device Context Configuration Guide, Release 5.x, for complete information on VDCs and assigning resources. All ports in one port channel must be in the same VDC. When you are using LACP, all possible 8 active ports and all possible 8 standby ports must be in the same VDC. The port channels can originate in one VDC (with all ports in that channel in the same VDC) and partner with a port channel in another VDC (again, all ports in that channel must be in that VDC). Note The port-channeling load-balancing mode works either for a single module or across the entire device. You must configure load balancing using port channels in the default VDC. You cannot configure load balancing using port channels within specified VDCs. See the "Load Balancing Using Port Channels" section on page 6-6 for more information on load balancing. High Availability Port channels provide high availability by load balancing traffic across multiple ports. If a physical port fails, the port channel is still operational if there is an active member in the port channel. You can bundle ports from different modules and create a port channel that remains operational even if a module fails because the settings are common across the module. Port channels support stateful and stateless restarts. A stateful restart occurs on a supervisor switchover. After the switchover, the Cisco DC-OS software applies the runtime configuration after the switchover. OL-23435-03 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 6-13

  • 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]
6-13
Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x
OL-23435-03
Chapter 6
Configuring Port Channels
Information About Port Channels
LACP Offload to Fabric Extenders
To reduce the load on the control plane of the Cisco Nexus 7000 Series device, Cisco NX-OS provides
the ability to offload link-level protocol processing to the Fabric Extender CPU. This is supported by
LACP by default as soon as there is at least one LACP port-channel configured on a fabric extender.
LACP Fast Timers
You can change the LACP timer rate to modify the duration of the LACP timeout. Use the
lacp rate
command to set the rate at which LACP control packets are sent to an LACP-supported interface. You
can change the timeout rate from the default rate (30 seconds) to the fast rate (1 second). This command
is supported only on LACP-enabled interfaces. To configure the LACP fast time rate, see
Configuring
the LACP Fast Timer Rate, page 6-34
.
ISSU and stateful switchover cannot be guaranteed with LACP fast timers.
Virtualization Support
You must configure the member ports and other port channel-related configuration from the virtual
device context (VDC) that contains the port channel and member ports. You can use the numbers from
1 to 4096 in each VDC to number the port channels and you can reuse these port channel numbers in
different VDCs. For example, you can configure port channel 100 in VDC1 and also configure a different
port channel 100 in VDC2.
However, the LACP system ID is different for each VDC. For more information on LACP, see the
“LACP
Overview” section on page 6-8
.
Note
See the
Cisco Nexus 7000 Series NX-OS Virtual Device Context Configuration Guide, Release 5.x
, for
complete information on VDCs and assigning resources.
All ports in one port channel must be in the same VDC. When you are using LACP, all possible 8 active
ports and all possible 8 standby ports must be in the same VDC. The port channels can originate in one
VDC (with all ports in that channel in the same VDC) and partner with a port channel in another VDC
(again, all ports in that channel must be in that VDC).
Note
The port-channeling load-balancing mode works either for a single module or across the entire device.
You must configure load balancing using port channels in the default VDC. You cannot configure load
balancing using port channels within specified VDCs. See the
“Load Balancing Using Port Channels”
section on page 6-6
for more information on load balancing.
High Availability
Port channels provide high availability by load balancing traffic across multiple ports. If a physical port
fails, the port channel is still operational if there is an active member in the port channel. You can bundle
ports from different modules and create a port channel that remains operational even if a module fails
because the settings are common across the module.
Port channels support stateful and stateless restarts. A stateful restart occurs on a supervisor switchover.
After the switchover, the Cisco DC-OS software applies the runtime configuration after the switchover.