1SCTE-HMS-HEADENDIDENT-TC-MIB DEFINITIONS ::= BEGIN 2 3IMPORTS 4 MODULE-IDENTITY, enterprises, Integer32, Unsigned32 5 FROM SNMPv2-SMI 6 TEXTUAL-CONVENTION 7 FROM SNMPv2-TC; 8 9hmsTextualConventionMIB MODULE-IDENTITY 10 LAST-UPDATED "200807231300Z" 11 ORGANIZATION "SCTE HMS Working Group" 12 CONTACT-INFO "SCTE HMS Subcommittee, Chairman 13 mail to: standards@scte.org " 14 15 DESCRIPTION 16 "The MIB module is for representing general information 17 about HeadEnd Digital equipment present(or indoor) 18 and is supported by an SNMP agent." 19 20 REVISION "200807231300Z" 21 DESCRIPTION "Changed enumeration for QAMChannelInterleaveMode." 22 23 REVISION "200807121300Z" 24 DESCRIPTION 25 "Modifications due to Comment Resolution Phase 2 26 1. Un-Commented out HeAlarmControl, HeTrapRegenerate to add Alarm Processing 27 back into the HMS-154 mib files. 28 2. Added support for Alarm Processing. 29 3. Removed enumerations that were not used under the heDigital tree (heLaserType). 30 4. Modified QAMChannelModulationFormat. 31 5. Removed Display String from IMPORTS 32 6. Removed HeLaserType 33 7. Added enumeration QAMChannelInterleaveMode" 34 35 36 REVISION "200801161300Z" 37 DESCRIPTION 38 "Modifications due to Comment Resolution Meeting 39 1. Commented out HeAlarmControl, HeTrapRegenerate, HeDigitalRedundancyStatus 40 per Comment Resolution meeting for formal release of the Mib File. 41 2. Added comments to HeDigitalAlarmSeverity and HeDigitalAlarmType that they 42 are not used per Comment Resolution meeting for formal release of the Mib File, 43 and commented out the enumerations so no-one uses them until they are needed in 44 case they will have to change. 45 3. Added the enumeration other to HeDigitalAlarmType so it would be universal." 46 47 REVISION "200712170000Z" 48 DESCRIPTION 49 "Modifications due to voting comments 50 1. Changed syntax errors for capitalized words. 51 2. Changed mib to have the -MIB extention" 52 53 ::= { enterprises scteRoot(5591) scteHmsTree (1) insidePlantIdent (11) 54 heDigital (5) 1 } 55 56VideoInputFrameRateType ::= TEXTUAL-CONVENTION 57 STATUS current 58 DESCRIPTION 59 " This value defines the types of MPEG Video Input Frame Rate that is 60 supported by QAM devices." 61 SYNTAX INTEGER { 62 other (1), 63 autoSelect (2), 64 f24Hz (3), 65 f25Hz (4), 66 f29Hz97 (5), 67 f30Hz (6), 68 f29or30Hz (7), 69 f48Hz (8), 70 f50Hz (9), 71 f59Hz94 (10), 72 f60Hz (11), 73 f59or60Hz (12) } 74 75QAMChannelModulationFormat ::= TEXTUAL-CONVENTION 76 STATUS current 77 DESCRIPTION 78 " This value defines the types of QAM Channel Modulation that is 79 supported by QAM devices." 80 SYNTAX INTEGER { 81 unknown(1), 82 other(2), 83 qam64(3), 84 qam256(4), 85 qam128(5), 86 qam512 (6), 87 qam1024 (7) 88 } 89 90QAMChannelInterleaveMode ::= TEXTUAL-CONVENTION 91 STATUS current 92 DESCRIPTION 93 " This value defines the types of QAM Interleave Mode 94 which follows the value of docsIfDownChannelInterleave. This 95 value is supported by HMS QAM devices." 96 SYNTAX INTEGER { 97 unknown(1), 98 other(2), 99 fecI8J16(3), 100 fecI16J8(4), 101 fecI32J4(5), 102 fecI64J2(6), 103 fecI128J1(7), 104 fecI12J17(8), 105 fecI128J2(9), 106 fecI128J3(10), 107 fecI128J4(11), 108 fecI128J5(12), 109 fecI128J6(13), 110 fecI128J7(14), 111 fecI128J8(15) 112 } 113 114 115ProgDataType ::= TEXTUAL-CONVENTION 116 STATUS current 117 DESCRIPTION 118 "This value defines the types of data that can be contained in 119 Programs and program streams." 120 SYNTAX INTEGER { 121 video (1), 122 audio (2), 123 data (3), 124 other(4) 125 } 126 127DeviceEnableDisableValues ::= TEXTUAL-CONVENTION 128 STATUS current 129 DESCRIPTION 130 "This data type represents whether the object is disabled(1) or 131 enabled(2), or the object is not supported (3) by the current 132 configuration or this device's hardware." 133 SYNTAX INTEGER { 134 disabled (1), 135 enabled (2), 136 notSupported(3) 137 } 138 139 140MpegErrorStatus ::= TEXTUAL-CONVENTION 141 STATUS current 142 DESCRIPTION 143 "This data type represents whether the object is good(1) or has 144 errors(2), or the object is not supported (3) by the current 145 configuration or this device's hardware." 146 SYNTAX INTEGER { 147 good (1), 148 errors (2), 149 notSupported(3) 150 } 151 152HePIDValue ::= TEXTUAL-CONVENTION 153 DISPLAY-HINT "d" 154 STATUS current 155 DESCRIPTION 156 "This data type represents a packet identifier (PID) 157 value which ranges from 0 to (2^13 - 1). The value of 158 65535 indicates that either the PID is invalid or does 159 not exist." 160 SYNTAX Unsigned32 (0..8191 | 65535) 161 162HeClockSource ::= TEXTUAL-CONVENTION 163 STATUS current 164 DESCRIPTION 165 "An enumerated value that provides the location where the 166 value for the clock on the module is coming from. 167 internal - this value is being derived internally from the local 168 module timing source. 169 external - an source that is external to the module, such as a 170 controller card is providing a signal to calculate the real time clock. 171 ntp - this module is running the ntp protocol and can sync up to a 172 master ntp clock source. 173 other - the real time clock source does not fit into the existing values. " 174 SYNTAX INTEGER { 175 unknown(1), 176 other(2), 177 internal(3), 178 external(4), 179 ntp(5), 180 none(6) 181 } 182 183HeResetValue ::= TEXTUAL-CONVENTION 184 STATUS current 185 DESCRIPTION 186 "Configured reset value for a specific device. 187 reset - the value of reset is SET at the device and the device 188 will reset. 189 running - the normal value of the device is running when an SNMP 190 GET of the reset value is sent. 191 resetting - The value resetting shall be returned if an SNMP GET of 192 the device is performed after a reset SET command is sent and before 193 the device can actually perform the reset. A second reset SET command 194 should not interrupt the reset sequence. If a second SET is sent, it 195 will be ignored. 196 " 197 SYNTAX INTEGER { 198 reset(1), 199 running(2), 200 resetting(3) 201 } 202 203HeTenthVolt ::= TEXTUAL-CONVENTION 204 DISPLAY-HINT "d-1" 205 STATUS current 206 DESCRIPTION 207 "This data type represents voltage levels that are normally 208 expressed in volts. Units are in tenths of a volt; 209 for example, -48.1 volts will be represented as -481." 210 SYNTAX Integer32 211 212HeTenthdBm ::= TEXTUAL-CONVENTION 213 DISPLAY-HINT "d-1" 214 STATUS current 215 DESCRIPTION 216 "This data type represents power levels 217 that are normally expressed in dBm. Units 218 are in tenths of a dBm; 219 for example, -5.1 dBm will be represented as -51." 220 SYNTAX Integer32 221 222HeTenthdBmV ::= TEXTUAL-CONVENTION 223 DISPLAY-HINT "d-1" 224 STATUS current 225 DESCRIPTION 226 "This data type represents power levels 227 that are normally expressed in dBmV. Units 228 are in tenths of a dBmV; 229 for example, -5.1 dBmV will be represented as -51." 230 SYNTAX Integer32 231 232HeTenthCentigrade ::= TEXTUAL-CONVENTION 233 DISPLAY-HINT "d-1" 234 STATUS current 235 DESCRIPTION 236 "This data type represents temperature values that 237 are normally expressed in Centigrade. Units are in 238 tenths of a Centigrade; 239 for example, -5.1 Centigrade will be represented as -51." 240 SYNTAX Integer32 241 242HeHundredthNanoMeter ::= TEXTUAL-CONVENTION 243 DISPLAY-HINT "d-2" 244 STATUS current 245 DESCRIPTION 246 "This data type represents wavelength values that 247 are normally expressed in nano meters. Units are in 248 hundredths of a NanoMeter; 249 for example, 1550.56 nm will be represented as 155056." 250 SYNTAX Unsigned32 251 252HeTenthdB ::= TEXTUAL-CONVENTION 253 DISPLAY-HINT "d-1" 254 STATUS current 255 DESCRIPTION 256 "This data type represents power levels 257 that are normally expressed in dB. Units 258 are in tenths of a dB; 259 for example, -5.1 dB will be represented as -51." 260 SYNTAX Integer32 261 262HeOnOffControl ::= TEXTUAL-CONVENTION 263 STATUS current 264 DESCRIPTION 265 "An enumerated value that provides a control of a particular 266 hardware or software parameter that usually represent 267 some sort of switch. 268 269 A SET request with a value off(1) will cause the switch 270 to be shut off. 271 272 A SET request with a value on(2) will cause the switch 273 to be turned on. 274 275 A value meaningless(3) will be implemented by the 276 variables that represent a switch with write-only access. 277 A GET request for the value of the write-only variable 278 shall return a value meaningless(3). 279 280 A SET request with a value meaningless(3) for the variable 281 with write access shall have no effect and no exception is 282 generated. 283 284 A value may be used by the variables with both read-write 285 and write-only access. 286 287 The variables with read-only access shall be defined with 288 the textual convention HeOnOffStatus." 289 SYNTAX INTEGER { 290 off(1), 291 on(2), 292 meaningless(3) 293 } 294 295HeOnOffStatus ::= TEXTUAL-CONVENTION 296 STATUS current 297 DESCRIPTION 298 "An enumerated value that provides a status of a particular 299 hardware or software parameter that usually represent 300 some sort of switch. 301 302 A value off(1) indicates the switch is off. 303 304 A value on(2) indicates the switch is on." 305 SYNTAX INTEGER { 306 off(1), 307 on(2) 308 } 309 310 311-- 312-- Values to support Alarmable parameters 313-- 314 315 316HeAlarmControl ::= TEXTUAL-CONVENTION 317 STATUS current 318 DESCRIPTION 319 "Alarm Control value for a specific device. This object is used to control sending 320 traps related to this headend entity or enabling disabling of raising an alarm 321 condition for a specific entity." 322 SYNTAX INTEGER { 323 alarmEnabled(1), 324 alarmDisabled(2) 325 } 326 327 328HeTrapRegenerate ::= TEXTUAL-CONVENTION 329 STATUS current 330 DESCRIPTION 331 " This value tells the SNMP Agent to send the Trap Regenerate Trap for 332 all values of Current alarms for this entity. The device can provide 333 for a means to send ALL current alarms, not just one specific entity." 334 SYNTAX INTEGER { 335 trapRegenerate(1), 336 trapNormal(2) 337 } 338 339HeDigitalAlarmSeverity ::= TEXTUAL-CONVENTION 340 STATUS current 341 DESCRIPTION 342 " The alarm severity that is determined by the device and sent over in the trap message." 343 SYNTAX INTEGER { 344 critical(1), 345 major(2), 346 minor(3), 347 warning(4), 348 status(5), 349 clear(6), 350 information(7) 351 } 352 353HeDigitalAlarmType ::= TEXTUAL-CONVENTION 354 STATUS current 355 DESCRIPTION 356 " The alarm type that describes the Event that caused the alarm." 357 SYNTAX INTEGER 358 { 359 communication(1), 360 process(2), 361 session(3), 362 capacity(4), 363 maintenance(5), 364 provisioning(6), 365 programMgmt(7), 366 redundancy(8), 367 other(9) 368 } 369 370HeFaultStatus ::= TEXTUAL-CONVENTION 371 STATUS current 372 DESCRIPTION 373 "An enumerated value that provides a fault status of 374 a particular hardware or software parameter that 375 usually represent some sort of condition. 376 377 A value normal(1) indicates the normal condition. 378 379 A value fault(2) indicates the fault condition." 380 SYNTAX INTEGER { 381 normal(1), 382 fault(2) 383 } 384 385 386HeMilliAmp ::= TEXTUAL-CONVENTION 387 DISPLAY-HINT "d-3" 388 STATUS current 389 DESCRIPTION 390 "This data type represents current levels that are normally 391 expressed in amperes. Units are in milliamperes; 392 for example, 2.1 Amperes would be expressed as 2100." 393 SYNTAX Unsigned32 394 395HeHundredthWatts ::= TEXTUAL-CONVENTION 396 DISPLAY-HINT "d-2" 397 STATUS current 398 DESCRIPTION 399 "This data type represents power values that 400 are normally expressed in watts. Units are in 401 hundredths of a watt; 402 for example, 420 watts will be represented as 42000." 403 SYNTAX Unsigned32 404 405 406-- 407-- Redundancy Status was removed from heDigitalCommon and is Commented out per comment 408-- resolution meeting until such time as heDigitalCommon redundancy values are implemented. 409-- 410 411-- HeDigitalRedundancyStatus ::= TEXTUAL-CONVENTION 412-- STATUS current 413-- DESCRIPTION 414-- "This value will indicate the supported level of redundancy for this 415-- entity. 416-- notAvailable, this interface does not support any type of redundancy, 417-- no Mib objects are supported. 418-- 419-- off - some type of redundancy is available and is defined in configuration, 420-- but redundancy for this entity is turned off. 421-- 422-- automatic - there is redundancy and the function is not defined in 423-- configuration, the redundant switch is automatic and always on. 424-- 425-- LoadBalanced, this interface is paired with a specific interface and shares 426-- the load. Any redundant switch will send as many streams to the other 427-- interface as possible. In this condition there isn't a 100% backup unless 428-- both links are only operating at 50% of the maximum capacity. 429-- 430-- hotStandby - redundancy is a one to one relationship with one entity 431-- configured to take over in the event of failure with minimal to no disruption 432-- in service. 433-- 434-- backup - would be for any interface that isn't one to one. You could have 435-- 1 backup to 2 active, 1 to 3, 1 to 4 or any combination of backup scenarios. 436-- The exact combinations would be part of Redundancy configuration, not this 437-- configured status parameter. The backup redundant configuration could cause 438-- minimal disruption of service. 439-- 440-- other - this would cover any type of redundancy that is not described by the 441-- other definitions. This would mean that the entity does support redundancy of 442-- some type. " 443-- SYNTAX INTEGER { 444-- notAvailable(1), 445-- off(2), 446-- automatic(3), 447-- loadBalanced(4), 448-- hotStandby(5), 449-- backup(6), 450-- other(7) 451-- } 452-- 453 454END 455