midcomRuleOperStatus

The actual status of the policy rule.  The
midcomRuleOperStatus object may have the following values:
              
- newEntry(1) indicates that the entry in the
  midcomRuleTable was created, but not modified yet.
  Such an entry needs to be filled with values specifying
  a request first.
              
- setting(2) indicates that the entry has been already
  modified after generating it, but no request was made
  yet.
              
- checkingRequest(3) indicates that midcomRuleAdminStatus
  has recently been set and that the MIDCOM-MIB
  implementation is currently checking the parameters of
  the request.  This is a transient state.  The value of
  this object will change to either incorrectRequest(4)
  or processingRequest(5) without any external
  interaction.  A MIDCOM-MIB implementation MAY return
  this value while checking request parameters.
              
- incorrectRequest(4) indicates that checking a request
  resulted in detecting an incorrect value in one of the
  objects containing request parameters.  The failure
  reason is indicated by the value of midcomRuleError.
              
- processingRequest(5) indicates that
  midcomRuleAdminStatus has recently been set and that
  the MIDCOM-MIB implementation is currently processing
  the request and trying to configure the middlebox
  accordingly.  This is a transient state.  The value of
  this object will change to either requestRejected(6),
  reserved(7), or enabled(8) without any external
  interaction.  A MIDCOM-MIB implementation MAY return
  this value while processing a request.
              
- requestRejected(6) indicates that a request to establish
              
  a policy rule specified by the entry was rejected.  The
  reason for rejection is indicated by the value of
  midcomRuleError.
              
- reserved(7) indicates that the entry describes an
  established policy reserve rule.
  These values of MidcomRuleEntry are meaningful
  for a reserved policy rule:
      - midcomRuleMaxIdleTime
      - midcomRuleInterface
      - midcomRuleTransportProtocol
      - midcomRulePortRange
      - midcomRuleInternalIpVersion
      - midcomRuleExternalIpVersion
      - midcomRuleInternalIpAddr
      - midcomRuleInternalIpPrefixLength
      - midcomRuleInternalPort
      - midcomRuleOutsideIpAddr
      - midcomRuleOutsidePort
      - midcomRuleLifetime
              
- enabled(8) indicates that the entry describes an
  established policy enable rule.
  These values of MidcomRuleEntry are meaningful
  for an enabled policy rule:
              
      - midcomRuleFlowDirection
      - midcomRuleInterface
      - midcomRuleMaxIdleTime
      - midcomRuleTransportProtocol
      - midcomRulePortRange
      - midcomRuleInternalIpVersion
      - midcomRuleExternalIpVersion
      - midcomRuleInternalIpAddr
      - midcomRuleInternalIpPrefixLength
      - midcomRuleInternalPort
      - midcomRuleExternalIpAddr
      - midcomRuleExternalIpPrefixLength
      - midcomRuleExternalPort
      - midcomRuleInsideIpAddr
      - midcomRuleInsidePort
      - midcomRuleOutsideIpAddr
      - midcomRuleOutsidePort
      - midcomRuleLifetime
              
- timedOut(9) indicates that the lifetime of a previously
  established policy rule has expired and that the policy
  rule is terminated for this reason.
              
- terminatedOnRequest(10) indicates that a previously
  established policy rule was terminated by an SNMP
  manager setting the midcomRuleLifetime to 0 or
  setting midcomGroupLifetime to 0.
              
- terminated(11) indicates that a previously established
  policy rule was terminated by the MIDCOM-MIB
  implementation for a reason other than lifetime
  expiration or an explicit request from a MIDCOM client.
              
- genericError(12) indicates that the policy rule
  specified by the entry is not established due to
  an error condition not listed above.
              
The states timedOut(9), terminatedOnRequest(10), and
terminated(11) are referred to as termination states.
              
The states incorrectRequest(4), requestRejected(6),
and genericError(12) are referred to as error states.
              
The checkingRequest(3) and processingRequest(5)
states are transient states, which will lead to either
one of the error states or the reserved(7) state or the
enabled(8) state.  MIDCOM-MIB implementations MAY return
these values when checking or processing requests.

MIB

MIDCOM-MIB

OID

.1.3.6.1.2.1.171.1.1.3.1.5

Type

column

Access

readonly

Status

current

Parent

midcomRuleEntry

Table

midcomRuleTable

Siblings

25