smilint output for ./SNMP-SSH-TM-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| error | 2 |
| warning | 1 |
| Message Types |
|---|
| Type | Count |
|---|
| object-identifier-not-prefix (error) | 2 |
| type-unref (warning) | 1 |
Messages:
SNMP-SSH-TM-MIB
1: -- extracted from draft-ietf-isms-secshell-08.txt
2: -- at Tue Jul 10 06:08:47 2007
3:
4: SNMP-SSH-TM-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY, OBJECT-TYPE,
8:
9:
10: OBJECT-IDENTITY, snmpModules, snmpDomains,
11: Gauge32, Counter32, Unsigned32
12: FROM SNMPv2-SMI
13: TEXTUAL-CONVENTION
14: FROM SNMPv2-TC
15: MODULE-COMPLIANCE, OBJECT-GROUP
16: FROM SNMPv2-CONF
17: ;
18:
19: sshtmMIB MODULE-IDENTITY
20: LAST-UPDATED "200707050000Z"
21: ORGANIZATION "ISMS Working Group"
22: CONTACT-INFO "WG-EMail: isms@lists.ietf.org
23: Subscribe: isms-request@lists.ietf.org
24:
25: Chairs:
26: Juergen Quittek
27: NEC Europe Ltd.
28: Network Laboratories
29: Kurfuersten-Anlage 36
30: 69115 Heidelberg
31: Germany
32: +49 6221 90511-15
33: quittek@netlab.nec.de
34:
35: Juergen Schoenwaelder
36: Jacobs University Bremen
37: Campus Ring 1
38: 28725 Bremen
39: Germany
40: +49 421 200-3587
41: j.schoenwaelder@iu-bremen.de
42:
43: Co-editors:
44: David Harrington
45: Huawei Technologies USA
46: 1700 Alma Drive
47: Plano Texas 75075
48: USA
49: +1 603-436-8634
50: ietfdbh@comcast.net
51:
52: Joseph Salowey
53: Cisco Systems
54:
55:
56: 2901 3rd Ave
57: Seattle, WA 98121
58: USA
59: jsalowey@cisco.com
60: "
61: DESCRIPTION "The Secure Shell Transport Model MIB
62:
63: Copyright (C) The Internet Society (2007). This
64: version of this MIB module is part of RFC XXXX;
65: see the RFC itself for full legal notices.
66: -- NOTE to RFC editor: replace XXXX with actual RFC number
67: -- for this document and remove this note
68: "
69:
70: REVISION "200707050000Z"
71: DESCRIPTION "The initial version, published in RFC XXXX.
72: -- NOTE to RFC editor: replace XXXX with actual RFC number
73: -- for this document and remove this note
74: "
75:
76: ::= { snmpModules xxxx }
76: error -
Object identifier element `xxxx' name only allowed as first element
77: -- RFC Ed.: replace xxxx with IANA-assigned number and
78: -- remove this note
79: -- ---------------------------------------------------------- --
80: -- subtrees in the SNMP-SSH-TM-MIB
81: -- ---------------------------------------------------------- --
82:
83: sshtmNotifications OBJECT IDENTIFIER ::= { sshtmMIB 0 }
84: sshtmObjects OBJECT IDENTIFIER ::= { sshtmMIB 1 }
85: sshtmConformance OBJECT IDENTIFIER ::= { sshtmMIB 2 }
86:
87: -- -------------------------------------------------------------
88: -- Objects
89: -- -------------------------------------------------------------
90:
91: snmpSSHDomain OBJECT-IDENTITY
92: STATUS current
93: DESCRIPTION
94: "The SNMP over SSH transport domain. The corresponding transport
95: address is of type SnmpSSHAddress.
96:
97: When an SNMP entity uses the snmpSSHDomain transport
98: model, it must be capable of accepting messages up to
99: and including 8192 octets in size. Implementation of
100: larger values is encouraged whenever possible."
101: ::= { snmpDomains yy }
101: error -
Object identifier element `yy' name only allowed as first element
102:
103:
104: -- RFC Ed.: replace yy with IANA-assigned number and
105: -- remove this note
106:
107: SnmpSSHAddress ::= TEXTUAL-CONVENTION
107: warning -
warning: current type `SnmpSSHAddress' is not referenced in this module
108: DISPLAY-HINT "1a"
109: STATUS current
110: DESCRIPTION
111: "Represents either a hostname encoded in ASCII
112: using the IDNA protocol, as specified in RFC3490, followed by
113: a colon ':' (ASCII character 0x3A) and a decimal port number
114: in ASCII, or an IP address followed by a colon ':'
115: (ASCII character 0x3A) and a decimal port number in ASCII.
116: The name SHOULD be fully qualified whenever possible.
117:
118: Values of this textual convention are not directly useable
119: as transport-layer addressing information, and require
120: runtime resolution. As such, applications that write them
121: must be prepared for handling errors if such values are
122: not supported, or cannot be resolved (if resolution occurs
123: at the time of the management operation).
124:
125: The DESCRIPTION clause of TransportAddress objects that may
126: have snmpSSHAddress values must fully describe how (and
127: when) such names are to be resolved to IP addresses and vice
128: versa.
129:
130: This textual convention SHOULD NOT be used directly in
131: object definitions since it restricts addresses to a
132: specific format. However, if it is used, it MAY be used
133: either on its own or in conjunction with
134: TransportAddressType or TransportDomain as a pair.
135:
136: When this textual convention is used as a syntax of an
137: index object, there may be issues with the limit of 128
138: sub-identifiers specified in SMIv2, STD 58. In this case,
139: the OBJECT-TYPE declaration MUST include a 'SIZE' clause
140: to limit the number of potential instance sub-identifiers."
141: SYNTAX OCTET STRING (SIZE (1..255))
142:
143: -- The sshtmSession Group
144:
145: sshtmSession OBJECT IDENTIFIER ::= { sshtmObjects 1 }
146:
147: sshtmSessionCurrent OBJECT-TYPE
148: SYNTAX Gauge32
149:
150:
151: MAX-ACCESS read-only
152: STATUS current
153: DESCRIPTION "The current number of open sessions.
154: "
155: ::= { sshtmSession 1 }
156:
157: sshtmSessionMaxSupported OBJECT-TYPE
158: SYNTAX Unsigned32
159: MAX-ACCESS read-only
160: STATUS current
161: DESCRIPTION "The maximum number of open sessions supported.
162: The value zero indicates the maximum is dynamic.
163: "
164: ::= { sshtmSession 2 }
165:
166: sshtmSessionOpenErrors OBJECT-TYPE
167: SYNTAX Counter32
168: MAX-ACCESS read-only
169: STATUS current
170: DESCRIPTION "The number of times an openSession() request
171: failed to open a Session.
172: "
173: ::= { sshtmSession 3 }
174:
175: sshtmSessionUserAuthFailures OBJECT-TYPE
176: SYNTAX Counter32
177: MAX-ACCESS read-only
178: STATUS current
179: DESCRIPTION "The number of times an openSession() request
180: failed due to user authentication failures.
181: "
182: ::= { sshtmSession 4 }
183:
184: sshtmSessionChannelOpenFailures OBJECT-TYPE
185: SYNTAX Counter32
186: MAX-ACCESS read-only
187: STATUS current
188: DESCRIPTION "The number of times an openSession() request
189: failed due to channel open failures.
190: "
191: ::= { sshtmSession 5 }
192:
193: sshtmSessionNoAvailableSessions OBJECT-TYPE
194: SYNTAX Counter32
195: MAX-ACCESS read-only
196: STATUS current
197: DESCRIPTION "The number of times a Response message
198: was dropped because the corresponding
199: session was no longer available.
200: "
201: ::= { sshtmSession 6 }
202:
203: -- ************************************************
204: -- sshtmMIB - Conformance Information
205: -- ************************************************
206:
207: sshtmGroups OBJECT IDENTIFIER ::= { sshtmConformance 1 }
208:
209: sshtmCompliances OBJECT IDENTIFIER ::= { sshtmConformance 2 }
210:
211: -- ************************************************
212: -- Units of conformance
213: -- ************************************************
214: sshtmGroup OBJECT-GROUP
215: OBJECTS {
216: sshtmSessionCurrent,
217: sshtmSessionMaxSupported,
218: sshtmSessionOpenErrors,
219: sshtmSessionUserAuthFailures,
220: sshtmSessionChannelOpenFailures,
221: sshtmSessionNoAvailableSessions
222: }
223: STATUS current
224: DESCRIPTION "A collection of objects for maintaining
225: information of an SNMP engine which implements the
226: SNMP Secure Shell Transport Model.
227: "
228:
229:
230: ::= { sshtmGroups 2 }
231:
232: -- ************************************************
233: -- Compliance statements
234: -- ************************************************
235:
236: sshtmCompliance MODULE-COMPLIANCE
237: STATUS current
238: DESCRIPTION
239: "The compliance statement for SNMP engines that support the
240: SNMP-SSH-TM-MIB"
241: MODULE
242: MANDATORY-GROUPS { sshtmGroup }
243: ::= { sshtmCompliances 1 }
244:
245: END
246:
247: --
248: -- Copyright (C) The IETF Trust (2007).
249: --
250: -- This document is subject to the rights, licenses and restrictions
251: -- contained in BCP 78, and except as set forth therein, the authors
252: -- retain all their rights.
253: --
254: -- This document and the information contained herein are provided on an
255: -- "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
256: -- OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
257: -- THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
258: -- OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
259: -- THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
260: -- WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
261: --
262: -- Intellectual Property
263: --
264: -- The IETF takes no position regarding the validity or scope of any
265: -- Intellectual Property Rights or other rights that might be claimed to
266: -- pertain to the implementation or use of the technology described in
267: -- this document or the extent to which any license under such rights
268: -- might or might not be available; nor does it represent that it has
269: -- made any independent effort to identify any such rights. Information
270: -- on the procedures with respect to rights in RFC documents can be
271: -- found in BCP 78 and BCP 79.
272: --
273: -- Copies of IPR disclosures made to the IETF Secretariat and any
274: -- assurances of licenses to be made available, or the result of an
275: -- attempt made to obtain a general license or permission for the use of
276: -- such proprietary rights by implementers or users of this
277: -- specification can be obtained from the IETF on-line IPR repository at
278: -- http://www.ietf.org/ipr.
279: --
280: -- The IETF invites any interested party to bring to its attention any
281: -- copyrights, patents or patent applications, or other proprietary
282: -- rights that may cover technology that may be required to implement
283: -- this standard. Please address the information to the IETF at
284: -- ietf-ipr@ietf.org.
285: --
286: