This monitor catches Xian events that notifies when the Deleted corrupted packet buffers if has changed its state.
Number of deleted corrupted packet buffers is over threshold.
The number of corrupted packet buffers that were deleted is above the maximum threshold configured in Xian Network Manager 2012.
The switch is detecting a large amount of corrupted packet buffers. This vulnerability is likely due to a memory corruption bug, and may be an exploitable buffer overflow.
An excessive amount of corrupted packet buffers may lead to a traffic slow down. Analyze the buffer strategies for handling message buffers and perform buffer tuning, if necessary.
Monitors the number of times a corrupted packet buffer has been deleted.
Target | Jalasoft.Xian.Common.Elements.ThirdParty.HP.JsXPacketBufferElement | ||
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.HPProCurveSwitches.DeletedCorruptedPacketBuffers.1.1" Accessibility="Public" Enabled="true" Target="ThirdParty_HP!Jalasoft.Xian.Common.Elements.ThirdParty.HP.JsXPacketBufferElement" ParentMonitorID="SystemHealth!System.Health.PerformanceState" Remotable="true" Priority="Normal">
<Category>StateCollection</Category>
<AlertSettings AlertMessage="DeletedCorruptedPacketBuffers_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>