11/30/2022 11:39:16 AM System Health Memory Up 410 MB 11/30/2022 11:38:30 AM System Health Memory Down The queries for the following channel IDs returned no data: 2,3,4,5 (code: PE269) 11/30/2022 11:17:16 AM System Health Memory Up 410 MB 11/30/2022 11:16:30 AM System Health Memory Down The queries for the following channel IDs returned no data: 2,3,4,5 (code: PE269) 11/30/2022 11:08:16 AM System Health Memory Up 410 MB 11/30/2022 11:07:30 AM System Health Memory Down The queries for the following channel IDs returned no data: 2,3,4,5 (code: PE269) 11/30/2022 11:05:40 AM System Health Memory Up 410 MB 11/30/2022 11:05:30 AM System Health Memory Down The queries for the following channel IDs returned no data: 2,3,4,5 (code: PE269) 11/30/2022 11:04:16 AM System Health Memory Up 410 MB
Article Comments
11/30/2022 11:39:16 AM System Health Memory Up 410 MB 11/30/2022 11:38:30 AM System Health Memory Down The queries for the following channel IDs returned no data: 2,3,4,5 (code: PE269) 11/30/2022 11:17:16 AM System Health Memory Up 410 MB 11/30/2022 11:16:30 AM System Health Memory Down The queries for the following channel IDs returned no data: 2,3,4,5 (code: PE269) 11/30/2022 11:08:16 AM System Health Memory Up 410 MB 11/30/2022 11:07:30 AM System Health Memory Down The queries for the following channel IDs returned no data: 2,3,4,5 (code: PE269) 11/30/2022 11:05:40 AM System Health Memory Up 410 MB 11/30/2022 11:05:30 AM System Health Memory Down The queries for the following channel IDs returned no data: 2,3,4,5 (code: PE269) 11/30/2022 11:04:16 AM System Health Memory Up 410 MB
Article Comments.
Hi Seif,
The error message indicates that PRTG sends and that the target device replies, but with the message that the data is no longer available on the target Cisco device. As this only happens sporadically and is automatically resolved with the next scanning interval according to the logs, it might be related to an overload on this device. I recommend to raise the scanning interval to at least 300s to check if this helps to relieve the system.
If this does not help, also take a look at the target machine's load, to see if for instance the CPU utilization is high during the time it cannot reply to PRTG's SNMP requests.
Kind regards,
Felix Saure, Technical Support Team
Dec, 2022 - Permalink
Hi Seif,
The error message indicates that PRTG sends and that the target device replies, but with the message that the data is no longer available on the target Cisco device. As this only happens sporadically and is automatically resolved with the next scanning interval according to the logs, it might be related to an overload on this device. I recommend to raise the scanning interval to at least 300s to check if this helps to relieve the system.
If this does not help, also take a look at the target machine's load, to see if for instance the CPU utilization is high during the time it cannot reply to PRTG's SNMP requests.
Kind regards,
Felix Saure, Technical Support Team
Dec, 2022 - Permalink