dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
21
share rss forum feed


metalhawk

join:2007-02-06
Nepean, ON
reply to highwire2007

Re: [Cable] Cable: Anyone still NOT have upstream channel bondin

My connection went down at 3am and still wasn't back at 8am. Rebooting the modem did nothing. I rebooted my router... et voila: 8/4 bonding. I live on Banner Rd.

Forward Path:
Channel Frequency Power SNR BER Modulation
1 609.0 MHz -6.3 dBmV 36.9 dB 0.000 % 256 QAM
2 591.0 MHz -5.5 dBmV 37.1 dB 0.000 % 256 QAM
3 597.0 MHz -5.8 dBmV 37.1 dB 0.000 % 256 QAM
4 603.0 MHz -6.2 dBmV 36.8 dB 0.000 % 256 QAM
5 615.0 MHz -6.3 dBmV 36.8 dB 0.000 % 256 QAM
6 621.0 MHz -6.4 dBmV 36.8 dB 0.000 % 256 QAM
7 633.0 MHz -5.9 dBmV 36.5 dB 0.000 % 256 QAM
8 639.0 MHz -6.0 dBmV 36.8 dB 0.000 % 256 QAM
Return Path:
Channel ID Frequency Power Modulation
2 25.3 MHz 45.8 dBmV 16 QAM
1 31.3 MHz 47.3 dBmV 16 QAM
3 22.1 MHz 45.8 dBmV 16 QAM
4 38.6 MHz 47.3 dBmV 16 QAM


chrisl83

join:2011-06-21
Almonte, ON

I got 8/4 yesterday and it broke my DCM 475 2.08.

I'm glad I'm moving away soon to Calgary.

I called at the crack of dawn tuesday, the fastest rogers can send a tech out is suppose to be Saturday.

That's a hilarious turn around time, I can't wait to get on shaw out there.



HiVolt
Premium
join:2000-12-28
Toronto, ON
kudos:21
Reviews:
·TekSavvy DSL
·TekSavvy Cable

1 edit

Hehe, i had 4x4 with QAM64 upstream bonding on my SB6120, and according to my logs my cable went out at around 3am, and didnt come back...

In the morning i couldnt even access the modem's diagnostic page. I rebooted it and it came back, still with 4x4 bonding but with only QAM16 on the upstream bonding... Weird... It has been rock solid for nearly 2 months on QAM64... I hope its not my modem starting to crap out, I really don't want one of those DCM's...

Some strange entries in the log after I rebooted it and regained access to the web interface.

Edit: hrm, seems my IP changed to a 198.x, maybe i got switched from McNicoll to Comstock? The tracert doesn't reveal anything relevant.

Edit2: Confirmed i got moved to Comstock, the RDNS hasn't been updated yet...

Sep 19 2012 11:51:14 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=e8:b7:48:0c:9a:c6;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice Cable Modem Reboot due to power reset ;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=e8:b7:48:0c:9a:c6;CM-QOS=1.1;CM-VER=3.0;
Sep 19 2012 08:19:13 6-Notice D106.0 DHCP Renew - lease parameters tftp file-bac1030001060022103aceec modified;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=e8:b7:48:0c:9a:c6;CM-QOS=1.1;CM-VER=3.0;
Sep 19 2012 08:19:13 4-Error D103.0 DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=e8:b7:48:0c:9a:c6;CM-QOS=1.1;CM-VER=3.0;
Sep 19 2012 07:54:42 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=e8:b7:48:0c:9a:c6;CM-QOS=1.1;CM-VER=3.0;
Sep 19 2012 07:54:41 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=e8:b7:48:0c:9a:c6;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:50 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=e8:b7:48:0c:9a:c6;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice Cable Modem Reboot due to T4 timeout ;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=e8:b7:48:0c:9a:c6;CM-QOS=1.1;CM-VER=3.0;
Sep 19 2012 07:53:21 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=e8:b7:48:0c:9a:c6;CM-QOS=1.1;CM-VER=3.0;
Sep 19 2012 07:53:21 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=e8:b7:48:0c:9a:c6;CM-QOS=1.1;CM-VER=3.0;
Sep 19 2012 07:53:20 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=e8:b7:48:0c:9a:c6;CM-QOS=1.1;CM-VER=3.0;
Sep 19 2012 07:53:11 5-Warning U102.0 TCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=e8:b7:48:0c:9a:c6;CM-QOS=1.1;CM-VER=3.0;
Sep 19 2012 07:53:11 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=e8:b7:48:0c:9a:c6;CM-QOS=1.1;CM-VER=3.0;
Sep 19 2012 07:53:11 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=e8:b7:48:0c:9a:c6;CM-QOS=1.1;CM-VER=3.0;
Sep 19 2012 07:53:11 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=e8:b7:48:0c:9a:c6;CM-QOS=1.1;CM-VER=3.0;
Sep 19 2012 07:53:11 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=e8:b7:48:0c:9a:c6;CM-QOS=1.1;CM-VER=3.0;
Sep 19 2012 07:53:11 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=e8:b7:48:0c:9a:c6;CM-QOS=1.1;CM-VER=3.0;
Sep 19 2012 07:53:10 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=e8:b7:48:0c:9a:c6;CM-QOS=1.1;CM-VER=3.0;
Sep 19 2012 07:53:10 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=e8:b7:48:0c:9a:c6;CM-QOS=1.1;CM-VER=3.0;
Sep 19 2012 07:53:10 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=e8:b7:48:0c:9a:c6;CM-QOS=1.1;CM-VER=3.0;
 

--
GO BLUE JAYS!



mlerner
Premium
join:2000-11-25
Nepean, ON
kudos:5
reply to metalhawk

Click for full size
Thanks for the heads up metalhawk. Upgraded here as well, but we're on the same street so just as expected. No modem outage here so I would have never known without that post.


metalhawk

join:2007-02-06
Nepean, ON
reply to metalhawk

Interestingly (and frustratingly), ever since I got upstream bonding, I have also gotten a bad case of the "resets". My DCM475 now reboots numerous times per day. It never (read: once per month or even less) used to happen. It started exactly when upstream bonding got here.



creed3020
Premium
join:2006-04-26
Kitchener, ON
kudos:2

Have you tried a factory reset on the modem? What firmware is your modem running currently?

I've been through two upstream bonding upgrades at different addresses/different POIs and never saw this occur with my DCM475.


mlord

join:2006-11-05
Nepean, ON
kudos:13
Reviews:
·Start Communicat..
reply to metalhawk

said by metalhawk:

My DCM475 now reboots numerous times per day. It never (read: once per month or even less) used to happen. It started exactly when upstream bonding got here.

Yeah, what "Software Version" (aka. firmware) is installed in that modem? (web interface at »192.168.100.1 , Diagnositics screen).

If it says "Stac 02.08", then the reboots may be curable by a firmware update to the recommended 02.16 version -- contact me to have the upgrade done locally in under half an hour.

Cheers


metalhawk

join:2007-02-06
Nepean, ON

2.08 is the version. And it's funny that you mention the upgrade because last night I read the thread where yourself and Teddy Boom experimented on the firmware flashing. A few more days of this here and I was going to PM you regarding it.



creed3020
Premium
join:2006-04-26
Kitchener, ON
kudos:2
Reviews:
·TekSavvy Cable

1 edit

said by metalhawk:

2.08 is the version. And it's funny that you mention the upgrade because last night I read the thread where yourself and Teddy Boom experimented on the firmware flashing. A few more days of this here and I was going to PM you regarding it.

I'm glad you read that thread now as I was going to recommend you to mlord based on your response of firmware. Looks like he took care of that already

My modem is at firmware 02.16 BTW, as it was a replacement for a SB6120 that died on me.

mlord

join:2006-11-05
Nepean, ON
kudos:13
Reviews:
·Start Communicat..
reply to metalhawk

said by metalhawk:

2.08 is the version. And it's funny that you mention the upgrade because last night I read the thread where yourself and Teddy Boom experimented on the firmware flashing. A few more days of this here and I was going to PM you regarding it.

Well, step one for anyone having the kinds of issues you see, is to get the modem up to date. That way you eliminate one possible cause of issues, now and for the future.

I ask only $5 towards the flashing rig costs, in exchange for updating a modem to the current 02.16 firmware. PM me when you decide to go for it. Friday evening is the next window of opportunity for getting it done.

Cheers


metalhawk

join:2007-02-06
Nepean, ON

First, here's my new stats. A few hours after I originally got upstream bonding, my connection went down again for a few hours. Upon coming back, my line stats were very different than what they were before. I'm no expert on this matter, but they look pretty good to me. The SNR could maybe be a bit higher, I suppose, but otherwise I think it's pretty clean.

Channel Frequency Power SNR BER Modulation
1 609.0 MHz 0.3 dBmV 38.0 dB 0.000 % 256 QAM
2 591.0 MHz 1.1 dBmV 38.3 dB 0.000 % 256 QAM
3 597.0 MHz 0.5 dBmV 38.2 dB 0.000 % 256 QAM
4 603.0 MHz 0.2 dBmV 38.0 dB 0.000 % 256 QAM
5 615.0 MHz 0.5 dBmV 37.8 dB 0.000 % 256 QAM
6 621.0 MHz 0.6 dBmV 37.9 dB 0.000 % 256 QAM
7 633.0 MHz 0.7 dBmV 37.5 dB 0.000 % 256 QAM
8 639.0 MHz 0.9 dBmV 37.6 dB 0.000 % 256 QAM
Return Path:
Channel ID Frequency Power Modulation
1 31.3 MHz 46.3 dBmV 16 QAM
2 25.3 MHz 44.3 dBmV 16 QAM
3 22.1 MHz 43.8 dBmV 16 QAM
4 38.6 MHz 45.3 dBmV 16 QAM

And every time my modem reboots, this pops up in the log:

Critical(3) - Received Response to Broadcast Maintenance Request, But no Un...
 


metalhawk

join:2007-02-06
Nepean, ON

As an update, mlord updated my firmware to 2.16 yesterday, and in the 30 hours or so since, not a single disconnect or error in the log. So if you're getting disconnects since getting your upstream bonded, this is your solution.