Device discovery issue with Sysedge. Element names are changing automatically after discovery
Issue with Sysedge :
suspecting the Server Automation Policy causing problem with the trap_community on the agent pc, we removed the the manager_name * from the sysedge.cf file.
Recycled the sysedge agent.
- Also found the name resolution issues on the ehealth server, added a host entry for the agent in the hosts file.
- Ran Walktree from both ends using ip, name and fqdn all are working now.
- Ran the discovery from the ehealth and it discovered the agent successfully.
Server Automation Policy causing problem with the trap_community on the agent pc, we removed the the manager_name * from the sysedge.cf file.