RTM-MIB: View SNMP OID List / Download MIB
VENDOR: STRATACOM
| Home | MIB: RTM-MIB | |||
|---|---|---|---|---|
| Download as: |
Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
|
|||
| Object Name | OID | Type | Access | Info |
| rtm | 1.3.6.1.4.1.351.120 | |||
| trapsConfig | 1.3.6.1.4.1.351.120.1 | |||
| trapConfigTable | 1.3.6.1.4.1.351.120.1.1 | no-access |
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. |
|
| 1.3.6.1.4.1.351.120.1.1.1 | no-access |
An entry for each of the SNMP Manager registered. Each SNMP Manager is identified by its IP Address specified in managerIPAddress object. |
||
| managerIPaddress | 1.3.6.1.4.1.351.120.1.1.1.1 | ipaddress | read-write |
A unique index value representing the SNMP manager. |
| managerPortNumber | 1.3.6.1.4.1.351.120.1.1.1.2 | integer | read-write |
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 | integer | read-write |
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). Enumeration: 'addRow': 1, 'delRow': 2. |
| readingTrapsFlag | 1.3.6.1.4.1.351.120.1.1.1.4 | integer | read-write |
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. Enumeration: 'true': 2, 'false': 1. |
| nextTrapSeqNum | 1.3.6.1.4.1.351.120.1.1.1.5 | integer | read-write |
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. |
| managerNumOfValidEntries | 1.3.6.1.4.1.351.120.1.2 | integer | read-only |
The number of entries in trapConfigTable. |
| lastSequenceNumber | 1.3.6.1.4.1.351.120.1.3 | integer | read-only |
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. |
| trapUploadTable | 1.3.6.1.4.1.351.120.1.4 | no-access |
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. |
|
| 1.3.6.1.4.1.351.120.1.4.1 | no-access |
Manager does a Get request on the elements of this entry to upload missing traps. |
||
| trapManagerIPaddress | 1.3.6.1.4.1.351.120.1.4.1.1 | ipaddress | read-write |
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 | integer | read-only |
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 | displaystring | read-only |
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 | integer | read-only |
Flag indicating the last trap saved in the system's FIFO queue. Enumeration: 'true': 2, 'false': 1. |
| recoverTrapTable | 1.3.6.1.4.1.351.120.1.5 | no-access |
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. |
|
| 1.3.6.1.4.1.351.120.1.5.1 | no-access |
The entry for each of the traps stored in the switch. |
||
| recoverTrapSequenceNum | 1.3.6.1.4.1.351.120.1.5.1.1 | integer | read-only |
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 | octet string | read-only |
Trap description string. This contains the Trap PDU that is stored in the system. |