Using the Blue Medora ITM Agent for Ping Probe

by bluemedora_editor on February 4, 2010

We will continue our tour of the Blue Medora ITM Agent for Ping Probe with a walkthrough of the agent in the TEP. In this post, we will consider a number of enterprise scenarios and use the agent to solve them. It is my hope that the information given here will help you to quickly begin taking advantage of the agent’s features in your ITM environment.

— Mike Major

General Overview

Consider this scenario: The network administrator arrives at the office on Monday morning. The first thing they would like to do is check the overall status of the network and troubleshoot any problem areas. For this scenario, we have set up 2 instances of Ping Probe. One instance represents our on site servers, and the other represents off site servers. To see a complete network overview, we click on “Ping Probe” in the navigator window.[vc_single_image image=”2176″ alignment=”center” border_color=”grey” img_link_large=”” img_link_target=”_self” img_size=”full”]You can quickly get an idea of the overall health of the network with the graphs located on the right side. More detailed results can be found down below. But what if you are only interested in the off site hosts that are down (not slow)? It would be a pain to scan through that list. Under the “OffSite” instance, click “Ping Probe Results”:[vc_single_image image=”2177″ alignment=”center” border_color=”grey” img_link_large=”” img_link_target=”_self” img_size=”full”]The default view shows us the overall health of all off site hosts, with a detailed list of slow or unreachable hosts at the bottom. To see only the unreachable hosts, right click on “Ping Probe Results” and choose Workspace->Down. We now have a list off all unreachable off site hosts:[vc_single_image image=”2178″ alignment=”center” border_color=”grey” img_link_large=”” img_link_target=”_self” img_size=”full”]Ping Probe also comes with default views for showing ony the slow hosts, healthy hosts or showing all hosts in the instance.

Critical Servers

Let’s try another scenario: Your network has many small servers that are expected to go down often throughout the day for whatever reason. However, there are also a number of critical servers. You would like the Ping Probe agent to notify you when one of the critical servers is down, but you do not want to be flooded with messages for the other servers.

This problem could be solved in multiple ways. First, you could set up separate instances for critical servers. In our example, we would end up with 4 instances: CriticalOnSite, OtherOnSite, CriticalOffSite and OtherOffSite. Then, change the autostart for the KXF_DOWN_RESPONSE situation in the instances you would like to be notified on. However, you might only have a handful of critical servers, so you may not need separate instances.

In this example, I will instead show you how to modify the situation to only fire if specific servers go down. First, right click on the instance you would like to apply the situation to and click “Manage Situations”:[vc_single_image image=”2179″ alignment=”center” border_color=”grey” img_link_large=”” img_link_target=”_self” img_size=”full”]This will bring up a list of the currently defined situations. We want to edit the KXF_DOWN_RESPONSE situation, so we right click that and click “Edit Situation…”:[vc_single_image image=”2180″ alignment=”center” border_color=”grey” img_link_large=”” img_link_target=”_self” img_size=”full”]This is the situation editor. Right now, we can see that this situation would fire off whenever a host comes back unreachable. We want to add another condition, so click the “Add conditions…” button:[vc_single_image image=”2181″ alignment=”center” border_color=”grey” img_link_large=”” img_link_target=”_self” img_size=”full”]For this condition, we want to check the host attribute for some specific values. So choose “Attribute Comparison” and select the “Host” attribute item. Click OK:[vc_single_image image=”2182″ alignment=”center” border_color=”grey” img_link_large=”” img_link_target=”_self” img_size=”full”]The new attribute condition was added to our situation editor. Now we just type in the critical hostnames and click Apply:[vc_single_image image=”2183″ alignment=”center” border_color=”grey” img_link_large=”” img_link_target=”_self” img_size=”full”]Back in the “Manage Situation” dialog, right click the KXF_DOWN_RESPONSE situation and click Start Situation:[vc_single_image image=”2184″ alignment=”center” border_color=”grey” img_link_large=”” img_link_target=”_self” img_size=”full”]We are now notified when a critical server is down![vc_single_image image=”2185″ alignment=”center” border_color=”grey” img_link_large=”” img_link_target=”_self” img_size=”full”]What if you have a number of off site servers located in an unstable network area? You may expect the servers to be unreachable from time to time, but that may not mean the servers themselves are down. Having a situation fire off every time they are unreachable might be overkill. Ping Probe can solve this problem as well. Navigate back to the situation editor for the KXF_DOWN_RESPONSE situation and click the Advanced button:[vc_single_image image=”2186″ alignment=”center” border_color=”grey” img_link_large=”” img_link_target=”_self” img_size=”full”]Now, change the “Consecutive true samples” to 5. This means the server will have to be unreachable for 5 consecutive Ping Probe samples before the situation will fire.[vc_single_image image=”2187″ alignment=”center” border_color=”grey” img_link_large=”” img_link_target=”_self” img_size=”full”]This should be sufficient enough to confidently say that the server is truly unreachable.

Well, that’s it for now. I hope these scenarios have given you a good idea of the power behind the Blue Medora ITM Agent for Ping Probe. As always, if you have any questions regarding this post, the Ping Probe Agent or anything else related to Blue Medora ITM Agents, feel free to drop me a line directly at:mike.major@bluemedora.com[vc_column width=”1/3″ el_class=”sidebar”][ultimatesocial_false count=”” align=”left” skin=”default” share_text=”Share: ” networks=”facebook, twitter, linkedin, reddit”]

Get started

Try BindPlane for free. No credit card required.

Sign up
True Visibility
BindPlane for VMware vRealize Operations

True Visibility allows cloud management teams to use VMware vRealize’s powerful machine learning and capacity planning engine across their entire hybrid cloud environment.

Azure Monitor...everything
BindPlane for Microsoft Azure Monitor

Make Azure Monitor your first-pane-of-glass across your entire multi-cloud, multi-database or hybrid platform environment.

Thank you for contacting us. Your information was received. We'll be in touch shortly.