  Lrscpa
join:1999-08-26 Demarest, NJ
| [OOL] How to clear Modem Event Log
I am getting occaisional disconnects on phone and internet service. When I go into the modem's (SBV5120) diagnostics screen the message under the Logs tab is "Event Log has reached maximum size. Older log entries are lost.", with no entries listed below. Can I clear this log myself, or will it require a call to CV? |
|
  kickass69
join:2002-06-03 Lake Hopatcong, NJ | If you go into Configuration....Click on Reset All Defaults and then Restart Cable Modem and let it start all the way back up and go back into the configuration manager, the log should be cleared with the recent startup entries. |
|
 TheWiseGuy Dog And Butterfly Premium,MVM join:2002-07-04 Yonkers, NY
| reply to Lrscpa I doubt resetting the log will help. You need to use Docsdiag to check the log.
See
»Re: Slow OOL Speeds
or
»Re: Surfboard or Scientific Atlanta? -- Warning, If you post nonsense and use misinformation and are here to argue based on those methods, you will be put on ignore. |
|
  RARPSL
join:1999-12-08 Suffern, NY
| Neither will help since the problem is that CV floods the modem with another "DIST: Management Message with unidentified Version->4 - Discard message" message every two seconds. Since the buffer is 100 entries, this means that after 200 seconds there is no message in the buffer except for these error messages (which the display code is told to not display). Docsdiag will only display the last 100 messages received which due to the flooding will be 100 copies of the error message. |
|
  jaa Premium,MVM join:2000-06-13
·Optimum Online
·Vonage
| reply to Lrscpa said by Lrscpa :Can I clear this log myself, or will it require a call to CV? A call to CV support will not help. The script they follow does not have "clear log" instructions.
said by Lrscpa :I am getting occaisional disconnects on phone and internet service. If you call with that, maybe they can help. -- NOTHING justifies terrorism. We don't negotiate with terrorists. Those that support terrorists are terrorists. |
|
  Tursiops_G Technoid Premium,MVM join:2002-02-06 Norwalk, CT clubs:
·Optimum Online
1 edit | reply to Lrscpa How are your Modem's Signal Levels?
Occasional Disconnects may possibly be due to "borderline" Signal problems... Go to the Modem's Signal Diagnostic page, and check the Signal levels...
Acceptable Signal Levels are:
Downstream: Signal-to-Noise Ratio: GREATER than 30 dB Power Level: Between -15 dBmV to +15 dBmV
Upstream: Power Level: LESS than 55 dBmV
If any of these are borderline (or out of spec), then check for Loose connections or Damaged Coaxial cable, and make sure that the Modem is connected to the FIRST 2:1 Splitter (closest to where the Cable Drop enters your House)...
If the cable/connections all check out OK, then Call CV, and schedule a Service Appointment...
-Tursiops_G. -- If You're Unsure, "RTFM"... If You're SURE, "RTFM" Anyway.  |
|
 TheWiseGuy Dog And Butterfly Premium,MVM join:2002-07-04 Yonkers, NY
| reply to RARPSL I have none of those in my Docsdiag log. I ran Docsdiag just before I posted to see if I had entries and I did (none were DIST: Management Message with unidentified Version->4 - Discard message). So while it is possible he is receiving those and that they have cleared all other entries in his log, it is also possible they have not. -- Warning, If you post nonsense and use misinformation and are here to argue based on those methods, you will be put on ignore. |
|
  kickass69
join:2002-06-03 Lake Hopatcong, NJ | I remember only getting those messages during my short time with Boost, once I switched back to the 603000000 Hz frequency they stopped. |
|
 TheWiseGuy Dog And Butterfly Premium,MVM join:2002-07-04 Yonkers, NY | If it is a DOCSIS 3.0 message for the Ultra tier, that might make sense. |
|
  RARPSL
join:1999-12-08 Suffern, NY
| reply to TheWiseGuy said by TheWiseGuy :I have none of those in my Docsdiag log. I ran Docsdiag just before I posted to see if I had entries and I did (none were DIST: Management Message with unidentified Version->4 - Discard message). So while it is possible he is receiving those and that they have cleared all other entries in his log, it is also possible they have not. What modem do you have and are you Standard or Boost? I think it only occurs with Boost Users. If you do not have a SBV5120 that might be the other reason. I acknowledge my error in that I did not make the need to be a Boost User for my comment to apply since it is apparently keyed to the Ultra use of the Boost Frequency. |
|
 TheWiseGuy Dog And Butterfly Premium,MVM join:2002-07-04 Yonkers, NY
| I have the SBV 5222 so I guess that could have an effect on whether they are in the logs. It does seem to be a DOCSIS 3.0 message and that probably means it only effects the Boost channels. No error on your part, you brought up a valid point that the logs might not help if they were being overwritten. -- Warning, If you post nonsense and use misinformation and are here to argue based on those methods, you will be put on ignore. |
|
  StreetSpirit Premium join:2002-08-13 Roslyn, NY
·Optimum Online
·Verizon Online DSL
| FWIW, On Boost in both my locations (LI, BK) I am seeing the repeating Management Message. For example,
|
|
 cablewizzard
join:2009-06-14 Hicksville, NY
| reply to Lrscpa said by Lrscpa :I am getting occaisional disconnects on phone and internet service. When I go into the modem's (SBV5120) diagnostics screen the message under the Logs tab is "Event Log has reached maximum size. Older log entries are lost.", with no entries listed below. Can I clear this log myself, or will it require a call to CV? I believe these are DOCSIS3 MDD messages, present on the Boost downstream channel, but not OOL. As the SB(V)5120 is a DOC2.0-only modem, the current firmware did not anticipate and hence does not understand those messages, and is rather noisy with its logging about it. I am confident future firmware versions for the SB(V)5120 modem will eliminate logging for these.
And yes, using docsdiag -log will get you the last N messages in the log, which is never stuck, and always aging out the oldest messages. Either run that the moment you experience a connectivity issue, or run it every few minutes with whatever the Windows' equivalent of a cronjob is. |
|