Re: Native VLAN?

  If you are an "access" interface, then you aren't passing any VLAN
information. The VLAN ID at that point is significant only to the switch
for grouping other devices in that specific broadcast domain. So the two
switches that are connected via access interfaces are unaware of the
difference. Now, it could make your documentation confusing but it
certainly will work just fine. I think that is what Hopalong is looking
for.

--Hammer--

On 9/30/2010 10:25 AM, Keith Matsepe wrote:
> Switch is trying to negotiate a trunk, use
>
> switchport mode access
>
>
> Rgds,
> Molomo
>
> On Thu, Sep 30, 2010 at 4:59 PM, --Hammer-- <bhmccie_at_gmail.com
> <mailto:bhmccie_at_gmail.com>> wrote:
>
> I'm sorry. To clarify, there is NO vlan information passing on
> the links because you are defined as an access interface.
>
> HTH,
>
>
> --Hammer--
>
>
> On 9/30/2010 9:47 AM, hopalong wrote:
>
> Hi
>
> I have two access ports connected to one another one is
> configured as
>
> interface FastEthernet0/2
> duplex full
> speed 100
> switchport access vlan 502
>
> and the other as
>
> switchport mode access 162
>
> This link seems to be working fine! The only clue I have is
> that the cdp
> neighbor entry at the vlan 502 end says that the native vlan
> is 162.
>
> No native vlans are defined. How is this working?
>
> Thanks
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Thu Sep 30 2010 - 10:29:49 ART