Thread Rating:
  • 1 Vote(s) - 3 Average
  • 1
  • 2
  • 3
  • 4
  • 5
TWC Automated Activation Page
#1
Hi folks,
I clone my provision modem running haxorware. Status shows operational, however each time i launch my browser it redirects to TWC automated activation page.

Any help is appreciated....


Uptime: 29m 26s
Memory: 350KiB/2748KiB (12%)
Status: Operational
DS: -1.3 dBmV/37.9 dB US: 47.4 dBmV Haxorware
Version 1.1 Revision 39

Event Log
Time Priority Code Description
1970-01-01 00:00:17 Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:06 Notice M571.1 Ethernet link up - ready to pass packets
2013-02-22 07:14:50 Notice M573.0 Modem Is Shutting Down and Rebooting...
2013-02-22 07:14:50 Critical Resetting the cable modem due to docsDevResetNow
1970-01-01 00:00:16 Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:06 Notice M571.1 Ethernet link up - ready to pass packets
2013-02-22 06:57:32 Notice M573.0 Modem Is Shutting Down and Rebooting...
2013-02-22 06:57:32 Critical Resetting the cable modem due to docsDevResetNow
1970-01-01 00:00:20 Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:36 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:36 Notice M571.4 Ethernet link dormant - not currently active
1970-01-01 00:07:46 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:07:46 Notice M571.4 Ethernet link dormant - not currently active
1970-01-01 00:11:51 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:11:51 Notice M571.1 Ethernet link up - ready to pass packets
1970-01-01 00:09:53 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:09:53 Notice M571.4 Ethernet link dormant - not currently active
1970-01-01 00:07:21 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:07:21 Notice M571.1 Ethernet link up - ready to pass packets
1970-01-01 00:03:11 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:03:11 Notice M571.4 Ethernet link dormant - not currently active
1970-01-01 00:00:04 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-10-30 02:40:56 Notice I401.0 TLV-11 - unrecognized OID
1970-01-01 00:01:04 Error D004.3 ToD request sent- No Response received
1970-01-01 00:01:04 Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:51 Critical R002.0 No Ranging Response received - T3 time-out (US 1)
1970-01-01 00:00:24 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:24 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:02 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:02 Notice M571.4 Ethernet link dormant - not currently active
1970-01-01 00:02:15 Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:02:12 Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:02:05 Critical R002.0 No Ranging Response received - T3 time-out (US 1)
1970-01-01 00:01:37 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:36 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:17 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:16 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 Notice M571.4 Ethernet link dormant - not currently active
1970-01-01 00:00:13 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:13 Notice M571.1 Ethernet link up - ready to pass packets
1970-01-01 00:00:02 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:02 Notice M571.4 Ethernet link dormant - not currently active
Reply
#2
2012-10-30 02:40:56 Notice I401.0 TLV-11 - unrecognized OID

Fix this
Knowledge=Power
Reply
#3
The TLV-11 - unrecognized OID message simply indicates that the configuration file contains different vendor (or multiple vendor) information in it.

Cable modem configuration files have multiple vendor-specific TLV-11, commonly called miscellaneous OIDs. They tell each brand of equipment how to do specific things for only that vendor. Since the config has multiple brands in it, all modems will report that error. They don't report that error when they see their native vendor info, but will report it during digestion of a config with other VSIF OID in it.

You may see the above notice in your cable modem's log files every time the modem registers it gets the configuration file. It should not affect the cm operation in any way

(22-02-2013, 06:24 PM)Florida Wrote:
(22-02-2013, 06:00 PM)ABMJR Wrote: 2012-10-30 02:40:56 Notice I401.0 TLV-11 - unrecognized OID

Fix this

if im not mistaking that means certs don't match mac?

might have a break or cut in his coax ????? posably
if you cant test dont invest !!!!!
Reply
#4
No, nothing whatsoever to do with any Plant/RF issues. This is internal with CVC issues..

TWC uses Co-signed FW now.
Knowledge=Power
Reply
#5
LOL @ DNS..

Nothing whatsoever to do with DNS
Knowledge=Power
Reply
#6
TLV is a show stopper in my neighborhood. It means you aren't doing something right.

Are you running Hax Diag or lite? USE LITE!

Did you make a full clone of your sub after the signed firmware push or did you just upload your sub's nonvol into hax?

It looks to me like you either overwrote the signed firm with diag which will kill it and not let get issued an ip...Diag oversteps the byte size of stock firm and new CMTS firm catches it.....Oops! and will throw up a tlv error.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)