TELDAT-MON-FEATURES-DNS-MIB: View SNMP OID List / Download MIB

VENDOR: TELDAT, S.A.


 Home MIB: TELDAT-MON-FEATURES-DNS-MIB
Download as:   
SNMPv2-CONF, SNMPv2-SMI, SNMPv2-TC, TELDAT-SW-STRUCTURE-MIB

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).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 telProdNpMonFeatDNS 1.3.6.1.4.1.2007.4.1.2.4.8
     teldatDNSMonProbeGroup 1.3.6.1.4.1.2007.4.1.2.4.8.1
         teldatDNSMonProbeTable 1.3.6.1.4.1.2007.4.1.2.4.8.1.1 no-access
DNS probes table. Each entry identifies a DNS probe.
             teldatDNSMonProbeEntry 1.3.6.1.4.1.2007.4.1.2.4.8.1.1.1 no-access
An entry identifies a DNS probe, used to measure the DNS resolution time, and it is comprised of the following parameters: the probe identifier, the probe status, the URL used for the last resolve time measurement, the date and time that the probe was last started and the resolve time measured.
                 teldatDNSMonProbeIdentifier 1.3.6.1.4.1.2007.4.1.2.4.8.1.1.1.1 integer read-only
Index of the table: probe indentifier.
                 teldatDNSMonProbeStatus 1.3.6.1.4.1.2007.4.1.2.4.8.1.1.1.2 displaystring read-only
Status of the DNS probe: Waiting, executing, or completed correctly or with errors.
                 teldatDNSMonProbeURL 1.3.6.1.4.1.2007.4.1.2.4.8.1.1.1.3 displaystring read-only
First resolved URL for the given DNS probe.
                 teldatDNSMonProbeInitDate 1.3.6.1.4.1.2007.4.1.2.4.8.1.1.1.4 octet string read-only
The date the probe was last started. If the probe has not ever been started yet, this is shown as 0.
                 teldatDNSMonProbeInitTime 1.3.6.1.4.1.2007.4.1.2.4.8.1.1.1.5 octet string read-only
The time the probe was last started. If the probe has not ever been started yet, this is shown as 0.
                 teldatDNSMonProbeResolveTime 1.3.6.1.4.1.2007.4.1.2.4.8.1.1.1.6 integer read-only
Measured resolve time.
         teldatDNSMonProbeStartTable 1.3.6.1.4.1.2007.4.1.2.4.8.1.2 no-access
This table allows to start the execution of the probe whose identifier takes the value given by the index. Each entry refers to one of the configured probes, and consists of two variables: the identifier of the probe, which is the index of the table, and a variable which is used to start the execution of the probe when a SET operation to this variable is made (and gives it the value 1).
             teldatDNSMonProbeStartEntry 1.3.6.1.4.1.2007.4.1.2.4.8.1.2.1 no-access
Each entry refers to one of the configured probes, and consists of two variables: the identifier of the probe, which is the index of the table, and a variable which is used to start the execution of the probe when a SET operation to this variable is made (and gives it the value 1).
                 teldatDNSMonProbeStartIndex 1.3.6.1.4.1.2007.4.1.2.4.8.1.2.1.1 integer read-only
Index of the table: probe identifier.
                 teldatDNSMonProbeStartCommand 1.3.6.1.4.1.2007.4.1.2.4.8.1.2.1.2 integer read-write
If the value of this variable is set to 1, the execution of the probe whose identifier takes the value given by the index will start. In GET operations, the value taken by this variable indicates the result of the last operation: ok (2), if the last operation was made succesfully; the value undefined (3) indicates that operations of this type have not been made yet. If the operation failed, this variable could take different values depending on the error cause: no-memory (4), if there was not enough memory to start the DNS probe; wrong-identifier(5) if the probe identifier introduced was not correct; already-started (6) indicates that the probe which was going to be started was started previously and is in execution; dns-uninitialized (7) if the DNS system has not been initialized; error (8) if another generic error has occurred. Enumeration: 'ok': 2, 'undefined': 3, 'already-started': 6, 'wrong-identifier': 5, 'start': 1, 'no-memory': 4, 'error': 8, 'dns-uninitialized': 7.
         teldatDNSMonProbeResetPPPAndStartTable 1.3.6.1.4.1.2007.4.1.2.4.8.1.3 no-access
This table allows to start the execution of the probe whose identifier takes the value given by the index once the PPP indicated has restablished connection after being shut down. Each entry refers to a pair probe-ppp connection, and consists of three variables: the identifier of the probe, the identifier of the PPP interface, and a variable which is used to start the execution of the probe when a SET operation to this variable is made (and gives it the value 1).
             teldatDNSMonProbeResetPPPAndStartEntry 1.3.6.1.4.1.2007.4.1.2.4.8.1.3.1 no-access
Each entry refers to a pair probe-ppp connection, and consists of three variables: the identifier of the probe, the identifier of the PPP interface, and a variable which is used to start the execution of the probe when a SET operation to this variable is made (and gives it the value 1).
                 teldatDNSMonProbeResetPPPAndStartIndex 1.3.6.1.4.1.2007.4.1.2.4.8.1.3.1.1 integer read-only
Index of the table: probe identifier.
                 teldatDNSMonProbeResetPPPIndex 1.3.6.1.4.1.2007.4.1.2.4.8.1.3.1.2 integer read-only
Index of the table: number of the PPP interface.
                 teldatDNSMonProbeResetPPPAndStartCommand 1.3.6.1.4.1.2007.4.1.2.4.8.1.3.1.3 integer read-write
If the value of this variable is set to 1, the PPP connection established through the interface given by the index will be disconnect and the DNS probe given by the other index will be started once the PPP connection restablishes. In GET operations, the value taken by this variable indicates the result of the last operation: ok (2), if the last operation was made succesfully; the value undefined (3) indicates that operations of this type have not been made yet. If the operation failed, this variable could take different values depending on the error cause: no-memory (4), if there was not enough memory to start the DNS probe; wrong-identifier(5) if the probe identifier introduced was not correct; already-started (6) indicates that the probe which was going to be started was started previously and is in execution; dns-uninitialized (7) if the DNS system has not been initialized; error (8) if another generic error has occurred. Enumeration: 'ok': 2, 'undefined': 3, 'already-started': 6, 'wrong-identifier': 5, 'start': 1, 'no-memory': 4, 'error': 8, 'dns-uninitialized': 7.