AD | Application | AWS | Azure | Cloud | Database | Enterprise | Environmental | Event Log | File System | IoT | IT Service | Network/System | NIS2 | Infra | Performance | Protocol | SaaS | Security | Service Level | Storage | Linux | VMware | VoIP | Web | Wireless | SNMP

MonitorTools.com » Technical documentation » SNMP » MIB » Stratacom » RTM-MIB » Objects

RTM-MIB.mib object

Introduction

Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2025 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers). This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.

ActiveXperts Network Monitor 2025 can import MIB file RTM-MIB and use it to monitor vendor specific OID's.

RTM-MIB file content

Object view of RTM-MIB:

Scalar Object
trapConfigEntry .1.3.6.1.4.1.351.120.1.1.1
An entry for each of the SNMP Manager registered. Each SNMP Manager is identified by its IP Address specified in managerIPAddress object.
managerNumOfValidEntries .1.3.6.1.4.1.351.120.1.2
The number of entries in trapConfigTable.
lastSequenceNumber .1.3.6.1.4.1.351.120.1.3
The sequence number of the last trap generated by the system. This object is used in each of the RTM Compliant trap definitions. The manager can figure out whether any trap is lost(missing) by comparing the lastSequenceNumber values received in last 2 traps.
trapUploadEntry .1.3.6.1.4.1.351.120.1.4.1
Manager does a Get request on the elements of this entry to upload missing traps.
recoverTrapEntry .1.3.6.1.4.1.351.120.1.5.1
The entry for each of the traps stored in the switch.
Tabular Object
managerIPaddress .1.3.6.1.4.1.351.120.1.1.1.1
A unique index value representing the SNMP manager.
managerPortNumber .1.3.6.1.4.1.351.120.1.1.1.2
The UDP Port number on which the manager receives traps from a system.
managerRowStatus .1.3.6.1.4.1.351.120.1.1.1.3
This object is used for adding(registering) and deleting(de-registering) SNMP managers in the system. By setting this object to 'addRow' snmp manager will be registered with the system. By setting this object to 'delRow' snmp manager will be registered with the system. In some systems, the SNMP Manager will be de-registered automatically by the agent (to allow other SNMP managers to register), if manager is idle for long time( This time is called aging interval time). In order to avoid Managers being de-registered automatically it is expected that the SNMP Managers keep sending keep-alive requests(SNMP GET on this object) to the system for predefined interval(Choosen by SNMP Manager). The keep-alive requests need to be sent few minutes before the aging interval expires. The aging value of the Registered Managers are in the order of minutes(system dependent or user configured). The value supported for the aging value is system dependent. The system might support aging value per manager basis or per node basis (applicable to all the registered managers).
readingTrapsFlag .1.3.6.1.4.1.351.120.1.1.1.4
An entry for the state of the manager. The value 'false' indicates that SNMP manager is not in the middle of uploading traps(via trapUploadTable). The value 'true' indicates that SNMP manager is in the middle of uploading traps(via trapUploadTable). When the value is 'true' the system will not send traps to the corresponding manager identified by managerIPAddress object.
nextTrapSeqNum .1.3.6.1.4.1.351.120.1.1.1.5
Set by the manager to indicate the first trap(identified by this sequence number) it is interested in uploading. The agent increments this value when readingTrapsFlag is set to true(1) and SNMP Get is performed on trapUploadTable. The trapUploadTable entries returned depends upon this value. If there are no traps in the system with the the sequence number, the agent will set the value for this object to the head of FIFO(Saved traps) and return an error response.
trapManagerIPaddress .1.3.6.1.4.1.351.120.1.4.1.1
IP address of the manager used as an index to the table. The value of this object must match with the value in the managerIPaddress object.
trapSequenceNum .1.3.6.1.4.1.351.120.1.4.1.2
The sequence number associated with the trap. This sequence number has to match with the value in lastSequenceNumber object embedded in trapPduString.
trapPduString .1.3.6.1.4.1.351.120.1.4.1.3
Trap description string. This contains the Trap PDU that is stored in the system.
endOfQueueFlag .1.3.6.1.4.1.351.120.1.4.1.4
Flag indicating the last trap saved in the system's FIFO queue.
recoverTrapSequenceNum .1.3.6.1.4.1.351.120.1.5.1.1
The sequence number associated with the trap. The system tries to find a matching entry in the list of traps stored. If there is a match, an valid entry returned with value for 'recoverTrapPduString' object.
recoverTrapPduString .1.3.6.1.4.1.351.120.1.5.1.2
Trap description string. This contains the Trap PDU that is stored in the system.
Table
trapConfigTable .1.3.6.1.4.1.351.120.1.1
The trap configuration table. This table is used for registering SNMP managers with the system. The system will send traps only to the registered SNMP mangers.
trapUploadTable .1.3.6.1.4.1.351.120.1.4
The trapUploadTable is used by the manager to retrieve missing(lost) traps using robust trap mechanism. The manager does a Get request on this table.
recoverTrapTable .1.3.6.1.4.1.351.120.1.5
A table containing information about the traps sent from the system/switch. The total number of traps stored in the switch is implementation specific. It is expected that systems supporting RTM Mechanism save atleast least 500 traps , so that NMS applications can recover the traps if they determined it to be lost.
Object Identifier
rtm .1.3.6.1.4.1.351.120
trapsConfig .1.3.6.1.4.1.351.120.1
M