The Endpoint Security server identifies a host as an inactive host when its agent has not interacted with the server for a specified time period (its aging period). When a host is identified as inactive, it is added to the count of inactive hosts on the Web UI dashboard.
You can specify the time period after which the Endpoint Security (HX) server identifies a host as inactive using the Web UI or the CLI.
Defining the Inactivity Time Period Using the Web UI
To define the inactivity time period using the Web UI:
In the Web UI, select Aging Settings on the Admin menu. The Aging Settings page appears.
In the Host Aging area of the page, enter the inactivity time period in the Show on the dashboard when hosts are inactive for: box.
Specify the inactivity period in days, hours, minutes, or seconds, or any combination of these. A minimum of one day must be specified. A maximum of 365 days can be specified. For example,
45 days 6 hours 30 minutes 15 secondsis a valid entry. Note that24 hoursis not a valid entry, although1 dayis.Click Save.
Note
If you click Cancel, your Host Aging settings are not saved. To discard changes and revert to default settings, after you have clicked Save, click Reset to defaults next to the Show on the dashboard when hosts are inactive for: box.
Defining the Inactivity Time Period Using the CLI
To define the inactivity time period using the CLI:
hostname > enable
hostname # configure terminalEnable the CLI configuration mode:
Enter the aging period for inactive agents:
hostname (config) # hx agent inactivity period <seconds>Valid values range from 86400 seconds (one day) through 31536000 seconds (one year). The default is 2582000 seconds (30 days).
To restore the default inactivity aging period:
hostname (config) # no hx agent inactivity periodVerify the updated host inactivity time period settings:
hostname (config) # show hx agent inactivity
Save your settings:
hostname (config) # write mem