F5 Big IP: Fragmentation failed Health Monitor

Jalasoft.Xian.SmartManagementPacks.F5BigIp.FragmentationFailed.1.2 (AggregateMonitor)

This monitor catches Xian events that notifies when the Fragmentation failed if has changed its state.

Knowledge Base article:

Summary

Failed fragmentation is over threshold.

The number of fragments is above the maximum threshold configured in Xian Network Manager 2012 due to failed fragmentation processes.

Causes

If the counter is at a suspect level, there might be a capacity problem. Fragmentation is always undesirable because it reduces performance, but it could be required due to restrictions in the communication channel.

Resolutions

Verify that the “don’t fragment” flag is unset. Designing an internal network is also possible in order to avoid fragmentation. For implementation purposes, it is fairly common to use 576-byte datagrams, whenever the entire path availability to handle larger packets cannot be verified.

Additional

Monitors the number of failed fragments during the fragmentation process.

Element properties:

Target

Jalasoft.Xian.Common.Types.ThirdParty.F5Networks.JsXF5BigIpV9SnmpInterfaceElementContainer

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

Fragmentation failed Alert

{0}

Source Code:

<AggregateMonitor ID="Jalasoft.Xian.SmartManagementPacks.F5BigIp.FragmentationFailed.1.2" Accessibility="Public" Enabled="true" Target="ThirdParty_F5Networks!Jalasoft.Xian.Common.Types.ThirdParty.F5Networks.JsXF5BigIpV9SnmpInterfaceElementContainer" ParentMonitorID="SystemHealth!System.Health.PerformanceState" Remotable="true" Priority="Normal">

  <Category>StateCollection</Category>

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