Home
  •  

P-bit Severely Errored Seconds

Microsoft.SystemCenter.NetworkDevice.Interface.DS3E3.PSESThresholdMonitor (UnitMonitor)

Knowledge Base article:

Summary

P-Bit Severely Errored Seconds Threshold Monitor. This monitor is configured to get the PSESs count from the interface for the past 15 minute interval.

Causes

Below are the details of the Object Identifier (OID) that is queried via an SNMP GET

Object

OID

Description

dsx3IntervalPSESs

.1.3.6.1.2.1.10.30.7.1.4

An P-bit Severely Errored Second is a second with 44 or more Path Code Violations OR one or more Out of Frame defects OR a detected incoming AIS. This is not incremented when UASs are counted.

This is defined in RFC 1407

Additional Information:

Resolutions

Below are some basic troubleshooting steps

  1. Check the cabling to the device.

  2. Perform any vendor specific hardware tests on the device to determine if the device's hardware is functioning properly

  3. Call your circuit vendor to have them look at your circuit.

  4. Raise the threshold on the monitor. This will allow for better "tuning" of the application to your environment. Take care no to raise the threshold too much as this could allow important events to go unnoticed.

Element properties:

TargetMicrosoft.SystemCenter.NetworkDevice.Interface.DS3E3
Parent MonitorSystem.Health.PerformanceState
CategoryPerformanceHealth
EnabledFalse
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveFalse
Monitor TypeMicrosoft.SystemCenter.NetworkDevice.SnmpThresholdMonitorType
RemotableTrue
AccessibilityPublic
Alert Message
P-bit Severely Errored Seconds Exceed Threshold
The count of P-bit severely errored seconds (PSES) on this interface has exceeded the defined threshold for the last 15 minute interval.
RunAsDefault

Source Code:

<UnitMonitor ID="Microsoft.SystemCenter.NetworkDevice.Interface.DS3E3.PSESThresholdMonitor" Accessibility="Public" Enabled="false" Target="Microsoft.SystemCenter.NetworkDevice.Interface.DS3E3" ParentMonitorID="Health!System.Health.PerformanceState" Remotable="true" Priority="Normal" TypeID="Microsoft.SystemCenter.NetworkDevice.SnmpThresholdMonitorType" ConfirmDelivery="false">

  <Category>PerformanceHealth</Category>

  <AlertSettings AlertMessage="Microsoft.SystemCenter.NetworkDevice.Interface.DS3E3.PSESThresholdMonitor.AlertMessage">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>false</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

  </AlertSettings>

  <OperationalStates>

    <OperationalState HealthState="Success" MonitorTypeStateID="UnderThreshold" ID="BelowThreshold"/>

    <OperationalState HealthState="Error" MonitorTypeStateID="OverThreshold" ID="AboveThreshold"/>

  </OperationalStates>

  <Configuration>

    <Interval>180</Interval>

    <IP>$Target/Host/Property[Type="NetworkDevice!Microsoft.SystemCenter.NetworkDevice"]/IPAddress$</IP>

    <CommunityString>$Target/Host/Property[Type="NetworkDevice!Microsoft.SystemCenter.NetworkDevice"]/CommunityString$</CommunityString>

    <Version>$Target/Host/Property[Type="NetworkDevice!Microsoft.SystemCenter.NetworkDevice"]/Version$</Version>

    <SnmpVarBinds>

      <SnmpVarBind>

        <OID>1.3.6.1.2.1.10.30.7.1.4.$Target/Property[Type="Microsoft.SystemCenter.NetworkDevice.Interface"]/ifIndex$.1</OID>

        <Syntax>2</Syntax>

        <Value VariantType="3"/>

      </SnmpVarBind>

    </SnmpVarBinds>

    <Threshold>0</Threshold>

  </Configuration>

</UnitMonitor>