02-21-2017 03:01 PM - edited 03-08-2019 09:26 AM
This document says:
IA client ports do not support these features:
...
- IEEE 802.1Q tunneling
My ports will take the commands but I just can't seem to get it working, however I can't see anything conclusive online that says it should or shouldn't work. Can anyone advise whether the above link is 100% correct and QinQ isn't possible on 6800IA or if I've misunderstood?
Many thanks!
02-22-2017 12:37 AM
Hi
Check the FEX itself it will tell you what there capable of , but there stripped down so I doubt they support qinq , mine don't look to anyway 2248s and 2232s
# sh int Eth101/1/12 capabilities
Ethernet101/1/12
Model: N2K-C2248TP-1GE
Type (Non SFP): 10/100/1000BaseT
Speed: 10,100,1000,auto
Duplex: full
Trunk encap. type: 802.1Q
Channel: yes
Broadcast suppression: no
Flowcontrol: rx-(off/on),tx-(off/on)
Rate mode: none
QOS scheduling: rx-(6q1t),tx-(1p6q0t)
CoS rewrite: no
ToS rewrite: no
SPAN: yes
UDLD: no
MDIX: no
Link Debounce: yes
Link Debounce Time: yes
dot1Q-tunnel mode: yes
Pvlan Trunk capable: yes
TDR capable: no
FabricPath capable: no
Port mode: Switched
FEX Fabric: no
02-22-2017 04:15 AM
Hi thanks for the reply. I can see yours says the below:
dot1Q-tunnel mode: yes
Where as mine doesn't have this line:
sh int Gi101/1/0/3 capabilities
GigabitEthernet101/1/0/3
Model: C6800IA-48FPD
Type: 10/100/1000BaseT
Speed: 10,100,1000,auto
Duplex: half,full
Trunk encap. type: 802.1Q
Trunk mode: on,off,desirable,nonegotiate
Channel: yes
Broadcast suppression: percentage(0-100)
Flowcontrol: rx-(off,on,desired),tx-(none)
Membership: static
Fast Start: yes
QOS scheduling: rx-(1p3q3t), tx-(1p3q3t)
QOS queueing mode: rx-(cos,dscp), tx-(cos,dscp)
CoS rewrite: yes
ToS rewrite: yes
Inline power: yes, policing, poeplus
SPAN: source/destination
UDLD yes
Link Debounce: no
Link Debounce Time: no
Ports-in-ASIC (Sub-port ASIC) : UNAVAILABLEnum_bus = 0, num_ports = 0
Remote switch uplink: no
Port-Security: yes
Dot1x: yes
Strangely enough though an SFP port on the C6832-X-LE doesn't have this either, but I'd imagine the brain of the FEX should be able to do QinQ?
sh int te1/1/6 capabilities
TenGigabitEthernet1/1/6
Model: C6832-X-LE
Type: 10/100/1000BaseT
Speed: 10,100,1000,auto
Duplex: half,full
Trunk encap. type: 802.1Q
Trunk mode: on,off,desirable,nonegotiate
Channel: yes
Broadcast suppression: percentage(0-100)
Flowcontrol: rx-(off,on,desired),tx-(off,on,desired)
Membership: static
Fast Start: yes
QOS scheduling: rx-(1p7q4t), tx-(1p7q4t)
QOS queueing mode: rx-(cos,dscp), tx-(cos,dscp)
CoS rewrite: yes
ToS rewrite: yes
Inline power: no
SPAN: source/destination
UDLD yes
Link Debounce: yes
Link Debounce Time: no
Ports-in-ASIC (Sub-port ASIC) : 1-2,5-6 (1-8)
Remote switch uplink: no
Port-Security: yes
Dot1x: yes
Any advice on the above?
02-22-2017 04:46 AM
yes see mine is coming off a 5K and a diff fex not a 6k switch so the capabilities may be different per fex , if its not there its not supported usually , I was told by TAC before that's where you check what your FEX port can do as we had discrepancies between are different types of fexes and there abilities
saying that looking at the doc qinq is not supported on any 2k model connected to 5/6 or 7 switches , its not listed at all as a feature
http://www.cisco.com/c/en/us/products/collateral/switches/nexus-2000-series-fabric-extenders/data_sheet_c78-507093.html
but then I see bugs for qinq in fexes released last month
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCut03537/?referring_site=bugquickviewredir
The commands are definitely there though on my fex
(config-if)# switchport dot1q ethertype ?
0x8100 Default EtherType for 802.1q frames
0x88A8 EtherType for 802.1ad double tagged frames
0x9100 EtherType for QinQ frames
<0x600-0xffff> Any EtherType
c
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide