This monitor catches Xian events that notifies when the Fragments created if has changed its state.
Number of created fragments is over threshold.
The number of fragments created is above the maximum threshold configured in Xian Network Manager 2012.
If the counter is at a suspect level, there might be a capacity problem, but this procedure could be required because of restrictions in the communication channel or also to reduce latency.
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 fragments created by the fragmentation process on the device.
Target | Jalasoft.Xian.Common.Types.ThirdParty.Cisco.JsXCiscoPixFirewallSnmpInterfaceElementContainer | ||
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.CiscoPix.FragmentsCreated.1.1" Accessibility="Public" Enabled="true" Target="ThirdParty_Cisco!Jalasoft.Xian.Common.Types.ThirdParty.Cisco.JsXCiscoPixFirewallSnmpInterfaceElementContainer" ParentMonitorID="SystemHealth!System.Health.PerformanceState" Remotable="true" Priority="Normal">
<Category>StateCollection</Category>
<AlertSettings AlertMessage="FragmentsCreated_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>