This monitor catches Xian events that notifies when the Load Balancing sessions outgoing dropped packets if has changed its state.
Load Balancing session global outgoing dropped packets is over threshold.
The number of discarded outgoing packets by all active Load Balancing sessions is above the maximum threshold configured in Xian Network Manager 2012.
It may be due to Firewall are being used. 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 Load Balancing sessions which were dropped during transmit processing by the managed entity
Target | Jalasoft.Xian.Common.Elements.ThirdParty.Cisco.JsXCiscoASALBSessionsElement | ||
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.LBSessionsOutgoingDroppedPackets.1.1" Accessibility="Public" Enabled="true" Target="ThirdParty_Cisco!Jalasoft.Xian.Common.Elements.ThirdParty.Cisco.JsXCiscoASALBSessionsElement" ParentMonitorID="SystemHealth!System.Health.PerformanceState" Remotable="true" Priority="Normal">
<Category>StateCollection</Category>
<AlertSettings AlertMessage="LBSessionsOutgoingDroppedPackets_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>