Society of Cable Telecommunications Engineers

Similar documents
ENGINEERING COMMITTEE Hybrid Management Sub-Layer Subcommittee AMERICAN NATIONAL STANDARD

Network Operations Subcommittee AMERICAN NATIONAL STANDARD ANSI/SCTE

Network Operations Subcommittee AMERICAN NATIONAL STANDARD ANSI/SCTE

ENGINEERING COMMITTEE Data Standards Subcommittee AMERICAN NATIONAL STANDARD

ENGINEERING COMMITTEE Digital Video Subcommittee

ENGINEERING COMMITTEE Digital Video Subcommittee SCTE Digital Program Insertion Advertising Systems Interfaces.

ANSI/SCTE

AMERICAN NATIONAL STANDARD

AMERICAN NATIONAL STANDARD

ANSI/SCTE

ANSI/SCTE

Network Operations Subcommittee AMERICAN NATIONAL STANDARD

SNMPv2 Object Descriptions

ENGINEERING COMMITTEE Digital Video Subcommittee SCTE Digital Program Insertion Advertising Systems Interfaces. Part 4

NOTICE. (Formulated under the cognizance of the CTA R7 Home Networks Committee.)

The Marway Chassis MIB. Status of this Memo. This document specifies a proprietary MIB module of Marway Power Solutions.

AMERICAN NATIONAL STANDARD

NAFEM-UTILITYMANAGEMENT-MIB DEFINITIONS ::= BEGIN. -- From file: "utility-management.mib" IMPORTS

ANSI/SCTE

The Marway Sensor MIB. Status of this Memo. This document specifies a proprietary MIB module of Marway Power Solutions.

Cable Facility Classification Definitions and Requirements

Category: Standards Track September MIB Textual Conventions for Uniform Resource Identifiers (URIs)

ANSI/CEA Standard. Modular Communications Interface for Thermostat Message Set ANSI/CEA

Feb :33 draft-glenn-id-sensor-alert-mib-01.txt Page 1

Author of previous version: B. Stewart November 2000

Network Working Group. Category: Standards Track June Protocol Independent Multicast (PIM) Bootstrap Router MIB

Brief Introduction to the Internet Standard Management Framework

ANSI/CEA Standard. Fiber-Optic Channel Specification

INTERNATIONAL STANDARD

SOCIETY OF CABLE TELECOMMUNICATIONS ENGINEERS, INC.

Request for Comments: 2493 Category: Standards Track January 1999

NOTICE. (Formulated under the cognizance of the CTA R4.8 DTV Interface Subcommittee.)

INTERNATIONAL STANDARD

Avaya Inc. K.C. Norseth L-3 Communications December 2002

Internet Engineering Task Force (IETF) Request for Comments: 5907 Category: Standards Track ISSN: B. Haberman, Ed.

ANSI/CEA Standard. Tunneling Device Area Network Protocols over Internet Protocol Channels ANSI/CEA-852-C

TDX - SNMP Revision 02-01

Category: Informational 1 April Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2

Internet Engineering Task Force (IETF) Category: Standards Track. J. Quittek. NEC Europe Ltd. October 2012

Category: Standards Track August 2005

Lecture 5: Foundation of Network Management

Request for Comments: October 1996

ENGINEERING COMMITTEE Network Operations Subcommittee SCTE STANDARD SCTE

NOTICE. (Formulated under the cognizance of the CTA R7 Home Networks Committee.)

Pica8 private MIB. March, Version: 2.

ITU-T Recommendation Q

CEA Standard. Control Networking Protocol Specification Part 5: Implementation- Application-Layer-Guidelines CEA-709.5

Network Working Group. Category: Standards Track Independent Consultant M. Ellison, Ed. Ellison Software Consulting, Inc.

Network Working Group Request for Comments: 4131 Category: Standards Track Toshiba E. Cardona, Ed. CableLabs A. Katsnelson September 2005

Network Working Group. Intended status: Standards Track. January 15, 2010

Network Working Group. Category: Standards Track Tohoku University K. Nagami INTEC NetCore Inc. S. Gundavelli Cisco Systems Inc.

TCG. SNMP MIB for TPM-Based Attestation

NAFEM-INVENTORY-MANAGEMENT-MIB DEFINITIONS ::= BEGIN. -- From file: "inventory-management.mib" IMPORTS -- enterprises FROM RFC1155-SMI

Internet Engineering Task Force (IETF) B. Claise Cisco Systems, Inc. G. Muenz Technische Universitaet Muenchen April 2010

ANSI/CEA Standard. Free Topology Twisted-Pair Channel Specification ANSI/CEA R-2015

ENGINEERING COMMITTEE Data Standards Subcommittee AMERICAN NATIONAL STANDARD ANSI/SCTE IPCablecom 1.5 Management Event Mechanism

Category: Standards Track December 1998

Request for Comments: Cisco Systems, Inc. M. Rose Dover Beach Consulting, Inc. S. Waldbusser International Network Services January 1996

Request for Comments: 5488 Category: Standards Track. Network Mobility (NEMO) Management Information Base

VCE Vision Intelligent Operations Version Integration Guide for SNMP

NOTICE. (Formulated under the cognizance of the CTA R7 Home Networks Committee.)

Network Working Group. Category: Standards Track June 2007

PUBLICLY AVAILABLE SPECIFICATION PRE-STANDARD

NAFEM-SECURITY-MIB DEFINITIONS ::= BEGIN. -- From file: "security.mib" IMPORTS. NafemDateTime, NafemChoice, NafemTime, NafemInterval,

SERIES H: AUDIOVISUAL AND MULTIMEDIA SYSTEMS Infrastructure of audiovisual services Coding of moving video

Intended status: Standards Track Expires: April 27, 2015 Q. Zhao Huawei Technology D. King Old Dog Consulting J. Hardwick Metaswitch October 24, 2014

Network Working Group. Effective Software December 2005

NAFEM Data Protocol Standard

Category: Standards Track March 1994

Lecture 18: Network Management

ANSI/SCTE

PUBLICLY AVAILABLE SPECIFICATION

NAFEM-ADMINISTRATION-MIB DEFINITIONS ::= BEGIN. -- From file: "administration.mib" IMPORTS. admininfo, admincommunity,

Internet Engineering Task Force (IETF) Category: Standards Track. NEC Europe Ltd. M. Chandramouli Cisco Systems, Inc. May 2013

INTERNATIONAL STANDARD

JEDEC SOLID STATE TECHNOLOGY ASSOCIATION

Intended Status: Proposed Standard. Proxy Mobile IPv6 Management Information Base <draft-ietf-netlmm-pmipv6-mib-03.txt>

PLANEAMENTO E GESTÃO DE REDES INFORMÁTICAS COMPUTER NETWORKS PLANNING AND MANAGEMENT

Internet Engineering Task Force (IETF) Category: Standards Track

Internet Engineering Task Force (IETF)

Request for Comments: Oversi O. Nicklass, Ed. RADVISION May Definitions of Textual Conventions for Pseudowire (PW) Management

This document is a preview generated by EVS

INTERNATIONAL STANDARD

Internet Engineering Task Force (IETF) Category: Standards Track. S. Gundavelli Cisco R. Wakikawa Toyota ITC May 2012

INTERNATIONAL STANDARD

This document is a preview generated by EVS

Specification for TRAN Layer Services

PROPOSED DRAFT FOR TRIAL USE AND DISCUSSION ONLY secretariat PROPOSED DRAFT AES24-2-TU 99/02/2818:41

INTERNATIONAL STANDARD

Feb :33 draft-glenn-id-notification-mib-04.txt Page 1

IETF TRUST. Legal Provisions Relating to IETF Documents. February 12, Effective Date: February 15, 2009

NAFEM-BULK-TRANSFER-MIB DEFINITIONS ::= BEGIN. -- From file: "bulk-transfer.mib" IMPORTS. NafemDateTime, NafemChoice, NafemInterval,

Category: Standards Track July 2002

ANSI/CEA Standard. Control Network Protocol Specification ANSI/CEA D

Network Working Group Request for Comments: 4070 Category: Standards Track PESA Switching Systems May 2005

Network Operations Subcommittee AMERICAN NATIONAL STANDARD ANSI/SCTE

INTERNATIONAL STANDARD

INTERNATIONAL STANDARD

RADIUS Working Group Bernard Aboba. Category: Standards Track <draft-ietf-radius-auth-clientmib-01.txt> 12 February 1998

INTERNATIONAL STANDARD

Transcription:

Society of Cable Telecommunications Engineers ENGINEERING COMMITTEE HFC Management Subcommittee AMERICAN NATIONAL STANDARD ANSI/SCTE 84-1 2009 HMS Common Inside Plant Management Information Base (MIB) Part 1: SCTE-HMS-HE-COMMON-MIB

NOTICE The Society of Cable Telecommunications Engineers (SCTE) Standards are intended to serve the public interest by providing specifications, test methods and procedures that promote uniformity of product, interchangeability and ultimately the long term reliability of broadband communications facilities. These documents shall not in any way preclude any member or nonmember of SCTE from manufacturing or selling products not conforming to such documents, nor shall the existence of such standards preclude their voluntary use by those other than SCTE members, whether used domestically or internationally. SCTE assumes no obligations or liability whatsoever to any party who may adopt the Standards. Such adopting party assumes all risks associated with adoption of these Standards or Recommended Practices, and accepts full responsibility for any damage and/or claims arising from the adoption of such Standards or Recommended Practices. Attention is called to the possibility that implementation of this standard may require use of subject matter covered by patent rights. By publication of this standard, no position is taken with respect to the existence or validity of any patent rights in connection therewith. SCTE shall not be responsible for identifying patents for which a license may be required or for conducting inquires into the legal validity or scope of those patents that are brought to its attention. Patent holders who believe that they hold patents which are essential to the implementation of this standard have been requested to provide information about those patents and any related licensing terms and conditions. Any such declarations made before or after publication of this document are available on the SCTE web site at http://www.scte.org. All Rights Reserved Society of Cable Telecommunications Engineers, Inc. 2009 140 Philips Road Exton, PA 19341 i

CONTENTS SCOPE... 1 COPYRIGHT... 1 NORMATIVE REFERENCE... 1 INFORMATIVE REFERENCE... 1 TERMS AND DEFINITIONS... 1 REQUIREMENTS... 2 ii

SCOPE The MIB module is for representing general information about optical equipment present in the headend (or indoor) and is supported by an SNMP agent. COPYRIGHT The MIB definition found in this document may be incorporated directly in products without further permission from the copyright owner, SCTE. NORMATIVE REFERENCE IETF RFC2578, Structure of Management Information Version 2 (SMIv2) IETF RFC2579, Textual Conventions for SMIv2 IETF RFC2580, Conformance Statements for SMIv2 IETF RFC2737, Entity MIB (Version 2) ANSI/SCTE 36,SCTE Root Management Information Block (MIB) SCTE 38-11, Hybrid Management Sub-layer Management Information Base (MIB) Part 11: SCTE-HMS-HEADENDIDENT-MIB IETF RFC2573, SNMP Applications IETF RFC1907, Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2) ANSI/SCTE 38-1, Hybrid Management Sublayer Management Information Blocks (MIB) Part 1: Property MIB INFORMATIVE REFERENCE None TERMS AND DEFINITIONS This document defines the following terms: Management Information Base (MIB) - the specification of information in a manner that allows standard access through a network management protocol. 1

REQUIREMENTS This section defines the mandatory syntax of the SCTE-HMS-HE-COMMON-MIB. It follows the IETF Simple Network Management Protocol (SNMP) for defining managed objects. The syntax is given below: 2

-- Module Name: HMS111R9.MIB (SCTE 84-1) -- SCTE Status: Adopted SCTE-HMS-HE-COMMON-MIB DEFINITIONS ::= BEGIN IMPORTS Integer32, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE FROM SNMPv2-SMI DisplayString, DateAndTime FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF entphysicalindex FROM ENTITY-MIB sctehmstree FROM SCTE-ROOT -- see SCTE 36 (formerly HMS028) hecommon, HeTenthCentigrade FROM SCTE-HMS-HEADENDIDENT-MIB; -- see SCTE 38-11 (formerly HMS114) hecommonmib MODULE-IDENTITY LAST-UPDATED "200302170000Z" -- February 17, 2003 ORGANIZATION "SCTE HMS Working Group" CONTACT-INFO " SCTE HMS Subcommittee, Chairman mailto:standards@scte.org " "The MIB module is for representing general information about optical equipment present in the headend (or indoor) and is supported by an SNMP agent." REVISION "200302170000Z" -- February 17, 2003 " Incorporated RTF comments posted by January 10, 2003. " 1

::= { hecommon 1 hecommonobjects OBJECT IDENTIFIER ::= { hecommonmib 1 -- MIB contains 2 groups hecommonparams OBJECT IDENTIFIER ::= { hecommonobjects 1 hecommonlog OBJECT IDENTIFIER ::= { hecommonobjects 2 -- The Common Table hecommontable OBJECT-TYPE SYNTAX SEQUENCE OF HeCommonEntry MAX-ACCESS not-accessible "A table containing information about headend (or indoor) equipment." ::= { hecommonparams 1 hecommonentry OBJECT-TYPE SYNTAX HeCommonEntry MAX-ACCESS not-accessible "Information about particular headend equipment." INDEX { entphysicalindex ::= { hecommontable 1 HeCommonEntry ::= SEQUENCE { hecommontime DateAndTime, hecommontemperature HeTenthCentigrade, hecommonsoftwarereset INTEGER, hecommonalarmdetectioncontrol INTEGER hecommontime OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-write 2

"Real time clock." ::= { hecommonentry 1 hecommontemperature OBJECT-TYPE SYNTAX HeTenthCentigrade MAX-ACCESS read-only "Temperature measured inside the headend equipment. This object must provide for the alarm management capabilities with a corresponding entry in the propertytable of SCTE-HMS-PROPERTY-MIB (HMS026). An alarm shall be recorded as an entry in the currentalarmtable of SCTE-HMS-PROPERTY-MIB (HMS026). A log record shall be added as an entry in the hecommonlogtable. An hecommonalarmevent notification shall be sent." ::= { hecommonentry 2 hecommonsoftwarereset OBJECT-TYPE SYNTAX INTEGER { reset(1) MAX-ACCESS read-write "This object is used to reset software of the headend physical entity. A SET request with the value reset(1) only shall reset the software application. The reset implementation is vendor specific. A GET request shall always return the value reset(1) and 3

shall have no effect on the entity." ::= { hecommonentry 3 hecommonalarmdetectioncontrol OBJECT-TYPE SYNTAX INTEGER { detectiondisabled(1), detectionenabled(2), detectionenabledandregenerate(3) MAX-ACCESS read-write "This object is used to control the detection of alarms in this headend entity. Each headend entity may provide for the alarm management capabilities. The provisions shall be done by means of the propertytable and/or the discretepropertytable of SCTE-HMS-PROPERTY-MIB (HMS026). When a threshold from either the propertytable or the discretepropertytable is crossed in a manner described by SCTE-HMS-PROPERTY-MIB (HMS026), then an alarm is said to have occurred. When the alarm is detected, then (1) an entry is placed in the hecommonlogtable, which serves as a log of the most recent alarm events; (2) an hecommonalarmevent trap is generated; (3) a property which is not in the nominal state will have an entry in the currentalarmtable of SCTE-HMS-PROPERTY-MIB. The detectiondisabled(1) value prevents the threshold detection process associated with the property table and discrete property table from running. The headend entity shall not generate alarms. The contents of the hecommonlogtable, currentalarmtable, each 4

instance of discretealarmstate, and each instance of currentalarmstate shall remain in the state prior to detectiondisabled(1) being applied. The detectionenabled(2) value permits alarm detection to run. The detection process continues from the state the headend entity was in prior to detectionenabled(2) being set. The detectionenabledandregenerate(3) value clears all alarm information and permits alarm detection to run. All alarm properties, both discrete and analog, are restored to the nominal value before alarm detection runs. Any properties that are in an alarm state SHALL NOT produce a 'return to normal' alarm as part of the process. Setting this value clears the hecommonlogtable and the currentalarmtable. The detectionenabledandregenerate(3) value is transient, that is a SET request with a value detectionenabledandregnerate(3) shall return the same value detectionenabledandregnerate(3). Subsequent GET requests shall return a value detectionenabled(2). The detectiondisabled(1) value shall affect the generation of hecommonalarmevent trap only. Traps added in the future are assumed to be unaffected by this object, unless stated in the description of that trap. This object has a default value of detectionenabled(2). The value shall be maintained in non-volatile memory." ::= { hecommonentry 4 -- The Common Log Group and Table hecommonlognumberofentries OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-only 5

"The current number of entries in the hecommonlogtable. Before the very first wrap-around condition occurs for hecommonlogindex, hecommonlognumberofentries will return the total number of entries logged in hecommonlogtable, since the unit was powered up. After the first wrap-around condition has occured for for the value of the MIB variable hecommonlogindex, hecommonlognumberofentries will return the maximum number of rows the hecommonlogtable can hold. " ::= { hecommonlog 1 hecommonloglastindex OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-only "Index of the most recent alarm entry logged in the hecommonlogtable. The value of this variable can be used as the value of hecommonlogindex to retrieve the most recent logged entry." ::= { hecommonlog 2 hecommonlogtable OBJECT-TYPE SYNTAX SEQUENCE OF HeCommonLogEntry MAX-ACCESS not-accessible "A list of alarms that have been logged. Agent should generate the SNMP HMS notification every time a new alarm entry is logged. This table should support a minimum of 16 entries." ::= { hecommonlog 3 hecommonlogentry OBJECT-TYPE SYNTAX HeCommonLogEntry MAX-ACCESS not-accessible 6

"A set of data describing an alarm event that has been logged." INDEX { hecommonlogindex ::= { hecommonlogtable 1 HeCommonLogEntry ::= SEQUENCE { hecommonlogindex Integer32, hecommonlogoid OBJECT IDENTIFIER, hecommonlogvalue Integer32, hecommonlogstate INTEGER, hecommonlogtime DateAndTime, hecommonlogtext DisplayString hecommonlogindex OBJECT-TYPE SYNTAX Integer32 (1..65535) MAX-ACCESS not-accessible "An index that uniquely identifies an entry in the log table. Indexes are assigned beginning with 1 and increased by one with each new log entry up to 65535. The next entry after 65535 is one. The agent may choose to delete the oldest instances of hecommonlogentry as required because of lack of memory. It is an implementation-specific matter as to when this deletion may occur. Note - The wrap-around for the hecommonlogindex variable MUST occur after 65535 regardless of the implementation specific size of the hlcommonlogtable." ::= { hecommonlogentry 1 hecommonlogoid OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-only 7

"This is the OID of the object that has changed alarm state." ::= { hecommonlogentry 2 hecommonlogvalue OBJECT-TYPE SYNTAX Integer32 (-2147483648..2147483647) MAX-ACCESS read-only "This is the value of the object at the time it changed alarm state." ::= { hecommonlogentry 3 hecommonlogstate OBJECT-TYPE SYNTAX INTEGER { hecommonnominal(1), hecommonhihi(2), hecommonhi(3), hecommonlo(4), hecommonlolo(5), hecommondiscretemajor(6), hecommondiscreteminor(7) MAX-ACCESS read-only "The new alarm state of the object which caused the event to be recorded into the log." ::= { hecommonlogentry 4 hecommonlogtime OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-only "This is the time when the alarm change for the object occured." 8

::= { hecommonlogentry 5 hecommonlogtext OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-only "This is a text field describing the alarm. This field could be a zero length string in certain agent implementations." ::= { hecommonlogentry 6 -- Headend Common MIB Trap Definitions hecommontraps OBJECT IDENTIFIER ::= { hecommonmib 2 hecommontrapprefix OBJECT IDENTIFIER ::= { sctehmstree 0 hecommonalarmevent NOTIFICATION-TYPE OBJECTS { hecommonlogoid, hecommonlogvalue, hecommonlogstate, hecommonlogtime "The SNMP trap that is generated when an alarm event is found. At the option of the unit, the hecommonlogtext variable may be reported as a fifth varbind, for those instances where an additional text field is supported." ::= { hecommontrapprefix 5 -- Conformance information hecommonconformance OBJECT IDENTIFIER ::= { hecommonmib 3 hecommoncompliances OBJECT IDENTIFIER ::= { hecommonconformance 1 hecommongroups OBJECT IDENTIFIER ::= { hecommonconformance 2 9

-- Compliance statements hecommoncompliance MODULE-COMPLIANCE "The compliance statement for SNMP entities which implement this MIB." MODULE -- this module MANDATORY-GROUPS { hecommonloggroup, hecommonnotificationsgroup MODULE ENTITY-MIB MANDATORY-GROUPS { entityphysicalgroup, entityphysical2group, entitygeneralgroup, entitynotificationsgroup MODULE SNMP-TARGET-MIB MANDATORY-GROUPS { snmptargetbasicgroup MODULE SNMP-NOTIFICATION-MIB MANDATORY-GROUPS { snmpnotifygroup MODULE SNMPv2-MIB MANDATORY-GROUPS { systemgroup -- The OBJECT clauses below indicate the optional objects of -- the systemgroup. They also imply that other objects of -- the group must be implemented: -- sysdescr, -- sysobjectid, -- sysuptime, -- syscontact, -- sysname, -- syslocation, -- sysservices. 10

OBJECT sysordescr MIN-ACCESS not-accessible "Implementation of this object is optional." OBJECT sysorid MIN-ACCESS not-accessible "Implementation of this object is optional." OBJECT sysorlastchange MIN-ACCESS not-accessible "Implementation of this object is optional." OBJECT sysoruptime MIN-ACCESS not-accessible "Implementation of this object is optional." MODULE SCTE-HMS-PROPERTY-MIB MANDATORY-GROUPS { analogalarmsgroup, discretealarmsgroup, currentalarmsgroup ::= { hecommoncompliances 1 -- MIB groupings hecommonparamsgroup OBJECT-GROUP OBJECTS { hecommontime, hecommontemperature, hecommonsoftwarereset, hecommonalarmdetectioncontrol 11

"The collection of objects which are used to represent the common parameters of the headend managed entities." ::= { hecommongroups 1 hecommonloggroup OBJECT-GROUP OBJECTS { hecommonlognumberofentries, hecommonloglastindex, hecommonlogoid, hecommonlogvalue, hecommonlogstate, hecommonlogtime, hecommonlogtext "The collection of objects which are used to record an alarm event into the headend agent log." ::= { hecommongroups 2 hecommonnotificationsgroup NOTIFICATION-GROUP NOTIFICATIONS { hecommonalarmevent "The collection of notifications used by the headend agent to report the exceptional conditions to the management application." ::= { hecommongroups 3 END 12