Hi Michael,
Try:
interface Ethernet2/0.16
encapsulation dot1Q 16 native
Your router is sending out an ARP request with dot1q tag 16. The other
system responds, but when the switch returns the ARP reply to your
router, it's not tagging the frame and your router is receiving it in
what it believes is the native VLAN (VLAN 1, by default). That's why
you're getting the "wrong cable" message -- if you tell the router the
native VLAN is 16, it will treat the incoming ARP reply as arriving on
E2/0.16, instead of E2/0.
Alternatively you can set the native VLAN on the switch side to the
default value, 1 ("default switchport trunk native vlan" or
"switchport trunk native vlan 1"). This will cause the switch to tag
the ARP reply frame with dot1q 16 and your router will treat it
accordingly.
cheers,
Dale
On Sun, May 17, 2009 at 12:22 PM, Michael Jones <majonestx_at_gmail.com> wrote:
> sure
>
> RSRack1R6#sho run int ethernet 2/0
> Building configuration...
>
> Current configuration : 57 bytes
> !
> interface Ethernet2/0
> no ip address
> full-duplex
> end
>
> RSRack1R6#sho run int ethernet 2/0.16
> Building configuration...
>
> Current configuration : 87 bytes
> !
> interface Ethernet2/0.16
> encapsulation dot1Q 16
> ip address 16.0.0.6 255.0.0.0
> end
>
>
> Here is my switch config.- I know the problem lies between these two. I have
> even created a vlan 16 SVI and on the below switch and haven't been able to
> get icmp
> across the trunk link. There is a another sub interface that works fine up
> and down the switch. Which im sure isolates this to a native vlan issue.
>
> RSRack1SW2#sho run int fa0/6
> Building configuration...
>
> Current configuration : 150 bytes
> !
> interface FastEthernet0/6
> switchport trunk encapsulation dot1q
> switchport trunk native vlan 16
> switchport mode trunk
> duplex full
> end
Blogs and organic groups at http://www.ccie.net
Received on Sun May 17 2009 - 12:30:54 ART
This archive was generated by hypermail 2.2.0 : Mon Jun 01 2009 - 07:04:43 ART