This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Missing endpoint information from an active port - UDT v3.2

Missing endpoint information from an active port - UDT v3.2

NPM 11.0.1

UDT 3.2

We are having two issues with UDT -

1. Missing endpoint information from an active port. This is not on every port, probably very few but still not accurate.

2. Endpoint changing IP address via DHCP - seeing a 2-3 hr lag where both IP's are listed (duplicate device) for the port.

Per Solarwinds support we have implemented several things but to no avail.

UDT polling set to 20 minutes instead of the default 30 minutes

Installed NPM 11.0.1 HotFix4

Moved UDT devices from an additional poller over to our primary poller (very low polling/reduced traffic)

Question - We have several printers attached to a switch. The ports that printers are attached to are listed as active (as it should) and it does show the active connection with the MAC and IP address but only in Port history. Could these devices be going into a "sleep" mode and that is why UDT is not showing it as a constant "current" connection?

Does anyone have any suggestions or recommendations on what we can do ?

Thank you

-Gino

  • Hi Gino,

    I am curious as to the status of your issue. I have similar
    issues in a larger environment and assumed that it was related to the network
    size. Do the mac addresses show in the mac address table of your host device?
    Also, what snmp version are you running ?

         

    Thanks

    David

  • Hi David,

    We actually made this change in our environment - Moved UDT devices from an additional poller over to our primary poller (very low polling/reduced traffic). We did not install NPM 11.0.1 Hotfix4 in our production environment because when we tested it in our dev environment

    it did not make a difference.

    >1. Missing endpoint information from an active port. This is not on every port, probably very few but still not accurate.

    We found the reason why certain devices are not displayed even though they have a persistent connection onto a port.

    The devices are those that go into "sleep" mode such as printers and wyse terminals. We are using a work-around by adding those devices

    (since they are always connected to the same port) as a node in NPM and having it poll the device which in turn causes UDT to show its

    connections - mac and ip addresses and hostname (if it's in dns).

    >2. Endpoint changing IP address via DHCP - seeing a 2-3 hr lag where both IP's are listed (duplicate device) for the port.

    We still do not have a solution for the 2/3 hour lag time when a connection changes its ip addess.

    Note: I noticed that there are new hotfixes available that pertain to UDT that may help.

    User Device Tracker v3.2.0 - Hot Fix 1, 2, 3

    SolarWinds Orion Core 2014.2.1 Hotfix7

    Thanks,

    Gino