1、 ETSI TS 103 161-12 V1.1.1 (2011-10) Access, Terminals, Transmission and Multiplexing (ATTM); Integrated Broadband Cable and Television Networks; IPCablecom 1.5; Part 12: Management Event Mechanism Technical Specification ETSI ETSI TS 103 161-12 V1.1.1 (2011-10)2Reference DTS/ATTM-003011-12 Keywords
2、 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 notice
3、 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 Portable D
4、ocument 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 on t
5、he 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 be r
6、eproduced 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, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the be
7、nefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 103 161-12 V1.1.1 (2011-10)3Contents Intellectual Property Ri
8、ghts 4g3Foreword . 4g31 Scope 6g31.1 Purpose . 6g31.2 Introduction 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 7g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Void 8g35 Background 8g36 IPCablecom Management Event Mechanism Functiona
9、l Requirements . 9g37 Management Event Reporting Mechanism 10g37.1 Event Notification Categories 10g37.1.1 Event ID Assignments 10g37.2 IPCablecom Management Event Format 10g37.3 IPCablecom Management Event Access Method . 11g37.4 Management Event ID 11g37.5 Management Event Severities 11g37.5.1 Cha
10、nging Default Event Severities . 12g37.6 Notification Mechanism . 12g37.7 Local Log of Events . 12g37.8 Syslog . 13g37.8.1 Syslog Message Format 13g37.8.2 PRI Part of a Syslog Packet 13g37.8.3 MSG Part of a Syslog Packet 13g37.9 Event Throttling . 14g37.10 Severity and Priority Definition . 15g38 IP
11、Cablecom Management Event Data Template . 16g3Annex A (informative): IPCablecom-defined Provisioning Events . 17g3Annex B (normative): IPCablecom-defined Powering Events . 19g3Annex C (informative): Bibliography . 21g3History 22g3ETSI ETSI TS 103 161-12 V1.1.1 (2011-10)4Intellectual Property Rights
12、IPRs essential or potentially essential to the present 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
13、 potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/ipr.etsi.org). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI
14、. No guarantee can be given as to the existence 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 Acc
15、ess, Terminals, Transmission and Multiplexing (ATTM). The present document is part 12 of a multi-part IPCablecom 1.5 deliverable covering the Digital Broadband Cable Access to the Public Telecommunications Network; IP Multimedia Time Critical Services, as identified below: Part 1: “Overview“; Part 2
16、: “Architectural framework for the delivery 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“
17、; Part 5: “Dynamic Quality of Service for the 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“;
18、Part 9: “Security“; Part 10: “Management Information 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 Specificati
19、on“; Part 15 “Analog Trunking for PBX Specification“; 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
20、 Event MIB Specification“; ETSI ETSI TS 103 161-12 V1.1.1 (2011-10)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 maintenanc
21、e and future enhancements. ETSI ETSI TS 103 161-12 V1.1.1 (2011-10)61 Scope 1.1 Purpose The present document defines the Management Event Mechanism that IPCablecom elements can use to report asynchronous events that indicate malfunction situations and notification about important non-fault situation
22、. Events are defined in the present document as conditions requiring the reporting of information to management systems and/or local log. A goal of IPCablecom is to maintain consistency with the DOCSISevent reporting mechanism i.2. 1.2 Introduction The present document is one of two documents that t
23、ogether define a framework for reporting Management Events in the IPCablecom architecture. The present document defines the general event reporting mechanism and framework. The mechanism consists of a set of protocols and interfaces that can be used by individual elements and components in the IPCab
24、lecom architecture. The present document defines how the SNMPv3 transport protocol, SYSLOG, local log, and the IPCablecom Management Event MIB are used to carry management event information to an event management system. This management event mechanism is further defined and supported by the Managem
25、ent Event Mechanism MIB as specified in 1 and i.7 if the latter is implemented by the MTA. Consequently, each reference to the Management Event MIB in the present document will correspond to the MIB as defined either in 1, or alternatively, in 1 and i.7. 2 References References are either specific (
26、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 not found
27、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 documents a
28、re necessary for the application of the present document. 1 ETSI TS 103 161-20: “Access, Terminals, Transmission and Multiplexing (ATTM); Integrated Broadband Cable and Television Networks; IPCablecom 1.5; Part 20: Management Event MIB Specification“. 2 ETSI TS 103 161-11: “Access, Terminals, Transm
29、ission and Multiplexing (ATTM); Integrated Broadband Cable and Television Networks; IPCablecom 1.5; Part 11: Media Terminal Adapter (MTA) device provisioning“. 3 ETSI TS 103 161-14: “Access, Terminals, Transmission and Multiplexing (ATTM); Integrated Broadband Cable and Television Networks; IPCablec
30、om 1.5; Part 14: Embedded MTA Analog Interface and Powering Specification“. 4 IETF RFC 3413: “Simple Network Management Protocol (SNMP) Applications“, December 2002. 5 IETF RFC 3164: “The BSD Syslog Protocol“, August 2001. ETSI ETSI TS 103 161-12 V1.1.1 (2011-10)72.2 Informative references The follo
31、wing 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 TS 103 161: “Access, Terminals, Transmission and Multiplexing (ATTM); Integrated Broadband Cable and Television Networks; IPCablecom 1.5
32、“. i.2 ANSI/SCTE 23-3 2010: “DOCSIS1.1 Part 3: Operations Support System Interface“. i.3 ETSI TS 103 161-2: “Access, Terminals, Transmission and Multiplexing (ATTM); Integrated Broadband Cable and Television Networks; IPCablecom 1.5; Part 2: Architectural framework for the delivery of time critical
33、services over Cable Television Networks using Cable Modems“. i.4 Telcordia GR-474: “Network Maintenance: Alarm and Control for Network Elements“. i.5 ITU-T Recommendation M.3100: “Generic Network Information Model“, 1995. i.6 ITU-T Recommendation X.733: “Open Systems Interconnection - Systems manage
34、ment: Alarm reporting function“, 1992. i.7 IETF RFC 5428: “Management Event Management Information Base (MIB) for PacketCable- and IPCablecom-Compliant Devices“, April 2009. i.8 IETF RFC 2573: “SNMP Applications“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present docume
35、nt, the following terms and definitions apply: network management: functions related to the management of data across the network 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: BSD Berkeley Software Distribution CDR Call Detail Record CMIP Common Manag
36、ement Information Protocol CMS Call Management Server CMTS Cable Modem Termination System DHCP Dynamic Host Configuration Protocol DNS Domain Name Server DOCSISData Over Cable System Interface Specification FQDN Fully Qualified Domain Name IP Internet Protocol IPSec Internet Protocol Security MGC Me
37、dia Gateway Controller MIB Management Information Base MSO Multi-System Operator MTA Media Terminal Adapter OSS Operations Systems Support PSTN Public Switched Telephone Network RKS Record Keeping Server SNMP Simple Network Management Protocol SYSLOG System Log NOTE: Used to grant Kerberos tickets.
38、ETSI ETSI TS 103 161-12 V1.1.1 (2011-10)8TFTP Trivial File Transfer Protocol TGS Ticket Granting Server TL1 Transaction Language1 UDP User Datagram Protocol ID Identifier PRI Primary Rate Interface MSG Message Generation PBX Private Branch Exchange RADIUS Remote Access Dial-In User Service IANA Inte
39、rnet Assigned Number Association EMS Element Management System OSI Open Systems Interconnection UTC Universal Coordinated Time ACK Acknowledgement PID Packet identifier SRV Service Record AC Access Class KDC Key Distribution Center AS Access Server AP Access Point UPS Uninterruptible Power Source 4
40、Void 5 Background The IPCablecom architecture is an end-end broadband architecture that supports voice, video, and other multimedia services. The individual components that compose the IPCablecom architecture are defined in i.3. The OSS back office contains business, service, and network management
41、components supporting the core business processes. The IPCablecom set of specifications defines a limited set of OSS functional components and interfaces to support MTA Device Provisioning 2 Event Messaging to carry billing information i.1, and the Management Event Mechanism defined in the present d
42、ocument to carry fault and other data. In addition to the Management Event Mechanism, the IPCablecom architecture supports the following additional reporting mechanism: IPCablecom Events Messages for billing information i.1. This reporting mechanism uses the RADIUS transport protocol, a pre-defined
43、set of Event Message attributes (e.g. BillingCorrelationID, CalledPartyNumber, TrunkGroupID, etc.), and the IPCablecom Event Messages data format to carry per-call information between IPCablecom network elements (CMS, CMTS, MGC) and a Record Keeping Server (RKS). For each call, the RKS combines all
44、associated Event Messages into a single Call Detail Record (CDR) which may be sent to a back office billing, fraud detection or other system. Vendor-proprietary data attributes may be included along with the IPCablecom-defined set of attributes in an IPCablecom Event Message. Other Reporting Methods
45、. It is possible that IPCablecom elements implement reporting methods specified in DOCSISMIBs, IPCablecom MIBs or other standard MIBs. It is possible that IPCablecom elements implement methods such as SNMPv3, CMIP, TL1. These event-reporting mechanisms are not defined in the present document. ETSI E
46、TSI TS 103 161-12 V1.1.1 (2011-10)96 IPCablecom Management Event Mechanism Functional Requirements The functional requirements addressed by the Message Event Mechanism specification are as follows: 1) The event report must provide either the FQDN or IP address of the reporting device. NOTE 1: It is
47、highly recommended that the device provide the FQDN. 2) The IPCablecom management event reporting mechanism must support 2 types of events: IPCablecom-specific and Vendor-specific. 3) The management event reporting mechanism must support the IPCablecom 1.5 Management Event MIB 1. All the events that
48、 can be generated by the IPCablecom device must be included in the MIB table pktcDevEventDescrTable. 4) The IPCablecom management event reporting mechanism must support the BSD syslog protocol 5. 5) The management event reporting mechanism must support SNMPv3/v2c Traps and SNMPv3/v2c Informs. 6) The
49、 management event reporting mechanism must comply with SNMP Applications 4 since these MIBs provide the mechanism for distributing SNMPv3 traps and informs. The elements must support a mechanism to allow the element management system to map each event to a reported notification mechanism(s). For example: none, local, SYSLOG, SNMPv3/v2c Trap, SNMPv3/v2c inform. NOTE 2: Refer to the IPCablecom 1.5 MTA Device Provisioning Specification 2 for more information about SNMP configuration. 7) Each event must be uniquely i
