https://community.hpe.com/t5/server-management-systems/bi-weekly-data-collection/m-p/4093567#M29920 I have 4 servers that are failing in the bi weekly data collection. I thought that they may be failing due to the backup running, causing bandwidth errors so I ran them during a weekend day when very is very little happening and they still failed. I receive the following error in the results windows.<BR /><BR />[SNMP] This system failed to respond to SNMP in the timeout interval.<BR />Root Cause: The system is no longer running SNMP, or the agent is responding more slowly than the timeout value set for the system.<BR />Corrective Action: Check network and configuration of target system. Try adjusting the SNMP timeout value for the system in the System Protocol Settings page. Verify the SNMP read community has not changed. Rerun Data Collection.<BR /><BR />Data collection on this system was aborted due to a timeout or it was abruptly stopped. Data may be incomplete.<BR />Root Cause: Data collection on the target system has taken longer than allowed. This can be due to network connectivity issues, a busy target system, or timeout values set too low.<BR />Corrective Action: Check network and configuration of target system. Check the following settings (and adjust values as needed) using mxglobalsettings: Detached_DC_Timeout, Storage_DC_Timeout, DC_Abandon_Latency (all in seconds)<BR /><BR />SNMP is running fine. How Do I check and adjust the settings for Detached_DC_Timeout, Storage_DC_Timeout, DC_Abandon_Latency?<BR /> Mon, 29 Oct 2007 08:15:08 GMT mwalders 2007-10-29T08:15:08Z https://community.hpe.com/t5/server-management-systems/bi-weekly-data-collection/m-p/4093567#M29920 I have 4 servers that are failing in the bi weekly data collection. I thought that they may be failing due to the backup running, causing bandwidth errors so I ran them during a weekend day when very is very little happening and they still failed. I receive the following error in the results windows.<BR /><BR />[SNMP] This system failed to respond to SNMP in the timeout interval.<BR />Root Cause: The system is no longer running SNMP, or the agent is responding more slowly than the timeout value set for the system.<BR />Corrective Action: Check network and configuration of target system. Try adjusting the SNMP timeout value for the system in the System Protocol Settings page. Verify the SNMP read community has not changed. Rerun Data Collection.<BR /><BR />Data collection on this system was aborted due to a timeout or it was abruptly stopped. Data may be incomplete.<BR />Root Cause: Data collection on the target system has taken longer than allowed. This can be due to network connectivity issues, a busy target system, or timeout values set too low.<BR />Corrective Action: Check network and configuration of target system. Check the following settings (and adjust values as needed) using mxglobalsettings: Detached_DC_Timeout, Storage_DC_Timeout, DC_Abandon_Latency (all in seconds)<BR /><BR />SNMP is running fine. How Do I check and adjust the settings for Detached_DC_Timeout, Storage_DC_Timeout, DC_Abandon_Latency?<BR /> Mon, 29 Oct 2007 08:15:08 GMT https://community.hpe.com/t5/server-management-systems/bi-weekly-data-collection/m-p/4093567#M29920 mwalders 2007-10-29T08:15:08Z https://community.hpe.com/t5/server-management-systems/bi-weekly-data-collection/m-p/4093568#M29921 Hi mwalders<BR /><BR />You can navigate to HP SIM installed directory. For eg C:\Program Files\HP\System Insight Manager\Config\mxglobalsettings.props.<BR /><BR />Open the file in note pad. Find the above parameters and you define the timeout for those.<BR /><BR /> Fri, 02 Nov 2007 12:18:40 GMT https://community.hpe.com/t5/server-management-systems/bi-weekly-data-collection/m-p/4093568#M29921 Rider 2007-11-02T12:18:40Z https://community.hpe.com/t5/server-management-systems/bi-weekly-data-collection/m-p/4093569#M29922 Did you ever find a real resolution to this, or what setting to change?<BR /><BR />I just upgraded a few servers to PSP 8.40 and now my Data Collection (HP SIM 6) to those servers is getting this error on almost all of them. Wed, 12 May 2010 15:01:34 GMT https://community.hpe.com/t5/server-management-systems/bi-weekly-data-collection/m-p/4093569#M29922 James Kennedy_4 2010-05-12T15:01:34Z