midcomRuleLifetime

MIDCOM-MIB · .1.3.6.1.2.1.171.1.1.3.1.26

Object

column r/w seconds SNMPv2-SMIUnsigned32
The remaining lifetime in seconds of this policy rule.
              
Lifetime of a policy rule starts when object
midcomRuleOperStatus in the same entry enters either
state reserved(7) or state enabled(8).
              
This object is used as input to a request for establishing
a policy rule as well as for indicating the properties of
an established policy rule.
              
If object midcomRuleOperStatus of the same entry has a
value of either newEntry(1) or setting(2), then this
object can be written by a manager in order to specify
the requested lifetime of a policy rule to be established.
              
If object midcomRuleOperStatus of the same entry has a
value of either reserved(7) or enabled(8), then this
object indicates the (continuously decreasing) remaining
lifetime of the established policy rule.  Note that when
entering state reserved(7) or enabled(8), the MIDCOM-MIB
implementation can choose a lifetime shorter than the one
requested.
              
Unlike other parameters of the policy rule, this parameter
can still be written in state reserved(7) and enabled(8).
              
Writing to this object is processed by the MIDCOM-MIB
implementation by choosing a lifetime value that is
greater than 0 and less than or equal to the minimum of
the requested value and the value specified by object
midcomConfigMaxLifetime:
              
 0 <= lt_granted <= MINIMUM(lt_requested, lt_maximum)
              
where:
   - lt_granted is the actually granted lifetime by the
     MIDCOM-MIB implementation
   - lt_requested is the requested lifetime of the MIDCOM
     client
   - lt_maximum is the value of object
     midcomConfigMaxLifetime
              
SNMP SET requests to this object may be rejected or the
value of the object after an accepted SET operation may be
less than the value that was contained in the SNMP SET
request.
              
Successfully writing a value of 0 terminates the policy
rule.  Note that after a policy rule is terminated, still
the entry will exist as long as indicated by the value of
midcomRuleStorageTime.
              
Writing to this object in any state other than
newEntry(1), setting(2), reserved(7), or enabled(7)
will always fail with an 'inconsistentValue' error.
              
Note that this error code is SNMP specific.  If the MIB
module is used with other protocols than SNMP, errors with
similar semantics specific to those protocols should be
returned.
              
If object midcomRuleOperStatus of the same entry has a
value other than newEntry(1), setting(2), reserved(7), or
enabled(8), then the value of this object is irrelevant.

Context

MIB
MIDCOM-MIB
OID
.1.3.6.1.2.1.171.1.1.3.1.26
Type
column
Access
readwrite
Status
current
Units
seconds
Parent
midcomRuleEntry
Table
midcomRuleTable
Siblings
25

Syntax

seconds SNMPv2-SMIUnsigned32
Source
SNMPv2-SMIUnsigned32
Base type
Unsigned32

Values & Constraints

Type Constraints
range: 0..4294967295

Related Objects

Sibling Objects