DNS-TRAPS-MIB

All MIBs › DNS-TRAPS-MIB

Organization: Motorola Connected Home Solutions

Last Updated: 2006-04-27

Category: Vendor: D-Link

Description: Defines SNMP trap notifications for DNS service events and failures in DNS server appliances.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is DNS-TRAPS-MIB?

DNS-TRAPS-MIB is a vendor MIB template defining common SNMP trap notifications for DNS service events and failures, intended to be imported and customized (with a vendor-specific enterprise OID) by application-specific DNS appliance MIBs rather than used standalone. It standardizes a set of alarm variables and a severity-level enumeration so that DNS-related fault events can be reported consistently across products built on this template. Its use in monitoring is entirely fault/trap-oriented: it exists to notify operators of DNS service failures or degraded conditions, functioning much like a software-status alerting layer for a DNS server rather than exposing performance counters. As a trap template, it has an inherent structural dependency on being copied into a concrete application MIB with a real enterprise number before it can be deployed. It is used within DNS server appliance products where the vendor has adapted this template to raise SNMP traps for DNS service faults. Engineers can download the DNS-TRAPS-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in DNS-TRAPS-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

DNS server appliance (vendor-specific, built on this trap template)

Monitoring Examples

No runtime data objects were extracted for this module, and by design this MIB is a trap-notification template rather than a source of pollable status objects; a concrete monitoring scenario with real object names cannot be constructed since the sample objects were empty and the module explicitly describes itself as a template to be copied into other MIBs. In practice, a receiving NMS would primarily be a trap-listener target for whichever vendor MIB imports and populates this template's alarm/severity variables.

Imported Objects

From BCS-IDENT-MIB

bcs	OBJECT-IDENTITY

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
OBJECT-TYPE

How to Use in IPNetwork Monitor

Example using alarmConditionNotInList OID:

Select a DNS server appliance (vendor trap template, Motorola Connected Home Solutions origin) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type alarmConditionNotInList into the Find box to locate it in the OID tree, then select it and click OK. It reports the alarm which occurs when a clear condition command is issued and there is no such condition in the current condition list. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an Integer32-type OID, Value bounds is the most useful condition here — trigger an alert if the value drifts significantly from its normal baseline, since an unexpected change often points to a real underlying issue. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
dns	1.3.6.1.4.1.1166.7.5			The MIB module for the DNS common trap VARIABLES. The MIB tree for this MIB is shown below: revision number sds0.001 - initial version revision number sds0.002 - revised with the changes (1) traps are template defined here, it should be copied to application mib module with correct ENTERPRISE declared. (2) all alarm var.'s SYNTAX use enumeration of severity level definition.
dnsTraps	1.3.6.1.4.1.1166.7.5.1
dnsAlarms	1.3.6.1.4.1.1166.7.5.2
I32 alarmConditionNotInListEx	1.3.6.1.4.1.1166.7.5.2.20	Integer32	read-only	Alarm which occurs when a clear condition command is issued and there is no such condition in the current condition list. This is a counter for the trap 20.
I32 alarmConditionAlreadyInList	1.3.6.1.4.1.1166.7.5.2.21	Integer32	read-only	Alarm which occurs when a set condition command is issued and there is already the same condition in the current condition list. This is a counter for the trap 21.
I32 alarmConditionListFull	1.3.6.1.4.1.1166.7.5.2.22	Integer32	read-only	Alarm which occurs when a set condition command is issued and there is no room in the current condition list. This is a counter for the trap 22.
I32 alarmInvalidCaseInSwitch	1.3.6.1.4.1.1166.7.5.2.23	Integer32	read-only	Alarm which occurs when in a switch statement the default case is reached. This is a counter for the trap 23.
I32 alarmCannotCreateSemaphore	1.3.6.1.4.1.1166.7.5.2.24	Integer32	read-only	Alarm which occurs when a semaphore cannot be created. This is a counter for the trap 24.
I32 alarmCannotOpenSocket	1.3.6.1.4.1.1166.7.5.2.25	Integer32	read-only	Alarm which occurs when a socket cannot be opened. This is a counter for the trap 25.
I32 alarmUnknownMessageReceived	1.3.6.1.4.1.1166.7.5.2.26	Integer32	read-only	Alarm which occurs when an unknown message is received. This is a counter for the trap 26.
I32 alarmInvalidMessageReceived	1.3.6.1.4.1.1166.7.5.2.27	Integer32	read-only	Alarm which occurs when an invalid message is received. This is a counter for the trap 27.

RFC description

Defines trap variables and alarm severities for DNS common element management in cable headend systems.

Start monitoring DNS server appliance (vendor trap template, Motorola Connected Home Solutions origin) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download DNS-TRAPS-MIB

What Is DNS-TRAPS-MIB?

Supported Devices

Monitoring Examples

This MIB depends on

Related MIBs

How to Use in IPNetwork Monitor

RFC description