cancel
Showing results for 
Search instead for 
Did you mean: 

General Instability and Slow Upload

tony22
On our wavelength

Hi folks,

1/2

Virgin recently resolved the severe evening congestion problems. However, we're now encountering intermittent drop-outs and upload performance problems. It's a real pain, as I lose my connectivity to company network.

The graph looks ok other than some latency spikiness:

tony22_0-1656082362391.png

I'm also pasting stats and log. Anything obvious amiss?

Cable Modem Status

Item

Status

Comments

Cable Modem Status

Online

DOCSIS 3.1

Primary downstream channel

Locked

SC-QAM

Channel Overview

Downstream

Upstream

DOCSIS 3.0 channels

31

4

DOCSIS 3.1 channels

1

0

 

3.0 Downstream channels

Channel

Frequency (Hz)

Power (dBmV)

SNR (dB)

Modulation

Channel ID

29

363000000

4.2

37.4

QAM256

29

1

139000000

6

33.4

QAM256

1

2

147000000

5.8

33.8

QAM256

2

3

155000000

5.5

34

QAM256

3

4

163000000

5.2

34.5

QAM256

4

5

171000000

4.8

34.5

QAM256

5

6

179000000

4.6

34.9

QAM256

6

7

187000000

4.6

35.1

QAM256

7

8

195000000

4.6

35.8

QAM256

8

9

203000000

4.5

35.6

QAM256

9

10

211000000

4.5

36.4

QAM256

10

11

219000000

4.4

36.4

QAM256

11

12

227000000

4.7

36.6

QAM256

12

13

235000000

4.9

36.4

QAM256

13

14

243000000

5.1

36.6

QAM256

14

15

251000000

5.1

37.4

QAM256

15

16

259000000

5.2

37.4

QAM256

16

17

267000000

5

37.4

QAM256

17

18

275000000

4.9

37.4

QAM256

18

19

283000000

4.9

37.6

QAM256

19

20

291000000

5.1

37.6

QAM256

20

21

299000000

5

37.6

QAM256

21

22

307000000

4.6

37.4

QAM256

22

23

315000000

4.4

37.6

QAM256

23

24

323000000

4

37.6

QAM256

24

25

331000000

4.1

37.4

QAM256

25

26

339000000

4.2

37.4

QAM256

26

27

347000000

4.1

37.6

QAM256

27

28

355000000

4.2

37.6

QAM256

28

30

371000000

4.3

37.4

QAM256

30

31

379000000

4.2

37.6

QAM256

31

 

3 REPLIES 3

tony22
On our wavelength

2/2

3.0 Downstream channels

Channel

Lock Status

RxMER (dB)

Pre RS Errors

Post RS Errors

29

Locked

37.355988

0

0

1

Locked

33.376591

717

0

2

Locked

33.834164

321

0

3

Locked

33.956509

99

0

4

Locked

34.483570

56

0

5

Locked

34.483570

34

0

6

Locked

34.925610

16

0

7

Locked

35.083549

4

0

8

Locked

35.779911

0

0

9

Locked

35.595078

1

0

10

Locked

36.386890

2

0

11

Locked

36.386890

0

0

12

Locked

36.609653

0

0

13

Locked

36.386890

0

0

14

Locked

36.609653

0

0

15

Locked

37.355988

0

0

16

Locked

37.355988

0

0

17

Locked

37.355988

0

0

18

Locked

37.355988

0

0

19

Locked

37.636276

0

0

20

Locked

37.636276

0

0

21

Locked

37.636276

0

0

22

Locked

37.355988

0

0

23

Locked

37.636276

0

0

24

Locked

37.636276

0

0

25

Locked

37.355988

0

0

26

Locked

37.355988

0

0

27

Locked

37.636276

0

0

28

Locked

37.636276

0

0

30

Locked

37.355988

0

0

31

Locked

37.636276

0

0

 

3.1 Downstream channels

Channel

Channel Width (MHz)

FFT Type

Number of Active Subcarriers

Modulation (Active Profile)

First Active Subcarrier (Hz)

159

96

4K

1880

QAM4096

759




3.1 Downstream channels

Channel ID

Lock Status

RxMER Data (dB)

PLC Power (dBmV)

Correcteds (Active Profile)

Uncorrectables (Active Profile)

159

Locked

38

4.3

2038652520

3699

 

3.0 Upstream channels

Channel

Frequency (Hz)

Power (dBmV)

Symbol Rate (ksps)

Modulation

Channel ID

1

32600000

43

5120 KSym/sec

64QAM

5

2

39400000

44

5120 KSym/sec

64QAM

4

3

46200000

44.8

5120 KSym/sec

64QAM

3

4

53700000

45.8

5120 KSym/sec

64QAM

2




3.0 Upstream channels

Channel

Channel Type

T1 Timeouts

T2 Timeouts

T3 Timeouts

T4 Timeouts

1

US_TYPE_STDMA

0

0

1

0

2

US_TYPE_STDMA

0

0

0

0

3

US_TYPE_STDMA

0

0

0

0

4

US_TYPE_STDMA

0

0

1

0

 

Network Log

Time

Priority

Description

Thu 16/06/2022 08:40:29

3

No Ranging Response received - T3 time-out;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;

Thu 16/06/2022 08:40:37

6

CM-STATUS message sent. Event Type Code: 4; Chan ID: 9; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC= CM-QOS=1.1;CM-VER=3.1;

Thu 16/06/2022 08:40:37

3

No Ranging Response received - T3 time-out;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;

Thu 16/06/2022 08:41:09

3

Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

Thu 16/06/2022 08:41:09

3

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=;CMTS-MAC=:23;CM-QOS=1.1;CM-VER=3.1;

Thu 16/06/2022 08:41:29

3

Ranging Request Retries exhausted;CM-MAC=;CMTS-MAC=00:;CM-QOS=1.1;CM-VER=3.1;

Thu 16/06/2022 08:41:29

3

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=;CMTS-MAC=3;CM-QOS=1.1;CM-VER=3.1;

Thu 16/06/2022 08:41:49

3

Ranging Request Retries exhausted;CM-MAC=;CMTS-MAC=00:;CM-QOS=1.1;CM-VER=3.1;

Thu 16/06/2022 08:41:49

3

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

Thu 16/06/2022 08:42:29

3

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

Thu 16/06/2022 08:47:50

5

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC= CM-QOS=1.1;CM-VER=3.1;

Thu 16/06/2022 08:54:16

6

CM-STATUS message sent. Event Type Code: 5; Chan ID: 22; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;

Thu 16/06/2022 15:09:11

3

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;

Thu 16/06/2022 15:09:15

5

Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

Thu 16/06/2022 15:09:20

6

CM-STATUS message sent. Event Type Code: 5; Chan ID: 5; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;

Thu 16/06/2022 15:10:28

3

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC= CM-QOS=1.1;CM-VER=3.1;

Thu 16/06/2022 15:10:33

5

Lost MDD Timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

Thu 16/06/2022 15:10:43

3

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Thu 16/06/2022 15:11:08

5

Lost MDD Timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

Thu 16/06/2022 15:11:17

6

CM-STATUS message sent. Event Type Code: 4; Chan ID: 2; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;

Thu 16/06/2022 15:11:46

3

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;

Thu 16/06/2022 15:12:02

6

CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;

Thu 16/06/2022 15:15:36

3

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;

Thu 16/06/2022 15:15:41

6

CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC= CM-QOS=1.1;CM-VER=3.1;

Thu 16/06/2022 15:26:01

5

DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;

Fri 17/06/2022 02:00:23

6

CM-STATUS message sent. Event Type Code: 5; Chan ID: 2; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;

Fri 17/06/2022 02:02:18

3

Unicast Ranging Received Abort Response - initializing MAC;CM-MAC= CM-QOS=1.1;CM-VER=3.1;

Fri 17/06/2022 02:02:18

3

No Ranging Response received - T3 time-out;CM-MAC=e4:57:;CM-QOS=1.1;CM-VER=3.1;

Fri 17/06/2022 02:03:16

6

CM-STATUS message sent. Event Type Code: 5; Chan ID: 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;

Fri 17/06/2022 02:12:20

3

No Ranging Response received - T3 time-out;CM-MAC=e4:57:;CM-QOS=1.1;CM-VER=3.1;

Fri 17/06/2022 02:12:51

6

CM-STATUS message sent. Event Type Code: 5; Chan ID: 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;

Fri 17/06/2022 02:14:16

3

Unicast Ranging Received Abort Response - initializing MAC;CM-MAC= 23;CM-QOS=1.1;CM-VER=3.1;

Fri 17/06/2022 02:14:17

3

No Ranging Response received - T3 time-out;CM-MAC=e4:57:;CM-QOS=1.1;CM-VER=3.1;

Fri 17/06/2022 02:14:36

6

CM-STATUS message sent. Event Type Code: 5; Chan ID: 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CM-QOS=1.1;CM-VER=3.1;

 

An engineer was here around the time the problem started too, to install in a neighbour's flat. Could there now be too many on a splitter? A previous engineer had put my direct but I now can't find my cable.

Hi tony22,

Thank you for your post. I'm very sorry for the issue you've been having with your Broadband service. 

I have taken a look on our system and it looks as though a technician visit maybe needed. 

I will private message you to confirm some details and look into this further. 

^Martin

Thank you for chatting with me over Private Message. 

Please keep us posted on the engineer visit.

^Martin