[c-nsp] %CDP-4-DUPLEX_MISMATCH - But they aren't connected!

[Tuc at T-B-O-H.NET]

> 
> Tuc at T-B-O-H.NET wrote:
> 
> >>> 	The setup looks like this :
> >>>
> >>> TRANSIT1                  TRANSIT2
> >>>    |                         |
> >>>    |-E0/0                    |-E1/0
> >>>    |                         |
> >>> -------------------------------------
> >>>               3640
> >>> -------------------------------------
> >>>    |                         |
> >>>    |-E0/1                    |-E1/1
> >>>    |--------BVI1-------------|
> >>>    |                         |
> >>>    |-FA0/24                  |-FA0/24
> >>> ----------                ------------
> >>> 2924-1                      2924-2
> >>> ---------                 ------------
> >>>   |-FA0/15
> >>>   |
> >>>   |-Netgear Ethernet Over Power Extender
> >>>
> >>> 	So its complaining that FA0/15 on 2924-1 is mismatched
> >>> to E0/0 on the 3640. Well, DUH, no fooling. I would think 
> >>> the only things it cares about are 3640~E0/1&2924-1~FA0/24
> >>> and 3640~E1/1&2924-2~FA0/24 since those are the only 2 places
> >>> that the Ciscos directly connect. 
> >> What is on the other end of the Netgear Ethernet Over Power Extender on 
> >> Fa0/15 on 2924-1?
> >>
> > 	The other end is a NetGear Ethernet Over Power Router
> > (WGX102, part of the WGXB102 kit)
> >> Which device is complaining?  2924-1, the 3640, or both?
> >>
> > 	3640.......
> 
> Unless there is some type of bridging or leakage between TRANSIT1 and 
> the Netgear kit, it sure looks like a very strange bug.  E0/0 on the 
> 3640 isn't in any way touching Fa0/15 on 2924-1 at layer 2.
> 
	:-D

	Thats what I'm saying.... :)

	Any idea where to look to debug it? It happens maybe 20 times
a month, and its at a REMOTE (Not just meaning away from the office,
also meaning you need to drive 9 miles on the edge of the Atlantic
Ocean in a 4X4 to get there) site (Which this week I happen to be at)
so would like to do as much debug as possible while local.

		Thanks, Tuc