KBI 311775 Issue Addressed: Ping Blast Timeout Error Timeout. Error: 301 In System Down Rule

Version

Argent Advanced Technology 5.1A-1904-C and below

Date

Friday, 23 August 2019

Summary

System Down Rule using Ping Blast checking in Cascade Logic could be broken always due to timeout error

The Relator trace log could look like following:

Fri Jul 19 10:15:05.237 ARTSMON01 xxargent Start testing server 192.168.90.4 (Engine: 32-bit, Trace: Normal)

Fri Jul 19 10:15:05.238 ARTSMON01 xxargent STARTED Ping Blast worker thread

Fri Jul 19 10:15:08.440 ARTSMON01 xxargent STARTED Ping Blast worker thread

Fri Jul 19 10:15:11.642 ARTSMON01 xxargent STARTED Ping Blast worker thread

Fri Jul 19 10:15:14.651 ARTSMON01 xxargent STARTED Ping Blast worker thread

Fri Jul 19 10:15:17.867 ARTSMON01 xxargent STARTED Ping Blast worker thread

Fri Jul 19 10:15:21.226 ARTSMON01 xxargent STARTED Ping Blast worker thread

Fri Jul 19 10:15:24.559 ARTSMON01 xxargent STARTED Ping Blast worker thread

Fri Jul 19 10:15:27.825 ARTSMON01 xxargent STARTED Ping Blast worker thread

Fri Jul 19 10:15:31.090 ARTSMON01 xxargent STARTED Ping Blast worker thread

Fri Jul 19 10:15:34.387 ARTSMON01 xxargent STARTED Ping Blast worker thread

Fri Jul 19 10:15:44.809 ARTSMON01 xxargent Total of 10 ping requests were tested

Fri Jul 19 10:15:44.809 ARTSMON01 xxargent >>> Total Time Consumed: 39.578 <<<

Fri Jul 19 10:15:44.809 ARTSMON01 xxargent Timeout. (Error: 301)

Fri Jul 19 10:15:45.200 ARTSMON01 xxargent (Result) Failed to ping blast server ‘192.168.90.4’ – Broken

Fri Jul 19 10:15:45.856 ARTSMON01 xxargent Performance data is saved successfully

The issue is caused by invalid default value for packet size (3)

The issue has been addressed in Argent AT 5.1A-1907-A

Technical Background

The minimum packet size in Ping test is 32 bytes

The invalid value of 3 bytes causes the Ping timeout always

Resolution

Edit the production System Down Rule and change packet size from 3 to 32 bytes