Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
Webcast-Catalyst9k
New Member

Strange log entry

I am doing a debug all on a 2621xm that has very little traffic on it. I am seeing the following message on the 2621xm that I can't figure out:

Local MobileIP: FastEthernet0/1 add 172.30.8.29 rejected

*Mar 1 15:47:27.029: IP ARP req filtered src 172.30.8.29 0003.6d1a.7f3f, dst 17

2.30.8.200 0000.0000.0000 wrong cable, interface FastEthernet0/1

*Mar 1 15:47:27.033:

Local MobileIP: FastEthernet0/1 add 172.30.8.29 rejected

*Mar 1 15:47:27.033: IP ARP req filtered src 172.30.8.29 0003.6d1a.7f3f, dst 17

2.30.8.52 0000.0000.0000 wrong cable, interface FastEthernet0/1

I have no idea what this means and Cisco's output interpreter cant tell me anything either.

The setup I have is as follows:

2621XM (fast0/1.1 dot1q vlan 100)---->4006(port 6/48 dot1q trunk)---->3640 (fast0/0.2 dot1q vlan100 from port 3/2 on the same 4006 also trunked).

Now fast0/0.1 on the 3640 has the 172.30.8.x network configured on it so these packets are coming from that interface over the the 2621.

I guess there are a few things going on but if I can figure out this 'wrong cable' error, I might just have everything else fall in line.

Thanks for any input.

2 REPLIES
Bronze

Re: Strange log entry

The 2621 is sending an arp request for 172.30.8.29, and realizes that the 172.30.8.x network is not configured on that interface (hence the failure).

This can sometimes be caused by policy routing, or perhaps you have a static route that points to a physical interface as its next-hop (as opposed to an IP address)?

New Member

Re: Strange log entry

Well, it turned out to be pretty straightforward.

Simply put, I had a 4006 on the one side that was set to trunk mode on the port that was linked to the router. That switch was then connected to another router through another port that was trunked as well. Most of that 4006 is filled with users on the 172.30.8 segment. I only wanted to have packets from a seperate VLAN go across the link to the 2621. I just had to put that uplink port in the single VLAN instead of trunking it.

Pretty simple after I figured it out.

Thanks for the response.

115
Views
0
Helpful
2
Replies
CreatePlease to create content