Community Forum

Strange random outages. Possible comm issue with CMTS end. Or defective device?

Regular Visitor

Strange random outages. Possible comm issue with CMTS end. Or defective device?

Hello,

 

I've got a few sets of logs to share, as I'm unsure of which one will be of use.  

 

To begin, I am using a Netgear C7100V Modem/Router.  We have a Home VoIP system, and a mesh wifi system connected to it.  

Periodically, the internet will go down, the router will NOT assign even an internal IP addresses(even when connected directly via Ethernet), and the console is not reachable even when connected to the wireless or Ethernet connection.  Devices that connect are just given an IP assignment error. 

 

Strangely, on the Comcast mobile application it also shows our modem as being disconnected and not active.  Occassionally a temporary fix has been to just reboot the device from this mobile application, and upon reboot it will work fine, but lately it seems to be getting fixed from this less and less.  Formerly, this issue was arising every week or so, but it now seems to be more frequent. *** And just realized that it is also fairly strange that the device can receive remote commands when it is showing as disconnected. Fancy!

 

The only way that has worked consistently is to call Comcast support, notify them of the issue, and magically the internet comes back up usually a few minutes after contacting them.  It sounds very similar to a lease that is not being assigned to our device for whatever reason.

 

I know from looking up troubleshooting articles that this device has several MAC addresses, but I would think that if Comcast had the wrong MAC address for the device, it wouldn't function at all, not just have intermittent issues.

 

The other alternative is a defective device, and hopefully from this post I can get some guidance on how to determine if that is the case.  

 

The final possibility is an issue with the communication between the CMTS switch and our device, which I also am only vaguely aware of how those devices function, and hope someone with the proper knowledge can check these logs to confirm if that is the case as well.

 

I am unable to attach logs so I'll be pasting several sets of logs below.  I will continue to update this post as logs appear.

 

Time

Text

EndpointName

2019-04-21 19:42:06

INFO: Endpt 1 on-hook; cmgr event OPER_NOK_FORBIDDEN

mb0b98ad85e59.chic7.il.comcast.net/21.233.8.35

2019-04-21 19:42:06

Registration failed for user <B0B98AD85E59002@ims.comcast.net>; reason<port shutdown 403 FORBIDDEN>

mb0b98ad85e59.chic7.il.comcast.net/21.233.8.35

2019-04-21 19:42:05

INFO: Endpt 1 on-hook; cmgr event TARGETS_UPDATE

mb0b98ad85e59.chic7.il.comcast.net/21.233.8.35

2019-04-21 19:41:18

INFO: Endpt 0 on-hook; cmgr event MWI_ON

mb0b98ad85e59.chic7.il.comcast.net/21.233.8.35

2019-04-21 19:41:18

INFO: Endpt 0 on-hook; cmgr event OPER_OK

mb0b98ad85e59.chic7.il.comcast.net/21.233.8.35

2019-04-21 19:41:18

INFO: Endpt 0 on-hook; cmgr event TARGETS_UPDATE

mb0b98ad85e59.chic7.il.comcast.net/21.233.8.35

2019-04-21 19:41:17

INFO: Endpt 0 on-hook; cmgr event TARGETS_UPDATE

mb0b98ad85e59.chic7.il.comcast.net/21.233.8.35

2019-04-21 19:41:17

INFO: Endpt 0 on-hook; cmgr event TARGETS_UPDATE

mb0b98ad85e59.chic7.il.comcast.net/21.233.8.35

2019-04-21 19:41:17

INFO: Endpt 0 on-hook; cmgr event TARGETS_UPDATE

mb0b98ad85e59.chic7.il.comcast.net/21.233.8.35

2019-04-21 19:41:17

INFO: Endpt 0 on-hook; cmgr event TARGETS_UPDATE

mb0b98ad85e59.chic7.il.comcast.net/21.233.8.35

2019-04-21 19:40:39

MEM-CONN-ERROR;No IP address

mb0b98ad85e59.chic7.il.comcast.net/21.233.8.35

2019-04-21 19:40:38

Provisioning Complete

mb0b98ad85e59.chic7.il.comcast.net/21.233.8.35

 

** Clearly, the registration failed in this log is the one I'm thinking could be the issue.  Unsure though.  This is the MTA Event Log.

 

Now, this next one is the Event Log.  This is where I feel that it clearly shows the CMTS is having issues communicating with the device, but it’s beyond my knowledge as to what is really going on here.

 

2019-04-24, 10:04:14.0

Warning (5)

MDD message timeout;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:01:5c:6c:74:4b;CM-QOS=1.1;CM-VER=3.0;

2019-04-24, 10:02:35.0

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:01:5c:6c:74:4b;CM-QOS=1.1;CM-VER=3.0;

2019-04-24, 09:59:35.0

Warning (5)

MDD message timeout;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:01:5c:6c:74:4b;CM-QOS=1.1;CM-VER=3.0;

2019-04-24, 09:59:32.0

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:01:5c:6c:74:4b;CM-QOS=1.1;CM-VER=3.0;

2019-04-24, 09:59:31.0

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:01:5c:6c:74:4b;CM-QOS=1.1;CM-VER=3.0;

2019-04-24, 09:57:10.0

Warning (5)

MDD message timeout;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:01:5c:6c:74:4b;CM-QOS=1.1;CM-VER=3.0;

2019-04-24, 09:57:06.0

Critical (3)

SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:01:5c:6c:74:4b;CM-QOS=1.1;CM-VER=3.0;

2019-04-23, 14:03:38.0

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:01:5c:6c:74:4b;CM-QOS=1.1;CM-VER=3.0;

2019-04-23, 13:22:00.0

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

2019-04-23, 13:21:52.0

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:01:5c:6c:74:4b;CM-QOS=1.1;CM-VER=3.0;

2019-04-23, 13:21:52.0

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:01:5c:6c:74:4b;CM-QOS=1.1;CM-VER=3.0;

2019-04-23, 13:21:14.0

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:01:5c:6c:74:4b;CM-QOS=1.1;CM-VER=3.0;

2019-04-23, 13:21:13.0

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:01:5c:6c:74:4b;CM-QOS=1.1;CM-VER=3.0;

2019-04-23, 13:20:50.0

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:01:5c:6c:74:4b;CM-QOS=1.1;CM-VER=3.0;

Time Not Established

Notice (6)

Honoring MDD; IP provisioning mode = IPv6

Time Not Established

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:01:5c:6c:74:4b;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:01:5c:6c:74:4b;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:b9:8a:d8:5e:58;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Expert

Re: Strange random outages. Possible comm issue with CMTS end. Or defective device?

Please also post the *Downstream Power Level*, the *Upstream Power Level*, and the *SNR* (Signal to Noise Ratio) numbers.




I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Regular Visitor

Re: Strange random outages. Possible comm issue with CMTS end. Or defective device?

Thanks for the quick reply.  Just found the info you requested, just giving you the whole page from cable connection.

 

Wouldn't it be a perfect world if adjusting this frequency start value turned out to be the fix for this?

 

Probably better to not get my hopes up.  Especially with that mighty large amount of uncorrectables.

 

I'm way past my pay grade on this but is that the docsis packet inspection picking up that many corrupt beyond recovery? 

 

Scratching my head a bit on this one.  Maybe some interference? Could a Moca filter be the culprit? We are using one currently.

 

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

<tabindex=-1>Startup Procedure</tabindex=-1>
Procedure Status Comment
Acquire Downstream Channel 651000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK ------------
Security Enable BPI+

<tabindex=-1>Downstream Bonded Channels</tabindex=-1>
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 28 651000000 Hz 7.8 dBmV 38.5 dB 293 353
2 Locked QAM256 1 483000000 Hz 5.4 dBmV 37.5 dB 70 329
3 Locked QAM256 2 489000000 Hz 5.7 dBmV 37.6 dB 167 327
4 Locked QAM256 3 495000000 Hz 5.6 dBmV 37.5 dB 1 0
5 Locked QAM256 4 507000000 Hz 5.7 dBmV 35.4 dB 1 0
6 Locked QAM256 5 513000000 Hz 5.5 dBmV 37.6 dB 185 343
7 Locked QAM256 6 519000000 Hz 5.4 dBmV 37.6 dB 105 337
8 Locked QAM256 7 525000000 Hz 5.2 dBmV 37.5 dB 3 0
9 Locked QAM256 8 531000000 Hz 5.2 dBmV 37.6 dB 2 0
10 Locked QAM256 12 555000000 Hz 5.5 dBmV 37.6 dB 3207 6979
11 Locked QAM256 13 561000000 Hz 5.5 dBmV 37.3 dB 3016 7918
12 Locked QAM256 15 573000000 Hz 6.1 dBmV 38.0 dB 6900 24488
13 Locked QAM256 16 579000000 Hz 6.1 dBmV 38.0 dB 22 0
14 Locked QAM256 17 585000000 Hz 6.4 dBmV 38.1 dB 169 322
15 Locked QAM256 18 591000000 Hz 6.2 dBmV 37.9 dB 154 339
16 Locked QAM256 19 597000000 Hz 6.7 dBmV 38.2 dB 2126 4575
17 Locked QAM256 20 603000000 Hz 6.3 dBmV 38.3 dB 0 0
18 Locked QAM256 22 615000000 Hz 6.3 dBmV 38.2 dB 0 0
19 Locked QAM256 23 621000000 Hz 6.6 dBmV 38.6 dB 0 0
20 Locked QAM256 26 639000000 Hz 7.0 dBmV 38.5 dB 0 0
21 Locked QAM256 27 645000000 Hz 7.3 dBmV 38.6 dB 0 0
22 Locked QAM256 29 657000000 Hz 7.8 dBmV 39.0 dB 0 0
23 Locked QAM256 30 663000000 Hz 7.7 dBmV 39.0 dB 0 0
24 Locked QAM256 31 669000000 Hz 8.1 dBmV 39.0 dB 0 0

<tabindex=-1>Upstream Bonded Channels</tabindex=-1>
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 1 5120 Ksym/sec 35800000 Hz 46.8 dBmV
2 Locked ATDMA 2 5120 Ksym/sec 29400000 Hz 46.5 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 23000000 Hz 46.5 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 16600000 Hz 46.5 dBmV
5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 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
Regular Visitor

Re: Strange random outages. Possible comm issue with CMTS end. Or defective device?

Bump

 

Just had it happen again, have some more logs for you.  Just noticed a considerable increase in the downstream power levels from my previous post.

 

Starting Frequency

 
 

Startup Procedure

Procedure

Status

Comment

Acquire Downstream Channel

651000000 Hz

Locked

Connectivity State

OK

Operational

Boot State

OK

Operational

Configuration File

OK

------------

Security

Enable

BPI+

 
   

Downstream Bonded Channels

 

Channel

Lock Status

Modulation

Channel ID

Frequency

Power

SNR

Correctables

Uncorrectables

1

Locked

QAM256

28

651000000 Hz

10.0 dBmV

38.7 dB

595

353

2

Locked

QAM256

1

483000000 Hz

7.6 dBmV

37.7 dB

70

329

3

Locked

QAM256

2

489000000 Hz

7.9 dBmV

37.9 dB

167

327

4

Locked

QAM256

3

495000000 Hz

7.9 dBmV

37.9 dB

7

0

5

Locked

QAM256

4

507000000 Hz

8.0 dBmV

36.1 dB

7

0

6

Locked

QAM256

5

513000000 Hz

7.9 dBmV

38.0 dB

186

343

7

Locked

QAM256

6

519000000 Hz

7.7 dBmV

38.0 dB

110

337

8

Locked

QAM256

7

525000000 Hz

7.5 dBmV

37.9 dB

8

0

9

Locked

QAM256

8

531000000 Hz

7.5 dBmV

37.9 dB

7

0

10

Locked

QAM256

12

555000000 Hz

7.9 dBmV

38.0 dB

3219

6979

11

Locked

QAM256

13

561000000 Hz

7.9 dBmV

37.7 dB

3035

7918

12

Locked

QAM256

15

573000000 Hz

8.4 dBmV

38.3 dB

6918

24488

13

Locked

QAM256

16

579000000 Hz

8.4 dBmV

38.3 dB

47

0

14

Locked

QAM256

17

585000000 Hz

8.6 dBmV

38.4 dB

208

322

15

Locked

QAM256

18

591000000 Hz

8.4 dBmV

38.3 dB

222

339

16

Locked

QAM256

19

597000000 Hz

9.0 dBmV

38.4 dB

2199

4575

17

Locked

QAM256

20

603000000 Hz

8.5 dBmV

38.6 dB

0

0

18

Locked

QAM256

22

615000000 Hz

8.6 dBmV

38.6 dB

0

0

19

Locked

QAM256

23

621000000 Hz

8.9 dBmV

39.0 dB

0

0

20

Locked

QAM256

26

639000000 Hz

9.2 dBmV

38.7 dB

1

0

21

Locked

QAM256

27

645000000 Hz

9.5 dBmV

39.0 dB

0

0

22

Locked

QAM256

29

657000000 Hz

9.8 dBmV

39.1 dB

0

0

23

Locked

QAM256

30

663000000 Hz

9.9 dBmV

39.3 dB

0

0

24

Locked

QAM256

31

669000000 Hz

10.1 dBmV

39.4 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

35800000 Hz

44.8 dBmV

2

Locked

ATDMA

2

5120 Ksym/sec

29400000 Hz

44.8 dBmV

3

Locked

ATDMA

3

5120 Ksym/sec

23000000 Hz

44.5 dBmV

4

Locked

ATDMA

4

5120 Ksym/sec

16600000 Hz

44.8 dBmV

5

Not Locked

Unknown

0

0 Ksym/sec

0 Hz

0.0 dBmV

6

Not Locked

Unknown

0

0 Ksym/sec

0 Hz

0.0 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

 
   

Current System Time: Sat Apr 27 13:48:27 2019 

 

System Up Time: 96:22:58

 

 

@EG 

 

Also, another most likely? unrelated issue, but concerning all the same.

 

[Firewall Up ]

1

Sat Apr 27 13:58:57 2019

---.---.---.---:---

---.---.---.---:---

[Internet connected ]

1

Sat Apr 27 13:58:58 2019

:0

0.0.0.0:0

[Public Network Interface up ]

1

Sat Apr 27 13:58:57 2019

---.---.---.---:---

---.---.---.---:---

[Firewall Up ]

1

Sat Apr 27 13:58:19 2019

---.---.---.---:---

---.---.---.---:---

[Internet connected ]

1

Sat Apr 27 13:58:20 2019

:0

0.0.0.0:0

[Public Network Interface up ]

1

Sat Apr 27 13:58:19 2019

---.---.---.---:---

---.---.---.---:---

[SUCCESS: User interface login ]

1

Sat Apr 27 13:58:05 2019

192.168.100.1:80

192.168.0.30:51372

[Time Of Day established ]

1

Sat Apr 27 13:58:03 2019

---.---.---.---:---

---.---.---.---:---

[Internet disconnected ]

1

Thu Jan 01 00:01:01 1970

---.---.---.---:---

---.---.---.---:---

[SUCCESS: User interface login ]

1

Thu Jan 01 00:00:49 1970

192.168.100.1:80

192.168.0.30:51167

[Internet disconnected ]

1

Sat Apr 27 13:54:23 2019

---.---.---.---:---

---.---.---.---:---

[SUCCESS: User interface login ]

1

Sat Apr 27 13:48:18 2019

192.168.100.1:80

192.168.0.30:49801

[FAILURE: User interface login ]

277

Sat Apr 27 08:22:26 2019

:8443

107.182.231.98:55865

 

So I was originally looking at the top entries but this one at the bottom caught my eye.

This is the remote https management port that I opened last week to be able to remote into the device if it went down while I was at work, so I could get logs for you guys.

Before that entry, there were a couple port scans on my router from random IP addresses.  I traced this one, to be from Hosting Services Inc. in New York.  Should I be filing a complaint with them?

 

EDIT: Removed my external IP address.  Left the ports on there.

Regular Visitor

Re: Strange random outages. Possible comm issue with CMTS end. Or defective device?

Anytime I call the customer support phone number I end up talking with someone from the Phillipines who just sends out a local tech that doesn't understand what I'm showing him.

Does anyone know of a way that I can actually get someone to look into this for me?
Regular Visitor

Re: Strange random outages. Possible comm issue with CMTS end. Or defective device?

So I see people replying to other posts, but haven't received one in several days.

I'm pretty much fed up with Comcast at this point, and don't think I should have to do so much work on my own time to get their service to work properly.

It's a little ridiculous that I pay for a service but can't even get a person on the phone that has any clue about how to use it or operate it aside from calling out a local technician.

 

Sorry for the rant.  At this point, I'm ready to start shopping for a new provider.  I appreciate the one gentleman that did try to help, best of luck to the rest of you, hopefully you can get some guidance.