APERTUS-TNSERVER-MIB :: aperTnServRtmNumberOfBoundaries

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsAPERTUS-TNSERVER-MIBaperTnServRtmNumberOfBoundaries

aperTnServRtmNumberOfBoundaries

Module: APERTUS-TNSERVER-MIB

OID (symbolic): APERTUS-TNSERVER-MIB::aperTnServRtmNumberOfBoundaries

OID (numeric): 1.3.6.1.4.1.543.3.1.4.1.21.1.12

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: The number of RTM boundaries utilized by the LU. At least one RTM boundary must be specified so the range of this variable is 1-4.

Writing this variable causes the RtmBoundary values for the LU previously written by the management station to be validated and confirmed to be in strictly increasing order. If validation is successful, the new boundary values are written to the kernel, causing the current RTM counters to be reset. If validation is unsuccessful, the buffered values are dropped and not written to the kernel.

What is aperTnServRtmNumberOfBoundaries?

Configures how many response-time boundary thresholds (1 to 4) are used to bucket transactions for this LU, and validates/commits any previously set boundary values when written.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.543.3.1.4.1.21.1.12
snmpwalk -v2c -c public <target> APERTUS-TNSERVER-MIB::aperTnServRtmNumberOfBoundaries

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.543.3.1.4.1.21.1.12.1
snmpget -v2c -c public <target> APERTUS-TNSERVER-MIB::aperTnServRtmNumberOfBoundaries.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.543.3.1.4.1.21.1.12.1 i <value>

Start monitoring Apertus Technologies translation/naming server appliance (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the APERTUS-TNSERVER-MIB::aperTnServRtmNumberOfBoundaries OID value, configure state conditions and alerts, and monitor any Apertus Technologies translation/naming server appliance (legacy) from a single console.

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.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
Numeric OIDNameModule
1.3.6.1.4.1.543apertusAPERTUS-TNSERVER-MIB
1.3.6.1.4.1.543.3expressAPERTUS-TNSERVER-MIB
1.3.6.1.4.1.543.3.1aperTnServMIBAPERTUS-TNSERVER-MIB
1.3.6.1.4.1.543.3.1.4aperTnServStatsAPERTUS-TNSERVER-MIB
1.3.6.1.4.1.543.3.1.4.1aperTnServRtmAPERTUS-TNSERVER-MIB
1.3.6.1.4.1.543.3.1.4.1.21aperTnServRtmTableAPERTUS-TNSERVER-MIB
1.3.6.1.4.1.543.3.1.4.1.21.1aperTnServRtmEntryAPERTUS-TNSERVER-MIB
1.3.6.1.4.1.543.3.1.4.1.21.1.12aperTnServRtmNumberOfBoundariesAPERTUS-TNSERVER-MIB