Cisco ASA: CPU load Health Monitor

Jalasoft.Xian.SmartManagementPacks.CiscoASA.CPULoad.1.1 (AggregateMonitor)

This monitor catches Xian events that notifies when the CPU load has changed its state.

Knowledge Base article:

Summary

CPU load is over threshold.

CPU load percentage is above the maximum threshold configured in Xian Network Manager 2012.

Causes

If percentage exceeds 80% for continuous periods, you may have a CPU bottleneck on your ASA device. Occasional peaks of 100% are nothing to worry about and are normal for most ASA devices.

Resolutions

If you notice that the percentage is gradually increasing, this is a sign that you may eventually run out of CPU cycles on your ASA device. Verify which processes are using such amount of CPU and stop them if not necessary. Upgrade if necessary or redistribute the traffic using other ASA devices or gateways.

Additional

Monitors last-five-minutes average Cisco ASA CPU load.

Element properties:

Target

Jalasoft.Xian.Common.Elements.ThirdParty.Cisco.JsXCiscoASASnmpDeviceElement

Parent Monitor

System.Health.PerformanceState

Algorithm

WorstOf

Category

StateCollection

Enabled

True

Alert Generate

True

Alert Severity

MatchMonitorHealth

Alert Priority

Low

Alert Auto Resolve

True

Remotable

True

Accessibility

Public

Alert Message

CPU load Alert

{0}

Source Code:

<AggregateMonitor ID="Jalasoft.Xian.SmartManagementPacks.CiscoASA.CPULoad.1.1" Accessibility="Public" Enabled="true" Target="ThirdParty_Cisco!Jalasoft.Xian.Common.Elements.ThirdParty.Cisco.JsXCiscoASASnmpDeviceElement" ParentMonitorID="SystemHealth!System.Health.PerformanceState" Remotable="true" Priority="Normal">

  <Category>StateCollection</Category>

  <AlertSettings AlertMessage="CPULoad_AlertMessage">

    <AlertOnState>Warning</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Low</AlertPriority>

    <AlertSeverity>MatchMonitorHealth</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Data/Context/Params/Param[3]$</AlertParameter1>

    </AlertParameters>

  </AlertSettings>

  <Algorithm>WorstOf</Algorithm>

</AggregateMonitor>