SystemEDGE Agent doesn't always respond to remote SNMP polls.

Document ID:  TEC1175019
Last Modified Date:  08/04/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA SystemEDGE

Releases

  • CA SystemEDGE:Release:5.9

Components

  • SYSTEMEDGE AGENT:SEAGNT
  • SYSTEM EDGE CORE AGENT:SEAGT
Issue:

The SystemEDGE agent runs high CPU usage and Ehealth is not able to collect the performance data on a consistent basis.

Cause:

SystemEDGE is a single threaded application, and it will not be able to respond to bulk SNMP requests while it is in the process of updating the MIB.

The following entry in the Sysedge.log is a good indicator the Server is overloaded (CPU and\or disk subsystem) and this is impacting SystemEDGE's ability to refresh the MIB in a timely manner:

query_monitor_entries(): Performance problem detected (monitoring cycle). Elapsed time 185.826648s). SystemEDGE may not be responding to SNMP queries during that time.

 

 

Resolution:

This issue is brought about by Server\OS performance issues.    Review server configuration and consider increasing CPU and\or memory and review disk subsytem for potential I\O related bottlenecks.

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >