Network Change & Configuration Management

Reply

Side effects of changing the "End Host Expiration Hours" setting to 7 days

Authority
Posts: 36
1763     0

Because we need a longer overview of the end hosts on our network, we would like to change the "End Host Expiration Hours" setting to 168 hours.

Are there any know side effects of doing this? Like an exploding database? Or slower reaction times of the GUI/API?

 

We've got about 100k end hosts on our network across ~6000 network devices.

 

Re: Side effects of changing the "End Host Expiration Hours" setting to 7 days

Adviser
Posts: 407
1764     0

I would open a case, not that I'm aware of Smiley Happy But I've never tested it.

 

 

Follow me on LinkedIn: https://www.linkedin.com/in/sifbaksh
Twitter: https://twitter.com/sifbaksh

Re: Side effects of changing the "End Host Expiration Hours" setting to 7 days

Expert
Posts: 127
1764     0

I've never tried extended this beyond 24 hours, but one thought is that this might skew the numbers of actual connected end points if you are using a lot of DHCP and users going from wired connections then to wireless and back.

 

Proceed with caution Smiley Surprised)

-Lon.

Showing results for 
Search instead for 
Do you mean 

Recommended for You