I just figured it out. There is a "feature" that was supposed to be
fixed on the 2600 in this release, but it was not. I'm running 12.1(5)
and they say this problem was fixed in anything after 12.1(3). Back
then, the native VLAN IP address had to be configured on the major
interface, not on a subinterface. I removed the subinterface for VLAN 1
and configured it on the major interface and everything works great. If
I upgrade to 12.1(6), I would have to go back to the normal method,
placing the native VLAN on a subinterface like all the others.
Regards,
John
>>> "Tim O'Brien" <[EMAIL PROTECTED]> 2/20/01 1:12:53 PM >>>
That is very weird. Have you tried changing the encapsulation type and
then
rebooting both of the boxes to clear any "remains" out?
Tim
----- Original Message -----
From: "John Neiberger" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 20, 2001 2:57 PM
Subject: Re: ARP issue with 802.1q Trunking
Unfortunately, that doesn't even make sense in this scenario. I'm
using
a straight-through cable from the router to the switch, and ISL
trunking
is working great. I only get that error when I change the
encapsulation
type. Weird, huh?
thanks,
John
>>> "Tim O'Brien" <[EMAIL PROTECTED]> 2/20/01 12:54:05 PM >>>
The only thing that I could find is "Verify the cable selection
(crossover
versus non-crossover)".
Tim
----- Original Message -----
From: "John Neiberger" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 20, 2001 2:25 PM
Subject: ARP issue with 802.1q Trunking
I have a 2620 connected to a 2924XL using ISL trunking. Three VLANs
configured on both sides, VLAN 1 is the management VLAN. I can ping
from the router to the switch and vice versa.
Now, I changed the encapulation type on both sides to dot1q and
communication breaks. Turning on debugging, I found the following
problem. Apparently, the 2620 is throwing out the ARP replies from
the
switch. Here is the output from debup arp:
00:15:09: IP ARP: sent req src 10.16.102.70 0030.8546.b740,
dst 10.16.102.16 0000.0000.0000 FastEthernet0/0.1
00:15:09: IP ARP: sent req src 10.16.102.70 0030.8546.b740,
dst 10.16.102.16 0000.0000.0000 FastEthernet0/0.1
00:15:09: IP ARP rep filtered src 10.16.102.16 0005.3214.99c0, dst
10.16.102.70
0030.8546.b740 wrong cable, interface FastEthernet0/0
00:15:09: IP ARP rep filtered src 10.16.102.16 0005.3214.99c0, dst
10.16.102.70
0030.8546.b740 wrong cable, interface FastEthernet0/0
What the heck does wrong cable mean? The only potential problem I
see
is that it is sending the ARP request out fa0/0.1, but receiving the
reply on fa0/0. Is there some configuration step that I'm missing?
I've never tried to configure dot1q before, but it seems to me that if
the native vlan is the same on both sides that the only configuration
difference would be the encapsulation type on each side.
Can any of you provide any advice concerning this? And changing back
to ISL isn't going to solve my problem because I'm just playing around
and I want to make this work! :-)
Thanks,
John
_________________________________
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
