1 Reply Latest reply on Feb 19, 2013 1:53 AM by ZycaR

    Having issues with neighbor discovery timeouts

    mattbro

      (This is a fairly new build of 3.1 that was upgraded to 3.1.1 on 2/13/13)

       

      I keep running into issues getting neighbor discovery from a fairly busy "Core" router.

       

      I have tried adjusting the SNMP timout settings from 2500 to 5000 in both Polling Settings and IPAM Subnet Scan Settings. All that seemed to do was double the time it took to scan subnets.

       

      I have verified that I can SNMPWALK the OID ok (it is slow but it does eventually return everything):

      snmpwalk -v 2c -c public 1.2.3.4 1.3.6.1.2.1.4.22

       

      Neighbor discovery is working fine for other subnets/routers. Can someone verify exactly which setting controls the timeout for Neighbor Discovery? (And, what else that setting will also affect if you know).

       

      I do actually have records in the IPAM_History table for the problematic subnet for some Neighbor Scans that run overnight but the IPAM_EVENTS table shows that it errored every time so my guess is that overnight it at least is able to get partial results but during the day when the router is busier, I am not getting any results.

       

      SQL that I am using to see that I am getting results from Neighbor scans at least some of the time:

      select top 10000 * from IPAM_IPHistoryReport h where h.ARP = 1 and h.Source = 'Neighbor Scan' and h.IPAddress like 1.2.3%' ORDER BY Time DESC

       

      Any pointers on logs or SQL tables to find more info for troubleshooting would be appreciated as well!

       

      I ran a SQL query to show some of the events:

      select top 1000 * from IPAM_Events where EventType = 975 or EventType = 976 order by EventTime DESC

       

      I only have event 975 for the subnet/router I am having issues with. All of the 976 events are for a different subnet/router that is working great.

       

      2/15/13 8:19 AM 976 SYSTEM The neighbor scanning of 'Current IC Client Network' started at 2/15/2013 8:19:38 AM has finished successfully. 552 IP(s) were found. The scan duration was '0' minutes.

      2/15/13 8:08 AM 975 SYSTEM Neighbor scanning for subnet 'SSM IC Servers (core)' failed with error: Cannot get ARP table from device 1.2.3.4. Error: Timeout [31040]

      2/15/13 8:08 AM 975 SYSTEM Neighbor scanning for subnet 'SSM IC Servers (core)' failed with error: Cannot get ARP table from device 1.2.3.4. Error: Timeout [31040]

      2/15/13 7:19 AM 976 SYSTEM The neighbor scanning of 'Current IC Client Network' started at 2/15/2013 7:19:33 AM has finished successfully. 507 IP(s) were found. The scan duration was '0' minutes.

      2/15/13 7:09 AM 975 SYSTEM Neighbor scanning for subnet 'SSM IC Servers (core)' failed with error: Cannot get ARP table from device 1.2.3.4. Error: Timeout [31040]

      2/15/13 7:09 AM 975 SYSTEM Neighbor scanning for subnet 'SSM IC Servers (core)' failed with error: Cannot get ARP table from device 1.2.3.4. Error: Timeout [31040]

      2/15/13 6:19 AM 975 SYSTEM Neighbor scanning for subnet 'SSM IC Servers (core)' failed with error: unknown error

      2/15/13 6:19 AM 976 SYSTEM The neighbor scanning of 'Current IC Client Network' started at 2/15/2013 6:19:33 AM has finished successfully. 698 IP(s) were found. The scan duration was '0' minutes.

      2/15/13 6:16 AM 975 SYSTEM Neighbor scanning for subnet 'SSM IC Servers (core)' failed with error: Cannot get ARP table from device 1.2.3.4. Error: Timeout [31040]

      2/15/13 5:19 AM 976 SYSTEM The neighbor scanning of 'Current IC Client Network' started at 2/15/2013 5:19:38 AM has finished successfully. 698 IP(s) were found. The scan duration was '0' minutes.

      2/15/13 5:16 AM 975 SYSTEM Neighbor scanning for subnet 'SSM IC Servers (core)' failed with error: unknown error

      2/15/13 5:08 AM 975 SYSTEM Neighbor scanning for subnet 'SSM IC Servers (core)' failed with error: Cannot get ARP table from device 1.2.3.4. Error: Timeout [31040]

      2/15/13 5:06 AM 975 SYSTEM Neighbor scanning for subnet 'SSM IC Servers (core)' failed with error: Cannot get ARP table from device 1.2.3.4. Error: Timeout [31040]

      2/15/13 4:19 AM 976 SYSTEM The neighbor scanning of 'Current IC Client Network' started at 2/15/2013 4:19:32 AM has finished successfully. 476 IP(s) were found. The scan duration was '0' minutes.

       

      Thanks for any help you can provide!

      Matt