Modem Issues

wondering if any has the knowledge to decipher these logs and let me know what they think is going on. to put it in a nutshell, i have intermittent internet issues. randomly slow internet or none at all, ISP has been out numerous times over the YEARS with no improvement. As of late, during the Steam sale, on a number of occasions while downloading a game i had just purchased the modem would reset itself, i called the cable company, and according to their diagnostics, i was hitting the reset button.....seriously?? so here are the logs i could get from my modem this moment.

Downstream Channel
The data shown in the table below provides information about the signal coming from the network to your cable modem.

Downstream Status

Operational
Channel ID

4
Downstream Frequency

627000000 Hz
Modulation

256QAM
Bit Rate

42884296 bits/sec
Power Level

8.5 dBmV
Signal to Noise Ratio

38.0 dBmV
Upstream Channel
The data shown in the table below provides information about the signal being transmitted to the network from your cable modem.

Upstream Status

Operational
Channel ID

4
Upstream Frequency

36200000 Hz
Modulation

16QAM
Symbol Rate

2560 Ksym/sec
Power Level

45.0 dBmV

Sun Jul 29 09:16:50 2012 73040100 Notice (6) TLV-11 - unrecognized OID
Sun Jul 29 09:16:36 2012 2436694060 Critical (3) Booting up the cable modem
Sun Jul 29 09:15:32 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sat Jul 28 04:45:35 2012 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Tue Jul 24 07:35:42 2012 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Mon Jul 23 13:39:52 2012 2436694060 Critical (3) Booting up the cable modem
Sun Jul 22 18:58:39 2012 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Sun Jul 22 00:34:38 2012 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Sat Jul 21 23:52:32 2012 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Sat Jul 21 23:52:02 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Time Not Established 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Time Not Established 2436694060 Critical (3) Booting up the cable modem
Time Not Established 68000700 Critical (3) TFTP Failed - OUT OF ORDER packets
Sat Jul 21 14:16:17 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Fri Jul 20 23:43:41 2012 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Thu Jul 19 05:22:03 2012 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Thu Jul 19 05:21:33 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Wed Jul 18 01:31:36 2012 82000400 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Wed Jul 18 01:31:06 2012 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Tue Jul 17 07:14:10 2012 82000200 Critical (3) No Ranging Response received - T3 time-out
Tue Jul 17 07:13:50 2012 82000300 Critical (3) Init RANGING Critical Ranging Request Retries exhausted
Tue Jul 17 07:13:50 2012 82000200 Critical (3) No Ranging Response received - T3 time-out
Tue Jul 17 07:12:09 2012 82000300 Critical (3) Init RANGING Critical Ranging Request Retries exhausted
Tue Jul 17 07:12:09 2012 82000200 Critical (3) No Ranging Response received - T3 time-out
Tue Jul 17 07:11:28 2012 82000300 Critical (3) Init RANGING Critical Ranging Request Retries exhausted
Tue Jul 17 07:11:28 2012 82000200 Critical (3) No Ranging Response received - T3 time-out
Tue Jul 17 07:10:51 2012 82000300 Critical (3) Init RANGING Critical Ranging Request Retries exhausted
Tue Jul 17 07:10:51 2012 82000200 Critical (3) No Ranging Response received - T3 time-out
Tue Jul 17 07:10:13 2012 82000300 Critical (3) Init RANGING Critical Ranging Request Retries exhausted
Tue Jul 17 07:10:13 2012 82000200 Critical (3) No Ranging Response received - T3 time-out
Tue Jul 24 07:38:47 2012 84000200 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Tue Jul 24 07:38:57 2012 84000100 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...

i'm not a pro, but seeing all those T3 time-outs and exhausted requests makes me think there's a lil more going on with my modem/internet than me sitting here and resetting my modem during a download... i'm still baffled by that answer.


PACKETCABLE (MTA) Events
The data shown in the table below provides information about the PacketCable events of your cable modem.

Time ID Level Description MAC Address Endpoint Name
07/30/2012 20:31:05 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/30/2012 16:31:17 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/30/2012 16:20:34 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/30/2012 06:43:24 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/29/2012 23:08:47 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/29/2012 22:00:09 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/29/2012 16:35:26 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/29/2012 09:17:54 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/29/2012 09:16:58 54 Information (5) INFO: Endpoint is not connected to CMS 00-23-BE-39-13-2E AALN/1:******************************************************
07/28/2012 21:34:30 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/28/2012 20:59:14 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/28/2012 18:17:22 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/28/2012 18:11:23 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/28/2012 18:09:50 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/28/2012 04:51:07 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/28/2012 04:46:31 54 Information (5) INFO: Endpoint is not connected to CMS 00-23-BE-39-13-2E AALN/1:******************************************************
07/28/2012 04:45:35 52 Critical(1) Loss of RF 00-23-BE-39-13-2E AALN/1:******************************************************
07/28/2012 02:28:57 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/28/2012 01:48:29 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/27/2012 21:41:30 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/27/2012 21:36:58 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/27/2012 21:23:07 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/27/2012 03:04:41 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/26/2012 21:30:40 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/25/2012 12:45:20 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/24/2012 23:27:33 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/24/2012 23:12:30 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/24/2012 21:44:17 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/24/2012 20:21:45 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/24/2012 20:14:45 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/24/2012 20:13:16 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/24/2012 19:03:03 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/24/2012 19:00:08 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/24/2012 18:59:02 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/24/2012 07:44:05 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/24/2012 07:39:45 54 Information (5) INFO: Endpoint is not connected to CMS 00-23-BE-39-13-2E AALN/1:******************************************************
07/24/2012 07:35:42 52 Critical(1) Loss of RF 00-23-BE-39-13-2E AALN/1:******************************************************
07/24/2012 04:21:17 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/24/2012 01:05:49 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/23/2012 22:00:10 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/23/2012 21:02:59 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/23/2012 21:00:37 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/23/2012 16:09:10 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/23/2012 13:40:42 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/23/2012 13:40:18 54 Information (5) INFO: Endpoint is not connected to CMS 00-23-BE-39-13-2E AALN/1:******************************************************
07/23/2012 03:41:55 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/22/2012 19:03:27 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/22/2012 18:59:34 54 Information (5) INFO: Endpoint is not connected to CMS 00-23-BE-39-13-2E AALN/1:******************************************************
07/22/2012 18:58:39 52 Critical(1) Loss of RF 00-23-BE-39-13-2E AALN/1:******************************************************
07/22/2012 17:44:53 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/22/2012 17:43:32 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/22/2012 17:42:49 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/22/2012 17:18:56 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/22/2012 17:18:17 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/22/2012 17:17:30 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/22/2012 17:16:42 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/22/2012 17:15:34 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/22/2012 17:14:38 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/22/2012 17:11:46 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/22/2012 17:11:41 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/22/2012 00:38:14 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/22/2012 00:35:23 54 Information (5) INFO: Endpoint is not connected to CMS 00-23-BE-39-13-2E AALN/1:******************************************************
07/22/2012 00:34:38 52 Critical(1) Loss of RF 00-23-BE-39-13-2E AALN/1:******************************************************
07/22/2012 00:26:00 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/21/2012 23:55:49 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/21/2012 23:53:26 54 Information (5) INFO: Endpoint is not connected to CMS 00-23-BE-39-13-2E AALN/1:******************************************************
07/21/2012 23:52:32 52 Critical(1) Loss of RF 00-23-BE-39-13-2E AALN/1:******************************************************
07/21/2012 22:30:06 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/21/2012 22:01:05 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/21/2012 21:46:03 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/21/2012 18:57:21 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/21/2012 14:26:12 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/21/2012 14:21:22 54 Information (5) INFO: Endpoint is not connected to CMS 00-23-BE-39-13-2E AALN/1:******************************************************
07/21/2012 14:15:45 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/20/2012 23:49:30 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/20/2012 23:44:42 54 Information (5) INFO: Endpoint is not connected to CMS 00-23-BE-39-13-2E AALN/1:******************************************************
07/20/2012 23:43:41 52 Critical(1) Loss of RF 00-23-BE-39-13-2E AALN/1:******************************************************
07/20/2012 18:18:14 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/20/2012 17:59:36 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/20/2012 16:35:30 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/19/2012 21:47:50 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/19/2012 20:24:10 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/19/2012 05:24:20 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/19/2012 05:22:57 54 Information (5) INFO: Endpoint is not connected to CMS 00-23-BE-39-13-2E AALN/1:******************************************************
07/19/2012 05:22:03 52 Critical(1) Loss of RF 00-23-BE-39-13-2E AALN/1:******************************************************
07/18/2012 20:47:40 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/18/2012 19:11:01 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/18/2012 18:10:52 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/18/2012 13:46:54 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/18/2012 07:49:24 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/18/2012 07:18:32 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/18/2012 02:34:00 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/18/2012 01:33:45 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/18/2012 01:32:21 54 Information (5) INFO: Endpoint is not connected to CMS 00-23-BE-39-13-2E AALN/1:******************************************************
07/18/2012 01:31:36 52 Critical(1) Loss of RF 00-23-BE-39-13-2E AALN/1:******************************************************
07/18/2012 00:01:43 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/17/2012 23:59:26 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/17/2012 23:56:43 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/17/2012 23:45:35 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/17/2012 20:47:27 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/17/2012 20:37:13 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/17/2012 20:32:13 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/17/2012 20:25:33 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/17/2012 19:24:40 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/17/2012 17:34:07 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/17/2012 07:14:58 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************
07/17/2012 07:14:38 54 Information (5) INFO: Endpoint is not connected to CMS 00-23-BE-39-13-2E AALN/1:******************************************************
07/17/2012 05:05:08 52 Critical(1) Loss of RF 00-23-BE-39-13-2E AALN/1:******************************************************
07/16/2012 23:31:08 53 Information (5) INFO: Endpoint is connected to CMS (and not in call) 00-23-BE-39-13-2E AALN/1:******************************************************


in this log i notice a once a day Loss of RF in the log. wondering if this is normal as well.
2 answers Last reply
More about modem issues
  1. Years ago I lived in Florida and had a similar problem. Turned out the cable lines leading to the house were frayed and cracked, leading to intermittent outages. We checked everything but that for days and weeks before throwing up our hands and deciding, why not, let's change the wiring. Like magic, problem solved.

    So if you live in a location with above ground cables and lots of weathering, it’s something to consider. It’s one of those things that everyone assumes is good and is working properly. But when it goes bad, it’s very hard to detect. My cable guy was actually the one who offered to change it (probably because he was frustrated as much as I was). He told me they change out all the street wiring about every 10 years (at least in that area), but not necessary the line from the street to the home.
  2. eibgrad said:
    Years ago I lived in Florida and had a similar problem. Turned out the cable lines leading to the house were frayed and cracked, leading to intermittent outages. We checked everything but that for days and weeks before throwing up our hands and deciding, why not, let's change the wiring. Like magic, problem solved.

    So if you live in a location with above ground cables and lots of weathering, it’s something to consider. It’s one of those things that everyone assumes is good and is working properly. But when it goes bad, it’s very hard to detect. My cable guy was actually the one who offered to change it (probably because he was frustrated as much as I was). He told me they change out all the street wiring about every 10 years (at least in that area), but not necessary the line from the street to the home.



    Thanks for replying to both of my posts, I appreciate it so much. I've had too many service calls out here for these issues to even consider using the ISP i am anymore, but I'll try running that past them, because as far as I know, that's the only thing here yet to be replaced. I know all the wiring in the house was replaced, modem, splitters, cablebox (they thought it would help the internet?) So i'll see if i can get them to replace the wiring from pole to house, as I am in Daytona Beach, Florida.
Ask a new question

Read More

Internet Service Providers Modem Networking