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