[nsp] VLAN settings on 2950s/2610s

Security security at cytanet.com.cy
Sat May 10 19:48:12 EDT 2003


The use of the native command did not help. I used it on the subinterface
of the cisco2610 and also on the trunk port on the switch. The only way to
make trunking work was to configure two VLANs on the 2950 switch without
using VLAN1. I am thinking to proceed and upgrate the switch software
and/or the router IOS to see what will happen.


>This is correct, I've had this issue when switching from a 7206 to a 3620.
>I think the the 7206 didn't require "native" on the VLAN1 interface, and
>worked fine.  Could have been a firmware issue.
>
>Just make sure to add the "native" command on the end like Ryan suggested.
>
>interface FastEthernet4/0.1
> encapsulation dot1Q 1 native
>
>
>Sharan
>
>----- Original Message -----
>From: "Ryan O'Connell" <ryan at complicity.co.uk>
>To: <security at cytanet.com.cy>; <cisco-nsp at puck.nether.net>
>Sent: Friday, May 09, 2003 10:25 AM
>Subject: Re: [nsp] VLAN settings on 2950s/2610s
>
>
>> At 09/05/2003 16:12, Security wrote:
>> >I spend several hours working with catalyst2950 switch and a Cisco2610
>> >router trying to configure VLAN trunking using 802.1q. I Discover that
>when
>> >one of the VLANs is the default (VLAN1) trunking is not working. Using
>> >other vlans e.g vlan2 and Vlan3 trunking is working perfectly.
According
>to
>> >Cisco Documentation trunking should also work with VLAN1 as one of the
>> >VLANs.
>> >
>> >Can anyone advise? I am thinking of a bug on the software of the switch
>but
>> >your advice will be appreciated
>>
>> Make sure you have Native (default) VLANs set properly both sides -
>> switches have a default native VLAN and router don't. Anything in the
>> native VLAN doesn't get tagged when being sent out, so the router will
>drop
>> it when receiving it unless one subinterface has been marked "native".
>>
>>  From memory, by default on the 2950 the default native VLAN is 1 so you
>> need to make sure you use "encapsulation dot1q 1 native" on the 2610 for
>> the appropriate subinterface. (This is from memory though, I may have it
>wrong)
>>
>> _______________________________________________
>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>> http://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>
>
>
>
_____________________________
CYTANET WebMail
http://webmail.cytanet.com.cy


More information about the cisco-nsp mailing list