After a K1000 hostname change and default inventory cycle, Agent-managed devices might not update the last host value in the amp_auto.conf file correctly if the Agent has been running for a period of time. If Agents do not update the lasthost value before the DNS routing to the K1000 server is changed, they cannot locate the K1000 and they become orphaned.
This is a known issue with the 6.4 release of the K1000. The issue is expected to be resolved in a future release of the K1000 product
KA-1903.
Workaround
Steps to follow to make sure K1000 renames successfully with 6.4 agent:
1) Add routing for new K1000 hostname in DNS, leaving old hostname resolvable as well.
2) Rename K1000 from K1000 administrative interface.
3) Restart the agent(s) (no need to reboot the system, just restarting the agent is sufficient), and wait for or force inventory
4) New K1000 name should be saved as lasthost in amp_auto.conf
5) Drop the record for the old K1000 name from DNS, agent will retry connection, and it should reconnect with the new K1 name
If agents are orphaned and stuck to trying to connect with the old K1000 name that's no longer resolvable:
1) Add old K1000 name back to DNS
2) Use AMPTools resetconf host=new_k1_name (replacing new_k1_name with the new hostname of your K1000) once agents reconnect to the old K1000 name
Or
3) Restart agent, and wait for or force inventory after agent reconnects
This issue is expected to be resolved in a future release of the K1000 product.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center