PAMSC HNode Information Update Frequency

Products

• CA Privileged Access Manager - Server Control (PAMSC)

Issue/Introduction

PAMSC endpoint OS information is queried from the Enterprise Management DMS using the command below. If the server's kernel gets updated, how long does it take to get updated in the DMS?

 # selang -c "host [email protected]; sr hnode pamscendpoint1.example.com props(HNODE_INFO)"

Resolution

Endpoint information is updated when policyfetcher sends a heartbeat to the ENTM server. This occurs during service startup and periodically based on the following seos.ini tokens:

• check_deployment_tasks: Defines how often (in seconds) policyfetcher checks for tasks. Default is 3600 (1 hour).
• endpoint_heartbeat: Defines the frequency of heartbeats as a factor of the check_deployment_tasks setting. Default is 6.

By default, the heartbeat is sent every 6 hours. To verify when the heartbeat is sent, search policyfetcher.log for "sending heartbeat to DH" for entries similar to the following example.

sending heartbeat to DH...(editres HNODE ("pamscendpoint1.example.com") node_type+("ACU") latest_keep_alive("01/01/26@01:01") node_version+("ACU:14.10.80.52") node_ip+("##.##.##.##") node_info("Linux 5.14.0-611..."))

For immediate HNODE updates after a change is made to the endpoint, restart the PAMSC services on the endpoint to send the newest heartbeat.