Menu
Reply
djwilliams100
  • 165
  • 1
  • 6
Dialled in
821 Views
Message 1 of 16
Flag for a moderator

T3 Timeouts (again)

Is someone able to look into what might be happening to cause packet loss throughout the day please?

chrome_PtbFhq0cXO.png

 

Network Log

Time

Priority

Description

17/09/2020 20:03:1

critical

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

17/09/2020 18:41:5

Error

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

17/09/2020 14:55:51

Error

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

17/09/2020 14:41:49

critical

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

16/09/2020 12:39:37

Error

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

12/09/2020 09:19:43

critical

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

11/09/2020 22:34:29

Error

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

11/09/2020 12:43:48

Error

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

11/09/2020 04:21:4

critical

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

11/09/2020 02:53:11

Error

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

11/09/2020 02:49:53

critical

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

10/09/2020 12:56:5

Warning!

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

08/09/2020 19:42:21

critical

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

08/09/2020 02:42:0

Error

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

06/09/2020 19:11:56

Error

DHCP RENEW sent - No response for IPv4;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;

01/09/2020 23:39:30

notice

SW download Successful - Via NMS

01/09/2020 23:37:36

notice

SW Download INIT - Via NMS

 

 

Downstream bonded channels

Channel

Frequency (Hz)

Power (dBmV)

SNR (dB)

Modulation

Channel ID

1

138750000

2.9

37

256 qam

1

2

146750000

2.7

37

256 qam

2

3

154750000

3

37

256 qam

3

4

162750000

2.7

37

256 qam

4

5

170750000

3.2

37

256 qam

5

6

178750000

3

37

256 qam

6

7

186750000

3.2

38

256 qam

7

8

194750000

2.7

38

256 qam

8

9

202750000

2.7

38

256 qam

9

10

210750000

2.2

37

256 qam

10

11

218750000

2

38

256 qam

11

12

226750000

1.5

37

256 qam

12

13

234750000

1.7

38

256 qam

13

14

242750000

2

38

256 qam

14

15

250750000

2.5

38

256 qam

15

16

258750000

2.9

38

256 qam

16

17

266750000

3.5

38

256 qam

17

18

274750000

4.1

38

256 qam

18

19

282750000

4.5

38

256 qam

19

20

290750000

4.8

38

256 qam

20

21

298750000

5.3

38

256 qam

21

22

306750000

6

40

256 qam

22

23

314750000

6.5

40

256 qam

23

24

322750000

7

40

256 qam

24




Downstream bonded channels

Channel

Locked Status

RxMER (dB)

Pre RS Errors

Post RS Errors

1

Locked

37.3

21887

51

2

Locked

37.3

8817

1

3

Locked

37.6

5972

15

4

Locked

37.6

15823

13

5

Locked

37.3

7405

45

6

Locked

37.6

1896

13

7

Locked

38.9

7208

2401

8

Locked

38.9

25388

14

9

Locked

38.6

12623

0

10

Locked

37.3

3767

0

11

Locked

38.6

11825

0

12

Locked

37.3

20962

13

13

Locked

38.6

41482

0

14

Locked

38.9

62114

2

15

Locked

38.9

79360

2

16

Locked

38.6

61023

3

17

Locked

38.9

34053

0

18

Locked

38.9

5681

2

19

Locked

38.9

1275

0

20

Locked

38.9

710

0

21

Locked

38.6

898

15

22

Locked

40.3

630

12

23

Locked

40.3

670

12

24

Locked

40.3

611

13

 

Upstream bonded channels

Channel

Channel Type

T1 Timeouts

T2 Timeouts

T3 Timeouts

T4 Timeouts

1

ATDMA

0

0

5

0

2

ATDMA

0

0

1

0

3

ATDMA

0

0

0

0

4

ATDMA

0

0

18

0

 

0 Kudos
Reply
Martin_N
  • 5.6K
  • 234
  • 322
Forum Team
Forum Team
694 Views
Message 2 of 16
Flag for a moderator

Re: T3 Timeouts (again)

Hi djwilliams100,

 

Thank you for your post and welcome to the community. 

 

I'm very sorry to hear about the issue you're having. 

 

I have taken a look on our side and it is showing you have an SNR (Sound to Noise Ratio) fault reported in your area. 

 

The fault reference for this is: F008388487.

 

The current estimated fix date is: 30 SEP 2020 10:50

 

^Martin

0 Kudos
Reply
djwilliams100
  • 165
  • 1
  • 6
Dialled in
684 Views
Message 3 of 16
Flag for a moderator

Re: T3 Timeouts (again)

Thank you. Ill keep an eye on it. 

0 Kudos
Reply
djwilliams100
  • 165
  • 1
  • 6
Dialled in
568 Views
Message 4 of 16
Flag for a moderator

Re: T3 Timeouts (again)

Any update please?

Still seeing multiple drops each day

chrome_R8yAwCtOAV.png

0 Kudos
Reply
Emily_G
  • 4.82K
  • 209
  • 286
Forum Team (Retired)
Forum Team (Retired)
519 Views
Message 5 of 16
Flag for a moderator

Re: T3 Timeouts (again)

Thanks for the post, we can see there's a known area fault relating to SNR, I'll pop the information on this below for you.

 

Reference: F008388487

Estimated repair time: 12 OCT 2020 15:00

 

Thanks, Emily.

0 Kudos
Reply
djwilliams100
  • 165
  • 1
  • 6
Dialled in
470 Views
Message 6 of 16
Flag for a moderator

Re: T3 Timeouts (again)

Hi Emily

Any update again please? . A day after this was supposed to be fixed, the internet was unusable for me last night

djwilliams100_0-1602662086735.png

 

0 Kudos
Reply
djwilliams100
  • 165
  • 1
  • 6
Dialled in
441 Views
Message 7 of 16
Flag for a moderator

Re: T3 Timeouts (again)

Hello?

Any update please? Still seeing connection issues after i was advised the issue was going to be fixed

djwilliams100_0-1603193809707.png

 

0 Kudos
Reply
Emily_G
  • 4.82K
  • 209
  • 286
Forum Team (Retired)
Forum Team (Retired)
415 Views
Message 8 of 16
Flag for a moderator

Re: T3 Timeouts (again)

Thanks for the post Djwilliams100.

 

We can see there's currently an SNR area fault which may be affecting your services, I'll pop the information on this for you below. 

 

Reference: F008388487

Estimated repair time: 27 OCT 2020 15:00

 

Thanks, Emily

0 Kudos
Reply
djwilliams100
  • 165
  • 1
  • 6
Dialled in
403 Views
Message 9 of 16
Flag for a moderator

Re: T3 Timeouts (again)

Morning Emily

Is there any update on when this be fixed please? Still seeing packet loss

djwilliams100_0-1604057799066.png

 

Time Priority Description

29/10/2020 21:33:51criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/10/2020 15:39:54ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/10/2020 05:11:39criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
Paul_DN
  • 6.35K
  • 363
  • 659
Forum Team
Forum Team
356 Views
Message 10 of 16
Flag for a moderator

Re: T3 Timeouts (again)

Hi djwilliams100,

 

Thank you for reaching out to us in our community and a warm welcome to you, I am sorry to hear you are experiencing time outs, I have been unable to locate your account.

 

So I can help further I will invite you into a private chat, please click on the purple envelope to accept.

 

Regards

 

Paul.

0 Kudos
Reply