smilint output for ./HC-PerfHist-TC-MIB
Message Severities |
Severity | Count |
warning | 14 |
Message Types |
Type | Count |
type-unref (warning) | 7 |
type-without-format (warning) | 7 |
Messages:
HC-PerfHist-TC-MIB
1: -- extracted from rfc3705.txt
2: -- at Sat Feb 7 06:16:39 2004
57:
58: HCPerfValidIntervals ::= TEXTUAL-CONVENTION
58: warning -
warning: current type `HCPerfValidIntervals' is not referenced in this module
58: warning -
warning: type `HCPerfValidIntervals' has no format specification
59: STATUS current
60: DESCRIPTION
61: "The number of near end intervals for which data was
62: collected. The value of an object with an
63: HCPerfValidIntervals syntax will be 96 unless the
64: measurement was (re-)started within the last 1440 minutes,
65: in which case the value will be the number of complete 15
66: minute intervals for which the agent has at least some data.
67: In certain cases (e.g., in the case where the agent is a
68: proxy) it is possible that some intervals are unavailable.
69: In this case, this interval is the maximum interval number
70: for which data is available."
71: SYNTAX Integer32 (0..96)
72:
73: HCPerfInvalidIntervals ::= TEXTUAL-CONVENTION
73: warning -
warning: current type `HCPerfInvalidIntervals' is not referenced in this module
73: warning -
warning: type `HCPerfInvalidIntervals' has no format specification
74: STATUS current
75: DESCRIPTION
76: "The number of near end intervals for which no data is
77: available. The value of an object with an
78: HCPerfInvalidIntervals syntax will typically be zero except
79: in cases where the data for some intervals are not available
80: (e.g., in proxy situations)."
81: SYNTAX Integer32 (0..96)
82:
83: HCPerfTimeElapsed ::= TEXTUAL-CONVENTION
83: warning -
warning: current type `HCPerfTimeElapsed' is not referenced in this module
83: warning -
warning: type `HCPerfTimeElapsed' has no format specification
84: STATUS current
85: DESCRIPTION
86: "The number of seconds that have elapsed since the beginning
87: of the current measurement period. If, for some reason,
88: such as an adjustment in the system's time-of-day clock or
89: the addition of a leap second, the duration of the current
90: interval exceeds the maximum value, the agent will return
91: the maximum value.
92:
93: For 15 minute intervals, the range is limited to (0..899).
94: For 24 hour intervals, the range is limited to (0..86399)."
95: SYNTAX Integer32 (0..86399)
96:
97: HCPerfIntervalThreshold ::= TEXTUAL-CONVENTION
97: warning -
warning: current type `HCPerfIntervalThreshold' is not referenced in this module
97: warning -
warning: type `HCPerfIntervalThreshold' has no format specification
98: STATUS current
99: DESCRIPTION
100: "This convention defines a range of values that may be set
101: in a fault threshold alarm control. As the number of
102: seconds in a 15-minute interval numbers at most 900,
103: objects of this type may have a range of 0...900, where the
104: value of 0 disables the alarm."
105: SYNTAX Unsigned32 (0..900)
106:
107: HCPerfCurrentCount ::= TEXTUAL-CONVENTION
107: warning -
warning: current type `HCPerfCurrentCount' is not referenced in this module
107: warning -
warning: type `HCPerfCurrentCount' has no format specification
108: STATUS current
109: DESCRIPTION
110: "A gauge associated with a performance measurement in a
111: current 15 minute measurement interval. The value of an
112: object with an HCPerfCurrentCount syntax starts from zero
113: and is increased when associated events occur, until the
114: end of the 15 minute interval. At that time the value of
115: the gauge is stored in the first 15 minute history
116: interval, and the gauge is restarted at zero. In the case
117: where the agent has no valid data available for the
118: current interval, the corresponding object instance is not
119: available and upon a retrieval request a corresponding
120: error message shall be returned to indicate that this
121: instance does not exist.
122:
123: This count represents a non-negative integer, which
124: may increase or decrease, but shall never exceed 2^64-1
125: (18446744073709551615 decimal), nor fall below 0. The
126: value of an object with HCPerfCurrentCount syntax
127: assumes its maximum value whenever the underlying count
128: exceeds 2^64-1. If the underlying count subsequently
129: decreases below 2^64-1 (due, e.g., to a retroactive
130: adjustment as a result of entering or exiting unavailable
131: time), then the object's value also decreases.
132:
133: Note that this TC is not strictly supported in SMIv2,
134: because the 'always increasing' and 'counter wrap'
135: semantics associated with the Counter64 base type are not
136: preserved. It is possible that management applications
137: which rely solely upon the (Counter64) ASN.1 tag to
138: determine object semantics will mistakenly operate upon
139: objects of this type as they would for Counter64 objects.
140:
141: This textual convention represents a limited and short-
142: term solution, and may be deprecated as a long term
143: solution is defined and deployed to replace it."
144: SYNTAX Counter64
145:
146: HCPerfIntervalCount ::= TEXTUAL-CONVENTION
146: warning -
warning: current type `HCPerfIntervalCount' is not referenced in this module
146: warning -
warning: type `HCPerfIntervalCount' has no format specification
147: STATUS current
148: DESCRIPTION
149: "A gauge associated with a performance measurement in
150: a previous 15 minute measurement interval. In the case
151: where the agent has no valid data available for a
152: particular interval, the corresponding object instance is
153: not available and upon a retrieval request a corresponding
154: error message shall be returned to indicate that this
155: instance does not exist.
156:
157: Let X be an object with HCPerfIntervalCount syntax.
158: Let Y be an object with HCPerfCurrentCount syntax.
159: Let Z be an object with HCPerfTotalCount syntax.
160: Then, in a system supporting a history of n intervals with
161: X(1) and X(n) the most and least recent intervals
162: respectively, the following applies at the end of a 15
163: minute interval:
164:
165: - discard the value of X(n)
166: - the value of X(i) becomes that of X(i-1)
167: for n >= i > 1
168: - the value of X(1) becomes that of Y.
169: - the value of Z, if supported, is adjusted.
170:
171: This count represents a non-negative integer, which
172: may increase or decrease, but shall never exceed 2^64-1
173: (18446744073709551615 decimal), nor fall below 0. The
174: value of an object with HCPerfIntervalCount syntax
175: assumes its maximum value whenever the underlying count
176: exceeds 2^64-1. If the underlying count subsequently
177: decreases below 2^64-1 (due, e.g., to a retroactive
178: adjustment as a result of entering or exiting unavailable
179: time), then the value of the object also decreases.
180:
181: Note that this TC is not strictly supported in SMIv2,
182: because the 'always increasing' and 'counter wrap'
183: semantics associated with the Counter64 base type are not
184: preserved. It is possible that management applications
185: which rely solely upon the (Counter64) ASN.1 tag to
186: determine object semantics will mistakenly operate upon
187: objects of this type as they would for Counter64 objects.
188:
189: This textual convention represents a limited and short-
190: term solution, and may be deprecated as a long term
191: solution is defined and deployed to replace it."
192: SYNTAX Counter64
193:
194: HCPerfTotalCount ::= TEXTUAL-CONVENTION
194: warning -
warning: current type `HCPerfTotalCount' is not referenced in this module
194: warning -
warning: type `HCPerfTotalCount' has no format specification
195: STATUS current
196: DESCRIPTION
197: "A gauge representing the aggregate of previous valid 15
198: minute measurement intervals. Intervals for which no
199: valid data was available are not counted.
200:
201: This count represents a non-negative integer, which
202: may increase or decrease, but shall never exceed 2^64-1
203: (18446744073709551615 decimal), nor fall below 0. The
204: value of an object with HCPerfTotalCount syntax
205: assumes its maximum value whenever the underlying count
206: exceeds 2^64-1. If the underlying count subsequently
207: decreases below 2^64-1 (due, e.g., to a retroactive
208: adjustment as a result of entering or exiting unavailable
209: time), then the object's value also decreases.
210:
211: Note that this TC is not strictly supported in SMIv2,
212: because the 'always increasing' and 'counter wrap'
213: semantics associated with the Counter64 base type are not
214: preserved. It is possible that management applications
215: which rely solely upon the (Counter64) ASN.1 tag to
216: determine object semantics will mistakenly operate upon
217: objects of this type as they would for Counter64 objects.
218:
219: This textual convention represents a limited and short-
220: term solution, and may be deprecated as a long term
221: solution is defined and deployed to replace it."
222: SYNTAX Counter64
223: END
224:
225: --
226: -- Copyright (C) The Internet Society (2004). All Rights Reserved.
227: --
228: -- This document and translations of it may be copied and furnished to
229: -- others, and derivative works that comment on or otherwise explain it
230: -- or assist in its implementation may be prepared, copied, published
231: -- and distributed, in whole or in part, without restriction of any
232: -- kind, provided that the above copyright notice and this paragraph are
233: -- included on all such copies and derivative works. However, this
234: -- document itself may not be modified in any way, such as by removing
235: -- the copyright notice or references to the Internet Society or other
236: -- Internet organizations, except as needed for the purpose of
237: -- developing Internet standards in which case the procedures for
238: -- copyrights defined in the Internet Standards process must be
239: -- followed, or as required to translate it into languages other than
240: -- English.
241: --
242: -- The limited permissions granted above are perpetual and will not be
243: -- revoked by the Internet Society or its successors or assignees.
244: --
245: -- This document and the information contained herein is provided on an
246: -- "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
247: -- TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
248: -- BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
249: -- HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
250: -- MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
251: --
252: