Cisco ASA: Webvpn sessions incoming dropped packets Health Monitor

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

This monitor catches Xian events that notifies when the Webvpn sessions incoming dropped packets if has changed its state.

Knowledge Base article:

Summary

Webvpn session global incoming dropped packets is over threshold.

The number of discarded incoming packets by all active Webvpn sessions is above the maximum threshold configured in Xian Network Manager 2012.

Causes

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

Resolutions

Check your sessions logs and determine what is the cause of the dropping

Additional

Monitors the total number of packets dropped by all active Webvpn sessions during received processing which were dropped by the managed entity.

Element properties:

Target

Jalasoft.Xian.Common.Elements.ThirdParty.Cisco.JsXCiscoASAWebvpnSessionsElement

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

Webvpn sessions incoming dropped packets Alert

{0}

Source Code:

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

  <Category>StateCollection</Category>

  <AlertSettings AlertMessage="WebvpnSessionsIncomingDroppedPackets_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>