Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Engineer's ToolSet (ETS) > Engineer's Toolset Administrator Guide > List of tools included in Engineer's Toolset > Network Performance Monitor > Example of a failure of a load balancing alert suppression

Example of a failure of a load balancing alert suppression

Table of contents
No headers
Created by Aileen de Lara_ret, last modified by Aileen de Lara_ret on Jan 12, 2017

Views: 7 Votes: 0 Revisions: 2

If you have multiple servers configured to load balance your website, knowing how you load sharing scheme is performing is very important to site stability. Within this example, assume that you want to be alerted when the CPU load on two servers exceeds 80 percent, but only if one shows a CPU load of 40 percent or less. If the second server reports greater than 40 percent utilization, the alert is suppressed.

You must configure two alerts, one alert for each server. These alerts are identical, except for the servers monitored.

  1. Click Alerts > Configure Alerts, and then on the Configure Alerts window, click New Alert.
  2. In the Name of Alert field enter an alert name.
  3. Click the Property to Monitor tab, and then in the Node Statistics section of the tree, select % CPU Utilization.
  4. Click the Monitored Network Objects tab, and then select the server to monitor.
  5. Click the Alert Trigger tab, and then enter the percentage for Alert and Reset triggers.
    Enter 80 percent to follow the scenario.
  6. Click the Time of Day tab, and then select the time of day parameters, if necessary.
  7. Click the Alert Suppression tab, and then click Suppress this Alert if ANY of the selected Suppressions are Active.
  8. Click Add.
  9. On the tab, select % CPU Utilization.
  10. Click the NetwProperty to Monitorork Object tab, and then check the second server of the load balanced pair.
  11. Click the Suppression Trigger tab, and then select Greater Than and enter 40 in the text-entry field
  12. Click OK.
  13. Select the newly created suppression condition to activate it.
  14. Repeat the procedure, but reverse the server choices made at Steps 4 and 10.
 
Last modified
17:43, 12 Jan 2017

Tags

Classifications

Public