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

DTS/ATTM-003011-12

General Information

• Status: Published
• Publication Date: 26-Oct-2011
• Technical Committee: ATTM AT3 - Integrated broadband cable and television networks
• Current Stage: 12 - Completion
• Due Date: 31-Oct-2011
• Completion Date: 27-Oct-2011

Standards Content (Sample)

Technical Specification
Access, Terminals, Transmission and Multiplexing (ATTM);
Integrated Broadband Cable and Television Networks;
IPCablecom 1.5;
Part 12: Management Event Mechanism

2 ETSI TS 103 161-12 V1.1.1 (2011-10)

Reference
DTS/ATTM-003011-12
Keywords
access, broadband, cable, IP, multimedia, PSTN
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
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 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 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 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.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP 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
3 ETSI TS 103 161-12 V1.1.1 (2011-10)
Contents
Intellectual Property Rights . 4
Foreword . 4
1 Scope . 6
1.1 Purpose . 6
1.2 Introduction . 6
2 References . 6
2.1 Normative references . 6
2.2 Informative references . 7
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 Void . 8
5 Background . 8
6 IPCablecom Management Event Mechanism Functional Requirements . 9
7 Management Event Reporting Mechanism . 10
7.1 Event Notification Categories . 10
7.1.1 Event ID Assignments . 10
7.2 IPCablecom Management Event Format . 10
7.3 IPCablecom Management Event Access Method . 11
7.4 Management Event ID . 11
7.5 Management Event Severities . 11
7.5.1 Changing Default Event Severities . 12
7.6 Notification Mechanism . 12
7.7 Local Log of Events . 12
7.8 Syslog . 13
7.8.1 Syslog Message Format . 13
7.8.2 PRI Part of a Syslog Packet . 13
7.8.3 MSG Part of a Syslog Packet . 13
7.9 Event Throttling . 14
7.10 Severity and Priority Definition . 15
8 IPCablecom Management Event Data Template . 16
Annex A (informative): IPCablecom-defined Provisioning Events . 17
Annex B (normative): IPCablecom-defined Powering Events . 19
Annex C (informative): Bibliography . 21
History . 22

ETSI
4 ETSI TS 103 161-12 V1.1.1 (2011-10)
Intellectual Property Rights
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 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. 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 Access, 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: "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";
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";
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 Specification";
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 Event MIB Specification";
ETSI
5 ETSI TS 103 161-12 V1.1.1 (2011-10)
Part 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
6 ETSI TS 103 161-12 V1.1.1 (2011-10)
1 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.
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 DOCSIS event reporting mechanism [i.2].
1.2 Introduction
The present document is one of two documents that together 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 IPCablecom 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 Management 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 (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 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 are 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, Transmission 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; IPCablecom 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
7 ETSI TS 103 161-12 V1.1.1 (2011-10)
2.2 Informative references
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 TS 103 161: "Access, Terminals, Transmission and Multiplexing (ATTM); Integrated
Broadband Cable and Television Networks; IPCablecom 1.5". ®
[i.2] ANSI/SCTE 23-3 2010: "DOCSIS 1.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 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 management: 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 document, 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 Management Information Protocol
CMS Call Management Server
CMTS Cable Modem Termination System
DHCP Dynamic Host Configuration Protocol
DNS Domain Name Server ®
DOCSIS Data Over Cable System Interface Specification
FQDN Fully Qualified Domain Name
IP Internet Protocol
IPSec Internet Protocol Security
MGC Media 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.
ETSI
8 ETSI TS 103 161-12 V1.1.1 (2011-10)
TFTP 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 Internet 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 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 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 document 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 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 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. It is possible that IPCablecom elements implement reporting methods specified in ®
DOCSIS MIBs, 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
9 ETSI TS 103 161-12 V1.1.1 (2011-10)
6 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 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 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 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 identifiable to the point of origin such as a specific endpoint on an MTA.
8) The capability should exist to map event IDs to priorities in the back office.
9) IPCablecom elements must send a timestamp with each management event.
10) IPCablecom elements must send a Severity level with each management event. Elements may use the Severity
level within the network element to determine the order in which events are sent in compliance with Telcordia
GR 474's clause 2.2.3 and clause 7.10 of the present document.
11) The severity level of management events generated by the network element must be modifiable on the
IPCablecom element by the management system.
12) The display string of management events generated by the IPCablecom element must be modifiable on the
network element by the management system.
13) A default notification mechanism must be associated with each event.
14) IPCablecom-specific event definitions should contain a NULL display string in order to reduce memory
requirements on the IPCablecom element.
15) Event definitions must contain a display string.
16) Vendor-specific event definitions may contain a NULL display string in order to reduce memory requirements
on the IPCablecom element.
17) Event throttling mechanism must be configurable by the management system.
18) All events are uniquely identified by vendor through the IANA assigned enterprise number. IPCablecom
events use the IANA assigned enterprise number.
19) An event must provide the Event ID of the event.
ETSI
10 ETSI TS 103 161-12 V1.1.1 (2011-10)
7 Management Event Reporting Mechanism
The Management Event Mechanism and the associated Management Event MIB must be implemented on the MTA.
The Management Event Mechanism and the associated Management Event Mechanism MIB may be implemented on
any IPCablecom element such as the CMS, MGC, and others.
7.1 Event Notification Categories
All events delivered by (event mechanism document) fit into two main categories:
• IPCablecom-specific
• Vendor-specific
IPCablecom-specific events are defined in the present document and referenced by concerned specifications whereas
vendor-specific events are left to vendor implementation and are out of scope of the present document.
Each Event has an associated Event ID as described in the next clause. IPCablecom-specific events are identical if their
EventIDs are identical. The IPCablecom-specific EventIDs are specified by the IPCablecom Specifications, including
the present document. For each particular vendor, Vendor-specific events are identical if the corresponding Event IDs
are identical. The Vendor-specific EventIDs are defined by particular vendors and is out of scope for the present
document.
EXAMPLE: Two or more IPCablecom Events with the same Event ID (say 4000950100) are considered to be
identical irrespective of the description or other parameters.
Two or more Vendor-Specific Events, from the same vendor (say XYZ) with the same Event ID
(say 10) are considered to be identical irrespective of the description or other parameters.
For identical events occurring consecutively, the MTA may choose to store only a single event. In such a case, the event
description recorded must reflect the most recent event.
Aside from the procedures defined in the present document, event recording must conform to the requirements of [1]
and Event Descriptions must not be longer than 127 characters.
7.1.1 Event ID Assignments
• The EventID is a 32-bit unsigned integer.
• IPCablecom-specific EventIDs must be defined in the range of 0x80000000 (decimal 2 147 483 648) to
0xFFFFFFFF (decimal 4 294 967 295).
• Vendor-specific EventIDs must be defined in the range of 0x00000000 (decimal 0) to 0x7FFFFFFF (decimal
2 147 483 647).
• Vendor-specific EventIDs must be unique for a particular vendor's enterprise number in sysObjectID.
7.2 IPCablecom Management Event Format
The format of an IPCablecom Management Event is made up of the following information:
• Event Counter - indicator of event sequence
• Event Time - time of occurrence
• Event severity - severity of condition as defined in clause 7.5
• Event Enterprise number - Vendor specific enterprise number
• Event ID - determines event function
ETSI
11 ETSI TS 103 161-12 V1.1.1 (2011-10)
• Event Text - describes the event in human readable form
• FQDN/Endpoint ID - describes the device FQDN and the specific endpoint associated with the event
7.3 IPCablecom Management Event Access Method
The IPCablecom event access method is defined through the use of SNMPv3 in the case of local log access and trap or
inform access. The SYSLOG uses UDP packets to convey the event data.
For local event log access, an EMS may send SNMP GET, GET-NEXT or GET-BULK requests to the IPCablecom
element, accessing rows of the local event table. Each row
...