cancel
Showing results for 
Search instead for 
Did you mean: 

Post-RS Errors

bmo
Tuning in

Hi,

Experiencing lots of glitchiness across my 100MB connection to a HUB3.

The logs are showing what feels like quite a lot of Pre and Post-RS errors:

bmo_0-1629814485553.png

Might this be the cause of the glitchiness? Worth escalating to the support team @ VM?

Thanks

Boyd

 

1 ACCEPTED SOLUTION

Accepted Solutions

Tom_F
Forum Team (Retired)
Forum Team (Retired)

Thanks for getting back to me @bmo. I've scheduled a visit from an engineer, you will find confirmation via your online account (virg.in/myVM) and can reschedule from there if needed.

 

Please keep us posted with how that goes, or let us know if we can help with anything else.

 

Tom 

See where this Helpful Answer was posted

18 REPLIES 18

bmo
Tuning in

Oh - and I rebooted the hub last week....

bmo
Tuning in

Logs are a little variable too. But then it's sometimes once per day, and other times pretty patchy/glitchy at times

Time Priority Description

24/08/2021 13:51:43Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/08/2021 13:46:54noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/08/2021 13:46:9Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/08/2021 12:20:33Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/08/2021 01:31:2ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2021 12:19:0Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/08/2021 17:24:43criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/08/2021 13:31:1ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/08/2021 17:05:53criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

jbrennand
Very Insightful Person
Very Insightful Person
That looks a dreadful connection - looks like it may need a Tech visit - can you post up more details this way....
___________________________________________________________

In your browser’s URL box type in http://192.168.0.1  (or http://192.168.100.1 - if in modem mode) and hit return. On the first page up [there should be no need to login if you have done so before unless you have the New Hub4 when you do] click on the “router status” icon/text at bottom-middle or top/right of the first page up and then copy/paste as “Formatted Text” (not images) 3 FULL sets of data onto here – 2 pages from the Downstream, 2 from the Upstream, & the Network Logs page. Don't worry too much about the formatting it can be easily read & DON’T include personal data or MAC addresses - blank them out - if you copy/paste the data, the board software will do this for you (you may need to click the "submit" button again.

Also, in the meantime... If you haven’t already, set up a free, secure and “offlsite” - “Broadband Quality Monitor” to continually monitor the state of your connection and record any true network dropouts , latency issues, packet drops, etc - it will thus allow you to differentiate between those and simple wifi dropouts. It does it 24/7/365 and it keeps a visual record of any/all of your network disconnections, useful data to have to match to the Network logs (in your Hub settings) and also in discussions with VM - note it will take a few hours to start seeing a sensible picture - post up the “link” to the “share live graph” (as per instructions on the TB website) when it starts to develop.

https://www.thinkbroadband.com/broadband/monitoring/quality

--------------------
John
--------------------

I do not work for VM. My services: HD TV on VIP (+ Sky Sports & Movies & BT sport), x3 V6 boxes (1 wired, 2 on WiFi) Hub5 in modem mode with Apple Airport Extreme Router +2 Airport Express's & TP-Link Archer C64 WAP. On Volt 350Mbps, Talk Anytime Phone, x2 Mobile SIM only iPhones.

Hi John,

Many thanks for the feedback.

I dumped the logs below.

I'll take a look at the broadband quality monitor - though pinging my router every second seems quite a bit.

Cheers

Boyd

Downstream bonded channels

Channel

Frequency (Hz)

Power (dBmV)

SNR (dB)

Modulation

Channel ID

1

323000000

-1.4

40

256 qam

24

2

139000000

-1.7

38

256 qam

1

3

147000000

-2

40

256 qam

2

4

155000000

-2.4

40

256 qam

3

5

163000000

-3

38

256 qam

4

6

171000000

-3

40

256 qam

5

7

179000000

-2

40

256 qam

6

8

187000000

-2

40

256 qam

7

9

195000000

-1.9

40

256 qam

8

10

203000000

-1.9

40

256 qam

9

11

211000000

-1.7

40

256 qam

10

12

219000000

-1.7

40

256 qam

11

13

227000000

-1.7

40

256 qam

12

14

235000000

-1.7

40

256 qam

13

15

243000000

-2

40

256 qam

14

16

251000000

-1.9

40

256 qam

15

17

259000000

-1.7

40

256 qam

16

18

267000000

-1.5

40

256 qam

17

19

275000000

-1.5

40

256 qam

18

20

283000000

-1.4

40

256 qam

19

21

291000000

-1.2

40

256 qam

20

22

299000000

-1.2

40

256 qam

21

23

307000000

-1.2

40

256 qam

22

24

315000000

-1.2

40

256 qam

23

 

Downstream bonded channels

Channel

Locked Status

RxMER (dB)

Pre RS Errors

Post RS Errors

1

Locked

40.9

1611

0

2

Locked

38.9

70030600

68538155

3

Locked

40.9

14600017

7116674

4

Locked

40.3

72099508

12255372

5

Locked

38.9

73570419

64205820

6

Locked

40.3

1159148

3847450

7

Locked

40.3

68531165

21116550

8

Locked

40.3

32426633

693228

9

Locked

40.3

66460

9714

10

Locked

40.9

45594

7604

11

Locked

40.3

28081

446

12

Locked

40.3

22323

278

13

Locked

40.3

35981

5129

14

Locked

40.9

33233

6394

15

Locked

40.3

19213

121

16

Locked

40.9

8698

103

17

Locked

40.3

11901

81

18

Locked

40.9

21517

3280

19

Locked

40.3

20324

551

20

Locked

40.3

4221

8

21

Locked

40.9

3205

32

22

Locked

40.9

13069

266

23

Locked

40.3

10486

25

24

Locked

40.3

1691

0

 

Upstream bonded channels

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

15370000051512064 qam6
26030000051512064 qam5
33940000051512064 qam8
44619998951512064 qam7



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0020
2ATDMA0030
3ATDMA0010
4ATDMA0010
 

And the Network Log

Network Log

Time

Priority

Description

26/08/2021 14:34:21

Warning!

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

26/08/2021 14:33:14

notice

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

26/08/2021 14:00:57

Warning!

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

26/08/2021 13:59:47

notice

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

26/08/2021 13:59:14

Warning!

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

26/08/2021 12:12:20

Warning!

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

26/08/2021 12:12:19

Warning!

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

26/08/2021 10:57:59

Warning!

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

26/08/2021 10:57:59

Warning!

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

26/08/2021 10:22:2

Warning!

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

26/08/2021 10:22:2

Warning!

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

25/08/2021 22:48:0

Warning!

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

25/08/2021 22:45:7

Warning!

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

25/08/2021 20:57:19

Warning!

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

25/08/2021 20:56:15

Warning!

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

25/08/2021 20:44:57

Warning!

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

25/08/2021 20:44:54

Warning!

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

25/08/2021 18:13:42

Warning!

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

25/08/2021 16:38:30

critical

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

24/08/2021 22:06:58

Warning!

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

Tom_F
Forum Team (Retired)
Forum Team (Retired)

Hi bmo, thanks for posting.

 

Sorry to hear about the problems with your connection. I've taken a closer look into this today using your forum info and can see the upstream power levels are a bit on the high side and I feel this probably needs further attention.

 

If you get back to me via PM we'll be able to get that arranged for you.

 

Tom

Tom_F
Forum Team (Retired)
Forum Team (Retired)

Thanks for getting back to me @bmo. I've scheduled a visit from an engineer, you will find confirmation via your online account (virg.in/myVM) and can reschedule from there if needed.

 

Please keep us posted with how that goes, or let us know if we can help with anything else.

 

Tom 

Hi Tom_F

 

Thanks for scheduling that.

The engineer has been (he was early) and has quickly identified and fixed a poor conection at street level so hopefully that is the root cause. Logs seem OK so far (but a little early to tell)

Kudos to both you and the engineer that turned up.

Thanks

Boyd

Tom_F
Forum Team (Retired)
Forum Team (Retired)

Thanks for updating the thread bmo, glad we could help. Please don't hesitate to get back in touch if you have any more issues.

 

Tom