LMS 3.2 Campus Manager - Throttle SNMP User Tracking?

Answered Question
Nov 22nd, 2009
User Badges:

Hi,


We monitor a network through a firewall controlled by a third party and we are experiencing lost icmp packets during the snmp get stage of User Tracking acquistion at 1000 and 1400 for approximately a minute. It seems to be flooding the link at these times causing false outages for our other NMS systems.


Is there a way to throttle/slow down the number of snmp requests being sent by User Tracking acquisition?


Cheers,

Sigfrid

Correct Answer by Joe Clarke about 7 years 4 months ago

You cannot throttle the number of requests on a device basis, no.  However, you can control the number of UT threads that run in parallel.  By default, UT will run 12 parallel threads to acquire users.  You can decrease this in NMSROOT/campus/etc/cwsi/ut.properties by modifying the ThreadPool.vmpsadmin.count property.  I'm not sure if this will help your particular situation, but it may be worth a try.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Joe Clarke Sun, 11/22/2009 - 14:44
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

You cannot throttle the number of requests on a device basis, no.  However, you can control the number of UT threads that run in parallel.  By default, UT will run 12 parallel threads to acquire users.  You can decrease this in NMSROOT/campus/etc/cwsi/ut.properties by modifying the ThreadPool.vmpsadmin.count property.  I'm not sure if this will help your particular situation, but it may be worth a try.

eidumsigfrid Sun, 11/22/2009 - 14:46
User Badges:

Cheers mate, will it require a restart after changing the ut.properties file?

Joe Clarke Sun, 11/22/2009 - 14:54
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

The property file needs to be modified while UT is NOT running.  Nothing will need to be restarted.  The next time UT runs, it will re-read the file, and only spawn the specified number of threads.

eidumsigfrid Sun, 11/22/2009 - 20:17
User Badges:

Reducing the number of concurrent threads has resolved this issue.


Thanks.

Actions

This Discussion

Related Content