1 IANA-ITU-ALARM-TC-MIB DEFINITIONS ::= BEGIN
5 FROM SNMPv2-SMI -- [RFC2578]
7 FROM SNMPv2-TC; -- [RFC2579]
11 ianaItuAlarmNumbers MODULE-IDENTITY
12 LAST-UPDATED "200409090000Z" -- September 09, 2004
15 "Postal: Internet Assigned Numbers Authority
16 Internet Corporation for Assigned Names
18 4676 Admiralty Way, Suite 330
19 Marina del Rey, CA 90292-6601
23 E-Mail: iana@iana.org"
25 "The MIB module defines the ITU Alarm
26 textual convention for objects expected to require
29 Copyright (C) The Internet Society (2004). The
30 initial version of this MIB module was published
31 in RFC 3877. For full legal notices see the RFC
32 itself. Supplementary information may be available on:
33 http://www.ietf.org/copyrights/ianamib.html"
34 REVISION "200409090000Z" -- September 09, 2004
36 "Initial version, published as RFC 3877."
39 IANAItuProbableCause ::= TEXTUAL-CONVENTION
42 "ITU-T probable cause values. Duplicate values defined in
43 X.733 are appended with X733 to ensure syntactic uniqueness.
44 Probable cause value 0 is reserved for special purposes.
46 The Internet Assigned Number Authority (IANA) is responsible
47 for the assignment of the enumerations in this TC.
48 IANAItuProbableCause value of 0 is reserved for special
49 purposes and MUST NOT be assigned.
51 Values of IANAItuProbableCause in the range 1 to 1023 are
52 reserved for causes that correspond to ITU-T probable cause.
54 All other requests for new causes will be handled on a
55 first-come, first served basis and will be assigned
56 enumeration values starting with 1025.
58 Request should come in the form of well-formed
61 SMI [RFC2578] for enumeration names that are unique and
62 sufficiently descriptive.
64 While some effort will be taken to ensure that new probable
65 causes do not conceptually duplicate existing probable
66 causes it is acknowledged that the existence of conceptual
67 duplicates in the starting probable cause list is an known
70 To aid IANA in the administration of probable cause names
71 and values, the OPS Area Director will appoint one or more
72 experts to help review requests.
74 See http://www.iana.org"
76 "ITU Recommendation M.3100, 'Generic Network Information
78 ITU Recommendation X.733, 'Information Technology - Open
79 Systems Interconnection - System Management: Alarm
80 Reporting Function', 1992
81 ITU Recommendation X.736, 'Information Technology - Open
82 Systems Interconnection - System Management: Security
83 Alarm Reporting Function', 1992"
87 -- The following probable causes were defined in M.3100
91 farEndReceiverFailure (4),
96 payloadTypeMismatch (9),
97 transmissionError (10),
98 remoteAlarmInterface (11),
100 pathTraceMismatch (13),
102 signalLabelMismatch (15),
103 lossOfMultiFrame (16),
105 transmitFailure (18),
106 modulationFailure (19),
107 demodulationFailure (20),
108 broadcastChannelFailure (21),
111 connectionEstablishmentError (22),
112 invalidMessageReceived (23),
113 localNodeTransmissionError (24),
114 remoteNodeTransmissionError (25),
117 --Values 27-50 are reserved for communications alarm related
119 -- The following are used with equipment alarm.
121 backplaneFailure (51),
123 equipmentIdentifierDuplication (53),
124 externalIFDeviceProblem (54),
125 lineCardProblem (55),
126 multiplexerProblem (56),
127 nEIdentifierDuplication (57),
129 processorProblem (59),
130 protectionPathFailure (60),
131 receiverFailure (61),
132 replaceableUnitMissing (62),
133 replaceableUnitTypeMismatch (63),
134 synchronizationSourceMismatch (64),
135 terminalProblem (65),
137 transmitterFailure (67),
138 trunkCardProblem (68),
139 replaceableUnitProblem (69),
140 realTimeClockFailure (70),
141 --An equipment alarm to be issued if the system detects that the
142 --real time clock has failed
144 batteryChargingFailure (72),
146 frequencyHoppingFailure (74),
148 lossOfSynchronisation (76),
149 lossOfRedundancy (77),
150 powerSupplyFailure (78),
151 signalQualityEvaluationFailure (79),
152 tranceiverFailure (80),
153 protectionMechanismFailure (81),
154 protectingResourceFailure (82),
155 -- Values 83-100 are reserved for equipment alarm related probable
157 -- The following are used with environmental alarm.
158 airCompressorFailure (101),
161 airConditioningFailure (102),
162 airDryerFailure (103),
163 batteryDischarging (104),
164 batteryFailure (105),
165 commercialPowerFailure (106),
166 coolingFanFailure (107),
168 fireDetectorFailure (109),
170 generatorFailure (111),
171 lowBatteryThreshold (112),
173 rectifierFailure (114),
174 rectifierHighVoltage (115),
175 rectifierLowFVoltage (116),
176 ventilationsSystemFailure (117),
177 enclosureDoorOpen (118),
182 highTemperature (123),
185 intrusionDetection (126),
188 lowCablePressure (129),
193 coolingSystemFailure (134),
194 externalEquipmentFailure (135),
195 externalPointFailure (136),
196 -- Values 137-150 are reserved for environmental alarm related
198 -- The following are used with Processing error alarm.
199 storageCapacityProblem (151),
200 memoryMismatch (152),
202 outOfCPUCycles (154),
203 sfwrEnvironmentProblem (155),
204 sfwrDownloadFailure (156),
205 lossOfRealTimel (157),
206 --A processing error alarm to be issued after the system has
207 --reinitialised. This will indicate
208 --to the management systems that the view they have of the managed
211 --system may no longer
212 --be valid. Usage example: The managed
213 --system issues this alarm after a reinitialization with severity
214 --warning to inform the
215 --management system about the event. No clearing notification will
217 applicationSubsystemFailure (158),
218 configurationOrCustomisationError (159),
219 databaseInconsistency (160),
223 timeoutExpired (164),
224 underlayingResourceUnavailable (165),
225 versionMismatch (166),
226 --Values 168-200 are reserved for processing error alarm related
228 bandwidthReduced (201),
230 excessiveErrorRate (203),
231 excessiveResponseTime (204),
232 excessiveRetransmissionRate (205),
233 reducedLoggingCapability (206),
234 systemResourcesOverload (207 ),
235 -- The following were defined X.733
237 applicationSubsystemFailture (501),
238 bandwidthReducedX733 (502),
239 callEstablishmentError (503),
240 communicationsProtocolError (504),
241 communicationsSubsystemFailure (505),
242 configurationOrCustomizationError (506),
243 congestionX733 (507),
245 cpuCyclesLimitExceeded (509),
246 dataSetOrModemError (510),
247 degradedSignalX733 (511),
248 dteDceInterfaceError (512),
249 enclosureDoorOpenX733 (513),
250 equipmentMalfunction (514),
251 excessiveVibration (515),
254 framingErrorX733 (518),
255 heatingVentCoolingSystemProblem (519),
256 humidityUnacceptable (520),
257 inputOutputDeviceError (521),
258 inputDeviceError (522),
263 localNodeTransmissionErrorX733 (525),
264 lossOfFrameX733 (526),
265 lossOfSignalX733 (527),
266 materialSupplyExhausted (528),
267 multiplexerProblemX733 (529),
268 outOfMemoryX733 (530),
269 ouputDeviceError (531),
270 performanceDegraded (532),
272 pressureUnacceptable (534),
273 processorProblems (535),
274 pumpFailureX733 (536),
275 queueSizeExceeded (537),
276 receiveFailureX733 (538),
277 receiverFailureX733 (539),
278 remoteNodeTransmissionErrorX733 (540),
279 resourceAtOrNearingCapacity (541),
280 responseTimeExecessive (542),
281 retransmissionRateExcessive (543),
282 softwareErrorX733 (544),
283 softwareProgramAbnormallyTerminated (545),
284 softwareProgramError (546),
285 storageCapacityProblemX733 (547),
286 temperatureUnacceptable (548),
287 thresholdCrossed (549),
288 timingProblemX733 (550),
289 toxicLeakDetected (551),
290 transmitFailureX733 (552),
291 transmiterFailure (553),
292 underlyingResourceUnavailable (554),
293 versionMismatchX733 (555),
294 -- The following are defined in X.736
295 authenticationFailure (600),
296 breachOfConfidentiality (601),
298 delayedInformation (603),
299 denialOfService (604),
300 duplicateInformation (605),
301 informationMissing (606),
302 informationModificationDetected (607),
303 informationOutOfSequence (608),
305 nonRepudiationFailure (610),
306 outOfHoursActivity (611),
308 proceduralError (613),
311 unauthorizedAccessAttempt (614),
312 unexpectedInformation (615),
317 IANAItuEventType ::= TEXTUAL-CONVENTION
320 "The ITU event Type values.
322 The Internet Assigned Number Authority (IANA) is
323 responsible for the assignment of the enumerations
326 Request should come in the form of well-formed
327 SMI [RFC2578] for enumeration names that are unique
328 and sufficiently descriptive.
330 See http://www.iana.org "
332 "ITU Recommendation X.736, 'Information Technology - Open
333 Systems Interconnection - System Management: Security
334 Alarm Reporting Function', 1992"
338 communicationsAlarm (2),
339 qualityOfServiceAlarm (3),
340 processingErrorAlarm (4),
342 environmentalAlarm (6),
343 integrityViolation (7),
344 operationalViolation (8),
345 physicalViolation (9),
346 securityServiceOrMechanismViolation (10),
347 timeDomainViolation (11)