Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
sb5101 goes in reboot cycle
#1
Sb5101 with Hax39 was working fine with valid certs and spoofed software version on TW but started rebooting every 1 min after going operational and getting valid Ip. Changing the modem does not help. Signal is good. It's also working fine in other places.
Telnet log

TLV-11[69]: 1.3.6.1.2.1.69.1.6.4.1.15.593 -> 593 (i32)
TLV-11[70]: 1.3.6.1.2.1.69.1.6.4.1.2.64 -> 4 (i32)
TLV-11[71]: 1.3.6.1.2.1.69.1.6.4.1.4.64 -> 2 (i32)
TLV-11[72]: 1.3.6.1.2.1.69.1.6.4.1.5.64 -> 1 (i32)
TLV-11[73]: 1.3.6.1.2.1.69.1.6.4.1.11.64 -> 17 (i32)
TLV-11[74]: 1.3.6.1.2.1.69.1.6.4.1.12.64 -> 68 (i32)
TLV-11[75]: 1.3.6.1.2.1.69.1.6.4.1.13.64 -> 68 (i32)
TLV-11[76]: 1.3.6.1.2.1.69.1.6.4.1.14.64 -> 67 (i32)
TLV-11[77]: 1.3.6.1.2.1.69.1.6.4.1.15.64 -> 67 (i32)
TLV-11[78]: 1.3.6.1.2.1.69.1.6.4.1.2.66 -> 4 (i32)
TLV-11[79]: 1.3.6.1.2.1.69.1.6.4.1.4.66 -> 1 (i32)
TLV-11[80]: 1.3.6.1.2.1.69.1.6.4.1.5.66 -> 1 (i32)
TLV-11[81]: 1.3.6.1.2.1.69.1.6.4.1.11.66 -> 17 (i32)
TLV-11[82]: 1.3.6.1.2.1.69.1.6.4.1.12.66 -> 67 (i32)
TLV-11[83]: 1.3.6.1.2.1.69.1.6.4.1.13.66 -> 67 (i32)
TLV-11[84]: 1.3.6.1.2.1.69.1.6.4.1.14.66 -> 68 (i32)
TLV-11[85]: 1.3.6.1.2.1.69.1.6.4.1.15.66 -> 68 (i32)
TLV-11[86]: 1.3.6.1.2.1.69.1.6.4.1.2.172 -> 4 (i32)
TLV-11[87]: 1.3.6.1.2.1.69.1.6.4.1.4.172 -> 2 (i32)
TLV-11[88]: 1.3.6.1.2.1.69.1.6.4.1.5.172 -> 2 (i32)
TLV-11[89]: 1.3.6.1.2.1.69.1.6.4.1.9.172 -> 172.16.0.0
TLV-11[90]: 1.3.6.1.2.1.69.1.6.4.1.10.172 -> 255.240.0.0
TLV-11[91]: 1.3.6.1.2.1.69.1.6.4.1.2.681 -> 4 (i32)
TLV-11[92]: 1.3.6.1.2.1.69.1.6.4.1.4.681 -> 0 (i32)
TLV-11[93]: 1.3.6.1.2.1.69.1.6.4.1.5.681 -> 1 (i32)
TLV-11[94]: 1.3.6.1.2.1.69.1.6.4.1.9.681 -> 232.10.10.0
TLV-11[95]: 1.3.6.1.2.1.69.1.6.4.1.10.681 -> 255.255.254.0
TLV-11[96]: 1.3.6.1.2.1.69.1.6.4.1.2.682 -> 4 (i32)
TLV-11[97]: 1.3.6.1.2.1.69.1.6.4.1.4.682 -> 1 (i32)
TLV-11[98]: 1.3.6.1.2.1.69.1.6.4.1.5.682 -> 3 (i32)
TLV-11[99]: 1.3.6.1.2.1.69.1.6.4.1.9.682 -> 10.128.0.0
TLV-11[100]: 1.3.6.1.2.1.69.1.6.4.1.10.682 -> 255.192.0.0
TLV-11[101]: 1.3.6.1.2.1.69.1.6.4.1.2.683 -> 4 (i32)
TLV-11[102]: 1.3.6.1.2.1.69.1.6.4.1.3.683 -> 2 (i32)
TLV-11[103]: 1.3.6.1.2.1.69.1.6.4.1.4.683 -> 1 (i32)
TLV-11[104]: 1.3.6.1.2.1.69.1.6.4.1.5.683 -> 1 (i32)
TLV-11[105]: 1.3.6.1.2.1.69.1.6.4.1.9.683 -> 224.0.0.9
TLV-11[106]: 1.3.6.1.2.1.69.1.6.4.1.10.683 -> 255.255.255.255
TLV-11[107]: 1.3.6.1.2.1.69.1.6.4.1.11.683 -> 17 (i32)
TLV-11[108]: 1.3.6.1.2.1.69.1.6.4.1.2.684 -> 4 (i32)
TLV-11[109]: 1.3.6.1.2.1.69.1.6.4.1.4.684 -> 1 (i32)
TLV-11[110]: 1.3.6.1.2.1.69.1.6.4.1.5.684 -> 1 (i32)
TLV-11[111]: 1.3.6.1.2.1.69.1.6.4.1.9.684 -> 224.0.0.0
TLV-11[112]: 1.3.6.1.2.1.69.1.6.4.1.10.684 -> 240.0.0.0
TLV-11[113]: 1.3.6.1.2.1.69.1.6.4.1.11.684 -> 17 (i32)
SB5102 CM Agent w/ BRCM Factory Support processing TLV-11's
SNMP packet sent to 10.45.245.154:225
113 TLV-11's OK.
Sending a REG-REQ to the CMTS...
CM>
CM> Received a REG-RSP message from the CMTS...
0x00005c3a [CmDocsisCtlThread] BcmCmDocsisCtlThread::RegRspMsgEvent: (CmDocsisC
tlThread) We registered with a DOCSIS 1.1 config file!
Registration complete!
Process CVC
Co-signer CVC verified
At least one CVC is valid.
DOCSIS CoS/QoS rate shaping enable is now 1
CmSnmpAgent::CmOperationalEvent for SB5102 CM Agent w/ BRCM Factory Support
CmSnmpAgent operating in 1.1 mode, including docsQos, excluding docsBpi
+++ No DH kickstart profiles or snmpCommunityTable entries installed.
We will operate in NMACCESS mode.
SB5102 CM Agent w/ BRCM Factory Support setting V1/V2 view to docsisNmAccessView
SB5102 CM Agent w/ BRCM Factory Support enabling management.
SB5102 CM Agent w/ BRCM Factory Support sending deferred traps...
Done w/ deferred traps.
SB5102 CPE Agent w/ BRCM Factory Support setting V1/V2 view to docsisNmAccessVie
w
0x00005c8a [CmDocsisCtlThread] BcmCmDocsisCtlThread::TestAndLaunchBpkm: (CmDocs
isCtlThread) BPKM enabled. starting BPKM key requests.
SB5102 CM Event Log w/ BRCM Factory Support sending deferred async messages...
Sending syslog message from IF 1 to 24.29.99.57:
<133> CABLEMODEM [ 'T 'T 'T 'T 'T 'T 'T 'T]: <2300955725> Ethernet link
up - ready to pass packets
Done w/ deferred msgs
Not logging event ID 66040100, control for level 7 is 0.
BPI initialization completed. Calling ConfigOperational().
Enabling network access for all CPE ports.

mot_scanList: Writing to Flash!
BcmCmDocsisStatusEventCodes::kCmIsOperational
Suspending SNMP Thread
0x00005dca [CmDocsisCtlThread] BcmVendorCmApplication::StopDhcpServer: (VendorE
xtension CmApp) Shutting down DHCP Server...
0x00005dca [CmDocsisCtlThread] BcmStandbySwitchThread::CmIsOperational: (Motoro
la Standby Switch Thread) Simulating a press of the standby switch to get the st
ate configured properly.
0x00005f82 [IGMP Thread] BcmIgmpThread::Starting Igmp Thread...: (IGMP Thread)
0x00005f82 [Motorola Standby Switch Thread] BcmStandbySwitchThread::ThreadMain:
(Motorola Standby Switch Thread) Standby switch was pressed!
0x00005f82 [Motorola Standby Switch Thread] BcmStandbySwitchThread:TonguerocessSwitc
hEvent: (Motorola Standby Switch Thread) Standby switch disabled in nonvol; ign
oring event.
Not logging event ID 2296948624, control for level 7 is 0.
CM> 0x00011a58 [CmDocsisCtlThread] BcmCmDocsisCtlThread::T4NoStationMaintEvent:
(CmDocsisCtlThread) ERROR - no Station Maint map op -> restart error

*
* We are currently at Freq 297000000 Hz...
* Current US Channel ID 22
* TargetDsFreq 297000000 Hz...
* TargetUsChan 22
* TargetContext 0
*

0x00011a58 [CmDocsisCtlThread] BcmCmDocsisCtlThread::T4NoStationMaintEvent: (Cm
DocsisCtlThread) MOTOROLA-SPECIFIC -> REBOOTING IN CASE OF T4
DefaultSnmpAgentClass::ShutdownPendingEvent for SB5102 CM Agent w/ BRCM Factor
y Support
SB5102 CM Agent w/ BRCM Factory Support disabling management.
SB5102 CM Agent w/ BRCM Factory Support defering traps.
SB5102 CM Agent w/ BRCM Factory Support sending deferred traps...
Done w/ deferred traps.
SB5102 CPE Agent w/ BRCM Factory Support disabling management.
SB5102 CPE Agent w/ BRCM Factory Support defering traps.
CmSnmpAgent waiting for packets, events, and traps to clear...
Logging event: Received Response to Broadcast Maintenance Request, But no Unicas
t Maintenance opportunities received - T4 timeout
Logging event: Modem Is Shutting Down and Rebooting...
Sending syslog message from IF 1 to 24.29.99.57:
<133> CABLEMODEM [ÇV64ÇV5 ]: <2300955924> Modem Is Shutting Down and Rebooting
...
CM> Bandwidth request failure! Status = 0
Non-Vol Settings successfully written to the device.
Stopping DHCP/ToD/TFTP (client requested)...
The ToD thread was stopped.
DHCPc: Releasing the lease with client id htype=1, value=00:xx:xx:xx:xx:xx
DHCPc: Sending Release packet; client id htype=1, value=00:xx:xx:xx:xx:xx
0x00011c88 [DHCP Client Thread] BcmEcosIpHalIf::RemoveLeaseImpl: (IP Stack1 Hal
If) Removing lease IP address 10.45.245.154 from IP stack 1
0x00011c88 [DHCP Client Thread] BcmEcosIpHalIf::RemoveLeaseImpl: (IP Stack1 Hal
If) This is the last address on the stack; shutting the stack down:numberOfAddre
sses=1
0x00011c92 [DHCP Client Thread] BcmEcosIpHalIf::ShutdownIpStackImpl: (IP Stack1
HalIf)
Shutting down IP stack 1
Reply


Messages In This Thread
sb5101 goes in reboot cycle - by cablefun - 17-11-2012, 08:15 PM
RE: sb5101 goes in reboot cycle - by ABMJR - 17-11-2012, 09:46 PM
RE: sb5101 goes in reboot cycle - by BornDirty - 17-11-2012, 09:49 PM
RE: sb5101 goes in reboot cycle - by cablefun - 17-11-2012, 10:26 PM
RE: sb5101 goes in reboot cycle - by marcin888888 - 17-11-2012, 10:31 PM
RE: sb5101 goes in reboot cycle - by cablefun - 17-11-2012, 10:33 PM
RE: sb5101 goes in reboot cycle - by marcin888888 - 17-11-2012, 10:50 PM
RE: sb5101 goes in reboot cycle - by ABMJR - 18-11-2012, 12:23 AM
RE: sb5101 goes in reboot cycle - by marcin888888 - 18-11-2012, 04:07 AM
RE: sb5101 goes in reboot cycle - by ABMJR - 18-11-2012, 04:28 AM
RE: sb5101 goes in reboot cycle - by cablefun - 19-11-2012, 08:26 AM
RE: sb5101 goes in reboot cycle - by marcin888888 - 19-11-2012, 02:38 PM
RE: sb5101 goes in reboot cycle - by cablefun - 20-11-2012, 08:46 PM
RE: sb5101 goes in reboot cycle - by digitalx1 - 06-12-2012, 08:18 PM
RE: sb5101 goes in reboot cycle - by kornwood - 06-12-2012, 08:20 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)