Aged Out Wireless Clients Not seen in past:168 hours.

  • 0
  • 1
  • Question
  • Updated 3 months ago
  • Answered
I am receiving the message shown above and am curious what this is actually describing. Is this advising me that if a wireless client is not seen on the network for 168 hours (7 days) that it is removed? I am using host lists to determine if you should have access to the network at this time. We have noticed on occasion that devices that were believed to be added to the lists are no longer present and must be added back to the host list. If this age out is not the underlying issue does what I am describing sound familiar and can anyone offer a solution or explanation?
Netsight v7.0.6.26, Identifi v10.21.02
Photo of Dean Ferraro

Dean Ferraro

  • 672 Points 500 badge 2x thumb

Posted 3 months ago

  • 0
  • 1
Photo of Ronald Dvorak

Ronald Dvorak, Embassador

  • 44,150 Points 20k badge 2x thumb
It's a setting in XMC.....

Client Cleanup Interval:
Wireless client statistics stored by the data collector are periodically cleaned up according to this  interval.
When the Collection Client Limit is reached, clients inactive longer than the time specified in the Time Between Collection Client Limit Events are aged out.

You'd set it here....

Photo of Dean Ferraro

Dean Ferraro

  • 672 Points 500 badge 2x thumb
Ron,

Thanks. So would this be part of the reason I seem to be dropping devices from static host lists? It is very far a few in between but nevertheless does happen. Could this be some kind of memory leak or something of this nature?
Photo of Ronald Dvorak

Ronald Dvorak, Embassador

  • 44,150 Points 20k badge 2x thumb
With "host list" you mean a end-system-group (=list of MACs) in Control?
Photo of Dean Ferraro

Dean Ferraro

  • 672 Points 500 badge 2x thumb
Yes exactly
Photo of Ronald Dvorak

Ronald Dvorak, Embassador

  • 44,150 Points 20k badge 2x thumb
That shouldn't have something to do with this setting but there is one that could remove the client from the group "Remove Associated MAC Locks and Occurrences in Groups"

Photo of Dean Ferraro

Dean Ferraro

  • 672 Points 500 badge 2x thumb
Ok I am familiar with these, you only make that mistake once.

Not a real big deal was just wondering if others had been experiencing any similar issues. I strongly doubt this is version specific as I have been noticing this since first deployed.

Thanks again

Dean