Show dsl interface error output

[Johan de Greef]

Hi all,

I was troubleshooting a faulty DSL interface when I found some error in my 'show dsl int atm 0' command. I got the following output:

FEC ES Errors:    0                               0

ES Errors:            0                               1

SES Errors:         0                               0

LOSES Errors:    0                               0

UES Errors:         0                              20727337

Obviously there is something wrong to get so many errors, but can somebody explain what these errors mean and what may be causing them?

I've browsed the CCNP course books and googled for an explanation, but nobody seems to have an step-by-step explanation for the output.

Thanks in advance,

Kind Regards,

Johan de Greef

[johnlloyd_13]

kindly post your full sh dsl int atm0 output and sh int atm0 | i error. i would usually look out for the attenuation and noise margin output. if you observe these errors keeps on incrementing, i would suggest to have your isp/telco provider technician check on the link and re-punch any faulty wiring.

[Johan de Greef]

Hi Johnlloyd,

Thanks for your answer. This is the complete 'show dsl interface' output:

ATM0/0/0

Alcatel 20190 chipset information

                ATU-R (DS)                      ATU-C (US)

Modem Status:    Showtime (DMTDSL_SHOWTIME)

DSL Mode:        ITU G.992.5 (ADSL2+) Annex A

ITU STD NUM:     0x03                            0x2

Chip Vendor ID:  'STMI'                          'BDCM'

Chip Vendor Specific:  0x0000                    0x6291

Chip Vendor Country:   0x0F                      0xB5

Modem Vendor ID: 'CSCO'                          '    '

Modem Vendor Specific: 0x0000                    0x0000

Modem Vendor Country:  0xB5                      0x00

Serial Number Near:    FOC13315RE2CISCO73993206

Serial Number Far:  Chip ID:     C196 (0)

DFE BOM:         DFE3.0 Annex A (1)

Capacity Used:   31%                             100%

Noise Margin:    22.0 dB                         11.5 dB

Output Power:    18.5 dBm                        12.0 dBm

Attenuation:     15.0 dB                          5.0 dB

FEC ES Errors:    0                               0

ES Errors:            0                               1

SES Errors:         0                               0

LOSES Errors:    0                               0

UES Errors:         0                              20727337

The capacity used in 100%, and I read that it should be under 80/85%. We contacted te provider to fix the problem, but I was just wondering wat these errors are and what might be causing them.

Although there are numerous UES errors, there are no errors in the show int output, so the two seem unrelated:

show int atm 0/0/0 | i errors
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     0 output errors, 0 collisions, 0 interface resets

[johnlloyd_13]

hi johan,

i agree, both seemed to be unrelated. strange, i haven't seen that output (UES) before even with "training log" enabled on our ADSL routers. could you post your show version output? let's see what your provider has to say.

877(config-if)#dsl enable-training-log

877#sh dsl int atm0
                ATU-R (DS)                      ATU-C (US)
Modem Status:    Showtime (DMTDSL_SHOWTIME)
DSL Mode:        ITU G.992.1 (G.DMT)
ITU STD NUM:     0x01                            0x01
Vendor ID:       'ALCB'                          'GSPN'
Vendor Specific: 0x0000                          0x0008
Vendor Country:  0x00                            0xFF
Capacity Used:   65%                             114%
Noise Margin:    31.0 dB                          8.0 dB
Output Power:     8.0 dBm                        10.0 dBm
Attenuation:      6.5 dB                          7.5 dB
Defect Status:   None                            None                       
Last Fail Code:  None
Selftest Result: 0x00
Subfunction:     0x15
Interrupts:      3907 (1 spurious)
Activations:     262
Init FW:         embedded
Operartion FW:   embedded
SW Version:      3.9.220
FW Version:      0x1A04

                 Interleave             Fast    Interleave              Fast
Speed (kbps):             0             3520             0               160
Reed-Solomon EC:          0                0             0                 0
CRC Errors:               0                0             0              6026
Header Errors:            0                0             0               995
Bit Errors:               0                0
BER Valid sec:            0                0
BER Invalid sec:          0                0

LOM Monitoring : Disabled

DMT Bits Per Bin
00: 0 0 0 0 0 0 0 4 5 4 4 4 3 3 3 3
10: 3 3 3 2 2 2 2 2 2 2 2 2 2 2 0 0
20: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
30: 0 0 0 0 0 0 0 0 0 0 0 0 2 0 0 2
40: 0 2 2 2 2 2 2 2 2 2 2 2 3 3 3 4
50: 4 4 4 4 4 4 2 5 4 5 5 5 5 5 5 5
60: 5 5 6 6 6 6 7 7 7 7 7 7 8 7 7 7
70: 7 7 7 6 7 6 6 6 6 6 6 6 5 5 5 5
80: 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5
90: 5 5 5 5 5 5 6 6 6 6 6 6 6 6 7 7
A0: 7 7 7 7 7 7 7 8 8 8 8 8 8 8 8 7
B0: 8 8 7 7 7 7 7 7 7 7 7 7 7 6 6 6
C0: 6 6 6 6 6 6 6 6 6 6 5 6 6 5 5 5
D0: 6 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5
E0: 5 5 5 5 5 5 5 5 5 5 4 5 5 4 5 4
F0: 4 4 4 4 4 0 0 0 0 0 0 0 0 0 0 0

Training log enabled, but not collected yet, beacuse
there have been no state transitions since log was enabled.
You can force a state transition through unplug/plug DSL line.

[Johan de Greef]

Hi Johnlloyd,

This is the output of the show ver command:

Cisco IOS Software, 1841 Software (C1841-BROADBAND-M), Version 12.4(24)T, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Wed 25-Feb-09 15:54 by prod_rel_team

ROM: System Bootstrap, Version 12.4(13r)T, RELEASE SOFTWARE (fc1)

RT-TTG01250-HOO-01 uptime is 2 weeks, 5 days, 20 hours, 18 minutes
System returned to ROM by power-on
System image file is "flash:c1841-broadband-mz.124-24.T.bin"

Cisco 1841 (revision 7.0) with 117760K/13312K bytes of memory.
Processor board ID FHK12052CMZ
2 FastEthernet interfaces
1 ATM interface
DRAM configuration is 64 bits wide with parity disabled.
191K bytes of NVRAM.
31360K bytes of ATA CompactFlash (Read/Write)

Configuration register is 0x2102

In the organization we use a combination of 1841's and 837's. I checked an 837, but couldn't find the errors in the show dsl command. When I checked another 1841 the error counters showed up, so it appears to be a 'feature' of 1841's.

[paolo bevilacqua]

The capacity used in 100%, and I read that it should be under 80/85%. We contacted te provider to fix the problem, but I was just wondering wat these errors are and what might be causing them.

Capacity at 100% is absolutely not a problem, and is common for high speeds in presence of some .loop impairment.

The high number of UES could even be a bug in firmware counting erroneosly.

Bottom line if you  have the real performacnes you're paying for, there is nothing to worry about.

[Johan de Greef]

Hi Paolo,

We are getting the performance we are paying for, but it seems strange that you've got an error counter which no one seems to be able to explain or knows about.

Our best friend Google also didn't know, so maybe I should and go ask Cisco.

[paolo bevilacqua]

ES= Errored Seconds.

U could be Unavailable, although the correct acronym for that would be US, not UES.

However as I mentioned the number is so high that seem to be random.

[Johan de Greef]

Yes, ES = Errored Seconds, but SES is Severe Errored Seconds and 10 ES translate into 1 SES. It would be pointless to translate 10 SES into 1 UES, because you would get multiple counters that hold the same information.

And the ES en SES counters would have to be cleared, because I've got 20 million UES errors, but only 1 ES error.

I checked many different 1841's at different customer sites, but every single one of them had UES errors. I`m beginning to wonder if these errors are always occuring but are not hampering normal service.

[paolo bevilacqua]

Do these increase any second ? I'm telling you, Cisco has many cosmetic bugs, this can be one.

[Johan de Greef]

Hi Paolo,

No, they don't increase every second. In the last week I haven't seen these numbers change.