dslreports logo
    All Forums Hot Topics Gallery
spc
Search Topic:
uniqs
1976
share rss forum feed

wingman99

join:2003-12-18
Opelika, AL

3 edits

Cisco 678 what is the Alarm meaning

cbos>s e
- Current Error Messages -
## Ticks Module Level Message
0 000:00:00:00 RADIUS Alarm Accounting failed to call socket
1 000:00:00:00 TRACEROUTE Alarm Failed to call socket
2 000:00:00:13 ATM Info Wan0 Up
3 000:13:04:16 ADSL Info crc_errors(228794) exceeded threshold.
4 000:13:04:16 ATM Info Wan0 Down
5 000:13:04:16 ATM Info WAN 0 physical layer is down
6 000:13:04:16 COMMANDER Info WAN 0 physical layer is down
7 000:13:04:30 ATM Info Wan0 Up
8 000:19:02:56 ADSL Alarm Local SNR Margin: 16.5dB
9 000:19:02:56 ADSL Alarm Overall Failures: 1
10 000:19:02:56 ADSL Alarm Local los: 138
11 000:19:02:56 ADSL Alarm Local sef: 142
12 000:19:02:56 ADSL Alarm Local lcdi: 140
13 000:19:02:56 ADSL Alarm Local SNR Margin: 17.0dB
14 000:19:02:56 ADSL Alarm Overall Failures: 1
15 000:19:02:56 ADSL Alarm Local los: 166
16 000:19:02:56 ADSL Alarm Local sef: 170
17 000:19:02:56 ADSL Alarm Local lcdi: 168
18 000:19:02:57 ADSL Alarm Local SNR Margin: 0.0dB
19 000:19:02:57 ADSL Alarm Overall Failures: 1
20 000:19:02:57 ADSL Alarm Local los: 194
21 000:19:02:57 ADSL Alarm Local sef: 198
22 000:19:02:57 ADSL Alarm Local lcdi: 196
23 000:19:02:57 ATM Info Wan0 Down
24 000:19:02:57 ATM Info WAN 0 physical layer is down
25 000:19:02:57 COMMANDER Info WAN 0 physical layer is down
26 000:19:03:06 ATM Info Wan0 Up
27 000:19:03:06 ADSL Info crc_errors(0) exceeded threshold.
28 000:19:03:06 ATM Info Wan0 Down
29 000:19:03:07 ATM Info WAN 0 physical layer is down
30 000:19:03:07 COMMANDER Info WAN 0 physical layer is down
31 000:19:03:23 ATM Info Wan0 Up
Total Number of Error Messages: 32

cbos#sh int wan0
wan0 ADSL Physical Port
Line Trained
Actual Configuration:
Overhead Framing: 3
Trellis Coding: Enabled
Standard Compliance: T1.413
Downstream Data Rate: 1536 Kbps
Upstream Data Rate: 864 Kbps
Interleave S Downstream: 4
Interleave D Downstream: 16
Interleave R Downstream: 16
Interleave S Upstream: 8
Interleave D Upstream: 8
Interleave R Upstream: 16
Modem Microcode: G96
DSP version: 0
Operating State: Showtime/Data Mode
Configured:
Echo Cancellation: Disabled
Overhead Framing: 3
Coding Gain: Auto
TX Power Attenuation: 0dB
Trellis Coding: Enabled
Bit Swapping: Disabled
Standard Compliance: T1.413
Remote Standard Compliance: T1.413
Tx Start Bin: 0x6
Tx End Bin: 0x1f
Data Interface: Utopia L1
Status:
Local SNR Margin: 13.0dB
Local Coding Gain: 8.5dB
Local Transmit Power: 12.3dB
Local Attenuation: 53.5dB
Remote Attenuation: 31.5dB
Local Counters:
Interleaved RS Corrected Bytes: 82917
Interleaved Symbols with CRC Errors: 87
No Cell Delineation Interleaved: 0
Out of Cell Delineation Interleaved: 1
Header Error Check Counter Interleaved: 546
Count of Severely Errored Frames: 65408
Count of Loss of Signal Frames: 0
Remote Counters:
Interleaved RS Corrected Bytes: 373
Interleaved Symbols with CRC Errors: 6
No Cell Delineation Interleaved: 0
Header Error Chec

bobk4000

join:2003-10-17
Saint Paul, MN
kudos:1
Reviews:
·CenturyLink
Wingman99,

The Alarm, Info, etc. are different levels of problems that can be recorded to a Syslog program or using SNMP (Simple Network Management Protocol) on an external computer.

With SNMP, you can create a "trap" that when it receives an Alarm from a device it can send an email or a page to let the appropriate person know that there is a problem with their router or computer. Typically used with real routers and computers, but they did include it with the Cisco 67x family.

Sorry for the delay in answering - I haven't checked this forum in a while.

Hope this helps.
Bob.

wingman99

join:2003-12-18
Opelika, AL
Do you know what is going on with what it says.

bobk4000

join:2003-10-17
Saint Paul, MN
kudos:1
Reviews:
·CenturyLink
reply to wingman99
I've seen entries like that logged when I've either disconnected my 678, or if there is a problem with the physical wiring between the 678 and the central office at the phone company. SNR Margin of 0.0 (or negative) shows up with a total loss of the DSL signals and the WAN0 interface is down.

At your end, it could be a loose or shorted connection anywhere from the Network Interface box back to where you plug in your 678. Getting any static or noise on your telephones? The way to determine if it's inside wiring or Qwest's problem is to open up your Network Interface box, unplug the connector and plug in a phone and check for any noise. If you still get the noise and/or static, then it's the wiring between you and the central office, and Qwest will have to fix it. However, if you now have a noise free phone, then it's something with your inside wiring.

One note, I've got a 1949 house that I redid all the phone wiring, with the exception of the cable that ran from the NID to an old inside surge protector. Guess what wire did short out after Qwest (USWest) added the Network Interface on the side of my house?

Regards,
Bob.

wingman99

join:2003-12-18
Opelika, AL

4 edits
I have a brand new home run installed by Qwest and me. They cant find any more things to try on mine or theirs. I was just wondering if you could tell if there still messing with things on there side or it's still line or DSLAM problem, because i have disconnect my line before and it shows - SNR like you said. The alarm is seldom and the wan down is occasional.

Also wondering why it jumped up to 17.0db set off Alarm
ADSL Alarm Local SNR Margin: 17.0dB

And what does this mean
10 000:19:02:56 ADSL Alarm Local los: 138
11 000:19:02:56 ADSL Alarm Local sef: 142
12 000:19:02:56 ADSL Alarm Local lcdi: 140

And the time about 10 seconds for the Alarm wan down to up
23 000:19:02:57 ATM Info Wan0 Down
24 000:19:02:57 ATM Info WAN 0 physical layer is down
25 000:19:02:57 COMMANDER Info WAN 0 physical layer is down
26 000:19:03:06 ATM Info Wan0 Up

So i can further diagnose this problem.

bobk4000

join:2003-10-17
Saint Paul, MN
kudos:1
Reviews:
·CenturyLink
I'm guessing Qwest may have been working on your line and it was either disconnected or shorted out, causing the drop in signal for a short period of time.

As for the 17 dB logging during the alarms, possibly the line was going up and down, and the 678 did have a good signal momentarily while it was trying to retrain.

Here's what I found for los, sef and lcdi:
LOS - Loss of Signal
SEF - Severely Errored Framing
LCDI - Loop Closure De-bounce Interval (I think.)

I'm no expert on telephone systems and DSL, I only play one on forums.

It looks like your phone line may have been shorted momentarily, maybe when a tech was working on one of the boxes between you and the CO. They might not have been working on your line, but a different line and they caused a problem on yours. Slip of a screwdriver or tool while they were working in one of the boxes? Or working on the wiring back at the CO where they split your phone line between the telephone switch and the DSLAM?

Are these drops and errors happening on a regular basis or was it a one time event?

Bob.

P.S., I learned something new today about those error counters - thanks!

wingman99

join:2003-12-18
Opelika, AL

1 edit
Thanks for your help. That is one of the things i was thinking, that they are working on other lines.

It's kind of random for me.

But in the last two days my connection seems to be better i will give it a week and get back to you .

bobk4000

join:2003-10-17
Saint Paul, MN
kudos:1
reply to wingman99
Happy to help, and I hope your line problems are resolved. I lurk in this forum mainly for Cisco 67x questions that pop up from time to time, so do post back.

Regards,
Bob.

wingman99

join:2003-12-18
Opelika, AL

1 edit
This happened yesterday and the day before

wan0 ADSL Physical Port
Line Trained
Actual Configuration:
Overhead Framing: 3
Trellis Coding: Enabled
Standard Compliance: T1.413
Downstream Data Rate: 1536 Kbps
Upstream Data Rate: 896 Kbps
Interleave S Downstream: 4
Interleave D Downstream: 16
Interleave R Downstream: 16
Interleave S Upstream: 8
Interleave D Upstream: 8
Interleave R Upstream: 16
Modem Microcode: G96
DSP version: 0
Operating State: Showtime/Data Mode
Configured:
Echo Cancellation: Disabled
Overhead Framing: 3
Coding Gain: Auto
TX Power Attenuation: 0dB
Trellis Coding: Enabled
Bit Swapping: Disabled
Standard Compliance: T1.413
Remote Standard Compliance: T1.413
Tx Start Bin: 0x6
Tx End Bin: 0x1f
Data Interface: Utopia L1
Status:
Local SNR Margin: 13.5dB
Local Coding Gain: 8.5dB
Local Transmit Power: 12.3dB
Local Attenuation: 53.5dB
Remote Attenuation: 31.5dB
Local Counters:
Interleaved RS Corrected Bytes: 130940780
Interleaved Symbols with CRC Errors: 233029
No Cell Delineation Interleaved: 232999
Out of Cell Delineation Interleaved: 527399
Header Error Check Counter Interleaved: 200556
Count of Severely Errored Frames: 200231
Count of Loss of Signal Frames: 200231
Remote Counters:
Interleaved RS Corrected Bytes: 276606
Interleaved Symbols with CRC Errors: 333046
No Cell Delineation Interleaved: 300448
Header Error Check Counter Interleaved: 331116
Count of Severely Errored Frames: 429229
Count of Loss of Signal Frames: 363559

cbos#s e
- Current Error Messages -
## Ticks Module Level Message
0 000:00:00:00 RADIUS Alarm Accounting failed to call socket
1 000:00:00:00 TRACEROUTE Alarm Failed to call socket
2 000:00:00:13 ATM Info Wan0 Up
3 002:12:50:05 ADSL Info crc_errors(460729) exceeded threshold.
4 002:12:50:05 ATM Info Wan0 Down
5 002:12:50:06 ATM Info WAN 0 physical layer is down
6 002:12:50:06 COMMANDER Info WAN 0 physical layer is down
7 002:12:50:19 ATM Info Wan0 Up
8 003:03:16:25 ADSL Alarm Local SNR Margin: 18.5dB
9 003:03:16:25 ADSL Alarm Overall Failures: 1
10 003:03:16:25 ADSL Alarm Local los: 139
11 003:03:16:25 ADSL Alarm Local sef: 143
12 003:03:16:25 ADSL Alarm Local lcdi: 140
13 003:03:16:25 ADSL Alarm Local SNR Margin: 20.0dB
14 003:03:16:25 ADSL Alarm Overall Failures: 1
15 003:03:16:25 ADSL Alarm Local los: 167
16 003:03:16:25 ADSL Alarm Local sef: 171
17 003:03:16:25 ADSL Alarm Local lcdi: 168
18 003:03:16:26 ADSL Alarm Local SNR Margin: 21.0dB
19 003:03:16:26 ADSL Alarm Overall Failures: 1
20 003:03:16:26 ADSL Alarm Local los: 195
21 003:03:16:26 ADSL Alarm Local sef: 199
22 003:03:16:26 ADSL Alarm Local lcdi: 196
23 003:03:16:26 ATM Info Wan0 Down
24 003:03:16:26 ATM Info WAN 0 physical layer is down
25 003:03:16:26 COMMANDER Info WAN 0 physical layer is down
26 003:03:16:35 ATM Info Wan0 Up
27 003:03:16:37 ADSL Info crc_errors(0) exceeded threshold.
28 003:03:16:37 ATM Info Wan0 Down
29 003:03:16:38 ATM Info WAN 0 physical layer is down
30 003:03:16:38 COMMANDER Info WAN 0 physical layer is down
31 003:03:16:51 ATM Info Wan0 Up
Total Number of Error Messages: 32

cbos#
cbos#stat wan0
Physical WAN Port 0 Statistics
# of dropped cells: 0 # of invalid cells: 0
# of CRC errors: 0
# of processed OAM loopback cells
segment: 0 end-to-end: 0

cbos#stat wan0-0
WAN0-0 Statistics
# of packets Rx: 295518 Tx: 964546
# of packets Rx errors: 0
# of wrong byte counts Rx: 0
# of out of Rx buffers: 0
# of too large packets Rx: 0
# of bytes Rx: 38788761 Tx: 149149306
# of packets to Tx: 3
# of rejected Tx packets: 0
# of Tx discards due to buffer usage policing: 0
total # of Tx errors: 0
# of processed OAM loopback cells
segment: 0 end-to-end: 0

cbos#sh process

Process Status Report
[TYPE] [NAME] [PRESENT] [ACCEPTING] [MEMORY]
---------------------------------------------------------------------
DRIVER D100 Ethernet Driver Yes 27648
DRIVER ATM WAN Driver Yes 17440
PROTOCOL Spanning Tree Yes 3072
TRANSPORT TCP Transport Yes 0
APPLICATION Sockets Interface Yes 240
APPLICATION RADIUS Accounting Yes No 0

System memory: In use: 535808 Available: 939407

Stack: 366824 bytes remain (0x1022AFB8 highest used)

CPU idle percentage: 99.40

cbos#sh chksum
Warning: traffic may pause for 5-6 seconds while checksum is being calculated!
image: pass
monitor: pass
user config: pass
custom config: MIX header/trailer not found

bobk4000

join:2003-10-17
Saint Paul, MN
kudos:1
Reviews:
·CenturyLink

1 edit
reply to wingman99
Wingman99,

Your 'Interleaved RS Corrected Bytes:' value is huge; I just checked mine and after 27 days of running, it's about 1/10th of yours. And I've received a whole bunch more bytes than you in that period based on my WAN0-0 stats.

Qwest should be seeing those same errors at the DSLAM at the central office - if you call into support, do they have any ideas? I know you have been down that path before, but maybe you will get lucky and find a knowledgeable tech who might do some digging.

As to where the problem is, well, wiring between you and the CO; DSLAM port, or possibly your Cisco? I've seen your posts over in the Qwest forum, but I can't remember if you have swapped out modems to see if the problem remains or not. Maybe rent an Actiontec and see if that helps - then you would know it's your Cisco, unfortunately.

Other things to try - if your ISP isn't Qwest, drop them a line and see if they will work with Qwest to get this resolved. If your ISP is Qwest I've used the following link to send them some feedback about how frustrated I was back when I tried to order the upgrade from CAP to DMT:

»www3.qwest.com/cgi-bin/qwest.cfg ··· /ask.php

Give them lots of details including all the visits from techs, the number of times you have called into support for help and use words like "disappointed", "frustrated", "discouraged", etc. instead of yelling and screaming, and you may be surprised when you get a call from someone at Qwest who was assigned to look into your problem and get it resolved. It worked for me when I kept getting a run around from their order entry folks.

Hope this helps.
Bob.

wingman99

join:2003-12-18
Opelika, AL

4 edits
I called them 12 times 6 different technicians came out. Also level 3 wanted to lower my speed but i told them to please fix the Disconnecting problem that i have once hour.

It's allot better than it was and my upload speed is better. Interleaving is working better more correction's
and allot less CRC errors. I only have 10 CRC errors know. How many do you have

If i call again they will probably lower my speed unless i can cum up with the fix. i still think it's a line problem but they said that they changed all my lines but i still wonder if they got the F3. They cut F1 twice then F2. I asked if they switched F3 and the one tech said yes they got them all.

Maybe all the F1 underground bundle's were involved with some kind of construction or repair this summer. I asked they did not know of any but they didn't check ether.

They switched F2 fore me without any line problems
detected with the meter just to try that was nice of him.

Ive seen them do more fore me than anyone else in these forms. It took allot of me helping and coordinating there efforts so that they would try different things instead of the easy way to fix it by lowering my speed, once they do that they wont give it back, it's called truble shooting tool. I call it Qwest money saver.

My SNR was 17db before all the trouble

I was collaborating with the last technician that I probably had two problems one at the DSLAM and one out on the line somewhere he agreed but he can't find it because it's so intermittent.

They changed the dslam box,line card that helped the most
my line goes down about 3 times a week just wondering if there working on it because some weeks it improves then it got worse now it's allot better.

»Wan0 Down i need help im at a loss

I swapped modems.

bobk4000

join:2003-10-17
Saint Paul, MN
kudos:1
Reviews:
·CenturyLink
I'll say one thing about this thread; I've learned a lot more about telecom and DSL terminology! Had to look up F1 & F2 (Feeder cable and Distribution cable). F3 - is that back at the central office?

What follows is my random thoughts while thinking out loud about the drops and retrains... (And you probably have been through all these anyway.)

So, it's not your modem(s) - has Qwest checked to see if there is a T1 line in your bundle? I've read where the T1's signal can cause a lot of crosstalk and interference with a DSL line. But I'm sure Qwest has checked for that, IF there is anything they can do about it.

Yeah, I'd say it's in Qwest's network, or something really, really funky with your Network Interface box. (Grounding issue?) No alarm system, DishTV or water meter plugged into your phone line needing a filter. (I'm sure you checked that.) Can you disconnect all phones and just run with your 678 and still get it to act up? That would eliminate all your inside wiring. Swapped DSL filter(s), in case one of those is doing something odd? Any phone line protection between your 678 and where you plug in? (I'm running mine through an APC UPS - it has surge protection for a modem.)

Another thought, do you have an overhead drop to your Network Interface box, or is it underground like I have? The reason I ask is a client of mine just had their overhead cables replaced since they took a direct hit from lightning earlier this summer. Everything still worked even with the melted cables, except there was a lot of noise on a couple of modem lines used to call out to communicate with their cash registers in their convenience stores.

Had lots of rain, or can you correlate rainstorms to when the line acts up?

I'm not sure if Qwest can or will do this - there are cable testers that will shoot a signal down a pair of wires (TDR - Time Domain Reflectometry) which will show any problems in the line on a display by measuring the reflected or returned signal. It can show splices, signal drops, all sorts of things.

Yeah, I'm really grasping at straws right now trying to think of anything else that might be causing your problem. Well, if you do get it resolved without having to drop your speed, shoot me an email or post back because I really would like to know what the problem was!

Since you asked about CRC errors, I'll post what I'm getting with my Cisco.

Regards,
Bob.

cbos>show uptime
Current uptime is 28 days, 1 hours and 9 minutes

(Nothing in the error log other than the usual startup entries at 0 uptime.)

cbos>show int wan0
wan0 ADSL Physical Port
Line Trained
Actual Configuration:
Overhead Framing: 3
Trellis Coding: Enabled
Standard Compliance: T1.413
Downstream Data Rate: 1536 Kbps
Upstream Data Rate: 1024 Kbps
Interleave S Downstream: 4
Interleave D Downstream: 16
Interleave R Downstream: 16
Interleave S Upstream: 4
Interleave D Upstream: 8
Interleave R Upstream: 16
Modem Microcode: G96
DSP version: 0
Operating State: Showtime/Data Mode
Configured:
Echo Cancellation: Disabled
Overhead Framing: 3
Coding Gain: Auto
TX Power Attenuation: 0dB
Trellis Coding: Enabled
Bit Swapping: Disabled
Standard Compliance: T1.413
Remote Standard Compliance: T1.413
Tx Start Bin: 0x6
Tx End Bin: 0x1f
Data Interface: Utopia L1
Status:
Local SNR Margin: 35.5dB
Local Coding Gain: 6.5dB
Local Transmit Power: 12.5dB
Local Attenuation: 23.0dB
Remote Attenuation: 22.5dB
Local Counters:
Interleaved RS Corrected Bytes: 1829139
Interleaved Symbols with CRC Errors: 1176663
No Cell Delineation Interleaved: 1895360
Out of Cell Delineation Interleaved: 1373248
Header Error Check Counter Interleaved: 1176169
Count of Severely Errored Frames: 1470528
Count of Loss of Signal Frames: 915264
Remote Counters:
Interleaved RS Corrected Bytes: 1455178
Interleaved Symbols with CRC Errors: 1568971
No Cell Delineation Interleaved: 1667264
Header Error Check Counter Interleaved: 1470789
Count of Severely Errored Frames: 1177280
Count of Loss of Signal Frames: 1504192

cbos>stats wan0-0
WAN0-0 Statistics
# of packets Rx: 2660939 Tx: 2137831
# of packets Rx errors: 67
# of wrong byte counts Rx: 0
# of out of Rx buffers: 0
# of too large packets Rx: 0
# of bytes Rx: 2516493267 Tx: 232068034
# of packets to Tx: 7
# of rejected Tx packets: 0
# of Tx discards due to buffer usage policing: 0
total # of Tx errors: 0
# of processed OAM loopback cells
segment: 0 end-to-end: 2

wingman99

join:2003-12-18
Opelika, AL

2 edits
The F1 was cut twice. It is the feeder that goes underground, my SNR staid at the same loss of 5-6db however the upload speed went to 896 that was great. F2 is ditrubution overhead for me. They did not tell me where F3 was at.

I did not know that T1 line could crosstalk is that a constant noise. Also i just read that DSL When adjacent pairs couple together they can cause disconnects do to rate drop. »www.dslprime.com/a/adsl21.pdf

I live near a hospital

I have had two Homeruns installed by Qwest and me also just before the last one i disconnected the phone lines at the NID to test.

I do have a overhead line drop that is not that old
you would think that they would have detected a problem with testing and inspection.

They did do several what is called local loop metal line test and it was fine

How did they find the problem with your clients line drop.

How far from the DSLAM are you.

bobk4000

join:2003-10-17
Saint Paul, MN
kudos:1
Reviews:
·CenturyLink
reply to wingman99
While I don't know all the terms and details of telco testing, the local loop metal line test sounds like they used a TDR like device to check the condition of the physical line from the CO to your home, or vice versa.

The T1 interference was something I read about long ago, and came to mind with your problem. Your local hospital may be using dedicated (or even redundant) data and phone lines separate from residential, however, I do contract work for a small law firm that uses a T1 for both data and phone service. It's in a small office park across the street from a bunch of homes, so folks over in the homes (or even others in the office park) may have problems with crosstalk from T1 lines near the DSL lines.

As for my client with the melted overhead wires - it was sort of funny. They had noise on several of their phone lines again, and Qwest came out to check for blown surge protectors in the box by the street where they have had problems before. (Distribution lines are underground to that point, then the line goes up a power pole and across to the building.) Things checked fine at the box, but they had lots of noise on the lines at the demark inside the building. So the tech figured it was between the building and the box, and as he looked up at the wires, that's when he noticed they were melted. It must have happened this summer when they had a nearby lightning strike one Sunday morning, since I had to stop in on Monday morning to fix a monitor and a computer that went down.

Actually, it was a weird summer for lightning around here; in June I had a number of drops and retrains on my line which I figured were caused by nearby strikes in my neighborhood. I started running Kiwi Syslog to log any problems on my DSL line with a readable timestamp, and of course it hasn't logged a single problem since then. Well, at least it's easier than trying to figure out the math between the current time, the Cisco uptime and the time of the event in the error log.

As for me, I'm about 7,000' from the central office, with underground wire the entire way up to my house. I seem to have a very quiet and stable phone line; back when I had CAP encoding the SNR would stay around 45dB all the time. Took me a while to get used to DMT's average SNR numbers when I upgraded my service to 1.5M.

I think there is a member of my church that works for Qwest and the next time I'm chatting with him I'll ask what a F3 line is in telco lingo.

Bob.