Controlled Slip Seconds Threshold Monitor. This monitor is configured to get the CCSs count from the interface for the past 15 minute interval.
Below are the details of the Object Identifier (OID) that is queried via an SNMP GET
Object | OID | Description |
|---|---|---|
dsx1IntervalCSSs | .1.3.6.1.2.1.10.18.8.1.7 | A Controlled Slip Second is a one-second interval containing one or more controlled slips. A Controlled Slip is the replication or deletion of the payload bits of a digital signal level 1 (DS1) frame. A Controlled Slip may be performed when there is a difference between the timing of a synchronous receiving terminal and the received signal. A Controlled Slip does not cause an Out of Frame defect. This is defined in RFC 1406 |
This can happen when:
There is a clocking issue on the circuit.
Below are some basic troubleshooting steps
Check the cabling to the device.
Verify that there is only one source for clocking on the line. Synchronous networks depend on having one source of clocking truth, and free-running clocks at both ends of a circuit will corrupt data as the two clocks drift in and out of synchronization
There must be no less than one clock source. If two CSU/DSUs are both operating in slave mode, each will look to the other as the source of timing information. Any changes in the timing of one CSU/DSU will affect the partner because both CSU/DSUs are attempting to lock on to the timing information supplied by the other
Perform any vendor specific hardware tests on the device to determine if the device's hardware is functioning properly
Call your circuit vendor to have them look at your circuit.
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.
| Target | Microsoft.SystemCenter.NetworkDevice.Interface.DS1E1 | ||
| Parent Monitor | System.Health.PerformanceState | ||
| Category | PerformanceHealth | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | Error | ||
| Alert Priority | Normal | ||
| Alert Auto Resolve | False | ||
| Monitor Type | Microsoft.SystemCenter.NetworkDevice.SnmpThresholdMonitorType | ||
| Remotable | True | ||
| Accessibility | Public | ||
| Alert Message |
| ||
| RunAs | Default |
Home
ENU <UnitMonitor ID="Microsoft.SystemCenter.NetworkDevice.Interface.DS1E1.CSSThresholdMonitor" Accessibility="Public" Enabled="onEssentialMonitoring" Target="Microsoft.SystemCenter.NetworkDevice.Interface.DS1E1" 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.DS1E1.CSSThresholdMonitor.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>600</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.18.8.1.7.$Target/Property[Type="Microsoft.SystemCenter.NetworkDevice.Interface"]/ifIndex$.1</OID>
<Syntax>2</Syntax>
<Value VariantType="3"/>
</SnmpVarBind>
</SnmpVarBinds>
<Threshold>100</Threshold>
</Configuration>
</UnitMonitor>