smilint output for ./IANA-ITU-ALARM-TC-MIB
| Message Severities |
|---|
| Severity | Count |
|---|
| warning | 2 |
| Message Types |
|---|
| Type | Count |
|---|
| type-unref (warning) | 2 |
Messages:
IANA-ITU-ALARM-TC-MIB
1: -- extracted from rfc3877.txt
2: -- at Sat Sep 18 06:23:14 2004
39:
40: IANAItuProbableCause ::= TEXTUAL-CONVENTION
40: warning -
warning: current type `IANAItuProbableCause' is not referenced in this module
41: STATUS current
42: DESCRIPTION
43: "ITU-T probable cause values. Duplicate values defined in
44: X.733 are appended with X733 to ensure syntactic uniqueness.
45: Probable cause value 0 is reserved for special purposes.
46:
47: The Internet Assigned Number Authority (IANA) is responsible
48: for the assignment of the enumerations in this TC.
49: IANAItuProbableCause value of 0 is reserved for special
50: purposes and MUST NOT be assigned.
51:
52: Values of IANAItuProbableCause in the range 1 to 1023 are
53: reserved for causes that correspond to ITU-T probable cause.
54:
55: All other requests for new causes will be handled on a
56: first-come, first served basis and will be assigned
57: enumeration values starting with 1025.
58:
59: Request should come in the form of well-formed
60: SMI [RFC2578] for enumeration names that are unique and
61: sufficiently descriptive.
62:
63: While some effort will be taken to ensure that new probable
64: causes do not conceptually duplicate existing probable
65: causes it is acknowledged that the existence of conceptual
66: duplicates in the starting probable cause list is an known
67: industry reality.
68:
69: To aid IANA in the administration of probable cause names
70: and values, the OPS Area Director will appoint one or more
71: experts to help review requests.
72:
73: See http://www.iana.org"
74: REFERENCE
75: "ITU Recommendation M.3100, 'Generic Network Information
76: Model', 1995
77: ITU Recommendation X.733, 'Information Technology - Open
78: Systems Interconnection - System Management: Alarm
79: Reporting Function', 1992
80: ITU Recommendation X.736, 'Information Technology - Open
81: Systems Interconnection - System Management: Security
82: Alarm Reporting Function', 1992"
83:
84: SYNTAX INTEGER
85: {
86: -- The following probable causes were defined in M.3100
87: aIS (1),
88: callSetUpFailure (2),
89: degradedSignal (3),
90: farEndReceiverFailure (4),
91: framingError (5),
92: lossOfFrame (6),
93: lossOfPointer (7),
94: lossOfSignal (8),
95: payloadTypeMismatch (9),
96: transmissionError (10),
97: remoteAlarmInterface (11),
98: excessiveBER (12),
99: pathTraceMismatch (13),
100: unavailable (14),
101: signalLabelMismatch (15),
102: lossOfMultiFrame (16),
103: receiveFailure (17),
104: transmitFailure (18),
105: modulationFailure (19),
106: demodulationFailure (20),
107: broadcastChannelFailure (21),
108: connectionEstablishmentError (22),
109: invalidMessageReceived (23),
110: localNodeTransmissionError (24),
111: remoteNodeTransmissionError (25),
112: routingFailure (26),
113:
114: --Values 27-50 are reserved for communications alarm related
115: --probable causes
116: -- The following are used with equipment alarm.
117:
118: backplaneFailure (51),
119: dataSetProblem (52),
120: equipmentIdentifierDuplication (53),
121: externalIFDeviceProblem (54),
122: lineCardProblem (55),
123: multiplexerProblem (56),
124: nEIdentifierDuplication (57),
125: powerProblem (58),
126: processorProblem (59),
127: protectionPathFailure (60),
128: receiverFailure (61),
129: replaceableUnitMissing (62),
130: replaceableUnitTypeMismatch (63),
131: synchronizationSourceMismatch (64),
132: terminalProblem (65),
133: timingProblem (66),
134: transmitterFailure (67),
135: trunkCardProblem (68),
136: replaceableUnitProblem (69),
137: realTimeClockFailure (70),
138: --An equipment alarm to be issued if the system detects that the
139: --real time clock has failed
140: antennaFailure (71),
141: batteryChargingFailure (72),
142: diskFailure (73),
143: frequencyHoppingFailure (74),
144: iODeviceError (75),
145: lossOfSynchronisation (76),
146: lossOfRedundancy (77),
147: powerSupplyFailure (78),
148: signalQualityEvaluationFailure (79),
149: tranceiverFailure (80),
150: protectionMechanismFailure (81),
151: protectingResourceFailure (82),
152: -- Values 83-100 are reserved for equipment alarm related probable
153: -- causes
154: -- The following are used with environmental alarm.
155: airCompressorFailure (101),
156: airConditioningFailure (102),
157: airDryerFailure (103),
158: batteryDischarging (104),
159: batteryFailure (105),
160: commercialPowerFailure (106),
161: coolingFanFailure (107),
162: engineFailure (108),
163: fireDetectorFailure (109),
164: fuseFailure (110),
165: generatorFailure (111),
166: lowBatteryThreshold (112),
167: pumpFailure (113),
168: rectifierFailure (114),
169: rectifierHighVoltage (115),
170: rectifierLowFVoltage (116),
171: ventilationsSystemFailure (117),
172: enclosureDoorOpen (118),
173: explosiveGas (119),
174: fire (120),
175: flood (121),
176: highHumidity (122),
177: highTemperature (123),
178: highWind (124),
179: iceBuildUp (125),
180: intrusionDetection (126),
181: lowFuel (127),
182: lowHumidity (128),
183: lowCablePressure (129),
184: lowTemperatue (130),
185: lowWater (131),
186: smoke (132),
187: toxicGas (133),
188: coolingSystemFailure (134),
189: externalEquipmentFailure (135),
190: externalPointFailure (136),
191: -- Values 137-150 are reserved for environmental alarm related
192: -- probable causes
193: -- The following are used with Processing error alarm.
194: storageCapacityProblem (151),
195: memoryMismatch (152),
196: corruptData (153),
197: outOfCPUCycles (154),
198: sfwrEnvironmentProblem (155),
199: sfwrDownloadFailure (156),
200: lossOfRealTimel (157),
201: --A processing error alarm to be issued after the system has
202: --reinitialised. This will indicate
203: --to the management systems that the view they have of the managed
204: --system may no longer
205: --be valid. Usage example: The managed
206: --system issues this alarm after a reinitialization with severity
207: --warning to inform the
208: --management system about the event. No clearing notification will
209: --be sent.
210: applicationSubsystemFailure (158),
211: configurationOrCustomisationError (159),
212: databaseInconsistency (160),
213: fileError (161),
214: outOfMemory (162),
215: softwareError (163),
216: timeoutExpired (164),
217: underlayingResourceUnavailable (165),
218: versionMismatch (166),
219: --Values 168-200 are reserved for processing error alarm related
220: -- probable causes.
221: bandwidthReduced (201),
222: congestion (202),
223: excessiveErrorRate (203),
224: excessiveResponseTime (204),
225: excessiveRetransmissionRate (205),
226: reducedLoggingCapability (206),
227: systemResourcesOverload (207 ),
228: -- The following were defined X.733
229: adapterError (500),
230: applicationSubsystemFailture (501),
231: bandwidthReducedX733 (502),
232: callEstablishmentError (503),
233: communicationsProtocolError (504),
234: communicationsSubsystemFailure (505),
235: configurationOrCustomizationError (506),
236: congestionX733 (507),
237: coruptData (508),
238: cpuCyclesLimitExceeded (509),
239: dataSetOrModemError (510),
240: degradedSignalX733 (511),
241: dteDceInterfaceError (512),
242: enclosureDoorOpenX733 (513),
243: equipmentMalfunction (514),
244: excessiveVibration (515),
245: fileErrorX733 (516),
246: fireDetected (517),
247: framingErrorX733 (518),
248: heatingVentCoolingSystemProblem (519),
249: humidityUnacceptable (520),
250: inputOutputDeviceError (521),
251: inputDeviceError (522),
252: lanError (523),
253: leakDetected (524),
254: localNodeTransmissionErrorX733 (525),
255: lossOfFrameX733 (526),
256: lossOfSignalX733 (527),
257: materialSupplyExhausted (528),
258: multiplexerProblemX733 (529),
259: outOfMemoryX733 (530),
260: ouputDeviceError (531),
261: performanceDegraded (532),
262: powerProblems (533),
263: pressureUnacceptable (534),
264: processorProblems (535),
265: pumpFailureX733 (536),
266: queueSizeExceeded (537),
267: receiveFailureX733 (538),
268: receiverFailureX733 (539),
269: remoteNodeTransmissionErrorX733 (540),
270: resourceAtOrNearingCapacity (541),
271: responseTimeExecessive (542),
272: retransmissionRateExcessive (543),
273: softwareErrorX733 (544),
274: softwareProgramAbnormallyTerminated (545),
275: softwareProgramError (546),
276: storageCapacityProblemX733 (547),
277: temperatureUnacceptable (548),
278: thresholdCrossed (549),
279: timingProblemX733 (550),
280: toxicLeakDetected (551),
281: transmitFailureX733 (552),
282: transmiterFailure (553),
283: underlyingResourceUnavailable (554),
284: versionMismatchX733 (555),
285: -- The following are defined in X.736
286: authenticationFailure (600),
287: breachOfConfidentiality (601),
288: cableTamper (602),
289: delayedInformation (603),
290: denialOfService (604),
291: duplicateInformation (605),
292: informationMissing (606),
293: informationModificationDetected (607),
294: informationOutOfSequence (608),
295: keyExpired (609),
296: nonRepudiationFailure (610),
297: outOfHoursActivity (611),
298: outOfService (612),
299: proceduralError (613),
300: unauthorizedAccessAttempt (614),
301: unexpectedInformation (615),
302:
303: other (1024)
304: }
305:
306: IANAItuEventType ::= TEXTUAL-CONVENTION
306: warning -
warning: current type `IANAItuEventType' is not referenced in this module
307: STATUS current
308: DESCRIPTION
309: "The ITU event Type values.
310:
311: The Internet Assigned Number Authority (IANA) is
312: responsible for the assignment of the enumerations
313: in this TC.
314:
315: Request should come in the form of well-formed
316: SMI [RFC2578] for enumeration names that are unique
317: and sufficiently descriptive.
318:
319: See http://www.iana.org "
320: REFERENCE
321: "ITU Recommendation X.736, 'Information Technology - Open
322: Systems Interconnection - System Management: Security
323: Alarm Reporting Function', 1992"
324: SYNTAX INTEGER
325: {
326: other (1),
327: communicationsAlarm (2),
328: qualityOfServiceAlarm (3),
329: processingErrorAlarm (4),
330: equipmentAlarm (5),
331: environmentalAlarm (6),
332: integrityViolation (7),
333: operationalViolation (8),
334: physicalViolation (9),
335: securityServiceOrMechanismViolation (10),
336: timeDomainViolation (11)
337: }
338:
339: END
340:
341: --
342: -- Copyright (C) The Internet Society (2004). This document is subject
343: -- to the rights, licenses and restrictions contained in BCP 78, and
344: -- except as set forth therein, the authors retain all their rights.
345: --
346: -- This document and the information contained herein are provided on an
347: -- "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
348: -- OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
349: -- ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
350: -- INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
351: -- INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
352: -- WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
353: --
354: -- Intellectual Property
355: --
356: -- The IETF takes no position regarding the validity or scope of any
357: -- Intellectual Property Rights or other rights that might be claimed to
358: -- pertain to the implementation or use of the technology described in
359: -- this document or the extent to which any license under such rights
360: -- might or might not be available; nor does it represent that it has
361: -- made any independent effort to identify any such rights. Information
362: -- on the procedures with respect to rights in RFC documents can be
363: -- found in BCP 78 and BCP 79.
364: --
365: -- Copies of IPR disclosures made to the IETF Secretariat and any
366: -- assurances of licenses to be made available, or the result of an
367: -- attempt made to obtain a general license or permission for the use of
368: -- such proprietary rights by implementers or users of this
369: -- specification can be obtained from the IETF on-line IPR repository at
370: -- http://www.ietf.org/ipr.
371: --
372: -- The IETF invites any interested party to bring to its attention any
373: -- copyrights, patents or patent applications, or other proprietary
374: -- rights that may cover technology that may be required to implement
375: -- this standard. Please address the information to the IETF at ietf-
376: -- ipr@ietf.org.
377: --
378: