Network Management

UDT Business Layer Process has high CPU usage on an additional polling engine

An additional polling engine is at 95% CPU usage. The Business Layer was split to run separate processes, the the UDT business layer is at approximately 50-70% CPU usage. The CPU usage is high due to polling layer 2 (L2) and layer 3 (L3) information.

First published date

10/30/2018 9:17 PM

Last published date

10/30/2018 9:17 PM

Overview

An additional polling engine is at 95% CPU usage. The Business Layer was split to run separate processes, the the UDT business layer is at approximately 50-70% CPU usage.

Product section

User Device Tracker

Cause

This seems to have been caused by the load on that server -- a combination of the number of jobs, ports, and large devices, and possibly SNMP delays.

 

  • UDT Scalability
    • UDT now supports:
      • 90K ports per polling engine 
      • 300K ports or more, maximum per instance (multiple polling engines) 
  • UDT_Job:
    • 300 Jobs L2 and L3 Jobs over last 3 days
    • Bringing back 70,000 ports

Resolution

  1. Edit UDT Settings -> Layer 2 Polling and change the value to 1200 minutes.
  2. Edit UDT Settings -> Layer 3 Polling and change the value to 1200 minutes.
  3. Edit UDT Settings -> SNMP pacing delay time and change the value to 1 (currently it is set 0 by default) on Device Tracker Advanced Settings page.
    If there are undesired side effects you may set this value back to zero.