Attachment uploads are currently disabled. This is a temporary situation and will resume as normal in the coming days.
UNSOLVED
- But doesn't that deviate from the standard then? I can explicitly tag VLAN 1 on HP and 3Com gear, and eventhough they don't call it 'tagging', I can do this on Cisco gear as well.
Perhaps I just bought the wrong brand.Message Edited by Bradc314 on 01-09-2006 09:00 AM
- Nothing in the IEEE 802.1q standard specifies that the device must be capable of tagging the native VLAN.The implementation of the 802.1q standard on the current PowerConnect switches (3300, 3400, 5324, 6024) does not allow for the tagging of traffic on VLAN 1 or the native VLAN. If you need to pass VLAN 1 traffic on a trunk, you would need to use VLAN 1 as the native (untagged) VLAN for both devices participating in the trunk.This implementation is similar to current Cisco switches (2970, 3750) in which the native VLAN traffic is transmitted untagged.
- The problem arises when you try to configure teaming and VLAN support in the Intel PRO/1000MT Nic's that came with my PowerEdge 2850's. Each VLAN defined for the team must be tagged or else it won't work. You cannot create an untagged vlan virtual adapter. Our infrastructure uses VLAN 1 actively, and since we've been using 3Com, HP, and Cisco gear, it's never been an issue. Now, with the Dell Switch it is.
I'm glad I found this out now and not down the road (we've budgeted to replace all of our switches this year, and we WERE going to go with Dell).
Thanks for the help.
GregG1
2 Intern
•
812 Posts
583
0
Posted January 9th, 2006 11:00