Event Monitors are mainly used to monitor the device in order to provide notifications to the technicians in a timely manner if there are any problems with the device performance. Testing in a network is done mainly to check the performance of the network. There are various tests which are available based on the monitors which are present in the device. The DNS Service needs to be monitored on the device to ensure that it properly responds and is able to resolve the queries which are received for a particular DNS hostname. This article explains how to monitor the DNS Service on the ON100 and gives the test results.
Applicable Devices
• OnPlus 100
Software Version
• v7.6.2.038
Monitor DNS Service
Step 1. Log in to the Cisco OnPlus Portal, click the desired customer, and choose Dashboard.
Step 2. Move the mouse over the ON100 device from the Network Topology view and click the Device Information icon.
Step 3. Click the Monitors tab. For each monitor, three icons are available. The first icon gives information about the particular monitor, the second icon is used test the monitor, and the third icon is used to indicate whether the monitor is enabled or not. Make sure the monitor is enabled before the testing is done. Please refer to the article Enable or Disable Device Monitors on OnPlus 100 to enable a monitor if it is not enabled.
Note: For the devices other than OnPlus Network Agent and devices which provide WAN port to connect to the Internet, this tab is blank when accessed first because event monitors are not added yet. In the case of the OnPlus, when the OnPlus Network Agent is activated for a customer, the event monitors such as WAN Network Performance, CPU Load, Duplicate IP, DHCP Server, DNS Service, and Memory are enabled and created by default. Default Monitors in OnPlus Network Agent cannot be deleted but can be disabled. The severity levels and other settings can also be edited for these monitors.
Step 4. Click the DNS Service monitor, which is the monitor to be tested. The DNS Service has a Target DNS Hostname and two latency parameters which can be edited.
Note: A Warning or Critical event is generated if the latency of the response crosses the specified thresholds. Sluggish Web browsing can be the reason for a slow DNS server response.
Step 5. Enter the DNS hostname that needs to be resolved by the name server in the Target DNS Hostname field.
Step 6. Enter the warning and critical values for latency (in seconds) in the Latency Warning (Seconds) and Latency Critical (Seconds) fields respectively. Latency is the delay from the time of the start of packet transmission at the sender to the time of the end of packet reception at the receiver.
Step 5. Click Test Monitor to test the DNS Service. A new page opens.
Step 6. (Optional) Check Generate an event to allow a real event to be created that reflects the result from the test. If the generated event has a delivery rule associated to it then the event will be created and delivered to the user in accordance to that rule.
Step 7. Click Run in the Run Test field to run the test. The results are shown in the Test Output field.
Step 8. (Optional) Click the Back arrow icon to return to the previous page to make any desired changes.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: