While configuring FEX (N2232PP model) on Nexus 7010 switches, it appears that we cannot configure FEX interfaces in switchport mode dot1q-tunnel
We have tested it in several situation :
- FEX connected on F2E (N7K-F248XP-25E) module
- FEX connected on M2 Module (N7K-M224XP-23L)
- With default or Jumbo MTU on FPC (and on FEX port so)
The FEX still refuse to accept to be configured in this mode :
N7010(config)# int e114/1/1
N7010(config-if)# switchport mode dot1q-tunnel
Error: dot1q tunnel mode not supported for interface type
Looking after information we have found no precision about dot1q tunneling not supported on FEX, but only how to configure it :
- https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus2000/sw/configuration/guide/b_Configuring_the_Cisco_Nexus_2000_Series_Fabric_Extender_rel_8_x/b_Configuring_the_Cisco_Nexus_2000_Series_Fabric_Extender_rel_6_0_chapter_01.html
- https://www.cisco.com/c/en/us/products/collateral/switches/nexus-2000-series-fabric-extenders/data_sheet_c78-507093.html
- https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus7000/sw/interfaces/config/cisco_nexus7000_interfaces_config_guide_8x/config-q-in-q-vlan-tunnels.html
But Documentation about Nexus 2000 shows configuration is working.
Is there any specific configuration to do to enable N2k FEX dot1q mode with 7010 parent ?
Is there hardware limitation with some N2k FEX model (knowing that 2232PP is one of the oldest model, even if still supported as B22 switches) ?
Is dot1Q tunnel possible on Nexus 2000 FEX with 7000 as parent ?
Other information about configuration :
N7010# sh version
Software
BIOS: version 2.18.0
kickstart: version 8.4(1)
system: version 8.4(1)
BIOS compile time: 04/01/2019
kickstart image file is: bootflash:///n7000-s2-kickstart.8.4.1.bin
kickstart compile time: 6/30/2019 23:00:00 [07/06/2019 22:46:41]
system image file is: bootflash:///n7000-s2-dk9.8.4.1.bin
system compile time: 6/30/2019 23:00:00 [07/07/2019 00:19:56]
N7010# sh fex 114 version
Software
Bootloader version: 0.2
System boot mode: primary
System image version: 8.4(1) [build (0.218)FXC_0_7]
Hardware
Module: Fabric Extender 32x10GE + 8x10G Module
CPU: Motorola, e300c4
Bootflash: locked
Please find hereafter the show interface capabilities
N7010# sh int e114/1/1 capabilities
Ethernet114/1/1
Model: unavailable
Type (SFP capable): unknown
Speed: 1000,10000
Duplex: full
Trunk encap. type: 802.1Q
FabricPath capable: no
Channel: yes
Broadcast suppression: no
Flowcontrol: rx-(off/on),tx-(off/on)
Rate mode: dedicated
Port mode: Routed,Switched
QOS scheduling: rx-(8q1t),tx-(1p8q1t)
CoS rewrite: yes
ToS rewrite: no
SPAN: no
UDLD: no
MDIX: no
TDR capable: no
Link Debounce: yes
Link Debounce Time: yes
FEX Fabric: no
dot1Q-tunnel mode: no
EFP: no
Num Rewrites Allowed: 0
Pvlan Trunk capable: yes
Port Group Members: none
EEE (efficient-eth): no
PFC capable: yes
Breakout capable: no
Link Up Debounce: no
FEC capable: no
[EDIT]
Still no answer about this specific case (N7K-C7010 with SUP2E, M2 and F2E linecards)
Seems that Some other Nexus as parent could enable dot1q-tunneling on FEX, as the following bug talks about :
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuv95106
[EDIT2]
while looking after other ways, as VxLAN, it appears that VxLAN need F3/M3 or more recent linecard as stated in this PDF document.
