Cisco N7K-C7010 Configuration Guide - Page 229

vPC and Orphan Ports, Virtualization Support, vPC Recovery After an Outage

Page 229 highlights

Chapter 7 Configuring vPCs Information About vPCs Send document comments to [email protected] When you enter the show cfs application command, the output displays "Physical-eth," which shows the applications that are using CFSoE. Cisco Fabric Services also transports data over TCP/IP. See the Cisco Nexus 7000 Series NX-OS System Management Configuration Guide, Release 5.x, for more information on CFS over IP. Note The software does not support CFS regions. vPC and Orphan Ports When a device that is not vPC-capable connects to each peer, the connected ports are known as orphan ports because they are not members of a vPC. The device's link to one peer will be active (forwarding) and the other link will be standby (blocking) due to STP. In case of a peer link failure or restoration, an orphan port's connectivity may be bound to the vPC failure or restoration process. For example, if a device's active orphan port connects to the secondary vPC peer, the device will lose any connections through the primary peer upon a peer link failure and the resulting suspending of vPC ports by the secondary peer. If the secondary peer were to also suspend the active orphan port, the device's standby port would become active and would provide a connection to the primary peer, restoring connectivity. Beginning with Cisco NX-OS Release 5.2(1), you can configure in the CLI that specific orphan ports are suspended by the secondary peer when it suspends its vPC ports, and are restored when the vPC is restored. Virtualization Support Note You must provision separate vPC peer link and peer-keepalive link infrastructures for each vPC domain deployed in a given VDC. Consolidating a vPC pair (two vPC peer devices of the same domain) in two VDCs of the same physical device is not supported. All ports in a given vPC must be in the same VDC. This version of the software supports only one vPC domain per VDC. You can use the numbers from 1 to 4096 in each VDC to number the vPC and you can reuse these vPC numbers in a different VDC. 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. vPC Recovery After an Outage In a data center outage, both of the Cisco Nexus 7000 Series devices that comprise a vPC get reloaded. Occasionally only one of the peers can be restored. With no functioning peer-keepalive or peer link, the vPC cannot function normally, but depending on your Cisco NX-OS release, a method may be available to allow vPC services using only the local ports of the functional peer. OL-23435-03 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 7-27

  • 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-27
Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x
OL-23435-03
Chapter 7
Configuring vPCs
Information About vPCs
When you enter the
show cfs application
command, the output displays “Physical-eth,” which shows
the applications that are using CFSoE.
Cisco Fabric Services also transports data over TCP/IP. See the
Cisco Nexus 7000 Series NX-OS System
Management Configuration Guide, Release 5.x
, for more information on CFS over IP.
Note
The software does not support CFS regions.
vPC and Orphan Ports
When a device that is not vPC-capable connects to each peer, the connected ports are known as orphan
ports because they are not members of a vPC. The device’s link to one peer will be active (forwarding)
and the other link will be standby (blocking) due to STP.
In case of a peer link failure or restoration, an orphan port’s connectivity may be bound to the vPC failure
or restoration process. For example, if a device’s active orphan port connects to the secondary vPC peer,
the device will lose any connections through the primary peer upon a peer link failure and the resulting
suspending of vPC ports by the secondary peer. If the secondary peer were to also suspend the active
orphan port, the device’s standby port would become active and would provide a connection to the
primary peer, restoring connectivity. Beginning with Cisco NX-OS Release 5.2(1), you can configure in
the CLI that specific orphan ports are suspended by the secondary peer when it suspends its vPC ports,
and are restored when the vPC is restored.
Virtualization Support
Note
You must provision separate vPC peer link and peer-keepalive link infrastructures for each vPC domain
deployed in a given VDC. Consolidating a vPC pair (two vPC peer devices of the same domain) in two
VDCs of the same physical device is not supported.
All ports in a given vPC must be in the same VDC. This version of the software supports only one vPC
domain per VDC. You can use the numbers from 1 to 4096 in each VDC to number the vPC and you can
reuse these vPC numbers in a different VDC.
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.
vPC Recovery After an Outage
In a data center outage, both of the Cisco Nexus 7000 Series devices that comprise a vPC get reloaded.
Occasionally only one of the peers can be restored. With no functioning peer-keepalive or peer link, the
vPC cannot function normally, but depending on your Cisco NX-OS release, a method may be available
to allow vPC services using only the local ports of the functional peer.