Cisco N7K-C7010 Configuration Guide - Page 220

Consequences of Parameter Mismatch, vPC Number, Moving Other Port Channels into a vPC

Page 220 highlights

Information About vPCs Chapter 7 Configuring vPCs Send document comments to [email protected] To ensure that all the configuration parameters are compatible, we recommend that you display the configurations for each vPC peer device once you configure the vPC. Consequences of Parameter Mismatch In releases earlier than Cisco NX-OS Release 5.2(1), when a consistency check detects a mismatch in a parameter from the list of parameters that must be identical, the vPC peer link and vPC are prevented from coming up. If a parameter mismatch is configured after the vPC is already established, the vPC moves into suspend mode and no traffic flows on the vPC. Beginning with Cisco NX-OS Release 5.2(1), you can configure the graceful consistency check feature, which suspends only the links on the secondary peer device when a mismatch is introduced in a working vPC. This feature is configurable only in the CLI and is enabled by default. Use the graceful consistency-check command to configure this feature. As part of the consistency check of all parameters from the list of parameters that must be identical, the system checks the consistency of all VLANs. In releases earlier than Cisco NX-OS Release 5.2(1), if the configuration of any enabled VLAN is inconsistent across the peer devices, the vPC is prevented from establishing or moves into a suspended mode. Beginning with Cisco NX-OS Release 5.2(1), the vPC will remain operational, and only the inconsistent VLANs will be brought down. This per-VLAN consistency check feature cannot be disabled and does not apply to Multiple Spanning Tree (MST) VLANs. vPC Number Once you have created the vPC domain ID and the vPC peer link, you create port channels to attach the downstream device to each vPC peer device. That is, you create one port channel to the downstream device from the primary vPC peer device and you create another port channel to the downstream device from the secondary peer device. Note We recommend that you configure the ports on the downstream devices that connect to a host or a network device that is not functioning as a switch or a bridge as STP edge ports. See the Cisco Nexus 7000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.x, for more information on STP port types. Finally, working on each vPC peer device, you assign a vPC number to the port channel that connects to the downstream device. You will experience minimal traffic disruption when you are creating vPCs. To simplify the configuration, you can assign the vPC ID number to every port channel to be the same as the port channel itself (that is, vPC ID 10 for port channel 10). Note The vPC number that you assign to the port channel connecting to the downstream device from the vPC peer device must be identical on both vPC peer devices. Moving Other Port Channels into a vPC Note You must attach a downstream device using a port channel to both vPC peer devices. 7-18 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-18
Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x
OL-23435-03
Chapter 7
Configuring vPCs
Information About vPCs
To ensure that all the configuration parameters are compatible, we recommend that you display the
configurations for each vPC peer device once you configure the vPC.
Consequences of Parameter Mismatch
In releases earlier than Cisco NX-OS Release 5.2(1), when a consistency check detects a mismatch in a
parameter from the list of parameters that must be identical, the vPC peer link and vPC are prevented
from coming up. If a parameter mismatch is configured after the vPC is already established, the vPC
moves into suspend mode and no traffic flows on the vPC.
Beginning with Cisco NX-OS Release 5.2(1), you can configure the graceful consistency check feature,
which suspends only the links on the secondary peer device when a mismatch is introduced in a working
vPC. This feature is configurable only in the CLI and is enabled by default.
Use the
graceful consistency-check
command to configure this feature.
As part of the consistency check of all parameters from the list of parameters that must be identical, the
system checks the consistency of all VLANs. In releases earlier than Cisco NX-OS Release 5.2(1), if the
configuration of any enabled VLAN is inconsistent across the peer devices, the vPC is prevented from
establishing or moves into a suspended mode.
Beginning with Cisco NX-OS Release 5.2(1), the vPC will remain operational, and only the inconsistent
VLANs will be brought down. This per-VLAN consistency check feature cannot be disabled and does
not apply to Multiple Spanning Tree (MST) VLANs.
vPC Number
Once you have created the vPC domain ID and the vPC peer link, you create port channels to attach the
downstream device to each vPC peer device. That is, you create one port channel to the downstream
device from the primary vPC peer device and you create another port channel to the downstream device
from the secondary peer device.
Note
We recommend that you configure the ports on the downstream devices that connect to a host or a
network device that is not functioning as a switch or a bridge as STP edge ports. See the
Cisco Nexus
7000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.x
, for more information on STP
port types.
Finally, working on each vPC peer device, you assign a vPC number to the port channel that connects to
the downstream device. You will experience minimal traffic disruption when you are creating vPCs. To
simplify the configuration, you can assign the vPC ID number to every port channel to be the same as
the port channel itself (that is, vPC ID 10 for port channel 10).
Note
The vPC number that you assign to the port channel connecting to the downstream device from the vPC
peer device
must
be identical on
both
vPC peer devices.
Moving Other Port Channels into a vPC
Note
You must attach a downstream device using a port channel to both vPC peer devices.