Software Version: SB5100-2.3.1.6-ENG03-d20off-NOSH
Hardware Version: 3
MIB Version: II
GUI Version: 1.0
VxWorks Version: 5.4
Woot!
I'll keep an eye on it and try running the Java diagnostics if/when it acts up again. I'll report back if I find anything interesting.
Thanks again.
And what do you know, it's gone down right this minute (~ 18:15) and there's nothing in the log yet. The modem lights are still indicating the connection is fine, but nothing's being received (from Z or the NY Times or my e-mail account). I power cycled the modem and it came back up again pretty quickly and is working fine again.
The log doesn't indicate anything useful:
1970-01-01 00:00:14 \t3-Critical \t0x040D9A2C \tDHCP WARNING - Non-critical field invalid in response.
2005-11-06 14:02:41 \t3-Critical \t0x04E33A10 \tReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2005-11-06 14:02:34 \t3-Critical \t0x0501BDC8 \tSYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-11-06 14:02:30 \t3-Critical \t0x0501BD64 \tSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2005-11-06 14:02:29 \t3-Critical \t0x0501BDC8 \tSYNC Timing Synchronization failure - Failed to acquire FEC framing
2005-11-06 12:08:49 \t3-Critical \t0x040D9A2C \tDHCP WARNING - Non-critical field invalid in response.
The time always resets to 1/1/1970 on power cycling. It takes a while for it reset the clock.
Grrrrr.
Cheers,
Scott.
(Off to download the DOCSIS [link|http://homepage.ntlworld.com/robin.d.h.walker/docsdiag/index.html|Java diagnostic] now...)