Cisco Router: Large buffer created Health Monitor

Jalasoft.Xian.SmartManagementPacks.CiscoRouters.LargeBufferCreated.1.1 (AggregateMonitor)

This monitor catches Xian events that notifies when the Large buffer created if has changed its state.

Knowledge Base article:

Summary

Number of created large buffers is over threshold.

The number of large buffers created is above the maximum threshold configured in Xian Network Manager 2012.

Causes

After buffer failures, the router is creating an excessive amount of large buffers in order to manage packets according to requirements, but they are not releasing the buffers, thus generating insufficience of free large buffers. This can be done because of a buffer leak.

Resolutions

Analyze the buffer sizes and strategies for handling overflows and perform buffer tuning. Sometimes it can be solved just by updating your Cisco IOS. Use 'show buffers old' to get more information and find the problem.

Additional

Monitors the number of large buffers created on a Cisco Router.

Element properties:

Target

Jalasoft.Xian.Common.Types.ThirdParty.Cisco.JsXCiscoRouterMemoryPoolElementContainer

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

Large buffer created Alert

{0}

Source Code:

<AggregateMonitor ID="Jalasoft.Xian.SmartManagementPacks.CiscoRouters.LargeBufferCreated.1.1" Accessibility="Public" Enabled="true" Target="ThirdParty_Cisco!Jalasoft.Xian.Common.Types.ThirdParty.Cisco.JsXCiscoRouterMemoryPoolElementContainer" ParentMonitorID="SystemHealth!System.Health.PerformanceState" Remotable="true" Priority="Normal">

  <Category>StateCollection</Category>

  <AlertSettings AlertMessage="LargeBufferCreated_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>