Last module self-test (done at startup) Passed Last clearing of alarm counters 00:03:01 loss of signal loss of frame AIS alarm Remote alarm Module access errors : Total Data (last 96 15 minute intervals): 258 Line Code Violations, 257 Path Code Violations 33 Slip Secs, 309 Fr Loss Secs, 37 Line Err Secs, 1 Degraded Mins 1 Errored Secs, 1 Bursty Err Secs, 0 Severely Err Secs, 320 Unavail Secs Data in current interval (153 seconds elapsed) 0 Line Code Violations, 0 Path Code Violations 0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins 0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs This output looks a lot better. It includes the welcome phrase "receiver has no alarms," and it indicates that we've just cleared the alarms, and no errors or alarms have been received since. The last two paragraphs of the output are especially important. CSU/DSUs usually keep track of all the events that have occurred during the previous 24 hours. These events are recorded in 15-minute intervals and reported as such. The first paragraph (Total Data), while alarming, is not as important as the next paragraph (Data in current interval), which shows us the events that have occurred during the current interval. This can be a bit confusing, SO let's take a closer look. By using the command show service-module interface performance-statistics, we can see which events occurred during each of the last 96 15-minute intervals: Router# sho service-module s0/1 performance-statistics Total Data (last 96 15 minute intervals): 258 Line Code Violations, 257 Path Code Violations 33 Slip Secs, 309 Fr Loss Secs, 37 Line Err Secs, 1 Degraded Mins 1 Errored Secs, 1 Bursty Err Secs, 0 Severely Err Secs, 320 Unavail Secs Data in current interval (380 seconds elapsed) : 0 Line Code Violations, 0 Path Code Violations 0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins 0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs Data in Interval 1: 1 Line Code Violations, 2 Path Code Violations 0 Slip Secs, 