Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
SB5101 wont connect to TW NYC
gcam77 Offline
Junior Member
**

Posts: 12
Threads: 2
Joined: Sep 2012
Reputation: 0
#1
SB5101 wont connect to TW NYC
My SB5101 just stopped connecting to TW NYC. Can anyone help me with this.

Here is the log:-

Time Priority Code Description
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:12 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:12 Notice M572.0 Ds Lock Failed - Reinitialize MAC...
1970-01-01 00:00:12 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:12 Notice M572.0 Ds Lock Failed - Reinitialize MAC...
1970-01-01 00:00:05 Notice M571.1 Ethernet link up - ready to pass packets
2012-09-11 16:56:23 Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-09-11 16:56:23 Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
1970-01-01 00:00:23 Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:12 Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:08 Critical R002.0 No Ranging Response received - T3 time-out (US 7)
1970-01-01 00:00:05 Notice M571.1 Ethernet link up - ready to pass packets
1970-01-01 00:00:02 Notice M571.4 Ethernet link dormant - not currently active
2012-09-11 16:55:23 Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-09-11 16:55:23 Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
1970-01-01 00:00:17 Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:05 Notice M571.1 Ethernet link up - ready to pass packets
1970-01-01 00:00:02 Notice M571.4 Ethernet link dormant - not currently active
2012-09-11 16:54:29 Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-09-11 16:54:29 Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2012-09-11 16:53:45 Critical I002.0 REG RSP not received
1970-01-01 00:00:35 Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:20 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:19 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:05 Notice M571.1 Ethernet link up - ready to pass packets
1970-01-01 00:00:02 Notice M571.4 Ethernet link dormant - not currently active
1970-01-01 00:01:25 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:25 Notice M573.0 Modem Is Shutting Down and Rebooting...
1970-01-01 00:01:25 Critical Resetting the cable modem due to docsDevResetNow
1970-01-01 00:00:08 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:08 Notice M571.1 Ethernet link up - ready to pass packets
1970-01-01 00:00:04 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
2012-09-11 16:47:42 Critical I002.0 REG RSP not received
2012-09-11 16:47:42 Critical I002.0 REG RSP not received
1970-01-01 00:00:16 Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:02 Notice M571.4 Ethernet link dormant - not currently active
2012-09-11 16:47:13 Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-09-11 16:47:13 Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2012-09-11 16:46:27 Critical I001.0 REG-RSP - invalid format or not recognized
2012-09-11 16:46:27 Critical I002.0 REG RSP not received
1970-01-01 00:00:17 Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:02 Notice M571.4 Ethernet link dormant - not currently active
2012-09-11 16:45:54 Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-09-11 16:45:54 Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2012-09-11 16:45:30 Critical I001.0 REG-RSP - invalid format or not recognized
1970-01-01 00:00:18 Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:02 Notice M571.4 Ethernet link dormant - not currently active
2012-09-11 16:45:01 Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-09-11 16:45:01 Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2012-09-11 16:44:37 Critical I001.0 REG-RSP - invalid format or not recognized
1970-01-01 00:00:16 Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:02 Notice M571.4 Ethernet link dormant - not currently active
2012-09-11 16:44:08 Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-09-11 16:44:08 Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2012-09-11 16:43:17 Critical I001.0 REG-RSP - invalid format or not recognized
1970-01-01 00:00:16 Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:03 Notice M571.4 Ethernet link dormant - not currently active
2012-09-11 16:42:51 Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-09-11 16:42:51 Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2012-09-11 16:41:59 Critical I001.0 REG-RSP - invalid format or not recognized
1970-01-01 00:00:23 Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:09 Critical R002.0 No Ranging Response received - T3 time-out (US 7)
1970-01-01 00:00:02 Notice M571.4 Ethernet link dormant - not currently active
2012-09-11 16:41:26 Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-09-11 16:41:26 Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2012-09-11 16:41:03 Critical I001.0 REG-RSP - invalid format or not recognized
1970-01-01 00:00:19 Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:02 Notice M571.4 Ethernet link dormant - not currently active
2012-09-11 16:40:31 Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-09-11 16:40:31 Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2012-09-11 16:39:46 Critical I001.0 REG-RSP - invalid format or not recognized
1970-01-01 00:00:22 Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:17 Critical D001.0 DHCP FAILED - Discover sent, no offer received
1970-01-01 00:00:02 Notice M571.4 Ethernet link dormant - not currently active
2012-09-11 16:39:13 Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-09-11 16:39:13 Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2012-09-11 16:38:49 Critical I001.0 REG-RSP - invalid format or not recognized
1970-01-01 00:00:17 Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:02 Notice M571.4 Ethernet link dormant - not currently active
2012-09-11 16:38:21 Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-09-11 16:38:21 Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2012-09-11 16:37:58 Critical I001.0 REG-RSP - invalid format or not recognized
1970-01-01 00:00:24 Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:10 Critical R002.0 No Ranging Response received - T3 time-out (US 7)
1970-01-01 00:00:02 Notice M571.4 Ethernet link dormant - not currently active
2012-09-11 16:37:23 Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-09-11 16:37:23 Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2012-09-11 16:36:34 Critical I001.0 REG-RSP - invalid format or not recognized
11-09-2012, 10:59 PM
Find Reply
ABMJR Away
DOCSIS Genius
*****

Posts: 1,513
Threads: 16
Joined: Dec 2009
Reputation: 78
#2
RE: SB5101 wont connect to TW NYC
Simple
Knowledge=Power
12-09-2012, 02:34 AM
Find Reply
drewmerc Offline
Prefect
******

Posts: 3,901
Threads: 19
Joined: Oct 2008
Reputation: 157
#3
RE: SB5101 wont connect to TW NYC
REG-RSP - invalid format or not recognized, i'll decode it "registration response - invalid"
__________________________________________________________________________________
******new discord chat link https://discord.gg/5BQQbsb*******
12-09-2012, 10:40 AM
Website Find Reply
gcam77 Offline
Junior Member
**

Posts: 12
Threads: 2
Joined: Sep 2012
Reputation: 0
#4
RE: SB5101 wont connect to TW NYC
Thanks for the responses. Can anyone tell me how to fix this problem? I am new at this.

The modem was connecting without any issues for a few weeks then it just stopped. I have searched for solutions but no luck.

Any help will be greatly appreciated.
12-09-2012, 01:38 PM
Find Reply
ABMJR Away
DOCSIS Genius
*****

Posts: 1,513
Threads: 16
Joined: Dec 2009
Reputation: 78
#5
RE: SB5101 wont connect to TW NYC
Post a TELNET log instead of an event log (worthless)..

I can say, your modem isnt provisioned for your CMTS, and you have new security..

Quote:1970-01-01 00:00:22 Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:17 Critical D001.0 DHCP FAILED - Discover sent, no offer received
Knowledge=Power
12-09-2012, 03:31 PM
Find Reply
gcam77 Offline
Junior Member
**

Posts: 12
Threads: 2
Joined: Sep 2012
Reputation: 0
#6
RE: SB5101 wont connect to TW NYC
Here is my TELNET LOG


=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2012.09.12 17:01:50 =~=~=~=~=~=~=~=~=~=~=~=
Haxorware integrated telnet daemon

Username: root
Password: ****
Welcome.

CM>
CM> run
CM>
CM> run_app


Running the system...


Beginning Cable Modem operation...

0x0000f320 [Scan Downstream Thread] BcmVendorCmDownstreamScanThread::ThreadMain: (Scan Downstream Thread) Scanning for a Downstream Channel...

mot_scanList: Setting override freq @ 0
Favorite[0].freq = 339000000
Attempting Downstream FEC lock @ freq= 339000000 Hz, QAM64/256

CM> Favorite[1].freq = 315000000
Attempting Downstream FEC lock @ freq= 315000000 Hz, QAM64/256
Favorite[2].freq = 297000000
Attempting Downstream FEC lock @ freq= 297000000 Hz, QAM64/256
Go back to 1st favorite
Attempting Downstream FEC lock @ freq= 501000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 507000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 513000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 519000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 525000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 531000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 537000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 543000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 549000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 555000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 561000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 567000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 573000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 579000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 585000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 591000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 597000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 603000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 609000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 615000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 621000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 627000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 633000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 639000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 645000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 651000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 657000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 663000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 669000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 675000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 681000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 687000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 693000000 Hz, QAM64
Found energy at frequency 693000000Hz! Publishing event kEventEnergyDetected...
Attempting Downstream FEC lock @ freq= 699000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 705000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 711000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 717000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 723000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 729000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 735000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 741000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 747000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 753000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 759000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 765000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 771000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 777000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 783000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 789000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 795000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 801000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 807000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 813000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 819000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 825000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 831000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 837000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 843000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 849000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 855000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 93000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 99000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 105000000 Hz, QAM64
Favorite[0].freq = 339000000
Attempting Downstream FEC lock @ freq= 339000000 Hz, QAM64/256
0x00013f24 [CmDocsisCtlThread] BcmCmDocsisCtlThread::StartUsInit: (CmDocsisCtlThread) Locked on the downstream. Waiting for UCDs...

******************************************
DOWNSTREAM STATUS
******************************************
Tuner Frequency = 339000000 Hz
Carrier Offset = 8 Hz
Symbol rate = 5360537 sym/sec
SNR = 37 dB
QAM Mode = QAM256
Tuner AGC = 0xfff00000
IF AGC = 0x150e320c
Power Level = 0 dB
QAM = LOCKED
FEC = LOCKED
******************************************

Calculating maximum number of IP filters:
Each IP filter consumes 1836 bytes of RAM.
Current free RAM is 417420 bytes.
Max heap reserved for IP filters (25%) = 104355
We can support 56 IP filters.
Calculating maximum number of LLC filters:
Each LLC filter consumes 724 bytes of RAM.
Current free RAM is 417420 bytes.
Max heap reserved for LLC filters (25%) = 104355
We can support 144 LLC filters.

CM> Selecting UCD for Us Channel 7

0x00014960 [CmDocsisCtlThread] BcmCmDocsisCtlThread::TestAndLaunchDsTimeSync: (CmDocsisCtlThread) starting ds time sync acquisition...
0x00014bfe [CmDocsisCtlThread] BcmCmDocsisCtlThread::SyncDsSyncOk: (CmDocsisCtlThread) downstream time sync acquired...
0x00014bfe [CmDocsisCtlThread] BcmCmDocsisCtlThread:Big GrinsSyncOkResumeUsInit: (CmDocsisCtlThread) pre-REG upstream target case...starting initial ranging.
Beginning initial ranging...
Using stored initial upstream power = 44.0 dBmV
0x00014c08 [CmDocsisCtlThread] BcmCmDocsisCtlThread::SyncDsSyncOk: (CmDocsisCtlThread) rx unexpected kDsSyncOk indication...

RNG-RSP Adj: tim=1024 power=0 freq=0 Stat=Continue
Not logging event ID 2307948724, control for level 7 is 0.

CM>
RNG-RSP Adj: tim=0 power=0 freq=400 Stat=Continue

CM>
RNG-RSP Adj: tim=0 power=0 freq=0 Stat=Success

******************************************
UPSTREAM STATUS
******************************************
Upstream Status = UP
Upstream Channel = 7
Upstream Frequency = 30600000 Hz
Upstream Power = 45 dBmV
Ranging SID = 0x18ad
Upstream Symbol Rate = 5120000 sym/sec
******************************************

Starting IP Initialization with DHCP...
DHCPc: Waiting 2 seconds before sending Discover; client id htype=1, value=00:26:24:e8:7d:e2
Not logging event ID 2307948624, control for level 7 is 0.

CM> DHCPc: Sending Discover packet; client id htype=1, value=00:26:24:e8:7d:e2
DHCPc: Received an Offer from DHCP server 00:01:5c:45:9a:41 (10.43.96.1); lease client id htype=1, value=00:26:24:e8:7d:e2

CM> DHCPc: Timed out waiting for offers for lease with client id htype=1, value=00:26:24:e8:7d:e2
DHCPc: Sending Request packet; client id htype=1, value=00:26:24:e8:7d:e2
DHCPc: Received an Ack from DHCP server 00:01:5c:45:9a:41 (10.43.96.1); lease client id htype=1, value=00:26:24:e8:7d:e2
Current IP address is default 0.0.0.0.
0x00016b98 [DHCP Client Thread] BcmEcosIpHalIf::ConfigureLeaseImpl: (IP Stack1 HalIf)
Configuring IP stack 1:
IP Address = 10.43.231.60 (primary IP address)
Subnet Mask = 255.255.224.0
Router = 10.43.224.1
IsPrimaryInterface = 1

Logging event: DHCP WARNING - Non-critical field invalid in response.
ARPing for default GW IP = 10.43.224.1
MAC = 00:01:5c:45:9a:41
DHCP completed successfully!

DHCP Settings:
Client Id = htype=1, value=00:26:24:e8:7d:e2
State = Renewing (5)
Static Lease = 0
AutoConfig Mode = IP, Subnet and Router
XID = 0x1d7df898
Number of Tries = 0
Max Discover Tries = 6
Max Request Tries = 6
DHCP server MAC addr = 00:01:5c:45:9a:41
Ignore NAKs = 0
My offered IP address = 10.43.231.60 (primary IP address)
(1) Subnet Mask = 255.255.224.0
(3) Router IP address = 10.43.224.1
(54) DHCP Server IP address = 24.29.137.62
(82) Relay Agent IP address = 10.43.96.1
TFTP Server IP address = 24.24.53.90
CM Configuration file = '?BBgdiT4AJiTofeIKK+c8@CivnPFeeGbDb7YxBzaWeOjge+vFtmQVR'
(2) UTC Time Offset = -18000 seconds
(4) Time Server IP address = 24.24.53.90
(6) Domain Name Server = 209.18.47.61; 209.18.47.62
(7) Log Server IP address = 24.29.99.57
(51) Lease time = 639129 seconds
(58) T1 (renew) = 319564 seconds
(59) T2 (rebind) = 559237 seconds
Lease is infinite = 0


SB5102 CM Agent w/ BRCM Factory Support IpStackEvent: Ip=10.43.231.60, Subnet=255.255.224.0, Gateway=10.43.224.1
CmSnmpAgent::IpAddressAcquiredEvent for SB5102 CM Agent w/ BRCM Factory Support
IP addr = 10.43.231.60
Starting Time Of Day...
0x00016c2e [CmDocsisIpThread] BcmDocsisTimeOfDayThread::SetTodServerIpAddress: (Time Of Day Thread) ToD servers: 24.24.53.90
Connecting to ToD server 24.24.53.90...
Sending UDP ToD request to server...
SNMP Agent Binding to 10.43.231.60:225
Not logging event ID 2291949724, control for level 7 is 0.

CM> UTC returned by ToD server 3556472573; UTC offset -18000
Current system time -> Wed Sep 12 16:02:53 2012

System start time -> Wed Sep 12 16:01:20 2012

Starting Tftp of configuration file...
Opening file '?BBgdiT4AJiTofeIKK+c8@CivnPFeeGbDb7YxBzaWeOjge+vFtmQVR' on 24.24.53.90 for reading...
tftp-enforce bypass is DISABLED

CM> Storing received cfg of size 3130 to memory
Tftp read < 512 bytes, we have reached end of file.
Tftp transfer complete!
TFTP Settings:
Stack Interface = 1
Server Ip Address = 24.24.53.90
Server Port Number = 39478
Total Blocks Read = 7
Total Bytes Read = 3130

Config file was read! IP Initialization completed...
MAX CPE per CM is being set to 32
TLV-11[1]: 1.3.6.1.2.1.69.1.2.1.2.16 -> 255.255.255.255
TLV-11[2]: 1.3.6.1.2.1.69.1.2.1.3.16 -> 255.255.255.255
TLV-11[3]: 1.3.6.1.2.1.69.1.2.1.4.16 -> RR_nycmny_nyc_m0d3m5
TLV-11[4]: 1.3.6.1.2.1.69.1.2.1.5.16 -> 3 (i32)
TLV-11[5]: 1.3.6.1.2.1.69.1.2.1.6.16 -> HEX:40 00
TLV-11[6]: 1.3.6.1.2.1.69.1.2.1.7.16 -> 4 (i32)
TLV-11[7]: 1.3.6.1.2.1.69.1.2.1.2.18 -> 255.255.255.255
TLV-11[8]: 1.3.6.1.2.1.69.1.2.1.3.18 -> 255.255.255.255
TLV-11[9]: 1.3.6.1.2.1.69.1.2.1.4.18 -> yZaK4E8l
TLV-11[10]: 1.3.6.1.2.1.69.1.2.1.5.18 -> 2 (i32)
TLV-11[11]: 1.3.6.1.2.1.69.1.2.1.6.18 -> HEX:40 00
TLV-11[12]: 1.3.6.1.2.1.69.1.2.1.7.18 -> 4 (i32)
TLV-11[13]: 1.3.6.1.2.1.69.1.2.1.2.19 -> 255.255.255.255
TLV-11[14]: 1.3.6.1.2.1.69.1.2.1.3.19 -> 255.255.255.255
TLV-11[15]: 1.3.6.1.2.1.69.1.2.1.4.19 -> mxGuP/7j7XydboD
TLV-11[16]: 1.3.6.1.2.1.69.1.2.1.5.19 -> 2 (i32)
TLV-11[17]: 1.3.6.1.2.1.69.1.2.1.6.19 -> HEX:40 00
TLV-11[18]: 1.3.6.1.2.1.69.1.2.1.7.19 -> 4 (i32)
TLV-11[19]: 1.3.6.1.2.1.69.1.2.1.2.20 -> 255.255.255.255
TLV-11[20]: 1.3.6.1.2.1.69.1.2.1.3.20 -> 255.255.255.255
TLV-11[21]: 1.3.6.1.2.1.69.1.2.1.4.20 -> 0RQOfsncj9TLupR
TLV-11[22]: 1.3.6.1.2.1.69.1.2.1.5.20 -> 3 (i32)
TLV-11[23]: 1.3.6.1.2.1.69.1.2.1.6.20 -> HEX:40 00
TLV-11[24]: 1.3.6.1.2.1.69.1.2.1.7.20 -> 4 (i32)
TLV-11[25]: 1.3.6.1.2.1.69.1.6.1.0 -> 1 (i32)
TLV-11[26]: 1.3.6.1.2.1.69.1.6.2.1.2.20 -> 4 (i32)
TLV-11[27]: 1.3.6.1.2.1.69.1.6.2.1.3.20 -> 0 (i32)
TLV-11[28]: 1.3.6.1.2.1.69.1.6.2.1.4.20 -> 1 (i32)
TLV-11[29]: 1.3.6.1.2.1.69.1.6.2.1.5.20 -> 2048 (i32)
TLV-11[30]: 1.3.6.1.2.1.69.1.6.2.1.2.22 -> 4 (i32)
TLV-11[31]: 1.3.6.1.2.1.69.1.6.2.1.3.22 -> 0 (i32)
TLV-11[32]: 1.3.6.1.2.1.69.1.6.2.1.4.22 -> 1 (i32)
TLV-11[33]: 1.3.6.1.2.1.69.1.6.2.1.5.22 -> 2054 (i32)
TLV-11[34]: 1.3.6.1.2.1.69.1.6.3.0 -> 2 (i32)
TLV-11[35]: 1.3.6.1.2.1.69.1.6.4.1.2.80 -> 4 (i32)
TLV-11[36]: 1.3.6.1.2.1.69.1.6.4.1.4.80 -> 1 (i32)
TLV-11[37]: 1.3.6.1.2.1.69.1.6.4.1.5.80 -> 1 (i32)
TLV-11[38]: 1.3.6.1.2.1.69.1.6.4.1.9.80 -> 10.0.0.0
TLV-11[39]: 1.3.6.1.2.1.69.1.6.4.1.10.80 -> 255.0.0.0
TLV-11[40]: 1.3.6.1.2.1.69.1.6.4.1.2.64 -> 4 (i32)
TLV-11[41]: 1.3.6.1.2.1.69.1.6.4.1.4.64 -> 2 (i32)
TLV-11[42]: 1.3.6.1.2.1.69.1.6.4.1.5.64 -> 1 (i32)
TLV-11[43]: 1.3.6.1.2.1.69.1.6.4.1.11.64 -> 17 (i32)
TLV-11[44]: 1.3.6.1.2.1.69.1.6.4.1.12.64 -> 68 (i32)
TLV-11[45]: 1.3.6.1.2.1.69.1.6.4.1.13.64 -> 68 (i32)
TLV-11[46]: 1.3.6.1.2.1.69.1.6.4.1.14.64 -> 67 (i32)
TLV-11[47]: 1.3.6.1.2.1.69.1.6.4.1.15.64 -> 67 (i32)
TLV-11[48]: 1.3.6.1.2.1.69.1.6.4.1.2.66 -> 4 (i32)
TLV-11[49]: 1.3.6.1.2.1.69.1.6.4.1.4.66 -> 1 (i32)
TLV-11[50]: 1.3.6.1.2.1.69.1.6.4.1.5.66 -> 1 (i32)
TLV-11[51]: 1.3.6.1.2.1.69.1.6.4.1.11.66 -> 17 (i32)
TLV-11[52]: 1.3.6.1.2.1.69.1.6.4.1.12.66 -> 67 (i32)
TLV-11[53]: 1.3.6.1.2.1.69.1.6.4.1.13.66 -> 67 (i32)
TLV-11[54]: 1.3.6.1.2.1.69.1.6.4.1.14.66 -> 68 (i32)
TLV-11[55]: 1.3.6.1.2.1.69.1.6.4.1.15.66 -> 68 (i32)
TLV-11[56]: 1.3.6.1.2.1.69.1.6.4.1.2.172 -> 4 (i32)
TLV-11[57]: 1.3.6.1.2.1.69.1.6.4.1.4.172 -> 2 (i32)
TLV-11[58]: 1.3.6.1.2.1.69.1.6.4.1.5.172 -> 2 (i32)
TLV-11[59]: 1.3.6.1.2.1.69.1.6.4.1.9.172 -> 172.16.0.0
TLV-11[60]: 1.3.6.1.2.1.69.1.6.4.1.10.172 -> 255.240.0.0
TLV-11[61]: 1.3.6.1.2.1.69.1.6.4.1.2.680 -> 4 (i32)
TLV-11[62]: 1.3.6.1.2.1.69.1.6.4.1.3.680 -> 2 (i32)
TLV-11[63]: 1.3.6.1.2.1.69.1.6.4.1.4.680 -> 1 (i32)
TLV-11[64]: 1.3.6.1.2.1.69.1.6.4.1.5.680 -> 1 (i32)
TLV-11[65]: 1.3.6.1.2.1.69.1.6.4.1.9.680 -> 224.0.0.22
TLV-11[66]: 1.3.6.1.2.1.69.1.6.4.1.10.680 -> 255.255.255.255
TLV-11[67]: 1.3.6.1.2.1.69.1.6.4.1.11.680 -> 17 (i32)
TLV-11[68]: 1.3.6.1.2.1.69.1.6.4.1.2.681 -> 4 (i32)
TLV-11[69]: 1.3.6.1.2.1.69.1.6.4.1.4.681 -> 0 (i32)
TLV-11[70]: 1.3.6.1.2.1.69.1.6.4.1.5.681 -> 1 (i32)
TLV-11[71]: 1.3.6.1.2.1.69.1.6.4.1.9.681 -> 232.10.10.0
TLV-11[72]: 1.3.6.1.2.1.69.1.6.4.1.10.681 -> 255.255.254.0
TLV-11[73]: 1.3.6.1.2.1.69.1.6.4.1.2.682 -> 4 (i32)
TLV-11[74]: 1.3.6.1.2.1.69.1.6.4.1.4.682 -> 1 (i32)
TLV-11[75]: 1.3.6.1.2.1.69.1.6.4.1.5.682 -> 3 (i32)
TLV-11[76]: 1.3.6.1.2.1.69.1.6.4.1.9.682 -> 10.128.0.0
TLV-11[77]: 1.3.6.1.2.1.69.1.6.4.1.10.682 -> 255.192.0.0
TLV-11[78]: 1.3.6.1.2.1.69.1.6.4.1.2.683 -> 4 (i32)
TLV-11[79]: 1.3.6.1.2.1.69.1.6.4.1.3.683 -> 2 (i32)
TLV-11[80]: 1.3.6.1.2.1.69.1.6.4.1.4.683 -> 1 (i32)
TLV-11[81]: 1.3.6.1.2.1.69.1.6.4.1.5.683 -> 1 (i32)
TLV-11[82]: 1.3.6.1.2.1.69.1.6.4.1.9.683 -> 224.0.0.9
TLV-11[83]: 1.3.6.1.2.1.69.1.6.4.1.10.683 -> 255.255.255.255
TLV-11[84]: 1.3.6.1.2.1.69.1.6.4.1.11.683 -> 17 (i32)
TLV-11[85]: 1.3.6.1.2.1.69.1.6.4.1.2.684 -> 4 (i32)
TLV-11[86]: 1.3.6.1.2.1.69.1.6.4.1.4.684 -> 1 (i32)
TLV-11[87]: 1.3.6.1.2.1.69.1.6.4.1.5.684 -> 1 (i32)
TLV-11[88]: 1.3.6.1.2.1.69.1.6.4.1.9.684 -> 224.0.0.0
TLV-11[89]: 1.3.6.1.2.1.69.1.6.4.1.10.684 -> 240.0.0.0
TLV-11[90]: 1.3.6.1.2.1.69.1.6.4.1.11.684 -> 17 (i32)
Time Of Day completed...
DefaultSnmpAgentClass::SystemTimeChangeEvent for SB5102 CM Agent w/ BRCM Factory Support
SB5102 CM Agent w/ BRCM Factory Support processing TLV-11's
SNMP packet sent to 10.43.231.60:225
90 TLV-11's OK.
Sending a REG-REQ to the CMTS...
Not logging event ID 2291949524, control for level 7 is 0.
Not logging event ID 2291949324, control for level 7 is 0.
Received a REG-RSP message from the CMTS...
0x000177dc [CmDocsisCtlThread] BcmCmDocsisCtlThread::RegRspMsgEvent: (CmDocsisCtlThread) 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 docsisNmAccessView
0x00017822 [CmDocsisCtlThread] BcmCmDocsisCtlThread::TestAndLaunchBpkm: (CmDocsisCtlThread) BPKM enabled. starting BPKM key requests.
SB5102 CM Event Log w/ BRCM Factory Support sending deferred async messages...
Done w/ deferred msgs
Not logging event ID 66040100, control for level 7 is 0.

CM> BPI initialization completed. Calling ConfigOperational().
Enabling network access for all CPE ports.

mot_scanList: Writing to Flash!
BcmCmDocsisStatusEventCodes::kCmIsOperational
Suspending SNMP Thread
0x00017cbe [CmDocsisCtlThread] BcmVendorCmApplication::StopDhcpServer: (VendorExtension CmApp) Shutting down DHCP Server...
0x00017cbe [CmDocsisCtlThread] BcmStandbySwitchThread::CmIsOperational: (Motorola Standby Switch Thread) Simulating a press of the standby switch to get the state configured properly.
0x00017cc8 [IGMP Thread] BcmIgmpThread::Starting Igmp Thread...: (IGMP Thread)
0x00017cc8 [Motorola Standby Switch Thread] BcmStandbySwitchThread::ThreadMain: (Motorola Standby Switch Thread) Standby switch was pressed!
0x00017cc8 [Motorola Standby Switch Thread] BcmStandbySwitchThread:TonguerocessSwitchEvent: (Motorola Standby Switch Thread) Leaving standby mode; restoring previous NACO and DHCP server states, and changing the LEDs.
0x00017cd2 [Motorola Standby Switch Thread] BcmVendorCmApplication::StopDhcpServer: (VendorExtension CmApp) Shutting down DHCP Server...
Not logging event ID 2296948624, control for level 7 is 0.
Not logging event ID 2300955525, control for level 7 is 0.

CM> Bandwidth request failure! Status = 0
Bandwidth request failure! Status = 0
0x0001da1a [CmDocsisCtlThread] BcmCmDocsisCtlThread::T4NoStationMaintEvent: (CmDocsisCtlThread) ERROR - no Station Maint map op -> restart error

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

0x0001da1a [CmDocsisCtlThread] BcmCmDocsisCtlThread::T4NoStationMaintEvent: (CmDocsisCtlThread) MOTOROLA-SPECIFIC -> REBOOTING IN CASE OF T4
DefaultSnmpAgentClass::ShutdownPendingEvent for SB5102 CM Agent w/ BRCM Factory 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 Unicast 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 [Motorola Corporation]: <2300955924> Modem Is Shutting Down and Rebooting...

CM> Bandwidth request failure! Status = 0
Stopping DHCP/ToD/TFTP (client requested)...
The ToD thread was stopped.
DHCPc: Releasing the lease with client id htype=1, value=00:26:24:e8:7d:e2
DHCPc: Sending Release packet; client id htype=1, value=00:26:24:e8:7d:e2
0x0001dc18 [DHCP Client Thread] BcmEcosIpHalIf::RemoveLeaseImpl: (IP Stack1 HalIf) Removing lease IP address 10.43.231.60 from IP stack 1
0x0001dc18 [DHCP Client Thread] BcmEcosIpHalIf::RemoveLeaseImpl: (IP Stack1 HalIf) This is the last address on the stack; shutting the stack down:numberOfAddresses=1
0x0001dc18 [DHCP Client Thread] BcmEcosIpHalIf::ShutdownIpStackImpl: (IP Stack1 HalIf)
Shutting down IP stack 1
12-09-2012, 10:03 PM
Find Reply
ABMJR Away
DOCSIS Genius
*****

Posts: 1,513
Threads: 16
Joined: Dec 2009
Reputation: 78
#7
RE: SB5101 wont connect to TW NYC
This is where it went to hell..

Quote:Logging event: Received Response to Broadcast Maintenance Request, But no Unicast 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 [Motorola Corporation]: <2300955924> Modem Is Shutting Down and Rebooting...

CM> Bandwidth request failure! Status = 0
Stopping DHCP/ToD/TFTP (client requested)...
The ToD thread was stopped.
DHCPc: Releasing the lease with client id htype=1, value=00:26:24:e8:7d:e2
DHCPc: Sending Release packet; client id htype=1, value=00:26:24:e8:7d:e2
0x0001dc18 [DHCP Client Thread] BcmEcosIpHalIf::RemoveLeaseImpl: (IP Stack1 HalIf) Removing lease IP address 10.43.231.60 from IP stack 1
0x0001dc18 [DHCP Client Thread] BcmEcosIpHalIf::RemoveLeaseImpl: (IP Stack1 HalIf) This is the last address on the stack; shutting the stack down:numberOfAddresses=1
0x0001dc18 [DHCP Client Thread] BcmEcosIpHalIf::ShutdownIpStackImpl: (IP Stack1 HalIf)
Shutting down IP stack 1
Knowledge=Power
12-09-2012, 10:07 PM
Find Reply
gcam77 Offline
Junior Member
**

Posts: 12
Threads: 2
Joined: Sep 2012
Reputation: 0
#8
RE: SB5101 wont connect to TW NYC
Thanks for the quick response. How do I go about fixing this?

(12-09-2012, 10:07 PM)ABMJR Wrote: This is where it went to hell..

Quote:Logging event: Received Response to Broadcast Maintenance Request, But no Unicast 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 [Motorola Corporation]: <2300955924> Modem Is Shutting Down and Rebooting...

CM> Bandwidth request failure! Status = 0
Stopping DHCP/ToD/TFTP (client requested)...
The ToD thread was stopped.
DHCPc: Releasing the lease with client id htype=1, value=00:26:24:e8:7d:e2
DHCPc: Sending Release packet; client id htype=1, value=00:26:24:e8:7d:e2
0x0001dc18 [DHCP Client Thread] BcmEcosIpHalIf::RemoveLeaseImpl: (IP Stack1 HalIf) Removing lease IP address 10.43.231.60 from IP stack 1
0x0001dc18 [DHCP Client Thread] BcmEcosIpHalIf::RemoveLeaseImpl: (IP Stack1 HalIf) This is the last address on the stack; shutting the stack down:numberOfAddresses=1
0x0001dc18 [DHCP Client Thread] BcmEcosIpHalIf::ShutdownIpStackImpl: (IP Stack1 HalIf)
Shutting down IP stack 1

12-09-2012, 10:11 PM
Find Reply
flint1 Offline
Junior Member
**

Posts: 2
Threads: 0
Joined: Sep 2012
Reputation: 0
#9
RE: SB5101 wont connect to TW NYC
same issue please help
12-09-2012, 10:50 PM
Find Reply
ABMJR Away
DOCSIS Genius
*****

Posts: 1,513
Threads: 16
Joined: Dec 2009
Reputation: 78
#10
RE: SB5101 wont connect to TW NYC
T4 Timeout No RNG-REQ Grant MAP Received by Cable Modem in 35 sec – Typically a Downstream Problem

T4 timeouts can usually be identified with downstream impairments causing the cable modem to miss receiving the RNG-REQ grant MAP transmitted to it
If T4 errors are impacting many modems off of a common leg, trouble shoot that leg
If T4 errors are just associated with one modem, look for low MER/level at that modem
T4 timeouts can also be associated with a CMTS that has extremely high utilization i.e. >95% depending on the vendor and firmware version
Rule of thumb for CMTS utilization is 80% to allow for peak usage periods
It is highly unlikely that T4 timeouts are associated with any upstream impairments

Knowledge=Power
12-09-2012, 10:52 PM
Find Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)