Home
  •  

Cisco Router: Ethernet SQE test errors Health Monitor

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

This monitor catches Xian events that notifies when the Ethernet SQE test errors if has changed its state.

Knowledge Base article:

Summary

Number of ethernet SQE test errors is over threshold.

The number of SQE test error messages generated is above the maximum threshold configured in Xian Network Manager 2012.

Causes

The SQE TEST ERROR is set in accordance with the rules to verify SQE detection mechanism in the PLS Carrier Sense Function as described in IEEE Std. 802.3, 1998 Edition, section 7.2.4.6.

Excessive collisions are being reported possibly due to misconfigured network or a device transmitting when it should not be and stepping on other packets.

Resolutions

Verify the physical plant, transceivers, ground loops (if the cable is grounded at two points), faulty cables or if a station is incorrectly connected to the network

Additional

Monitors the number of times that the SQE TEST ERROR message is generated by the PLS sublayer for a particular interface.

Element properties:

TargetJalasoft.Xian.Common.Elements.ThirdParty.Cisco.JsXCiscoRouterSnmpInterfaceElement
Parent MonitorSystem.Health.PerformanceState
AlgorithmWorstOf
CategoryStateCollection
EnabledTrue
Alert GenerateTrue
Alert SeverityMatchMonitorHealth
Alert PriorityLow
Alert Auto ResolveTrue
RemotableTrue
AccessibilityPublic
Alert Message
Ethernet SQE test errors Alert
{0}

Source Code:

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

  <Category>StateCollection</Category>

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