smilint output for ./IF-CAP-STACK-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| error | 2 |
| Message Types |
|---|
| Type | Count |
|---|
| bad-identifier-case (error) | 1 |
| object-identifier-not-prefix (error) | 1 |
Messages:
IF-CAP-STACK-MIB
1: -- extracted from draft-ietf-hubmib-efm-cu-mib-08.txt
2: -- at Tue Jul 31 06:08:51 2007
3:
4: IF-CAP-STACK-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY, OBJECT-TYPE, mib-2
8: FROM SNMPv2-SMI -- RFC 2578
9: TruthValue
10: FROM SNMPv2-TC -- RFC 2579
11: MODULE-COMPLIANCE, OBJECT-GROUP
12: FROM SNMPv2-CONF -- RFC 2580
13: ifStackGroup2, ifStackHigherLayer, ifStackLowerLayer
14: FROM IF-MIB -- RFC 2863
15: ifInvStackGroup
16: FROM IF-INVERTED-STACK-MIB -- RFC 2864
17: ;
18:
19: ifCapStackMIB MODULE-IDENTITY
20: LAST-UPDATED "200707290000Z" -- July 29, 2007
21: ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group"
22: CONTACT-INFO
23: "WG charter:
24: http://www.ietf.org/html.charters/hubmib-charter.html
25:
26: Mailing Lists:
27: General Discussion: hubmib@ietf.org
28: To Subscribe: hubmib-request@ietf.org
29: In Body: subscribe your_email_address
30:
31: Chair: Bert Wijnen
32: Postal: Alcatel-Lucent
33: Schagen 33
34: 3461 GL Linschoten
35: Netherlands
36: Tel: +31-348-407-775
37: E-mail: bwijnen@alcatel-lucent.com
38:
39: Editor: Edward Beili
40: Postal: Actelis Networks Inc.
41: 25 Bazel St., P.O.B. 10173
42: Petach-Tikva 10173
43: Israel
44: Tel: +972-3-924-3491
45: E-mail: edward.beili@actelis.com"
46:
47: DESCRIPTION
48: "The objects in this MIB module are used to describe
49: cross-connect capabilities of stacked (layered) interfaces,
50: complementing ifStackTable and ifInvStackTable defined in
51: IF-MIB and IF-INVERTED-STACK-MIB respectively.
52:
53: Copyright (C) The IETF Trust (2007). This version
54: of this MIB module is part of RFC XXXX; see the RFC
55: itself for full legal notices."
56:
57: REVISION "200707290000Z" -- July 29, 2007
58: DESCRIPTION "Initial version, published as RFC XXXX."
59:
60: -- EdNote: Replace XXXX with the actual RFC number &
61: -- remove this note
62:
63: ::= { mib-2 ZZZ }
63: error -
`ZZZ' should start with a lower case letter
63: error -
Object identifier element `ZZZ' name only allowed as first element
64:
65: -- EdNote: Replace ZZZ with a real OID once it is
66: -- allocated & remove this note.
67:
68: -- Sections of the module
69: -- Structured as recommended by RFC 4181, see
70: -- Appendix D: Suggested OID Layout
71:
72: ifCapStackObjects OBJECT IDENTIFIER ::= { ifCapStackMIB 1 }
73:
74: ifCapStackConformance OBJECT IDENTIFIER ::= { ifCapStackMIB 2 }
75:
76: -- Groups in the module
77:
78: --
79: -- ifCapStackTable group
80: --
81:
82: ifCapStackTable OBJECT-TYPE
83: SYNTAX SEQUENCE OF IfCapStackEntry
84: MAX-ACCESS not-accessible
85: STATUS current
86: DESCRIPTION
87: "This table, modeled after ifStackTable from IF-MIB,
88: contains information on the possible 'on-top-of'
89: relationships between the multiple sub-layers of network
90: interfaces (as opposed to actual relationships described in
91: ifStackTable). In particular, it contains information on
92: which sub-layers MAY possibly run 'on top of' which other
93: sub-layers, as determined by cross-connect capability of the
94: device, where each sub-layer corresponds to a conceptual row
95: in the ifTable. For example, when the sub-layer with ifIndex
96: value x can be connected to run on top of the sub-layer with
97: ifIndex value y, then this table contains:
98:
99: ifCapStackStatus.x.y=true
100:
101: The ifCapStackStatus.x.y row does not exist if it is
102: impossible to connect between the sub-layers x and y.
103:
104: Note that for most stacked interfaces (e.g. 2BASE-TL)
105: there's always at least one higher-level interface (e.g. PCS
106: port) for each lower-level interface (e.g. PME) and at
107: least one lower-level interface for each higher-level
108: interface, that is, there is at least a single row with a
109: 'true' status for any such existing value of x or y.
110:
111: This table is read-only as it describes device capabilities."
112: REFERENCE
113: "IF-MIB, ifStackTable"
114: ::= { ifCapStackObjects 1 }
115:
116: ifCapStackEntry OBJECT-TYPE
117: SYNTAX IfCapStackEntry
118: MAX-ACCESS not-accessible
119: STATUS current
120: DESCRIPTION
121: "Information on a particular relationship between two
122: sub-layers, specifying that one sub-layer MAY possibly run
123: on 'top' of the other sub-layer. Each sub-layer corresponds
124: to a conceptual row in the ifTable (interface index for
125: lower- and higher-layer respectively)."
126: INDEX {
127: ifStackHigherLayer,
128: ifStackLowerLayer
129: }
130: ::= { ifCapStackTable 1 }
131:
132: IfCapStackEntry ::= SEQUENCE {
133: ifCapStackStatus TruthValue
134: }
135:
136: ifCapStackStatus OBJECT-TYPE
137: SYNTAX TruthValue
138: MAX-ACCESS read-only
139: STATUS current
140: DESCRIPTION
141: "The status of the 'cross-connect capability' relationship
142: between two sub-layers. The following values can be returned:
143: true(1) - indicates that the sub-layer interface,
144: identified by the ifStackLowerLayer MAY
145: be connected to run 'below' the sub-layer
146: interface, identified by the
147: ifStackHigherLayer index.
148: false(2) - the sub-layer interfaces cannot be
149: connected temporarily due to
150: unavailability of the interface(s), e.g.
151: one of the interfaces is located on an
152: absent pluggable module.
153:
154: Note that lower-layer interface availability per higher-layer,
155: indicated by the value of 'true', can be constrained by
156: other parameters, for example by the aggregation capacity of
157: a higher-layer interface or by the lower-layer interface in
158: question being already connected to another higher-layer
159: interface. In order to ensure that a particular sub-layer can
160: be connected to another sub-layer, all respective objects
161: (e.g. ifCapStackTable, ifStackTable and efmCuPAFCapacity for
162: for EFMCu interfaces) SHALL be inspected.
163:
164: This object is read-only, unlike ifStackStatus, as it
165: describes a cross-connect capability."
166: ::= { ifCapStackEntry 1 }
167:
168: ifInvCapStackTable OBJECT-TYPE
169: SYNTAX SEQUENCE OF IfInvCapStackEntry
170: MAX-ACCESS not-accessible
171: STATUS current
172: DESCRIPTION
173: "A table containing information on the possible relationships
174: between the multiple sub-layers of network interfaces. This
175: table, modeled after ifInvStackTable from
176: IF-INVERTED-STACK-MIB, is an inverse of the ifCapStackTable
177: defined in this MIB module.
178: In particular, this table contains information on which
179: sub-layers MAY run 'underneath' which other sub-layers, where
180: each sub-layer corresponds to a conceptual row in the ifTable.
181: For example, when the sub-layer with ifIndex value x MAY be
182: connected to run underneath the sub-layer with ifIndex value
183: y, then this table contains:
184:
185: ifInvCapStackStatus.x.y=true
186:
187: This table contains exactly the same number of rows as the
188: ifCapStackTable, but the rows appear in a different order.
189:
190: This table is read-only as it describes a cross-connect
191: capability."
192: REFERENCE
193: "IF-INVERTED-STACK-MIB, ifInvStackTable"
194: ::= { ifCapStackObjects 2 }
195:
196: ifInvCapStackEntry OBJECT-TYPE
197: SYNTAX IfInvCapStackEntry
198: MAX-ACCESS not-accessible
199: STATUS current
200: DESCRIPTION
201: "Information on a particular relationship between two sub-
202: layers, specifying that one sub-layer MAY run underneath the
203: other sub-layer. Each sub-layer corresponds to a conceptual
204: row in the ifTable."
205: INDEX { ifStackLowerLayer, ifStackHigherLayer }
206: ::= { ifInvCapStackTable 1 }
207:
208: IfInvCapStackEntry ::= SEQUENCE {
209: ifInvCapStackStatus TruthValue
210: }
211:
212: ifInvCapStackStatus OBJECT-TYPE
213: SYNTAX TruthValue
214: MAX-ACCESS read-only
215: STATUS current
216: DESCRIPTION
217: "The status of the possible 'cross-connect capability'
218: relationship between two sub-layers.
219:
220: An instance of this object exists for each instance of the
221: ifCapStackStatus object, and vice versa. For example, if the
222: variable ifCapStackStatus.H.L exists, then the variable
223: ifInvStackStatus.L.H must also exist, and vice versa. In
224: addition, the two variables always have the same value.
225:
226: The ifInvStackStatus object is read-only, as it describes
227: a cross-connect capability."
228: REFERENCE
229: "ifCapStackStatus"
230: ::= { ifInvCapStackEntry 1 }
231:
232: --
233: -- Conformance Statements
234: --
235:
236: ifCapStackGroups OBJECT IDENTIFIER ::=
237: { ifCapStackConformance 1 }
238:
239: ifCapStackCompliances OBJECT IDENTIFIER ::=
240: { ifCapStackConformance 2 }
241:
242: -- Units of Conformance
243:
244: ifCapStackGroup OBJECT-GROUP
245: OBJECTS {
246: ifCapStackStatus,
247: ifInvCapStackStatus
248: }
249: STATUS current
250: DESCRIPTION
251: "A collection of objects providing information on the
252: cross-connect capability of multi-layer (stacked) network
253: interfaces."
254: ::= { ifCapStackGroups 1 }
255:
256:
257: -- Compliance Statements
258:
259: ifCapStackCompliance MODULE-COMPLIANCE
260: STATUS current
261: DESCRIPTION
262: "The compliance statement for SNMP entities, which provide
263: information on the cross-connect capability of multi-layer
264: (stacked) network interfaces, with flexible cross-connect
265: between the sub-layers."
266:
267:
268: MODULE -- this module
269: MANDATORY-GROUPS {
270: ifCapStackGroup
271:
272: }
273:
274: OBJECT ifCapStackStatus
275: SYNTAX TruthValue { true(1) }
276: DESCRIPTION
277: "Support for the false(2) value is OPTIONAL for
278: implementations supporting pluggable interfaces."
279:
280: OBJECT ifInvCapStackStatus
281: SYNTAX TruthValue { true(1) }
282: DESCRIPTION
283: "Support for the false(2) value is OPTIONAL for
284: implementations supporting pluggable interfaces."
285:
286: MODULE IF-MIB
287: MANDATORY-GROUPS {
288: ifStackGroup2
289: }
290:
291: MODULE IF-INVERTED-STACK-MIB
292: MANDATORY-GROUPS {
293: ifInvStackGroup
294: }
295:
296: ::= { ifCapStackCompliances 1 }
297: END
298:
299: --
300: -- Copyright (C) The IETF Trust (2007).
301: --
302: -- This document is subject to the rights, licenses and restrictions
303: -- contained in BCP 78, and except as set forth therein, the authors
304: -- retain all their rights.
305: --
306: -- This document and the information contained herein are provided on an
307: -- "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
308: -- OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
309: -- THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
310: -- OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
311: -- THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
312: -- WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
313: --
314: --
315: -- Intellectual Property
316: --
317: -- The IETF takes no position regarding the validity or scope of any
318: -- Intellectual Property Rights or other rights that might be claimed to
319: -- pertain to the implementation or use of the technology described in
320: -- this document or the extent to which any license under such rights
321: -- might or might not be available; nor does it represent that it has
322: -- made any independent effort to identify any such rights. Information
323: -- on the procedures with respect to rights in RFC documents can be
324: -- found in BCP 78 and BCP 79.
325: --
326: -- Copies of IPR disclosures made to the IETF Secretariat and any
327: -- assurances of licenses to be made available, or the result of an
328: -- attempt made to obtain a general license or permission for the use of
329: -- such proprietary rights by implementers or users of this
330: -- specification can be obtained from the IETF on-line IPR repository at
331: -- http://www.ietf.org/ipr.
332: --
333: -- The IETF invites any interested party to bring to its attention any
334: -- copyrights, patents or patent applications, or other proprietary
335: -- rights that may cover technology that may be required to implement
336: -- this standard. Please address the information to the IETF at
337: -- ietf-ipr@ietf.org.
338: --
339: --
340: -- Acknowledgment
341: --
342: -- Funding for the RFC Editor function is provided by the IETF
343: -- Administrative Support Activity (IASA).
344: