ANSI SCTE 165-16 pdf free download

ANSI SCTE 165-16 pdf free download.IPCablecom 1.5 Part 16: Management Event Mechanism.
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: 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 ‘pktcDevEventDescrTahle’.
4. The IPCahlecom management event reporting mechanism MUST support the BSD syslog protocol 181.
5. The management event reporting mechanism MUST support SNMPv3/v2c Traps and SNMPv3/v2c In forms.
6. The management event reporting mechanism MUST comply with SNMP Applications 171 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: Refer to the IPCablecom 1.5 MTA Device Provisioning Specification [3] 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. lPCahlecom 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 Beilcore GR474’s Section 2.2.3 and Section 7.10 of this document.
11. The severity level of management events generated by the network element MUST be modifiable on the IPCablecorn 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 IPCahlecorn 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 lANA assigned enterprise number. lPCablecom events use the CableLabs lANA assigned enterprise number.
19. An event MUST provide the Event ID of the event.
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-specitic
• Vendor-specific
IPCablecom-specific events are defined in this document and referenced by concerned specifications whereas vendor-specific events are left to vendor implementation and are out of scope of this specification.
Each Event has an associated Event ID as described in the next sub-section. IPCablecom-Specific events are identical if their EventlDs are identical. The IPCablecom-Specific EventlDs are specified by the IPCablecom Specifications, including this specification. For each particular vendor, Vendor-specific events are identical if the corresponding Event IDs are identical. The Vendor-specific EventlDs are defined by particular vendors and is out of scope for this specification.ANSI SCTE 165-16 pdf download.