ETSI TS 103 161-20-2011 Access Terminals Transmission and Multiplexing (ATTM) Integrated Broadband Cable and Television Networks IPCablecom 1 5 Part 20 Management Event MIB Specifi_1.pdf

《ETSI TS 103 161-20-2011 Access Terminals Transmission and Multiplexing (ATTM) Integrated Broadband Cable and Television Networks IPCablecom 1 5 Part 20 Management Event MIB Specifi_1.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 103 161-20-2011 Access Terminals Transmission and Multiplexing (ATTM) Integrated Broadband Cable and Television Networks IPCablecom 1 5 Part 20 Management Event MIB Specifi_1.pdf（19页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 103 161-20 V1.1.1 (2011-04)Technical Specification Access, Terminals, Transmission and Multiplexing (ATTM); Integrated Broadband Cable and Television Networks; IPCablecom 1.5;Part 20: Management Event MIB SpecificationETSI ETSI TS 103 161-20 V1.1.1 (2011-04)2Reference DTS/ATTM-003011-20 Key

2、words access, broadband, cable, IP, multimedia, PSTN ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important n

3、otice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Porta

4、ble Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information

5、 on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may

6、 be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2011. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Ma

7、rks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM

8、and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 103 161-20 V1.1.1 (2011-04)3Contents Intellectual Property Rights 4g3Foreword . 4g31 Scope 6g31.1 Organization of document 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 7g33 Defin

9、itions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Void 7g35 IPCablecom Management Event MIB . 8g3Annex A (informative): Bibliography . 18g3History 19g3ETSI ETSI TS 103 161-20 V1.1.1 (2011-04)4Intellectual Property Rights IPRs essential or potentially essential to the present

10、document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respec

11、t of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the e

12、xistence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI Technical Committee Access, Terminals, Transmission and Multip

13、lexing (ATTM). The present document is part 20 of a multi-part deliverable covering Access, Terminals, Transmission and Multiplexing (ATTM); Integrated Broadband Cable and Television Networks; IPCablecom 1.5, as identified below: Part 1: “Overview“; Part 2: “Architectural framework for the delivery

14、of time critical services over cable Television networks using cable modems“; Part 3: “Audio Codec Requirements for the Provision of Bi-Directional Audio Service over Cable Television Networks using Cable Modems“; Part 4: “Network Call Signalling Protocol“; Part 5: “Dynamic Quality of Service for th

15、e Provision of Real Time Services over Cable Television Networks using Cable Modems“; Part 6: “Event Message Specification“; Part 7: “Media Terminal Adapter (MTA) Management Information Base (MIB)“; Part 8: “Network Call Signalling (NCS) MIB Requirements“; Part 9: “Security“; Part 10: “Management In

16、formation Base (MIB) Framework“; Part 11: “Media Terminal Adapter (MTA) device provisioning“; Part 12: “Management Event Mechanism“; Part 13: “Trunking Gateway Control Protocol - MGCP option“; Part 14: “Embedded MTA Analog Interface and Powering Specification“; Part 15 “Analog Trunking for PBX Speci

17、fication“; Part 16: “Signalling for Call Management Server“; Part 17: “CMS Subscriber Provisioning Specification“; Part 18: “Media Terminal Adapter Extension MIB“; Part 19: “IPCablecom Audio Server Protocol Specification - MGCP option“; Part 20: “Management Event MIB Specification“; ETSI ETSI TS 103

18、 161-20 V1.1.1 (2011-04)5Part 21: “Signalling Extension MIB Specification“. NOTE 1: Additional parts may be proposed and will be added to the list in future versions. NOTE 2: The choice of a multi-part format for this deliverable is to facilitate maintenance and future enhancements. ETSI ETSI TS 103

19、 161-20 V1.1.1 (2011-04)61 Scope The Management Event MIB provides a common data and format definition for events (informative, alarm, etc.). It also specifies by what means events are transmitted. Use of a common event mechanism facilitates management of the MTA in a multi-vendor environment and pr

20、ovides a standard means to implement IPCablecom specified events. The present document describes an SNMP MIB in SMIv2, to support the management event mechanism as described in 1. It is intended to be implemented in the MTA and management devices. 1.1 Organization of document The Management Event MI

21、B defined in the present document provides a set of objects required for the management of IPCablecom-compliant Multimedia Terminal Adapter (MTA) devices. The mechanisms to control the event reporting are defined in the present document. This MIB itself is structured as six groups: Management inform

22、ation that controls the event reporting (pktcDevEventControl). Management information that configures the reporting of the various programmable events (pktcDevEventConfig). Management information that configures the event throttling control (pktcDevEventThrottle). Management information that configu

23、res that allows the retrieval of events via SNMP (pktcDevEventLocal). Management information that specifies the information sent in traps and informs (pktcDevEventNotify). Management information that defines the trap and inform messages (pktcDevEventNotification). 2 References References are either

24、specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which are

25、not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced do

26、cuments are necessary for the application of the present document. 1 PacketCable 1.5 PKT-SP-MEM1.5-I02-050812: “Management Event Mechanism“, August 12, 2005, Cable Television Laboratories, Inc. 2 Void. 3 Void. 4 Void. ETSI ETSI TS 103 161-20 V1.1.1 (2011-04)75 Void. 6 Void. 7 Void. 2.2 Informative r

27、eferences The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. i.1 ETSI TR 102 473: “Digital Video Broadcasting (DVB); IP Datacast over DVB-H: Use Cases and Services“. i.2 ETSI TR 102 469:

28、“Digital Video Broadcasting (DVB); IP Datacast over DVB-H: Architecture“. i.3 PacketCable 1.5 MTA MIB, PKT-SP-MIB-MTA1.5-I01-050128, January 28, 2005, Cable Television Laboratories, Inc. i.4 PacketCable 1.5 Signaling MIB, PKT-SP-MIB-SIG1.5-I01-050128, January 28, 2005, Cable Television Laboratories,

29、 Inc. i.5 PacketCable 1.5 Network-Based Call Signaling Protocol Specification, PKT-SP-NCS1.5-I02-050812, August 12, 2005, Cable Television Laboratories, Inc. i.6 PacketCable 1.5 Security Specification, PKT-SP-SEC1.5-I01-050128, January 28, 2005, Cable Television Laboratories, Inc. 3 Definitions and

30、abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: endpoint: Terminal, Gateway or MCU 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: FQDN Fully Qualified Domain Name IANA Internet Assigned

31、 Numbers Authority IP Internet Protocol MIB Management Information Base MTA Media Terminal Adapter SNMP Simple Network Management Protocol 4 Void ETSI ETSI TS 103 161-20 V1.1.1 (2011-04)85 IPCablecom Management Event MIB The IPCablecom 1.5 Management Event MIB MUST be implemented as defined below. P

32、KTC-EVENT-MIB DEFINITIONS := BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, NOTIFICATION-TYPE, BITS FROM SNMPv2-SMI DateAndTime FROM SNMPv2-TC clabProjPacketCable FROM CLAB-DEF-MIB SnmpAdminString FROM SNMP-FRAMEWORK-MIB OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP FROM SNMPv2-CONF i

33、fPhysAddress FROM IF-MIB InetAddressType, InetAddress, InetPortNumber FROM INET-ADDRESS-MIB ; pktcEventMib MODULE-IDENTITY LAST-UPDATED “200508120000Z“ - August 12, 2005 ORGANIZATION “Cable Television Laboratories, Inc“ CONTACT-INFO “Sumanth Channabasappa Postal: Cable Television Laboratories, Inc.

34、858 Coal Creek Circle Louisville, Colorado 80027 U.S.A. Phone: +1 303-661-9100 Fax: +1 303-661-9199 E-mail: “ DESCRIPTION “This MIB module supplies the basic management objects for event reporting Acknowledgements: Eugene Nechamkin - Broadcom Corp John Berg - CableLabs, Inc. Kevin Marez - Motorola,

35、Inc. Satish Kumar - Texas Instruments Venkatesh Sunkad - CableLabs, Inc.“ := clabProjPacketCable 3 - - pktcDevEventControl OBJECT IDENTIFIER := pktcEventMib 1 pktcDevEventThrottle OBJECT IDENTIFIER := pktcEventMib 2 pktcDevEventStatus OBJECT IDENTIFIER := pktcEventMib 3 pktcDevEventDescr OBJECT IDEN

36、TIFIER := pktcEventMib 4 pktcDevEventLog OBJECT IDENTIFIER := pktcEventMib 5 pktcDevEvNotification OBJECT IDENTIFIER := pktcEventMib 6 - - - Event Reporting control objects - pktcDevEvControl OBJECT-TYPE SYNTAX BITS resetEventLogTable(0), resetEventDescrTable(1) MAX-ACCESS read-write STATUS current

37、DESCRIPTION “This MIB object defines the actions related to the event log configuration. The MTA MUST take the appropriate action whenever a bit is set to a value of 1. Setting the resetEventLogTable(0) bit to a value of 1 clears the entire event log (Deletes all entries in pktcDevEventLogTable). ET

38、SI ETSI TS 103 161-20 V1.1.1 (2011-04)9Setting resetEventDescrTable(1) to a value of 1 resets the pktcDevEventDescrTable to the factory default values. Setting a control bit to a value of 0 MUST not result in any action. Reading this MIB object MUST always return 00.“ := pktcDevEventControl 1 pktcDe

39、vEvSyslogAddressType OBJECT-TYPE SYNTAX InetAddressType MAX-ACCESS read-write STATUS current DESCRIPTION “This MIB Object defines the address type of the Syslog server. IPCablecom devices implementing this MIB MUST support an InetAddressType of ipv4(1). IPCablecom devices MAY optionally implement ot

40、her address types. If an unsupported InetAddressType is used to set this object, the IPCablecom device MUST reject it and report an SNMP error stating wrong value. If an SNMP SET results in a type that does not match the value contained in the MIB Object pktcDevEvSyslogAddress, the IPCablecom device

41、 MUST reject the SNMP SET with an inconsistent value error.“ := pktcDevEventControl 2 pktcDevEvSyslogAddress OBJECT-TYPE SYNTAX InetAddress MAX-ACCESS read-write STATUS current DESCRIPTION “This MIB Object contains the IP address of the Syslog server. If this is set to either 0.0.0.0 or 255.255.255.

42、255 the device MUST inhibit syslog transmission. The use of FQDNs is syntactically allowed, but discouraged since a failure to resolve them in a timely manner may leave the device without access to the Syslog daemon during critical network events. The type of address this object represents is define

43、d by the MIB Object pktDevEvSyslogAddressType. If an SNMP SET results in a type that does not match that indicated by the MIB Object pktcDevEvSyslogAddressType, the IPCablecom device MUST reject the SNMP SET with an inconsistent value error.“ := pktcDevEventControl 3 pktcDevEvSyslogUdpPort OBJECT-TY

44、PE SYNTAX InetPortNumber MAX-ACCESS read-write STATUS current DESCRIPTION “This MIB Object contains the UDP Port Number of the Syslog Server. The IPCablecom device must send the Syslog messages to this port on the Syslog Server.“ DEFVAL 514 := pktcDevEventControl 4 - - Event throttling control - pkt

45、cDevEvThrottleAdminStatus OBJECT-TYPE SYNTAX INTEGER unconstrained(1), maintainBelowThreshold(2), stopAtThreshold(3), inhibited(4) ETSI ETSI TS 103 161-20 V1.1.1 (2011-04)10 MAX-ACCESS read-write STATUS current DESCRIPTION “This MIB Object controls the throttling of the transmitted messages upon gen

46、eration of an event (SNMP/Syslog). A value of unconstrained(1) causes event messages to be transmitted without regard to the threshold settings. A value of maintainBelowThreshold(2) causes event messages to be suppressed if the number of transmissions would otherwise exceed the threshold. A value of

47、 stopAtThreshold(3) causes event message transmission to cease at the threshold, and not resume until directed to do so. A value of inhibited(4) causes all event message Transmission to be suppressed. An event causing both an SNMP and a Syslog message is still treated as a single event. Writing to t

48、his object resets the thresholding state. Refer to MIB Objects pktcDevEvThrottleThreshold and pktcDevEvThrottleInterval for information on throttling.“ DEFVAL unconstrained := pktcDevEventThrottle 1 pktcDevEvThrottleThreshold OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-write STATUS current DESCRIPTION “This MIB Object contains the number of events per pktcDevEvThrottleInterval to be transmitted before throttling. An event causing both a SNMP and a syslog message is still treated as a single event.“ DEFVAL 2 := pktcDevEventThrottle 2 p