Ver la versión completa : [Urgente] SB5100 - No agarra Online (Casi Solucionado)
ElCucoArg
19/09/2008, 16:00
Hola gente nuevamente,
Estoy con un problema.... Tengo un SB5100 al cual desde ayer al medio dia se me desconectó... y tanto con el firm sigma, como con el original y con mac mia o de otro nodo y tambien con cfg forzado y no forzado me pasa lo mismo.....
No me levanta internet... se conectan todas las luces y la de online nunca queda enganchada..... (tengo el log pero me lo olvidé en cassa con el pendrive..., cuadno lo tenga lo subo) .... alguien sabe que puede ser....
y si es un problema del proveedor como hago para enterarme... sin que me descubran :D
Saludos y gracias
ElCucoArg
19/09/2008, 18:41
Me informaron que mis vecinos no tienen problema... alguien sabe que puede ser/
ElCucoArg
19/09/2008, 19:24
Bueno gente aca consegui el log se los paso
2008-09-19 07:43:18 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:43:16 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-09-19 07:43:16 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:43:13 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-09-19 07:43:12 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:43:10 7-Information Ô7954.16 Registration failure, re-scanning downstream
2008-09-19 07:43:10 7-Information D507.0 Retrieved Time....... SUCCESS
2008-09-19 07:43:10 7-Information D509.0 Retrieved TFTP Config Lugash1IP_Mot_1.1 SUCCESS
2008-09-19 07:43:10 3-Critical I402.0 TLV-11 - Illegal Set operation failed
2008-09-19 07:43:09 7-Information D511.0 Retrieved DHCP .......... SUCCESS
2008-09-19 07:43:05 7-Information T500.0 Acquired Upstream .......... SUCCESS
2008-09-19 07:43:04 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-09-19 07:43:04 7-Information T501.0 Acquired Downstream (585000000 Hz)........ SUCCESS
2008-09-19 07:43:04 3-Critical U002.0 UCD invalid or channel unusable
2008-09-19 07:43:02 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:43:01 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-09-19 07:43:00 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:43:00 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-09-19 07:43:00 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:42:59 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-09-19 07:42:59 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:42:58 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-09-19 07:42:56 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:42:56 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-09-19 07:42:55 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:42:55 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-09-19 07:42:55 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:42:54 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-09-19 07:42:53 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:42:53 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-09-19 07:42:50 7-Information Ô7954.16 Registration failure, re-scanning downstream
2008-09-19 07:42:50 7-Information D507.0 Retrieved Time....... SUCCESS
2008-09-19 07:42:50 7-Information D509.0 Retrieved TFTP Config Lugash1IP_Mot_1.1 SUCCESS
2008-09-19 07:42:50 3-Critical I402.0 TLV-11 - Illegal Set operation failed
2008-09-19 07:42:50 7-Information D511.0 Retrieved DHCP .......... SUCCESS
2008-09-19 07:42:43 7-Information T500.0 Acquired Upstream .......... SUCCESS
2008-09-19 07:42:42 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-09-19 07:42:41 7-Information T501.0 Acquired Downstream (585000000 Hz)........ SUCCESS
2008-09-19 07:42:41 3-Critical U002.0 UCD invalid or channel unusable
2008-09-19 07:42:39 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:42:39 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-09-19 07:42:38 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:42:25 7-Information Ô7954.16 Registration failure, re-scanning downstream
2008-09-19 07:42:25 7-Information D507.0 Retrieved Time....... SUCCESS
2008-09-19 07:42:25 7-Information D509.0 Retrieved TFTP Config Lugash1IP_Mot_1.1 SUCCESS
2008-09-19 07:42:25 3-Critical I402.0 TLV-11 - Illegal Set operation failed
2008-09-19 07:42:24 7-Information D511.0 Retrieved DHCP .......... SUCCESS
2008-09-19 07:42:18 7-Information T500.0 Acquired Upstream .......... SUCCESS
2008-09-19 07:42:17 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-09-19 07:42:17 7-Information T501.0 Acquired Downstream (585000000 Hz)........ SUCCESS
2008-09-19 07:42:17 3-Critical U002.0 UCD invalid or channel unusable
2008-09-19 07:42:15 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:42:00 7-Information Ô7954.16 Registration failure, re-scanning downstream
2008-09-19 07:42:00 7-Information D507.0 Retrieved Time....... SUCCESS
2008-09-19 07:42:00 7-Information D509.0 Retrieved TFTP Config Lugash1IP_Mot_1.1 SUCCESS
2008-09-19 07:42:00 3-Critical I402.0 TLV-11 - Illegal Set operation failed
2008-09-19 07:41:59 7-Information D511.0 Retrieved DHCP .......... SUCCESS
2008-09-19 07:41:55 7-Information T500.0 Acquired Upstream .......... SUCCESS
2008-09-19 07:41:55 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-09-19 07:41:54 7-Information T501.0 Acquired Downstream (585000000 Hz)........ SUCCESS
2008-09-19 07:41:54 3-Critical U002.0 UCD invalid or channel unusable
2008-09-19 07:41:52 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:41:47 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-09-19 07:41:47 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:41:41 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-09-19 07:41:41 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:41:40 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-09-19 07:41:40 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:41:39 7-Information Ô7954.16 Registration failure, re-scanning downstream
2008-09-19 07:41:39 7-Information D507.0 Retrieved Time....... SUCCESS
2008-09-19 07:41:39 7-Information D509.0 Retrieved TFTP Config Lugash1IP_Mot_1.1 SUCCESS
2008-09-19 07:41:39 3-Critical I402.0 TLV-11 - Illegal Set operation failed
2008-09-19 07:41:37 7-Information D511.0 Retrieved DHCP .......... SUCCESS
2008-09-19 07:41:30 7-Information T500.0 Acquired Upstream .......... SUCCESS
2008-09-19 07:41:30 3-Critical R002.0 No Ranging Response received - T3 time-out
2008-09-19 07:41:29 7-Information T501.0 Acquired Downstream (585000000 Hz)........ SUCCESS
2008-09-19 07:41:29 3-Critical U002.0 UCD invalid or channel unusable
2008-09-19 07:41:27 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:41:25 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-09-19 07:41:25 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:41:25 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-09-19 07:41:24 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:41:23 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-09-19 07:41:23 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:41:22 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-09-19 07:41:22 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:41:22 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-09-19 07:41:21 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:41:20 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-09-19 07:41:19 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:41:19 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-09-19 07:41:18 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:41:18 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-09-19 07:41:17 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:41:16 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-09-19 07:41:15 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-09-19 07:41:15 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-09-19 07:41:13 7-Information Ô7954.16 Registration failure, re-scanning downstream
2008-09-19 07:41:13 7-Information D507.0 Retrieved Time....... SUCCESS
2008-09-19 07:41:13 7-Information D509.0 Retrieved TFTP Config Lugash1IP_Mot_1.1 SUCCESS
y asi tengo la configuración.:
Frequency Plan: North American Standard/HRC/IRC
Upstream Channel ID : 4
Frequency (Hz): 585000000
Ya le puse para que me lo resetea y estuve MUCHAS horas y no levantó nada...
que puede ser gente...... AYUDAAAA!!!!
Al ser de esa zona y tema concreto, lo movemos a seccion correspondiente...
ElCucoArg
19/09/2008, 20:47
El Servidor que tengo es fibertel. pero aparentemente no es problema de fibertel ya que no tienen problemas mis vecinos.... (agregué el dato por si a alguien le servía de info.... pero no creo que sea problema de fibertel)
Ok, no me fije en esa última nota.
Ponle una mac de 1.0 que tengas antigua, pero de hace tiempo (asegurate que es operativa), con firm original mejor.
Salu2.
ElCucoArg
20/09/2008, 02:53
Hola....
No tengo ninguna mac 1.0 ... y menos que menos activa... trate de levantar con un cfg de 1.0 que simre anduvo y ya no lo encontro mas .... o sea que no creo que haya macs 1.0 o por lo menos de que yo este enterado.... (sniffeando tampoco enconte)
Aca les dejo el log que aparecio en telnet a ver si a alguien les sirve de algo...
Ya no se que mas probar o que puede ser el problema.... mañana voy a llevar el modem a lo de un amigo y viceversa... pero no se que va a pasar
A alguien se le ocurre otra cosa?
por k puede ser k no este levantando la frec... ? (la potencia esta bien... anda en -1, -2db...)
Gracias por avisamre
Te edite el post, en dicho log aparecia repetidamente muchas veces tu mac, y el log era muy grande como para buscar todas las lineas donde aparecia la mac.
Puedes poner el log mas corto, lo que interesa es donde aparece el error, pero fijate de no postear la mac.
Salu2.
ElCucoArg
20/09/2008, 20:40
Alguien tiene idea que puede llegar ser con la ayuda de estos dos logs?... No tengo posiblidad de probar mac 1.0
ElCucoArg
20/09/2008, 23:12
Bueno gente les comento las novedades.... probé el modem de un amigo que tambien esta con lo mismo pero con un sb4200 en mi casa y funciono de una.... y luego probé el modme mio aca en lo de mi amigo y tuve el mismo problema.... (estamos en nodos distnitos!)
Fijate bien porque tuve que volver a borrarte el log, tu mac empieza por 00:00.... y volvio a aparecer...
ElCucoArg
21/09/2008, 18:25
Bueno ... perdon... aca va el log bien depurado
TCNISO Embedded Telnet Server
login:
password:
Welcome to the Broadcom CLI (command-line interpreter).
To access the native VxWorks shell, type 'shell'.
CM> 0x00018e02 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::SyncRxMacMgtMsg: (CmDocsisCtlThread) WARNING - Unknown message type received (33)! Ignoring...
DHCPc: Received an Offer from DHCP server xx:xx:xx:xx:xx:xx (10.17.1.1); lease client id htype=1, value=xx:xx:xx:xx:xx:xx
CM> 0x000195d2 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::SyncRxMacMgtMsg: (CmDocsisCtlThread) WARNING - Unknown message type received (33)! Ignoring...
DHCPc: Timed out waiting for offers for lease with client id htype=1, value=xx:xx:xx:xx:xx:xx
DHCPc: Sending Request packet; client id htype=1, value=xx:xx:xx:xx:xx:xx
DHCPc: Received an Ack from DHCP server xx:xx:xx:xx:xx:xx (10.17.1.1); lease client id htype=1, value=xx:xx:xx:xx:xx:xx
Current IP address is default 169.0.0.1; removing existing route...
0x000195fa ['DHCP Client Thread' id=0x807c8fa0] BcmVxIpHalIf::ConfigureLeaseImpl: (IP Stack1 HalIf)
Configuring IP stack 1:
IP Address = 10.17.27.14
Subnet Mask = 255.255.0.0
Router = 10.17.1.1
DHCP completed successfully!
DHCP Settings:
Client Id = htype=1, value=xx:xx:xx:xx:xx:xx
State = Bound (4)
Static Lease = false
AutoConfig Mode = IP, Subnet and Router
XID = 0x6182
Number of Tries = 0
Max Discover Tries = 6
Max Request Tries = 6
DHCP server MAC addr = xx:xx:xx:xx:xx:xx
My offered IP address = 10.17.27.14
(1) Subnet Mask = 255.255.0.0
(3) Router IP address = 10.17.1.1
(54) DHCP Server IP address = 172.20.2.11
(82) Relay Agent IP address = 10.17.1.1
TFTP Server IP address = 172.20.2.11
CM Configuration file = 'Clancy1IP_Arris_1.1_BPI'
(2) UTC Time Offset = -10800 seconds
(4) Time Server IP address = 172.20.2.11
(7) Log Server IP address = 172.20.2.11
(51) Lease time = 2202117 seconds
(58) T1 (renew) = 1101058 seconds
(59) T2 (rebind) = 1926852 seconds
Lease is infinite = false
CmSnmpAgent::IpAddressAcquiredEvent for SB5100 CM Agent
IP addr = 10.17.27.14
SB5100 CM Agent ConfigIp: Ip=10.17.27.14, Subnet=255.255.0.0, Gateway=10.17.1.1
CM> Starting Time Of Day...
0x000199ec ['CmDocsisIpThread' id=0x807c3b50] BcmDocsisTimeOfDayThread::SetTodServerIpAddress: (Time Of Day Thread) ToD servers: 172.20.2.11
Connecting to ToD server 172.20.2.11...
Sending UDP ToD request to server...
Logging event: D511.0 Retrieved DHCP .......... SUCCESS
Sending syslog message from IF 1 to 192.168.100.10:
<134> CABLEMODEM [Motorola Corporation]: <2223898627> D511.0 Retrieved DHCP .......... SUCCESS
v1Trap: cmTrapLog 192.168.100.1->192.168.100.10:162, cmty="public"
v1Trap: cmTrapLog 10.17.27.14->192.168.100.10:162, cmty="public"
0x00019ae6 ['Time Of Day Thread' id=0x807c55d0] BcmDocsisTimeOfDayThread::HandleToD: (Time Of Day Thread) WARNING - Timed out waiting for a response from the ToD server.
Waiting 2000 ms before trying this server again...
Logging event: ToD request sent- No Response received
Sending syslog message from IF 1 to 192.168.100.10:
<131> CABLEMODEM [DOCSIS]: <68000403> ToD request sent- No Response received
Starting Tftp of configuration file...
Opening file 'Clancy1IP_Arris_1.1_BPI' on 172.20.2.11...
Forcing to download Cfg file: Wiggum1IP_Mot_1.1
v1Trap: docsDevCmTODFailTrap 192.168.100.1->192.168.100.10:162, cmty="public"
v1Trap: docsDevCmTODFailTrap 10.17.27.14->192.168.100.10:162, cmty="public"
tftpInit: Tftp outbound interface flag (1024)
Connected to 172.20.2.11 [69]
mode set to octet.
getting from 172.20.2.11:Wiggum1IP_Mot_1.1 [octet]
tftpSend: Attempt #(1) Backoff (2) tickCount (10533) blkReply (1)
ing 1.3.6.1.2.1.69.1.2.1.2.12 to 24.232.0.44
Not setting 1.3.6.1.2.1.69.1.2.1.3.12 to 255.255.255.255
Not setting 1.3.6.1.2.1.69.1.2.1.4.12 to mA6u0XkL1PnS
Not setting 1.3.6.1.2.1.69.1.2.1.5.12 to 3
Not setting 1.3.6.1.2.1.69.1.2.1.6.12 to @
Not setting 1.3.6.1.2.1.69.1.2.1.7.12 to 4
Not setting 1.3.6.1.2.1.69.1.2.1.2.21 to 10.200.252.5
Not setting 1.3.6.1.2.1.69.1.2.1.3.21 to 255.255.255.255
Not setting 1.3.6.1.2.1.69.1.2.1.4.21 to mA6u0XkL1PnS
Not setting 1.3.6.1.2.1.69.1.2.1.5.21 to 3
Not setting 1.3.6.1.2.1.69.1.2.1.6.21 to @
Not setting 1.3.6.1.2.1.69.1.2.1.7.21 to 4
Not setting 1.3.6.1.2.1.69.1.2.1.2.20 to 10.200.252.0
Not setting 1.3.6.1.2.1.69.1.2.1.3.20 to 255.255.255.0
Not setting 1.3.6.1.2.1.69.1.2.1.4.20 to q9Ei5uS4e3H8
Not setting 1.3.6.1.2.1.69.1.2.1.5.20 to 2
Not setting 1.3.6.1.2.1.69.1.2.1.6.20 to @
Not setting 1.3.6.1.2.1.69.1.2.1.7.20 to 4
Not setting 1.3.6.1.2.1.69.1.2.1.2.60 to 172.20.3.0
Not setting 1.3.6.1.2.1.69.1.2.1.3.60 to 255.255.255.0
Not setting 1.3.6.1.2.1.69.1.2.1.4.60 to q9Ei5uS4e3H8
Not setting 1.3.6.1.2.1.69.1.2.1.5.60 to 2
Not setting 1.3.6.1.2.1.69.1.2.1.6.60 to @
Not setting 1.3.6.1.2.1.69.1.2.1.7.60 to 4
Invalid TLV-11's: 2 wrong values, 0 duplicate sets.
But since we're in FACTORY mode we'll allow it.
MAX CPE per CM is being set to 2
Sending a REG-REQ to the CMTS...
Tftp read ZERO bytes, may have reached end of file.
Config file was read! IP Initialization completed...
Test of 1.3.6.1.2.1.69.1.2.1.7.11 to 4 failed w/ error code INCONSISTENT_VALUE
Test of 1.3.6.1.2.1.69.1.2.1.7.10 to 4 failed w/ error code INCONSISTENT_VALUE
1.3.6.1.4.1.1166.1.19.3.2.3.0 not found, ignoring without error.
1.3.6.1.4.1.1166.1.19.51.1.1.1.3.0 not found, ignoring without error.
1.3.6.1.4.1.1166.1.19.52.1.2.1.2.13.0 not found, ignoring without error.
Not setting 1.3.6.1.2.1.69.1.6.4.1.2.20 to 4
Not setting 1.3.6.1.2.1.69.1.6.4.1.3.20 to 1
.
.
.
Not setting 1.3.6.1.2.1.69.1.2.1.2.10 to 24.232.0.0
Not setting 1.3.6.1.2.1.69.1.2.1.3.10 to 255.255.255.0
Not setting 1.3.6.1.2.1.69.1.2.1.4.10 to q9Ei5uS4e3H8
Not setting 1.3.6.1.2.1.69.1.2.1.5.10 to 2
Not setting 1.3.6.1.2.1.69.1.2.1.6.10 to @
Not settLogging event: TLV-11 - unrecognized OID
Received a REG-RSP message from the CMTS...
0x00019d02 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::RegRspMsgEvent: (CmDocsisCtlThread) ERROR -
REG-RSP response code NOT ok! rsp code = 2 (kRejUnrecognizedConfigSetting)
0x00019d02 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::SyncRestartErrorEvent: (CmDocsisCtlThread)
Sending syslog message from IF 1 to 192.168.100.10:
<133> CABLEMODEM [DOCSIS]: <73040100> TLV-11 - unrecognized OID
v1Trap: docsDevCmInitTLVUnknownTrap 192.168.100.1->192.168.100.10:162, cmty="public"
v1Trap: docsDevCmInitTLVUnknownTrap 10.17.27.14->192.168.100.10:162, cmty="public"
Logging event: TLV-11 - unrecognized OID
Sending syslog message from IF 1 to 192.168.100.10:
<133> CABLEMODEM [DOCSIS]: <73040100> TLV-11 - unrecognized OID
v1Trap: docsDevCmInitTLVUnknownTrap 192.168.100.1->192.168.100.10:162, cmty="public"
v1Trap: docsDevCmInitTLVUnknownTrap 10.17.27.14->192.168.100.10:162, cmty="public"
Deleting DOCSIS 1.0 CoS Settings for SID 0x12a
0x00019dd4 ['CmDocsisCtlThread' id=0x807bda80] BcmDocsisCmHalIf::DeleteAllServiceFlows: (DOCSIS CableModem HalIf) Deleting all Upstream and Downstream Service Flows, along with associated Classifiers and P
HS rules...
Stopping DHCP/ToD/TFTP (client requested)...
Logging event: TLV-11 - unrecognized OID
Sending syslog message from IF 1 to 192.168.100.10:
<133> CABLEMODEM [DOCSIS]: <73040100> TLV-11 - unrecognized OID
v1Trap: docsDevCmInitTLVUnknownTrap 192.168.100.1->192.168.100.10:162, cmty="public"
v1Trap: docsDevCmInitTLVUnknownTrap 10.17.27.14->192.168.100.10:162, cmty="public"
Logging event: TLV-11 - Illegal Set operation failed
Sending syslog message from IF 1 to 192.168.100.10:
<130> CABLEMODEM [DOCSIS]: <73040200> TLV-11 - Illegal Set operation failed
Logging event: D509.0 Retrieved TFTP Config Clancy1IP_Arris_1.1_BPI SUCCESS
Sending syslog message from IF 1 to 192.168.100.10:
<134> CABLEMODEM [Motorola Corporation]: <2223898626> D509.0 Retrieved TFTP Config Clancy1IP_Arris_1.1_BPI SUCCESS
v1Trap: cmTrapLog 192.168.100.1->192.168.100.10:162, cmty="public"
v1Trap: cmTrapLog 10.17.27.14->192.168.100.10:162, cmty="public"
Logging event: Registration failure, re-scanning downstream
Sending syslog message from IF 1 to 192.168.100.10:
<134> CABLEMODEM [Motorola Corporation]: <2436694040> Registration failure, re-scanning downstream
CM> Connecting to ToD server 172.20.2.11...
Sending UDP ToD request to server...
CM> 0x0001a3b0 ['Time Of Day Thread' id=0x807c55d0] BcmDocsisTimeOfDayThread::HandleToD: (Time Of Day Thread) WARNING - Timed out waiting for a response from the ToD server.
Waiting 2000 ms before trying this server again...
Logging event: ToD request sent- No Response received
Sending syslog message from IF 1 to 192.168.100.10:
<131> CABLEMODEM [DOCSIS]: <68000403> ToD request sent- No Response received
v1Trap: docsDevCmTODFailTrap 192.168.100.1->192.168.100.10:162, cmty="public"
v1Trap: docsDevCmTODFailTrap 10.17.27.14->192.168.100.10:162, cmty="public"
CM> Connecting to ToD server 172.20.2.11...
Sending UDP ToD request to server...
CM> 0x0001ac7a ['Time Of Day Thread' id=0x807c55d0] BcmDocsisTimeOfDayThread::HandleToD: (Time Of Day Thread) WARNING - Timed out waiting for a response from the ToD server.
Waiting 2000 ms before trying this server again...
Logging event: ToD request sent- No Response received
Sending syslog message from IF 1 to 192.168.100.10:
<131> CABLEMODEM [DOCSIS]: <68000403> ToD request sent- No Response received
v1Trap: docsDevCmTODFailTrap 192.168.100.1->192.168.100.10:162, cmty="public"
v1Trap: docsDevCmTODFailTrap 10.17.27.14->192.168.100.10:162, cmty="public"
CM> 0x0001b44a ['Time Of Day Thread' id=0x807c55d0] BcmDocsisTimeOfDayThread::HandleTod: (Time Of Day Thread) WARNING - Exceeded max number of ToD retries for all servers. Waiting for period timer to expi
re...
0x0001b44a ['Time Of Day Thread' id=0x807c55d0] BcmDocsisTimeOfDayThread::HandleTod: (Time Of Day Thread) WARNING - Period timer expired. Trying ToD again...
Aborted ToD acquisition due to client request...
The ToD thread was stopped.
DHCPc: Releasing the lease with client id htype=1, value=xx:xx:xx:xx:xx:xx
DHCPc: Sending Release packet; client id htype=1, value=xx:xx:xx:xx:xx:xx
0x0001b44a ['DHCP Client Thread' id=0x807c8fa0] BcmDhcpClientIf::SendDhcpPacket: (DHCP ClientIf for IP Stack1) WARNING - Failed to send packet!
0x0001b44a ['DHCP Client Thread' id=0x807c8fa0] BcmDhcpClientIf::SendRelease: (DHCP ClientIf for IP Stack1) WARNING - Failed to create/send Release packet! Oh, well, no biggie...
0x0001b44a ['DHCP Client Thread' id=0x807c8fa0] BcmVxIpHalIf::RemoveLeaseImpl: (IP Stack1 HalIf) Removing lease IP address 10.17.27.14 from IP stack 1
0x0001b44a ['DHCP Client Thread' id=0x807c8fa0] BcmVxIpHalIf::RemoveLeaseImpl: (IP Stack1 HalIf) This is the last address on the stack; shutting the stack down.
0x0001b44a ['DHCP Client Thread' id=0x807c8fa0] BcmVxIpHalIf::ShutdownIpStackImpl: (IP Stack1 HalIf)
Shutting down IP stack 1
0x0001b44a ['DHCP Client Thread' id=0x807c8fa0] BcmVxIpHalIf::ShutdownIpStackImpl: (IP Stack1 HalIf) There are 1 IP addresses registered with this stack.
Logging event: ToD request sent- No Response received
Sending syslog message from IF 1 to 192.168.100.10:
<131> CABLEMODEM [DOCSIS]: <68000403> ToD request sent- No Response received
0x0001b454 ['Event Log Thread' id=0x807b4820] BcmVxSocket::Sendto: ERROR - SOCKET_ERROR: 65
docsDevEvSyslog::Send - sendto failure -1
v1Trap: docsDevCmTODFailTrap 192.168.100.1->192.168.100.10:162, cmty="public"
v1Trap: docsDevCmTODFailTrap 10.17.27.14->192.168.100.10:162, cmty="public"
AgentSendV1Trap - sendto failure 0041
BcmSnmpAgent::RestartPendingEvent for SB5100 CM Agent
SB5100 CM Agent setting V1/V2 view to
SB5100 CM Agent sending deferred traps...
Done w/ deferred traps.
SB5100 CM Agent ConfigIp: Ip=0.0.0.0, Subnet=0.0.0.0, Gateway=0.0.0.0
v1Trap: linkDownTrap(if2) 192.168.100.1->192.168.100.10:162, cmty="public"
CmSnmpAgent::ResetMibDefaults not restting due to factory mode
SB5100 CPE Agent setting V1/V2 view to docsisNmAccessView
Non-Vol Settings successfully written to the device.
0x0001b54e ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::ResetRngState: (CmDocsisCtlThread)
0x0001b54e ['Scan Downstream Thread' id=0x807d69c0] BcmVendorCmDownstreamScanThread::ThreadMain: (Scan Downstream Thread) Downstream Channel scan stopped!
SB5100 CM Event Log sending deferred async messages...
Done w/ deferred msgs
0x0001b562 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::SyncRxMacMgtMsg: (CmDocsisCtlThread) WARNING - Unknown message type received (33)! Ignoring...
0x0001b562 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::SyncRxMacMgtMsg: (CmDocsisCtlThread) WARNING - Unknown message type received (33)! Ignoring...
0x0001b562 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::SyncRxMacMgtMsg: (CmDocsisCtlThread) WARNING - Unknown message type received (33)! Ignoring...
0x0001b562 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::SyncRxMacMgtMsg: (CmDocsisCtlThread) WARNING - Unknown message type received (33)! Ignoring...
0x0001b562 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::RxMsgEvent: (CmDocsisCtlThread) WARNING - iteration limit reached. giving up control...
0x0001b562 ['Scan Downstream Thread' id=0x807d69c0] BcmVendorCmDownstreamScanThread::ThreadMain: (Scan Downstream Thread) Scanning for a Downstream Channel...
mot_scanList: Setting override freq @ 0
Attempting Downstream FEC lock @ freq= 591000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 597000000 Hz, QAM256
Sending syslog message from IF 1 to 192.168.100.10:
<130> CABLEMODEM [DOCSIS]: <84000200> SYNC Timing Synchronization failure - Failed to acquire FEC framing
0x0001b616 ['Event Log Thread' id=0x807b4820] BcmVxSocket::Sendto: ERROR - SOCKET_ERROR: 65
docsDevEvSyslog::Send - sendto failure -1
Attempting Downstream FEC lock @ freq= 603000000 Hz, QAM256
Sending syslog message from IF 1 to 192.168.100.10:
<130> CABLEMODEM [DOCSIS]: <84000200> SYNC Timing Synchronization failure - Failed to acquire FEC framing
0x0001b6ca ['Event Log Thread' id=0x807b4820] BcmVxSocket::Sendto: ERROR - SOCKET_ERROR: 65
docsDevEvSyslog::Send - sendto failure -1
Attempting Downstream FEC lock @ freq= 609000000 Hz, QAM256
.
.
.
Favorite[0].freq = 585000000
Attempting Downstream FEC lock @ freq= 585000000 Hz, QAM64/256
Sending syslog message from IF 1 to 192.168.100.10:
<130> CABLEMODEM [DOCSIS]: <84000200> SYNC Timing Synchronization failure - Failed to acquire FEC framing
0x0001df88 ['Event Log Thread' id=0x807b4820] BcmVxSocket::Sendto: ERROR - SOCKET_ERROR: 65
docsDevEvSyslog::Send - sendto failure -1
CM> 0x0001e0f0 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::SyncDsLockOk: (CmDocsisCtlThread) Locked on the downstream. Waiting for UCDs...
******************************************
DOWNSTREAM STATUS
******************************************
Tuner Frequency = 585000000 Hz
Carrier Offset = -1 Hz
Symbol rate = 5360537 sym/sec
SNR = 36 dB
QAM Mode = QAM256
Tuner AGC = 0xde1b2c00
IF AGC = 0x7af00000
Power Level = -2 dB
QAM = LOCKED
FEC = LOCKED
******************************************
Received a UCD for Upstream Channel 2!
Received a UCD for Upstream Channel 34!
CM>
Received a UCD for Upstream Channel 3!
Received a UCD for Upstream Channel 35!
Received a UCD for Upstream Channel 4!
Received a UCD for Upstream Channel 36!
0x0001e3f2 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::SyncRxMacMgtMsg: (CmDocsisCtlThread) WARNING - Unknown message type received (33)! Ignoring...
Received a UCD for Upstream Channel 1!
Received a UCD for Upstream Channel 33!
CM>
Received a UCD for Upstream Channel 2!
Selecting UCD for Us Channel 34
BcmCmUsPhyOverheadSettings::ComputeReqDataPhyToMac Table() burst descriptor not found for kReqDataIUC.
Upstream Frequency = 31800000
Found QAM16 = false
0x0001e582 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::TestAndLaunchDsTimeSync: (CmDocsisCtlThread) entering...
new_us_scdma_enabled = false
fLastDsClockModeIsScdma = false
fCmDsTargetingState = kDsPhyOkUsUcdPending
IsDccContext() = false
0x0001e582 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::TestAndLaunchDsTimeSync: (CmDocsisCtlThread) starting ds time sync acquisition...
Received a UCD for Upstream Channel 34!
0x0001e7f8 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::SyncDsSyncOk: (CmDocsisCtlThread) downstream time sync acquired...
0x0001e7f8 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::DsSyncOkResumeUsInit: (CmDocsisCtlThread) pre-REG upstream target case...starting initial ranging.
Beginning initial ranging...
Using stored initial upstream power = 54.0 dBmV
0x0001e802 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::SyncDsSyncOk: (CmDocsisCtlThread) rx unexpected kDsSyncOk indication...
Logging event: T501.0 Acquired Downstream (585000000 Hz)........ SUCCESS
Sending syslog message from IF 1 to 192.168.100.10:
<134> CABLEMODEM [Motorola Corporation]: <2223898630> T501.0 Acquired Downstream (585000000 Hz)........ SUCCESS
0x0001e80c ['Event Log Thread' id=0x807b4820] BcmVxSocket::Sendto: ERROR - SOCKET_ERROR: 65
docsDevEvSyslog::Send - sendto failure -1
v1Trap: cmTrapLog 192.168.100.1->192.168.100.10:162, cmty="public"
RNG-RSP Adj: tim=2342 power=-6 freq=0 Stat=Continue
0x0001e8d4 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::ConfigStationMaint: (CmDocsisCtlThread)
config is kStationMaintenance mode.
RNG-RSP Adj: tim=1 power=0 freq=0 Stat=Success
0x0001e938 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::ConfigStationMaint: (CmDocsisCtlThread)
config is kPeriodicRanging mode.
******************************************
UPSTREAM STATUS
******************************************
Upstream Status = UP
Upstream Channel = 34
Upstream Frequency = 31800000 Hz
Upstream Power = 53 dBmV
Ranging SID = 0x8d
Upstream Symbol Rate = 2560000 sym/sec
******************************************
Starting IP Initialization with DHCP...
DHCPc: Waiting 3 seconds before sending Discover; client id htype=1, value=xx:xx:xx:xx:xx:xx
Logging event: T500.0 Acquired Upstream .......... SUCCESS
Sending syslog message from IF 1 to 192.168.100.10:
<134> CABLEMODEM [Motorola Corporation]: <2223898629> T500.0 Acquired Upstream .......... SUCCESS
0x0001e942 ['Event Log Thread' id=0x807b4820] BcmVxSocket::Sendto: ERROR - SOCKET_ERROR: 65
docsDevEvSyslog::Send - sendto failure -1
v1Trap: cmTrapLog 192.168.100.1->192.168.100.10:162, cmty="public"
CM> 0x0001ebc2 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::SyncRxMacMgtMsg: (CmDocsisCtlThread) WARNING - Unknown message type received (33)! Ignoring...
CM> 0x0001f392 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::SyncRxMacMgtMsg: (CmDocsisCtlThread) WARNING - Unknown message type received (33)! Ignoring...
CM> DHCPc: Sending Discover packet; client id htype=1, value=xx:xx:xx:xx:xx:xx
CM> DHCPc: Received an Offer from DHCP server xx:xx:xx:xx:xx:xx (10.17.1.1); lease client id htype=1, value=xx:xx:xx:xx:xx:xx
CM> 0x0001fb62 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::SyncRxMacMgtMsg: (CmDocsisCtlThread) WARNING - Unknown message type received (33)! Ignoring...
CM> DHCPc: Timed out waiting for offers for lease with client id htype=1, value=xx:xx:xx:xx:xx:xx
DHCPc: Sending Request packet; client id htype=1, value=xx:xx:xx:xx:xx:xx
DHCPc: Received an Ack from DHCP server xx:xx:xx:xx:xx:xx (10.17.1.1); lease client id htype=1, value=xx:xx:xx:xx:xx:xx
Current IP address is default 169.0.0.1; removing existing route...
0x000200ee ['DHCP Client Thread' id=0x807c8fa0] BcmVxIpHalIf::ConfigureLeaseImpl: (IP Stack1 HalIf)
Configuring IP stack 1:
IP Address = 10.17.27.14
Subnet Mask = 255.255.0.0
Router = 10.17.1.1
DHCP completed successfully!
... IGUAL QUE ARRIBA ...
CmSnmpAgent::IpAddressAcquiredEvent for SB5100 CM Agent
IP addr = 10.17.27.14
SB5100 CM Agent ConfigIp: Ip=10.17.27.14, Subnet=255.255.0.0, Gateway=10.17.1.1
CM> 0x00020332 ['CmDocsisCtlThread' id=0x807bda80] BcmCmDocsisCtlThread::SyncRxMacMgtMsg: (CmDocsisCtlThread) WARNING - Unknown message type received (33)! Ignoring...
CM> Starting Time Of Day...
0x000204e0 ['CmDocsisIpThread' id=0x807c3b50] BcmDocsisTimeOfDayThread::SetTodServerIpAddress: (Time Of Day Thread) ToD servers: 172.20.2.11
Connecting to ToD server 172.20.2.11...
Sending UDP ToD request to server...
Logging event: D511.0 Retrieved DHCP .......... SUCCESS
Sending syslog message from IF 1 to 192.168.100.10:
<134> CABLEMODEM [Motorola Corporation]: <2223898627> D511.0 Retrieved DHCP .......... SUCCESS
v1Trap: cmTrapLog 192.168.100.1->192.168.100.10:162, cmty="public"
v1Trap: cmTrapLog 10.17.27.14->192.168.100.10:162, cmty="public"
0x000205da ['Time Of Day Thread' id=0x807c55d0] BcmDocsisTimeOfDayThread::HandleToD: (Time Of Day Thread) WARNING - Timed out waiting for a response from the ToD server.
Waiting 2000 ms before trying this server again...
Logging event: ToD request sent- No Response received
Sending syslog message from IF 1 to 192.168.100.10:
<131> CABLEMODEM [DOCSIS]: <68000403> ToD request sent- No Response received
Starting Tftp of configuration file...
Opening file 'Clancy1IP_Arris_1.1_BPI' on 172.20.2.11...
Forcing to download Cfg file: Wiggum1IP_Mot_1.1
v1Trap: docsDevCmTODFailTrap 192.168.100.1->192.168.100.10:162, cmty="public"
v1Trap: docsDevCmTODFailTrap 10.17.27.14->192.168.100.10:162, cmty="public"
tftpInit: Tftp outbound interface flag (1024)
Connected to 172.20.2.11 [69]
mode set to octet.
getting from 172.20.2.11:Wiggum1IP_Mot_1.1 [octet]
tftpSend: Attempt #(1) Backoff (2) tickCount (13271) blkReply (1)
Tftp read ZERO bytes, may have reached end of file.
Config file was read! IP Initialization completed...
Test of 1.3.6.1.2.1.69.1.2.1.7.11 to 4 failed w/ error code INCONSISTENT_VALUE
Test of 1.3.6.1.2.1.69.1.2.1.7.10 to 4 failed w/ error code INCONSISTENT_VALUE
0x000207ba ['CmDocsisCtlThread' id=0x807bda80] BcmOperatingSystemFactory::VxWorksTerminateCallout : (Singleton) FATAL - Somebody called terminate(), possibly as a result of an unhandled C++ exception. Deli
berately crashing the system so that we restart..
Connection to host lost.
trate de depurarlo lo mas posible... espero que este bien....
la pregunta forzada es... el modem de tu amigo es "legal" ?
ElCucoArg
22/09/2008, 12:25
No, Mi amigo esta con un sb4200 y esta con el firm cambiado, pero tiene puesta su mac (de otro nodo que el mio ) y esta forzando bajar un cfg de doc 1.1....
Es posible que me hayan bloqueado la entrada por numero de serie del modem?
ElCucoArg
23/09/2008, 12:48
A alguien le paso lo mismo? Alguien sabe que puedo llegar a probar? ALGO!!!!! PORFAVOR!!!
ElCucoArg
24/09/2008, 14:19
Aparentemnte es problema de activar el bpi+.... se solucionó pero a medias.. ahora tengo otro error que postiare en otro thread.... saludos
El Cuco Arq estas postiando post repetidos en diferentes hilos favor de leer las normas saludos
ElCucoArg
25/09/2008, 13:56
Si ya lo se que lo hice pero el motivo fue simplemente para que cualquiera que lo busque y tenga el mismo problema (ya que el otro hilo era un problema muy similar al mio) pueda encontrar la solución....
Pido discuplas si no debía hacerlo....
pinchechema
25/09/2008, 19:24
"TFTP Config Lugash1IP_Mot_1.1 SUCCESS " Apoco esa es la config que te da? no le metas config, cambia todas las direcciones mac y reinicia.
ElCucoArg
25/09/2008, 19:36
Ese es el config defautl de la m@c puesta...
Con o sin config... me pasaba lo mismo...
igual era problema de bpi+...
ahora tenvo que ver k pasa... por k despues de k levantó estaba medio inestable.
saludos
Powered by vBulletin® Version 4.1.12 Copyright © 2012 vBulletin Solutions, Inc. All rights reserved.