1841 not routing to Internet with HWIC1-ADSL?

void_main1024 · ‎09-02-2015

Hi everyone,

I've configured an 1841 running ipbasek9-mz.124-24.T with a hwic1-adsl in slot 0.

I'm able to dial up the ADSL2+ circuit and get an IP address from the service provider (BT). I've verified that the username and password is correct and that the line is fully functional by testing with a non-Cisco router.

My problem is that I am unable to get the 1841 router to do anything with the line, ping, resolve DNS or route/NAT. I'm not completely new to Cisco having configured other routers in the past, but this one has got me stumped. Beginning to wonder if I have got a hardware fault.

Can anyone tell me if my config looks OK, and anything I can do to get this to work?

BT-D2#sh ip int br

Interface IP-Address OK? Method Status Protocol

FastEthernet0/0 192.168.10.150 YES NVRAM up up

FastEthernet0/1 unassigned YES NVRAM administratively down down

ATM0/0/0 unassigned YES NVRAM up up

NVI0 192.168.10.150 YES unset up up

Virtual-Access1 unassigned YES unset up up

Virtual-Access2 unassigned YES unset up up

Dialer0 [REMOVED] YES IPCP up up

BT-D2#show run
Building configuration...

Current configuration : 3617 bytes
!
version 12.4
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
!
hostname BT-D2
!
boot-start-marker
boot system flash flash:c1841-ipbasek9-mz.124-24.T.bin
boot-end-marker
!
logging message-counter syslog
logging buffered 51200 warnings
enable secret 5 [REMOVED]
!
no aaa new-model
dot11 syslog
ip source-route
!
!
!
!
ip cef
ip domain name [REMOVED]
ip name-server 208.67.222.222
ip name-server 208.67.220.220
multilink bundle-name authenticated
!
!
!
!
!
username [REMOVED]
username [REMOVED]
archive
log config
hidekeys
!
!
ip ssh time-out 60
ip ssh authentication-retries 2
ip ssh version 2
!
!
!
interface FastEthernet0/0
description LAN
ip address 192.168.10.150 255.255.255.0
ip nat inside
ip virtual-reassembly
duplex auto
speed auto
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface ATM0/0/0
no ip address
no atm ilmi-keepalive
pvc 0/38
encapsulation aal5mux ppp dialer
dialer pool-member 1
!
!
interface Dialer0
description BT Internet
ip address negotiated
ip access-group 101 out
no ip unreachables
no ip proxy-arp
ip nat outside
ip virtual-reassembly
encapsulation ppp
dialer pool 1
dialer idle-timeout 0
dialer persistent
dialer-group 1
no cdp enable
ppp reliable-link
ppp authentication chap callin
ppp chap hostname [REMOVED]
ppp chap password 7 [REMOVED]
ppp pap sent-username [REMOVED] password 7 [REMOVED]
!
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 Dialer0
!
no ip http server
no ip http secure-server
!
ip nat inside source list 1 interface Dialer0 overload
!
access-list 1 permit 192.168.10.0 0.0.0.255
!
access-list 2 remark Management Access
access-list 2 permit 192.168.10.0 0.0.0.255
!
access-list 101 remark Blocked Traffic
access-list 101 deny ip any 64.4.23.0 0.0.0.255
access-list 101 deny ip any 65.55.223.0 0.0.0.255
access-list 101 deny ip any 111.221.74.0 0.0.0.255
access-list 101 deny ip any 111.221.77.0 0.0.0.255
access-list 101 deny ip any 157.55.56.0 0.0.0.255
access-list 101 deny ip any 157.55.130.0 0.0.0.255
access-list 101 deny ip any 157.55.235.0 0.0.0.255
access-list 101 deny ip any 157.56.52.0 0.0.0.255
access-list 101 deny ip any 213.199.179.0 0.0.0.255
access-list 101 deny ip any 108.160.160.0 0.0.15.255
access-list 101 deny ip any 108.160.161.0 0.0.0.255
access-list 101 deny ip any 108.160.162.0 0.0.0.255
access-list 101 deny ip any 108.160.163.0 0.0.0.255
access-list 101 deny ip any 108.160.164.0 0.0.0.255
access-list 101 deny ip any 108.160.165.0 0.0.0.255
access-list 101 deny ip any 108.160.166.0 0.0.0.255
access-list 101 deny ip any 199.47.216.0 0.0.0.255
access-list 101 deny ip any 199.47.217.0 0.0.0.255
access-list 101 deny ip any 199.47.218.0 0.0.0.255
access-list 101 deny ip any 199.47.219.0 0.0.0.255
access-list 101 permit ip any any
!
!
control-plane
!
banner motd ^CC
[REMOVED]
^C
!
line con 0
login local
line aux 0
login local
line vty 0 4
access-class 2 in
privilege level 15
login local
transport input ssh
!
scheduler allocate 20000 1000
end

r-godden · ‎09-03-2015

cant see a

dialer-list 1 protocol ip permit

void_main1024 · ‎09-03-2015

Hi r-godden,

Thanks for your reply.

I added in dialer-list 1 protocol ip permit to my configuration, but I can't see that it has made any difference.

I noticed that I can't ping the dialer0 ip address (DHCP from ISP) on the router itself, but I can from a workstation on my LAN, is that significant in any way? I thought it was strange.

Can anyone suggest the next thing I can try to troubleshoot this problem?

Kind regards

Peter Paluch · ‎09-03-2015

Hello,

Your current configuration uses the PPPoA type of connection. I assume that this is correct but I just want to point out that it is not the typical PPPoE that is often used on DSLs, and I would like to hear from you that you have intentionally used PPPoA here because that's what your ISP is running.

You can safely remove the following commands from your Dialer0, as they are not required for its proper operation:

dialer idle-timeout 0
dialer-group 1
ppp authentication chap callin

Using the dialer-list suggested by r-godden is also not required, as this Dialer is not in fact a dialed connection and there is no list of interesting traffic necessary to cause the Dialer to come up. After all, you have configured it with dialer persistent which is exactly about keeping a dialed connection up for all times (even though your DSL connection is not truly dialed).

Your Dialer0 is also configured with ppp reliable-link. I believe that this can be the cause of your problems. This command causes your router to attempt running a reliable Layer2 protocol on top of PPP - namely, the LAPB protocol. However, for the LAPB to work, your ISP would also need to support LAPB over PPP and expect you to run it. Unless your provides explicitly requires and expects you to do this then using this command inappropriately will result in your inability to communicate with ISP. So please double check whether your ISP explicitly requires you to use LAPB over PPP, and if not, remove the ppp reliable-link from your Dialer0 interface. I have in fact never seen this command being really used in real life networks.

Best regards,
Peter

void_main1024 · ‎09-08-2015

Hi Peter,

Firstly may I thank you for your reply to my post, I appreciate your input.

I must admit that I did not specifically decide to configure the connection for PPPoA over PPPoE, however I can confirm that PPPoA does work on the line - I've tested with PPPoA using a cheap router. I've researched and it would appear that here in the UK both PPPoE and PPPoA are supported on BT's 21CN network. Perhaps it would be worth trying PPPoE in case there is some chipset incompatibility?

I have changed my configuration as you suggested, here is the current configuration:

BT-D2#show run
Building configuration...

Current configuration : 3550 bytes
!
version 12.4
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
!
hostname BT-D2
!
boot-start-marker
boot system flash flash:c1841-ipbasek9-mz.124-24.T.bin
boot-end-marker
!
logging message-counter syslog
logging buffered 51200 warnings
enable secret 5 [REMOVED]
!
no aaa new-model
dot11 syslog
ip source-route
!
!
ip cef
ip domain name [REMOVED]
ip name-server 208.67.222.222
ip name-server 208.67.220.220
multilink bundle-name authenticated
!
!
username [REMOVED]
username [REMOVED]
archive
log config
hidekeys
!
!
ip ssh time-out 60
ip ssh authentication-retries 2
ip ssh version 2
!
!
interface FastEthernet0/0
description LAN
ip address 192.168.10.150 255.255.255.0
ip nat inside
ip virtual-reassembly
duplex auto
speed auto
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface ATM0/0/0
no ip address
no atm ilmi-keepalive
pvc 0/38
encapsulation aal5mux ppp dialer
dialer pool-member 1
!
!
interface Dialer0
description BT Internet
ip address negotiated
ip access-group 101 out
no ip unreachables
no ip proxy-arp
ip nat outside
ip virtual-reassembly
encapsulation ppp
dialer pool 1
dialer idle-timeout 0
dialer persistent
no cdp enable
ppp chap hostname [REMOVED]
ppp chap password 7 [REMOVED]
ppp pap sent-username [REMOVED] password 7 [REMOVED]
!
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 Dialer0
!
no ip http server
no ip http secure-server
!
ip nat inside source list 1 interface Dialer0 overload
!
access-list 1 permit 192.168.10.0 0.0.0.255
!
access-list 2 remark Management Access
access-list 2 permit 192.168.10.0 0.0.0.255
!
access-list 101 remark Blocked Traffic
access-list 101 deny ip any 64.4.23.0 0.0.0.255
access-list 101 deny ip any 65.55.223.0 0.0.0.255
access-list 101 deny ip any 111.221.74.0 0.0.0.255
access-list 101 deny ip any 111.221.77.0 0.0.0.255
access-list 101 deny ip any 157.55.56.0 0.0.0.255
access-list 101 deny ip any 157.55.130.0 0.0.0.255
access-list 101 deny ip any 157.55.235.0 0.0.0.255
access-list 101 deny ip any 157.56.52.0 0.0.0.255
access-list 101 deny ip any 213.199.179.0 0.0.0.255
access-list 101 deny ip any 108.160.160.0 0.0.15.255
access-list 101 deny ip any 108.160.161.0 0.0.0.255
access-list 101 deny ip any 108.160.162.0 0.0.0.255
access-list 101 deny ip any 108.160.163.0 0.0.0.255
access-list 101 deny ip any 108.160.164.0 0.0.0.255
access-list 101 deny ip any 108.160.165.0 0.0.0.255
access-list 101 deny ip any 108.160.166.0 0.0.0.255
access-list 101 deny ip any 199.47.216.0 0.0.0.255
access-list 101 deny ip any 199.47.217.0 0.0.0.255
access-list 101 deny ip any 199.47.218.0 0.0.0.255
access-list 101 deny ip any 199.47.219.0 0.0.0.255
access-list 101 permit ip any any
!
!
control-plane
!
banner motd ^CC
[REMOVED]
^C
!
line con 0
login local
line aux 0
login local
line vty 0 4
access-class 2 in
privilege level 15
login local
transport input ssh
!
scheduler allocate 20000 1000
end

I tried to remove dialer idle-timeout 0 as suggested but was unable to do so:

BT-D2(config)#interface dialer 0
BT-D2(config-if)#no dialer idle-timeout 0
%Remove dialer persistent command first

I'm afraid however that the configuration is not working, it seems to take an age for the router to obtain an IP address, and when it does it's not a usable connection. Very strange.

I would like to add that I normally use an 887VA-M on this line, and I have some other 2800 series routers spare here too, perhaps I should try the line card in another router.

Peter Paluch · ‎09-09-2015

Hello,

You can of course try to migrate this configuration to PPPoE if that works better. The commands would be:

interface ATM0/0/0
 pvc 0/38
  no dialer pool-member 1
  no encapsulation aal5mux ppp dialer
  pppoe-client dial-pool-number 1
  exit
 exit
interface Dialer0
 no dialer persistent
 no dialer idle-timeout 0
 mtu 1492
 ip tcp adjust-mss 1452
 exit
end

The configuration change is relatively simple - you remove the PPPoA configuration from the PVC along with the AAL5MUX encapsulation and simply start a PPPoE client on the PVC (it uses AAL5SNAP automatically by default). Then, on the Dialer0 interface, the MTU and TCP MSS are decreased to accomodate the added PPPoE overhead.

Would you mind testing this out before experimenting with another router?

Just curious, when using PPPoA, you had AAL5MUX configured. That is the logical choice but I have seen ISPs who are also using AAL5SNAP for this. It is possible that BT also uses AAL5SNAP for the PPPoA. If that is so then you wouldn't need to migrate to PPPoE but perhaps just change the encapsulation on the PVC 0/38 using encapsulation aal5snap command and shut/no shut the Dialer interface to see if it helps.

Best regards,
Peter

void_main1024 · ‎09-10-2015

Hi Peter,

Ok so my ISP definitely uses AAL5MUX, this is the encapsulation used on my working 887 using PPPoA.

I've read that both PPPoA and PPPoE are supported and I tried configuring as per the commands you very kindly listed. The result was the same - after a long-ish period of time the dialer0 interface negotiates an IP address but I'm not able to pass any traffic.

I thought perhaps looking at show dsl interface atm 0/0/0 and show controllers atm 0/0/0 might help to further diagnose what is happening with this situation:

BT-D2#show controllers atm 0/0/0
Interface: ATM0/0/0, Hardware: HWIC-DSLSAR (with Alcatel ADSL Module), State: up
IDB: 64673858 Instance: 6469E914 reg_dslsar:50520000 adsl_regs: 50560000
fpgaRegs:50408000 alcRegs: 50580000
PHY Inst:646D9D94 us_bwidth:1040
Slot: 0 Unit: 0 Subunit: 0 pkt Size: 4528
VCperVP: 256 max_vp: 256 max_vc: 65536 total vc: 1
rct_size:65536 vpivcibit:16 connTblVCI:8 vpi_bits: 8
vpvc_sel:3 enabled: 0 throttled: 0 cell drops: 55
Last Peridic Timer 00:40:52.868(2452868)
delayed_tbqe: 00000000 invalid_tbqe_index: 00000000

FPGA Register Value Notes
--------------- ---------- ----------
FPGA Rev 0x00050027

ADSL Register Value Notes
--------------- ---------- ----------
intr_enable_reg: 0xC3C VCCLOSED.JUMPC.FBQE.RQAF.RPQAF.TBQAF.
ADSL Config Reg 0x000D8C80 CD LED on;
LT-TE Mode = TE;
NTR Pass Thru = 0;
NTR Enable = 1;
OK LED on;
LOOPBACK LED off;
Gen ADSL over POTS error int on bad ADSL over POTS access

ADSL Int Enable 0x00000003 ADSL over POTS normal interrupt enabled
ADSL over POTS error interrupt enabled

DSLSAR Register Value Notes
--------------- ---------- ----------
config: 0x600D0A20 RXEN.RegulateXmit.RMCell.TXEN.
Rx Buffer size: 1024. RCT: Large, VPI Bits: 8.
status: 0x00000000
rpq_base: 0x07766000
rpq_head: 0x07766350 (53 entries from base)
rpq_tail: 0x07766350 (0 entries from head)
clkPerCell: 2609361 (line rate: 1040 Kbps)
Tx Error: 0x00000000
Lookup Error cnt: 0x00000002 Cell Rx-ed with no Open RCTEntry.
Invalid Cell cnt: 0x00000000
Tx packet: 0x00000078
Tx OAM: 0x00000000
Rx packet: 0x0000000C
Rx packet drop: 0x00000000
Rx OAM: 0x00000000
Rx OAM drop: 0x00000002
Timer: 0x00000000
tstBase1: 0x0001B718 TST boot jump.
Pre-timer Count: 333
rcid_tableBase: 0x00000000
rct_base: 0x00011000
fbq_base: 0x0001F800
fbq_head: 0x0001F8D4 (53 entries from base)
fbq_tail: 0x0001F8F8 (9 entries from head)
rawCellBase: 0x07764000
rcq_head: 0x07764180 (6 entries from base)
rcq_tail: 0x07764180 (0 entries from head)
Last Addr: 0x00000000
tbq_base: 0x07767000
tbq_head: 0x077672B0 (86 entries from base)
tbq_tail: 0x077672B0 (0 entries from head)
DSLSAR Spurious Interrupts:0x0
DSLSAR Interrupts: 0x8F
VC Closed: 0x2E
JMP-COMPLETE:0x5D
FIFOF: 0x3
FBQE: 0x1
Last Addr:0x0

Host Memory Qs Value Notes
--------------- ---------- ----------
rxCellQ: 0x07764000
rxPacketQ: 0x07766000
txBufQ: 0x07767000

txPakInfo Array
Index vcd pak Ptr particle Ptr
----- --- ------- ------------

rx_particleArray:
Index ParticlePointer
----- ---------------
53. 0x646C81C0
54. 0x646C8400
55. 0x646C83C0
56. 0x646C8100
57. 0x646C8380
58. 0x646C8340
59. 0x646C8F00
60. 0x646C8500
61. 0x646C8440

VC QoS Summary
--------------
Active Configured Scheduled
Connections
VCD VPI/VCI COS PCR SCR/MCR COS PCR SCR/MCR
--- --------- -------- ------ ------- -------- ------- --------
1 0 /38 UBR 0 n/a UBR 1040 n/a

Connections RX RX RX RX RX TX TX TX TX TX TX
VCD VPI/ VCI AAL5 AAL2 RAW Chain Drop AAL5 AAL2 RAW TSI Drop MISS
--- --- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- -----
0 0 /0 0 0 0 0 0 0 0 0 0 0 0
1 0 /38 104 0 0 0 0 699 0 0 0 3 0

Receive Connection Table:
VC AAL
VCD VPI/ VCI controlStatus open type
---- -------- ------------- ---- ----
1 0 / 38 68A0000 Yes AAL5

Tx Queues: |<-- TCD Contents -->|<---- tcqTail TBD Contents --->|
VCD(VPI/VCI) Queue tcqTailbase Tail Head control bufAddr aal5Ctrl cellHdr
------------ ----- ----------- ---- ---- -------- -------- -------- --------
0 (0 /0 ) LOW 20000 0 0 344844F1 509DD1D1 7CC4067 66285101
HIGH 38000 0 0 D5B1290C 11147075 728459CD 98112526
1 (0 /38 ) LOW 21000 0 0 44430DC8 19FD2EA0 CD9B4684 530577B3
HIGH 39010 1 1 8010046 7303678 46 262

OAM pak statistics [vcd/tx/dropped]:
1/0/0
OAM enqueue failures : 0
OAM Bad VCD drops : 0
OAM cells handled inline: 0
OAM Max Tx time Statistics:
1 : < 4 msec
OAM used samples : 0
OAM ignored samples : 0

Queue Statistics

TxQInfo for vcd 0
--------------------
tx_ring_limit=10, max_tsi_seq_num=0, max_tx_time=214560
Total number of packets = 0
Total number of packets transmitted = 0
Total number of packets dropped = 0
HP TxQInfo for vcd 0
--------------------
tx_ring_limit=30, max_tsi_seq_num=0, max_tx_time=214560
Total number of packets = 0
Total number of packets transmitted = 0
Total number of packets dropped = 0
TxQInfo for vcd 1
--------------------
tx_ring_limit=10, max_tsi_seq_num=0, max_tx_time=2083
Total number of packets = 0
Total number of packets transmitted = 0
Total number of packets dropped = 0
HP TxQInfo for vcd 1
--------------------
tx_ring_limit=30, max_tsi_seq_num=0, max_tx_time=2083
Total number of packets = 601
Total number of packets transmitted = 601
Total number of packets dropped = 0

BT-D2#
BT-D2#show dsl interface atm 0/0/0
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 0x3
Chip Vendor ID: 'STMI' 'TSTC'
Chip Vendor Specific: 0x0000 0x0510
Chip Vendor Country: 0x0F 0xB5
Modem Vendor ID: 'CSCO' 'TSTC'
Modem Vendor Specific: 0x0000 0x5100
Modem Vendor Country: 0xB5 0xB5
Serial Number Near: FOC1431078NCISCO73993206
Serial Number Far: Chip ID: C196P (1)
DFE BOM: DFE3.0 Annex A (1)
Capacity Used: 100% 100%
Noise Margin: 3.0 dB 5.0 dB
Output Power: 20.0 dBm 12.5 dBm
Attenuation: 19.0 dB 9.0 dB
FEC ES Errors: 0 0
ES Errors: 61 295517
SES Errors: 60 772
LOSES Errors: 8 1762
UES Errors: 21 1274
Defect Status: None None
Last Fail Code: None
Watchdog Counter: 0xDA
Watchdog Resets: 0
Selftest Result: 0x00
Subfunction: 0x00
Interrupts: 16778 (0 spurious)
PHY Access Err: 0
Activations: 24
LED Status: OFF
LED On Time: 0
LED Off Time: 0
Init FW: init_AMR-3.0.014_no_bist.bin
Operation FW: AMR-3.0.014.bin
FW Source: embedded
FW Version: 3.0.14

DS Channel1 DS Channel0 US Channel1 US Channel0
Speed (kbps): 0 16897 0 1040
Cells: 0 122 0 1062819
Reed-Solomon EC: 0 0 0 0
CRC Errors: 0 0 0 338042
Header Errors: 0 0 0 245824
Total BER: 0E-0 0E-0
Leakage Average BER: 0E-0 0E-0
Interleave Delay: 0 32 0 1
ATU-R (DS) ATU-C (US)
Bitswap: enabled enabled
Bitswap success: 0 0
Bitswap failure: 0 0

LOM Monitoring : Disabled

DMT Bits Per Bin
000: 0 0 0 0 0 0 4 6 7 8 9 B C B D C
010: D D D D D D D D D D C C B B A 0
020: 0 0 2 2 4 4 4 5 6 7 8 8 9 9 A A
030: B B B B B C C C C C C C C C C C
040: C C D C C C C C C C C C C C C C
050: 2 C C C C C C C C C C C C C C C
060: C C C C C C C C C C C C C C C C
070: C C C C C C C C C C C C C C C C
080: C C C C C C C C C C C C C C C C
090: C B B B C C B B B B C B B B B B
0A0: B B B B B B B B B B B B B B B B
0B0: B B B B B B B B B B B B B B B B
0C0: B B B B B B B B B B B B B B B B
0D0: B B B B B B B B B A B B B B B B
0E0: A A B B B B B B A B A B A A A A
0F0: A A A B A A A A A A A A A A A A
100: A B A A A A A A A A A A A A A A
110: A A A A A A A A A A 9 A 9 9 A A
120: A A A A A 9 9 9 9 9 9 9 9 9 9 9
130: 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9
140: 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9
150: 8 9 9 9 9 9 9 9 9 9 9 9 9 8 9 8
160: 9 9 9 8 9 9 8 9 9 8 9 8 8 8 8 9
170: 9 9 8 8 8 8 8 8 8 8 8 8 8 8 8 8
180: 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8
190: 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8
1A0: 8 8 8 8 7 8 8 8 8 8 8 8 8 8 8 8
1B0: 8 8 8 8 7 8 8 7 7 7 7 8 7 7 7 7
1C0: 7 7 7 7 7 7 7 7 7 7 7 7 6 5 3 2
1D0: 3 0 5 7 7 7 7 7 8 7 7 7 7 7 7 7
1E0: 7 7 7 7 7 7 7 7 7 6 6 6 5 5 5 5
1F0: 5 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4

DSL: Training log buffer capability is not enabled
BT-D2#

What immediately caught my eye is this:
ES Errors: 61 295517

I presume that this number is far higher than one would normally expect, and further more under CRC and header errors there is a significant value in the upstream channel?

CRC Errors: 0 0 0 338042
Header Errors: 0 0 0 245824

Best regards
Stuart

Peter Paluch · ‎09-11-2015

Hi Stuart,

The Noise Margin values seem to me to be in red numbers. 3 dB of noise margin is too low - it is recommended that this value is 10 dB or more. Either the line is of poor quality, or this particular DSL modem you are using does not sit well with this particular line. Can you test a different modem and see if the reported values are better?

There is a theoretical option of downloading a replacement firmware for the DSL modem card you are using, and storing it into FLASH. Upgraded firmwares may have better characteristics on select lines, so trying out a different DSL modem firmware may help. This operation is reversible - the firmware is always loaded from the FLASH, and if the file is removed, the router will revert back to using the embedded firmware version.

Please visit the page

http://www.alcatron.net/cisco877/firmware/

Consider testing the following firmware files in the following order:

adsl_alc_20190_6.0.010.bin (store in FLASH as adsl_alc_20190.bin)

adsl_alc_firmware.4-10-9.bin (store in FLASH as adsl_alc_firmware.bin, if it gets not loaded, rename to adsl_alc_20190.bin)

adsl_alc_20190.4.0.15.bin (store in FLASH as adsl_alc_20190.bin)

adsl_alc_20190_4.0.223.bin (store in FLASH as adsl_alc_20190.bin)

adsl_alc_20190_4.0.018.bin (store in FLASH as adsl_alc_20190.bin)

To test each of these firmwares, store it into the FLASH of your 1841 router under the indicated name, then reload the router and check the output of the show dsl interface atm0/0/0 whether the firmware was loaded, then check the trained modem parameters and perhaps the connectivity. Only one firmware can be present in the FLASH at a time.

Best regards,
Peter

void_main1024 · ‎09-18-2015

Hi Peter,

Thank you for your reply, I just wanted to write in and say that I'm working though your suggestions and will post back a proper response shortly.

I didn't want to leave it too long before replying hence this message.

Best regards

Stuart

void_main1024 · ‎10-06-2015

Hi Peter,

I do apologise for the delay in my reply.

It would seem to me that the line is of poor quality, here is the result of my working 887 on the same line:

R1#show controllers vdsl 0
Controller VDSL 0 is UP

Daemon Status: Up

XTU-R (DS) XTU-C (US)
Chip Vendor ID: 'BDCM' 'TSTC'
Chip Vendor Specific: 0x0000 0x0510
Chip Vendor Country: 0xB500 0xB500
Modem Vendor ID: 'CSCO' ' '
Modem Vendor Specific: 0x4602 0x0000
Modem Vendor Country: 0xB500 0x0000
Serial Number Near: FCZ1814C2PG 887VA-M- 15.3(3)M
Serial Number Far: 00000000000000000000000000000000
Modem Version Near: 15.3(3)M
Modem Version Far: 0x0510

Modem Status: TC Sync (Showtime!)
DSL Config Mode: AUTO
Trained Mode: G.992.5 (ADSL2+) Annex A
TC Mode: ATM
Selftest Result: 0x00
DELT configuration: disabled
DELT state: not running
Trellis: ON ON
SRA: disabled disabled
SRA count: 0 0
Bit swap: enabled enabled
Bit swap count: 3 9
Line Attenuation: 18.5 dB 9.0 dB
Signal Attenuation: 19.4 dB 0.0 dB
Noise Margin: 3.2 dB 5.7 dB
Attainable Rate: 18716 kbits/s 1352 kbits/s
Actual Power: 20.9 dBm 12.2 dBm
Total FECC: 0 0
Total ES: 0 0
Total SES: 0 0
Total LOSS: 0 0
Total UAS: 32 32
Total LPRS: 0 0
Total LOFS: 0 0
Total LOLS: 0 0

Full inits: 1
Failed full inits: 0
Short inits: 0
Failed short inits: 0

Firmware Source File Name (version)
-------- ------ -------------------
VDSL embedded VDSL_LINUX_DEV_01212008 (1)

Modem FW Version: 130205_1433-4.02L.03.A2pv6C035j.d23j
Modem PHY Version: A2pv6C035j.d23j
Vendor Version: Ap6v35j.23j 68

DS Channel1 DS Channel0 US Channel1 US Channel0
Speed (kbps): 0 17463 0 1128
SRA Previous Speed: 0 0 0 0
Previous Speed: 0 0 0 0
Total Cells: 0 1229027 0 69204
User Cells: 0 43 0 48
Reed-Solomon EC: 0 0 0 0
CRC Errors: 0 0 0 0
Header Errors: 0 0 0 0
Interleave (ms): 0.00 0.09 0.00 1.00
Actual INP: 0.00 0.00 0.00 0.00

Training Log : Stopped
Training Log Filename : flash:vdsllog.bin

Never the less, this router does hold the line reliably so I proceeded to download the modem firmware, starting with the first you suggested:

BT-D2#show dsl interface atM 0/0/0
ATM0/0/0
Alcatel 20190 chipset information

Line has not yet been activated.

Modem Status: Down (DMTDSL_DO_OPEN)
DSL Mode: Unknown
Interrupts: 4157 (0 spurious)
PHY Access Err: 0
Activations: 0
LED Status: OFF
LED On Time: 0
LED Off Time: 0
Init FW: init_AMR_6.0.010.bin
Operation FW: AMR-E-6.0.010.bin
FW Source: external

DSL: Training log buffer capability is not enabled
BT-D2#

It did seem to load the firmware, but it did not seem to bring the line up. I assume this is normal behavior when the modem does not support that firmware version, so I will proceed to test the other firmware files you listed, in the order listed and make a further post.

Kind regards

Stuart

void_main1024 · ‎10-12-2015

Hi Peter,

I've now tried all the firmware versions and the best result I got was with the 4.0.223 firmware:

BT-D2#sh ip int br
Interface IP-Address OK? Method Status Protocol
FastEthernet0/0 192.168.10.150 YES NVRAM up up
FastEthernet0/1 unassigned YES NVRAM administratively down down
ATM0/0/0 unassigned YES NVRAM up up
NVI0 192.168.10.150 YES unset up up
Virtual-Access1 unassigned YES unset up up
Dialer0 ~~xxx.xx.xxx.xx~~ YES IPCP up up

BT-D2#show dsl interface atm 0/0/0
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 0x3
Chip Vendor ID: 'STMI' 'TSTC'
Chip Vendor Specific: 0x0000 0x0510
Chip Vendor Country: 0x0F 0xB5
Modem Vendor ID: 'CSCO' 'TSTC'
Modem Vendor Specific: 0x0000 0x5100
Modem Vendor Country: 0xB5 0xB5
Serial Number Near: FOC1431078NCISCO73993206
Serial Number Far: Chip ID: C196 (3)
DFE BOM: DFE3.0 Annex A (1)
Capacity Used: 96% 81%
Noise Margin: 4.0 dB 5.0 dB
Output Power: 20.5 dBm 12.5 dBm
Attenuation: 20.0 dB 9.0 dB
FEC ES Errors: 0 1540
ES Errors: 0 348842
SES Errors: 0 1071
LOSES Errors: 0 2272
UES Errors: 0 1534
Defect Status: None None
Last Fail Code: None
Watchdog Counter: 0x10
Watchdog Resets: 0
Selftest Result: 0x00
Subfunction: 0x00
Interrupts: 4174 (0 spurious)
PHY Access Err: 0
Activations: 1
LED Status: OFF
LED On Time: 0
LED Off Time: 0
Init FW: init_AMR_4.0.223.bin
Operation FW: AMR-E-4.0.223.bin
FW Source: external
FW Version: 4.0.223

DS Channel1 DS Channel0 US Channel1 US Channel0
Speed (kbps): 0 16305 0 1008
Cells: 0 86 0 592684
Reed-Solomon EC: 0 0 0 2078
CRC Errors: 0 0 0 405790
Header Errors: 0 0 0 291611
Total BER: 0E-0 0E-0
Leakage Average BER: 0E-0 0E-0
Interleave Delay: 0 38 0 5
ATU-R (DS) ATU-C (US)
Bitswap: enabled enabled
Bitswap success: 0 0
Bitswap failure: 0 0

LOM Monitoring : Disabled

DMT Bits Per Bin
000: 0 0 0 0 0 0 4 6 7 9 9 9 B B C C
010: D D D D D D D D D D C C B B A 0
020: 0 2 4 4 6 7 7 8 9 A A A B B C C
030: C C D D D D D D D D D D D D D D
040: D D D D D D D D D D D D D D D D
050: D D D D D D D D D D D D D D D D
060: 2 D D D D D D C D C C D D D D D
070: D D C D D D D D D D C C D C C C
080: C C C C C C C C C C C C C C C C
090: C C C C C C C C C C C C C C C C
0A0: C C C C C C C C C C C C C C C C
0B0: C C B C C C C C B B C C B C B C
0C0: B C C B B B C C B B B B B B B B
0D0: B B B B B B B B B B B B B B B B
0E0: B B B B B B B B B B B B B B B B
0F0: B B B B B B B B B B B B B B B B
100: B B B B B A B A B B B A B A B B
110: A A A B A A A A A A A A A A A A
120: A A A A A A A A A A A A A A A A
130: A A A A 9 A A A A A A A A A A 9
140: 9 A A 9 A A A A 9 9 A 9 9 9 9 9
150: 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9
160: 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9
170: 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9 9
180: 9 9 9 9 9 9 9 9 9 9 8 9 9 8 9 9
190: 9 9 8 9 9 9 9 8 8 9 9 8 9 8 9 8
1A0: 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8
1B0: 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8
1C0: 8 8 8 8 8 8 8 8 8 8 7 0 0 0 0 0
1D0: 0 0 0 0 0 7 8 8 8 8 8 8 8 8 8 8
1E0: 8 8 7 7 7 7 7 7 7 7 7 7 6 6 6 6
1F0: 5 5 5 5 5 5 4 4 5 5 5 5 5 5 5 5

DSL: Training log buffer capability is not enabled

Public IP address removed.

So it seems the line is up and has managed to obtain an IP address from the service provider. The noise margin of 4.0 dB should work and the sync rate is OK.

Interestingly I read that in the UK the exchange equipment will automatically reduce the signal it sends (thus reducing the noise margin) so it can use more tones in the spectrum and thus sync at a higher rate for higher throughput. Some engineers claim that the target noise margin is 3.0 dB, but can drop to below 1.0dB in some circumstances. Apparently the noise on lines increases at night but not normally beyond a 3db margin hence the target.

Anyway, even though the router is syncing the line and getting an IP address, I'm still not able to use the router for anything productive - I cannot use it as a gateway, nor can I ping an address from the router itself.. there is still something wrong.

Peter Paluch · ‎10-13-2015

Hi Stuart,

I am surprised at the finding that even though you are assigned an IP address on the router, you cannot ping any IP address from the router itself. That is very strange indeed.

Can you actually ping your own IP address that you were assigned on the Dialer0 interface? This ping is performed through your ISP, as on all point-to-point interfaces including Dialer0, packets originated by router and destined to the router itself are sent to the other end, and the other end is supposed to send the packet back. It is a kind of a loopback test. If you can ping your own Dialer0 IP address, then the basic IP connectivity between you and your ISP is working. If not, there's a reason for concern. In addition, I'd be interested in knowing if you can ping public IP addresses such as 8.8.8.8, 4.2.2.2, 87.197.31.42, or 158.193.152.2 from the router.

If some of these pings work and some don't, it would also be interesting to find out where do the pings go dead - in that case, I suggest configuring no ip domain lookup in your configuration first, and running a plain traceroute toward the unresponsive IP address.

In any case, the configuration of your router - if it is identical to the one you have posted - is very basic, and I see no reason why the router should be unable to communicate with external IP addresses. Do you have another router, perhaps from even a different vendor, to test on the same DSL circuit to see if the problem goes away? I am getting the feeling that this issue will need to be discussed with your ISP, as the problem could potentially be on their side.

Best regards,
Peter