This monitor catches Xian events that notifies when the IPSec sessions incoming traffic if has changed its state.
IPSec session global incoming traffic is over threshold.
The number of all active IPSec sessions incoming Kbits per second is above the maximum threshold configured in Xian Network Manager 2012.
There is a high amount of octets being received by all active IPSec sessions.
Review the sessions that are running in order to close the less priority sessions.
Monitors the traffic received on all active IPSec sessions, detecting when the average traffic is above normal values.
Target | Jalasoft.Xian.Common.Elements.ThirdParty.Cisco.JsXCiscoASAIPSecSessionsElement | ||
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 |
|
<AggregateMonitor ID="Jalasoft.Xian.SmartManagementPacks.CiscoASA.IPSecSessionsIncomingTraffic.1.1" Accessibility="Public" Enabled="true" Target="ThirdParty_Cisco!Jalasoft.Xian.Common.Elements.ThirdParty.Cisco.JsXCiscoASAIPSecSessionsElement" ParentMonitorID="SystemHealth!System.Health.PerformanceState" Remotable="true" Priority="Normal">
<Category>StateCollection</Category>
<AlertSettings AlertMessage="IPSecSessionsIncomingTraffic_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>