Thanks for the reply. The device can understand 802.1q and can tag/untag frames. The cisco is outside my control and I have very little experience with the native vlan setting. My thinking is that the cisco config should be something like
switchport mode trunk switchport trunk encapsulation dot1q swtitchport allowed vlan 100,201 (some of that syntax may not be correct) and that if I am doing tagging on the access device, the native vlan part of the config is not needed On Wed, May 14, 2008 at 7:50 AM, Jeff Cartier <[EMAIL PROTECTED]> wrote: > If the device is incapable of understanding IEEE 802.1Q then it will not > be able to recognize and interpret the tagged frames, and will only > understand the native/untagged vlans. It should only be communicating > on the native vlan. > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Chad Whitten > Sent: Wednesday, May 14, 2008 8:44 AM > To: [email protected] > Subject: [c-nsp] vlan tagging question > > I have a non-cisco access device connecting to a cisco 3750 via gigE. > The 3750 interface is set for 802.1q trunking with two vlans - 100 and > 201. Vlan 201 is the native vlan on the cisco interface. Should the > access device be tagging packets on vlan 201 or leaving them untagged? > > -- > Chad Whitten > Metro Network Solutions > (601) 366-6630 Phone > (601) 366-6066 Fax > (601) 842-6804 Cellular > [EMAIL PROTECTED] > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > -- Chad Whitten Metro Network Solutions (601) 366-6630 Phone (601) 366-6066 Fax (601) 842-6804 Cellular [EMAIL PROTECTED] _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
