ITU-T J 176-2002 IPCablecom management event mechanism MIB SERIES J CABLE NETWORKS AND TRANSMISSION OF TELEVISION SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS IPCablecom (Study Gro.pdf

1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T J.176TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (07/2002) SERIES J: CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS IPCablecom IPCablecom management event mechanism MIBITU-T Recommendation J.176 ITU-T J-SER

2、IES RECOMMENDATIONS CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS General Recommendations J.1J.9 General specifications for analogue sound-programme transmission J.10J.19 Performance characteristics of analogue sound-programme circuits J.20J.29 Equipment

3、 and lines used for analogue sound-programme circuits J.30J.39 Digital encoders for analogue sound-programme signals J.40J.49 Digital transmission of sound-programme signals J.50J.59 Circuits for analogue television transmission J.60J.69 Analogue television transmission over metallic lines and inter

4、connection with radio-relay links J.70J.79 Digital transmission of television signals J.80J.89 Ancillary digital services for television transmission J.90J.99 Operational requirements and methods for television transmission J.100J.109 Interactive systems for digital television distribution J.110J.12

5、9 Transport of MPEG-2 signals on packetised networks J.130J.139 Measurement of the quality of service J.140J.149 Digital television distribution through local subscriber networks J.150J.159 IPCablecom J.160J.179 Miscellaneous J.180J.199 Application for Interactive Digital Television J.200J.209 For f

6、urther details, please refer to the list of ITU-T Recommendations. ITU-T Rec. J.176 (07/2002) i ITU-T Recommendation J.176 IPCablecom management event mechanism MIB Summary This Recommendation defines the MIB for Management Event Mechanism that IPCablecom elements can use to report to management sys

7、tems and/or local logs asynchronous events that indicate malfunction situations and notification about important non-fault situation. Source ITU-T Recommendation J.176 was prepared by ITU-T Study Group 9 (2001-2004) and approved under the WTSA Resolution 1 procedure on 29 July 2002. ii ITU-T Rec. J.

8、176 (07/2002) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff

9、questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommenda

10、tions on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendati

11、on, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a c

12、laimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU ha

13、d not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. ITU 2002 All right

14、s reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. ITU-T Rec. J.176 (07/2002) iii CONTENTS Page 1 Scope 1 2 References. 1 2.1 Normative references 1 2.2 Informative . 1 3 Terms and definitions . 2 4 Abbreviations and acron

15、yms 2 5 Conventions 2 6 IPCablecom Management Event MIB 3 ITU-T Rec. J.176 (07/2002) 1 ITU-T Recommendation J.176 IPCablecom management event mechanism MIB 1 Scope The Management Event MIB provides a common data and format definition for events (informative, alarm, etc). It also specifies by what me

16、ans events are transmitted. Use of a common event mechanism facilitates management of the MTA in a multi-vendor environment and provides a standard means to implement IPCablecom specified events. This Recommendation describes an SNMP MIB to support the management event mechanism as described in ITU-

17、T Rec. J.172. It is intended to be implemented in the MTA, and management devices. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions in

18、dicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T

19、 Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. 2.1 Normative references ITU-T Recommendation J.172 (2002), IPCablecom management event mechanism. 2.2 Informative ITU-T Recomm

20、endation J.160 (2002), Architectural framework for the delivery of time-critical services over cable television networks using cable modems. ITU-T Recommendation J.162 (2001), Network call signalling protocol for the delivery of time-critical services over cable television networks using cable modem

21、s. ITU-T Recommendation J.167 (2001), Media terminal adapter (MTA) device provisioning requirements for the delivery of real-time services over cable television networks using cable modems. ITU-T Recommendation J.168 (2001), IPCablecom Media Terminal Adapter (MTA) MIB requirements. ITU-T Recommendat

22、ion J.169 (2001), IPCablecom network call signalling (NCS) MIB requirements. ITU-T Recommendation J.170 (2002), IPCablecom security specification. IETF RFC 1906 (1996), Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2). IETF RFC 2570 (1999), Introduction to Version

23、3 of the Internet-standard Network Management Framework. IETF RFC 2571 (1999), An Architecture for Describing SNMP Management Frameworks. IETF RFC 2572 (1999), Message Processing and Dispatching for the Simple Network Management Protocol (SNMP). 2 ITU-T Rec. J.176 (07/2002) IETF RFC 2573 (1999), SNM

24、P Applications. IETF STD0058 (RFC 2579) (1999), Textual Conventions for SMIv2. 3 Terms and definitions This Recommendation defines the following term: 3.1 endpoint: A Terminal, Gateway or MCU. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations: FQDN Fully Qualified Dom

25、ain Name IANA Internet Assigned Numbers Authority IP Internet Protocol MAC Media Access Control MIB Management Information Base MTA Media Terminal Adapter SNMP Simple Network Management Protocol 5 Conventions If this Recommendation is implemented, the keywords “MUST“ and “SHALL“ as well as “REQUIRED

26、“ are to be interpreted as indicating a mandatory aspect of this Recommendation. The keywords indicating a certain level of significance of particular requirements that are used throughout this Recommendation are summarized below. “MUST“ This word or the adjective “REQUIRED“ means that the item is a

27、n absolute requirement of this Recommendation. “MUST NOT“ This phrase means that the item is an absolute prohibition of this Recommendation. “SHOULD“ This word or the adjective “RECOMMENDED“ means that there may exist valid reasons in particular circumstances to ignore this item, but the full implic

28、ations should be understood and the case carefully weighed before choosing a different course. “SHOULD NOT“ This phrase means that there may exist valid reasons in particular circumstances when the listed behavior is acceptable or even useful, but the full implications should be understood and the c

29、ase carefully weighed before implementing any behavior described with this label. “MAY“ This word or the adjective “OPTIONAL“ means that this item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because it enhances the product, for example

30、; another vendor may omit the same item. ITU-T Rec. J.176 (07/2002) 3 6 IPCablecom Management Event MIB The IPCablecom Management Event MIB MUST be implemented as defined below. PKTC-EVENT-MIB DEFINITIONS := BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32, NOTIFICATION-TYPE, BITS F

31、ROM SNMPv2-SMI TruthValue, DisplayString, DateAndTime FROM SNMPv2-TC OBJECT-GROUP, MODULE-COMPLIANCE, InetAddressType, InetAddress FROM INET-ADDRESS-MIB NOTIFICATION-GROUP FROM SNMPv2-CONF clabProjPacketCable FROM CLAB-DEF-MIB; pktcEventMib MODULE-IDENTITY LAST-UPDATED “0203080000Z“ - 03/08/02 ORGAN

32、IZATION “Packet Cable Provisioning/OSS Group“ CONTACT-INFO “Matt Osman Postal: Cable Television Laboratories, Inc. 400 Centennial Parkway Louisville, Colorado 80027-1266 U.S.A. Phone: +1 303-661-9100 Fax: +1 303-661-9199 E-mail: “ DESCRIPTION “This MIB module supplies the basic management objects fo

33、r event reporting Acknowledgements: Rick Vetter - Motorola Eugene Nechamkin - Broadcom“ := clabProjPacketCable 3 - - pktcDevEventControl OBJECT IDENTIFIER := pktcEventMib 1 pktcDevEventConfig OBJECT IDENTIFIER := pktcEventMib 2 pktcDevEventThrottle OBJECT IDENTIFIER := pktcEventMib 3 pktcDevEventLoc

34、al OBJECT IDENTIFIER := pktcEventMib 4 pktcDevEventNotify OBJECT IDENTIFIER := pktcEventMib 5 pktcDevEvNotification OBJECT IDENTIFIER := pktcEventMib 6 0 - - Event Reporting - - - Event reporting control - pktcDevEvControl OBJECT-TYPE SYNTAX INTEGER resetLog(1), setDefaults(2), 4 ITU-T Rec. J.176 (0

35、7/2002) useConfigured(3) MAX-ACCESS read-write STATUS current DESCRIPTION “This object defines actions related to the event log configuration. Setting this object to resetLog(1) empties the event log. All event log data is deleted. Setting it to setDefault(2) restores all event priorities to their f

36、actory-default reporting parameters. Setting it to useConfigured(3) reloads previously configured parameters.“ := pktcDevEventControl 1 pktcDevEvControlState OBJECT-TYPE SYNTAX INTEGER logReset(1), defaultsSet(2), userConfigured(3), processing(4) MAX-ACCESS read-only STATUS current DESCRIPTION “This

37、 object reflects the state of the device as modified in pktcDevEvControl. Processing indicates that a state change is underway. This object reflects the state of the device.“ := pktcDevEventControl 2 pktcDevEvSyslogAddressType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-write STATUS current D

38、ESCRIPTION “The type of Internet address of the Syslog server. Not all address types may be supported.“ := pktcDevEventControl 3 pktcDevEvSyslogAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-write STATUS current DESCRIPTION “The IP address of the Syslog server. If 0.0.0.0, syslog transmissio

39、n is inhibited. The use of FQDNs is syntactically allowed but it is discouraged for syslog servers since not resolving them in a timely manner may leave the device without access to the Syslog daemon during critical network events.“ := pktcDevEventControl 3 pktcDevEvSyslogUdpPort OBJECT-TYPE SYNTAX

40、Unsigned32 MAX-ACCESS read-write STATUS current DESCRIPTION “The UDP port number the syslog device is using to send requests to the syslog server.“ DEFVAL 514 := pktcDevEventControl 4 - - Event throttling control - ITU-T Rec. J.176 (07/2002) 5 pktcDevEvThrottleAdminStatus OBJECT-TYPE SYNTAX INTEGER

41、throttlingInhibited(1), dynamicThresholding(2), manualThresholding(3), eventsInhibited(4) MAX-ACCESS read-write STATUS current DESCRIPTION “Controls the transmission of traps and syslog messages with respect to the trap pacing threshold. throttlingInhibited(1) causes traps and syslog messages to be

42、transmitted without regard to the threshold settings. dynamicThresholding(2) causes trap transmission and syslog messages to be suppressed if the number of traps would otherwise exceed the threshold. manualThresholding(3) causes trap transmission to cease at the threshold, and not resume until direc

43、ted to do so. eventsInhibited(4) causes all trap transmission and syslog messages to be suppressed. A single event is always treated as a single event for threshold counting. That is, an event causing both a trap and a syslog message is still treated as a single event. Writing to this object resets

44、the thresholding state. At initial startup, this object has a default value of throttlingInhibited(1).“ DEFVAL throttlingInhibited := pktcDevEventThrottle 1 pktcDevEvThrottleInhibited OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION “If true(1), trap/inform and syslog tr

45、ansmission is currently inhibited due to thresholds and/or the current setting of pktcDevEvThrottleAdminStatus. In addition, this is set to true(1) if transmission is inhibited due to no syslog (pktcDevEvSyslogAddress) or trap/inform (pktcMtaDevSnmpEntity) destinations having been set.“ := pktcDevEv

46、entThrottle 2 pktcDevEvThrottleThreshold OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-write STATUS current DESCRIPTION “Number of trap/syslog events per pktcDevEvThrottleInterval to be transmitted before throttling. A single event is always treated as a single event for Threshold counting. That is,

47、 an event causing both a trap/inform and a syslog message is still treated as a single event. At initial startup, this object returns 2.“ DEFVAL 2 := pktcDevEventThrottle 3 6 ITU-T Rec. J.176 (07/2002) pktcDevEvThrottleInterval OBJECT-TYPE SYNTAX Integer32 (12147483647) UNITS “seconds“ MAX-ACCESS re

48、ad-write STATUS current DESCRIPTION “The interval over which the throttle threshold applies. At initial startup, this object has a value of 1.“ DEFVAL 1 := pktcDevEventThrottle 4 - - Event configuration - - - The following table configures the reporting of the various programmable - events. - pktcDe

49、vEvProgrammableTable OBJECT-TYPE SYNTAX SEQUENCE OF PktcDevEvProgrammableEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION “This table allows control of the reporting of event classes. For each event priority, a combination of logging and reporting mechanisms may be chosen. The mapping of event types to priorities is vendor-dependent. Vendors may also choose to allow the user to