Hi all,
I've had a Superhub 2 for around more than 2 months now and it had always been running fine and connected to DOCSIS 3 (6 downstreams and 2 upstreams). Last week, the v26 update was rolled out and all Superhub 2 in the Witton area in Aston are connecting to DOCSIS1...
I've had 2 engineers out who fit in a new Superhub 2 and checked the Superhub 2 directly from the cab. It didn't lock to DOCSIS 3 so he sent it to the engineer departments. Today, I got a phonecall it was complete... however, it didn't lock to DOCSIS 3 and only has only 1 upstream. I managed to ring level 2 support who said that with v26.. Superhub 2 doesn't lock to DOCSIS3 and that it's a bug?
Does anyone else have this issue.
Code:
Downstream
DS-1 DS-2 DS-3 DS-4 DS-5 DS-6 DS-7 DS-8
Frequency (Hz) 299000000 N/A N/A N/A N/A N/A N/A N/A
Lock Status(QAM Lock/FEC Sync/MPEG Lock) Locked Unlocked Unlocked Unlocked Unlocked Unlocked Unlocked Unlocked
Channel ID 181 N/A N/A N/A N/A N/A N/A N/A
Modulation 256QAM Unknown Unknown Unknown Unknown Unknown Unknown Unknown
Symbol Rate (Msym/sec) 6.952000 N/A N/A N/A N/A N/A N/A N/A
Interleave Depth I=12
J=17 N/A N/A N/A N/A N/A N/A N/A
Power Level (dBmV) 1.38 N/A N/A N/A N/A N/A N/A N/A
RxMER (dB) 37.09 N/A N/A N/A N/A N/A N/A N/A
Pre RS Errors 543 N/A N/A N/A N/A N/A N/A N/A
Post RS Errors 276 N/A N/A N/A N/A N/A N/A N/A
Code:
Upstream
US-1 US-2 US-3 US-4
Channel Type 2.0 N/A N/A N/A
Channel ID 33 N/A N/A N/A
Frequency (Hz) 37600000 N/A N/A N/A
Ranging Status Success N/A N/A N/A
Modulation 16QAM N/A N/A N/A
Symbol Rate (Sym/sec) 5120000 N/A N/A N/A
Mini-Slot Size 4 N/A N/A N/A
Power Level (dBmV) 40.25 N/A N/A N/A
T1 Timeouts 0 0 0 0
T2 Timeouts 0 0 0 0
T3 Timeouts 1 0 0 0
T4 Timeouts 0 0 0 0
Code:
Network Log
First Time Last Time Priority Error Number Description
26/09/2013 15:13:42 GMT 26/09/2013 15:13:42 GMT Error (4) 68010302 DHCP WAN IP - 82.46.138.186
26/09/2013 15:12:58 GMT 26/09/2013 15:12:58 GMT Error (4) 68000407 TOD established
26/09/2013 15:12:41 GMT 26/09/2013 15:12:41 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
26/09/2013 15:12:34 GMT 26/09/2013 15:12:34 GMT Notice (6) 84000510 Downstream Locked Successfully
26/09/2013 15:12:27 GMT 26/09/2013 15:12:27 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
26/09/2013 15:12:25 GMT 26/09/2013 15:12:25 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
26/09/2013 15:12:24 GMT 26/09/2013 15:12:24 GMT Critical (3) 73000200 REG RSP not received
26/09/2013 15:12:24 GMT 26/09/2013 15:12:24 GMT Error (4) 73027100 T6 Timeout and retries exceeded
26/09/2013 15:12:24 GMT 26/09/2013 15:12:24 GMT Critical (3) 73025103 Registration RSP rejected unspecified reason
26/09/2013 15:12:23 GMT 26/09/2013 15:12:23 GMT Critical (3) 73025104 Registration RSP rejected message syntax error
26/09/2013 15:12:22 GMT 26/09/2013 15:12:22 GMT Error (4) 68000407 TOD established
Time Not Established Time Not Established Notice (6) 84000510 Downstream Locked Successfully
26/09/2013 15:05:49 GMT 26/09/2013 15:05:49 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
26/09/2013 15:05:42 GMT 26/09/2013 15:05:42 GMT Notice (6) 84000510 Downstream Locked Successfully
26/09/2013 15:05:32 GMT 26/09/2013 15:05:32 GMT Critical (3) 73000200 REG RSP not received
26/09/2013 15:05:32 GMT 26/09/2013 15:05:32 GMT Error (4) 73027100 T6 Timeout and retries exceeded
26/09/2013 15:05:32 GMT 26/09/2013 15:05:32 GMT Critical (3) 73025103 Registration RSP rejected unspecified reason
26/09/2013 15:05:32 GMT 26/09/2013 15:05:32 GMT Critical (3) 73025104 Registration RSP rejected message syntax error
26/09/2013 15:05:31 GMT 26/09/2013 15:05:31 GMT Error (4) 68000407 TOD established
26/09/2013 15:05:10 GMT 26/09/2013 15:05:10 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out