Marcus Beaman - 2014-05-15

Hey,

Digging through more of the debug, those devices are showing up with
invalid IPes. Each CDP neighbor should have a hex representation of it's
IP, but for those I'm seeing some wierd value (top one is a valid hex
address, bottom one is the not:

DEBUG: Device returned "0x0a2db40e"
DEBUG: Device returned "
-n
"
you might try clear the cdp table on the upstream switch (kin-mdf-stack),
and each C3560-8PC to see if this clear the problem up (enable mode, "clear
cdp table")

thanks,

-marcus

On Thu, May 15, 2014 at 1:43 PM, Marcus Beaman beamanm@gmail.com wrote:

I agree, rcdp grabs the ip address for the devices the same as doing a
"sho cdp nei detail". If you run that on the upstream switches, do you see
an IP address for the devices? If you do, then there is some disconnect in
the CDP neighbors SNMP MIB for those devices. You could also verify the
CDP configs are consistent on the devices "sho run | inc cdp", and/or
remove the SNMP config from the upstream device and re-add it to see if
this clears the MIBs up. Make sure any "cdp source interface" commands
have IP addresses assigned to them (if the commands is applied).

At some point I we could also setup a web conference to do some
troubleshooting real time.

thanks,

-marcus

On Thu, May 15, 2014 at 11:55 AM, Kakisger kakisger@users.sf.net wrote:

Hey Marcus, it seems to have the same result. What seems to be happening
is that when the 3560 is discovered via CDP, it's IP is not being picked
up... so then it gets put on the "SK NO IP" (skip no ip i think). So even
when we do verbose, the IP is just not being parsed from that switch.

Having problem with Cisco 3560 8 port switches and some 3560s in general.https://sourceforge.net/p/rcdp/discussion/general/thread/2b9dc0be/?limit=50#f1b2

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/rcdp/discussion/general/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/