Can you provide me the debug output? Also, what happens if you rcdp the devices's IP address directly, does it work each time? If yes, it could actually be an issue with the upstream device.
thanks,
-marcus
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Marcus, thanks for the response... file is attached. First section is the normal run so you can see the output a little more clearly, then the same command with -d. Let me know what you think.
It seems that they do always return NA. When i point at them directly, they seem to be functional. I only have a read only string, so there is only 1 snmp community in that spot of the conf file.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It seems that they do always return NA. When i point at them directly,
they seem to be functional. I only have a read only string, so there is
only 1 snmp community in that spot of the conf file.
Sorry for the delay, I work this project on the side from my regular job. Can you try your discovery without the -l flag (ie -rq) and see if the IPs for your C3560-8PC show up?
thanks,
-marcus
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just to be more specific this could be an issue with the "-v" flag, so please try the "-rq" and if this works you can try the "-rlq" and also see if this works. This would still give you serials and uplink output.
thanks,
-marcus
Last edit: Marcus Beaman 2014-05-12
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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.
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.
Can u try doing a clear CDP table on the upstream switch and then run rcdp
60 sec later?
On May 15, 2014 5:30 PM, "Kakisger" kakisger@users.sf.net wrote:
And i should have added, yes, i do see the full CDP detail info.
OK, thanks for trying. Not sure why the one switch is returning bad SNMP
hex string, but maybe we can setup a webconference. I have some time
between 1-3pm PST or let me know if you have a date/time that works and
I'll see if I'm available.
It simply doesn't discover their IP address as neighbors. The specific model number is WS-C3560-8PC. Just wondering if anyone else has had this issue.
Last edit: Kakisger 2014-02-24
Can you provide me the debug output? Also, what happens if you rcdp the devices's IP address directly, does it work each time? If yes, it could actually be an issue with the upstream device.
thanks,
-marcus
Marcus, thanks for the response... file is attached. First section is the normal run so you can see the output a little more clearly, then the same command with -d. Let me know what you think.
Hello Marcus, just checking to see if you had a chance to look the logs over. Thank you in advance.
Hey,
Sorry I haven't had a chance to look at it yet. I will get to it this week and send out an update.
thanks,
-marcus
No problem. I know how that goes. Let me know if you need any more data.
Do the C3560-8PC devices always return NA for an IP, or do they sometimes
return an real IP address?
If you rcdp the C3560-8PC device directly, does it always return and IP
address or will it fail also?
Also, on our SNMP strings, put the RW string first, then a RO string as the
order is important.
thanks
-marcus
On Sat, Mar 15, 2014 at 10:39 AM, Kakisger kakisger@users.sf.net wrote:
It seems that they do always return NA. When i point at them directly, they seem to be functional. I only have a read only string, so there is only 1 snmp community in that spot of the conf file.
If you have multiple SNMP strings in your config file, can you please put
the read string first and re-run the test.
thanks,
-marcus
On Wed, Mar 26, 2014 at 6:55 AM, Kakisger kakisger@users.sf.net wrote:
I just have a single r/o community in the file and also on the devices.
Hi Kakisger,
Sorry for the delay, I work this project on the side from my regular job. Can you try your discovery without the -l flag (ie -rq) and see if the IPs for your C3560-8PC show up?
thanks,
-marcus
Just to be more specific this could be an issue with the "-v" flag, so please try the "-rq" and if this works you can try the "-rlq" and also see if this works. This would still give you serials and uplink output.
thanks,
-marcus
Last edit: Marcus Beaman 2014-05-12
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.
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:
All the cdp configs are pretty standard, we don't fiddle with them. Definitely open to a web conference... when would you have time?
And i should have added, yes, i do see the full CDP detail info.
Can u try doing a clear CDP table on the upstream switch and then run rcdp
60 sec later?
On May 15, 2014 5:30 PM, "Kakisger" kakisger@users.sf.net wrote:
Tried that, no go sir.
OK, thanks for trying. Not sure why the one switch is returning bad SNMP
hex string, but maybe we can setup a webconference. I have some time
between 1-3pm PST or let me know if you have a date/time that works and
I'll see if I'm available.
thanks,
-marcus
On Mon, May 19, 2014 at 9:41 PM, Kakisger kakisger@users.sf.net wrote:
Marcus, i have time all afternoon today if you do.