POMdev wrote: 
> This has produced output condensed into the following ~25 hour report
> for 7 radios:
> 
> > 
Code:
--------------------
  >   >       number of failed pings: ----------------------- ----- quick, full 
resets
  > dev/loc      params    index:     0   1  2 3 4  5 6 7  8  9 10 
  > Ofc  2S Ping 2s3q6f Fails[9]: 33429 225  1 0 0  0 0 0  0  0 0
  > bsmt  M Ping 2s3q6f Fails[9]: 33381  58  0 0 1 69 2 0 75  3 0
  > LR   1F Ping 2s3q6f Fails[9]: 32106 178  3 0 4 54 2 0 76 16 0
  > Kit  1E Ping 2s3q6f Fails[9]: 33261 168  1 1 3 67 1 0 77  5 0
  > MBR  2E Ping 2s3q6f Fails[9]: 28918 748 58 3 1 36 2 0 53 11 0    (22 hours)
  > Ofc  2N Ping 2s3q6f Fails[9]: 34452 130  1 1 0 21 0 0 32 10 0
  > bsmt  W Ping 2s3q6f Fails[9]:  7487  14  0 0 0  0 0 0  0  0 0    (<6 hrs)
  > ---- activity -------    ok        q      f    q  f 
  > 
--------------------
> > 
> 
> A quick reset was performed after 3 failed pings, and a full reset
> after 6. Array indexes [0 - 7] display the number of failed pings
> counted before the system had a successful ping. Array indexes [8] and
> [9] count the number of times the quick and full reset actions were
> performed. The full reset sets the failed ping counter to 1 (to keep
> trying), so index [7] is zero. Index [10] is unused.
> 
> By far, the pings succeed with zero intervening failures, so the [0]
> numbers are large. The radios had some 1, and just a few 2 ping
> failures, which likely would not be noticed. Three ping failures
> before recovery were not seen in earlier testing, so the radios
> performed a quick reset [8] at the 3rd ping failure. These succeeded
> most of the time, with recoveries shown in indexes [3..6]. These lower
> outages might not cause interruption. Full recoveries were required in
> 3/75 to 10/32 of the cases. The reason the quick reset works or
> doesn't is unknown at this time. The full recovery has worked reliably
> for the last 6 months.

Could you please try to explain this a little more clearly? I'm not
completely following your explanation of the various numbers. I assume
that based on your explanation, "Ping 2s3q6f" indicates that it's
pinging every 2 seconds and doing a quick reset after 3 failed pings and
a full reset after 6 failed pings. But I get lost on the 10 array
digits. What's the difference between array indexes 0-7 if they're all
counts of failed pings? When does a failed ping increment index 0 vs 1
vs 2, etc? What event(s) triggers each index to reset (if they do
reset)?


------------------------------------------------------------------------
RichardDavies's Profile: http://forums.slimdevices.com/member.php?userid=35024
View this thread: http://forums.slimdevices.com/showthread.php?t=111663

_______________________________________________
Radio mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/radio

Reply via email to