This monitor catches Xian events that notifies when the Free huge buffers has changed its state.
Number of free huge buffers is under threshold.
The number of available huge buffers is below the minimum threshold configured in Xian Network Manager 2012.
The device is assigning packets to an excessive amount of huge buffers in order to manage them according to requirements, but those are not releasing the buffers, thus generating insufficiency of free huge buffers. It can be done because of a buffer leak.
Analyze the buffer sizes and strategies for handling overflows and reconfigure. Sometimes it can be solved just by updating your Cisco IOS. Use 'show buffers old' command to get more information and find the problem.
Monitors the number of free huge buffers on a Cisco Wireless device.
Target | Jalasoft.Xian.Common.Types.ThirdParty.Cisco.JsXCiscoWirelessMemoryPoolElementContainer | ||
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.CiscoWireless.FreeHugeBuffers.1.1" Accessibility="Public" Enabled="true" Target="ThirdParty_Cisco!Jalasoft.Xian.Common.Types.ThirdParty.Cisco.JsXCiscoWirelessMemoryPoolElementContainer" ParentMonitorID="SystemHealth!System.Health.PerformanceState" Remotable="true" Priority="Normal">
<Category>StateCollection</Category>
<AlertSettings AlertMessage="FreeHugeBuffers_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>