Menu
Reply
ClMcGee
  • 44
  • 0
  • 0
Tuning in
369 Views
Message 41 of 61
Flag for a moderator

Re: RCS Partial Service/No Ranging Response received

Today was totally unbearable to work overall.

ClMcGee_0-1654801380980.png

Connection gets worse and worse

0 Kudos
Reply
ClMcGee
  • 44
  • 0
  • 0
Tuning in
353 Views
Message 42 of 61
Flag for a moderator

Re: RCS Partial Service/No Ranging Response received

That is just ridiculous, jumping up and down like crazy. Also for some reason service check still reminds me of maintenance which should've been done more than 12 hours ago.

Upstream bonded channels

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

14619998638.5512064 qam3
23940002135.3512064 qam4
35369997445.3512064 qam2
46030000038512064 qam1



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0030
3ATDMA0010
4ATDMA0000

 

0 Kudos
Reply
ClMcGee
  • 44
  • 0
  • 0
Tuning in
339 Views
Message 43 of 61
Flag for a moderator

Re: RCS Partial Service/No Ranging Response received

@Carley_S

So as you can see, nothing has changed unless worsened

0 Kudos
Reply
ClMcGee
  • 44
  • 0
  • 0
Tuning in
324 Views
Message 44 of 61
Flag for a moderator

Re: RCS Partial Service/No Ranging Response received

So for now I've again booked a tech visit on closest date possible (got redirected there after service check). This is my 4th tech visit, hope he won't just ignore my attempts to show logs/data that could indicate the possible problems like the last tech guy.

ClMcGee_0-1654856946054.png

 

0 Kudos
Reply
ClMcGee
  • 44
  • 0
  • 0
Tuning in
298 Views
Message 45 of 61
Flag for a moderator

Re: RCS Partial Service/No Ranging Response received

And whilst waiting for tech, 12th of June and this again

ClMcGee_0-1655031627799.png

 

0 Kudos
Reply
ClMcGee
  • 44
  • 0
  • 0
Tuning in
295 Views
Message 46 of 61
Flag for a moderator

Re: RCS Partial Service/No Ranging Response received

Also my today's error lags is very different to what I see usually, does this mean that Hub is dying?

Network Log

Time Priority Description

12/06/2022 10:37:50noticeNOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;X;CM-QOS=1.1;CM-VER=3.0;
12/06/2022 10:37:36criticalNo Ranging Response received - T3 time-out;X;CM-QOS=1.1;CM-VER=3.0;
12/06/2022 10:37:35criticalUnicast Ranging Received Abort Response - initializing MAC;X;CM-QOS=1.1;CM-VER=3.0;
12/06/2022 10:37:31noticeNOTICE ATOM is restarted due to RPC timeout as part of Self Healing Mechanism;X;CM-QOS=1.1;CM-VER=3.0;
12/06/2022 10:35:56criticalNo Ranging Response received - T3 time-out;X;CM-QOS=1.1;CM-VER=3.0;
12/06/2022 10:35:56criticalUnicast Ranging Received Abort Response - initializing MAC;X;CM-QOS=1.1;CM-VER=3.0;
12/06/2022 10:34:36criticalNo Ranging Response received - T3 time-out;X;CM-QOS=1.1;CM-VER=3.0;
12/06/2022 10:34:36criticalUnicast Ranging Received Abort Response - initializing MAC;X;CM-QOS=1.1;CM-VER=3.0;
12/06/2022 10:33:16criticalNo Ranging Response received - T3 time-out;x;CM-QOS=1.1;CM-VER=3.0;
12/06/2022 10:33:16criticalUnicast Ranging Received Abort Response - initializing MAC;x;CM-QOS=1.1;CM-VER=3.0;
12/06/2022 10:31:56criticalNo Ranging Response received - T3 time-out;x;CM-QOS=1.1;CM-VER=3.0;
12/06/2022 10:31:56criticalUnicast Ranging Received Abort Response - initializing MAC;X;CM-QOS=1.1;CM-VER=3.0;
12/06/2022 10:30:36criticalNo Ranging Response received - T3 time-out;X;CM-QOS=1.1;CM-VER=3.0;
12/06/2022 10:30:36criticalUnicast Ranging Received Abort Response - initializing MAC;X;CM-QOS=1.1;CM-VER=3.0;
12/06/2022 10:29:16criticalNo Ranging Response received - T3 time-out;x;CM-QOS=1.1;CM-VER=3.0;
12/06/2022 10:29:16criticalUnicast Ranging Received Abort Response - initializing MAC;x;CM-QOS=1.1;CM-VER=3.0;
12/06/2022 10:27:57criticalNo Ranging Response received - T3 time-out;x;CM-QOS=1.1;CM-VER=3.0;
12/06/2022 10:27:56criticalUnicast Ranging Received Abort Response - initializing MAC;x;CM-QOS=1.1;CM-VER=3.0;
12/06/2022 10:27:20criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;x;CM-QOS=1.1;CM-VER=3.0;
12/06/2022 10:27:20criticalRanging Request Retries exhausted;xCM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
Natalie_L
  • 6.6K
  • 238
  • 510
Forum Team
Forum Team
290 Views
Message 47 of 61
Flag for a moderator

Re: RCS Partial Service/No Ranging Response received

Hi CIMcGee, 

Thank you for getting back in touch with us here on the Community.

I am sorry to hear the problem is ongoing but I am happy you have been able to schedule the visit with the team.

Please do let us know how it all goes and if you require any further assistance. 

Thank you,

 

 

Nat
0 Kudos
Reply
ClMcGee
  • 44
  • 0
  • 0
Tuning in
285 Views
Message 48 of 61
Flag for a moderator

Re: RCS Partial Service/No Ranging Response received

Thanks for response. Will again post here after the tech visit and/or if anyhting like these log changes occurs 

0 Kudos
Reply
ClMcGee
  • 44
  • 0
  • 0
Tuning in
272 Views
Message 49 of 61
Flag for a moderator

Re: RCS Partial Service/No Ranging Response received

So just wanted to share that graph, totally not the worst, but I've never been experiencing such a heavy and frequent packet loss in my life.

ClMcGee_1-1655074081043.png

this huge red line was when hub probably rebooted itself due to "kernel panic"

0 Kudos
Reply
ClMcGee
  • 44
  • 0
  • 0
Tuning in
250 Views
Message 50 of 61
Flag for a moderator

Re: RCS Partial Service/No Ranging Response received

So the tech guy was superb this time, amazing service. However that "ghost" of intermittent signal was not present at that time, thus he decided to book me a cable change (the one that goes from street cab to our property). Will have to wait for it again.

 

0 Kudos
Reply