nopaste
HomeAll pastesPopular pastesRecent pastes

Public paste
sb5100MOD bpi disabled
By: flymods | Date: Jun 3 2010 00:41 | Format: None | Expires: never | Size: 10.07 KB | Hits: 1524
Edit & repaste | raw paste | Request removal

  1. =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2010.06.02 19:32:12 =~=~=~=~=~=~=~=~=~=~=~=
  2. SB5100MoD by ToM - Embedded Telnet Server
  3.  
  4. login: SB5100MOD
  5. password:
  6. Welcome to the Broadcom CLI (command-line interpreter).
  7. To access the native VxWorks shell, type 'shell'.
  8. Attempting Downstream FEC lock @ freq= 231000000 Hz, QAM64
  9.  
  10. CM> Attempting Downstream FEC lock @ freq= 225000000 Hz, QAM64
  11. Attempting Downstream FEC lock @ freq= 219000000 Hz, QAM64
  12. Attempting Downstream FEC lock @ freq= 213000000 Hz, QAM64
  13. Attempting Downstream FEC lock @ freq= 207000000 Hz, QAM64
  14. Attempting Downstream FEC lock @ freq= 201000000 Hz, QAM64
  15. Attempting Downstream FEC lock @ freq= 195000000 Hz, QAM64
  16. Attempting Downstream FEC lock @ freq= 189000000 Hz, QAM64
  17. Attempting Downstream FEC lock @ freq= 183000000 Hz, QAM64
  18. Attempting Downstream FEC lock @ freq= 177000000 Hz, QAM64
  19. Attempting Downstream FEC lock @ freq= 171000000 Hz, QAM64
  20. Attempting Downstream FEC lock @ freq= 165000000 Hz, QAM64
  21. Attempting Downstream FEC lock @ freq= 159000000 Hz, QAM64
  22. Attempting Downstream FEC lock @ freq= 153000000 Hz, QAM64
  23. Attempting Downstream FEC lock @ freq= 147000000 Hz, QAM64
  24. Attempting Downstream FEC lock @ freq= 141000000 Hz, QAM64
  25. Attempting Downstream FEC lock @ freq= 135000000 Hz, QAM64
  26. Go back to 1st favorite
  27. Attempting Downstream FEC lock @ freq= 129000000 Hz, QAM64
  28. Attempting Downstream FEC lock @ freq= 123000000 Hz, QAM64
  29. Attempting Downstream FEC lock @ freq= 501000000 Hz, QAM256
  30. Attempting Downstream FEC lock @ freq= 507000000 Hz, QAM256
  31. Attempting Downstream FEC lock @ freq= 513000000 Hz, QAM256
  32. Attempting Downstream FEC lock @ freq= 519000000 Hz, QAM256
  33. Attempting Downstream FEC lock @ freq= 525000000 Hz, QAM256
  34. Attempting Downstream FEC lock @ freq= 531000000 Hz, QAM256
  35. Attempting Downstream FEC lock @ freq= 537000000 Hz, QAM256
  36. Attempting Downstream FEC lock @ freq= 543000000 Hz, QAM256
  37. Attempting Downstream FEC lock @ freq= 549000000 Hz, QAM256
  38. Attempting Downstream FEC lock @ freq= 555000000 Hz, QAM256
  39. Attempting Downstream FEC lock @ freq= 561000000 Hz, QAM256
  40. Attempting Downstream FEC lock @ freq= 567000000 Hz, QAM256
  41. Attempting Downstream FEC lock @ freq= 573000000 Hz, QAM256
  42. Attempting Downstream FEC lock @ freq= 579000000 Hz, QAM256
  43. Attempting Downstream FEC lock @ freq= 585000000 Hz, QAM256
  44. Attempting Downstream FEC lock @ freq= 591000000 Hz, QAM256
  45. Attempting Downstream FEC lock @ freq= 597000000 Hz, QAM256
  46. Attempting Downstream FEC lock @ freq= 603000000 Hz, QAM256
  47. Attempting Downstream FEC lock @ freq= 609000000 Hz, QAM256
  48. 0x00009420 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::SyncDsLockOk:  (CmDocsisCtlThread) Locked on the downstream.  Waiting for UCDs...
  49.  
  50. ******************************************
  51.             DOWNSTREAM STATUS
  52. ******************************************
  53.   Tuner Frequency = 609000000 Hz
  54.    Carrier Offset = -14 Hz
  55.       Symbol rate = 5360537 sym/sec
  56.               SNR = 34 dB
  57.          QAM Mode = QAM256
  58.         Tuner AGC = 0xfff00000
  59.            IF AGC = 0x84274a80
  60.       Power Level = -12 dB
  61.               QAM = LOCKED
  62.               FEC = LOCKED
  63. ******************************************
  64.  
  65.  
  66. CM>
  67. Received a UCD for Upstream Channel 1!
  68.  
  69. Received a UCD for Upstream Channel 2!
  70.  
  71. Received a UCD for Upstream Channel 3!
  72.  
  73. Received a UCD for Upstream Channel 4!
  74.  
  75. Received a UCD for Upstream Channel 4!
  76. Selecting UCD for Us Channel 3
  77.  
  78. BcmCmUsPhyOverheadSettings::ComputeReqDataPhyToMacTable() burst descriptor not found for kReqDataIUC.
  79. Upstream Frequency =  29504000
  80. Found QAM16 =  true
  81. 0x00009e48 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::TestAndLaunchDsTimeSync:  (CmDocsisCtlThread) entering...
  82.        new_us_scdma_enabled = false
  83.     fLastDsClockModeIsScdma = false
  84.         fCmDsTargetingState = kDsPhyOkUsUcdPending
  85.              IsDccContext() = false
  86.  
  87. 0x00009e48 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::TestAndLaunchDsTimeSync:  (CmDocsisCtlThread) starting ds time sync acquisition...
  88.  
  89. Received a UCD for Upstream Channel 1!
  90.  
  91. Received a UCD for Upstream Channel 2!
  92.  
  93. Received a UCD for Upstream Channel 3!
  94. 0x0000a0b4 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::SyncDsSyncOk:  (CmDocsisCtlThread) downstream time sync acquired...
  95. 0x0000a0b4 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::DsSyncOkResumeUsInit:  (CmDocsisCtlThread) pre-REG upstream target case...starting initial ranging.
  96. Beginning initial ranging...
  97. Using default initial upstream power = 8.0 dBmV
  98. 0x0000a0b4 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::SyncDsSyncOk:  (CmDocsisCtlThread) rx unexpected kDsSyncOk indication...
  99. Logging event: T501.0 Acquired Downstream (609000000 Hz)........ SUCCESS
  100. v1Trap: cmTrapLog 192.168.100.1->192.168.100.10:162, cmty="public"
  101. Adjusting the initial ranging power to 33.0 dBmV...
  102. Logging event: No Ranging Response received - T3 time-out
  103.  
  104. CM> Adjusting the initial ranging power to 46.0 dBmV...
  105. Logging event: No Ranging Response received - T3 time-out
  106.  
  107. CM> Adjusting the initial ranging power to 21.0 dBmV...
  108. Logging event: No Ranging Response received - T3 time-out
  109.  
  110. CM> Adjusting the initial ranging power to 52.0 dBmV...
  111. Logging event: No Ranging Response received - T3 time-out
  112.  
  113. CM> Adjusting the initial ranging power to 39.0 dBmV...
  114. Logging event: No Ranging Response received - T3 time-out
  115.  
  116. CM> Adjusting the initial ranging power to 27.0 dBmV...
  117. Logging event: No Ranging Response received - T3 time-out
  118.  
  119. CM> Adjusting the initial ranging power to 14.0 dBmV...
  120. Logging event: No Ranging Response received - T3 time-out
  121.  
  122. CM> Adjusting the initial ranging power to 55.0 dBmV...
  123. Logging event: No Ranging Response received - T3 time-out
  124.  
  125. CM> Adjusting the initial ranging power to 49.0 dBmV...
  126. Logging event: No Ranging Response received - T3 time-out
  127.  
  128. CM> Adjusting the initial ranging power to 42.0 dBmV...
  129. Logging event: No Ranging Response received - T3 time-out
  130.  
  131. CM> Adjusting the initial ranging power to 36.0 dBmV...
  132. Logging event: No Ranging Response received - T3 time-out
  133.  
  134. CM> Adjusting the initial ranging power to 30.0 dBmV...
  135. Logging event: No Ranging Response received - T3 time-out
  136.  
  137. CM> Adjusting the initial ranging power to 24.0 dBmV...
  138. Logging event: No Ranging Response received - T3 time-out
  139.  
  140. CM> Adjusting the initial ranging power to 17.0 dBmV...
  141. Logging event: No Ranging Response received - T3 time-out
  142.  
  143. CM> Adjusting the initial ranging power to 11.0 dBmV...
  144. Logging event: No Ranging Response received - T3 time-out
  145.  
  146. CM> Adjusting the initial ranging power to 58.0 dBmV...
  147. Logging event: No Ranging Response received - T3 time-out
  148.  
  149. CM> 0x00016bc0 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::T3NoRngRspEvent:  (CmDocsisCtlThread) ERROR - No initial ranging response from CMTS.
  150. 0x00016bc0 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::CommonRngErrorHandler:  (CmDocsisCtlThread)
  151. 0x00016bc0 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::TargetNextUsChan:  (CmDocsisCtlThread)
  152. 0x00016bc0 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::ResetRngState:  (CmDocsisCtlThread)
  153. Logging event: No Ranging Response received - T3 time-out
  154. Logging event: Init RANGING Critical Ranging Request Retries exhausted
  155.  
  156. CM>
  157. Received a UCD for Upstream Channel 1!
  158.  
  159. Received a UCD for Upstream Channel 2!
  160.  
  161. Received a UCD for Upstream Channel 3!
  162.  
  163. Received a UCD for Upstream Channel 4!
  164.  
  165. Received a UCD for Upstream Channel 4!
  166. Selecting UCD for Us Channel 1
  167.  
  168. BcmCmUsPhyOverheadSettings::ComputeReqDataPhyToMacTable() burst descriptor not found for kReqDataIUC.
  169. Upstream Frequency =  29504000
  170. Found QAM16 =  true
  171. 0x000178b8 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::TestAndLaunchDsTimeSync:  (CmDocsisCtlThread) entering...
  172.        new_us_scdma_enabled = false
  173.     fLastDsClockModeIsScdma = false
  174.         fCmDsTargetingState = kDsOkUsPending
  175.              IsDccContext() = false
  176.  
  177. 0x000178b8 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::TestAndLaunchDsTimeSync:  (CmDocsisCtlThread) ds time sync should be ok.  resume us init now.
  178. 0x000178b8 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::DsSyncOkResumeUsInit:  (CmDocsisCtlThread) pre-REG upstream target case...starting initial ranging.
  179. Beginning initial ranging...
  180. Using default initial upstream power = 8.0 dBmV
  181.  
  182. Received a UCD for Upstream Channel 1!
  183.  
  184. Received a UCD for Upstream Channel 2!
  185.  
  186. Received a UCD for Upstream Channel 3!
  187. UCD change detected.  Status = 0
  188. Logging event: T501.0 Acquired Downstream (609000000 Hz)........ SUCCESS
  189. v1Trap: cmTrapLog 192.168.100.1->192.168.100.10:162, cmty="public"
  190.  
  191. CM> Adjusting the initial ranging power to 33.0 dBmV...
  192. Logging event: No Ranging Response received - T3 time-out
  193. Adjusting the initial ranging power to 46.0 dBmV...
  194. Logging event: No Ranging Response received - T3 time-out
  195.  
  196. CM> Adjusting the initial ranging power to 21.0 dBmV...
  197. Logging event: No Ranging Response received - T3 time-out
  198.  
  199. CM> Adjusting the initial ranging power to 52.0 dBmV...
  200. Logging event: No Ranging Response received - T3 time-out
  201.  
  202. CM> Adjusting the initial ranging power to 39.0 dBmV...
  203. Logging event: No Ranging Response received - T3 time-out
  204.  
  205. CM> Adjusting the initial ranging power to 27.0 dBmV...
  206. Logging event: No Ranging Response received - T3 time-out
  207.  
  208. CM> Adjusting the initial ranging power to 14.0 dBmV...
  209. Logging event: No Ranging Response received - T3 time-out
  210.  
  211. CM> Adjusting the initial ranging power to 55.0 dBmV...
  212. Logging event: No Ranging Response received - T3 time-out
  213.  
  214. CM> Adjusting the initial ranging power to 49.0 dBmV...
  215. Logging event: No Ranging Response received - T3 time-out
  216.  
  217. CM> Adjusting the initial ranging power to 42.0 dBmV...
  218. Logging event: No Ranging Response received - T3 time-out
  219.  
  220. CM> Adjusting the initial ranging power to 36.0 dBmV...
  221. Logging event: No Ranging Response received - T3 time-out
  222.  
  223. CM> Adjusting the initial ranging power to 30.0 dBmV...
  224. Logging event: No Ranging Response received - T3 time-out
  225.  
  226. CM> Adjusting the initial ranging power to 24.0 dBmV...
  227. Logging event: No Ranging Response received - T3 time-out
  228.  
  229. CM>
Latest pastes
Pills gen in behalf of patients. What side effects can this medication cause? cmvspnhcmgay
19 hours ago
Undefined
8 days ago
Undefined
10 days ago
Undefined
20 days ago
Undefined
21 days ago

What's new | Credits | Contact