Forum Discussion

ellisb51's avatar
ellisb51
Joining in
2 years ago

network stats check

Is someone able to check the below stats for me? Are the numerous T3 timeouts concerning?

 

Downstream bonded channels

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

1139000000-1.738256 qam1
2147000000-1.540256 qam2
3155000000-1.740256 qam3
4163000000-1.740256 qam4
5171000000-1.540256 qam5
6179000000-1.540256 qam6
7187000000-1.440256 qam7
8195000000-1.240256 qam8
9203000000-1.440256 qam9
10211000000-1.740256 qam10
11219000000-1.540256 qam11
12227000000-1.740256 qam12
13235000000-1.740256 qam13
14243000000-1.940256 qam14
15251000000-1.940256 qam15
16259000000-1.940256 qam16
17267000000-1.540256 qam17
18275000000-1.540256 qam18
19283000000-1.440256 qam19
20291000000-1.240256 qam20
21299000000-140256 qam21
22307000000-140256 qam22
23315000000-0.940256 qam23
24323000000-0.740256 qam24



Downstream bonded channels

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

1Locked38.93500
2Locked40.31850
3Locked40.31010
4Locked40.31763
5Locked40.31000
6Locked40.31110
7Locked40.31160
8Locked40.3840
9Locked40.31310
10Locked40.31190
11Locked40.31110
12Locked40.31170
13Locked40.31690
14Locked40.32360
15Locked40.33330
16Locked40.33070
17Locked40.32240
18Locked40.32450
19Locked40.32090
20Locked40.31630
21Locked40.31770
22Locked40.31650
23Locked40.32720
24Locked40.32580

Upstream bonded channels

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

13660000043.5512064 qam11
22360000044.3512064 qam13
33010000043.8512064 qam12
44310000044.3512064 qam10
54960000044.3512064 qam9



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA00260
2ATDMA0040
3ATDMA0080
4ATDMA0070
5ATDMA0060

 

General Configuration

Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
834ncxv9873254k;fg87dsfd;



Primary Downstream Service Flow

SFID23500
Max Traffic Rate402500089
Max Traffic Burst42600
Min Traffic Rate0



Primary Upstream Service Flow

SFID23499
Max Traffic Rate38500089
Max Traffic Burst42600
Min Traffic Rate0
Max Concatenated Burst42600
Scheduling TypeBestEffort

 

7 Replies

Sort By
    • ellisb51's avatar
      ellisb51
      Joining in
      2 years ago

      See below:

      Network Log

       

      Time Priority Description

      22/02/2024 00:24:22noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      22/02/2024 00:24:22ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      19/02/2024 00:35:41criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      18/02/2024 12:24:22noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      18/02/2024 12:24:22ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      15/02/2024 00:24:21noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      15/02/2024 00:24:21ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      11/02/2024 12:55:7criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      11/02/2024 12:24:21noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      11/02/2024 12:24:21ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      09/02/2024 14:47:51criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      08/02/2024 00:24:21noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      08/02/2024 00:24:21ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      06/02/2024 00:32:43criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      04/02/2024 12:24:21noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      04/02/2024 12:24:21ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      02/02/2024 01:55:41criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      02/02/2024 01:55:39Warning!B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      02/02/2024 01:54:1criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
      02/02/2024 01:53:32critical
      • Adduxi's avatar
        Adduxi
        Very Insightful Person
        2 years ago

        I would suggest a factory reset as below.  There is something amiss with that number of T3 errors, it's as if the Hub is not completing a download from VM?

        60 second factory pinhole reset as below;
        Remove any ethernet cables from the Hub and hold the pinhole reset switch for 60 seconds. Do NOT reboot the Hub, just let it do it's thing. Note you will need the passwords from the bottom of the Hub afterwards, so make sure they are legible. NOTE this will remove any custom settings you may have set in the Hub, and they will all have to be setup again.