smilint output for ./SYSLOG-TC-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| error | 2 |
| warning | 2 |
| Message Types |
|---|
| Type | Count |
|---|
| bad-identifier-case (error) | 1 |
| object-identifier-not-prefix (error) | 1 |
| type-unref (warning) | 2 |
Messages:
SYSLOG-TC-MIB
1: -- extracted from draft-ietf-syslog-tc-mib-02.txt
2: -- at Tue Jul 10 06:08:47 2007
3:
4: SYSLOG-TC-MIB DEFINITIONS ::= BEGIN
5:
6: IMPORTS
7: MODULE-IDENTITY, mib-2
8: FROM SNMPv2-SMI -- [RFC2578]
9: TEXTUAL-CONVENTION
10: FROM SNMPv2-TC; -- [RFC2579]
11:
12: syslogTCMIB MODULE-IDENTITY
13: LAST-UPDATED "200706100000Z" -- 10th June, 2007
14: ORGANIZATION "IETF Syslog Working Group"
15: CONTACT-INFO
16: " Glenn Mansfield Keeni
17: Postal: Cyber Solutions Inc.
18: 6-6-3, Minami Yoshinari
19: Aoba-ku, Sendai, Japan 989-3204.
20: Tel: +81-22-303-4012
21: Fax: +81-22-303-4015
22: E-mail: glenn@cysols.com
23:
24: Support Group E-mail: syslog@ietf.org
25: "
26:
27: DESCRIPTION
28: "The MIB module containing textual conventions for syslog
29: messages.
30:
31: Copyright (C) The IETF Trust (2007). This version of
32: this MIB module is part of RFC XXXX; see the RFC itself for
33: full legal notices.
34: "
35: -- RFC Ed.: replace XXXX with the actual RFC number & remove this
36: -- note
37: REVISION "200706100000Z" -- 10th June, 2007
38: DESCRIPTION
39: "The initial version, published as RFC XXXX."
40:
41: -- RFC Ed.: replace XXXX with the actual RFC number & remove this
42: -- note
43:
44:
45: ::= { mib-2 YYYY } -- Will be assigned by IANA
45: error -
`YYYY' should start with a lower case letter
45: error -
Object identifier element `YYYY' name only allowed as first element
46:
47: -- IANA Reg.: Please assign a value for "YYYY" under the
48: -- 'mib-2' subtree and record the assignment in the SMI
49: -- Numbers registry.
50:
51: -- RFC Ed.: When the above assignment has been made, please
52: -- remove the above note
53: -- replace "YYYY" here with the assigned value and
54: -- remove this note.
55:
56:
57:
58: -- -------------------------------------------------------------
59: -- Textual Conventions
60: -- -------------------------------------------------------------
61: -- The Facilities and Severities of syslog messages are
62: -- numerically coded with decimal values.
63: -- Some of the operating system daemons and processes are
64: -- traditionally designated by the Facility values given below.
65: -- Daemons and processes that do not have an explicitly
66: -- assigned Facility may use any of the "local use" Facilities
67: -- or they may use the "user-level" Facility.
68: SyslogFacility ::= TEXTUAL-CONVENTION
68: warning -
warning: current type `SyslogFacility' is not referenced in this module
69: STATUS current
70: DESCRIPTION
71: "This textual convention enumerates the facilities
72: that originate syslog messages.
73: "
74: SYNTAX INTEGER
75: {
76: kernel (0), -- kernel messages
77: user (1), -- user-level messages
78: mail (2), -- mail system messages
79: daemon (3), -- system daemons' messages
80: auth1 (4), -- security/authorization messages
81: syslog (5), -- messages generated internally by
82: -- syslogd
83: lpr (6), -- line printer subsystem messages
84: news (7), -- network news subsystem messages
85: uucp (8), -- UUCP subsystem messages
86: cron1 (9), -- clock daemon messages
87: auth2 (10),-- security/authorization messages
88: ftp (11),-- ftp daemon messages
89: ntp (12),-- NTP subsystem messages
90: logAudit (13),-- log audit messages
91: logAlert (14),-- log alert messages
92: cron2 (15),-- clock daemon messages
93: local0 (16),
94: local1 (17),
95: local2 (18),
96: local3 (19),
97: local4 (20),
98: local5 (21),
99: local6 (22),
100: local7 (23)
101: }
102:
103: SyslogSeverity ::= TEXTUAL-CONVENTION
103: warning -
warning: current type `SyslogSeverity' is not referenced in this module
104: STATUS current
105: DESCRIPTION
106: "This textual convention enumerates the severity levels
107: of syslog messages.
108: "
109: SYNTAX INTEGER
110: {
111: emergency (0), -- system is unusable
112: alert (1), -- action must be taken immediately
113: critical (2), -- critical condition
114: error (3), -- error condition
115: warning (4), -- warning condition
116: notice (5), -- normal but significant condition
117: info (6), -- informational message
118: debug (7) -- debug-level messages
119: }
120:
121:
122: END
123:
124: --
125: -- Copyright (C) The IETF Trust (2007).
126: --
127: -- This document is subject to the rights, licenses and restrictions
128: -- contained in BCP 78, and except as set forth therein, the authors
129: -- retain all their rights.
130: --
131: -- This document and the information contained herein are provided on
132: -- an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
133: -- REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
134: -- IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
135: -- WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
136: -- WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY
137: -- RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
138: -- PARTICULAR PURPOSE.
139: -- Intellectual Property
140: --
141: -- The IETF takes no position regarding the validity or scope of any
142: -- Intellectual Property Rights or other rights that might be claimed
143: -- to pertain to the implementation or use of the technology
144: -- described in this document or the extent to which any license
145: -- under such rights might or might not be available; nor does it
146: -- represent that it has made any independent effort to identify any
147: -- such rights. Information on the procedures with respect to
148: -- rights in RFC documents can be found in BCP 78 and BCP 79.
149: --
150: -- Copies of IPR disclosures made to the IETF Secretariat and any
151: -- assurances of licenses to be made available, or the result of an
152: -- attempt made to obtain a general license or permission for the use
153: -- of such proprietary rights by implementers or users of this
154: -- specification can be obtained from the IETF on-line IPR repository
155: -- at http://www.ietf.org/ipr.
156: --
157: -- The IETF invites any interested party to bring to its attention
158: -- any copyrights, patents or patent applications, or other
159: -- proprietary rights that may cover technology that may be required
160: -- to implement this standard. Please address the information to the
161: -- IETF at ietf-ipr@ietf.org.
162: --
163: -- Acknowledgment
164: --
165: -- Funding for the RFC Editor function is provided by the IETF
166: -- Administrative Support Activity (IASA).
167: -- APPENDIX
168: --
169: --
170: -- This section documents the development of the draft. It will be
171: -- deleted when the draft becomes an RFC.
172: --
173: -- Revision History:
174: -- Changes from draft-ietf-syslog-tc-mib-01.txt
175: -- to draft-ietf-syslog-tc-mib-02.txt
176: