Reply
Highlighted
Tutor

Re: SB8200 .to RAX200 WAN aggregation slows down

I can't find in the tech specs or user manual the LAG method used is it 802.3d lacp or Netgear prop? Assume the two ends of the links are talking different protocols. Only way I could get this working reliably was to split links across two different on prem layer 2 switches then re aggregate them. 

be great if tech support could clarify the protocol used then we could look up the tech specs of the modems and determine which will work or not. Other wise shooting in the dark

Message 76 of 119
Highlighted
Tutor

Re: SB8200 .to RAX200 WAN aggregation slows down

I have the latets firmware installed now for 2 days and stable without LAG for internet. I am now testing with LAG and will report back for router firmware version V1.0.2.88_1.0.50 (and the CM1200 modem still on V1.02.02).

Model: RAX200|Nighthawk Tri-band AX12 12-Stream Wi-Fi 6 Router
Message 77 of 119
Highlighted
Guide

Re: SB8200 .to RAX200 WAN aggregation slows down

Latest firmware on RAX120 1.0.1.122 didn't help, nor firmware from support -- with Comcast, cm1200 firware v1.02.02 and hardware v1.01.

Another router where WAN LAG does work is the TP Link Archer C5400X (WAN and Port 1), then use LAN2 and LAN3 for LAG to switch.


Message 78 of 119
Highlighted
Tutor

Re: SB8200 .to RAX200 WAN aggregation slows down

Seems I cannot edit my post for an update, but the newest router firmware did not fix the issue. Internet slowed down 7.5 hours after I turned LAG back on. 

Model: RAX200|Nighthawk Tri-band AX12 12-Stream Wi-Fi 6 Router
Message 79 of 119
Highlighted
Guru

Re: SB8200 .to RAX200 WAN aggregation slows down

back to disabled LAG
CAX80-> RBK53-> GS716v2-> TP-Link M9Plus
Message 80 of 119
Highlighted
Aspirant

Re: CM1200 to Rax200 WAN aggregation slows down (requires reboot)

I just purchased this combo. Still waiting on my modem to arrive. I am just now reading through this entire thread, and honestly can’t believe this is such a problem. Has anyone actually had NETGEAR entertain a response as to why this is actually happening? Are there any products out there where LAG actually works?
Model: CM1200|Nighthawk Multi-Gig Speed Cable Modem, RAX200|Nighthawk Tri-band AX12 12-Stream Wi-Fi 6 Router
Message 81 of 119
Highlighted
Guide

Re: CM1200 to Rax200 WAN aggregation slows down (requires reboot)

You should really return both of them and pre-order the CAX80. Simplest solution.
Model: CM1200|Nighthawk Multi-Gig Speed Cable Modem, RAX200|Nighthawk Tri-band AX12 12-Stream Wi-Fi 6 Router
Message 82 of 119
Highlighted
Guide

Re: CM1200 to Rax200 WAN aggregation slows down (requires reboot)

CAX80 arrives today... will be interesting see how it works — for all in one device the router firmware is different than modem which is interesting
Message 83 of 119
Highlighted

Re: CM1200 to Rax200 WAN aggregation slows down (requires reboot)


@nEo717 wrote:
....for all in one device the router firmware is different than modem which is interesting

It always is.

 

For example, there is a big problem with cable modems. Only ISPs can update that. Thus blocking Netgear from providing updates.

Just another user.

My network DM200 -> R7800 -> GS316 -> PL1000 -> Orbi RBR40 -> Orbi RBS50Y -> RBS40V
Message 84 of 119
Highlighted

Re: CM1200 to Rax200 WAN aggregation slows down (requires reboot)

All

 

   My recommendations would be the Asus GT-AX11000 Wi-Fi 6 Router paired with cm1200. I heard it works. Hence the issue we have is netgear hasn't communicate anything about the "fix". Their release notes state that there are no issues but we know there is an issue. It's been going on for months and the rumor is they have "fix" but it to my understanding hasn't been stated anywhere. The rumor is the cable modem fixes the problem even though the cable modem works with other routers. My guess is the modem "fix" is to force a disconnect once a day or so. That forces router to rebuild the connection stack. We know that if you pull the cable from the router to the cable modem it starts to work again for about a day.

Message 85 of 119
Highlighted
Guide

Re: CM1200 to Rax200 WAN aggregation slows down (requires reboot)

I switched to now to Netgear CAX80 -- Its the first Modem/Router I've found to be acceptable (let alone its actually pretty good) -- speed tests run around 1208 Mb/s now and never a need to reboot -- Bufferbloat bounces around from A to C is only thing that could use some work (but then again that's a problem for most devices like this). I'm using the Mult-gig port to connect to 10G switch which elimates any need at all for any link aggregation. 

Message 86 of 119
Highlighted

Re: CM1200 to Rax200 WAN aggregation slows down (requires reboot)

I can tell you that using the ROG GT-AX11000 with the CM1200 Link Aggregation doesnt work.  I have been trying for over a year to get it to work, complained to Comcast engineering, complained to Netgear, and nothing has ever been done to resolve the issue.  With the benefit of 10G and 2.5G dedicated ports and such on the market, I doubt it will ever be fixed.

Message 87 of 119
Highlighted

Re: CM1200 to Rax200 WAN aggregation slows down (requires reboot)

my mistake somebody posted that they had a AUS that work. It was Asus RT-AX88U they said worked. I do not know if any AUS rounders work,the person that was asking purchased something else anyways. thanks for the info. There many new products out now haven't been keeping up with new ones. I don't know if any work for sure. Netgrear isn't going fix issue I agree. I don't believe it's a Comcast issue. Netgear release notes doesn't acknowledge any issues WAN

 

i don't have 1g service. I get about 350 mbps constantly without WAN which is the speed of service. It is better than the old linksys router I had.

Model: RAX120|Nighthawk AX12 12-Stream WiFi Router
Message 88 of 119
Highlighted

Re: CM1200 to Rax200 WAN aggregation slows down (requires reboot)

I have the 1G service with comcast and I average about 947.82 down and about 42up.  I have been in communication with someone in Comcast who has taken this to engineering and this was the response we got back yesterday.

 

"Hey Chris,

Following up, the eng team responded and said Netgear confirmed this issue was fixed in the latest firmware V2.02.05 which is rolling out to Comcast customers GA 8/19 in 2 days."

 

So if everyone can start reporting that has comcast as your service and your firmware revision after 08/19 to verify if you have received the new v2.02.05 would be great.  Remember it may take a day or two to receive after the initial rollout.

 

Model: CM1200|Nighthawk Multi-Gig Speed Cable Modem
Message 89 of 119
Highlighted
Tutor

Re: CM1200 to Rax200 WAN aggregation slows down (requires reboot)

For which device? I would assume you mean the modem (CM1200) since that is the only device Comcast can push to, but the current version is V1.02.02 and the version you mentioned would be a huge jump which I rarely see happen. Curious if the version is wrong or I am thinking of the wrong device...
Message 90 of 119
Highlighted
Tutor

Re: CM1200 to Rax200 WAN aggregation slows down (requires reboot)

I have the CM1150V and the current firmware version is V2.02.04
Message 91 of 119
Highlighted

Re: CM1200 to Rax200 WAN aggregation slows down (requires reboot)


@dayjob wrote:
For which device? I would assume you mean the modem (CM1200) since that is the only device Comcast can push to, but the current version is V1.02.02 and the version you mentioned would be a huge jump which I rarely see happen. Curious if the version is wrong or I am thinking of the wrong device...

As you suggest, it is down to ISPs to push firmware on to cable modems. Although one or two newer Netgear cable devices do claim to support user updates.

 

I have yet to see any evidence that ISPs update on a regular basis, especially for third party modems. (They may not even do it on rented modems.)  From what some people say here, most ISPs don't even seem to know about firmware.

 

It would be great to have reports here of updates going out to particular hardware.

Just another user.

My network DM200 -> R7800 -> GS316 -> PL1000 -> Orbi RBR40 -> Orbi RBS50Y -> RBS40V
Message 92 of 119
Highlighted

Re: CM1200 to Rax200 WAN aggregation slows down (requires reboot)

Well considering all this started when I was on the comcast forums investigsting the same issues across the board with my Comcast Account. I asked if he could look into this.  He is the Director of Technology Product Experience with Comcast.  I gave him various links to  many people having the same issues with my modem version and firmware. He was willing to push it up engineering chain to get some results.  He has, I have emailed him again regarding if the update and if it is limited to the CM1200 or will all be getting some type of firmware update across the board with multiple modems and such.  I am waiting to hear back at the moment.  

 

 

Message 93 of 119
Highlighted
Initiate

Re: CM1200 to Rax200 WAN aggregation slows down (requires reboot)

I can confirm that firmware V2.02.05 for the CM1200 has been released! My CM1200 reset itself on 12:08am Pacific on Comcast. Can't test out link aggregation right now and will do it later on today but it's good to know that a new firmware is out.

Message 94 of 119
Highlighted

Re: CM1200 to Rax200 WAN aggregation slows down (requires reboot)

I can also confirm new firmware pushed to CM1200 on the Southeast coast. Setup aggregation this AM. Will confirm fix in 24hrs.
Message 95 of 119
Highlighted
Luminary

Re: CM1200 to Rax200 WAN aggregation slows down (requires reboot)

@tcmathews, has Comcast provided the release notes for CM1200 firmware V2.02.05?

 

P.S.:  Firmware on my CM1200 was automatically updated from V1.02.02 to V2.02.05 early this morning by Comcast.

Model: CM1200|Nighthawk Multi-Gig Speed Cable Modem, RAX120|Nighthawk AX12 12-Stream WiFi Router
Message 96 of 119
Highlighted

Re: CM1200 to Rax200 WAN aggregation slows down (requires reboot)

@Topology  Not as of yet.  I will send my contact an email asking if he can get the notes. Netgear hasnt updated their page of firmware releases to date so not sure when they will do that considering they wouldnt admit there was an issue. I have setup my aggregation between my CM1200 and ASUS ROG GT-AX11000 and will be monitoring throughout the next 24hrs.

 

Can you guys post your event logs, I am curious to see if anyone else is getting this particular error.

 

TimePriorityDescription
Wed Aug 19 05:34:25 2020Warning (5)REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 05:34:21 2020Critical (3)SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 05:34:21 2020Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 05:34:16 2020Notice (6)TLV-11 - unrecognized OID;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 02:06:39 2020Warning (5)REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 02:06:35 2020Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 02:06:30 2020Notice (6)TLV-11 - unrecognized OID;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 02:04:38 2020Notice (6)SW download Successful - Via Config file
Wed Aug 19 02:03:52 2020Notice (6)SW Download INIT - Via Config file d11_m_cm1200_gigabit_c01.cm
Wed Aug 19 02:03:38 2020Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 02:03:33 2020Notice (6)TLV-11 - unrecognized OID;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Wed Aug 19 02:02:13 2020Critical (3)Resetting the cable modem due to docsDevResetNow
Tue Aug 18 23:20:46 2020Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 18 23:20:38 2020Notice (6)CM-STATUS message sent. Event Type Code: 22; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 18 23:20:35 2020Notice (6)CM-STATUS message sent. Event Type Code: 23; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 18 14:10:49 2020Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 18 14:09:59 2020Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 18 14:09:19 2020Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 18 14:08:42 2020Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 18 14:08:05 2020Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 18 14:07:39 2020Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 18 14:07:11 2020Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 18 14:06:47 2020Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 18 14:04:01 2020Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 18 14:03:35 2020Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 18 11:54:38 2020Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 18 11:54:10 2020Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 17 13:27:54 2020Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 17 13:27:21 2020Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 17 12:47:04 2020Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 17 12:46:31 2020Notice (6)CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 17 12:45:04 2020Notice (6)CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=08:36:c9:3f:2f:50;CMTS-MAC=00:01:5c:8e:a0:54;CM-QOS=1.1;CM-VER=3.1;
Message 97 of 119
Highlighted

Re: CM1200 to Rax200 WAN aggregation slows down (requires reboot)

that doesnlt exist for cable devices, where Netgear


@tcmathews wrote:

@Topology  Not as of yet.  I will send my contact an email asking if he can get the notes. Netgear hasnt updated their page of firmware releases to date so not sure when they will do that considering they wouldnt admit there was an issue.

Apart from not admitting that there is an issue, if that happened, there is nowhere obvious for Netgear to post release notes for cable modem firmware. Fixes and updates usually sit in the firmware bundle for routers and other devices, but it can't post new firmware for cable kit.

 

Something on the product support pages would be good. Stuff gets lost here.

 

Congratulations are in order for actually getting an ISP to take responsibility for the problem and finding a fix. This rarely, if ever, seems to happen. Well done.

 

By the way, if, or when, people are happy with the outcome, it might be good to mark this discussion as Solved. That could guide newcomers who turn up with the same problem.

Just another user.

My network DM200 -> R7800 -> GS316 -> PL1000 -> Orbi RBR40 -> Orbi RBS50Y -> RBS40V
Message 98 of 119
Highlighted

Re: CM1200 to Rax200 WAN aggregation slows down (requires reboot)

Internet completely shuts off now instead of just slowing down after about an hour.

Port agg will clearly never be available on these devices. The CM1200 and RAX200 are officially the last Netgear devices I ever purchase.
Message 99 of 119
Highlighted
Star

Re: CM1200 to Rax200 WAN aggregation slows down (requires reboot)

I can confirm CM2000 firmware update to  V2.02.05 at 1:20 AM CST (Minnesota).  I have one of the warning messages asked about above in the logs.  No messages since then.

 

Wed Aug 19 01:20:08 2020Warning (5)DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=28:80:88:ae:cb:30;CMTS-MAC=58:97:bd:98:bc:f0;CM-QOS=1.1;CM-VER=3.1;

 

It has been one year since Netgear responded to my escalated case on performance degradation that this problem would be fixed. I plan to test link aggregation later today, and I will report my results.

Message 100 of 119
Top Contributors
Discussion stats
Announcements