This monitor catches Xian events that notifies when the IPSec sessions total dropped packets if has changed its state.
IPSec session global total dropped packets is over threshold.
The number of discarded incoming and outgoing packets by all active IPSec sessions is above the maximum threshold configured in Xian Network Manager 2012.
It may be due to Firewall are being used, which may drop the packets before they are processed. Another option is that the packet is dropped because the flag does not allow DHCP pass-through traffic. Thus, the client cannot acquire an address, and it times out
Check your sessions logs and determine what is the cause of the dropping
Monitors the total number of packets dropped by all active IPSec sessions during received and sent processing which were dropped by the managed entity.
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.IPSecSessionsTotalDroppedPackets.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="IPSecSessionsTotalDroppedPackets_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>