NAFEM-UTILITYMANAGEMENT-MIB DEFINITIONS ::= BEGIN. -- From file: "utility-management.mib" IMPORTS
|
|
- Penelope Alexander
- 6 years ago
- Views:
Transcription
1 NAFEM-UTILITYMANAGEMENT-MIB DEFINITIONS ::= BEGIN From file: "utility-management.mib" IMPORTS OBJECT-TYPE IpAddress NafemDateTime, DisplayString, NafemChoice, NafemInterval, NafemAlarmStatus utilitymgmtgroup, utilitymgmtinstance, utilitymgmtcfg, utilitymgmtdata, utilitymgmtalarm, utilitymgmtlog, utilitymgmtloghist, utilitynotify FROM RFC-1212 FROM RFC1065-SMI FROM NAFEM-TC-MIB FROM NAFEM-REG-MIB; nafemutilmgmtmodule MODULE-IDENTITY LAST-UPDATED " " ORGANIZATION "NAFEM" ORGANIZATION "NAFEM" CONTACT-INFO " Contact: NAFEM Technical Liaison Committee Postal: North American Association of Food Equipment Manufacturers (NAFEM) 161 North Clark Street, Suite 2020 Chicago IL Phone: Fax: Web: " DESCRIPTION " The Utility Management Object Group module. Copyright (c) 2003 North American Association of Food Equipment Manufacturers (NAFEM). All rights reserved. Reproduction of this document is authorized on the condition that the foregoing copyright notice is included. This SNMP MIB module (Specification) embodies NAFEM's proprietary intellectual property. NAFEM retains all title and ownership in the Specification, including any revisions. NAFEM grants all interested parties a non-exclusive license to use and distribute an unmodified copy of this Specification in connection with management of products that incorporate the NAFEM Communications Protocol, and without fee, provided this copyright notice and license appear on all copies. This Specification is supplied 'AS IS' and NAFEM makes not warranty, either expressed or implied, as to the use, operation, condition, or performance of the Specification. " 1
2 REVISION " 2.00 " DESCRIPTION " Updated version of MIB module NAFEM-UTILITYMANAGEMENT-MIB " begin definitions Utility Management CONFIGURATION Table utilitymgmtcfgtable OBJECT-TYPE SYNTAX SEQUENCE OF UtilityMgmtCfgEntry DESCRIPTION " Table of utility systems within the hosted equipment that need to be monitored under utility management practices. Systems that have multiple utility types will have more than one entry in this table. " ::= { utilitymgmtcfg 1 utilitymgmtcfgentry OBJECT-TYPE SYNTAX UtilityMgmtCfgEntry DESCRIPTION " A utility type entry. " INDEX { utilitymgmtcfgentryindex ::= { utilitymgmtcfgtable 1 UtilityMgmtCfgEntry ::= SEQUENCE { UtilityMgmtCfgEntryIndex utilitymgmtcfgname utilitymgmtcfgtype utilitymgmtcfgdesc utilitymgmtcfgratedvalue utilitymgmtcfgunits DisplayString, DisplayString, INTEGER utilitymgmtcfgentryindex OBJECT-TYPE DESCRIPTION " Utility type sequence number to index within the table of configurations. " ::= { utilitymgmtcfgentry 1 utilitymgmtcfgname OBJECT-TYPE SYNTAX DisplayString (SIZE (0..32)) DESCRIPTION " A user/supplier textual description of the utility type. " ::= { utilitymgmtcfgentry 2 2
3 utilitymgmtcfgtype OBJECT-TYPE { not-available (1), gas (2), electricity (3), water (4), steam (5), compressed-gas (6), refrigerant (7), other (8) DESCRIPTION " A standardized utility descriptor. " ::= { utilitymgmtcfgentry 3 utilitymgmtcfgdesc OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) DESCRIPTION " Textual description of utility type to communicate to the user the actual application or importance of this attribute. " ::= { utilitymgmtcfgentry 4 utilitymgmtcfgratedvalue OBJECT-TYPE DESCRIPTION " The manufacturer's rating of this utility based on name plate entry. " ::= { utilitymgmtcfgentry 5 utilitymgmtcfgunits OBJECT-TYPE enumerated parameters in NAFEM approved units DESCRIPTION " A standardized engineering units descriptor. " ::= { utilitymgmtcfgentry 6 Utility Management DATA Table utilitymgmtdatatable OBJECT-TYPE SYNTAX SEQUENCE OF UtilityMgmtDataEntry DESCRIPTION " Table of utility current values within the hosted equipment that shall be monitored under utility management practices. Systems that have multiple utility types will have more than one entry in this table. " ::= { utilitymgmtdata 1 utilitymgmtdataentry OBJECT-TYPE SYNTAX UtilityMgmtDataEntry DESCRIPTION " An entry in the table of utility data properties for each utility type. " INDEX { utilitymgmtdataentryindex ::= { utilitymgmtdatatable 1 3
4 UtilityMgmtDataEntry ::= SEQUENCE { utilitymgmtdataentryindex utilitymgmtdatavalue utilitymgmtdatastatus utilitymgmtdatatimestamp NafemAlarmStatus, NafemDateTime utilitymgmtdataentryindex OBJECT-TYPE DESCRIPTION " Utility type sequence number to index within the table of utility types. " ::= { utilitymgmtdataentry 1 utilitymgmtdatavalue OBJECT-TYPE DESCRIPTION " Utility measured value expressed in utilitymgmtcfgunits. " ::= { utilitymgmtdataentry 2 utilitymgmtdatastatus OBJECT-TYPE SYNTAX NafemAlarmStatus DESCRIPTION " The status of a data object. " ::= { utilitymgmtdataentry 3 utilitymgmtdatatimestamp OBJECT-TYPE SYNTAX NafemDateTime DESCRIPTION " A time stamp when the data object was last updated. " ::= { utilitymgmtdataentry 4 Utility Management ALARM Table utilitymgmtalarmtable OBJECT-TYPE SYNTAX SEQUENCE OF UtilityMgmtAlarmEntry DESCRIPTION " Table of utility alarm configuration and status attributes within the hosted equipment. Systems that have multiple utility types will have more than one entry in this table. Corresponding utility configuration information can be cross-reference by the INDEX field value in associated object tables. " ::= { utilitymgmtalarm 1 utilitymgmtalarmentry OBJECT-TYPE SYNTAX UtilityMgmtAlarmEntry DESCRIPTION " An entry in the table of history data for each utility type logged. " INDEX { utilitymgmtalarmentryindex ::= { utilitymgmtalarmtable 1 4
5 UtilityMgmtAlarmEntry ::= SEQUENCE { utilitymgmtalarmentryindex utilitymgmtalarmcritlimithigh utilitymgmtalarmcritlimitlow utilitymgmtalarmwarnlimithigh utilitymgmtalarmwarnlimitlow utilitymgmtalarmdeviation utilitymgmtalarmclear utilitymgmtalarmbypass NafemChoice, NafemChoice utilitymgmtalarmentryindex OBJECT-TYPE DESCRIPTION " Alarm sequence number to index within the table of utility types. " ::= { utilitymgmtalarmentry 1 utilitymgmtalarmcritlimithigh OBJECT-TYPE DESCRIPTION " The value of monitored attribute at which an notification trap is triggered. Either equal to or greater than. " ::= { utilitymgmtalarmentry 2 utilitymgmtalarmcritlimitlow OBJECT-TYPE DESCRIPTION " The value of monitored attribute at which an notification trap is triggered. Either equal to or less than. " ::= { utilitymgmtalarmentry 3 utilitymgmtalarmwarnlimithigh OBJECT-TYPE DESCRIPTION " The value of monitored attribute at which an notification trap is triggered. Either equal to or greater than. " ::= { utilitymgmtalarmentry 4 utilitymgmtalarmwarnlimitlow OBJECT-TYPE DESCRIPTION " The value of monitored attribute at which an notification trap is triggered. Either equal to or less than. " ::= { utilitymgmtalarmentry 5 utilitymgmtalarmdeviation OBJECT-TYPE DESCRIPTION " The change between consecutive readings in monitored attribute at which an alarm event is triggered. " ::= { utilitymgmtalarmentry 6 5
6 utilitymgmtalarmclear OBJECT-TYPE SYNTAX NafemChoice DESCRIPTION " Setting this attribute to 2 will signal the device to CLEAR the alarm status. If the alarm condition exists the reset attempt will have no effect, or else the status will be no alarm. " ::= { utilitymgmtalarmentry 7 utilitymgmtalarmbypass OBJECT-TYPE SYNTAX NafemChoice DESCRIPTION " Setting this attribute to 2 will signal the device to enable disable the alarm. Setting this value to 1 will enable the alarm. " ::= { utilitymgmtalarmentry 8 Utility Management LOG Table utilitymgmtlogtable OBJECT-TYPE SYNTAX SEQUENCE OF UtilityMgmtLogEntry DESCRIPTION " Table of utility log configuration attribute within the hosted equipment that shall be logged under utility management practices. Systems that have multiple utility types will have more than one entry in this table. Corresponding utility configuration information can be cross-referenced by the NAME field value in associated object tables. " ::= { utilitymgmtlog 1 utilitymgmtlogentry OBJECT-TYPE SYNTAX UtilityMgmtLogEntry DESCRIPTION " Entry into the utility management log. " INDEX { utilitymgmtlogentryindex ::= { utilitymgmtlogtable 1 UtilityMgmtLogEntry ::= SEQUENCE { UtilityMgmtLogEntryIndex utilitymgmtlogname DisplayString, utilitymgmtlogenable NafemChoice, utilitymgmtloginterval NafemInterval, utilitymgmtlogdeviation utilitymgmtlogforcedinterval NafemInterval, utilitymgmtlogmaxholddays utilitymgmtloghistory OBJECT IDENTIFIER utilitymgmtlogentryindex OBJECT-TYPE DESCRIPTION " Log sequence number to index within the table of initialized devices. " ::= { utilitymgmtlogentry 1 6
7 utilitymgmtlogname OBJECT-TYPE SYNTAX DisplayString (SIZE (0..32)) DESCRIPTION " A textual name of the utility item from the configuration table." ::= { utilitymgmtlogentry 2 utilitymgmtlogenable OBJECT-TYPE SYNTAX NafemChoice DESCRIPTION " YES enables history table activation. " ::= { utilitymgmtlogentry 3 utilitymgmtloginterval OBJECT-TYPE SYNTAX NafemInterval DESCRIPTION " The minimum time in NafemInterval values that a value attribute shall be logged in to the history table. " ::= { utilitymgmtlogentry 4 utilitymgmtlogdeviation OBJECT-TYPE DESCRIPTION " The amount of change between consecutive monitoring events that would log a record to the history table. " ::= { utilitymgmtlogentry 5 utilitymgmtlogforcedinterval OBJECT-TYPE SYNTAX NafemInterval DESCRIPTION " The minimum time in NafemInterval Values that a value attribute must be forced to log to a history record. " ::= { utilitymgmtlogentry 6 utilitymgmtlogmaxholddays OBJECT-TYPE DESCRIPTION " The number of days that the logged history records are kept in memory before they can be over written by subsequent record logs. " ::= { utilitymgmtlogentry 7 utilitymgmtloghistory OBJECT-TYPE SYNTAX OBJECT IDENTIFIER DESCRIPTION " Oid for the utilitymgmtloghisttable sub-table. " ::= { utilitymgmtlogentry 8 utilitymgmtloghist OBJECT IDENTIFIER ::= {utilitymgmtlogentry 7 7
8 utilitymgmtloghisttable OBJECT-TYPE SYNTAX SEQUENCE OF UtilityMgmtLogHistEntry DESCRIPTION " Table of utility history log records within the hosted equipment that shall be logged under utility management practices. Systems that have multiple recording events will have more than one entry in this table. " ::= { utilitymgmtloghist 1 utilitymgmtloghistentry OBJECT-TYPE SYNTAX UtilityMgmtLogHistEntry DESCRIPTION "An entry in the table of history properties for each utility type logged. " INDEX { utilitymgmtloghistentryindex ::= { utilitymgmtloghisttable 1 UtilityMgmtLogHistEntry ::= SEQUENCE { utilitymgmtloghistentryindex utilitymgmtloghistvalue utilitymgmtloghisttimestamp NafemDateTime utilitymgmtloghistentryindex OBJECT-TYPE DESCRIPTION " The index into the utilitymgmtloghisttable. " ::= { utilitymgmtloghistentry 1 utilitymgmtloghistvalue OBJECT-TYPE DESCRIPTION " The value of the associated attribute defined by the NAME field that is recorded due to a triggered log event. " ::= { utilitymgmtloghistentry 2 utilitymgmtloghisttimestamp OBJECT-TYPE SYNTAX NafemDateTime DESCRIPTION " The date and time that the value of the associated attribute defined by the NAME field was recorded due to a triggered log event. " ::= { utilitymgmtloghistentry 3 utilitynotifytable OBJECT-TYPE SYNTAX SEQUENCE OF UtilityNotifyEntry DESCRIPTION " " ::= {utilitynotify 1 8
9 utilitynotifyentry OBJECT-TYPE SYNTAX UtilityNotifyEntry DESCRIPTION " " INDEX { utilitynotifytableindex ::= {utilitynotifytable 1 UtilityNotifyEntry ::= SEQUENCE { utilitynotifytableindex utilitynotifymessage DisplayString, utilitynotifycode utilitynotifytimestamp NafemDateTime, utilitynotifyenable NafemChoice utilitynotifytableindex OBJECT-TYPE DESCRIPTION " A textual description of the notify message Index for the rows of utilitynotifytable. " ::= { utilitynotifyentry 1 utilitynotifymessage OBJECT-TYPE SYNTAX DisplayString (SIZE (0..32)) DESCRIPTION " A textual description of the notify message. " ::= { utilitynotifyentry 2 utilitynotifycode OBJECT-TYPE NafemNotifyCode DESCRIPTION " A Code description of the notify message. " ::= {utilitynotifyentry 3 utilitynotifytimestamp OBJECT-TYPE SYNTAX NafemDateTime read-only DESCRIPTION " The date and time at which an event occurred. " ::= { utilitynotifyentry 4 utilitynotifyenable OBJECT-TYPE SYNTAX NafemChoice DESCRIPTION " 1 = No trap generation, 2 = Enable trap generation, Reference current NAFEM textual convention. " ::= { utilitynotifyentry 5 9
10 utilitynotifyacktable OBJECT-TYPE SYNTAX SEQUENCE OF UtilityNotifyAckEntry DESCRIPTION " Table of associated acknowledgement feature attribute to the notification message. This table is used when the system requires a response from a manager when a trap is sent. " ::= {utilitynotify 2 utilitynotifyackentry OBJECT-TYPE SYNTAX UtilityNotifyAckEntry DESCRIPTION " Entry in acknowledgement table. " INDEX { utilitynotifyacktableindex ::= {utilitynotifyacktable 1 UtilityNotifyAckEntry ::= SEQUENCE { utilitynotifyacktableindex utilitynotifyack utilitynotifyinterval utilitynotifyretries utilitynotifyresponse NafemChoice, NafemInterval, IpAddress utilitynotifyacktableindex OBJECT-TYPE DESCRIPTION " Index for the rows of the utilitynotifyacktable. " ::= { utilitynotifyackentry 1 utilitynotifyack OBJECT-TYPE SYNTAX NafemChoice DESCRIPTION " 1 = No acknowledgement required from manager, 2 = Acknowledgement required, Reference current NAFEM textual convention. " ::= { utilitynotifyackentry 2 utilitynotifyinterval OBJECT-TYPE SYNTAX NafemInterval DESCRIPTION " Delay interval between non-acknowledged trap events. Applicable only when acknowledgement required. Reference current NAFEM textual convention. " ::= { utilitynotifyackentry 3 utilitynotifyretries OBJECT-TYPE DESCRIPTION " Number of attempts of non-acknowledged trap events. Applicable only when acknowledgement required. " ::= { utilitynotifyackentry 4 10
11 utilitynotifyresponse OBJECT-TYPE SYNTAX IpAddress DESCRIPTION " Response word from SNMP Manager to acknowledge to. Manager writes his/her Ipaddress to confirm receipt. " ::= { utilitynotifyackentry 5 END MIB-utility-v2.00;
NAFEM-INVENTORY-MANAGEMENT-MIB DEFINITIONS ::= BEGIN. -- From file: "inventory-management.mib" IMPORTS -- enterprises FROM RFC1155-SMI
NAFEM-INVENTORY-MANAGEMENT-MIB DEFINITIONS ::= BEGIN From file: "inventory-management.mib" IMPORTS enterprises FROM RFC1155-SMI IpAddress, Counter FROM RFC1065-SMI OBJECT-TYPE FROM RFC-1212 DisplayString
More informationNAFEM-ADMINISTRATION-MIB DEFINITIONS ::= BEGIN. -- From file: "administration.mib" IMPORTS. admininfo, admincommunity,
NAFEM-ADMINISTRATION-MIB DEFINITIONS ::= BEGIN From file: "administration.mib" IMPORTS OBJECT-TYPE DisplayString admininfo, admincommunity, adminnotify NafemAlarmStatus, NafemDateTime, NafemChoice, NafemInterval
More informationNAFEM-BULK-TRANSFER-MIB DEFINITIONS ::= BEGIN. -- From file: "bulk-transfer.mib" IMPORTS. NafemDateTime, NafemChoice, NafemInterval,
NAFEM-BULK-TRANSFER-MIB DEFINITIONS ::= BEGIN From file: "bulk-transfer.mib" IMPORTS IpAddress OBJECT-TYPE DisplayString NafemDateTime,, NafemInterval, NafemAlarmStatus bulktransfergroup, bulkstoragemedia,
More informationNAFEM-SECURITY-MIB DEFINITIONS ::= BEGIN. -- From file: "security.mib" IMPORTS. NafemDateTime, NafemChoice, NafemTime, NafemInterval,
NAFEM-SECURITY-MIB DEFINITIONS ::= BEGIN From file: "security.mib" IMPORTS OBJECT-TYPE IpAddress DisplayString NafemDateTime, NafemChoice, NafemTime, NafemInterval, NafemAlarmStatus securitygroup, securitysystem,
More informationNAFEM-TEXTUAL-CONVENTION-MIB DEFINITIONS ::= BEGIN. --NAFEM-ROOT OBJECT IDENTIFIER ::= { enterprises 8117 }
NAFEM-TEXTUAL-CONVENTION-MIB DEFINITIONS ::= BEGIN NAFEM-ROOT OBJECT IDENTIFIER ::= { enterprises 8117 nafemtcmodule MODULE-IDENTITY LAST-UPDATED " 200301010000000 " ORGANIZATION "NAFEM" ORGANIZATION "NAFEM"
More informationSociety of Cable Telecommunications Engineers
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)
More informationPica8 private MIB. March, Version: 2.
March, 2015 Version: 2 www.pica8.com Pica8, Inc. 1032 Elwell Court, Suite 105 Palo Alto, CA. 94303 +1 (650) 614-5838 sales@pica8.com support@pica8.com Copyright 2015 Pica8 Inc. Pica8 is a registered trademark
More informationRequest for Comments: 2493 Category: Standards Track January 1999
Network Working Group K. Tesink, Editor Request for Comments: 2493 Bellcore Category: Standards Track January 1999 Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals
More informationBrief Introduction to the Internet Standard Management Framework
Part 2: Structure of Management Information Version 2 (SMIv2) The SMI is the Data Definition Language, based loosely on an old version of ASN.1 and used to model and define management information to be
More informationThe Marway Chassis MIB. Status of this Memo. This document specifies a proprietary MIB module of Marway Power Solutions.
The Marway Chassis MIB Status of this Memo This document specifies a proprietary MIB module of Marway Power Solutions. Distribution of this memo is limited to Marway product licensees and other interested
More information1. 2. 3. o o o o o o o o o o o NUTANIX-MIB DEFINITIONS ::= BEGIN IMPORTS DisplayString FROM RFC1213-MIB enterprises, MODULE-IDENTITY, OBJECT-TYPE, Integer32, Counter64 FROM SNMPv2-SMI TimeStamp
More informationThe Marway Sensor MIB. Status of this Memo. This document specifies a proprietary MIB module of Marway Power Solutions.
The Marway Sensor MIB Status of this Memo This document specifies a proprietary MIB module of Marway Power Solutions. Distribution of this memo is limited to Marway product licensees and other interested
More informationInternet Engineering Task Force (IETF) Category: Standards Track. J. Quittek. NEC Europe Ltd. October 2012
Internet Engineering Task Force (IETF) Request for Comments: 6727 Category: Standards Track ISSN: 2070-1721 T. Dietz, Ed. NEC Europe Ltd. B. Claise Cisco Systems, Inc. J. Quittek NEC Europe Ltd. October
More informationCategory: Standards Track September MIB Textual Conventions for Uniform Resource Identifiers (URIs)
Network Working Group D. McWalter, Ed. Request for Comments: 5017 Data Connection Ltd Category: Standards Track September 2007 MIB Textual Conventions for Uniform Resource Identifiers (URIs) Status of
More informationRADIUS Working Group Bernard Aboba. Category: Standards Track <draft-ietf-radius-auth-clientmib-01.txt> 12 February 1998
RADIUS Working Group Bernard Aboba INTERNET-DRAFT Microsoft Category: Standards Track Glen Zorn Microsoft 12 February 1998 RADIUS Authentication Client MIB 1.
More informationInternet Engineering Task Force (IETF) Request for Comments: 7330 Category: Standards Track. Cisco Systems August 2014
Internet Engineering Task Force (IETF) Request for Comments: 7330 Category: Standards Track ISSN: 2070-1721 T. Nadeau Brocade Z. Ali N. Akiya Cisco Systems August 2014 Definitions of Textual Conventions
More informationNAFEM Data Protocol Standard
NAFEM Data Protocol Standard Version 3.00 1.0 Scope This document provides a framework for standardized data transmission between a host computer and various pieces of commercial food service equipment.
More informationOAM Principles. version 5.4
version 5.4 Typeset in L A TEX from SGML source using the DOCBUILDER 3.3.2 Document System. Contents 1 1 1.1 Introduction......................................... 1 1.1.1 Terminology......................................
More information[AN018] Configuring a Device for InformaCast M2M. Version 2.0 9/22/ ADVANCED NETWORK DEVICES 3820 NORTH VENTURA DR.
[AN018] Configuring a Device for Version 2.0 9/22/2017 2017 ADVANCED NETWORK DEVICES 3820 NORTH VENTURA DR. ARLINGTON HEIGHTS, IL 60004 U.S.A ALL RIGHTS RESERVED PROPRIETARY NOTICE AND LIABILITY DISCLAIMER
More informationNetwork Working Group. Category: Standards Track June Protocol Independent Multicast (PIM) Bootstrap Router MIB
Network Working Group Request for Comments: 5240 Category: Standards Track B. Joshi Infosys Technologies Ltd. R. Bijlani June 2008 Protocol Independent Multicast (PIM) Bootstrap Router MIB Status of This
More informationCharacterization of SNMP MIB Modules
Characterization of SNMP MIB Modules Jürgen Schönwälder j.schoenwaelder@iu-bremen.de International University Bremen Campus Ring 1 28725 Bremen, Germany Characterization of SNMP MIB Modules p. 1 Motivation
More informationInternet Engineering Task Force (IETF)
Internet Engineering Task Force (IETF) Request for Comments: 7420 Category: Standards Track ISSN: 2070-1721 A. Koushik Brocade Communications, Inc. E. Stephan Orange Q. Zhao Huawei Technology D. King Old
More informationES V1.1.1 ( )
Standard Human Factors; Procedure for registering a supplementary service code 2 Reference DES/HF-00008 (cso00icp.pdf) Keywords supplementary service, registration Postal address F-06921 Sophia Antipolis
More informationInnosoft January 1994
Network Working Group Request for Comments: 1566 Category: Standards Track S. Kille, WG Chair ISODE Consortium N. Freed, Editor Innosoft January 1994 Mail Monitoring MIB Status of this Memo This document
More informationMultistate Value/ BACnet Multistate Value
Object Dictionary 1 Multistate Value/ BACnet Multistate Value Introduction Note: The Johnson Controls Multistate Value object is considered a BACnet Multistate Value object because it supports BACnet functionality.
More information-- extracted from rfc2515.txt -- at Mon Nov 15 17:11: ATM-MIB DEFINITIONS ::= BEGIN
-- extracted from rfc2515.txt -- at Mon Nov 15 17:11:39 1999 DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, -TYPE, Counter32, Integer32, IpAddress, mib-2 FROM SNMPv2-SMI DisplayString, RowStatus, TruthValue
More informationCisco Management Information Base
CHAPTER 7 This chapter describes the Management Information Base (MIB) text files that are supported by Cisco Unified Communications Manager (Cisco Unified CM) and are used with Simple Network Management
More informationCHAPTER. Introduction
CHAPTER 1 Network management takes place between two major types of systems: those in control, called managing systems, and those observed and controlled, called managed systems. The most common managing
More informationIntended status: Standards Track Expires: April 27, 2015 Q. Zhao Huawei Technology D. King Old Dog Consulting J. Hardwick Metaswitch October 24, 2014
PCE Working Group Internet-Draft Intended status: Standards Track Expires: April 27, 2015 A. Koushik Brocade Communications Inc. E. Stephan Orange Q. Zhao Huawei Technology D. King Old Dog Consulting J.
More informationRequest for Comments: Oversi O. Nicklass, Ed. RADVISION May Definitions of Textual Conventions for Pseudowire (PW) Management
Network Working Group Request for Comments: 5542 Category: Standards Track T. Nadeau, Ed. BT D. Zelig, Ed. Oversi O. Nicklass, Ed. RADVISION May 2009 Definitions of Textual Conventions for Pseudowire (PW)
More informationNetwork Working Group. Intended status: Standards Track. January 15, 2010
Network Working Group Internet-Draft Intended status: Standards Track Expires: July 19, 2010 G. Zorn Network Zen S. Comerica Cisco Systems January 15, 2010 Diameter Base Protocol MIB draft-ietf-dime-diameter-base-protocol-mib-04.txt
More informationIEEE Broadband Wireless Access Working Group <http://ieee802.org/16> MIB II Integration and MIB II Table
00-0-0 IEEE C0.i-0/00r Project Title Date Submitted Source(s) IEEE 0. Broadband Wireless Access Working Group MIB II Integration and MIB II Table 00-0-0 Joey Chou Intel Corporation
More informationMembership Application Form U.S. and Canadian Group
» The Organization Key Contact who serves as liaison with the American Marketing Association for your Group Membership fills out this application form and returns it to the AMA at the address or email
More informationConfiguring RMON. Understanding RMON CHAPTER
22 CHAPTER This chapter describes how to configure Remote Network Monitoring (RMON) on your switch. RMON is a standard monitoring specification that defines a set of statistics and functions that can be
More informationPower and Energy Monitoring MIB
draft- Mouli Chandramouli, B. Schoening Juergen Quittek Thomas Dietz Benoit Claise 81th IETF Meeting, Quebec, 2011 Draft based on Working Charter 4. Power and Energy Monitoring MIB document - The EMAN
More informationNetwork Working Group Request for Comments: 4070 Category: Standards Track PESA Switching Systems May 2005
Network Working Group Request for Comments: 4070 Category: Standards Track M. Dodge ECI Telecom B. Ray PESA Switching Systems May 2005 Definitions of Managed Object Extensions for Very High Speed Digital
More informationThe SNMPTrap Driver. This document relates to SNMPTrap driver version 1.2
The SNMPTrap Driver The SNMPTrap driver allows a North device to notify a network management station of events by sending Simple Network Management Protocol (SNMP) traps. SNMP is widely used to manage
More informationDraft ETSI EN V1.1.1 ( )
Draft EN 301 850-1 V1.1.1 (2000-10) European Standard (Telecommunications series) Integrated Services Digital Network (ISDN); Signalling System No.7 (SS7); ISDN User Part (ISUP); Application transport
More informationFeb :33 draft-glenn-id-sensor-alert-mib-01.txt Page 1
Feb 15 2001 17:33 Page 1 ID Message Exchange Format Working Group INTERNET-DRAFT Glenn Mansfield Cyber Solutions Inc. Dipankar Gupta Hewlett Packard Company November 20 2000 Status of this Memo Intrusion
More informationCharacterization of SNMP MIB Modules
Characterization of SNMP MIB Modules Jürgen Schönwälder j.schoenwaelder@iu-bremen.de International University Bremen Campus Ring 1 28725 Bremen, Germany slides.tex Characterization of SNMP MIB Modules
More informationHPE Network Node Manager i Software 10.30
HPE Network Node Manager i Software 10.30 Step-by-Step Guide to Custom Poller White Paper Contents Custom Poller... 3 Setting Up Your MIB... 3 Step 1: Identify the MIB Variable You Want to Poll... 3 Step
More informationFeb :33 draft-glenn-id-notification-mib-04.txt Page 1
Feb 15 2001 17:33 Page 1 ID Message Exchange Format Working Group Glenn Mansfield INTERNET-DRAFT Cyber Solutions Inc. November 20,2000 Status of this Memo Intrusion Detection Message MIB This document
More informationTCG. SNMP MIB for TPM-Based Attestation
SNMP MIB for TPM-Based Attestation Specification Version 0.8 Revision 0.02 May 22, 2018 DRAFT Contact: admin@trustedcomputinggroup.org Work in Progress This document is an intermediate draft for comment
More informationNetwork Management (NETW-1001)
Network Management (NETW-1001) Dr. Mohamed Abdelwahab Saleh IET-Networks, GUC Spring 2017 TOC 1 SNMPv1 Messages 2 SNMP messages Two main purposes: Monitoring and configuration. SNMP version 1 defines five
More informationDESCRIPTION "This revision is being published as part of the third update of the Packetcable Signaling MIBs enhancements for PacketCable 1.5.
ECL: Module name changed to distinguish from CableLabs module PKTC-ECL-EN-SIG-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, BITS FROM SNMPv2-SMI ifindex FROM IF-MIB SnmpAdminString
More informationSNMP NETIO M2M API protocols docs
SNMP NETIO M2M API protocols docs Protocol version: NETIO-MIB 1.05 Short summary SNMP is implemented as M2M API protocol, where NETIO device can use SNMP protocol allowing monitoring and control of NETIO
More informationTrend Log/BACnet Trend Log
Object Dictionary 1 Trend Log/BACnet Trend Log Introduction Notes: The Johnson Controls Trend Log object is considered a BACnet Trend Log object because it supports BACnet functionality. In addition, this
More informationEG V1.2.1 ( )
ETSI Guide Integrated Circuits Cards (ICC); ETSI numbering system for telecommunication; ALgorithm IDentifiers (ALID) European Telecommunications Standards Institute 2 Reference REG/ICC-00013 (bd000ioq.pdf)
More informationManual. Teldat SA. RMON (Remote Network Monitoring) Teldat-Dm 796-I. Copyright Version Teldat SA
Manual Teldat-Dm 796-I Copyright Version 11.01 1 Manual Legal Notice Warranty This publication is subject to change. Teldat offers no warranty whatsoever for information contained in this manual. Teldat
More informationNetwork Working Group. Category: Standards Track Tohoku University K. Nagami INTEC NetCore Inc. S. Gundavelli Cisco Systems Inc.
Network Working Group Request for Comments: 4295 Category: Standards Track G. Keeni Cyber Solutions Inc. K. Koide Tohoku University K. Nagami INTEC NetCore Inc. S. Gundavelli Cisco Systems Inc. April 2006
More informationENGINEERING COMMITTEE Hybrid Management Sub-Layer Subcommittee AMERICAN NATIONAL STANDARD
ENGINEERING COMMITTEE Hybrid Management Sub-Layer Subcommittee AMERICAN NATIONAL STANDARD ANSI/SCTE 38-5 2008 Hybrid Fiber/Coax Outside Plant Status Monitoring SCTE-HMS-FIBERNODE-MIB Management Information
More informationBarracuda NextGen Firewall X SNMP MIB
You can monitor objects included in this MIB either from custom scripts or from your SNMP monitor PHION-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF
More informationCategory: Informational 1 April Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
Network Working Group M. Slavitch Request for Comments: 2325 Loran Technologies Inc. Category: Informational 1 April 1998 Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using
More informationAuthor of previous version: B. Stewart November 2000
Network Working Group Request for Comments: 3014 Category: Standards Track Editor of this version: R. Kavasseri Cisco Systems, Inc. Author of previous version: B. Stewart November 2000 Notification Log
More informationCategory: Standards Track December 1998
Network Working Group M. Daniele Request for Comments: 2454 Compaq Computer Corporation Category: Standards Track December 1998 Status of this Memo IP Version 6 Management Information Base for the User
More informationSNMP SIMULATOR. Description
SNMP SIMULATOR Overview The SNMP Agent Simulator enables simulation of standalone SNMP agents to test and demonstrate SNMP-based management applications. Its unique ability to create default values from
More informationNetwork Working Group. Category: Standards Track September 2003
Network Working Group B. Wijnen Request for Comments: 3595 Lucent Technologies Category: Standards Track September 2003 Status of this Memo Textual Conventions for IPv6 Flow Label This document specifies
More informationXerox CentreWare for HP OpenView NNM Users Guide Version 1.5
Xerox CentreWare for HP OpenView NNM Users Guide Version 1.5 2002 by Xerox Corporation. All rights reserved. Copyright protection claimed includes all forms and matters of copyright material and information
More informationFinal draft ETSI EN V1.1.3 ( )
Final draft EN 301 069-2 V1.1.3 (2000-08) European Standard (Telecommunications series) Integrated Services Digital Network (ISDN); Signalling System No.7; ISDN User Part (ISUP); Application transport
More informationCELLTRAQ Battery Monitoring Software
CELLTRAQ Battery Monitoring Software Instructions April 2009 167-000128A INNOVATION TECHNOLOGY QUALITY WORLDWIDE Page 2 CELLTRAQ Overview CELLTRAQ CELLTRAQ is a web application that is used to monitor
More informationNetwork Working Group J. Case
Network Working Group J. Case Request for Comments: 1442 SNMP Research, Inc. K. McCloghrie Hughes LAN Systems M. Rose Dover Beach Consulting, Inc. S. Waldbusser Carnegie Mellon University April 1993 Structure
More informationHP Network Node Manager i Software Step-by-Step Guide to Custom Poller
HP Network Node Manager i Software Step-by-Step Guide to Custom Poller NNMi 9.1x Patch 2 This document includes two examples. The first example illustrates how to use Custom Poller to monitor disk space.
More informationEvent MIB and Expression MIB Enhancements
This document provides information about the several existing Simple Network Management Protocol (SNMP) MIBs that are enhanced and new SNMP MIBs that are added. Finding Feature Information, page 1 Information
More informationNetwork Working Group Request for Comments: 4131 Category: Standards Track Toshiba E. Cardona, Ed. CableLabs A. Katsnelson September 2005
Network Working Group Request for Comments: 4131 Category: Standards Track S. Green Consultant K. Ozawa Toshiba E. Cardona, Ed. CableLabs A. Katsnelson September 2005 Management Information Base for Data
More informationETSI TS V2.1.1 ( ) Technical Specification
TS 186 014-1 V2.1.1 (2009-05) Technical Specification Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services: Communication Diversion
More informationDraft ETSI EG V3.1.1 ( )
Draft EG 200 351 V3.1.1 (1999-07) Guide object identifier tree; Rules and registration procedures 2 Draft EG 200 351 V3.1.1 (1999-07) Reference REG/SPS-05209 (39001icq.PDF) Keywords object identifier,
More informationInternet Engineering Task Force (IETF) Category: Standards Track. S. Gundavelli Cisco R. Wakikawa Toyota ITC May 2012
Internet Engineering Task Force (IETF) Request for Comments: 6475 Category: Standards Track ISSN: 2070-1721 G. Keeni Cyber Solutions, Inc. K. Koide KDDI Corporation S. Gundavelli Cisco R. Wakikawa Toyota
More informationDo more, with less. When Simple isn t so Simple Using SNMP in Broadcast Facility control. -
When Simple isn t so Simple Using SNMP in Broadcast Facility control Do more, with less contact@audemat-aztec.com 1 Economic Challenges Do More, with Less contact@audemat-aztec.com 2 Do More, with Less
More informationIntended Status: Proposed Standard. Proxy Mobile IPv6 Management Information Base <draft-ietf-netlmm-pmipv6-mib-03.txt>
NETLMM Working Group INTERNET-DRAFT Intended Status: Proposed Standard Expires: February 19, 2011 Glenn M. Keeni Cyber Solutions Inc. K. Koide KDDI Corporation S. Gundavelli Cisco R. Wakikawa Toyota ITC
More informationNetwork Working Group Request for Comments: 2514 Category: Standards Track Cisco Systems K. Tesink Bellcore Editors February 1999
Network Working Group Request for Comments: 2514 Category: Standards Track M. Noto 3Com E. Spiegel Cisco Systems K. Tesink Bellcore Editors February 1999 Definitions of Textual Conventions and OBJECT-IDENTITIES
More informationSNMP. Simple Network Management Protocol. Chris Francois CS 417d Fall 1998
SNMP Simple Network Management Protocol Chris Francois CS 417d Fall 1998 cfrancois@acm.org What is Network Management? Basic tasks that fall under this category are: Configuration Management Keeping track
More informationDo more, with less Using SNMP in Broadcast Facility Control Miami Ennes conference 03/10/11
Do more, with less contact@audemat-aztec.com 1 Economic Challenges Do More, with Less contact@audemat-aztec.com 2 Broadcasters also finding ways to Economize Do More, with Less Connectivity new Pathways
More informationNetwork Working Group. Category: Standards Track Nortel Networks S. Routhier Integrated Systems Inc. B. Wijnen Lucent Technologies March 2000
Network Working Group Request for Comments: 2576 Category: Standards Track R. Frye CoSine Communications D. Levi Nortel Networks S. Routhier Integrated Systems Inc. B. Wijnen Lucent Technologies March
More informationN2 Binary Input/ BACnet Binary Input
Object Dictionary 1 N2 Binary Input/ BACnet Binary Input Introduction Note: The Johnson Controls Binary Input object is considered a BACnet Binary Input object, because it supports BACnet functionality.
More informationNetwork Working Group Request for Comments: 2320 Category: Standards Track Bay Networks, Inc. K. White IBM Corp. T. Kuo Bay Networks, Inc.
Network Working Group Request for Comments: 2320 Category: Standards Track M. Greene Xedia Corp. J. Luciani Bay Networks, Inc. K. White IBM Corp. T. Kuo Bay Networks, Inc. April 1998 Status of this Memo
More informationN2 Multistate Output/ BACnet Multistate Output
Object Dictionary 1 N2 Multistate Output/ BACnet Multistate Output Introduction Note: The Johnson Controls N2 Multistate Output object is considered a BACnet Multistate Output object because it supports
More informationPacketCable Signaling MIB Specification
PacketCable Signaling MIB Specification CLOSED Notice This PacketCable specification is the result of a cooperative effort undertaken at the direction of Cable Television Laboratories, Inc. for the benefit
More informationDraftETSI EN V1.1.3 ( )
Draft EN 301 486-1 V1.1.3 (1999-12) European Standard (Telecommunications series) Broadband Integrated Services Digital Network (B-ISDN); Digital Subscriber Signalling System No. two (DSS2) protocol; Connection
More informationTDX - SNMP Revision 02-01
TDX - SNMP Revision 02-01 Summary Status Approved by Revision 02-0 Page 1 of 17 Revision History Rev Date Author Description 00-01 2013-07-03 Erik Nielsen Draft. 00-02 2013-10-09 Erik Nielsen Draft 01-00
More informationETSI TS V7.0.0 ( )
TS 100 600 V7.0.0 (1999-08) Technical Specification Digital cellular telecommunications system (Phase 2+); Signalling requirements on interworking between the Integrated Services Digital Network (ISDN)
More informationN2 Analog Input/ BACnet Analog Input
Object Dictionary 1 N2 Analog Input/ BACnet Analog Input Introduction Note: The Johnson Controls N2 Analog Input object is considered a BACnet Analog Input object because it supports BACnet functionality.
More informationNetwork Working Group Request for Comments: 4069 Category: Standards Track PESA Switching Systems May 2005
Network Working Group Request for Comments: 4069 Category: Standards Track M. Dodge ECI Telecom B. Ray PESA Switching Systems May 2005 Definitions of Managed Object Extensions for Very High Speed Digital
More informationNetwork Management (NETW-1001)
Network Management (NETW-1001) Dr. Mohamed Abdelwahab Saleh IET-Networks, GUC Spring 2017 TOC 1 MIBs 2 Review Managed objects are the network components to be managed (monitored and/or configured). To
More informationETSI TS V9.3.0 ( )
TS 132 125 V9.3.0 (2012-03) Technical Specification Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Advanced
More informationInternet Engineering Task Force (IETF) B. Claise Cisco Systems, Inc. G. Muenz Technische Universitaet Muenchen April 2010
Internet Engineering Task Force (IETF) Request for Comments: 5815 Category: Standards Track ISSN: 2070-1721 T. Dietz, Ed. NEC Europe, Ltd. A. Kobayashi NTT PF Labs. B. Claise Cisco Systems, Inc. G. Muenz
More informationTechNote. XCAPI SNMP Support. October 14,
TechNote XCAPI SNMP Support October 14, 2014 www.te-systems.de Page 2 2.1 Installation............................................... 4 2.2 SNMP Applications.......................................... 5
More informationXerox CentreWare for HP OpenView NNM User Guide. Version 1.1
Xerox CentreWare for HP OpenView NNM User Guide Version 1.1 2000 by Xerox Corporation. All rights reserved. Copyright protection claimed includes all forms and matters of copyright material and information
More informationETSI TR V2.1.1 ( ) Technical Report
TR 183 050 V2.1.1 (2009-01) Technical Report Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Register of assigned protocol numbers and names 2 TR 183
More informationDo more, with less. - 1
Do more, with less contact@audemat-aztec.com 1 Economic Challenges Do More, with Less contact@audemat-aztec.com 2 Broadcasters also finding ways to Economize Do More, with Less Connectivity new Pathways
More informationSEHI Supports Management Module SM-CSI1020
SEHI Titlepage Supports Management Module SM-CSI1020 Device Management Copyright Notice Document 1012. Copyright 2003 by Aprisma Management Technologies, Inc. All rights reserved worldwide. Use, duplication,
More informationISO/IEC INTERNATIONAL STANDARD. Information technology Multimedia content description interface Part 5: Multimedia description schemes
INTERNATIONAL STANDARD ISO/IEC 15938-5 First edition 2003-05-15 Information technology Multimedia content description interface Part 5: Multimedia description schemes Technologies de l'information Interface
More informationNetwork Working Group Request For Comments: 1304 Editors Bell Communications Research February 1992
Network Working Group Request For Comments: 1304 T. Cox K. Tesink Editors Bell Communications Research February 1992 Definitions of Managed Objects for the SIP Interface Type Status of this Memo This RFC
More informationEUROPEAN ETS TELECOMMUNICATION October 1993 STANDARD
EUROPEAN ETS 300 287 TELECOMMUNICATION October 1993 STANDARD Source: ETSI TC-SPS Reference: DE/SPS-02005 ICS: 33.080 Key words: ISDN, Signalling System No.7, TCAP Integrated Services Digital Network (ISDN);
More informationETSI GS NFV-IFA 007 V2.1.1 ( )
GS NFV-IFA 007 V2.1.1 (2016-10) GROUP SPECIFICATION Network Functions Virtualisation (NFV); Management and Orchestration; Or-Vnfm reference point - Interface and Information Model Specification Disclaimer
More informationInternet Engineering Task Force (IETF) Category: Standards Track. S. Sivakumar Cisco Systems T. Taylor PT Taylor Consulting October 2015
Internet Engineering Task Force (IETF) Request for Comments: 7659 Category: Standards Track ISSN: 2070-1721 S. Perreault Jive Communications T. Tsou Huawei Technologies S. Sivakumar Cisco Systems T. Taylor
More informationInternet Engineering Task Force (IETF) Request for Comments: 8038 Category: Standards Track. S. B S Mojo Networks, Inc. C. McDowall.
Internet Engineering Task Force (IETF) Request for Comments: 8038 Category: Standards Track ISSN: 2070-1721 P. Aitken, Ed. Brocade B. Claise Cisco Systems, Inc. S. B S Mojo Networks, Inc. C. McDowall Brocade
More informationLecture 18: Network Management
Lecture 18: Network Management Prof. Shervin Shirmohammadi SITE, University of Ottawa Prof. Shervin Shirmohammadi CEG 4183 18-1 Objective Manage a network by managing its components: routers, bridges,
More informationCHAPTER 25 Management Resources
CHAPTER 25 Management Resources Acronyms... iii Chapter 25. Management Resources... 25-1 25.1 General... 25-1 25.2 Structure of Management Resources... 25-1 25.2.1 Public RFC-Based Management Resources...
More informationInternet Engineering Task Force (IETF) Request for Comments: ISSN: April 2014
Internet Engineering Task Force (IETF) M. Bakke Request for Comments: 7147 Dell Obsoletes: 4544 P. Venkatesen Category: Standards Track HCL Technologies ISSN: 2070-1721 April 2014 Abstract Definitions
More information