cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post
Highlighted
Level 11

UDT loses device information

UDT loses device information in some switches. When I do UDT discovery again, I got port information back, but within one hour it's lost again! In some other Cisco swithes with same model, same IOS and same basic configuration, device info stays as it should. Something to do about it?

0 Kudos
10 Replies
Highlighted
Level 12

Re: UDT loses device information

What are your polling intervals?

polling jobs.JPG

0 Kudos
Highlighted
Level 11

Re: UDT loses device information

At start it was default 30min but after that i've tried the other values.

New information of my problem: Now devices have shown in port list for couple of days. I just don't know why! There is nothing in switch configurations that could affect to this. I made re-discovery in wednesday morning, and devices disappeared from there quite soon. When i made the same again in afternoon, they suddenly started to stay in list. Why's that? Bug?!? As told, the other switch with identical configuration is showing all the devices correctly (that other switch also lost devices once before, but now works ok) but this one needed MANY discoveries to work ok.

0 Kudos
Highlighted
Level 12

Re: UDT loses device information

I had similar problem like this, except it was happening to ALL of my switches

What you can do is run the UDT compatibility checker against the switch that does not keep the devices as well as your L3 device where the IP addresses are registered.

You would then see the MAC addresses are being discovered in the L2 job on the switches and also see if these MAC addresses are present in the ARP table.

If they are present on both, then you have a UDT issue that would be case for Tech Support

Highlighted
Level 11

Re: UDT loses device information

shawn_b,

Where do I find the 'UDT compatibility checker' ? Having same issue on a handful of switches, and would to follow your suggestion before escalating to solarwinds support.

ellen.

0 Kudos
Highlighted
Level 11

Re: UDT loses device information

Shawn_b,

I found the 'UDT compability checker' standalone tool. It was documented in Solarwinds Knowledgebase. SolarWinds Knowledge Base :: User Device Tracker Compatibility Checker

Thank you Shawn_b for your suggestions. I'm working through it to identify why some nodes are UDT PITA nodes.

0 Kudos
Highlighted

Re: UDT loses device information

Ismo,

please contact our support for this issue.

Regards

Peter

0 Kudos
Highlighted
Level 11

Re: UDT loses device information

Ports are showing devices correctly now. As I told in last message, I made discovery again (actually that was 4th time in whole history) and now information stays in sheet as it should.

So, you still think I should contact support? Right now I can't show you anything that doesn't work ok... 

0 Kudos
Highlighted

Re: UDT loses device information

UDT is broken in so many ways that it's making me cry; I have had cases for months and they have still not fixed the code. There are fundamental flaws in the way it works (I am not talking feature requests here, I am talking that design is not working issues. ).


check for message like this:

2014-04-29 10:12:49,962 [ 27] WARN    -   ScheduleOrUpdateJob() - job scheduling was aborted (Capability is disabled [N:6407|Layer3|disabled|30|1].)  [SolarWinds.UDT.BusinessLayer.Polling.UDTJobManager]

if it fails to poll something from a node for some reason then it decides that the node no-longer supports that functionality. For example if the retrieval of the L3 tables fails for some reason it will stop fetching L3 data and not report this anywhere (other than buried in a logfile, or a check-box on the edit-node page). Instead of rediscovery try going to the edit-node details and checking that it is polling for L2 and/or L3 data

If you have Jumbo frames enabled and/or your SNMP devices return more than ~4K of UDP data then the SNMP library used by UDT will fail. There is buddy-drop for 3.0.1 (not integrated into 3.0.2 but it works for 3.0.2 ) that fixes this.

This is just one of the fundamental design errors: a an assumption by a programmer in one part of the code has ramifications and side-effects throughout the whole product that make troubleshooting almost impossible.

Richard

Highlighted
Level 11

Re: UDT loses device information

if it fails to poll something from a node for some reason then it decides that the node no-longer supports that functionality. For example if the retrieval of the L3 tables fails for some reason it will stop fetching L3 data and not report this anywhere (other than buried in a logfile, or a check-box on the edit-node page). Instead of rediscovery try going to the edit-node details and checking that it is polling for L2 and/or L3 data

Actually, after I got information to stay in table, I even disabled L2 and L3 polling from "edit node" settings, and even that didn't remove port data. So these settings doesn't seem to affect to anything in normal L2 switches.

0 Kudos