< draft-ietf-disman-express-mib-11.txt   draft-ietf-disman-express-mib-12.txt >
Internet Draft Distributed Management Expression MIB 4 February 2000 Network Working Group Editor of this version:
Internet-Draft Ramanathan R. Kavasseri
Expires December 2000 Cisco Systems, Inc.
Author of previous version:
Bob Stewart
12 June 2000
Distributed Management Expression MIB Distributed Management Expression MIB
4 February 2000 draft-ietf-disman-express-mib-12.txt
draft-ietf-disman-express-mib-11.txt
Bob Stewart
Cisco Systems, Inc.
Ramanathan R. Kavasseri
Cisco Systems, Inc.
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026. provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Task Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other groups Force (IETF), its areas, and its working groups. Note that other groups
may also distribute working documents as Internet-Drafts. may also distribute working documents as Internet-Drafts.
skipping to change at page 1, line 42 skipping to change at page 2, line ?
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Distribution of this document is unlimited. Please send comments to the Distribution of this document is unlimited. Please send comments to the
Distributed Management Working Group, <disman@dorothy.BMC.com>. Distributed Management Working Group, <disman@dorothy.BMC.com>.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
1. Abstract 1. Abstract
This memo defines a portion of the Management Information Base (MIB) for This memo defines a portion of the Management Information Base (MIB) for
use with network management protocols in the Internet community. In use with network management protocols in the Internet community. In
particular, it describes managed objects used for managing expressions particular, it describes managed objects used for managing expressions
of MIB objects. The results of these expressions become MIB objects of MIB objects. The results of these expressions become MIB objects
usable like any other MIB object, such as for the test condition for usable like any other MIB object, such as for the test condition for
declaring an event. declaring an event.
skipping to change at page 4, line 32 skipping to change at page 4, line 32
complex, high-level application, considerably different from simple complex, high-level application, considerably different from simple
instrumentation for a communication driver or a protocol. The MIB is instrumentation for a communication driver or a protocol. The MIB is
appropriate in a relatively powerful, resource-rich managed system and appropriate in a relatively powerful, resource-rich managed system and
not necessarily in a severely limited environment. not necessarily in a severely limited environment.
Nevertheless, due to dependencies from the Event MIB [RFCEventMIB] and Nevertheless, due to dependencies from the Event MIB [RFCEventMIB] and
the need to support as low-end a system as possible, the Expression MIB the need to support as low-end a system as possible, the Expression MIB
can be somewhat stripped down for lower-power, lower-resource can be somewhat stripped down for lower-power, lower-resource
implementations, as described in the Subsets section, below. implementations, as described in the Subsets section, below.
Implementation of the Expression MIB in an managed system led to the Implementation of the Expression MIB in a managed system led to the
addition of objects that may not have been necessary in an application addition of objects that may not have been necessary in an application
environment with complete knowledge of compiled MIB definitions. This environment with complete knowledge of compiled MIB definitions. This
is appropriate since implementation must be possible within typical is appropriate since implementation must be possible within typical
managed systems with some constraints on system resources. managed systems with some constraints on system resources.
3.1. Usage 3.1. Usage
On managed systems that can afford the overhead, the Expression MIB is a On managed systems that can afford the overhead, the Expression MIB is a
way to create new, customized MIB objects for monitoring. Although way to create new, customized MIB objects for monitoring. Although
these can save some network traffic and overhead on management systems, these can save some network traffic and overhead on management systems,
skipping to change at page 8, line 37 skipping to change at page 8, line 37
3.5.1. Resource 3.5.1. Resource
The resource section has objects to manage resource usage by wildcarded The resource section has objects to manage resource usage by wildcarded
delta expressions, a potential major consumer of CPU and memory. delta expressions, a potential major consumer of CPU and memory.
3.5.2. Definition 3.5.2. Definition
The definition section contains the tables that define expressions. The definition section contains the tables that define expressions.
The expression table, indexed by expression name, contains those The expression table, indexed by expression owner and expression name,
parameters that apply to the entire expression, such as the expression contains those parameters that apply to the entire expression, such as
itself, the data type of the result, and the sampling interval if it the expression itself, the data type of the result, and the sampling
contains delta or change values. interval if it contains delta or change values.
The object table, indexed by expression name and object index within The object table, indexed by expression owner, expression name and
each expression, contains the parameters that apply to the individual object index within each expression, contains the parameters that apply
objects that go into the expression, including the object identifier, to the individual objects that go into the expression, including the
sample type, discontinuity indicator, and such. object identifier, sample type, discontinuity indicator, and such.
3.5.3. Value 3.5.3. Value
The value section contains the values of evaluated expressions. The value section contains the values of evaluated expressions.
The value table, indexed by expression name and instance fragment The value table, indexed by expression name and instance fragment
contains a "discriminated union" of evaluated expression results. For a contains a "discriminated union" of evaluated expression results. For a
given expression only one of the columns is instantiated, depending on given expression only one of the columns is instantiated, depending on
the result data type for the expression. The instance fragment is a the result data type for the expression. The instance fragment is a
constant or the final section of the object identifier that filled in a constant or the final section of the object identifier that filled in a
skipping to change at page 10, line 11 skipping to change at page 10, line 11
INDEX { townIndex, personIndex } INDEX { townIndex, personIndex }
In our friendly application we may have entered our expression as: In our friendly application we may have entered our expression as:
100 * townPersonBlessings.976.* / personBlessings.* 100 * townPersonBlessings.976.* / personBlessings.*
What goes in expExpression is: What goes in expExpression is:
100*$1/$2 100*$1/$2
For example purposes we'll use some slightly far-fetched OIDs, but the For example purposes we'll use some slightly far-fetched OIDs. The
weirdity won't matter. The People MIB is 1.3.6.1.99.7 and the Town MIB People MIB is 1.3.6.1.99.7 and the Town MIB is 1.3.6.1.99.11, so for our
is 1.3.6.1.99.11, so for our two counters the OIDs are: two counters the OIDs are:
personBlessings 1.3.6.1.99.7.1.3.1.4 personBlessings 1.3.6.1.99.7.1.3.1.4
townPersonBlessings 1.3.6.1.99.11.1.2.1.9 townPersonBlessings 1.3.6.1.99.11.1.2.1.9
The rule for wildcards is that all the wildcarded parts have to match The rule for wildcards is that all the wildcarded parts have to match
exactly. In this case that means we have to hardwire the town and only exactly. In this case that means we have to hardwire the town and only
the personIndex can be wildcarded. So our values for expObjectID are: the personIndex can be wildcarded. So our values for expObjectID are:
1.3.6.1.99.7.1.3.1.4 1.3.6.1.99.7.1.3.1.4
1.3.6.1.99.11.1.2.1.9.976 1.3.6.1.99.11.1.2.1.9.976
skipping to change at page 11, line 43 skipping to change at page 11, line 43
For notational clarity, in the rest of this document, a string in quotes For notational clarity, in the rest of this document, a string in quotes
as part of the object instance indicates the value that would actually as part of the object instance indicates the value that would actually
be one subidentifier per byte. The objects all belong to owner "me". be one subidentifier per byte. The objects all belong to owner "me".
Also for clarity OIDs are expressed as the object descriptor and Also for clarity OIDs are expressed as the object descriptor and
instance. In fact they must be supplied numerically, with all instance. In fact they must be supplied numerically, with all
subidentifiers in place before the part for the particular object and subidentifiers in place before the part for the particular object and
instance. instance.
What the user must set in expExpressionTable: What the user would set in expExpressionTable:
expExpression.2."me".4."hard" = "$1==1" expExpression.2."me".4."hard" = "$1==1"
expExpressionValueType.2."me".4."hard" = unsigned32 expExpressionValueType.2."me".4."hard" = unsigned32
expExpressionRowStatus.2."me"4."hard" = 'active' expExpressionRowStatus.2."me"4."hard" = 'active'
expExpression.2."me".4."util" = "($1+$2)*800/$4/$3" expExpression.2."me".4."util" = "($1+$2)*800/$4/$3"
expExpressionValueType.2."me".4."util" = integer32 expExpressionValueType.2."me".4."util" = integer32
expExpressionDeltaInterval.2."me".4."util" = 6 expExpressionDeltaInterval.2."me".4."util" = 6
expExpressionRowStatus.2."me"4."util" = 'active' expExpressionRowStatus.2."me"4."util" = 'active'
What the user must set in expObjectTable: What the user would set in expObjectTable:
expObjectID.2."me".4."hard".1 = ifConnectorPresent expObjectID.2."me".4."hard".1 = ifConnectorPresent
expObjectWildcard.2."me".4."hard".1 = 'true' expObjectWildcard.2."me".4."hard".1 = 'true'
expObjectSampleType.2."me".4."hard".1 = 'absoluteValue' expObjectSampleType.2."me".4."hard".1 = 'absoluteValue'
expObjectRowStatus.2."me".4."hard".1 = 'active' expObjectRowStatus.2."me".4."hard".1 = 'active'
expObjectID.2."me".4."util".1 = ifInOctets expObjectID.2."me".4."util".1 = ifInOctets
expObjectWildcard.2."me".4."util".1 = 'true' expObjectWildcard.2."me".4."util".1 = 'true'
expObjectSampleType.2."me".4."util".1 = 'deltaValue' expObjectSampleType.2."me".4."util".1 = 'deltaValue'
expObjectConditional.2."me".4."util".1 = expObjectConditional.2."me".4."util".1 =
skipping to change at page 14, line 13 skipping to change at page 14, line 13
watch for overutilization of all hardware network connections. watch for overutilization of all hardware network connections.
4. Definitions 4. Definitions
DISMAN-EXPRESSION-MIB DEFINITIONS ::= BEGIN DISMAN-EXPRESSION-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Integer32, Gauge32, Unsigned32, Integer32, Gauge32, Unsigned32,
Counter32, Counter64, IpAddress, Counter32, Counter64, IpAddress,
TimeTicks, mib-2 FROM SNMPv2-SMI TimeTicks, mib-2, zeroDotZero FROM SNMPv2-SMI
RowStatus, TruthValue, TimeStamp FROM SNMPv2-TC RowStatus, TruthValue, TimeStamp FROM SNMPv2-TC
sysUpTime FROM SNMPv2-MIB sysUpTime FROM SNMPv2-MIB
SnmpAdminString FROM SNMP-FRAMEWORK-MIB SnmpAdminString FROM SNMP-FRAMEWORK-MIB
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
dismanExpressionMIB MODULE-IDENTITY dismanExpressionMIB MODULE-IDENTITY
LAST-UPDATED "9910220000Z" LAST-UPDATED "200006120000Z" -- 12 June 2000
ORGANIZATION "IETF Distributed Management Working Group" ORGANIZATION "IETF Distributed Management Working Group"
CONTACT-INFO "Ramanathan Kavasseri CONTACT-INFO "Ramanathan Kavasseri
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive, 170 West Tasman Drive,
San Jose CA 95134-1706. San Jose CA 95134-1706.
Phone: +1 408 527 2446 Phone: +1 408 527 2446
Email: ramk@cisco.com" Email: ramk@cisco.com"
DESCRIPTION DESCRIPTION
"The MIB module for defining expressions of MIB objects for "The MIB module for defining expressions of MIB objects for
management purposes." management purposes."
-- Revision History -- Revision History
REVISION "9910220000Z" -- 22 October 1999 REVISION "200006120000Z" -- 12 June 2000
DESCRIPTION "This is the initial version of this MIB. DESCRIPTION "This is the initial version of this MIB.
Published as RFC xxxxx" Published as RFC xxxx"
::= { mib-2 xx } -- final assignment by IANA at publication time ::= { mib-2 xx } -- final assignment by IANA at publication time
dismanExpressionMIBObjects OBJECT IDENTIFIER ::= { dismanExpressionMIB 1 } dismanExpressionMIBObjects OBJECT IDENTIFIER ::= { dismanExpressionMIB 1 }
expResource OBJECT IDENTIFIER ::= { dismanExpressionMIBObjects 1 } expResource OBJECT IDENTIFIER ::= { dismanExpressionMIBObjects 1 }
expDefine OBJECT IDENTIFIER ::= { dismanExpressionMIBObjects 2 } expDefine OBJECT IDENTIFIER ::= { dismanExpressionMIBObjects 2 }
expValue OBJECT IDENTIFIER ::= { dismanExpressionMIBObjects 3 } expValue OBJECT IDENTIFIER ::= { dismanExpressionMIBObjects 3 }
-- --
-- Resource Control -- Resource Control
skipping to change at page 33, line 11 skipping to change at page 33, line 11
"The value 'timeTicks' indicates the expObjectDeltaDiscontinuityID "The value 'timeTicks' indicates the expObjectDeltaDiscontinuityID
of this row is of syntax TimeTicks. The value 'timeStamp' indicates of this row is of syntax TimeTicks. The value 'timeStamp' indicates
syntax TimeStamp. The value 'dateAndTime indicates syntax syntax TimeStamp. The value 'dateAndTime indicates syntax
DateAndTime. DateAndTime.
This object is instantiated only if expObjectSampleType is This object is instantiated only if expObjectSampleType is
'deltaValue' or 'changedValue'." 'deltaValue' or 'changedValue'."
DEFVAL { timeTicks } DEFVAL { timeTicks }
::= { expObjectEntry 7 } ::= { expObjectEntry 7 }
zeroDotZero OBJECT IDENTIFIER ::= { 0 0 }
expObjectConditional OBJECT-TYPE expObjectConditional OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The OBJECT IDENTIFIER (OID) of an object that overrides "The OBJECT IDENTIFIER (OID) of an object that overrides
whether the instance of expObjectID is to be considered whether the instance of expObjectID is to be considered
usable. If the value of the object at expObjectConditional usable. If the value of the object at expObjectConditional
is 0 or not instantiated, the object at expObjectID is is 0 or not instantiated, the object at expObjectID is
treated as if it is not instantiated. In other words, treated as if it is not instantiated. In other words,
 End of changes. 14 change blocks. 
31 lines changed or deleted 26 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/