how-to block ads
|
netboy
@epix.net
|  [HELP] Cisco 1721 and WIC-1ADSL Slow, 320Kbit
Hi. I have a 1721 Cisco router with a WIC-1ADSL card. I have connected to my ISP ADSL service but only get at most about 384K of download speed (speedtest.net). The sh interface for the ATM0 int shows the following:
ATM0 is up, line protocol is up
Hardware is DSLSAR (with Alcatel ADSL Module)
MTU 4470 bytes, sub MTU 4470, BW 320 Kbit, DLY 6400 usec,
reliability 255/255, txload 1/255, rxload 15/255
Encapsulation ATM, loopback not set
Seems like I am only able to get max of 320Kbit?
How can I increase the bandwidth? Is the WIC-1ADSL limited to 320K? My old setup using a Speedtream 5200 through a Cisco 2610 ethernet interface yields near T1 speeds. I got the new router and thought the new WIC card would give me better performance.
Thanks in advance,
Netboy | |
Phraxos
Premium
join:2004-06-12
UK
| No, the WIC-1ADSL is certainly not limited to 320K, something is wrong if you were getting much better speeds before! I presume from what you are saying that all you have changed is the router and the adsl interface? The provider, line and filter are unchanged from your previous solution?
Please post a "sh dsl int atm0"
Also, does the serial number of your interface start with FOC07 ? | |
dervari
join:2000-01-17
Atlanta, GA
clubs:
 ·Comcast
| reply to netboy
Not sure about a DSL WIC, but on a T1 WIC the bandwidth is set in the interface config manually and really had no bearing on the connection speed.
This may not work on a DSL WIC, but try doing a "show service-module" command and see if it gives you any more data. | |
netboy
@epix.net
| reply to Phraxos
Phraxos,
You are correct in that all I have changed is the router and adsl interface. The provider, line and filter are exactly the same.
Here is the sh dsl int atm0:
##########################
Alcatel 20150 chipset information
ATU-R (DS) ATU-C (US)
Modem Status: Showtime (DMTDSL_SHOWTIME)
DSL Mode: ITU G.992.1 (G.DMT)
ITU STD NUM: 0x01 0x1
Vendor ID: 'ALCB' 'BDCM'
Vendor Specific: 0x0000 0x610C
Vendor Country: 0x00 0xB5
Capacity Used: 99% 83%
Noise Margin: 2.5 dB 7.0 dB
Output Power: 16.0 dBm 12.0 dBm
Attenuation: 56.5 dB 31.5 dB
Defect Status: None None
Last Fail Code: None
Selftest Result: 0x00
Subfunction: 0x15
Interrupts: 14615 (0 spurious)
PHY Access Err: 0
Activations: 8
Init FW: embedded
Operation FW: embedded
SW Version: 3.8131
FW Version: 0x1A04
Interleave Fast Interleave Fast
Speed (kbps): 0 448 0 320
Reed-Solomon EC: 0 0 0 0
CRC Errors: 0 3 0 0
Header Errors: 0 1 0 0
Bit Errors: 0 0
BER Valid sec: 0 0
BER Invalid sec: 0 0
DMT Bits Per Bin
00: 0 0 0 0 0 0 0 2 3 4 5 5 6 5 6 5
10: 5 5 5 5 5 5 5 5 4 4 4 4 4 3 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 2 2 2 2 2 2
40: 2 2 2 3 2 2 3 2 3 2 3 3 3 3 4 4
50: 4 4 4 4 4 5 5 5 5 4 5 4 4 4 4 4
60: 4 3 2 2 2 2 2 2 2 2 2 0 0 0 0 0
70: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
80: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
90: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
A0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
B0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
C0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
D0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
E0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
F0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
DSL: Training log buffer capability is not enabled
##############################
The WIC serial number is a FOCO1xxxxxxx
Here is also something of interest with the debug atm events log entires. Note toward end where it states it it setting line from fast to slow, and seems to force Peakrate and Avgrate to 320 (the speed shown in the sh int atm0):
Dec 24 01:45:58.765: DSL(ATM0): Received response: 0x80
Dec 24 01:45:59.201: DSL(ATM0): Downloading ASW_R3_8_131.bin
Dec 24 01:45:59.666: DSL:(ATM0) Downloaded 100 blocks
Dec 24 01:45:59.898: DSL:(ATM0) Downloaded 200 blocks
Dec 24 01:46:00.131: DSL:(ATM0) Downloaded 300 blocks
Dec 24 01:46:00.363: DSL:(ATM0) Downloaded 400 blocks
Dec 24 01:46:00.591: DSL:(ATM0) Downloaded 500 blocks
Dec 24 01:46:00.820: DSL:(ATM0) Downloaded 600 blocks
Dec 24 01:46:01.052: DSL:(ATM0) Downloaded 700 blocks
Dec 24 01:46:01.280: DSL:(ATM0) Downloaded 800 blocks
Dec 24 01:46:01.508: DSL:(ATM0) Downloaded 900 blocks
Dec 24 01:46:01.737: DSL:(ATM0) Downloaded 1000 blocks
Dec 24 01:46:01.965: DSL:(ATM0) Downloaded 1100 blocks
Dec 24 01:46:02.197: DSL:(ATM0) Downloaded 1200 blocks
Dec 24 01:46:02.425: DSL:(ATM0) Downloaded 1300 blocks
Dec 24 01:46:02.462: DSL:(ATM0) Downloaded 1317 blocks... Finished!
Dec 24 01:46:02.462: DSL(ATM0): Sent command 0x14
Dec 24 01:46:04.472: DSL(ATM0):changed current state to do open!!
Dec 24 01:46:04.472: DSL(ATM0): Send ADSL_OPEN command.
Dec 24 01:46:04.472: DSL(ATM0): Using subfunction 0x15
Dec 24 01:46:04.472: DSL(ATM0): Sent command 0x3
Dec 24 01:46:06.975: DSL(ATM0): 1: Modem state = 0x8
Dec 24 01:46:09.502: DSL(ATM0): 2: Modem state = 0x10
Dec 24 01:46:12.005: DSL(ATM0): 3: Modem state = 0x10
Dec 24 01:46:14.508: DSL(ATM0): 4: Modem state = 0x10
Dec 24 01:46:16.606: DSL(ATM0): Received response: 0x24
Dec 24 01:46:16.606: DSL(ATM0): Showtime!
Dec 24 01:46:16.610: DSL(ATM0): Sent command 0x11
Dec 24 01:46:16.614: DSL(ATM0): Received response: 0x61
Dec 24 01:46:16.614: DSL(ATM0): Read firmware revision 0x1A04
Dec 24 01:46:16.614: DSL(ATM0): Sent command 0x31
Dec 24 01:46:16.618: DSL(ATM0): Received response: 0x12
Dec 24 01:46:16.618: DSL(ATM0): operation mode 0x0002
Dec 24 01:46:16.618: DSL(ATM0): Sent command 0x33
Dec 24 01:46:16.622: DSL(ATM0): Received response: 0x16
Dec 24 01:46:16.622: DSL(ATM0): Far End ITU Country Code 0xB5
Dec 24 01:46:16.622: DSL(ATM0): Far End ITU Vendor ID BDCM
Dec 24 01:46:16.622: DSL(ATM0): Far End ITU Vendor ID Specific 0x610C
Dec 24 01:46:16.622: DSL(ATM0): Far End ITU Vendor STD Number 0x0001
Dec 24 01:46:16.626: DSL(ATM0): Sent command 0x32
Dec 24 01:46:16.630: DSL(ATM0): Received response: 0x14
Dec 24 01:46:16.630: DSL(ATM0): Near End ITU Country Code 0x00
Dec 24 01:46:16.630: DSL(ATM0): Near End ITU Vendor ID ALCB
Dec 24 01:46:16.634: DSL(ATM0): Near End ITU Vendor ID Specific 0x0000
Dec 24 01:46:16.634: DSL(ATM0): Near End ITU Vendor STD Number 0x0001
Dec 24 01:46:16.634: ATM0 dslsar_MatchSARTxToLineSpeed(): usbw 320, clkPerCell 46812 prev_clkPerCell 9702
Dec 24 01:46:16.634: ATM0 dslsar_MatchSARTxToLineSpeed(): Changing line speed from fast to slow
Dec 24 01:46:16.746: ATM0 dslsar_update_us_bandwidth(): upstream bw =320 Kbps
Dec 24 01:46:26.594: (ATM0) dslsar_periodic: ENABLING DSLSAR
Dec 24 01:46:26.602: dslsar enable ATM0
Dec 24 01:46:26.602: dslsar_1a_setup_vc(ATM0): vc:2 vpi:8 vci:35 state 2
Dec 24 01:46:26.602: ATM0 dslsar_vc_setup: vcd 2, vpi 8, vci 35, avgrate 0
Dec 24 01:46:26.602: CONFIGURING(ATM0) VC 2 (8/35) IN TX SCHEDULE TABLE SET 0
Dec 24 01:46:26.602: (ATM0)Forcing Peakrate and Avgrate to: 320
Dec 24 01:46:26.602: (ATM0)Requested QoS: Peakrate = 320, Avgrate = 320, Burstsize =0
Dec 24 01:46:26.602: (ATM0)Configuring VC 2: slot 0 in TST 5
Dec 24 01:46:26.602: (ATM0) SUCCESSFUL CONFIGURATION OF VC 2 (8/35), QOS Type 4
Dec 24 01:46:26.602: dslsar_setup_cos(ATM0): vc:2 wred_name:- max_q:40
Dec 24 01:46:26.606: CONFIGURING(ATM0) VC 2 (8/35) IN TX SCHEDULE TABLE SET 0
Dec 24 01:46:26.606: (ATM0)Forcing Peakrate and Avgrate to: 320
Dec 24 01:46:26.606: (ATM0)Requested QoS: Peakrate = 320, Avgrate = 320, Burstsize =0
Dec 24 01:46:26.606: (ATM0)Configuring VC 2: slot 0 in TST 5
Dec 24 01:46:26.606: (ATM0) SUCCESSFUL CONFIGURATION OF VC 2 (8/35), QOS Type 4
Dec 24 01:46:28.508: %LINK-3-UPDOWN: Interface ATM0, changed state to up
Dec 24 01:46:28.508: dslsar_atm_lineaction(ATM0): state=4
Dec 24 01:46:28.508: dslsar_atm_lineaction: REG_INVOKE: line up
Dec 24 01:46:29.509: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up | |
Phraxos
Premium
join:2004-06-12
UK
| reply to netboy
"Capacity Used: 99% 83%
Noise Margin: 2.5 dB 7.0 dB"
There is your problem.
You want the noise margin to be as large as possible and certainly no lower than 5-6 dB. Your speed is being limited by the quality of the connection.
As the line hasn't changed I suspect you have a faulty ADSL WIC. I presume you have picked this up second hand? The part serial number you gave can't be right - the first two digits reference the year the card was manufactured, 11 is 2007 so FOC01 would be 1997 and I'm pretty sure that they didn't make ADSL WICs then. Can you check it again? The reason I ask is that Cisco manufactured a large quantity of faulty WICs that had a serial number starting FOC07 (but not all FOC07 WICs are faulty, there is more info to differentiate them). | |
Phraxos
Premium
join:2004-06-12
UK
edit:
December 23rd, @09:31PM
| ....also if you have a spare filter there would be no harm in changing it and seeing if that makes any difference to the noise margin.
[Edit] and one last thought - don't rule out an ADSL/phone line fault. Just because this may have occurred at the same time you changed your equipment doesn't mean that it isn't just a coincidence of timing! Have you tried reconnecting your old setup just to check that the ADSL connection is still good? | |
TomS_
debugger it
Premium,MVM
join:2002-07-19
Australia
| reply to netboy
I would try the following (this is what I generally suggest to customers of the ISP I work for):
* Fully isolate the line - remove all devices bar the ADSL modem, see if the line stats change.
* Try a different wall socket - perhaps, even though coincidental, your current socket has issues.
* Definitely try a different cable - extension cables are hopeless for ADSL. Keep any cables from the wall to the modem as short as possible. If you are using a short cable, try replacing it.
* Try a different filter - if you are using a splitter or central filter, try a different one, it may be faulty.
As Phraxos suggested, low SNR is not good. The lower the SNR, the louder noise is on your line in comparison to the ADSL signal, so higher SNR is always better. Low SNR doesnt always mean low speed, more often than not it causes reliability issues, but depending on just how bad the noise is, it can eat away at subcarriers, which will lower your overall speed (and I say that based on 4 years of level 2 helpdesk experience at various ISPs).
Modem firmwares also make a BIG difference, so it is quite possible that the firmware being used to drive your WIC-1ADSL may not be as optimised as a more recent driver. Drivers are embedded within IOS images, so if you can, try and obtain a more recent firmware.
If all of the above fail, test your previous setup and see what sort of speed you can get. If you can get full speed, it could potentially be a faulty WIC. See if you can get it replaced from the people you bought it from. If you still get poor speeds, see my previous paragraph regarding firmwares.
Failing all of the above, its likely a line issue, so contact your ISP to log a fault. | |
netboy
@epix.net
| reply to netboy
Thanks a lot to all who replied to my post! After struggling all day with this thing, I think we got it!
I changed the filter and also took out the extra cable and the ups line filter (an APC Backups 1000 with a tel line filter where the DSL line was plugged into, then an output to the WIC-1ADSL). Each one seemed to have a small effect on the line quality as I tested each separately after replacing one at a time. This seems to have corrected the issue. Noise is up to 30 and 23 dB now. I still only see 384Kbps at the interface but my speedtest is up above 1300Kbps now!
Should I be seeing a better number in Kbps on the interfaces?
Here is the output with the corrections:
sh int:
ATM0 is up, line protocol is up
Hardware is DSLSAR (with Alcatel ADSL Module)
MTU 4470 bytes, sub MTU 4470, BW 384 Kbit, DLY 5330 usec,
reliability 237/255, txload 2/255, rxload 214/255
Encapsulation ATM, loopback not set
Encapsulation(s): AAL5 AAL2, PVC mode
23 maximum active VCs, 256 VCs per VP, 1 current VCCs
VC Auto Creation Disabled.
VC idle disconnect time: 300 seconds
Last input 00:10:30, output 00:00:04, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: Per VC Queueing
5 minute input rate 323000 bits/sec, 27 packets/sec
5 minute output rate 4000 bits/sec, 16 packets/sec
19248 packets input, 28310110 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
13621 packets output, 1031557 bytes, 0 underruns
0 output errors, 0 collisions, 2 interface resets
0 output buffer failures, 0 output buffers swapped out
ATM0.35 is administratively down, line protocol is down
Hardware is DSLSAR (with Alcatel ADSL Module)
MTU 4470 bytes, BW 384 Kbit, DLY 5330 usec,
reliability 237/255, txload 2/255, rxload 214/255
Encapsulation ATM
0 packets input, 0 bytes
0 packets output, 0 bytes
0 OAM cells input, 0 OAM cells output
AAL5 CRC errors : 0
AAL5 SAR Timeouts : 0
AAL5 Oversized SDUs : 0
Last clearing of "show interface" counters never
ATM0.835 is up, line protocol is up
Hardware is DSLSAR (with Alcatel ADSL Module)
MTU 4470 bytes, BW 384 Kbit, DLY 5330 usec,
reliability 237/255, txload 2/255, rxload 214/255
Encapsulation ATM
19248 packets input, 28311907 bytes
13621 packets output, 1031557 bytes
0 OAM cells input, 0 OAM cells output
AAL5 CRC errors : 0
AAL5 SAR Timeouts : 0
AAL5 Oversized SDUs : 0
Last clearing of "show interface" counters never
##############################
sh dsl int atm0:
Alcatel 20150 chipset information
ATU-R (DS) ATU-C (US)
Modem Status: Showtime (DMTDSL_SHOWTIME)
DSL Mode: ITU G.992.1 (G.DMT)
ITU STD NUM: 0x01 0x1
Vendor ID: 'ALCB' 'BDCM'
Vendor Specific: 0x0000 0x610C
Vendor Country: 0x00 0xB5
Capacity Used: 22% 45%
Noise Margin: 30.0 dB 23.0 dB
Output Power: 20.0 dBm 11.5 dBm
Attenuation: 28.0 dB 9.0 dB
Defect Status: None None
Last Fail Code: None
Selftest Result: 0x00
Subfunction: 0x15
Interrupts: 1333 (0 spurious)
PHY Access Err: 0
Activations: 1
Init FW: embedded
Operation FW: embedded
SW Version: 3.8131
FW Version: 0x1A04
Interleave Fast Interleave Fast
Speed (kbps): 0 1536 0 384
Reed-Solomon EC: 0 0 0 0
CRC Errors: 0 0 0 0
Header Errors: 0 0 0 0
Bit Errors: 0 0
BER Valid sec: 0 0
BER Invalid sec: 0 0
DMT Bits Per Bin
00: 0 0 0 0 0 0 0 2 2 4 5 6 6 6 6 6
10: 6 6 5 6 6 6 6 6 5 5 5 5 5 5 0 0
20: 0 0 0 0 0 0 0 0 2 2 0 0 0 2 2 2
30: 2 2 2 2 2 2 2 2 2 3 3 3 4 4 4 4
40: 4 4 4 4 4 2 4 4 5 5 5 5 5 5 5 5
50: 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 4
60: 4 4 4 4 4 4 4 4 4 4 3 3 3 2 2 2
70: 2 2 2 2 2 2 0 0 0 0 0 0 0 0 0 0
80: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
90: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
A0: 0 0 0 2 2 0 0 0 0 2 0 2 2 2 2 2
B0: 2 0 2 2 2 2 2 2 2 3 3 3 3 3 3 3
C0: 3 3 3 3 3 3 3 4 4 4 4 4 4 4 4 4
D0: 4 3 3 4 3 3 3 3 3 3 3 3 3 3 3 2
E0: 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
F0: 2 2 2 2 2 2 0 0 0 0 0 0 0 0 0 0
DSL: Training log buffer capability is not enabled
############################ | |
netboy
@epix.net
| reply to netboy
My speedtest (speedtest.net) seems to be adequate now, but does anyone know why I am still seeing 384K in the "sh int atm0" ?
MTU 4470 bytes, sub MTU 4470, BW 384 Kbit, DLY 5330 usec,.....
Just wondering if the WIC-1ADSL does not give an accurate measurement here, or if there is some other explanation. | |
Phraxos
Premium
join:2004-06-12
UK
| FWIW I have no idea where the BW figure comes from. Mine also bares no obvious relation to the actual bandwidth figure of the connection.
I think you will find that people rarely look at that output; "sh dsl int atm" tells you a lot more useful info. | |
netboy
@epix.net | Thanks again. | |
RyanG1
Premium
join:2002-02-10
San Antonio, TX
clubs: 
edit:
December 28th, @02:30AM
| the command
reports the actual sync speed in both downstream and upstream as well as the channel type.
yours reports
so you have a downstream channel using fastpath at 1536 kbps and an upstream channel using fastpath at 384 kbps.
the bandwidth listed on the sh int atm0 is for QoS purposes only, not an actual listing of interface speed/sync rate.
--
call me on FWD: 654674 | |
|
