hj lee wrote: > In passive mode, it maintains token_recv_count and mcast_recv_count. > Whenever a token or mcast msg is received, the corresponding count is > increased by 1. Also it compares this count to other interface. If that > difference is more than rrp_problem_count_threshold, then the interface > (has smaller count value) becomes FAULTY, won't be used any more until > administrator fixes it.
Can I assume that token_recv_count and mcast_recv_count are also internal variables? Also, do those counters reset or otherwise reset over time? I would assume they would have to, otherwise a few stray packets over time would cause an inevitable FAULT being declared on a NIC? If this is the case, what is the mechanism? Or is it assumed that the number of usual-dropped-packets will average out over time? I can't see that being very reliable though. Thanks for replying! You explanation was *exactly* what I needed to hear to help me understand this. Digi _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
