That's called a trunk. The switch expects to receive frames tagged with the vlan that the frame should be deposited in. If you're plugging a server into port 1, its NIC will need to support 802.1q.
The "switchport voice vlan" command mentioned is actually a trunk link with some pruning (simplification). The switch still expects the frames destined for the voice vlan to have a .1q tag with the specified voice vlan ID.
Mmm. In that case, perhaps I have been working under a misapprehension.
I thought that the point was that the phone didn't have to add the dot1q VLID tag, hence the phone did not have to be hard coded with its VLAN number. I thought it left the VLAN id as zero, but marked CoS 5 on the dot1p. The switch then recognises voice traffic by VLID=0 and CoS=5, and put all that traffic in the voice VLAN, while all other traffic got put in the access VLAN.
Of course, the phone MAY put in the correct VLAN if it wants. If a switch receives a dot1q frame tagged with its access VLAN, then it forwards it on the access VLAN. In the same way, if it receives a dot1q frame tagged with the voice VLAN, then it will forward it on the voice VLAN. If it receives a frame with a dot1q frame tagged with a NULL VLID AND CoS 5, then it forwards it on the voice VLAN.
Usualy, NIC cards don;t support 802 dot1Q for they must be member of untagged vlan. one NIC can only be member of one and only one untagged vlan. device to device, such as say, a PIX to a Switch, can be on a tagged VLAN.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...