RFC 4544, "Definitions of Managed Objects for Internet Small Computer System Interface (iSCSI)", May 2006
Note: This RFC has been obsoleted by RFC 7147Source of RFC: ips (tsv)
Errata ID: 61
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2006-07-04
Rejected by: Lars Eggert
Date Rejected: 2008-12-19
(9) common problem with indiscontinuity tagging The Session Stats Table defines and admits High-Capacity (64-bit) and Low-Capacity (32-bit) octet counters. If both types of counters are implemented, according to the DESCRIPTION clauses of all these counters, [...] If this counter has suffered a discontinuity, the time of the last discontinuity is indicated in iscsiSsnDiscontinuityTime." Hence, iscsiSsnDiscontinuityTime must indicate discontinuities in the HC and the LC counters, i.e. it must be changed whenever one of the LC counters wraps back to zero, making it almost useless for efficient surveillance of discontinuities in all the other counters covered by this object. Perhaps, as it has been done in a few other IETF MIBs in the past, inclusion of additional 32-bit counters yielding the high part (most significant 32 bits) of the HC counters for use with SNMPv1 management stations would have allowed to change the semantics of iscsiSsnDiscontinuityTime to avoid too frequent changes.
Item (9) - the situation in which "one of the LC counters wraps back to
zero" is a regular increment of a continuous counter, i.e., it
is not a discontinuity. Thus, this item is unfounded.