BSR 1000 error | docsis.org

You are here

BSR 1000 error

6 posts / 0 new
Last post
niamul
BSR 1000 error

hello
we have 1xbsr1000.

we upgraded the firmware to appImage_20113PRRU.bin. and after that we faced a problem. the problem is that with multiple clients connected to a modem, when one client starts downloading, the others do not get any bandwidth.

then we downgraded to bsr1000r_12004PRR.bin and the problem we face now is that we get input error on our RF interface and also on our ethernet interface.

here is the config

BSR 1000R(tm) version 1.2.0.04.PRR
Copyright (c) 2001 by RiverDelta Networks.
Compiled Wed Feb 4 13:58:31 EST 2004
MPC750 processor with 128MB memory.
Boot ROM: RDN CMTS Board BootRom 00.03.01.TA
CPU: MPC750
Memory Size: 128 MB
Board Program ID: RD
Format Version: 7
Assembly Type : 7
Part Number : PCA-0055-02 Rev A
Serial Number : 027006997
Product Number: 027007308
Fabric Interface FPGA Version: 00000043
Hardware Acceleration: ON
System Up Time: 2 days 17 hours 36 minutes 26 seconds

hermes#show ca mode sum
Interface Total Active Registered
Modems Modems Modems
Cable 0/0/U0 121 3 86
Cable 0/0/U1 74 1 56
Cable 0/0/U2 98 2 69
Cable 0/0/U3 115 0 85
Total 408 6 296

hermes#show cable modulation-profile

Profile 1
Intvl FEC FEC Burst Guard MOD Scrambl Scrambl Diff Preambl Last
usage err len len time type seed encode length code-
code corre mod word
reque 0 16 2 8 qpsk scrambl 0x152 no-dif 64 fixed
initi 5 34 0 48 qpsk scrambl 0x152 no-dif 128 fixed
stati 5 34 0 48 qpsk scrambl 0x152 no-dif 128 fixed
short 5 78 8 8 16qam scrambl 0x152 no-dif 144 short
long 10 235 121 8 16qam scrambl 0x152 no-dif 160 short

Profile 2
Intvl FEC FEC Burst Guard MOD Scrambl Scrambl Diff Preambl Last
usage err len len time type seed encode length code-
code corre mod word
reque 0 16 2 8 qpsk scrambl 0x152 no-dif 64 fixed
initi 5 34 0 48 qpsk scrambl 0x152 no-dif 128 fixed
stati 5 34 0 48 qpsk scrambl 0x152 no-dif 128 fixed
short 5 78 12 8 qpsk scrambl 0x152 no-dif 72 short
long 8 220 240 8 qpsk scrambl 0x152 no-dif 80 short

Profile 3
Intvl FEC FEC Burst Guard MOD Scrambl Scrambl Diff Preambl Last
usage err len len time type seed encode length code-
code corre mod word
reque 0 16 2 8 qpsk scrambl 0x152 no-dif 64 fixed
initi 5 34 0 48 qpsk scrambl 0x152 no-dif 128 fixed
stati 5 34 0 48 qpsk scrambl 0x152 no-dif 128 fixed
short 5 78 12 8 qpsk scrambl 0x152 no-dif 72 short
long 8 220 0 8 qpsk scrambl 0x152 no-dif 80 short

Interface settings::

interface cable 0/0
ip address 10.1.0.10 255.255.0.0
ip helper-address 10.0.0.235
cable helper-address 10.0.0.235 cable-modem
cable helper-address 10.0.0.235 host
ip access-group 127 in
no shutdown
no ip unreachables
cable downstream 0 frequency 405000000
cable downstream 0 modulation 64
cable downstream 0 power-level 515
cable downstream 0 rate-limit
no cable downstream 0 shutdown
cable upstream 0 frequency 21584000
cable upstream 0 channel-width 1600000
cable upstream 0 power-level default -70
cable upstream 0 modulation-profile 2
cable upstream 0 rate-limit
cable upstream 0 map-interval 2000
cable upstream 0 physical-delay automatic
no cable upstream 0 shutdown
cable upstream 1 frequency 23184000
cable upstream 1 channel-width 1600000
cable upstream 1 power-level default -70
cable upstream 1 modulation-profile 3
cable upstream 1 rate-limit
cable upstream 1 physical-delay automatic
no cable upstream 1 shutdown
cable upstream 2 frequency 15984000
cable upstream 2 channel-width 1600000
cable upstream 2 power-level default -60
cable upstream 2 modulation-profile 2
cable upstream 2 rate-limit
cable upstream 2 map-interval 2000
cable upstream 2 physical-delay automatic
no cable upstream 2 shutdown
cable upstream 3 frequency 24784000
cable upstream 3 channel-width 1600000
cable upstream 3 power-level default -80
cable upstream 3 modulation-profile 2
cable upstream 3 rate-limit
cable upstream 3 map-interval 2000
cable upstream 3 physical-delay automatic
no cable upstream 3 shutdown
ip dhcp relay information option
host authorization on

hermes#show interfaces cable 0/0 downstream
Cable 0/0: Downstream 0 is up
3117531 packet output, 1920089177 bytes, 0 discarded
304 total active modems
hermes#show interfaces cable 0/0 upstr
hermes#show interfaces cable 0/0 upstream
Cable 0/0: Upstream 0 is up
Received 8329 broadcasts, 2297 multicasts, 471514 unicasts
18156 discarded, 18156 errors, 0 unknown protocol
482140 packets input
Total Modems On This Upstream Channel : 89
Cable 0/0: Upstream 1 is up
Received 8457 broadcasts, 1284 multicasts, 376593 unicasts
18224 discarded, 18224 errors, 0 unknown protocol
386334 packets input
Total Modems On This Upstream Channel : 58
Cable 0/0: Upstream 2 is up
Received 5040 broadcasts, 2065 multicasts, 330771 unicasts
3857 discarded, 3857 errors, 0 unknown protocol
337876 packets input
Total Modems On This Upstream Channel : 71
Cable 0/0: Upstream 3 is up
Received 8864 broadcasts, 975 multicasts, 490423 unicasts
6104 discarded, 6104 errors, 0 unknown protocol
500262 packets input
Total Modems On This Upstream Channel : 85

hermes#show interfaces eth 0/0
ethernet 0/0 is up, line protocol is up
Hardware address is 00:30:b8:80:45:9f
Internet address is 10.0.0.10/16
MTU 1500 bytes, BW 100000 Kbits
Encapsulation Arpa
(Auto) Full-duplex, (Auto) 100Mb/s, 100BaseTX/FX
ARP Timeout 01:00:00
Last input 00:00:01, output 00:00:00
Last clearing of "show interface" counters 00:13:29
Last state change at 00:00:17, 1 interface resets
Queueing strategy: fifo
Output queue 0/100, 0 drops; input queue 0/0, 0 drops
1069 packets input, 152083 bytes
Received 125 broadcasts, 23 multicasts
0 input errors, 0 CRC, 0 overruns
0 runts, 0 giants, 0 alignments
1298 packets output, 567587 bytes
0 output errors, 0 collisions, 0 underruns
0 late collisions, 0 deferred, 0 lost carrier

any and all help on this matter would be greatly appreciated.

niamul
realy need help

nobody to suggest anything?

cmcaldas
all in the timing

Your post was on a Sunday and Monday was a holiday ;-)
As for the firmware downgrade, that would not have made a difference. regardless of the cmts you use, you would of had the same problem.
the cmts will limit the speed of the modem, not each cpe behind it..... I recommend you go back to the newer firmware and add a router with qos behind the modem. thinking there's a hub or switch behind the modem now. swap it with a router and configure it so each user can only have 1 meg each for example.
If a modem gets a file that's 3 meg down and 512k up for example, and rate limit is configured on the downstream and upstream. the cmts will limit the modem's speed to the 3Mb and 512k. the user behind the modem would get those speeds. if I configure the modem for 16 users, the speed would still be 3Mb and 512k. if one of those 16 users is doing a large ftp or file transfer, then they will eat up the bandwidth. the cmts is doing what it's configured to do. limit the modem's speed. it's up to you or the end user to rate limit behind the modem ..

cmcaldas
Speed

Anothing thing to think about, 408 modems sharing 27Mb downstrean and 2.5Mb upstream (b4 docsis overhead)
if possible, go to 256Qam downstream and 3.2 meg wide on the upstream. not sure what your snr is on the upstream, but if it's 21 and higher, go to 16Qam. otherwise, increase the channel width and leave it on qpsk

niamul
thanks

cmcaldas, thank you for the reply.

we here in bangladesh work saturday to thursday. we sometimes forget the rest of the world works mondays to friday :)

anyways, we have a NetForcer Allot to control the bandwidth of each client.. but some how the control of Allot is being bypassed by some QOS/COS parameter of the new firmware that we had upgraded to; which is why we came back to the old firmware.

our upstream SNR varies from 20 to 23 and the downstream from 30 to 35.
we are also get input packet drop in each upstream. if we reset the counter, we get a 1000 input errors within a minute or two. we searched the motorola site but found nothing. our search led us here and it seems this was a good find :)

for bandwidth control, we are thinking of installing a Mikrotik router 3.23 OS. that should effectively control the bandwidth of each client. for some of the modems, we have more than 25 clients under each modem and those are the ones that are facing most of the problem.

our client bandwidth varies from package to package, 96kb/s to 256kb/s to FDX 512kb/s.

the biggest problem isn't getting bandwidth, but that it fluctuates. all of a sudden download and browsing will stop for 30 seconds or more and then resume. if clients download from our local server, they usually get their full bw of lets say 32kB/s and it will drop to 2kB/s and rise again. then they will get their full bandwidth assigned.

the drop is possible due to the input error on the upstream port but we are unsure, hence posting here.

anymore input on it would be great.

what we may try now is upgrade the firmware to the latest and adding the mikrotik bandwidth controller.. before we do that, we are hopeful more people here will have some better suggestion.

tia

Niamul

cmcaldas
low cpu maybe?

I'm thinking your controlling the user traffic after the cmts rather than before it. what do you have for a delta when you run sh proc cpu?
what is the uncorrectable on the return? what does the modem file have in regards to downstream and upstream speed, taking into consideration that there are 25 users behind the modem. have you tried to lower the number of users behind each modem? thinking if there's 25+ users for each modem and the return is 128 or 256k there isn't enough bandwidth. I recommend no more than 16 users, if anyone else thinks otherwise, please let me know

Log in or register to post comments