1、 The attached document is a Registered Disclosure Document prepared by the proponent identified below. It has been examined by the appropriate SMPTE Technology Committee and is believed to contain adequate information to satisfy the objectives defined in the Scope, and to be technically consistent.
2、This document is NOT a Standard, Recommended Practice or Engineering Guideline, and does NOT imply a finding or representation of the Society. Errors in this document should be reported to the proponent identified below, with a copy to engsmpte.org. All other inquiries in respect of this document, i
3、ncluding inquiries as to intellectual property requirements that may be attached to use of the disclosed technology, should be addressed to the proponent identified below. Proponent contact information: Northon Rodrigues Thomson Broadcast and Media solutions 15655 SW Greystone Ct. Beaverton OR 97006
4、 (USA) Email Northon.RodriguesT Page 1 of 29 pages RDD 1-2003 Copyright 2003 by THE SOCIETY OF MOTION PICTURE AND TELEVISION ENGINEERS 595 W. Hartsdale Ave., White Plains, NY 10607 (914) 761-1100 Approved July 28, 2003 SMPTE REGISTERED DISCLOSURE DOCUMENT DDRMON-MIB-1 A Digital Disk Recorder Simple
5、Network Management Protocol Management Information Base RDD 1-2003 Page 2 of 29 pages 1 Scope This Registered Disclosure describes a Management Information Base (MIB) for a digital disk recorder. A MIB, when used with the Simple Network Management Protocol (SNMP), allows a remote computer to monitor
6、 the status, set certain device management variables and receive notifications when certain conditions occur. Additional MIBs may be used to monitor and manage other digital disk recorders and additional types of broadcast devices. This MIB does not describe a general-purpose device control protocol
7、. 2 Normative references The following documents contain provisions, which, through reference, constitute provisions of this document: RFC 1155, Rose, M. and McCloghrie, K., “Structure and Identification of Management Information for TCP/IP-based Internets”, May 1990 RFC 1157, Case, J., Fedor, M., S
8、choffstall, M. and Davin, J., “A Simple Network Management Protocol”, May 1990 RFC 1212, Rose, M. and McCloghrie, K., “Concise MIB Definitions”, March 1991 RFC 1902, Rose, M. and McCloghrie, K., “Structure of Management Information for Version 2 of the Simple Network Management Protocol”, January 19
9、96 RFC 1903, Rose, M., Case, J., Waldbusser, S., and McCloghrie, K., “Textual Conventions for Version 2 of the Simple Network Management Protocol”, January 1996 RFC 1904, Rose, M. and McCloghrie, K. “Conformance Statements for Version 2 of the Simple Network Management Protocol”, January 1996 RFC 19
10、05, Rose, M., Case, J., Waldbusser, S., and McCloghrie, K., ”Protocol Operations for Version 2 of the Simple Network Management Protocol, January 1996 RFC 1907, Rose, M. and McCloghrie, K., “Management Information Base for Version 2 of the Simple Network Management Protocol”, January 1996 3 Definiti
11、ons 3.1 agent: An entity that assumes the operational role of receiving, processing, and responding to requests, and generating event reports. It must have access to the network management information to respond to requests, and must be notified of internal events to generate reports. 3.2 columnar o
12、r table object: An object that has zero, one, or more instances at any point in time. For instance, the state of a TCP connection is a columnar object. There may be zero, one, or more TCP connections to a system at any point in time. Each TCP connection that exists has a state. 3.3 conceptual MIB ta
13、ble: The SMI requires related columnar objects to be organized into conceptual tables. One or more columnar objects defined in the same table or another table uniquely identify the instance of each columnar object in a table. These objects are collectively referred to as the tables index variables.
14、3.4 data types: Table 1 describes the data types or the syntax of the objects discussed in this document. RDD 1-2003 Page 3 of 29 pages Table 1 Data type descriptions Data Type Description INTEGER Enumerated 32-bit signed integer whose value varies between (-231) and (231-1) Integer32 32-bit signed
15、integer whose value varies between (-231) and (231-1) OCTET STRING Eight-bit bytes of binary or textual information. The maximum number of octets in an objects value is limited to 65535 (216-1) octets. IpAddress A string of four octets. A value of this type is an IPv4 address encoded in network byte
16、 order Counter32 A non-negative 32-bit integer whose range includes only non-negative integers. The reported value for objects of this type is a count, modulo 232, of the occurrence of an event or the measure of flow. The starting value of a counter is undefined unless specified where the type is us
17、ed. Gauge32 Specify a value whose range includes only non-negative integers. The values range from zero to (232-1). These types have the behavior such that the reported value is always within the specified range even when the actual value is outside the specified range. DisplayString A stream of eig
18、ht-bit bytes where each byte is a character from the NVT-ASCII character set. Note that this stream is not null-terminated. TimeTicks A non-negative value, whose range includes only non-negative integers. The reported value is an elapsed time, modulo 232, in units of hundredths of a second between t
19、wo events (or epochs). The length of time between rollovers is approximately 497 days. PhysAddress A stream of eight-bit bytes where the collective stream of bytes defines the data-link layer address of a network interface. Numerical values in this document that are preceded by 0x are hexadecimal va
20、lues. All other numerical values are decimal numbers. 3.5 management information base (MIB): Definitions of related management information, events, and associated implementation compliance requirements are specified in documents called management information base (MIB) specifications. These specific
21、ations include prose sections and computer readable descriptions. The MIB modules are written in an adapted sub-set of the ASN.1 language. In essence, MIBs are specifications containing definitions of management information so that networked systems can be remotely monitored, configured, and control
22、led. 3.6 manager, or management station: An entity that assumes the operational role of generating requests to retrieve or modify management information, receiving responses to requests, or receiving event reports. This role is assumed by (or on behalf of) a management application. 3.7 objects: In t
23、he SNMP framework, a system is managed by retrieval and modification of management information. Each class (or type) of management information is called an object. The definition of an object RDD 1-2003 Page 4 of 29 pages type includes its data type, the maximum allowed access, its assigned identity
24、, how instances are identified, and its semantics (or behaviors). 3.8 object group: A collection of logically related objects within a MIB module. It refers to a collection of scalar objects and/or columnar and scalar objects. Grouping objects aids in maintenance and improves organization of the MIB
25、 module. Groups also permit selective implementation of related managed objects on the agent. 3.9 object identifier (OID): An identification scheme conceptualized in abstract syntax notation one (ASN.1) is used to uniquely identify managed objects by assigning an identifier to each object. This iden
26、tifier is administratively assigned such that it uniquely identifies the object for all space and time and is called an object identifier (OID). An OID value is an ordered sequence of non-negative integers, written from left to right, containing at least two elements. SNMP imposes a restriction on t
27、he maximum length of any OID value to 128 numbers in the sequence and the maximum value of a number to 232-1. Each number in the sequence is called a sub-identifier in the SMI. An OID value is usually written as a sequence of numbers separated by a dot (.) and optionally labeled. 3.10 object instanc
28、e or variable: A specific instance from a class of management information is called a variable or an object instance. 3.11 scalar objects: An object that has exactly one instance or value. An example of a scalar object is the location of a managed system, since a system has exactly one location. 3.1
29、2 SnmpGet: An SNMP operation used to retrieve the value of an objects instance. The operand is a list of identities, which exactly match the identity of returned variables. 3.13 SnmpGetNext: An SNMP operation used to retrieve the value of an objects instance. The operand is a list of identities, whi
30、ch are approximations of the identity of returned variables. Each returned identity is the one assigned to the first accessible variable whose identity is greater than the given identity. 3.14 SnmpSet: An SNMP operation used to modify the value of an objects instance. The operand is a list of pairs.
31、 Each pair consists of the identity of a variable and its desired value. SnmpSet operations are used to configure and control a managed system. 3.15 SnmpTrap, or SnmpNotification: An SNMP event reporting operation, which specifies an event and zero or more list of pairs. A pair consists of the ident
32、ity of a variable and its value. This operation is used to report the occurrence of events on a managed system to a list of managers configured to receive events for that managed system. 3.16 structure of management information (SMI): The rules for writing SNMP MIBs defined using a subset of ASN.1.
33、These rules include the type definition or syntax of objects, rules to define objects, notifications, and other constructs used in the MIBs. RFC1155 defines the SMI for version 1. RFC1212 called the SNMPv2-SMI supersedes RFC1155-SMI and enhances it. This is the definition of SMI version 2. The DDRMO
34、N-MIB1 MIB uses SMIv2 for its MIB definitions. 3.17 VITC: Vertical interval time code. 4 DDRMON-MIB1 MIB overview The DDRMON-MIB1 MIB is a specific MIB module that contains SMIv2 compliant definitions of managed objects used for networked monitoring of digital disk recorders. The MIB is classified i
35、nto four major groups: The pvsNotifications group which defines all the DDRMON-MIB1specific notifications RDD 1-2003 Page 5 of 29 pages The pvsGeneral group which defines generic diagnostic objects and objects that allow fine tuning of the DDRMON-MIB1s internal monitoring engine. The pvsCardCage gro
36、up which defines the slot-map information of the disk recorder card cage and board specific status information. The pvsSubSystems group which further segregates object definitions depending on logical subsystems on the disk recorder. The MIB objects descriptions discussed in the document use the fol
37、lowing conventions: Default integer enumeration: In Italic. Objects that can accept a SnmpSet operation (Read/Write objects): In Italic. Objects that are a table index: In Bold. 5 pvsGeneral group This group defines objects which aid in diagnostics, as well as a group dedicated to the configuration
38、of the fault indicators incorporated into the disk recorder. 5.1 General system level diagnostic aiding objects These objects, although not directly initiating or reporting the results of system diagnostics, provide general reporting which may assist in interpreting the results of diagnostics. Table
39、 2 Generic diagnostic objects Object Syntax Usage PvsMode INTEGER normal-mode(1), maintenance-mode(2) The disk recorder system software runs in two distinct modes. In normal-mode, media operations can be performed the system. In maintenance-mode, only maintenance operations such as running system di
40、agnostics can be performed. pvsLastTrapCategory INTEGER alarm(1), warning(2), informational(3), resent-alarm(32769), resent-warning(32770) This object holds the category of the trap that was last dispatched. It can be used by a manager to decode the categorization of disk recorder MIB traps and is i
41、ncluded as the first enterprise variable in every disk recorder MIB trap. Resent-alarm and resent-warning used when the system resends previously sent warnings and alarms that are not handled or acknowledged within a stipulated time. pvsSerialCode DisplayString The serial number assigned to this dis
42、k recorder. pvsSoftwareBuild DisplayString The disk recorder software build number. pvsModel DisplayString Indicates the disk recorder model. pvsVerLow Integer32 The lower order version-stamp of the SNMP software that is used on the disk recorder. This number matches the number of revisions to this
43、MIB module. pvsVerHigh Integer32 The higher order version stamp of the SNMP software that is used on the disk recorder. This number implies major upgrades to the agent software, for instance support for new MIB modules. RDD 1-2003 Page 6 of 29 pages 5.2 Fault indicator configuration group Along with
44、 SNMP-based monitoring, the disk recorder uses public and private logs to trace all its operations. A fault indicator installed on the front panel indicates operational anomalies, and a subset of the GPI output ports is used for general purpose electrical switching to trigger customized hardware-bas
45、ed notifications. The objects in this group provide control and configuration of the behavior of these fault indicator resources. Table 3 Fault indicator objects Object Syntax Usage pvsFaultLed INTEGER led-off (1), led-on (2) The system provides a general-purpose front panel indicator (LED) which si
46、gnals system status. An SnmpSet operation with the value led-on(1) lights the indicator, signaling a system fault. pvsTrapResendEnable INTEGER trap-resend-disable( 1), trap-resend-enable (2) The system can resend SNMP warning or alarm traps periodically until it detects a normal condition for that a
47、larm or warning. This variable disables or enables the trap resend. By default, resend is enabled. A change to this value takes effect only after a system reboot, although a subsequent SnmpGet prior to the reboot returns the new value. pvsTrapResendInterval TimeTicks This variable holds the warning
48、or alarm trap resend frequency in hundredths of a second. The default value is 360000, which corresponds to a default resend interval of one hour. A change to this value takes effect only after a system reboot, although a subsequent SnmpGet prior to the reboot returns the new value. PvsSuppressionIn
49、terval TimeTicks Under certain circumstances. the system may log the same information repetitively. This variable suppresses repeated messages for the specified duration. A value of 0 indicates that the system will not suppress any repeated messages. The default value is 180000, which i suppresses repeated log messages for a duration of half an hour. A change to this value takes effect only after a system reboot, although a subsequent SnmpGet prior to the reboot returns the new value. The GPI output control and configuration
