This monitor catches Xian events that notifies when the Fragmentation failed if has changed its state.
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.
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.
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.
Monitors the number of failed fragments during the fragmentation process.
Target | Jalasoft.Xian.Common.Types.ThirdParty.Cisco.JsXCiscoVpnConcSnmpInterfaceElementContainer | ||
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.CiscoVPN.FragmentationFailed.1.1" Accessibility="Public" Enabled="true" Target="ThirdParty_Cisco!Jalasoft.Xian.Common.Types.ThirdParty.Cisco.JsXCiscoVpnConcSnmpInterfaceElementContainer" 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>