Results 1 to 6 of 6

Thread: Modem Dropping Out...Please Analyze Log

  1. #1
    Junior Member
    Join Date
    Sep 2006
    Posts
    3

    Modem Dropping Out...Please Analyze Log

    Howdy,
    New member here. My modem [Motorola SB4101]started dropping out a few weeks ago.
    Charter swears it is my router. I replaced my Linksys BEFSR41, configured and the same problem happens. Will drop out within an hour or so.
    So, I am sort of convinced the modem [3 years old] may be the problem.
    Admittedly, I have not tried the modem straight by itself but, why is it I have surfed without any problems for 3 years and now have problems?
    Anyway, here is some log data if someone can please evaluate it, and many thanks!

    Downstream Value
    Frequency 735000000 Hz Locked
    Signal to Noise Ratio 35 dB
    Power Level -5 dBmV

    Upstream Value
    Channel ID 1
    Frequency 23984000 Hz Ranged

    Power Level 49 dBmV

    Time Priority Code Message
    060918200732 8-Debug M579.3 CM Cert Upgrade Disabled. Motorola CM certificate present
    060918200732 8-Debug I503.0 Cable Modem is OPERATIONAL
    060918200732 8-Debug F502.1 Bridge Forwarding Enabled.
    060918200732 8-Debug F502.3 Bridge Learning Enabled.
    060918200732 8-Debug B918.0 Baseline Privacy is skipped
    060918200732 7-Information X519.8 Unit Update - MMFMMD - SCD flags
    060918200732 8-Debug I500.1 DOCSIS 1.0 Registration Completed
    060918200732 7-Information I500.4 Attempting DOCSIS 1.0 Registration
    060918200732 7-Information D509.0 Retrieved TFTP Config File SUCCESS
    060918200732 7-Information D507.0 Retrieved Time....... SUCCESS
    ************ 7-Information D511.0 Retrieved DHCP .......... SUCCESS
    ************ 5-Warning D3.0 DHCP WARNING - Non-critical field invalid in response
    ************ 4-Error D530.8 DHCP - Invalid Log Server IP Address.
    ************ 5-Warning D520.2 DHCP Attempt# 2 BkOff: 5s Tot DSC:2 OFF:1 REQ:1 ACK:1
    ************ 3-Critical D1.0 DHCP FAILED - Discover sent, no offer received
    ************ 7-Information D0.0 DHCP CM Net Configuration download and Time of Day
    ************ 7-Information T500.0 Acquired Upstream .......... SUCCESS
    ************ 8-Debug T503.1 Acquire US with status OK, powerLevel 49, tempSid 4779
    ************ 8-Debug T505.0 Acquired Upstream with status OK
    ************ 7-Information T501.0 Acquired Downstream (735000000 Hz)........ SUCCESS
    ************ 8-Debug T509.0 Acquired DS with status OK, DS Freq 735000000, US Id 1
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 105000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 99000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 93000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 855000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 849000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 843000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 837000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 831000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 825000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 819000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 813000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 807000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 801000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 795000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 789000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 783000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 777000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 771000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 765000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 759000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 753000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 747000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 741000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 735000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 729000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 723000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 717000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 711000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 705000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 699000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 693000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 687000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 681000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 675000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 669000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 663000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 657000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 651000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO SYNC, DS Freq 645000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO SYNC, DS Freq 633000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO SYNC, DS Freq 573000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 543000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 537000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 531000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 525000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 519000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 513000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 507000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 501000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO SYNC, DS Freq 555000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO SYNC, DS Freq 735000000, US Id 0
    ************ 7-Information I510.0 *** BOOTING *** SB4100-0.4.9.5-SCM01-NOSH
    ************ 7-Information H501.2 HFC: Shutting Downstream Down
    ************ 7-Information X519.8 Unit Update - MMFMMD - SCD flags
    ************ 8-Debug T509.0 Acquired DS with status NO SYNC, DS Freq 555000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 735000000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 121756000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 127756300, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 133756600, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 139756900, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 145757200, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 151757500, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 157757800, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 163758100, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 169758400, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 175758700, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 181759000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 187759300, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 193759600, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 199759900, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 205760200, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 211760500, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 217760800, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 223761100, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 229761400, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 235761700, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 241762000, US Id 0
    ************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
    ************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 247762300, US Id 0
    Event Log has reached maximum size. Older log entries are lost.




    Status |

  2. #2
    Moderator YeOldeStonecat's Avatar
    Join Date
    Jan 2001
    Location
    Somewhere along the shoreline in New England
    Posts
    50,857
    One of the most common things to check, is if you have any splitters before the modem. Especially if outside.
    MORNING WOOD Lumber Company
    Guinness for Strength!!!

  3. #3
    Junior Member
    Join Date
    Sep 2006
    Posts
    3
    Both splitters are in good visual shape. All cables and plugs are in good visual shape. I have been surfing hard for about two hours this evening and I know what is going to happen about any minute now....

  4. #4
    Moderator YeOldeStonecat's Avatar
    Join Date
    Jan 2001
    Location
    Somewhere along the shoreline in New England
    Posts
    50,857
    Visual won't do it on a splitter...can pick them up at local electronics store for under 20 bucks. That's the first thing I'd try...had to do it with mine in under 1 year..my outdoor one.
    MORNING WOOD Lumber Company
    Guinness for Strength!!!

  5. #5
    Regular Member buckifan's Avatar
    Join Date
    Jan 2004
    Location
    Buckeye Nation
    Posts
    133
    The log entries needed to diagnose are lost due to the modem logging debug entries. I don't see a problem with your signal levels so I would probably try a new modem if all your connectors and splitters pass inspection as suggested.

  6. #6
    Junior Member
    Join Date
    Sep 2006
    Posts
    3
    Well folks, it was indeed the modem. Only Charter techs did not want to admit it during three sessions on the phone. The tech who came to the house told my wife that three years got his also. Now, all is well.

    Just imagine....a civil engineer who does not know squat about internet systems told 'the experts' what their problem was and, was correct in the diagnosis.
    Perhaps I sould go to work for NASA

    Thanks for your replies!

Similar Threads

  1. Router Cable Modem connection problems
    By mrglouie in forum General Broadband Forum
    Replies: 6
    Last Post: 06-14-09, 01:50 PM
  2. Modem speed drop solved
    By MrFlimpy in forum Broadband Tweaks Help
    Replies: 2
    Last Post: 05-02-08, 10:47 PM
  3. Best Data Modem
    By mccreadys4 in forum General Broadband Forum
    Replies: 4
    Last Post: 04-06-06, 05:18 AM
  4. Slow speed with new modem
    By gbiddle in forum General Broadband Forum
    Replies: 2
    Last Post: 02-26-06, 05:48 PM
  5. cable modem resetting peculiarity
    By xwray in forum General Broadband Forum
    Replies: 1
    Last Post: 02-07-06, 10:05 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •