This monitor catches Xian events that notifies when the Reassembly requests if has changed its state.
Reassembly requests are over threshold.
The number of reassembly requests is above the maximum threshold configured in Xian Network Manager 2012.
If the counter is at a suspect level, it may be a capacity problem, but this procedure may be necessary because every network that a packet has traveled over, could have a different frame size.
Verify network configuration in order to establish if the high amount of reassembly requests is correct.
Monitors the number of reassembly requests that were received 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.ReassemblyRequests.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="ReassemblyRequests_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>