cancel
Showing results for 
Search instead for 
Did you mean: 

Slow speed after upgrade to M500

prosys
Tuning in

Hi all,

Upgraded to M500 couple of days ago after being on 100 and struggling with utilization. Barely getting 200MBits/sec.

Will post router stats below

prosys_0-1634064293867.png

 

7 REPLIES 7

legacy1
Alessandro Volta
Tested by wire?

---------------------------------------------------------------

prosys
Tuning in

Cable Modem StatusItem Status Comments

Acquired Downstream Channel (Hz)
203000000
Locked
Ranged Upstream Channel (Hz)
46200000
Locked
Provisioning State
Online

 

 

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

12030000004.638256 qam9
22110000004.538256 qam10
32190000004.538256 qam11
42270000004.538256 qam12
52350000004.638256 qam13
62430000004.538256 qam14
72510000004.538256 qam15
82590000004.338256 qam16
9267000000438256 qam17
102750000003.438256 qam18
11283000000338256 qam19
122910000003.438256 qam20
132990000004.138256 qam21
143070000004.638256 qam22
153150000004.938256 qam23
16323000000538256 qam24
173310000004.938256 qam25
183710000005.838256 qam26
193790000005.638256 qam27
203870000005.538256 qam28
213950000005.838256 qam29
22403000000638256 qam30
234110000006.138256 qam31
244190000005.938256 qam32



Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked38.61800
2Locked38.61510
3Locked38.91290
4Locked38.61170
5Locked38.61200
6Locked38.9780
7Locked38.6580
8Locked38.92340
9Locked38.9410
10Locked38.6770
11Locked38.9880
12Locked38.61430
13Locked38.6670
14Locked38.9520
15Locked38.9830
16Locked38.6380
17Locked38.6350
18Locked38.9280
19Locked38.91550
20Locked38.9990
21Locked38.9350
22Locked38.6290
23Locked38.9310
24Locked38.9290

 



Yeah tested using CAT6 on both work and personal laptop and tested on 5Ghz on IPhone close to the router 

prosys
Tuning in

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

14620000043512064 qam1
22580000042512064 qam4
33940000042.8512064 qam2
43260000042.3512064 qam3



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0020
2ATDMA0010
3ATDMA0000
4ATDMA0000

 

prosys
Tuning in

General Configuration

Network access

Allowed

Maximum Number of CPEs

1

Baseline Privacy

Enabled

DOCSIS Mode

Docsis30

Config file

cmreg-vmdg505-bbt053-b.cm

 

Primary Downstream Service Flow

SFID

33220

Max Traffic Rate

575000000

Max Traffic Burst

42600

Min Traffic Rate

0

 

Primary Upstream Service Flow

SFID

33219

Max Traffic Rate

38520000

Max Traffic Burst

42600

Min Traffic Rate

0

Max Concatenated Burst

16320

Scheduling Type

BestEffort

prosys
Tuning in

 

Network Log

Time

Priority

Description

11/10/2021 22:54:20

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

11/10/2021 16:59:25

Error

DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

10/10/2021 03:57:23

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

08/10/2021 14:38:46

notice

LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

01/01/1970 00:01:41

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

07/10/2021 21:44:23

Error

DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

04/10/2021 18:36:25

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

04/10/2021 11:05:23

notice

LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

04/10/2021 11:04:47

Warning!

LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

04/10/2021 08:18:8

Error

DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

30/09/2021 21:18:14

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

30/09/2021 20:18:7

Error

DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

28/09/2021 12:51:50

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

24/09/2021 19:25:36

Error

DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

24/09/2021 19:25:34

Error

DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

24/09/2021 16:42:5

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

19/09/2021 23:55:35

Error

DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

17/09/2021 01:32:13

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

16/09/2021 11:55:35

Error

DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

14/09/2021 07:35:48

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

Natalie_L
Forum Team (Retired)
Forum Team (Retired)

Hi prosys, 

 

Thank you for reaching out to us here on the Community. 

 

I am very sorry to hear you have been experiencing some issues with the service since upgrading. 

 

I have taken a look at the data and nothing is jumping out at me to suggest there is an issue with the power levels. 

 

Are you using a BQM (Broadband Quality Monitor) on the service? If so, are you able to post a link to this so that we may take a look? 

 

Thanks 

 

 

Nat