Device dicscovery issue with Sysedge

Article Id: 4670

Status: Published

Updated On: 14-02-2018 08:19

Legacy Id: TEC1823671

Products:

EHEALTH - MISC , CA eHealth Performance Management - Data Polling , CA eHealth Performance Management - Usage and Administration , DEVELOPER PROG , REMOTE POLLER

Issue/Introduction:

Device discovery issue with Sysedge. Element names are changing automatically after discovery

Cause:

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.

Environment:

Sysedge 5.8.2eHealth 6.3.2.11Windows 2008 Server

Resolution:

Server Automation Policy causing problem with the trap_community on the agent pc, we removed the the manager_name * from the sysedge.cf file.