IEEE 802.1Q-in-Q VLAN Tagging support on Nexus 5548UP ?

Hi,
Is Q-in-Q tunneling supported on the N5K platform ? I can not find any document that says it is.
I am currently running code version 5.1(3)N1(1) and am not able to configure it.
I can however find documents that say it is supported on the N7K platform -->
http://www.cisco.com/en/US/docs/switches/datacenter/sw/5_x/nx-os/interfaces/configuration/guide/if_qinq_tunnel.html
and
http://www.cisco.com/en/US/docs/ios/lanswitch/configuration/guide/lsw_ieee_802.1q.html#wp1049541
If it is not supported on the N5K platform, what are the alternatives on this platform, if any ?
Thx !

Hi,
Curently q-in-q support is not included into nexus 5000 hardware. Nexus 7000 has different hardware base that's why some supported feature list may differ.
HTH,
Alex

Similar Messages

Vlan tag issue with Nexus 4001 in IBM Blade Centre

Hi
I have a DC architecture with a pair of Nexus 7010's running 3 VDC's (Core/Aggregation/Enterprise). I have at the edge Nexus 5548's which connect to back to the Aggregation VDC. Also connecting back to the Aggregation VDC is an IBM Blade Chassis which has a Nexus 4001i in slots 7 and slot 9. These blade servers are running ESXi 4.0 and are mapped to the Nexus 4001 blade switch.
I had set up the Native VLAN as VLAN 999 which connects up to the ESXi host and I am trunking up multiple VLANS for the Virtual Machines.
The problem I have is that VM's in all VLANS except the ESXi host VLAN (VLAN 10) cannot see their default gateway, and I suspect that there is an issue with the VLAN tag going up to the ESXi host. I have read enough documentation to suggest that this is where the issue is.
My Nexus 4001 interface configuration is below
interface Ethernet1/1
switchport mode trunk
switchport trunk native vlan 999
switchport trunk allowed vlan 10,30,40-41,60-62,90,96,999
spanning-tree port type edge trunk
speed auto
The Aggregation VDC on the Nexus 7010 is the default gateway for all these VLANS.
I also noted that the Nexus 5000 and Nexus 7000 supports the command vlan dot1q tag native command yet the Nexus 4000 doesn't seem to support this. Any assistance would be useful
Thanks
Greg

Your configuration on the N4K looks correct. You shouldn't use vlan dot1q tag native commands on your N7Ks and N5Ks. Native VLAN tagging is really for QinQ (dot1q tunneling).
My only suggestion is check your configuration of the vSwitch in the ESXi host and the host network profile.
Regards,
jerry

Does Cisco7200VXR support feature Q-in-Q VLAN tag termination?

There is only 10000ESR platform support announced in feature guide and no information in Feature Navigator tool...
http://www.cisco.com/en/US/customer/products/sw/iosswrel/ps5207/products_feature_guide09186a00801f0f4a.html

Hi there,
Well.. it seems this feature has several names:
"Cisco IOS Software Releases 12.3 T - IEEE 802.1Q-in-Q VLAN Tag Termination"
http://www.cisco.com/en/US/products/sw/iosswrel/ps5207/products_feature_guide09186a00801f0f4a.html
"Cisco IOS Software Releases 12.0 S - Stacked VLAN Processing"
http://www.cisco.com/en/US/products/sw/iosswrel/ps1829/products_feature_guide09186a008021b9ee.html
But I can't find any reference to the 7200 having support for it... though many others has it.. mainly switches.. not too surprising.. :)
Did it help?

VLAN tagging for Desktops

I have a test VDI 3.1.1 system set up and I have to say, I'm quite impressed. In about a day, I was able to serve Windows 7 desktops, something we can't do with our current VMware View setup. One apparent limitation I have run into, however, is 802.1q VLAN tagging support for Desktop NICs. I have created a 2-way aggregate on nxge0 and nxge1. The portchannel these are connected to is set up for 802.1q tagging, and Solaris is plumbed with aggr13001 to tag its packets with VLAN 13, for example. However, traffic from Desktops is not so tagged, so its packets go nowhere. Is there any way to define a VLAN for a given Desktop Pool? This is important for us, as we tend to keep server systems on campus-only subnets, while desktops get Internet-routed addresses.
Thanks,
Charles

Aggregation shouldn't have any adverse effect here. You need to configure VDI to use the correct VLANs on a per Pools basis. In the VDI Manager first navigate to the Desktop Provider -> Networks tab and 'Refresh' the networks. This will scan all VirtualBox hosts in the provider for currently plumbed interfaces, each of which will be listed by their subnet.
After all networks are detected navigate to the Pool -> Settings tab and select 'Host Networking' followed by the required subnet(s). The primary subnet listed here is used for RDP connections.

802.1X with Guest vlan support IOS version ???

I don't know, Whitch IOS version support 802.1X with Guest vlan to Catalyst 2950 and 3550 switch
please reply to my question.

Tkank for your help.
Also, Cisco web is explained , except for Catalyst 2950 Standard Image (SI) in IOS 12.1(22)EA3
but I can't understand, My site is using catalyst 2950 SI to 802.1X and guest vlan in IOS image 12.1(22)EA3
ex) TW_14F_A_C2950_32.8#sh ver
Cisco Internetwork Operating System Software
IOS (tm) C2950 Software (C2950-I6Q4L2-M), Version 12.1(22)EA3, RELEASE SOFTWARE (fc1)
Running Standard Image
24 FastEthernet/IEEE 802.3 interface(s)
Model number: WS-C2950-24
please, reply for my question

Catalyst 2960 XR support standar IEEE 802.3i

Hi
The Catalyst 2960 XR support standar IEEE 802.3i?.
becouse the datasheet not is present.
Best regards.

Data Sheet doesnt cover this standard:
tandards
● IEEE 802.1D Spanning Tree Protocol
● IEEE 802.1p CoS Prioritization
● IEEE 802.1Q VLAN
● IEEE 802.1s
● IEEE 802.1w
● IEEE 802.1X
● IEEE 802.1ab (LLDP)
● IEEE 802.3ad
● IEEE 802.3af
● IEEE 802.3ah (100BASE-X single/multimode fiber only)
● IEEE 802.3x full duplex on 10BASE-T, 100BASE-TX, and 1000BASE-T ports
● IEEE 802.3 10BASE-T specification
● IEEE 802.3u 100BASE-TX specification
● IEEE 802.3ab 1000BASE-T specification
● IEEE 802.3z 1000BASE-X specification
Could you please open a TAC case so that we check with BU on the same?

802.1Q VLAN Tagging on DSL WAN Connection

Hi
Does anybody know if SRP527W supports 802.1Q VLAN tagging on DSL WAN connection for RFC1483 bridged connections?
Thanks
Justin

Hi Justin,
Sorry for the delay in responding. Yes, this feature is now supported by the SRP527W using the MR3 release. (Please see https://supportforums.cisco.com/docs/DOC-13853).
Andy

Does Iphone support IEEE 802.3N

Does the IPhone 4 support IEEE 802.3N 5GHz network?

Straight from the iPhone's tech specs website: 802.11b/g/n Wi-Fi (802.11n 2.4GHz only)

SUN GigaSwift VLAN tagging NIC DLPI support

Is there any DLPI that support the VLAN tagging ?
I have 2 problems using the normal DLPI to setup VLAN tagging of the "ce" driver.
(1) I do DL_ATTACH_REQ , ppa = 223000 (VID=223 of interface 0)
DL_BIND_REQ, dl_type=0x0800, This allows me to tx/rx of IP packet ET_TYPE=0x0800
I cannot rx/tx ARP packet ET_TYPE=0x0806 !!!!!
I have to ATTACH and BIND 223000 with dl_type=0x0806
So for every VLAN ID I have to DL_BIND_REQ for 0x0800 and 0x0806 !!!
Does anyone know if this is right way to do ???
(2) When DL_PROMISCON_REQ dl_type=MULTICAST, I will rx what I transmit !!!
This seems to be wrong !!! Does anyone know how to setup VLAN to receive IP multicast frames ?
Thanks
e-mail: [email protected]

I can't answer your question. But I can confirm that I noticed that as well. It took me a lot of time to figure out it just ain't possible. One of the reasons we don't use it.

PPPoE Over IEEE 802.1Q VLANs in 12.4T

I am trying to configure PPPoE Over IEEE 802.1Q VLan on a 2811 router with (C2800NM-SPSERVICESK9-M), Version 12.4(24)T8
PPPoE client on FastEthernet0/0 works fine.
interface FastEthernet0/0
no ip address
duplex auto
speed auto
pppoe enable group global
pppoe-client dial-pool-number 1
But PPPoE session is not established on a subinterface with encapsulation dot1Q. It is not even trying to connect to the PPPoE server.
Cisco Feature Navigator says that this feature was added in 12.4T.
Can anybody confirm that 'PPPoE over IEEE 802.1Q VLANs' feature works fine on this IOS?
Thank you in advance!

Below works fine.
vpdn enable
vpdn-group 1
request-dialin
protocol pppoe
bba-group pppoe global
interface FastEthernet0/0
no ip address
duplex auto
speed auto
pppoe enable group global
pppoe-client dial-pool-number 1
But the same doesn't work over the subinterface:
interface FastEthernet0/0.2
encapsulation dot1Q 2
pppoe enable group global
pppoe-client dial-pool-number 1

RV Support VLAN Tagging on WAN Port?

Hi,
I'd like to know if RV Series Router can support VLAN tagging on the WAN port itself? I need this cause my ISP using such method to connect to end user modem/router.
Thank you.
Regards,
Danny

Anything available other than this RV315W? That model is only 10/100 on the LAN. VLAN on the WAN is fairly standard for fibre installs and should be a feature across all SMB routers.

IEEE 802.1ad / 0x88a8

I have moved to another vendor at my edge, and I have continued to use 0x8100 as my ethertype which seems to play nice except for when a customer has a native vlan1 setup.
Vlan1 will get tagged into my SVLAN 301, but Cisco sees it as an incorrect BPDU, and shuts down the port. I also see customer CDP neighbor information, and other stuff when the customer doesnt prune his network down, or uses vlan1 on transparent lan services.
My new vendor told me to use the IEEE 802.1ad standard for the outter tag, (ethertype 0x88a8), but Cisco doesnt support it. Does anyone know why Cisco is not following the IEEE 802.1ad standard for provider bridges (Q-Q) tagging on the ME3400 series? I know they developed their own proprietary GBPT protocol for handling of L2 protocols but that doesnt help me now.
Just some quick searching, shows that the 7600 is supported with 12.2SR. ME3400's are not, its a 'future' release, but I dont know how long ago that document was written.
*May 10 18:30:30 MST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/1, changed state to up
*May 10 18:30:31 MST: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 1 on GigabitEthernet1/0/1 VLAN301.
*May 10 18:30:31 MST: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking GigabitEthernet1/0/1 on VLAN0301. Inconsistent local vlan.
show spanning-tree vlan 301
VLAN0301
Spanning tree enabled protocol rstp
Root ID Priority 4397
Address 0017.5aaf.f200
This bridge is the root
Hello Time 2 sec Max Age 10 sec Forward Delay 7 sec
Bridge ID Priority 4397 (priority 4096 sys-id-ext 301)
Address 0017.5aaf.f200
Hello Time 2 sec Max Age 10 sec Forward Delay 7 sec
Aging Time 300
Interface Role Sts Cost Prio.Nbr Type
Gi1/0/1 Desg BKN*4 128.1 P2p *PVID_Inc
Gi1/0/2 Desg BKN*4 128.2 P2p *PVID_Inc

Currently, the default ether type is 0x8100 on a Cisco 7600 for the Q-in-Q outer tag. However, a few non-Cisco vendors use 0x9100 or 0x9200 ether type for the Q-in-Q outer tag. For Cisco 7600 router to operate seamlessly with other vendors it is required to provide a mechanism to change the default ethertype.
Moreover, there is a need to support ethertype 0x88A8 to support provider bridge defined by IEEE 802.1ad. Custom ethertype feature is proposed as a solution for this problem that enable change of ethertype as per requirements. Under the custom ethertype model, ethertype 0x9100, 0x9200 and 0x88A8 can be configured using "dot1q tunneling" CLI under a physical port.
Benefits
The explanation for the error message:
%SPANTREE-2-RECV_BAD_TLV: Received SSTP BPDU with bad TLV on [chars]
[chars].
Explanation The specified interface has received a Shared Spanning-Tree Protocol (SSTP) bridge protocol data unit (BPDU) that was missing the VLAN ID tag. The BPDU has been discarded.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Span & wireshark to see p-bits and vlan tags

Problem:
I do not see 802.1Q tags nor do I see p-bits (COS) in my wireshark captures. My setup is not working and I have no way to verify (sniff) that the 6509 is setting the p-bits to 3. I need to see them to troubleshoot effectively. Help!
Setup:
I am port mirroring off of my 6509. Port 1/16 should be tagging and setting the p-bits to a value of 3. How can I confirm?
interface GigabitEthernet1/16
description DonkX
no ip address
load-interval 30
mls qos cos 3       ! I've tried my tests with and without this command
mls qos cos trust      ! I've tried my tests with and without this command
switchport
switchport access vlan 941
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 941
switchport mode trunk
no cdp enable
end
sho mon
Session 1
Type                   : Local Session
Source Ports           :
    Both               : Gi1/16
Destination Ports      : Gi8/47
Port G1/16 is the GE uplink to DonkX
Port G8/47 is the Windows 2003 Server with wireshark.
Port G8/9 is my RH4 Linux box with TCPdump.
Steps taken to resolve the problem:
I have followed this document to set this up correctly on my windows box with a Intel Proset 1000MT. I have updated the drivers and made the registry changes with no captures showing tagging/cos information.
http://www.intel.com/support/network/sb/CS-005897.htm
Regardless of my settings, this document says I shouldn't have to worry about drivers:
http://wiki.wireshark.org/CaptureSetup/VLAN
"You'll definitely see the VLAN tags, regardless of what OS the independent system is running or what type of network adapter you're using."
Details:
I am testing a new GPON access product (DonkX) that uplinks via GigE using trunking and setting p-bits. To prioritize my video the new DonkX sets the p-bits to 3 and it instantly ceases that traffic. I have only unidirectional traffic at this point so I can no longer arp, icmp, ftp, tftp, noth'n. The 6509 sends back a response to DonkX but I believe it is dropped because the p-bit is not set to 3. If I remove the priority from 3 to 0 on the DonkX system then it works correctly but without QoS of course.
-JGR

Alright, the saga continues. I saw tagged frames last week but began troubleshooting again this morning and can't see tagged frames!
If I remove the span then I can see tagged traffic on g8/47 (Windows 2003 Server 802.1q not configured on NIC). If I turn on monitoring I see no tagged traffic. I also tried this on a laptop running Fedora 12 (on g8/47) and had the same results. Any ideas?
I've mirrored another trunk port that is in production passing tagged traffic to an 3560 trunked and going to an ASA. The port to the 3560 and ASA (g3/7) requires tagging and works properly; however, I cannot see tags on this port either. Do you see anything obvious here or is this looking like a tac case?
interface GigabitEthernet1/16
description DonkX
no ip address
load-interval 30
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 941
switchport mode trunk
no cdp enable
end
interface GigabitEthernet8/47
no ip address
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
no cdp enable
end
conf t
no mon sess 1
mon sess 1 sourc int g1/16
mon sess 1 dest int g8/47
sho mon
Session 1
Type                   : Local Session
Source Ports           :
    Both               : Gi1/16
Destination Ports      : Gi8/47
Unit details:
WS-C6509 Version 12.2(18)SXD4
NAME: "1", DESCR: "WS-X6516A-GBIC SFM-capable 16 port 1000mb GBIC Rev. 4.2"
PID: WS-X6516A-GBIC
NAME: "8", DESCR: "WS-X6748-GE-TX CEF720 48 port 10/100/1000mb Ethernet Rev. 2.3"
PID: WS-X6748-GE-TX
NAME: "6", DESCR: "WS-SUP720-BASE 2 ports Supervisor Engine 720 Rev. 3.1"
PID: WS-SUP720-BASE
NAME: "msfc sub-module of 6", DESCR: "WS-SUP720 MSFC3 Daughterboard Rev. 2.3"
PID: WS-SUP720
NAME: "switching engine sub-module of 6", DESCR: "WS-F6K-PFC3A Policy Feature Card 3 Rev. 2.4"
PID: WS-F6K-PFC3A

Native VLAN tagging work-around?

Good Day!
Story here is that I am upgrading my 6500 Metro Ethernet core switch from CatOS to IOS and implementing several security components - one in question is implementing 'vlan dot1q tag native' global command on core switch. Most of my PE switches are 3550 series and are compatible with this configuration. The problem is that I also have several remote legacy 3508G switches that I need to support, and they will not accept this command.
Is anyone aware of a work-around config for these 3508s? So far have not found any help on CCO...
Thanks!

Don't know if you can do this on a Cat6500 running IOS, but here's my idea:
Set the native VLAN on the 3508G end of the 802.1Q trunk to a VLAN that is not going to be used anywhere for access, and match the native VLAN specification on your 6500's corresponding interface. Then, remove that VLAN from the trunk at both ends.
The way I read it, on the 6500 the "vlan dot1q tag native" command would tag outgoing traffic on the native VLAN; and would drop all incoming traffic on the native VLAN that wasn't tagged. But none of that will matter, because removing that one VLAN from the allowed VLAN list on the trunk will leave you with only tagged VLAN traffic on the trunk from the 3508G. CDP will see that the native VLAN is set the same at each end (if you use CDP), so it won't flag any mismatches there. You just won't use the native VLAN on the trunk.
I'm doing something similar with CatOS on a 6509 and 2950G access switches. Setting native VLAN to 1 (the default) on both ends, which makes it untagged; and then removing VLAN 1 from the trunk on both sides, leaving me with only tagged traffic on the trunk.
Now, VLAN 1 is a special case, you can't remove it completely from the allowed VLAN list on a 2950G. The documentation refers to it as "minimizing" VLAN 1: CDP and VTP traffic will still pass over it, as will a couple of other Cisco-centric things; but no user traffic, and no STP BPDUs. Testing it today, I verified the CDP and VTP traffic work in both directions after I cleared VLAN 1 from the trunk and had only one customer VLAN, tagged, on it.
In your situation, you can't remove VLAN 1 at all from a 3508G XL trunk. So just pick another VLAN to throw away as the native VLAN that you remove from the trunk, and transmit VLAN1 tagged across it.
I think DTP uses the native VLAN; so the only drawback to my idea is that you have to manually set the trunk mode rather than letting the switches negotiate it out. (No problem for me, I set them all manually anyway.)
Hope this helps.

Vlan tagging on VIC 1225

Hi Community
We are currently Setting up a c240 standalone Server, installed with a vic1225 (connected to a nexus 5500 vpc pair).
We have bare metal windows 2008 R2 os installed and enabled nic teaming ((802.3ad) with the enictool.
Now we want to setup vlan tagged nics in windows but there is no Way to do this....
Is this generally possible in windows 2008 Server ?
Thx in Advance for any tips.

Hello,
ENIC driver for W2K8 does not support VLAN dot 1q feature.
With W2K12, the native teaming driver from Windows tagging feature.
Alternate options are
1) Implement Adapter FEX
2) If you are planning to run Hyper-V on the host, then it can tag the VLANs.
3) Implement individual vNICs for each VLAN and configure active / active transmit load balancing on the host. Also, configure the switch ports as individual links allowing necessary vlans and do not them as port-channel / vPC
I recommend you to upgrade the firmware and drivers to latest version to eliminate known issues.
Padma

IEEE 802.1Q-in-Q VLAN Tagging support on Nexus 5548UP ?

Similar Messages

Maybe you are looking for