This monitor catches Xian events that notifies when the Incoming segments if has changed its state.
Number of incoming segments is over threshold.
The number of incoming segments per second is above the maximum threshold configured in Xian Network Manager 2012.
This count includes the segments received on current connections, including those received in error. The problem can be related to high TCP traffic for this device.
Verify traffic in this device and try to perform some tuning if necessary. It is also recommendable to redistribute the load between other devices if possible.
Monitors the number of segments that were received by the TCP protocol on the device.
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 |
|
<AggregateMonitor ID="Jalasoft.Xian.SmartManagementPacks.F5BigIp.IncomingSegments.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="IncomingSegments_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>