MIDCOM-MIB :: midcomRulePortRange

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › MIDCOM-MIB › midcomRulePortRange

midcomRulePortRange

Module: MIDCOM-MIB

OID (symbolic): MIDCOM-MIB::midcomRulePortRange

OID (numeric): 1.3.6.1.2.1.171.1.1.3.1.13

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-create

Description: 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.

What is midcomRulePortRange?

Specifies whether this rule requests a single(1) port number or a consecutive pair(2) of ports (lower number even), the latter needed by protocols like RTP that require a matched even/odd port pair.

OID Breakdown

Upper-level ancestors (6 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.2mgmtAPERTUS-NPG-MIB
1.3.6.1.2.1mib_2AXON-MIB
Numeric OIDNameModule
1.3.6.1.2.1.171midcomMIBMIDCOM-MIB
1.3.6.1.2.1.171.1midcomObjectsMIDCOM-MIB
1.3.6.1.2.1.171.1.1midcomTransactionMIDCOM-MIB
1.3.6.1.2.1.171.1.1.3midcomRuleTableMIDCOM-MIB
1.3.6.1.2.1.171.1.1.3.1midcomRuleEntryMIDCOM-MIB
1.3.6.1.2.1.171.1.1.3.1.13midcomRulePortRangeMIDCOM-MIB