Jump to content
Sign in to follow this  
meionm

Request: Can you post Log from Motorola cable modem 5100

Recommended Posts

I am tring to find out what wrong with my connection which goes slow aroud 6pm. So far I had one comcast tech check singal, whch turn out fine. Speed wise everything is fine till 5pm then the speed starts slowing down to about the third of it. Since I own my own modem I can't request comcast to swipe them, though I don't think that it is the modem.

So can you post Log from motorola 5100, I don't know if this will be usefull to me, but I would appreicate it. Mine is always like failure to acquire something, time out

Share this post


Link to post
Share on other sites

I guess I can post my Log

2005-07-20 22:55:47 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out

2005-07-20 16:17:47 3-Critical 0x04E33A10 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout

2005-07-20 16:17:42 3-Critical 0x0501BE90 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period

2005-07-20 16:17:34 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2005-07-20 16:17:14 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out

2005-07-20 16:15:52 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2005-07-20 16:08:59 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2005-07-20 16:08:29 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2005-07-20 16:08:28 3-Critical 0x04E33A10 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout

2005-07-20 16:08:28 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2005-07-20 16:07:53 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out

2005-07-17 17:11:43 3-Critical 0x04E33A10 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout

2005-07-17 17:11:43 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

1970-01-01 00:00:21 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

1970-01-01 00:00:03 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

1970-01-01 00:00:03 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

1970-01-01 00:00:02 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2005-07-16 20:54:54 3-Critical 0x040D9964 DHCP FAILED - Discover sent, no offer received

2005-07-16 20:54:42 3-Critical 0x04E33948 No Ranging Response received - T3 time-out

2005-07-16 20:54:29 3-Critical 0x04E33A10 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout

2005-07-16 20:54:18 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2005-07-16 20:53:54 3-Critical 0x0501BE90 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period

1970-01-01 00:00:06 3-Critical 0x04E33948 No Ranging Response received - T3 time-out

2005-07-16 18:50:19 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2005-07-16 18:50:07 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2005-07-16 18:50:06 3-Critical 0x04E33A10 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout

2005-07-16 18:50:06 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2005-07-16 18:49:32 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out

2005-07-16 12:04:34 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2005-07-16 12:04:24 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2005-07-16 12:04:22 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2005-07-16 12:04:22 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2005-07-16 12:04:21 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2005-07-16 12:04:21 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2005-07-16 12:04:20 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2005-07-16 12:04:20 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2005-07-16 12:04:17 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2005-07-16 12:04:17 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2005-07-16 12:04:15 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2005-07-16 12:04:15 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2005-07-16 12:04:15 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2005-07-16 12:04:15 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2005-07-16 12:04:11 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2005-07-16 12:04:11 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2005-07-16 12:04:09 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2005-07-16 12:04:09 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2005-07-16 12:04:09 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2005-07-16 12:04:09 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2005-07-16 12:04:08 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

Downstream Value

Frequency 711000000 Hz Locked

Signal to Noise Ratio 37 dB

Power Level -3 dBmV

The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading

Upstream Value

Channel ID 6

Frequency 24000000 Hz Ranged

Power Level 44 dBmV

and this my ping

Pinging yahoo.com [66.94.234.13] with 32 bytes of data:

Reply from 66.94.234.13: bytes=32 time=148ms TTL=51

Reply from 66.94.234.13: bytes=32 time=137ms TTL=52

Reply from 66.94.234.13: bytes=32 time=140ms TTL=51

Reply from 66.94.234.13: bytes=32 time=143ms TTL=51

Ping statistics for 66.94.234.13:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 137ms, Maximum = 148ms, Average = 142ms

C:Documents and SettingsAdministrator>

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...