Jump to content
Sign in to follow this  
Inquisitor

What's this mean? Modem not functioning properly?

Recommended Posts

Check this out:

1970-01-01 00:00:27 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.

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

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

1970-01-01 00:00:17 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

1970-01-01 00:00:14 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

1970-01-01 00:00:15 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.

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

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

1970-01-01 00:00:16 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.

2004-08-10 18:35:00 3-Critical 0x04E33B3C Unicast Ranging Received Abort Response - Re- initializing MAC

2004-08-10 12:42:59 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.

2004-08-10 12:42:57 3-Critical 0x040D99C8 DHCP FAILED - Request sent, No response

2004-08-10 12:42:27 3-Critical 0x040D9964 DHCP FAILED - Discover sent, no offer received

2004-08-10 12:42:17 3-Critical 0x04E33948 No Ranging Response received - T3 time-out

2004-08-10 12:41:47 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:41:45 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:41:45 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:41:40 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:41:40 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:41:40 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:41:40 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:41:36 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:41:36 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:41:34 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:41:34 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:41:32 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:41:32 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:41:32 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:41:31 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:41:31 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:41:31 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:41:30 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:41:30 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:41:30 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:41:30 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:41:29 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:41:21 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:41:20 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:41:20 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:41:19 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:41:18 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:41:17 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:41:16 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:41:16 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:41:16 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:41:12 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:41:12 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:41:05 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:41:05 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:40:53 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:40:53 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:40:47 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:40:47 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:40:45 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:40:45 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:40:44 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:40:44 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:40:44 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:40:44 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:40:43 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:40:43 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:40:43 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:40:42 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:40:42 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:40:34 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:40:33 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:40:33 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:40:32 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:40:31 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:40:30 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:40:30 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:40:18 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:40:18 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-10 12:40:06 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-10 12:40:05 3-Critical 0x04E33A10 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout

2004-08-10 12:40:05 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

1970-01-01 00:00:15 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.

2004-08-10 11:59:37 3-Critical 0x04E33948 No Ranging Response received - T3 time-out

2004-08-10 11:59:28 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted

2004-08-10 11:59:28 3-Critical 0x04E33948 No Ranging Response received - T3 time-out

2004-08-10 11:59:20 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted

2004-08-10 11:59:20 3-Critical 0x04E33948 No Ranging Response received - T3 time-out

2004-08-10 11:59:13 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted

2004-08-10 11:59:13 3-Critical 0x04E33948 No Ranging Response received - T3 time-out

2004-08-10 11:59:04 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted

In addition, I got this bullshit e-mail from a system administrator, who says he accidentally set the configuration file from 2.0 to 1.5. Now, he says it's been returned to 2.0, all you have to do is power cycle the modem -- done it, and it's still 1.5. :evil:

Share this post


Link to post
Share on other sites

looks like a diganostics from some type of fiber router/modem... If it wasnt broken then why did the system admin mess with it? :lol: hmm...try unpluging the internet cable from it and then power cycle it.. What brands/model??

Share this post


Link to post
Share on other sites

SB5100

I've never had problems connecting or anything, so I assume it's not a big deal. Also, the cap was set back to 2.0 mbps. The reason it took longer, he said, was because the TFTP server wasn't started properly.

Anyhow, I've always wondered why the logs looked like that, with all the 'critical' errors and 'failed to acquire' responses

Share this post


Link to post
Share on other sites

that means that it isnt finding the service...

Copy the status from the front of that page... http://192.168.100.1

Here is what mine look lie:

004-08-11 03:17:49 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

2004-08-11 03:18:22 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

2004-08-11 03:17:43 3-Critical 0x0501BE90 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period

2004-08-11 03:18:33 3-Critical 0x04E33948 No Ranging Response received - T3 time-out

1970-01-01 00:03:51 4-Error 0x040D9A93 ToD request sent- No Response received

2004-08-11 03:17:20 3-Critical 0x04E33A10 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout

2004-08-11 03:01:46 3-Critical 0x0501BEF4 SYNC Timing Synchronization failure - Loss of Sync

2004-08-12 18:20:17 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out

2004-08-08 18:33:48 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted

2004-08-08 18:30:04 3-Critical 0x040D9964 DHCP FAILED - Discover sent, no offer received

2004-08-08 18:30:28 3-Critical 0x040D99C8 DHCP FAILED - Request sent, No response

2004-04-13 09:40:10 3-Critical 0x0459E508 REG RSP not received

1970-01-01 00:03:17 3-Critical 0x04E338E4 No Maintenance Broadcasts for Ranging opportunities received - T2 time-out

2003-11-16 08:33:02 3-Critical 0x0510FFA4 No UCD's Received - Timeout

2004-08-08 18:27:42 3-Critical 0x04E33AD8 Unicast Maintenance Ranging attempted - No response - Retries exhausted

2004-08-08 18:32:22 3-Critical 0x040D9AF4 TFTP failed - request sent - No Response

If you want to know what your modem is doing check this out.. http://broadband.motorola.com/consumers/products/SB5100/downloads/SB5100_LED_Troubleshooting.pdf You can trace through the errors.. :twisted:

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...