+- Haxorware Forums (http://www.haxorware.com/forums)
+-- Forum: General (http://www.haxorware.com/forums/forumdisplay.php?fid=6)
+--- Forum: Modems (http://www.haxorware.com/forums/forumdisplay.php?fid=7)
+--- Thread: sb5101 event log (/showthread.php?tid=601)
sb5101 event log - justsomeguy - 18-09-2010
so after really screwing around with this sb5101 i finally tried to plug er in and see what happened...so it looked like it went online (showed online on the computer) but couldn't get to any website so i changed a check box (you'll see in the log) but still couldn't get anywhere...anyone got any ideas?
Time Priority Code Description
1970-01-01 00:00:56 Information D511.0 Retrieved DHCP .......... SUCCESS
1970-01-01 00:00:56 Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:52 Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:47 Information T500.0 Acquired Upstream .......... SUCCESS
1970-01-01 00:00:46 Critical R002.0 No Ranging Response received - T3 time-out (US 6)
1970-01-01 00:00:45 Information T501.0 Acquired Downstream (417000000 Hz)........ SUCCESS
1970-01-01 00:00:40 Critical R002.0 No Ranging Response received - T3 time-out (US 8)
1970-01-01 00:00:40 Information T501.0 Acquired Downstream (417000000 Hz)........ SUCCESS
1970-01-01 00:00:34 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:33 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:32 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:31 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:18 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:18 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:07 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2010-09-18 02:40:45 Notice M573.0 Modem Is Shutting Down and Rebooting...
2010-09-18 02:40:45 Critical Resetting the cable modem due to docsDevResetNow
1970-01-01 00:00:47 Information D511.0 Retrieved DHCP .......... SUCCESS
1970-01-01 00:00:47 Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:44 Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:40 Information T500.0 Acquired Upstream .......... SUCCESS
1970-01-01 00:00:39 Critical R002.0 No Ranging Response received - T3 time-out (US 5)
1970-01-01 00:00:39 Information T501.0 Acquired Downstream (417000000 Hz)........ SUCCESS
1970-01-01 00:00:34 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:34 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:32 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:31 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:18 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:17 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:06 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
** this is a mac issue isn't it? just doing a bit more reading and thought that might be whats wrong..i'll try to change and see what happens...but if anyone else has ideas please posts....thanks
RE: sb5101 event log - drewmerc - 18-09-2010
yes it looks very much like a mac issue
RE: sb5101 event log - justsomeguy - 18-09-2010
(18-09-2010, 07:29 AM)drewmerc Wrote: yes it looks very much like a mac issue
ok instead of just posting my event log i figured i'd post everything and all the setting i have on the unit...no matter what mac i use i keep getting help up..
Event Log
Time Priority Code Description
1970-01-01 00:00:46 Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:43 Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:37 Critical R002.0 No Ranging Response received - T3 time-out (US 5)
1970-01-01 00:00:31 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:31 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:29 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:29 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:17 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:16 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:05 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:46 Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:43 Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:37 Critical R002.0 No Ranging Response received - T3 time-out (US 5)
1970-01-01 00:00:31 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:31 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:29 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:28 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:16 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:16 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:04 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
in the overview it keeps getting help up ..here is that
Task Status
Acquire Downstream Channel Done
Obtain Upstream Parameters Done
Upstream Ranging Done
Establish IP Connectivity Done
Retrieve Time of Day In Progress
Negotiate security Waiting
Receive configuration Waiting
Register connection Waiting
Cable modem status IP Complete
and here is the settings i have on it :
General
Factory Mode ----not checked
Disable Firmware Upgrades---check
Force Network Access ---check
Tftp Enforce Bypass ---check
Disable IP Filters on startup ---check
Timeouts
Ignore T1 (No valid UCDs) --not checked
Ignore T2 (Ranging Opportunity) --not checked
Ignore T3 (Ranging Response) --not checked
Ignore T4 (Station Maintenance) --not checked
can anyone gimmie any advice?
RE: sb5101 event log - justsomeguy - 19-09-2010
ok so i figured out that i had to change my settings a bit..i unchecked tffp eforce bypass and changed my mac again. and disapbled bpi. also i changed the annex to both...still got the same results except for this :
1970-01-01 00:00:43 Critical D001.0 DHCP FAILED - Discover sent, no offer received
does this mean that my mac is good but my settings are still screwy?
also theres about 4 or 5 of T1's boxes in the settings area that are all unchecked...is this right?
thanks guys
RE: sb5101 event log - drewmerc - 19-09-2010
T1,T2,T3, & T4 Timeouts Descriptions
T1 Timeouts Number of timeouts caused by the router not receiving a valid UCD from the CMTS within the specified time.
T2 Timeouts Number of timeouts caused by the router not receiving a maintenance broadcast for ranging opportunities from the CMTS within a specified time.
T3 Timeouts Number of timeouts caused by the router not receiving a response within a specified time from the CMTS to a RNG-REQ message during initial maintenance.
T4 Timeouts Number of timeouts caused by the router not receiving a response within a specified time from the CMTS to a periodic maintenance request.
Flexibility in Dealing with Possible Theft-of-Service Attempts
Service providers have the option of deciding what response to take when a DOCSIS configuration file fails its CMTS MIC check: mark that cable modem and allow the user online, reject the registration request and refuse to allow the user to come online until a valid DOCSIS configuration file is used, or lock the cable modem in a restricted QoS configuration until the modem remains offline for 24 hours. Locking malicious modems is the most effective deterrent against hackers, because it provides the maximum penalty and minimum reward for any user attempting a theft-of-service attack.
Please read
DCC Depart messages
DCC gets invoked because of a saturated US or DS freq. The DCC option is usually configured to move "X" number of the top talkers (ie: heaviest users) to another available freq. This is Load Balancing by the CMTS/UBR
ripped from ABMJR's sig on surfboard hacker