OptimumOnline → Optimum suppressing modem Event Logs ?? (or simply delay)

I have two Optimum accounts (one business, one residential) in two different locations.

I own my modems, which right now are a Netgear CM600 and an Arris SB 6183.

I usually get TONS of error messages and timeouts in the Event Log of each modem.

Yesterday and today with each modem, the Event Logs are totally empty even after a 'refresh'.

I really doubt that Optimum's networks have become 100 percent perfect overnight.

The only other thing I can think of is that they are suppressing the error messages?

I would not say suppressing, but I have noticed that unless there is a major problem like rcs partial, mmd timeouts, or loss of service causing errors that the log is very delayed

I would see all clear until 8pm, then suddenly it would say there was a t3 timeout at 9am. That reported timeout was not there until 8pm at night. The reporting seems to happen in real time, but the log seems to be on some kind of delay

That makes sense.

Not that I [want] errors, but I'll see if some new ones show up by tomorrow at either of my locations.

"Be careful what you wish for".

They just dumped four (4) days of error messages on me.

not even the old logs?

same client to access both modems? i guess it's the client failed to load

I routinely clear the logs every few days, but this is the first time that fresh entries did not appear.I'm not sure what you mean by that "client" reference.

The two modems are on two totally different accounts in different locations. Each was accessed on a local computer using the »192.168.100.1/ address. Multiple browsers were tried in each case.

In any event, at my home (as noted) they sent me 4 days worth of error messages at once, and here at work they have now sent me some error messages from yesterday.

So the puzzle of having no error messages (previously receiving them all the time) is resolved.

I can't even access 192.168.100.1 on the TM1602 anymore.
Anyone know why?

This is very bizarre behavior I have no explanation for, especially on two different modems (but both use the Broadcom BCM3384 chipset family, albeit not exactly the same) at the same time but to clarify : Optimum plays no role in this:

• the event logs are generated by the cable modem internally, they are not "sent" to the modem by anyone
• log levels can be adjusted by way of configuration - but that would be a permanent config change during provisioning (boot), and not change on the fly.
• log message can be streamed by the cable modem to a monitoring system (syslog) - albeit I don't think there'd be much value in that relatively to the billions of records that would generate per day, and which would have to be stored (and watched for what exactly? on-demand polling of RF conditions works so much better)
• the log messages in the Web UI and on the backend (via SNMP) can be different , for example the Web UI never shows the NUMBER of times an event occurred - such as, say: 15 T3 timeouts. Visible from the SNMP side, never (why do you do such things, vendors, why?) visible on the Web UI. This is a "duplicate message" suppression mechanism for the logs - only changing to a new entry if the message/event is not the same.
• the logs may or may not be stored in NVRAM to survive a reboot - indeed, what's written to NVRAM may be selective/restricted - so the view of log messages (via both Web UI or SNMP) might be different before/after the reboot
• all of these behaviors are vendor/model/chipset specific and vary significantly between one another
• vendors (and chipset OEMs Broadcom and MaxLinear (formerly known as TI and then Intel's PUMA) implement vastly different log messages in both quantity and content

(and I prefer PUMA's log style way over the Broadcom logs btw).

Try rebooting the modem. The internal web server randomly crashes.

Sure enough - thanks Doc!

(And I'm the guy who posted "rebooting the computer fixes many a problem" - yet rebooting the modem didn't occur to me??)