1IANA-ITU-ALARM-TC-MIB DEFINITIONS ::= BEGIN 2 3 IMPORTS 4 MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI 5 TEXTUAL-CONVENTION FROM SNMPv2-TC; 6 7 ianaItuAlarmNumbers MODULE-IDENTITY 8 LAST-UPDATED "201405220000Z" -- May 22, 2014 9 ORGANIZATION "IANA" 10 CONTACT-INFO 11 "Postal: Internet Assigned Numbers Authority 12 Internet Corporation for Assigned Names 13 and Numbers 14 12025 Waterfront Drive, Suite 300 15 Los Angeles, CA 90094-2536 16 USA 17 18 Tel: +1 310-301-5800 19 E-Mail: iana&iana.org" 20 DESCRIPTION 21 "The MIB module defines the ITU Alarm 22 textual convention for objects expected to require 23 regular extension. 24 25 Copyright (C) The Internet Society (2004). The 26 initial version of this MIB module was published 27 in RFC 3877. For full legal notices see the RFC 28 itself. Supplementary information may be available on: 29 http://www.ietf.org/copyrights/ianamib.html" 30 31 REVISION "201405220000Z" 32 DESCRIPTION 33 "Updated contact info." 34 35 REVISION "200409090000Z" 36 DESCRIPTION 37 "Initial version, published as RFC 3877." 38 ::= { mib-2 119 } 39 40 IANAItuProbableCause ::= TEXTUAL-CONVENTION 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 SYNTAX INTEGER 84 { 85 -- The following probable causes were defined in M.3100 86 aIS (1), 87 callSetUpFailure (2), 88 degradedSignal (3), 89 farEndReceiverFailure (4), 90 framingError (5), 91 lossOfFrame (6), 92 lossOfPointer (7), 93 lossOfSignal (8), 94 payloadTypeMismatch (9), 95 transmissionError (10), 96 remoteAlarmInterface (11), 97 excessiveBER (12), 98 pathTraceMismatch (13), 99 unavailable (14), 100 signalLabelMismatch (15), 101 lossOfMultiFrame (16), 102 receiveFailure (17), 103 transmitFailure (18), 104 modulationFailure (19), 105 demodulationFailure (20), 106 broadcastChannelFailure (21), 107 connectionEstablishmentError (22), 108 invalidMessageReceived (23), 109 localNodeTransmissionError (24), 110 remoteNodeTransmissionError (25), 111 routingFailure (26), 112 --Values 27-50 are reserved for communications alarm related 113 --probable causes 114 -- The following are used with equipment alarm. 115 backplaneFailure (51), 116 dataSetProblem (52), 117 equipmentIdentifierDuplication (53), 118 externalIFDeviceProblem (54), 119 lineCardProblem (55), 120 multiplexerProblem (56), 121 nEIdentifierDuplication (57), 122 powerProblem (58), 123 processorProblem (59), 124 protectionPathFailure (60), 125 receiverFailure (61), 126 replaceableUnitMissing (62), 127 replaceableUnitTypeMismatch (63), 128 synchronizationSourceMismatch (64), 129 terminalProblem (65), 130 timingProblem (66), 131 transmitterFailure (67), 132 trunkCardProblem (68), 133 replaceableUnitProblem (69), 134 realTimeClockFailure (70), 135 --An equipment alarm to be issued if the system detects that the 136 --real time clock has failed 137 antennaFailure (71), 138 batteryChargingFailure (72), 139 diskFailure (73), 140 frequencyHoppingFailure (74), 141 iODeviceError (75), 142 lossOfSynchronisation (76), 143 lossOfRedundancy (77), 144 powerSupplyFailure (78), 145 signalQualityEvaluationFailure (79), 146 tranceiverFailure (80), 147 protectionMechanismFailure (81), 148 protectingResourceFailure (82), 149 -- Values 83-100 are reserved for equipment alarm related probable 150 -- causes 151 -- The following are used with environmental alarm. 152 airCompressorFailure (101), 153 airConditioningFailure (102), 154 airDryerFailure (103), 155 batteryDischarging (104), 156 batteryFailure (105), 157 commercialPowerFailure (106), 158 coolingFanFailure (107), 159 engineFailure (108), 160 fireDetectorFailure (109), 161 fuseFailure (110), 162 generatorFailure (111), 163 lowBatteryThreshold (112), 164 pumpFailure (113), 165 rectifierFailure (114), 166 rectifierHighVoltage (115), 167 rectifierLowFVoltage (116), 168 ventilationsSystemFailure (117), 169 enclosureDoorOpen (118), 170 explosiveGas (119), 171 fire (120), 172 flood (121), 173 highHumidity (122), 174 highTemperature (123), 175 highWind (124), 176 iceBuildUp (125), 177 intrusionDetection (126), 178 lowFuel (127), 179 lowHumidity (128), 180 lowCablePressure (129), 181 lowTemperatue (130), 182 lowWater (131), 183 smoke (132), 184 toxicGas (133), 185 coolingSystemFailure (134), 186 externalEquipmentFailure (135), 187 externalPointFailure (136), 188 -- Values 137-150 are reserved for environmental alarm related 189 -- probable causes 190 -- The following are used with Processing error alarm. 191 storageCapacityProblem (151), 192 memoryMismatch (152), 193 corruptData (153), 194 outOfCPUCycles (154), 195 sfwrEnvironmentProblem (155), 196 sfwrDownloadFailure (156), 197 lossOfRealTimel (157), 198 --A processing error alarm to be issued after the system has 199 --reinitialised. This will indicate 200 --to the management systems that the view they have of the managed 201 --system may no longer 202 --be valid. Usage example: The managed 203 --system issues this alarm after a reinitialization with severity 204 --warning to inform the 205 --management system about the event. No clearing notification will 206 --be sent. 207 applicationSubsystemFailure (158), 208 configurationOrCustomisationError (159), 209 databaseInconsistency (160), 210 fileError (161), 211 outOfMemory (162), 212 softwareError (163), 213 timeoutExpired (164), 214 underlayingResourceUnavailable (165), 215 versionMismatch (166), 216 --Values 168-200 are reserved for processing error alarm related 217 -- probable causes. 218 bandwidthReduced (201), 219 congestion (202), 220 excessiveErrorRate (203), 221 excessiveResponseTime (204), 222 excessiveRetransmissionRate (205), 223 reducedLoggingCapability (206), 224 systemResourcesOverload (207 ), 225 -- The following were defined X.733 226 adapterError (500), 227 applicationSubsystemFailture (501), 228 bandwidthReducedX733 (502), 229 callEstablishmentError (503), 230 communicationsProtocolError (504), 231 communicationsSubsystemFailure (505), 232 configurationOrCustomizationError (506), 233 congestionX733 (507), 234 coruptData (508), 235 cpuCyclesLimitExceeded (509), 236 dataSetOrModemError (510), 237 degradedSignalX733 (511), 238 dteDceInterfaceError (512), 239 enclosureDoorOpenX733 (513), 240 equipmentMalfunction (514), 241 excessiveVibration (515), 242 fileErrorX733 (516), 243 fireDetected (517), 244 framingErrorX733 (518), 245 heatingVentCoolingSystemProblem (519), 246 humidityUnacceptable (520), 247 inputOutputDeviceError (521), 248 inputDeviceError (522), 249 lanError (523), 250 leakDetected (524), 251 localNodeTransmissionErrorX733 (525), 252 lossOfFrameX733 (526), 253 lossOfSignalX733 (527), 254 materialSupplyExhausted (528), 255 multiplexerProblemX733 (529), 256 outOfMemoryX733 (530), 257 ouputDeviceError (531), 258 performanceDegraded (532), 259 powerProblems (533), 260 pressureUnacceptable (534), 261 processorProblems (535), 262 pumpFailureX733 (536), 263 queueSizeExceeded (537), 264 receiveFailureX733 (538), 265 receiverFailureX733 (539), 266 remoteNodeTransmissionErrorX733 (540), 267 resourceAtOrNearingCapacity (541), 268 responseTimeExecessive (542), 269 retransmissionRateExcessive (543), 270 softwareErrorX733 (544), 271 softwareProgramAbnormallyTerminated (545), 272 softwareProgramError (546), 273 storageCapacityProblemX733 (547), 274 temperatureUnacceptable (548), 275 thresholdCrossed (549), 276 timingProblemX733 (550), 277 toxicLeakDetected (551), 278 transmitFailureX733 (552), 279 transmiterFailure (553), 280 underlyingResourceUnavailable (554), 281 versionMismatchX733 (555), 282 -- The following are defined in X.736 283 authenticationFailure (600), 284 breachOfConfidentiality (601), 285 cableTamper (602), 286 delayedInformation (603), 287 denialOfService (604), 288 duplicateInformation (605), 289 informationMissing (606), 290 informationModificationDetected (607), 291 informationOutOfSequence (608), 292 keyExpired (609), 293 nonRepudiationFailure (610), 294 outOfHoursActivity (611), 295 outOfService (612), 296 proceduralError (613), 297 unauthorizedAccessAttempt (614), 298 unexpectedInformation (615), 299 other (1024) 300 } 301 302 IANAItuEventType ::= TEXTUAL-CONVENTION 303 STATUS current 304 DESCRIPTION 305 "The ITU event Type values. 306 307 The Internet Assigned Number Authority (IANA) is 308 responsible for the assignment of the enumerations 309 in this TC. 310 311 Request should come in the form of well-formed 312 SMI [RFC2578] for enumeration names that are unique 313 and sufficiently descriptive. 314 315 See http://www.iana.org " 316 REFERENCE 317 "ITU Recommendation X.736, 'Information Technology - Open 318 Systems Interconnection - System Management: Security 319 Alarm Reporting Function', 1992" 320 SYNTAX INTEGER 321 { 322 other (1), 323 communicationsAlarm (2), 324 qualityOfServiceAlarm (3), 325 processingErrorAlarm (4), 326 equipmentAlarm (5), 327 environmentalAlarm (6), 328 integrityViolation (7), 329 operationalViolation (8), 330 physicalViolation (9), 331 securityServiceOrMechanismViolation (10), 332 timeDomainViolation (11) 333 } 334 335 END 336