MIDCOM-MIB

File: MIDCOM-MIB.mib (89798 bytes)

Imported modules

SNMPv2-SMI SNMPv2-TC SNMPv2-CONF
SNMP-FRAMEWORK-MIB INET-ADDRESS-MIB IF-MIB
NAT-MIB

Imported symbols

MODULE-IDENTITY OBJECT-TYPE NOTIFICATION-TYPE
Unsigned32 Counter32 Gauge32
mib-2 TEXTUAL-CONVENTION TruthValue
StorageType RowStatus MODULE-COMPLIANCE
OBJECT-GROUP NOTIFICATION-GROUP SnmpAdminString
InetAddressType InetAddress InetPortNumber
InetAddressPrefixLength InterfaceIndexOrZero NatBindIdOrZero

Defined Types

MidcomRuleEntry  
SEQUENCE    
  midcomRuleOwner SnmpAdminString
  midcomRuleIndex Unsigned32
  midcomRuleAdminStatus INTEGER
  midcomRuleOperStatus INTEGER
  midcomRuleStorageType StorageType
  midcomRuleStorageTime Unsigned32
  midcomRuleError SnmpAdminString
  midcomRuleInterface InterfaceIndexOrZero
  midcomRuleFlowDirection INTEGER
  midcomRuleMaxIdleTime Unsigned32
  midcomRuleTransportProtocol Unsigned32
  midcomRulePortRange INTEGER
  midcomRuleInternalIpVersion InetAddressType
  midcomRuleExternalIpVersion InetAddressType
  midcomRuleInternalIpAddr InetAddress
  midcomRuleInternalIpPrefixLength InetAddressPrefixLength
  midcomRuleInternalPort InetPortNumber
  midcomRuleExternalIpAddr InetAddress
  midcomRuleExternalIpPrefixLength InetAddressPrefixLength
  midcomRuleExternalPort InetPortNumber
  midcomRuleInsideIpAddr InetAddress
  midcomRuleInsidePort InetPortNumber
  midcomRuleOutsideIpAddr InetAddress
  midcomRuleOutsidePort InetPortNumber
  midcomRuleLifetime Unsigned32
  midcomRuleRowStatus RowStatus

MidcomGroupEntry  
SEQUENCE    
  midcomGroupIndex Unsigned32
  midcomGroupLifetime Unsigned32

MidcomConfigIfEntry  
SEQUENCE    
  midcomConfigIfIndex InterfaceIndexOrZero
  midcomConfigIfBits BITS
  midcomConfigIfEnabled TruthValue

MidcomConfigFirewallEntry  
SEQUENCE    
  midcomConfigFirewallIndex InterfaceIndexOrZero
  midcomConfigFirewallGroupId SnmpAdminString
  midcomConfigFirewallPriority Unsigned32

MidcomNatBindMode  
An indicator of the kind of NAT resources used by a policy rule. This definition corresponds to the definition of NatBindMode in the NAT-MIB (RFC 4008). Value none(3) can be used to indicate that the policy rule does not use any NAT binding.
TEXTUAL-CONVENTION    
  INTEGER addressBind(1), addressPortBind(2), none(3)  

MidcomNatSessionIdOrZero  
A unique ID that is assigned to each NAT session by a NAT implementation. This definition corresponds to the definition of NatSessionId in the NAT-MIB (RFC 4008). Value 0 can be used to indicate that the policy rule does not use any NAT binding.
TEXTUAL-CONVENTION    
  Unsigned32  

MidcomResourceEntry  
SEQUENCE    
  midcomRscNatInternalAddrBindMode MidcomNatBindMode
  midcomRscNatInternalAddrBindId NatBindIdOrZero
  midcomRscNatInsideAddrBindMode MidcomNatBindMode
  midcomRscNatInsideAddrBindId NatBindIdOrZero
  midcomRscNatSessionId1 MidcomNatSessionIdOrZero
  midcomRscNatSessionId2 MidcomNatSessionIdOrZero
  midcomRscFirewallRuleId Unsigned32

Defined Values

midcomMIB 1.3.6.1.2.1.171
This MIB module defines a set of basic objects for configuring middleboxes, such as firewalls and network address translators, in order to enable communication across these devices. Managed objects defined in this MIB module are structured in three kinds of objects: - transaction objects required according to the MIDCOM protocol requirements defined in RFC 3304 and according to the MIDCOM protocol semantics defined in RFC 3989, - configuration objects that can be used for retrieving or setting parameters of the implementation of transaction objects, - optional monitoring objects that provide information about used resource and statistics The transaction objects are organized in two subtrees: - objects modeling MIDCOM policy rules in the midcomRuleTable - objects modeling MIDCOM policy rule groups in the midcomGroupTable Note that typically, configuration objects are not intended to be written by MIDCOM clients. In general, write access to these objects needs to be restricted more strictly than write access to objects in the transaction subtrees. Copyright (C) The Internet Society (2008). This version of this MIB module is part of RFC 5190; see the RFC itself for full legal notices.
MODULE-IDENTITY    

midcomNotifications 1.3.6.1.2.1.171.0
OBJECT IDENTIFIER    

midcomObjects 1.3.6.1.2.1.171.1
OBJECT IDENTIFIER    

midcomConformance 1.3.6.1.2.1.171.2
OBJECT IDENTIFIER    

midcomTransaction 1.3.6.1.2.1.171.1.1
OBJECT IDENTIFIER    

midcomConfig 1.3.6.1.2.1.171.1.2
OBJECT IDENTIFIER    

midcomMonitoring 1.3.6.1.2.1.171.1.3
OBJECT IDENTIFIER    

midcomRuleTable 1.3.6.1.2.1.171.1.1.3
This table lists policy rules. It is indexed by the midcomRuleOwner, the midcomGroupIndex, and the midcomRuleIndex. This implies that a rule is a member of exactly one group and that group membership cannot be changed. Entries can be deleted by writing to midcomGroupLifetime or midcomRuleLifetime and potentially also to midcomRuleStorageTime.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    MidcomRuleEntry

midcomRuleEntry 1.3.6.1.2.1.171.1.1.3.1
An entry describing a particular MIDCOM policy rule.
Status: current Access: not-accessible
OBJECT-TYPE    
  MidcomRuleEntry  

midcomRuleOwner 1.3.6.1.2.1.171.1.1.3.1.1
The manager who owns this row in the midcomRuleTable. This object SHOULD uniquely identify an authenticated MIDCOM client. This object is part of the table index to allow for the use of the SNMPv3 View-based Access Control Model (VACM, RFC 3415).
Status: current Access: not-accessible
OBJECT-TYPE    
  SnmpAdminString Size(0..32)  

midcomRuleIndex 1.3.6.1.2.1.171.1.1.3.1.3
The value of this object must be unique in combination with the values of the objects midcomRuleOwner and midcomGroupIndex in this row.
Status: current Access: not-accessible
OBJECT-TYPE    
  Unsigned32 1..4294967295  

midcomRuleAdminStatus 1.3.6.1.2.1.171.1.1.3.1.4
The value of this object indicates the desired status of the policy rule. See the definition of midcomRuleOperStatus for a description of the values. When a midcomRuleEntry is created without explicitly setting this object, its value will be notSet(3). However, a SET request can only set this object to either reserve(1) or enable(2). Attempts to set this object to notSet(3) 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. When the midcomRuleAdminStatus object is set, then the MIDCOM-MIB implementation will try to read the respective relevant objects of the entry and try to achieve the corresponding midcomRuleOperStatus. Setting midcomRuleAdminStatus to value reserve(1) when object midcomRuleOperStatus has a value of reserved(7) does not have any effect on the policy rule. Setting midcomRuleAdminStatus to value enable(2) when object midcomRuleOperStatus has a value of enabled(8) does not have any effect on the policy rule. Depending on whether the midcomRuleAdminStatus is set to reserve(1) or enable(2), several objects must be set in advance. They serve as parameters of the policy rule to be established. When object midcomRuleAdminStatus is set to reserve(1), then the following objects in the same entry are of relevance: - midcomRuleInterface - midcomRuleTransportProtocol - midcomRulePortRange - midcomRuleInternalIpVersion - midcomRuleExternalIpVersion - midcomRuleInternalIpAddr - midcomRuleInternalIpPrefixLength - midcomRuleInternalPort - midcomRuleLifetime MIDCOM-MIB implementation may also consider the value of object midcomRuleMaxIdleTime when establishing a reserve rule. When object midcomRuleAdminStatus is set to enable(2), then the following objects in the same entry are of relevance: - midcomRuleInterface - midcomRuleFlowDirection - midcomRuleMaxIdleTime - midcomRuleTransportProtocol - midcomRulePortRange - midcomRuleInternalIpVersion - midcomRuleExternalIpVersion - midcomRuleInternalIpAddr - midcomRuleInternalIpPrefixLength - midcomRuleInternalPort - midcomRuleExternalIpAddr - midcomRuleExternalIpPrefixLength - midcomRuleExternalPort - midcomRuleLifetime When retrieved, the object returns the last set value. If no value has been set, it returns the default value notSet(3).
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER reserve(1), enable(2), notSet(3)  

midcomRuleOperStatus 1.3.6.1.2.1.171.1.1.3.1.5
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.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER newEntry(1), setting(2), checkingRequest(3), incorrectRequest(4), processingRequest(5), requestRejected(6), reserved(7), enabled(8), timedOut(9), terminatedOnRequest(10), terminated(11), genericError(12)  

midcomRuleStorageType 1.3.6.1.2.1.171.1.1.3.1.6
When retrieved, this object returns the storage type of the policy rule. Writing to this object can change the storage type of the particular row from volatile(2) to nonVolatile(3) or vice versa. Attempts to set this object to permanent 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 midcomRuleStorageType has the value permanent(4), then all objects in this row whose MAX-ACCESS value is read-create must be read-only.
Status: current Access: read-create
OBJECT-TYPE    
  StorageType  

midcomRuleStorageTime 1.3.6.1.2.1.171.1.1.3.1.7
The value of this object specifies how long this row can exist in the midcomRuleTable after the midcomRuleOperStatus switched to a termination state or to an error state. This object returns the remaining time that the row may exist before it is aged out. After expiration or termination of the context, the value of this object ticks backwards. The entry in the midcomRuleTable is destroyed when the value reaches 0. The value of this object may be set in order to increase or reduce the remaining time that the row may exist. Setting the value to 0 will destroy this entry as soon as the midcomRuleOperStatus switched to a termination state or to an error state. Note that there is no guarantee that the row is stored as long as this object indicates. At any time, the MIDCOM- MIB implementation may decide to remove a row describing a terminated policy rule before the storage time of the corresponding row in the midcomRuleTable reaches the value of 0. In this case, the information stored in this row is not available anymore. If object midcomRuleStorageType indicates that the policy rule has the storage type permanent(4), then this object has a constant value of 4294967295.
Status: current Access: read-create
OBJECT-TYPE    
  Unsigned32  

midcomRuleError 1.3.6.1.2.1.171.1.1.3.1.8
This object contains a descriptive error message if the transition into the operational status reserved(7) or enabled(8) failed. Implementations must reset the error message to a zero-length string when a new attempt to change the policy rule status to reserved(7) or enabled(8) is started. RECOMMENDED values to be returned in particular cases include - 'lack of IP addresses' - 'lack of port numbers' - 'lack of resources' - 'specified NAT interface does not exist' - 'specified NAT interface does not support NAT' - 'conflict with already existing policy rule' - 'no internal IP wildcarding allowed' - 'no external IP wildcarding allowed' The semantics of these error messages and the corresponding behavior of the MIDCOM-MIB implementation are specified in sections 2.3.9 and 2.3.10 of RFC 3989.
Status: current Access: read-only
OBJECT-TYPE    
  SnmpAdminString  

midcomRuleInterface 1.3.6.1.2.1.171.1.1.3.1.9
This object indicates the IP interface for which enforcement of a policy rule is requested or performed, respectively. The interface is identified by its index in the ifTable (see IF-MIB in RFC 2863). If the object has a value of 0, then no particular interface is indicated. 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 the value newEntry(1) or setting(2), then this object can be written by a manager in order to request its preference concerning the interface at which it requests NAT service. The default value of 0 indicates that the manager does not have a preferred interface or does not have sufficient topology information for specifying one. Writing to this object in any state other than newEntry(1) or setting(2) 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 the value reserved(7) or enabled(8), then this object indicates the interface at which NAT service for this rule is performed. If NAT service is not required for enforcing the policy rule, then the value of this object is 0. Also, if the MIDCOM-MIB implementation cannot indicate an interface, because it does not have this information or because NAT service is not offered at a particular single interface, then the value of the object is 0. Note that the index of a particular interface in the ifTable may change after a re-initialization of the middlebox, for example, after adding another interface to it. In such a case, the value of this object may change, but the interface referred to by the MIDCOM-MIB MUST still be the same. If, after a re-initialization of the middlebox, the interface referred to before re-initialization cannot be uniquely mapped anymore to a particular entry in the ifTable, then the value of object midcomRuleOperStatus of the same entry MUST be changed to terminated(11). 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.
Status: current Access: read-create
OBJECT-TYPE    
  InterfaceIndexOrZero  

midcomRuleFlowDirection 1.3.6.1.2.1.171.1.1.3.1.10
This parameter specifies the direction of enabled communication, either inbound(1), outbound(2), or biDirectional(3). The semantics of this object depends on the protocol the rule relates to. If the rule is independent of the transport protocol (midcomRuleTransportProtocol has a value of 0) or if the transport protocol is UDP, then the value of midcomRuleFlowDirection indicates the direction of packets traversing the middlebox. In this case, value inbound(1) indicates that packets are traversing from outside to inside, value outbound(2) indicates that packets are traversing from inside to outside. For both values, inbound(1) and outbound(2) packets can traverse the middlebox only unidirectional. A bidirectional flow is indicated by value biDirectional(3). If the transport protocol is TCP, the packet flow is always bidirectional, but the value of midcomRuleFlowDirection indicates that: - inbound(1): bidirectional TCP packet flow. First packet, with TCP SYN flag set, must arrive at an outside interface of the middlebox. - outbound(2): bidirectional TCP packet flow. First packet, with TCP SYN flag set, must arrive at an inside interface of the middlebox. - biDirectional(3): bidirectional TCP packet flow. First packet, with TCP SYN flag set, may arrive at an inside or an outside interface of the middlebox. This object is used as input to a request for establishing a policy enable 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), setting(2), or reserved(7), then this object can be written by a manager in order to specify a requested direction to be enabled by a policy rule. Writing to this object in any state other than newEntry(1), setting(2), or reserved(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 the value enabled(8), then this object indicates the enabled flow direction. 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.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER inbound(1), outbound(2), biDirectional(3)  

midcomRuleMaxIdleTime 1.3.6.1.2.1.171.1.1.3.1.11
Maximum idle time of the policy rule in seconds. If no packet to which the policy rule applies passes the middlebox for the specified midcomRuleMaxIdleTime, then the policy rule enters the termination state timedOut(9). A value of 0 indicates that the policy does not require an individual idle time and that instead, a default idle time chosen by the middlebox is used. A value of 4294967295 ( = 2^32 - 1 ) indicates that the policy does not time out if it is idle. This object is used as input to a request for establishing a policy enable 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), setting(2), or reserved(7), then this object can be written by a manager in order to specify a maximum idle time for the policy rule to be requested. Writing to this object in any state others than newEntry(1), setting(2), or reserved(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 the value enabled(8), then this object indicates the maximum idle time of the policy rule. Note that even if a maximum idle time greater than zero was requested, the middlebox may not be able to support maximum idle times and set the value of this object to zero when entering state enabled(8). 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.
Status: current Access: read-create
OBJECT-TYPE    
  Unsigned32  

midcomRuleTransportProtocol 1.3.6.1.2.1.171.1.1.3.1.12
The transport protocol. Valid values for midcomRuleTransportProtocol other than zero are defined at: http://www.iana.org/assignments/protocol-numbers 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 a requested transport protocol. If translation of an IP address only is requested, then this object must have the default value 0. Writing to this object in any state other than newEntry(1) or setting(2) 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 the value reserved(7) or enabled(8), then this object indicates which transport protocol is enforced by this policy rule. A value of 0 indicates a rule acting on IP addresses only. 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.
Status: current Access: read-create
OBJECT-TYPE    
  Unsigned32 0..255  

midcomRulePortRange 1.3.6.1.2.1.171.1.1.3.1.13
The range of port numbers. 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. It is relevant to the operation of the MIDCOM-MIB implementation only if the value of object midcomTransportProtocol in the same entry has a value other than 0. If object midcomRuleOperStatus of the same entry has the value newEntry(1) or setting(2), then this object can be written by a manager in order to specify the requested size of the port range. With single(1) just a single port number is requested, with pair(2) a consecutive pair of port numbers is requested with the lower number being even. Requesting a consecutive pair of port numbers may be used by RTP [RFC3550] and may even be required to support older RTP applications. Writing to this object in any state other than newEntry(1), setting(2) or reserved(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 of either reserved(7) or enabled(8), then this object will have the value that it had before the transition to this state. 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.
Status: current Access: read-create
OBJECT-TYPE    
  INTEGER single(1), pair(2)  

midcomRuleInternalIpVersion 1.3.6.1.2.1.171.1.1.3.1.14
IP version of the internal address (A0) and the inside address (A1). Allowed values are ipv4(1), ipv6(2), ipv4z(3), and ipv6z(4). 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 the value newEntry(1) or setting(2), then this object can be written by a manager in order to specify the IP version required at the inside of the middlebox. Writing to this object in any state other than newEntry(1) or setting(2) 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 the value reserved(7) or enabled(8), then this object indicates the internal/inside IP version. 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.
Status: current Access: read-create
OBJECT-TYPE    
  InetAddressType  

midcomRuleExternalIpVersion 1.3.6.1.2.1.171.1.1.3.1.15
IP version of the external address (A3) and the outside address (A2). Allowed values are ipv4(1) and ipv6(2). 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 the value newEntry(1) or setting(2), then this object can be written by a manager in order to specify the IP version required at the outside of the middlebox. Writing to this object in any state other than newEntry(1) or setting(2) 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 the value reserved(7) or enabled(8), then this object indicates the external/outside IP version. 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.
Status: current Access: read-create
OBJECT-TYPE    
  InetAddressType  

midcomRuleInternalIpAddr 1.3.6.1.2.1.171.1.1.3.1.16
The internal IP address (A0). 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 the value newEntry(1) or setting(2), then this object can be written by a manager in order to specify the internal IP address for which a reserve policy rule or a enable policy rule is requested to be established. Writing to this object in any state other than newEntry(1) or setting(2) 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 the value reserved(7) or enabled(8), then this object will have the value which it had before the transition to this state. 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.
Status: current Access: read-create
OBJECT-TYPE    
  InetAddress  

midcomRuleInternalIpPrefixLength 1.3.6.1.2.1.171.1.1.3.1.17
The prefix length of the internal IP address used for wildcarding. A value of 0 indicates a full wildcard; in this case, the value of midcomRuleInternalIpAddr is irrelevant. If midcomRuleInternalIpVersion has a value of ipv4(1), then a value > 31 indicates no wildcarding at all. If midcomRuleInternalIpVersion has a value of ipv4(2), then a value > 127 indicates no wildcarding at all. A MIDCOM-MIB implementation that does not support IP address wildcarding MUST implement this object as read-only with a value of 128. A MIDCOM that does not support wildcarding based on prefix length MAY restrict allowed values for this object to 0 and 128. 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 the value newEntry(1) or setting(2), then this object can be written by a manager in order to specify the prefix length of the internal IP address for which a reserve policy rule or an enable policy rule is requested to be established. Writing to this object in any state other than newEntry(1) or setting(2) 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 the value reserved(7) or enabled(8), then this object will have the value which it had before the transition to this state. 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.
Status: current Access: read-create
OBJECT-TYPE    
  InetAddressPrefixLength  

midcomRuleInternalPort 1.3.6.1.2.1.171.1.1.3.1.18
The internal port number. A value of 0 is a wildcard. 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. It is relevant to the operation of the MIDCOM-MIB implementation only if the value of object midcomTransportProtocol in the same entry has a value other than 0. If object midcomRuleOperStatus of the same entry has the value newEntry(1) or setting(2), then this object can be written by a manager in order to specify the internal port number for which a reserve policy rule or an enable policy rule is requested to be established. Writing to this object in any state other than newEntry(1) or setting(2) 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 the value reserved(7) or enabled(8), then this object will have the value that it had before the transition to this state. 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.
Status: current Access: read-create
OBJECT-TYPE    
  InetPortNumber  

midcomRuleExternalIpAddr 1.3.6.1.2.1.171.1.1.3.1.19
The external IP address (A3). 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 the value newEntry(1), setting(2), or reserved(7), then this object can be written by a manager in order to specify the external IP address for which an enable policy rule is requested to be established. Writing to this object in any state other than newEntry(1), setting(2), or reserved(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 the value enabled(8), then this object will have the value that it had before the transition to this state. 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.
Status: current Access: read-create
OBJECT-TYPE    
  InetAddress  

midcomRuleExternalIpPrefixLength 1.3.6.1.2.1.171.1.1.3.1.20
The prefix length of the external IP address used for wildcarding. A value of 0 indicates a full wildcard; in this case, the value of midcomRuleExternalIpAddr is irrelevant. If midcomRuleExternalIpVersion has a value of ipv4(1), then a value > 31 indicates no wildcarding at all. If midcomRuleExternalIpVersion has a value of ipv4(2), then a value > 127 indicates no wildcarding at all. A MIDCOM-MIB implementation that does not support IP address wildcarding MUST implement this object as read-only with a value of 128. A MIDCOM that does not support wildcarding based on prefix length MAY restrict allowed values for this object to 0 and 128. 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 the value newEntry(1), setting(2), or reserved(7), then this object can be written by a manager in order to specify the prefix length of the external IP address for which an enable policy rule is requested to be established. Writing to this object in any state other than newEntry(1), setting(2), or reserved(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 the value enabled(8), then this object will have the value that it had before the transition to this state. 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.
Status: current Access: read-create
OBJECT-TYPE    
  InetAddressPrefixLength  

midcomRuleExternalPort 1.3.6.1.2.1.171.1.1.3.1.21
The external port number. A value of 0 is a wildcard. 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. It is relevant to the operation of the MIDCOM-MIB implementation only if the value of object midcomTransportProtocol in the same entry has a value other than 0. If object midcomRuleOperStatus of the same entry has the value newEntry(1), setting(2) or reserved(7), then this object can be written by a manager in order to specify the external port number for which an enable policy rule is requested to be established. Writing to this object in any state other than newEntry(1), setting(2) or reserved(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 the value enabled(8), then this object will have the value which it had before the transition to this state. 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.
Status: current Access: read-create
OBJECT-TYPE    
  InetPortNumber  

midcomRuleInsideIpAddr 1.3.6.1.2.1.171.1.1.3.1.22
The inside IP address at the middlebox (A1). The value of this object is relevant only if object midcomRuleOperStatus of the same entry has a value of either reserved(7) or enabled(8).
Status: current Access: read-only
OBJECT-TYPE    
  InetAddress  

midcomRuleInsidePort 1.3.6.1.2.1.171.1.1.3.1.23
The inside port number at the middlebox. A value of 0 is a wildcard. The value of this object is relevant only if object midcomRuleOperStatus of the same entry has a value of either reserved(7) or enabled(8).
Status: current Access: read-only
OBJECT-TYPE    
  InetPortNumber  

midcomRuleOutsideIpAddr 1.3.6.1.2.1.171.1.1.3.1.24
The outside IP address at the middlebox (A2). The value of this object is relevant only if object midcomRuleOperStatus of the same entry has a value of either reserved(7) or enabled(8).
Status: current Access: read-only
OBJECT-TYPE    
  InetAddress  

midcomRuleOutsidePort 1.3.6.1.2.1.171.1.1.3.1.25
The outside port number at the middlebox. A value of 0 is a wildcard. The value of this object is relevant only if object midcomRuleOperStatus of the same entry has a value of either reserved(7) or enabled(8).
Status: current Access: read-only
OBJECT-TYPE    
  InetPortNumber  

midcomRuleLifetime 1.3.6.1.2.1.171.1.1.3.1.26
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.
Status: current Access: read-create
OBJECT-TYPE    
  Unsigned32  

midcomRuleRowStatus 1.3.6.1.2.1.171.1.1.3.1.27
A control that allows entries to be added and removed from this table. Entries can also be removed from this table by setting objects midcomRuleLifetime and midcomRuleStorageTime of an entry to 0. Attempts to set a row notInService(2) where the value of the midcomRuleStorageType object is permanent(4) or readOnly(5) will result in an 'notWritable' 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. The value of this object has no effect on whether other objects in this conceptual row can be modified.
Status: current Access: read-create
OBJECT-TYPE    
  RowStatus  

midcomGroupTable 1.3.6.1.2.1.171.1.1.4
This table lists all current policy rule groups. Entries in this table are created or removed implicitly when entries in the midcomRuleTable are created or removed, respectively. A group entry in this table only exists as long as there are member rules of this group in the midcomRuleTable. The table serves for listing the existing groups and their remaining lifetimes and for changing lifetimes of groups and implicitly of all group members. Groups and all their member policy rules can only be deleted by deleting all member policies in the midcomRuleTable. Setting midcomGroupLifetime will result in setting the lifetime of all policy members to the same value.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    MidcomGroupEntry

midcomGroupEntry 1.3.6.1.2.1.171.1.1.4.1
An entry describing properties of a particular MIDCOM policy rule group.
Status: current Access: not-accessible
OBJECT-TYPE    
  MidcomGroupEntry  

midcomGroupIndex 1.3.6.1.2.1.171.1.1.4.1.2
The index of this group for the midcomRuleOwner. A group is identified by the combination of midcomRuleOwner and midcomGroupIndex. The value of this index must be unique per midcomRuleOwner.
Status: current Access: not-accessible
OBJECT-TYPE    
  Unsigned32 1..4294967295  

midcomGroupLifetime 1.3.6.1.2.1.171.1.1.4.1.3
When retrieved, this object delivers the maximum lifetime in seconds of all member rules of this group, i.e., of all rows in the midcomRuleTable that have the same values for midcomRuleOwner and midcomGroupIndex. Successfully writing to this object modifies the lifetime of all member policies. Successfully writing a value of 0 terminates all member policies and implicitly deletes the group as soon as all member entries are removed from the midcomRuleTable. Note that after a group's lifetime is expired or is set to 0, still the corresponding entry in the midcomGroupTable will exist as long as terminated member policy rules are stored as entries in the midcomRuleTable. 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.
Status: current Access: read-write
OBJECT-TYPE    
  Unsigned32  

midcomConfigMaxLifetime 1.3.6.1.2.1.171.1.2.1
When retrieved, this object returns the maximum lifetime, in seconds, that this middlebox allows policy rules to have.
Status: current Access: read-write
OBJECT-TYPE    
  Unsigned32  

midcomConfigPersistentRules 1.3.6.1.2.1.171.1.2.2
When retrieved, this object returns true(1) if the MIDCOM-MIB implementation can store policy rules persistently. Otherwise, it returns false(2). A value of true(1) indicates that there may be entries in the midcomRuleTable with object midcomRuleStorageType set to value nonVolatile(3).
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

midcomConfigIfTable 1.3.6.1.2.1.171.1.2.3
This table indicates capabilities of the MIDCOM-MIB implementation per IP interface. The table is indexed by the object midcomConfigIfIndex. For indexing a single interface, this object contains the value of the ifIndex object that is associated with the interface. If an entry with midcomConfigIfIndex = 0 occurs, then bits set in objects of this entry apply to all interfaces for which there is no entry in this table with the interface's index.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    MidcomConfigIfEntry

midcomConfigIfEntry 1.3.6.1.2.1.171.1.2.3.1
An entry describing the capabilities of a middlebox with respect to the indexed IP interface.
Status: current Access: not-accessible
OBJECT-TYPE    
  MidcomConfigIfEntry  

midcomConfigIfIndex 1.3.6.1.2.1.171.1.2.3.1.1
The index of an entry in the midcomConfigIfTable. For values different from zero, this object identifies an IP interface by containing the same value as the ifIndex object associated with the interface. Note that the index of a particular interface in the ifTable may change after a re-initialization of the middlebox, for example, after adding another interface to it. In such a case, the value of this object may change, but the interface referred to by the MIDCOM-MIB MUST still be the same. If, after a re-initialization of the middlebox, the interface referred to before re-initialization cannot be uniquely mapped anymore to a particular entry in the ifTable, then the value of object midcomConfigIfEnabled of the same entry MUST be changed to false(2). If the object has a value of 0, then values specified by further objects of the same entry apply to all interfaces for which there is no explicit entry in the midcomConfigIfTable.
Status: current Access: not-accessible
OBJECT-TYPE    
  InterfaceIndexOrZero  

midcomConfigIfBits 1.3.6.1.2.1.171.1.2.3.1.2
When retrieved, this object returns a set of bits indicating the capabilities (or configuration) of the middlebox with respect to the referenced IP interface. If the index equals 0, then all set bits apply to all interfaces. If the ipv4(0) bit is set, then the middlebox supports IPv4 at the indexed IP interface. If the ipv6(1) bit is set, then the middlebox supports IPv6 at the indexed IP interface. If the addressWildcards(2) bit is set, then the middlebox supports IP address wildcarding at the indexed IP interface. If the portWildcards(3) bit is set, then the middlebox supports port wildcarding at the indexed IP interface. If the firewall(4) bit is set, then the middlebox offers firewall functionality at the indexed interface. If the nat(5) bit is set, then the middlebox offers network address translation service at the indexed interface. If the portTranslation(6) bit is set, then the middlebox offers port translation service at the indexed interface. This bit is only relevant if nat(5) is set. If the protocolTranslation(7) bit is set, then the middlebox offers protocol translation service between IPv4 and IPv6 at the indexed interface. This bit is only relevant if nat(5) is set. If the twiceNat(8) bit is set, then the middlebox offers twice network address translation service at the indexed interface. This bit is only relevant if nat(5) is set. If the inside(9) bit is set, then the indexed interface is an inside interface with respect to NAT functionality. Otherwise, it is an outside interface. This bit is only relevant if nat(5) is set. An SNMP agent supporting both the MIDCOM-MIB module and the NAT-MIB module SHOULD ensure that the value of this object is consistent with the values of corresponding objects in the NAT-MIB module.
Status: current Access: read-only
OBJECT-TYPE    
  BITS ipv4(0), ipv6(1), addressWildcards(2), portWildcards(3), firewall(4), nat(5), portTranslation(6), protocolTranslation(7), twiceNat(8), inside(9)  

midcomConfigIfEnabled 1.3.6.1.2.1.171.1.2.3.1.3
The value of this object indicates the availability of the middlebox service described by midcomConfigIfBits at the indexed IP interface. By writing to this object, the MIDCOM support for the entire IP interface can be switched on or off. Setting this object to false(2) immediately stops middlebox support at the indexed IP interface. This implies that all policy rules that use NAT or firewall resources at the indexed IP interface are terminated immediately. In this case, the MIDCOM agent MUST send midcomUnsolicitedRuleEvent to all MIDCOM clients that have access to one of the terminated rules.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

midcomConfigFirewallTable 1.3.6.1.2.1.171.1.2.4
This table lists the firewall configuration per IP interface. It can be used for configuring how policy rules created by MIDCOM clients are realized as firewall rules of a firewall implementation. Particularly, the priority used for MIDCOM policy rules can be configured. For a single firewall implementation at a particular IP interface, all MIDCOM policy rules are realized as firewall rules with the same priority. Also, a firewall rule group name can be configured. The table is indexed by the object midcomConfigFirewallIndex. For indexing a single interface, this object contains the value of the ifIndex object that is associated with the interface. If an entry with midcomConfigFirewallIndex = 0 occurs, then bits set in objects of this entry apply to all interfaces for which there is no entry in this table for the interface's index.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    MidcomConfigFirewallEntry

midcomConfigFirewallEntry 1.3.6.1.2.1.171.1.2.4.1
An entry describing a particular set of firewall resources.
Status: current Access: not-accessible
OBJECT-TYPE    
  MidcomConfigFirewallEntry  

midcomConfigFirewallIndex 1.3.6.1.2.1.171.1.2.4.1.1
The index of an entry in the midcomConfigFirewallTable. For values different from 0, this object identifies an IP interface by containing the same value as the ifIndex object associated with the interface. Note that the index of a particular interface in the ifTable may change after a re-initialization of the middlebox, for example, after adding another interface to it. In such a case, the value of this object may change, but the interface referred to by the MIDCOM-MIB MUST still be the same. If, after a re-initialization of the middlebox, the interface referred to before re-initialization cannot be uniquely mapped anymore to a particular entry in the ifTable, then the entry in the midcomConfigFirewallTable MUST be deleted. If the object has a value of 0, then values specified by further objects of the same entry apply to all interfaces for which there is no explicit entry in the midcomConfigFirewallTable.
Status: current Access: not-accessible
OBJECT-TYPE    
  InterfaceIndexOrZero  

midcomConfigFirewallGroupId 1.3.6.1.2.1.171.1.2.4.1.2
The firewall rule group to which all firewall rules are assigned that the MIDCOM server creates for the interface indicated by object midcomConfigFirewallIndex. If the value of object midcomConfigFirewallIndex is 0, then all firewall rules of the MIDCOM server that are created for interfaces with no specific entry in the midcomConfigFirewallTable are assigned to the firewall rule group indicated by the value of this object.
Status: current Access: read-write
OBJECT-TYPE    
  SnmpAdminString  

midcomConfigFirewallPriority 1.3.6.1.2.1.171.1.2.4.1.3
The priority assigned to all firewall rules that the MIDCOM server creates for the interface indicated by object midcomConfigFirewallIndex. If the value of object midcomConfigFirewallIndex is 0, then this priority is assigned to all firewall rules of the MIDCOM server that are created for interfaces for which there is no specific entry in the midcomConfigFirewallTable.
Status: current Access: read-write
OBJECT-TYPE    
  Unsigned32  

midcomResourceTable 1.3.6.1.2.1.171.1.3.1
This table lists all used middlebox resources per MIDCOM policy rule. The midcomResourceTable augments the midcomRuleTable.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    MidcomResourceEntry

midcomResourceEntry 1.3.6.1.2.1.171.1.3.1.1
An entry describing a particular set of middlebox resources.
Status: current Access: not-accessible
OBJECT-TYPE    
  MidcomResourceEntry  

midcomRscNatInternalAddrBindMode 1.3.6.1.2.1.171.1.3.1.1.4
An indication of whether this policy rule uses an address NAT bind or an address-port NAT bind for binding the internal address. If the MIDCOM-MIB module is operated together with the NAT-MIB module (RFC 4008) then object midcomRscNatInternalAddrBindMode contains the same value as the corresponding object natSessionPrivateSrcEPBindMode of the NAT-MIB module.
Status: current Access: read-only
OBJECT-TYPE    
  MidcomNatBindMode  

midcomRscNatInternalAddrBindId 1.3.6.1.2.1.171.1.3.1.1.5
This object references to the allocated internal NAT bind that is used by this policy rule. A NAT bind describes the mapping of internal addresses to outside addresses. MIDCOM-MIB implementations can read this object to learn the corresponding NAT bind resource for this particular policy rule. If the MIDCOM-MIB module is operated together with the NAT-MIB module (RFC 4008) then object midcomRscNatInternalAddrBindId contains the same value as the corresponding object natSessionPrivateSrcEPBindId of the NAT-MIB module.
Status: current Access: read-only
OBJECT-TYPE    
  NatBindIdOrZero  

midcomRscNatInsideAddrBindMode 1.3.6.1.2.1.171.1.3.1.1.6
An indication of whether this policy rule uses an address NAT bind or an address-port NAT bind for binding the external address. If the MIDCOM-MIB module is operated together with the NAT-MIB module (RFC 4008), then object midcomRscNatInsideAddrBindMode contains the same value as the corresponding object natSessionPrivateDstEPBindMode of the NAT-MIB module.
Status: current Access: read-only
OBJECT-TYPE    
  MidcomNatBindMode  

midcomRscNatInsideAddrBindId 1.3.6.1.2.1.171.1.3.1.1.7
This object refers to the allocated external NAT bind that is used by this policy rule. A NAT bind describes the mapping of external addresses to inside addresses. MIDCOM-MIB implementations can read this object to learn the corresponding NAT bind resource for this particular policy rule. If the MIDCOM-MIB module is operated together with the NAT-MIB module (RFC 4008), then object midcomRscNatInsideAddrBindId contains the same value as the corresponding object natSessionPrivateDstEPBindId of the NAT-MIB module.
Status: current Access: read-only
OBJECT-TYPE    
  NatBindIdOrZero  

midcomRscNatSessionId1 1.3.6.1.2.1.171.1.3.1.1.8
This object refers to the first allocated NAT session for this policy rule. MIDCOM-MIB implementations can read this object to learn whether or not a NAT session for a particular policy rule is used. A value of 0 means that no NAT session is allocated for this policy rule. A value other than 0 refers to the NAT session.
Status: current Access: read-only
OBJECT-TYPE    
  MidcomNatSessionIdOrZero  

midcomRscNatSessionId2 1.3.6.1.2.1.171.1.3.1.1.9
This object refers to the second allocated NAT session for this policy rule. MIDCOM-MIB implementations can read this object to learn whether or not a NAT session for a particular policy rule is used. A value of 0 means that no NAT session is allocated for this policy rule. A value other than 0 refers to the NAT session.
Status: current Access: read-only
OBJECT-TYPE    
  MidcomNatSessionIdOrZero  

midcomRscFirewallRuleId 1.3.6.1.2.1.171.1.3.1.1.10
This object refers to the allocated firewall rule in the firewall engine for this policy rule. MIDCOM-MIB implementations can read this value to learn whether a firewall rule for this particular policy rule is used or not. A value of 0 means that no firewall rule is allocated for this policy rule. A value other than 0 refers to the firewall rule number within the firewall engine.
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

midcomStatistics 1.3.6.1.2.1.171.1.3.2
OBJECT IDENTIFIER    

midcomCurrentOwners 1.3.6.1.2.1.171.1.3.2.1
The number of different values for midcomRuleOwner for all current entries in the midcomRuleTable.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

midcomTotalRejectedRuleEntries 1.3.6.1.2.1.171.1.3.2.2
The total number of failed attempts to create an entry in the midcomRuleTable.
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

midcomCurrentRulesIncomplete 1.3.6.1.2.1.171.1.3.2.3
The current number of policy rules that are incomplete. Policy rules are loaded via row entries in the midcomRuleTable. This object counts policy rules that are loaded but not fully specified, i.e., they are in state newEntry(1) or setting(2).
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

midcomTotalIncorrectReserveRules 1.3.6.1.2.1.171.1.3.2.4
The total number of policy reserve rules that failed parameter check and entered state incorrectRequest(4).
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

midcomTotalRejectedReserveRules 1.3.6.1.2.1.171.1.3.2.5
The total number of policy reserve rules that failed while being processed and entered state requestRejected(6).
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

midcomCurrentActiveReserveRules 1.3.6.1.2.1.171.1.3.2.6
The number of currently active policy reserve rules.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

midcomTotalExpiredReserveRules 1.3.6.1.2.1.171.1.3.2.7
The total number of expired policy reserve rules (entered termination state timedOut(9)).
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

midcomTotalTerminatedOnRqReserveRules 1.3.6.1.2.1.171.1.3.2.8
The total number of policy reserve rules that were terminated on request (entered termination state terminatedOnRequest(10)).
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

midcomTotalTerminatedReserveRules 1.3.6.1.2.1.171.1.3.2.9
The total number of policy reserve rules that were terminated, but not on request (entered termination state terminated(11)).
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

midcomTotalIncorrectEnableRules 1.3.6.1.2.1.171.1.3.2.10
The total number of policy enable rules that failed parameter check and entered state incorrectRequest(4).
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

midcomTotalRejectedEnableRules 1.3.6.1.2.1.171.1.3.2.11
The total number of policy enable rules that failed while being processed and entered state requestRejected(6).
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

midcomCurrentActiveEnableRules 1.3.6.1.2.1.171.1.3.2.12
The number of currently active policy enable rules.
Status: current Access: read-only
OBJECT-TYPE    
  Gauge32  

midcomTotalExpiredEnableRules 1.3.6.1.2.1.171.1.3.2.13
The total number of expired policy enable rules (entered termination state timedOut(9)).
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

midcomTotalTerminatedOnRqEnableRules 1.3.6.1.2.1.171.1.3.2.14
The total number of policy enable rules that were terminated on request (entered termination state terminatedOnRequest(10)).
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

midcomTotalTerminatedEnableRules 1.3.6.1.2.1.171.1.3.2.15
The total number of policy enable rules that were terminated, but not on request (entered termination state terminated(11)).
Status: current Access: read-only
OBJECT-TYPE    
  Counter32  

midcomUnsolicitedRuleEvent 1.3.6.1.2.1.171.0.1
This notification is generated whenever the value of midcomRuleOperStatus enters any error state or any termination state without an explicit trigger by a MIDCOM client.
Status: current Access: read-only
NOTIFICATION-TYPE    

midcomSolicitedRuleEvent 1.3.6.1.2.1.171.0.2
This notification is generated whenever the value of midcomRuleOperStatus enters one of the states {reserved, enabled, any error state, any termination state} as a result of a MIDCOM agent writing successfully to object midcomRuleAdminStatus. In addition, it is generated when the lifetime of a rule was changed by successfully writing to object midcomRuleLifetime.
Status: current Access: read-only
NOTIFICATION-TYPE    

midcomSolicitedGroupEvent 1.3.6.1.2.1.171.0.3
This notification is generated for indicating that the lifetime of all member rules of the group was changed by successfully writing to object midcomGroupLifetime. Note that this notification is only sent if the lifetime of a group was changed by successfully writing to object midcomGroupLifetime. No notification is sent - if a group's lifetime is changed by writing to object midcomRuleLifetime of any of its member policies, - if a group's lifetime expires (in this case, notifications are sent for all member policies), or - if the group is terminated by terminating the last of its member policies without writing to object midcomGroupLifetime.
Status: current Access: read-only
NOTIFICATION-TYPE    

midcomCompliances 1.3.6.1.2.1.171.2.1
OBJECT IDENTIFIER    

midcomGroups 1.3.6.1.2.1.171.2.2
OBJECT IDENTIFIER    

midcomCompliance 1.3.6.1.2.1.171.2.1.1
The compliance statement for implementations of the MIDCOM-MIB module. Note that compliance with this compliance statement requires compliance with the ifCompliance3 MODULE-COMPLIANCE statement of the IF-MIB [RFC2863].
Status: current Access: read-only
MODULE-COMPLIANCE    

midcomRuleGroup 1.3.6.1.2.1.171.2.2.1
A collection of objects providing information about policy rules and policy rule groups.
Status: current Access: read-only
OBJECT-GROUP    

midcomCapabilitiesGroup 1.3.6.1.2.1.171.2.2.2
A collection of objects providing information about the capabilities of a middlebox.
Status: current Access: read-only
OBJECT-GROUP    

midcomConfigFirewallGroup 1.3.6.1.2.1.171.2.2.3
A collection of objects providing information about the firewall rule group and firewall rule priority to be used by firewalls loaded through MIDCOM.
Status: current Access: read-only
OBJECT-GROUP    

midcomResourceGroup 1.3.6.1.2.1.171.2.2.4
A collection of objects providing information about the used NAT and firewall resources.
Status: current Access: read-only
OBJECT-GROUP    

midcomStatisticsGroup 1.3.6.1.2.1.171.2.2.5
A collection of objects providing statistical information about the MIDCOM server.
Status: current Access: read-only
OBJECT-GROUP    

midcomNotificationsGroup 1.3.6.1.2.1.171.2.2.6
The notifications emitted by the midcomMIB.
Status: current Access: read-only
NOTIFICATION-GROUP