Cisco N7K-C7010 Configuration Guide - Page 283

Licensing Requirements for Q-in-Q Tunnels, Guidelines and Limitations, Configuring Q-in-Q Tunnels

Page 283 highlights

Chapter 9 Configuring Q-in-Q VLAN Tunnels Licensing Requirements for Q-in-Q Tunnels Send document comments to [email protected] Licensing Requirements for Q-in-Q Tunnels The following table shows the licensing requirements for this feature: Product Cisco NX-OS License Requirement 802.1Q-in-Q VLAN tunneling and L2 protocol tunneling require no license. Any feature not included in a license package is bundled with the Cisco NX-OS system images and is provided at no extra charge to you. For a complete explanation of the Cisco NX-OS licensing scheme, see the Cisco NX-OS Licensing Guide. Guidelines and Limitations Q-in-Q tunnels and Layer 2 tunneling have the following configuration guidelines and limitations: • Switches in the service-provider network must be configured to handle the increase in MTU size due to Q-in-Q tagging. • MAC address learning for Q-in-Q tagged packets is based on the outer VLAN (Service Provider VLAN) tag. Packet forwarding issues may occur in deployments where a single MAC address is used across multiple inner (customer) VLANs. • Layer 3 and higher parameters cannot be identified in tunnel traffic (for example, Layer 3 destination and source addresses). Tunneled traffic cannot be routed. • Cisco Nexus 7000 Series devices can provide only MAC-layer ACL/QoS for tunnel traffic (VLAN IDs and src/dest MAC addresses). • You should use MAC address-based frame distribution. • Asymmetrical links do not support the Dynamic Trunking Protocol (DTP) because only one port on the link is a trunk. You must configure the 802.1Q trunk port on an asymmetrical link to trunk unconditionally. • You cannot configure the 802.1Q tunneling feature on ports that are configured to support private VLANs. Private VLAN are not required in these deployments. • You must disable IGMP snooping on the tunnel VLANs. • Control Plane Policing (CoPP) is not supported. • You should run the vlan dot1Q tag native command to maintain the tagging on the native VLAN and drop untagged traffic. This will prevent native VLAN misconfigurations, • You must manually configure the 802.1Q interfaces to be edge ports. • Dot1x tunneling is not supported. • You should perform an EPLD upgrade to newer versions in order for EtherType configuration to take effect on some Cisco Nexus devices. Configuring Q-in-Q Tunnels and Layer 2 Protocol Tunneling This section describes how to configure Q-in-Q tunnels and Layer 2 protocol tunneling on Cisco Nexus 7000 Series devices. This section includes the following topics: • Creating a 802.1Q Tunnel Port, page 9-8 OL-23435-03 Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x 9-7

  • 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]
9-7
Cisco Nexus 7000 Series NX-OS Interfaces Configuration Guide, Release 5.x
OL-23435-03
Chapter 9
Configuring Q-in-Q VLAN Tunnels
Licensing Requirements for Q-in-Q Tunnels
Licensing Requirements for Q-in-Q Tunnels
The following table shows the licensing requirements for this feature:
Guidelines and Limitations
Q-in-Q tunnels and Layer 2 tunneling have the following configuration guidelines and limitations:
Switches in the service-provider network must be configured to handle the increase in MTU size due
to Q-in-Q tagging.
MAC address learning for Q-in-Q tagged packets is based on the outer VLAN (Service Provider
VLAN) tag. Packet forwarding issues may occur in deployments where a single MAC address is
used across multiple inner (customer) VLANs.
Layer 3 and higher parameters cannot be identified in tunnel traffic (for example, Layer 3
destination and source addresses). Tunneled traffic cannot be routed.
Cisco Nexus 7000 Series devices can provide only MAC-layer ACL/QoS for tunnel traffic (VLAN
IDs and src/dest MAC addresses).
You should use MAC address-based frame distribution.
Asymmetrical links do not support the Dynamic Trunking Protocol (DTP) because only one port on
the link is a trunk. You must configure the 802.1Q trunk port on an asymmetrical link to trunk
unconditionally.
You cannot configure the 802.1Q tunneling feature on ports that are configured to support private
VLANs. Private VLAN are not required in these deployments.
You must disable IGMP snooping on the tunnel VLANs.
Control Plane Policing (CoPP) is not supported.
You should run the
vlan dot1Q tag native
command to maintain the tagging on the native VLAN
and drop untagged traffic. This will prevent native VLAN misconfigurations,
You must manually configure the 802.1Q interfaces to be edge ports.
Dot1x tunneling is not supported.
You should perform an EPLD upgrade to newer versions in order for EtherType configuration to take
effect on some Cisco Nexus devices.
Configuring Q-in-Q Tunnels and Layer 2 Protocol Tunneling
This section describes how to configure Q-in-Q tunnels and Layer 2 protocol tunneling on Cisco Nexus
7000 Series devices.
This section includes the following topics:
Creating a 802.1Q Tunnel Port, page 9-8
Product
License Requirement
Cisco NX-OS
802.1Q-in-Q VLAN tunneling and L2 protocol tunneling require no license. Any
feature not included in a license package is bundled with the Cisco NX-OS system
images and is provided at no extra charge to you. For a complete explanation of the
Cisco NX-OS licensing scheme, see the
Cisco NX-OS Licensing Guide
.