VLAN tagging and tagging question

Hello,
I have a question about VLAN tagging on a Cisco switch.
I've learned that switches tag frames with VLAN IDs once the frame enters a Trunk port (not when it enters a VLAN port).
Now, if two computers from the same VALN and on the SAME switch talk to each other then logically there should not be any VLAN assignment on the frames (as if they were connected to a hub).
Is that correct please?
TIA

Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Just to muddy the waters, since VLAN edge/access ports don't normally tag frames with VLAN IDs, referencing your question about two computers "talking" to each other, it doesn't matter whether the two ports or on the same switch or even different switches; or in the same VLAN or not.
Also understand trunk ports normally tag frames, and edge/access ports don't, but an exception for the former is the "native" VLAN frames aren't tagged, and an exception for the latter, a Voice VLAN will tag frames.

Similar Messages

Q-in-Q w/o Native VLAN tag question

Let's assume that we have Q-in-Q setup between 2 service provider switches. To run Q-in-Q we want to terminate a trunk into each tunnel port and enable native VLAN tagging to ensure that all customer VLAN's are tagged. In some cases we may have a customer that wants to connect their own equipment into the tunnel port on our switch, so it wouldn't actually be a trunk - it would be an access port. If this occurs then there is no inner VLAN tag, only an outer VLAN tag. Will tunnelling still function properly in this scenario?

actually this is not true... sorry Kishore
Tunneling still works and traffic within the SP core will be singled tagged (with the SP tag only).
However when you do this you need to be extremely careful specially if you use dot1q trunks in the core with native vlan within the customer range. You might end up in unexpected result in this case.
See an exmple of a possible issue you might see in this case:
http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/12.2_58_se/configuration/guide/swtunnel.html#wp1008635
The solution would be to tag native vlan in the SP core or use ISL trunks or use native vlans outside customer range or (logically) use trunk ports on CE device (still paying attention to native vlan though).
Riccardo

(Another) Native VLAN tagging question..

I have completed CCNA 3 course and am in 4 right now. I am still confused about VLAN native commands such as
sw tr na vl xxx
When this is on a trunk port, what does it mean?
Thanks....

"So does that mean that before the packet goes onto the trunk link it is put into the native VLAN then when it exits the trunk link (on the other side) it is stripped of the VLAN info? "
No, what your prior quotation decribed is what a switch should do with untagged frames received on a port defined as a VLAN trunk.
The VLAN tags informs the switch what VLAN a frames belongs to when it is received on a VLAN trunk port, but without such a tag, how does the switch know the intended VLAN? It doesn't, from the frame itself. So, we can often configure a trunk port to place any untagged frames into one VLAN of our choice. In theory, once we define what VLAN untagged frames will be considered a member of, tagged frames, for that VLAN could also be accepted. Both should be treated the same by the receiving switch.
As for a switch sending packets out a VLAN trunk, normally you would expect all packets to be VLAN tagged although a switch might support sending one particular VLAN frames without tags to support a device, such as the PC described in your quotation, that doesn't understand how to process, or expect, tagged frames.
If you're wondering how this all comes to be, consider a PC that knows nothing about VLAN tags is connected to an IP phone which does (which connects to the network) and you want to place the two devices on different VLANs. As the PC traffic transits the phone could, in theory, wrap/unwrap the PC traffic with VLANs tags when working with the network switch. However, if the phone fails, you can design the IP phone hardware to keep the link good from PC to the network, but then the IP phone PC VLAN processing would be lost. So for that reason, and the reason, we might want to add/remove an IP phone "in front" of the PC, we want to continue to support untagged frames to/from the PC.
Altough the frames to the PC are untagged, since we can configure what VLAN untagged frame should be considered per port, we can have different PCs (on different ports) in different VLANs on the switch. (This is very similar to port based VLANs, but instead of being limited to one logical VLAN per port, we're limited to one untagged VLAN per port but can have multiple tagged VLANs per port.)

VLAN Tagging Question???

Hi friends,
I attached a simple diagram which modelize my question.
As u will see in the sample diagram. I have two networks one has 192.168.1.0/23 as a network address and the other has 10.10.10.0 /24.
I wanna connect these two networks to ASA 5510. But i dont have enough interfaces so i have to use single interface. lets say E1. Also i have an unmanaged switch.
Here is the question: If i configured subinterfaces as E1.100 and E1.200 on ASA. Do i need to set the port on Switch which is connected to ASA as a trunk port? (well.. i couldnt do it... its unmanageable)
Is the following configuration enough to use for my question?
interface ethernet1.100
vlan 100
ip address 192.168.1.1 255.255.254.0
nameif networkA
interface ethernet1.200
vlan 200
ip address 10.10.10.1 255.255.255.0
nameif networkB
or do i need to set any port as trunk?
Thanks alot?

You need trunk port on your switch anyway only one vlan (vlan 100 or vlan 200) can be transfered to ASA.
Over a trunk port you can transfer more than one VLAN traffic.
bye
FCS
Please rate me if I helped.

VLAN Tagging ESW-540 and 3750g

Hi everyone!
I'm a self taught cisco type person who really specialises in ASA rather than routers, but have fumbled my way through many a task with the help of this site and google... However! I am currently tasked with setting up a network, pretty much from scratch, that requires some fairly hefty VLAN deployment.
My hardware on hand (already existed so can't can't change anything easily) 5x ESW-540-48 Switches, 1x3750g switch, 1x2811 router.
I don't believe the router should be required as the 3750 is capable of intervlan routing. So what i'm trying to achieve is as follows:
VLAN 1 - 172.16.8.0/22 (A)
VLAN 2 - 10.0.2.0/24     (B)
VLAN 3 - 10.0.3.0/24     (C)
VLAN 4 - 10.0.4.0/24     (D)
VLAN 5 - 10.0.5.0/24     (E)
VLAN 6 - 10.0.6.0/24     (F)
VLAN 7 - 10.0.7.0/24     (G)
VLAN 8 - 10.0.8.0/24     (H)
VLAN 9 - 10.0.9.0/24     (I)
Server Room - Servers connected to the 3750G
3750G connected to 5 ESW switches distributed around the building.
ESW-1 Will have VLAN(A) and VLAN(B) devices connected, specified at port level.
ESW-2 Will have VLAN(A) and (C) devices connected, specified at port level.
ESW-3 Will have VLAN(A), (D), (E) and (F) devices connected, specified at port level.
ESW-4 Will have VLAN(A), (G) devices connected specified at port level.
ESW-5 Will have VLAN(A), (H) and (I) devices connected, specified at port level.
Now at one point I actually had the VLAN's *working* in that I could specify an IP address and could ping to and from it! However DHCP wasn't passing despite numerous attempts with DHCP relay and IP-Helper configurations.
Also I was having issues with VLAN 1 as the native VLAN, the ESW switches don't allow you to do much with them, as they 'weren't created by the user'. So tried switching that out to VLAN11 also but with very little success there (I had to change the native vlan on all trunks to VLAN 11)
All the 10.x.x.x addresses need to be able to communicate with each other
All the ESW switches need to be able to handle their respective VLAN's as well as VLAN 1 (for Printers and wireless access points distributed around the building).
Partly i'm doing this in the hope that maybe some helpful soul can make some sense of it, but also just the fact of writing it down MAY firm it up in my head somewhat
Thanks in advance!
Simon

Ok so - i gave up at 2am this morning, and going back to it with a fresh head! Here's the situation as it has unfolded...
I have configured up 4 of my vlans for the purpose of testing, so you'll note there are a few missing.
I have moved the Native to VLAN 11 because the ESW's were doing something weird, and wouldn't allow me to do anything with trunking... If anyone can see a MUCH easier way of doing this, please feel free to chime in!
Primarily my question though is - why isn't DHCP working? Do I need to configure DHCP relaying on the ESW switches? Or should the DHCP REQ be passed across the entire vlan back to the 3750 regardless. And if I do need to configure relaying on the ESW - how?
In my server room I have a 3750 and a bunch of servers.
One of these servers - 172.17.10.229 is a win 2k3 dhcp server (physical not virtualised)
On my dhcp server I have configured scopes for each vlan (not superscoped)
My servers are sitting on the first 16 ports of said 3750. I have set their ports to native vlan 11 and allow vlans 1-3 and 11.
My ESW switches are on ports 46, 47 and 48. Likewise, their native has been moved to vlan11 and allowed vlans 1-3 and 11.
My ESW switches have been moved to native vlan11 and trunked each of their port 48's to allow all vlans.
Test 1: Unmodified port #10 on ESW1 (default vlan 11).
Connect DHCP device.
IP address assigned from vlan 11: 172.17.10.101.
Can ping all VLAN interface addresses.
Test 2: Modified port #11 on ESW1 (VLAN 2).
Connect DHCP device.
No IP address assigned.
Set static IP address 10.0.2.55/24.
Can ping all VLAN interfaces, DHCP server, entire network.
Change IP address of test device to 172.17.10.102 for testing.
No ICMP responses from anywhere - this is good!
So as you can see i've done my homework - well most of it obviously. Because it still isn't working
Here's the config of the 3750, the ESWs of course are a bit harder to just post my config, but the general state is something like this...
ESW Switch 1
Native VLAN 11
IP Address:     172.17.8.101 255.255.252.0
Default Gateway:     172.17.8.253
Port 48 802.1q trunk - allowed VLAN's 1-3 (tagged), 11 (untagged)
ESW Switch 2
Native VLAN 11
IP Address:     172.17.8.102 255.255.252.0
Default Gateway:     172.17.8.253
Port 48 802.1q trunk - allowed VLAN's 1-3 (tagged), 11 (untagged)
ESW Switch 3
Native VLAN 11
IP Address:     172.17.8.103 255.255.252.0
Default Gateway:     172.17.8.253
Port 48 802.1q trunk - allowed VLAN's 1-3 (tagged), 11 (untagged)
hostname 3750switch
enable secret 5 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
enable password xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
no aaa new-model
switch 2 provision ws-c3750g-48ts
system mtu routing 1500
udld aggressive
ip subnet-zero
ip routing
ip domain-name mydomain.com
ip name-server 172.17.10.216
ip name-server 172.17.10.229
mls qos map cos-dscp 0 8 16 26 32 46 48 56
mls qos srr-queue input bandwidth 90 10
mls qos srr-queue input threshold 1 8 16
mls qos srr-queue input threshold 2 34 66
mls qos srr-queue input buffers 67 33
mls qos srr-queue input cos-map queue 1 threshold 2 1
mls qos srr-queue input cos-map queue 1 threshold 3 0
mls qos srr-queue input cos-map queue 2 threshold 1 2
mls qos srr-queue input cos-map queue 2 threshold 2 4 6 7
mls qos srr-queue input cos-map queue 2 threshold 3 3 5
mls qos srr-queue input dscp-map queue 1 threshold 2 9 10 11 12 13 14 15
mls qos srr-queue input dscp-map queue 1 threshold 3 0 1 2 3 4 5 6 7
mls qos srr-queue input dscp-map queue 1 threshold 3 32
mls qos srr-queue input dscp-map queue 2 threshold 1 16 17 18 19 20 21 22 23
mls qos srr-queue input dscp-map queue 2 threshold 2 33 34 35 36 37 38 39 48
mls qos srr-queue input dscp-map queue 2 threshold 2 49 50 51 52 53 54 55 56
mls qos srr-queue input dscp-map queue 2 threshold 2 57 58 59 60 61 62 63
mls qos srr-queue input dscp-map queue 2 threshold 3 24 25 26 27 28 29 30 31
mls qos srr-queue input dscp-map queue 2 threshold 3 40 41 42 43 44 45 46 47
mls qos srr-queue output cos-map queue 1 threshold 3 5
mls qos srr-queue output cos-map queue 2 threshold 3 3 6 7
mls qos srr-queue output cos-map queue 3 threshold 3 2 4
mls qos srr-queue output cos-map queue 4 threshold 2 1
mls qos srr-queue output cos-map queue 4 threshold 3 0
mls qos srr-queue output dscp-map queue 1 threshold 3 40 41 42 43 44 45 46 47
mls qos srr-queue output dscp-map queue 2 threshold 3 24 25 26 27 28 29 30 31
mls qos srr-queue output dscp-map queue 2 threshold 3 48 49 50 51 52 53 54 55
mls qos srr-queue output dscp-map queue 2 threshold 3 56 57 58 59 60 61 62 63
mls qos srr-queue output dscp-map queue 3 threshold 3 16 17 18 19 20 21 22 23
mls qos srr-queue output dscp-map queue 3 threshold 3 32 33 34 35 36 37 38 39
mls qos srr-queue output dscp-map queue 4 threshold 1 8
mls qos srr-queue output dscp-map queue 4 threshold 2 9 10 11 12 13 14 15
mls qos srr-queue output dscp-map queue 4 threshold 3 0 1 2 3 4 5 6 7
mls qos queue-set output 1 threshold 1 138 138 92 138
mls qos queue-set output 1 threshold 2 138 138 92 400
mls qos queue-set output 1 threshold 3 36 77 100 318
mls qos queue-set output 1 threshold 4 20 50 67 400
mls qos queue-set output 2 threshold 1 149 149 100 149
mls qos queue-set output 2 threshold 2 118 118 100 235
mls qos queue-set output 2 threshold 3 41 68 100 272
mls qos queue-set output 2 threshold 4 42 72 100 242
mls qos queue-set output 1 buffers 10 10 26 54
mls qos queue-set output 2 buffers 16 6 17 61
mls qos
macro global description cisco-global
errdisable recovery cause link-flap
errdisable recovery interval 60
no file verify auto
spanning-tree mode rapid-pvst
spanning-tree loopguard default
spanning-tree extend system-id
vlan internal allocation policy ascending
interface GigabitEthernet2/0/1
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
spanning-tree portfast trunk
interface GigabitEthernet2/0/2
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
spanning-tree portfast trunk
interface GigabitEthernet2/0/3
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
spanning-tree portfast trunk
interface GigabitEthernet2/0/4
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
spanning-tree portfast trunk
interface GigabitEthernet2/0/5
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
spanning-tree portfast trunk
interface GigabitEthernet2/0/6
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
spanning-tree portfast trunk
interface GigabitEthernet2/0/7
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
spanning-tree portfast trunk
interface GigabitEthernet2/0/8
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
spanning-tree portfast trunk
interface GigabitEthernet2/0/9
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
interface GigabitEthernet2/0/10
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
spanning-tree portfast trunk
interface GigabitEthernet2/0/11
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
interface GigabitEthernet2/0/12
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
interface GigabitEthernet2/0/13
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
interface GigabitEthernet2/0/14
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
spanning-tree portfast trunk
interface GigabitEthernet2/0/15
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
spanning-tree portfast trunk
interface GigabitEthernet2/0/16
switchport access vlan dynamic
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
spanning-tree portfast trunk
snip
interface GigabitEthernet2/0/47
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
spanning-tree portfast trunk
interface GigabitEthernet2/0/48
switchport trunk encapsulation dot1q
switchport trunk native vlan 11
switchport trunk allowed vlan 1-3,11
switchport mode trunk
interface GigabitEthernet2/0/49
interface GigabitEthernet2/0/50
interface GigabitEthernet2/0/51
interface GigabitEthernet2/0/52
interface Vlan1
ip address 10.0.1.254 255.255.255.0
ip helper-address 172.17.10.229
interface Vlan2
ip address 10.0.2.254 255.255.255.0
ip helper-address 172.17.10.229
interface Vlan3
ip address 10.0.3.254 255.255.255.0
ip helper-address 172.17.10.229
interface Vlan11
ip address 172.17.8.253 255.255.252.0
ip default-gateway 172.17.8.1
ip classless
ip route 0.0.0.0 0.0.0.0 172.17.8.1
ip http server
control-plane
line con 0
line vty 0 4
password xxxxxxxxxxxxxxxxxxxxx
login
length 0
line vty 5 15
password xxxxxxxxxxxxxxxxxxxxx
login
length 0
end
3750switch#

Hyper-V Vlan tagging. Question

Hi everyone,
The question is simple. My NIC is a Realtek PCI GBe familly controller, Priority and VLAN are enabled. I havent any physical switch and when i create an external virtual switch on hyper-v if I add a VM on VLAN 2 why it doesnt have Internet access or can
pingn the router ?
The virtual external switch has no default vlan on it, so it supoosed to be on TRUNK mode. I also have a static route on my router 192.168.2.0/24 -> 192.168.1.254.
If I add a VM with no VLAN tag and manually assign the IP adress it can communicate with the router but if I add a VLAN tag it doesnt.
What you think ?
Thanks

Hi Sir,
>>If I add a VM with no VLAN tag and manually assign the IP adress it can communicate with the router but if I add a VLAN tag it doesnt.
The simple answer is that gateway interface are not in same Vlan as the VM's .
As you know , different vlan can not access each other without route for Vlan .
>>The virtual external switch has no default vlan on it, so it supoosed to be on TRUNK mode.
I assume that you mean the vlan setting when you created external virtual switch :
(Actually , this Vlan setting applies to the virtual NIC for hyper-v host , if you uncheck "Allow management operating system to ..." the vlan setting will unavailable )
Based on my understanding of your case (One NIC connecting to router ), you may need to config "single arm route " on that router (it is a network question not hyper-v ).
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

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

Dfme and vlan tagging

Hi all,
is it possible that dmfe driver can handle tagged vlans?
I use SunOs5.9 with patch 116561-12, which should give the ability for vlan tagging, but I can�t ping the other boxes.
I�ve configured 2 Ip-addrs on a nic (dmfe1,dmfe1:1) netmasks and routing seems to be ok.
Any help is appreciated

Congratulations. You have successfully confused me.
Do you know the difference between VLAN and Virtual interfaces?
A virtual interfaces are of the form <interface><instance>:<virtual instance> and lives on top of the normal interface and, in a way, just adds another IP to it.
Example of virtual interfaces:
dmfe1:2
Where dmfe is the interface, 1 is its instance and 2 is the virtual instance.
VLAN taging is somewhat more complex, and gives you seperate traffic on each VLAN. A VLAN interface is constructed as:
<interface>.<three digit VLAN><three digit Instance>
To create a VLAN tag for VLAN 888 on dmfe1, the VLAN number would be 888 and the instance 001, which would give you an interface of
dmfe.888001
To create a VLAN tag for VLAN 44 on dmfe0:
dmfe.044000
7/M.

Using Link Aggregation and VLAN tagging with LDOMs

Hi,
Anyone know if Link aggregation combined with VLAN tagging works for LDOMs?
Any links or references would be appreciated.....
It would be very handy if each LDOM could have multiple interfaces on different VLANs....
Regards,
Daniel

I agree with bzptlx. While you can have vswitch plumbed without net-dev, and then route traffic inside the control domain, so that you can utilize aggregation, it adds complexity, and in some environments it's just impossible.
I would say that this is number 1 deficiency with LDOM's in general.

RV320 and WAN VLAN tagging/IPTV

I have a fiber connection on WAN1 which only works with VLAN tagging and I can't find a way to make it work without the provider's middleware router (Comtrend C5813)... Is there a way to connect to my FTTH (Lucent I240G-B) router directly? I'm having problems with my IPTV (multicast) service, if it's connect direct to the middleware I can have multiple channels running at once, but if I go back to the RV320 and do the same, everything start to pixelate.
Using Wireshark I can see that the RV320 is connecting to the different channels with CS4 DSCP marking.
Any ideas?
Thank you!

As you can read above, I'm having problems with my IPTV pixelation/cuts... I need to be able to connect directly to the fiber and have more control over the connection, but I don't see the option on the web admin for PPPOE over VLAN. I don't know if it's a hardware limitation or just software (the GUI).

Jumpstarting changes with U6: VLAN tagged interfaces and sysidcfg

Hello,
I've been banging my head on U6 for a few days and finally have to give up and cry for help. I can no longer build a jumpstarted server which ends up on a separate VLAN tagged LAN after first reboot.
I have an existing U5 SPARC jumpstart environment setup. We use VLAN tagging a lot in our environments and by default the only time a non VLAN tagged interface is used is during jumpstart. With the existing jumpstart we are using the following profiles:
root_password=mypassword
security_policy=NONE
timezone=GB
timeserver=localhost
terminal=vt100
network_interface=none {hostname=hostname}
system_locale=en_GB
name_service=NONE
system_locale=CIn the U5 profile we let the jumpstart server obtain its network configuration via DHCP and then obtain the profile above, which excludes all network settings. All the network settings were added as part of a finish script. This worked fine with U5. As far as I can see, with U6 at the point where the sysidcfg is first evaluated it removes the network settings and obviously then kills the jumpstart. So I have had to try a different approach. I have tried both of the following:
network_interface=PRIMARY { default_route=none protocol_ipv6=no}
network_interface=PRIMARY { dhcp default_route=none protocol_ipv6=no}However, using either of these causes the ce0, bge0 or whatever to remain defined, instead of the ce200000 and ce206000 interfaces that I have explcitly defined in hostname.ce200000 separately. I also get a number of arp errors on initial reboot, such as
Nov 20 20:27:29 unknown ip: ip_arp_done: init failed
Nov 20 20:27:29 unknown /sbin/dhcpagent[44]: configure_v4_lease: cannot set interface flags for ce0: Cannot assign requested addressI don't know if I am barking up the wrong tree but I believe I need to get the server on initial boot (or during finish) to reevaluate a different sysidcfg file. Alternatively, it might need some combination of presence/absence of /reconfigure or /etc/.UNCONFIGURED. I think I might also need to stop /sbin/netstrategy return dhcp specific results (I only use DHCP for jumpstart booting and not for normal boot), but I have no idea how to do that...
# /sbin/netstrategy
ufs ce0 dhcpAny help much appreciated!
thanks
Paul

Paul,
I don't want to suggest that I understand your problem but have you seen the comments about tagged vlans on the Opensolaris LDoms forum?
Near the bottom of thread [Solaris 10 10/08 (update 6)|http://www.opensolaris.org/jive/thread.jspa?threadID=81505&tstart=0] there is some discussion of tagged vlan support changes with U6.
It sounds like tagged vlans are going to be a problem with U6.
have a good weekend,
Glen

C2504 with LAG and VLAN tagging

Having issues with setting up LAG on a Cisco 2504 WLC and implementing VLAN tagging on the different SSID´s.
Without LAG I had this up and running by using dynamic interfaces and assigning the different SSID´s to a perticular interface which was then assigned a specific VLAN.
However once I enabled LAG on the 2504, the dynamic interfaces became disabled and im unable to find documentation on how to configure VLAN tagging on SSID´s when using LAG.
Relevant info:
Cisco 2504 WLC running 7.4.100.0 (FUS 1.8.0)
Cisco 2602 APs
Cisco 3560 switch running IOS 15 (c3560-ipbasek9-mz.150-2.SE3)
Switch output:
C3560-PoE8#show etherchannel 1 summary
Flags: D - down        P - bundled in port-channel
        I - stand-alone s - suspended
        H - Hot-standby (LACP only)
        R - Layer3      S - Layer2
        U - in use      f - failed to allocate aggregator
        M - not in use, minimum links not met
        u - unsuitable for bundling
        w - waiting to be aggregated
        d - default port
Number of channel-groups in use: 1
Number of aggregators:           1
Group Port-channel Protocol    Ports
------+-------------+-----------+-----------------------------------------------
1      Po1(SU)          -        Fa0/1(P)    Fa0/2(P)    Fa0/3(P)
                                 Fa0/4(P)
WLC output:
(Cisco Controller) >show lag summary
LAG Enabled
So basically what im trying to achieve is to implement LAG, use 2 SSID´s which are tagged in VLAN 300 and 400 respectively and keep management traffic untagged.

Hi Scott,
Yes I did.. But it seems that after deselecting the "Interface/Interface Group(G)" under the SSID´s and then selecting the dynamic interface again that the problem is resolved.

VLAN Tags and Hyper-V Switches

Does the Hyper-V 2012 Virtual Switch support forwarding VLAN-tagged packets to a guest OS with the VLAN tags intact? In other words, can I have a single virtual NIC handle multiple VLANs by doing the VLAN filtering inside the guest OS?
I would like to run a guest OS that sits on multiple VLANs, and while I could create and delete virtual NICs which are assigned to a single VLAN, it would be much more flexible in my environment to have Hyper-V simply forward frames with the VLAN (802.1q)
tags intact so that the guest OS can see the tags and deal with them appropriately. (looking at running a virtual router that sits across multiple VLANs).
I can't see any obvious way to do this. I thought that leaving the VLAN tag for the guest off would cause packets to be forwarded unfiltered, but that appears to not be the case. Does anyone know how to enable forwarding tagged frames through
a virtual switch/NIC to a guest OS?
Thanks!

Hi,
> Does it depend on any particular settings on the physical NIC?
No special settings on the physical NIC, but not every NIC support VLAN tagging. You should generally not set the VLAN ID at the physical NIC, it should be set on either the Virtual Switch or the individual Virtual Machine’s configuration. The VLAN ID on
the Virtual Switch is what the Host or Parent Partition uses. The VLAN ID setting on the individual Virtual Machine’s settings is what each VM will use.
For more information please refer to following MS articles:
Understanding Hyper-V VLANs
http://blogs.msdn.com/b/adamfazio/archive/2008/11/14/understanding-hyper-v-vlans.aspx
VLAN Tricks with NICs - Teaming & Hyper-V in Windows Server 2012
http://blogs.technet.com/b/keithmayer/archive/2012/11/20/vlan-tricks-with-nic-teaming-in-windows-server-2012.aspx#.UWznBmawrX0
Set-VMNetworkAdapterVlan
http://technet.microsoft.com/en-us/library/hh848475(v=wps.620).aspx
Hope this helps!
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Lawrence
TechNet Community Support

VLAN Tagging

I am trying to utilize a wireless device in a customer site that extends VLAN to the wireless infrastructure. My device does not support VLAN Tagging, so it will not work. My question is this: Is this the norm, requireing end-point devices to insert VLAN Tags in the normal ethernet frame, or do most environments perform the Tag insertion/stripping at teh acces point level. Since they can use multiplpe SSIDs on their access points, can a new SSID be set up for another wireless VLAN that does not require VLAN Tagging?

In a Cisco environment you configure your VLANs on your switches and configure the switchport the AP is connected to as a trunk port. On the AP you define the VLANs and SSIDs and tie each SSID to a VLAN. End devices connect to an SSID and when connected to that SSID are automatically connected to it's matching VLAN. The end device (be it a PC, barcode reader or whatever) doesn't need to know anything about VLANs or which VLAN it needs to connect to, as long as it's associated to the correct SSID it will be on the correct VLAN.

LOM VLAN tagging?

All,
I'm wondering if anyone has had any luck getting LOM to do vlan tagging. According to the manpage for ipmitool, it should support it by going "ipmitool lan set vlan id <vlanidnumber>" but it rejects it and prints the acceptable commands for ipmitool lan set, and none of them are vlan.
So, did Apple just compile ipmitool without the vlan option, does the Apple implementation of ipmi not support it? It's a huge pain in the rear to do MAC based vlanning (requires a radius server), so I'd really prefer to do it with vlan tagging, since it should work.
Thanks!

Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Just to muddy the waters, since VLAN edge/access ports don't normally tag frames with VLAN IDs, referencing your question about two computers "talking" to each other, it doesn't matter whether the two ports or on the same switch or even different switches; or in the same VLAN or not.
Also understand trunk ports normally tag frames, and edge/access ports don't, but an exception for the former is the "native" VLAN frames aren't tagged, and an exception for the latter, a Voice VLAN will tag frames.

VLAN tagging and tagging question

Similar Messages

Maybe you are looking for