Home
  •  

Cisco Router: DS1 current severely errored framing seconds Health Monitor

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

This monitor catches Xian events that notifies when the DS1 current severely errored framing seconds has changed its state.

Knowledge Base article:

Summary

Number of DS1 Current Severely Errored Framing Seconds is over threshold.

The number of Current Severely Errored Framing Seconds in the current 15-minute interval is above the maximum threshold configured in Xian Network Manager 2012.

Causes

A Severely Errored Framing Second is a second with one or more Out of Frame defects OR a detected AIS defect.

Out of Frame defects or a detected AIS defect.

Resolutions

Once an Out of Frame defect is declared, the framer starts searching for a correct framing pattern and ends when the signal is in frame. The Alarm Indication Signal failure is declared when an AIS defect is detected at the input and the AIS defect still exists after the Loss Of Frame failure which is caused by the unframed nature of the 'all-ones' signal is declared. The AIS failure is cleared when the Loss Of Frame failure is cleared.

Additional

This rule monitors the number of Severely Errored Framing Seconds encountered by a DS1 interface in the current interval.

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
DS1 current severely errored framing seconds Alert
{0}

Source Code:

<AggregateMonitor ID="Jalasoft.Xian.SmartManagementPacks.CiscoRouters.DS1CurrentSeverilyErroredFramingSeconds.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="DS1CurrentSeverilyErroredFramingSeconds_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>