U

Visitor

 • 

5 Messages

Sun, Jul 17, 2022 5:49 AM

Internet slow down (seems like a common issue)

Saw another user with a similar issue. I've had no issues for the past few years running a NETGEAR Gateway C7000v2. Now my internet speeds dropping to 30mbps or less, and sometimes I lose internet all together. Just started happening in the last couple days.

Posting my Event Log and Cable connects...

Time

Priority

Description

2022-7-16, 23:13:34

Warning (5) 

MDD message timeout;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 23:13:21

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 23:08:47

Warning (5) 

MDD message timeout;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 23:08:45

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 23:07:30

Warning (5) 

MDD message timeout;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 23:07:17

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 23:02:42

Warning (5) 

MDD message timeout;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 23:02:29

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 23:02:26

Warning (5) 

MDD message timeout;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 23:02:15

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 23:01:12

Warning (5) 

MDD message timeout;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 23:01:05

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 23:01:04

Warning (5) 

MDD message timeout;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 23:00:35

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 23:00:26

Warning (5) 

MDD message timeout;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 23:00:21

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 22:58:46

Warning (5) 

MDD message timeout;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 22:58:30

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 22:58:02

Warning (5) 

MDD message timeout;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 22:57:58

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 22:57:58

Warning (5) 

MDD message timeout;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 22:57:52

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 22:57:48

Warning (5) 

MDD message timeout;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 22:57:47

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 22:57:10

Warning (5) 

MDD message timeout;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 22:56:37

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 22:54:45

Warning (5) 

MDD message timeout;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 22:54:44

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 22:53:16

Warning (5) 

MDD message timeout;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 22:52:33

Critical (3) 

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 22:52:06

Warning (5) 

MDD message timeout;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 22:51:28

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 22:51:04

Critical (3) 

SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 22:50:43

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 22:50:35

Critical (3) 

No Ranging Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-16, 22:50:14

Notice (6) 

Honoring MDD; IP provisioning mode = IPv6

2022-7-16, 22:50:04

Critical (3) 

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.0;CM-VER=3.0;

2022-7-16, 22:50:03

Critical (3) 

No UCDs Received - Timeout;;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.0;CM-VER=3.0;

2022-7-16, 22:49:53

Warning (5) 

Lost MDD Timeout;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.0;CM-VER=3.0;

2022-7-16, 22:49:43

Critical (3) 

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.0;CM-VER=3.0;


Procedure

Status

Comment

Acquire Downstream Channel

567000000 Hz

Locked

Connectivity State

OK

Operational

Boot State

OK

Operational

Security

Enabled

BPI+

IP Provisioning Mode

Honor MDD

honorMdd(4)

 

Downstream Bonded Channels


Channel

Lock Status

Modulation

Channel ID

Frequency

Power

SNR

Correctables

Uncorrectables

1

Locked

QAM256

28

567000000 Hz

-3.4 dBmV

28.7 dB

41336427

6125522

2

Locked

QAM256

21

525000000 Hz

-3.1 dBmV

30.2 dB

1701

0

3

Locked

QAM256

22

531000000 Hz

-3.3 dBmV

37.1 dB

0

0

4

Locked

QAM256

23

537000000 Hz

-3.5 dBmV

40 dB

0

0

5

Locked

QAM256

24

543000000 Hz

-3.5 dBmV

40.2 dB

0

0

6

Locked

QAM256

25

549000000 Hz

-3.5 dBmV

40.3 dB

0

0

7

Locked

QAM256

26

555000000 Hz

-3.5 dBmV

40.4 dB

0

0

8

Locked

QAM256

27

561000000 Hz

-3.5 dBmV

35.6 dB

0

0

9

Locked

QAM256

29

573000000 Hz

-3.3 dBmV

27.1 dB

14052459

9394828

10

Locked

QAM256

30

579000000 Hz

-3.3 dBmV

26.1 dB

529390

331569

11

Locked

QAM256

31

585000000 Hz

-3.4 dBmV

37.6 dB

5

0

12

Locked

QAM256

32

591000000 Hz

-3.3 dBmV

37.1 dB

0

0

13

Locked

QAM256

33

597000000 Hz

-3.3 dBmV

38.1 dB

0

0

14

Locked

QAM256

34

603000000 Hz

-3.3 dBmV

38.4 dB

0

0

15

Locked

QAM256

35

609000000 Hz

-3.2 dBmV

40.1 dB

0

0

16

Locked

QAM256

36

615000000 Hz

-3.3 dBmV

40.2 dB

0

0

17

Locked

QAM256

37

621000000 Hz

-3.5 dBmV

31.9 dB

227

12

18

Locked

QAM256

38

627000000 Hz

-3.8 dBmV

25.7 dB

431

2495

19

Locked

QAM256

39

633000000 Hz

-4.1 dBmV

26.5 dB

436

1698

20

Locked

QAM256

40

639000000 Hz

-4.1 dBmV

28.2 dB

549

585

21

Locked

QAM256

41

645000000 Hz

-4.1 dBmV

40.8 dB

0

0

22

Locked

QAM256

42

651000000 Hz

-4.1 dBmV

40.4 dB

0

0

23

Locked

QAM256

43

657000000 Hz

-4.3 dBmV

40.2 dB

0

0

24

Locked

QAM256

44

663000000 Hz

-4.4 dBmV

39.8 dB

0

0

 

Upstream Bonded Channels


Channel

Lock Status

US Channel Type

Channel ID

Symbol Rate

Frequency

Power

1

Locked

ATDMA

1

5120 Ksym/sec

35600000 Hz

43.8 dBmV

2

Locked

ATDMA

2

5120 Ksym/sec

29200000 Hz

43.9 dBmV

3

Locked

ATDMA

3

5120 Ksym/sec

22800000 Hz

43.4 dBmV

4

Locked

ATDMA

4

5120 Ksym/sec

16400000 Hz

43.5 dBmV

5

Locked

ATDMA

5

2560 Ksym/sec

40400000 Hz

45.7 dBmV

6

Locked

ATDMA

6

2560 Ksym/sec

10400000 Hz

43.5 dBmV

7

Not Locked

Unknown

0

0 Ksym/sec

0 Hz

0.0 dBmV

8

Not Locked

Unknown

0

0 Ksym/sec

0 Hz

0.0 dBmV

Accepted Solution

EG

Expert

 • 

95.7K Messages

2 m ago

The SNR is too low / out of spec on many of the downstream channels. Seems that there is some extraneous noise leaking into the line(s) somewhere. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.

In an effort to try to obtain better connectivity / more wiggle room, check to see if there are there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1000 MHz, bi-directional, and no gold colored garbage from Radio Shack, Home Depot, Target, etc. Splitters should be swapped with known to be good / new ones to test.

Also check the coax cable for any damage such as cuts, nicks, kinks, sharp bends, etc.

If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two-way splitter connected directly off of the drop from the street / pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.


Good luck with it !

Visitor

 • 

5 Messages

2 m ago

Okay thanks! I replaced the coax cable. I have no splitters, but there was a SVCS12 (in-line cable simulator?) between the coax cable and router. I also removed that. Seems to be perfect now. 

EG

Expert

 • 

95.7K Messages

2 m ago

@user_ed9708 

For curiosity. Please post back with what the signal stats look like now.

Visitor

 • 

5 Messages

2 m ago

Frequency start Value

This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.


Starting Frequency

 

Startup Procedure


Procedure

Status

Comment

Acquire Downstream Channel

567000000 Hz

Locked

Connectivity State

OK

Operational

Boot State

OK

Operational

Security

Enabled

BPI+

IP Provisioning Mode

Honor MDD

honorMdd(4)

 

Downstream Bonded Channels


Channel

Lock Status

Modulation

Channel ID

Frequency

Power

SNR

Correctables

Uncorrectables

1

Locked

QAM256

28

567000000 Hz

4.4 dBmV

41.8 dB

0

0

2

Locked

QAM256

21

525000000 Hz

4.5 dBmV

40.3 dB

0

0

3

Locked

QAM256

22

531000000 Hz

4.4 dBmV

40.6 dB

0

0

4

Locked

QAM256

23

537000000 Hz

4.2 dBmV

40.6 dB

0

0

5

Locked

QAM256

24

543000000 Hz

4.1 dBmV

41 dB

0

0

6

Locked

QAM256

25

549000000 Hz

4.1 dBmV

41.2 dB

0

0

7

Locked

QAM256

26

555000000 Hz

4.1 dBmV

41.5 dB

0

0

8

Locked

QAM256

27

561000000 Hz

4.2 dBmV

40.2 dB

0

0

9

Locked

QAM256

29

573000000 Hz

4.8 dBmV

41.7 dB

0

0

10

Locked

QAM256

30

579000000 Hz

5 dBmV

41.7 dB

0

0

11

Locked

QAM256

31

585000000 Hz

5 dBmV

41.5 dB

6

0

12

Locked

QAM256

32

591000000 Hz

5 dBmV

41.2 dB

0

0

13

Locked

QAM256

33

597000000 Hz

5 dBmV

41.1 dB

0

0

14

Locked

QAM256

34

603000000 Hz

4.9 dBmV

41 dB

0

0

15

Locked

QAM256

35

609000000 Hz

5 dBmV

41.2 dB

0

0

16

Locked

QAM256

36

615000000 Hz

5 dBmV

41.4 dB

0

0

17

Locked

QAM256

37

621000000 Hz

5 dBmV

42 dB

0

0

18

Locked

QAM256

38

627000000 Hz

5 dBmV

42.3 dB

0

0

19

Locked

QAM256

39

633000000 Hz

5 dBmV

42.5 dB

0

0

20

Locked

QAM256

40

639000000 Hz

5 dBmV

41.9 dB

0

0

21

Locked

QAM256

41

645000000 Hz

4.9 dBmV

42.5 dB

0

0

22

Locked

QAM256

42

651000000 Hz

4.9 dBmV

42 dB

0

0

23

Locked

QAM256

43

657000000 Hz

4.9 dBmV

42.5 dB

0

0

24

Locked

QAM256

44

663000000 Hz

4.9 dBmV

41.9 dB

0

0

 

Upstream Bonded Channels


Channel

Lock Status

US Channel Type

Channel ID

Symbol Rate

Frequency

Power

1

Locked

ATDMA

6

2560 Ksym/sec

10400000 Hz

41.8 dBmV

2

Locked

ATDMA

2

5120 Ksym/sec

29200000 Hz

42.7 dBmV

3

Locked

ATDMA

3

5120 Ksym/sec

22800000 Hz

42.4 dBmV

4

Locked

ATDMA

4

5120 Ksym/sec

16400000 Hz

42.1 dBmV

5

Locked

ATDMA

5

2560 Ksym/sec

40400000 Hz

44.4 dBmV

6

Locked

ATDMA

1

5120 Ksym/sec

35600000 Hz

42.9 dBmV

7

Not Locked

Unknown

0

0 Ksym/sec

0 Hz

0.0 dBmV

8

Not Locked

Unknown

0

0 Ksym/sec

0 Hz

0.0 dBmV

Time

Priority

Description

1970-1-1, 00:00:47

Notice (6) 

Honoring MDD; IP provisioning mode = IPv6

1970-1-1, 00:00:41

Notice (6) 

WiFi Interface [wl1] set to Channel 153 (Side-Band Channel:N/A) - Reason:INIT

1970-1-1, 00:00:41

Notice (6) 

WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INIT

2022-7-17, 17:44:47

Critical (3) 

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.0;CM-VER=3.0;

2022-7-17, 17:44:46

Critical (3) 

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.0;CM-VER=3.0;

2022-7-17, 17:44:40

Critical (3) 

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 17:44:38

Critical (3) 

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 17:44:37

Critical (3) 

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 17:44:37

Critical (3) 

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 17:44:35

Critical (3) 

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 17:44:35

Critical (3) 

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 17:44:34

Critical (3) 

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 17:43:48

Critical (3) 

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 17:43:42

Critical (3) 

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 17:43:38

Critical (3) 

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 17:34:13

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 16:23:36

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

1970-1-1, 00:00:39

Critical (3) 

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.0;CM-VER=3.0;

2022-7-17, 08:21:50

Critical (3) 

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 08:21:44

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 08:21:31

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 08:03:07

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 07:29:26

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 07:12:23

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 07:11:00

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 07:10:01

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 07:09:36

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 07:09:13

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 07:08:24

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 07:05:41

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 07:04:18

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 07:03:27

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 06:36:57

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 06:28:26

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 06:18:56

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 06:13:54

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 06:11:35

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 06:09:17

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 05:50:21

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

2022-7-17, 05:47:47

Critical (3) 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[redacted];CMTS-MAC=[redacted];CM-QOS=1.1;CM-VER=3.0;

EG

Expert

 • 

95.7K Messages

2 m ago

Nice ! Thanks for posting back !

forum icon

New to the Community?

Start Here