smilint output for ./SNMP-ROWOP-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| error | 2 |
| warning | 5 |
| Message Types |
|---|
| Type | Count |
|---|
| bad-identifier-case (error) | 1 |
| import-unused (warning) | 4 |
| object-identifier-not-prefix (error) | 1 |
| type-unref (warning) | 1 |
Messages:
SNMP-ROWOP-MIB
1: -- extracted from draft-ietf-eos-snmp-rowops-01.txt
2: -- at Sat Jun 16 06:04:55 2001
3:
4: SNMP-ROWOP-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY, OBJECT-TYPE,
7: warning -
warning: identifier `OBJECT-TYPE' imported from module `SNMPv2-SMI' is never used
8: OBJECT-IDENTITY,
8: warning -
warning: identifier `OBJECT-IDENTITY' imported from module `SNMPv2-SMI' is never used
9: snmpModules FROM SNMPv2-SMI
10: TEXTUAL-CONVENTION FROM SNMPv2-TC
11: MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
11: warning -
warning: identifier `MODULE-COMPLIANCE' imported from module `SNMPv2-CONF' is never used
11: warning -
warning: identifier `OBJECT-GROUP' imported from module `SNMPv2-CONF' is never used
12:
13: snmpRowopMIB MODULE-IDENTITY
14: LAST-UPDATED "200106151500Z"
15: ORGANIZATION "EOS Working Group"
16: CONTACT-INFO "WG-EMail: eos@ops.ietf.org
17: Subscribe: eos-request@ops.ietf.org
18:
19: Co-Chair: Dale Francisco
20: EMail: dfrancisco@acm.org
21: phone: +1 408-324-1389
22:
23: Co-Chair: Glenn Waters
24: Nortel Networks
25: EMail: gww@nortelnetworks.com
26:
27: Editor: Lauren Heintz
28: Cisco Systems, Inc.
29: postal: 130 Baytech Drive
30: San Jose, CA 95134
31: USA
32: EMail: lheintz@cisco.com
33: phone: +1 408-853-6568
34: "
35: DESCRIPTION "The SNMP Row Operations MIB"
36: REVISION "200106151500Z"
37: DESCRIPTION "The initial version, published in
38: draft-ietf-eos-snmp-rowops-01.txt.
39: "
40: ::= { snmpModules TBD }
40: error -
`TBD' should start with a lower case letter
40: error -
Object identifier element `TBD' name only allowed as first element
41:
42: -- Textual Conventions
43:
44: RowState ::= TEXTUAL-CONVENTION
44: warning -
warning: current type `RowState' is not referenced in this module
45: STATUS current
46: DESCRIPTION "
47: This textual-convention provides a means
48: to represent the state of a conceptual row;
49: it does not provide a means to manage creation
50: and/or destruction of conceptual rows.
51:
52: In any row which includes a definition of RowState
53: that is also mandatory, that row MUST contain
54: an instantiation of a RowState object if any other
55: object in the same row is instantiated.
56:
57: A status column of this type has three defined
58: values:
59:
60: - `active', which indicates that the
61: conceptual row is in use by the managed
62: device and is considered fully operational
63: from a management perspective;
64:
65: - `notInService', which indicates that the
66: conceptual row is available for use by
67: the managed device but is NOT considered
68: fully operational from a management
69: perspective; a row in this state contains
70: all information necessary for a transition to
71: the active state;
72: - `notReady', which indicates that the
73: conceptual row is not available for use
74: by the managed device, perhaps because the
75: row is missing information or the row has
76: been explicitly set to this state;
77:
78: Any of the three states may be specified in a
79: management protocol set operation. At any time,
80: the value of an existing RowState object may be
81: modified or changed to any other state unless
82: the current value is notReady and the row (after
83: completion of a management set operation) would
84: not be consistent with an active state (i.e.
85: information is missing or inconsistent and as a
86: result the row could not assume an active state
87: until further management set operations were
88: performed). In this case, the value MUST remain
89: at notReady and an inconsistentValue error is
90: returned.
91:
92: A RowState object whose value is notReady MUST
93: implicitly promote itself from notReady to
94: notInService if any management protocol set
95: operation not referencing the status column
96: explicitly changes the value of any other object
97: in the same row AND the row afterward is now
98: consistent with the active state (i.e all
99: information needed to make the row active is
100: available).
101:
102: When a row does not exist, and a management
103: protocol set operation causes any object in the row
104: to be created, the status object will also be
105: instantiated and its initial value will be determined
106: by the first of the following rules that are satisfied:
107:
108: 1. if the set operation includes an initial value,
109: the RowState object will take on the highest
110: value (i.e. active is highest) consistent with
111: the state definitions, but no higher than the
112: provided value. For example, if a set operation
113: contains a varbind where RowState=notInService
114: (or active), the initial value will be notReady
115: if the row is in an inconsistent state after the
116: operation is complete; otherwise, it will be
117: notInService (or active).
118:
119: 2. if the set operation does not include an initial
120: value, but the RowState definition does include
121: a supported DEFVAL, the initial value will be the
122: highest value consistent with the state definitions
123: but no higher than the value specified in the
124: DEFVAL, unless the DEFVAL specifies a value of
125: notReady, which in this case, the DEFVAL is ignored
126: (i.e. case 3 below instead applies).
127:
128: 3. otherwise, the set operation does not include an
129: initial value, and the RowState definition does
130: not include a DEFVAL, and the initial value will
131: be set to the highest value consistent with the
132: state definitions. Thus, the initial state will
133: be active if the new row is consistent with that
134: state, or it will be notReady otherwise.
135:
136: No constraint is imposed on whether other objects
137: in the same row can be modified, regardless of the
138: value of the associated RowState object. If such
139: constraints are desired, they MUST be explicitly
140: stated in the DESCRIPTION clause of the status column.
141: In the absence of such statements, the managed device
142: MUST allow any object in any row to be modified at
143: any time, notwithstanding the possibility that other
144: MIB objects MAY also impose similar constraints.
145: An inconsistentValue error is returned when an invalid
146: attempt is made to alter a row whose state precludes
147: such an operation.
148:
149: RowState description clauses, in addition to
150: the DESCRIPTION clauses of associated column
151: objects, SHOULD together describe the general
152: conditions under which a row can be made active.
153: In the absence of such statements, any row SHOULD
154: generally be capable of being made active at any
155: time.
156:
157: The agent must detect conceptual rows that
158: have been in the notReady state for an abnormally
159: long period of time and remove them. It is the
160: responsibility of the DESCRIPTION clause of the
161: status column to indicate what an abnormally long
162: period of time would be. This period of time should
163: be long enough to allow for human response time
164: (including `think time') between the creation of the
165: conceptual row and the setting of the status to `active'.
166: In the absense of such information in the DESCRIPTION
167: clause, it is suggested that this period be approximately
168: 5 minutes in length. This removal action applies not only
169: to newly-created rows, but also to previously active rows
170: which are set to, and left in, the notReady state for a
171: prolonged period exceeding that which is considered normal
172: for such a conceptual row."
173: SYNTAX INTEGER {
174: active(1),
175: notInService(2),
176: notReady(3)
177: }
178:
179: END
180:
181: --
182: -- Copyright (C) The Internet Society (2001). All Rights Reserved.
183: --
184: -- This document and translations of it may be copied and furnished to
185: -- others, and derivative works that comment on or otherwise explain it
186: -- or assist in its implementation may be prepared, copied, published
187: -- and distributed, in whole or in part, without restriction of any
188: -- kind, provided that the above copyright notice and this paragraph are
189: -- included on all such copies and derivative works. However, this
190: -- document itself may not be modified in any way, such as by removing
191: -- the copyright notice or references to the Internet Society or other
192: -- Internet organizations, except as needed for the purpose of
193: -- developing Internet standards in which case the procedures for
194: -- copyrights defined in the Internet Standards process must be
195: -- followed, or as required to translate it into languages other than
196: -- English.
197: --
198: -- The limited permissions granted above are perpetual and will not be
199: -- revoked by the Internet Society or its successors or assigns.
200: --
201: -- This document and the information contained herein is provided on an
202: -- "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
203: -- TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
204: -- BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
205: -- HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
206: -- MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
207: --
208: