O Canada! > Canadian > TekSavvy > [Cable] Cable: Anyone still NOT have upstream channel bonding?

reply to highwire2007

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

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.

reply to metalhawk

reply to chrisl83
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;
 

reply to highwire2007
On a Thomson DCM476 right now, was a recent install, Markham area.

Status Code: Operational
Software Version: STAC.02.50
Software Model: a81a
Bootloader: 2.3.1

Cable Signal Details
Forward Path:
Channel Frequency Power SNR BER Modulation
1 663.0 MHz -0.4 dBmV 36.5 dB 0.000 % 256 QAM
2 615.0 MHz -0.4 dBmV 36.2 dB 0.000 % 256 QAM
3 621.0 MHz -0.3 dBmV 36.2 dB 0.000 % 256 QAM
4 633.0 MHz 0.0 dBmV 36.5 dB 0.000 % 256 QAM
5 639.0 MHz 0.0 dBmV 36.7 dB 0.000 % 256 QAM
6 645.0 MHz 0.1 dBmV 36.5 dB 0.000 % 256 QAM
7 651.0 MHz -0.1 dBmV 36.2 dB 0.000 % 256 QAM
8 657.0 MHz -0.2 dBmV 36.7 dB 0.000 % 256 QAM
Return Path:
Channel ID Frequency Power Modulation
2 25.3 MHz 32.3 dBmV 16 QAM
1 31.3 MHz 32.3 dBmV 16 QAM
3 22.1 MHz 32.3 dBmV 16 QAM
4 38.6 MHz 33.8 dBmV 16 QAM

reply to Perma
My north west London neighbourhood just got bonding on Friday. Hopefully the whole city will be covered soon.

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.

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.

reply to 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.

reply to metalhawk

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...
 

reply to highwire2007
Awesome. Received mine some time in the last couple days (finally).

reply to highwire2007
Just went from 4x2 64QAM to 4x4 64QAM in Brampton on my SB6120. Connection was down for an hour while the change was implemented by Robbers. My upstream speed has actually improved slightly after the upgrade, but it's still at the 1mbps tier as expected.

reply to highwire2007
1-Green and 4-Blue lights on my DCM476 meant a nice surprise this AM - channel bonding 8x4 (from 4x1).

Looks like its gone far to repair the issues of local node slow-down during peak hours that have been plaguing me for ~3 months (actually getting 28/1+ during peak hours this PM).

10/02/2012 - 11:47:00 PM EST

Status Code: Operational
Software Version: STAC.02.50
Software Model: a81a
Bootloader: 2.3.1
Cable Signal Details

Forward Path:
Channel Frequency Power SNR BER Modulation
1 597.0 MHz 0.4 dBmV 38.5 dB 0.000 % 256 QAM
2 591.0 MHz 0.3 dBmV 38.6 dB 0.000 % 256 QAM
3 603.0 MHz 0.2 dBmV 38.5 dB 0.000 % 256 QAM
4 609.0 MHz 0.4 dBmV 38.6 dB 0.000 % 256 QAM
5 615.0 MHz 0.4 dBmV 38.7 dB 0.000 % 256 QAM
6 621.0 MHz 0.5 dBmV 38.6 dB 0.000 % 256 QAM
7 633.0 MHz 0.4 dBmV 38.7 dB 0.000 % 256 QAM
8 639.0 MHz 0.4 dBmV 38.8 dB 0.000 % 256 QAM

Return Path:
Channel ID Frequency Power Modulation
1 31.3 MHz 38.3 dBmV 16 QAM
2 25.3 MHz 38.3 dBmV 16 QAM
3 22.1 MHz 38.3 dBmV 16 QAM
4 38.6 MHz 38.3 dBmV 16 QAM

Data Service Details
Provisioned Address: Yes
Provisioned Time: Yes
Provisioned Configuration: Yes
Registered: Yes
BPI: Enabled

reply to highwire2007

reply to SimGuy
I am in Ottawa (Orleans)
I have a DCM475 on stac 02.16
Just to be clear i did not upgrade it
I still only have 1 channel upstream
i have power cycled the modem

4 down channels
1 up channel

should it not be 8 down and 4 up if not better
why are other people in ottawa getting upstream bonding
do i need to do something

I supose this makes sense
my area is not congested
i was just hoping that with channel bonding
we will finally get acceptable upload speeds
i know nothing has changed yet but
would be nice