This monitor catches Xian events that notifies when the Output packet queue length has changed its state.
Output packet queue length is over threshold.
The number of packets is above the maximum threshold configured in Xian Network Manager 2012.
If the queue length is excessive for continuous periods, then you probably have a network bottleneck. It can be because your interface speed is less than the bandwidth of the network. Other causes may be excesive traffic and even probable SPAM or virus in the net.
If the problem is your interface speed, upgrade the interface. If the problem is the load, verify if it is an expected behavior and eventually redistribute load between other switches or gateways.
Monitors the length of output packet queue on any interface of a Cisco Switch.
Target | Jalasoft.Xian.Common.Elements.ThirdParty.Cisco.JsXCiscoSwitchInterfaceElement | ||
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.CiscoSwitches.OutputPacketQueueLength.1.1" Accessibility="Public" Enabled="true" Target="ThirdParty_Cisco!Jalasoft.Xian.Common.Elements.ThirdParty.Cisco.JsXCiscoSwitchInterfaceElement" ParentMonitorID="SystemHealth!System.Health.PerformanceState" Remotable="true" Priority="Normal">
<Category>StateCollection</Category>
<AlertSettings AlertMessage="OutputPacketQueueLength_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>