Menu
Reply
  • 17
  • 0
  • 0
Pazmatron
Tuning in
83 Views
Message 1 of 6
Flag for a moderator

drop outs/ ping spikes

wan side drop outs, have had virgin look at this already trying to get them to look at it again.

Downstream                     DS-1      DS-2      DS-3       DS-4      DS-5      DS-6      DS-7       DS-8

Frequency (Hz)266750000218750000226750000234750000242750000250750000258750000274750000
Lock Status(QAM Lock/FEC Sync/MPEG Lock)LockedLockedLockedLockedLockedLockedLockedLocked
Channel ID1378910111214
Modulation256QAM256QAM256QAM256QAM256QAM256QAM256QAM256QAM
Symbol Rate (Msym/sec)6.9520006.9520006.9520006.9520006.9520006.9520006.9520006.952000
Interleave DepthI=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
Power Level (dBmV)8.979.559.519.208.979.068.928.84
RxMER (dB)37.9437.3637.6437.3637.9437.9437.9437.94
Pre RS Errors1431212951122611326111592117221173812309
Post RS Errors91548590927598988918902190559670

Upstream               US-1 US-2 US-3 US-4

Channel Type2.0N/AN/A2.0
Channel ID25N/AN/A26
Frequency (Hz)45800000N/AN/A35800000
Ranging StatusSuccessOtherOtherSuccess
Modulation16QAMN/AN/A16QAM
Symbol Rate (Sym/sec)5120000N/AN/A5120000
Mini-Slot Size4N/AN/A4
Power Level (dBmV)39.71N/AN/A39.25
T1 Timeouts0000
T2 Timeouts0000
T3 Timeouts2000
T4 Timeouts0000

 

Network Log

First TimeLast TimePriorityError NumberDescription
01/01/2017 13:04:13 GMT01/01/2017 13:04:13 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
01/01/2017 13:04:12 GMT01/01/2017 13:04:12 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
01/01/2017 09:55:33 GMT01/01/2017 09:55:33 GMTError (4)68010302DHCP WAN IP - *
01/01/2017 09:54:35 GMT01/01/2017 09:54:35 GMTError (4)68000407TOD established
Time Not EstablishedTime Not EstablishedCritical (3)82000200No Ranging Response received - T3 time-out
Time Not EstablishedTime Not EstablishedCritical (3)82000200No Ranging Response received - T3 time-out
Time Not EstablishedTime Not EstablishedNotice (6)84000510Downstream Locked Successfully
01/01/2017 09:47:57 GMT01/01/2017 09:47:57 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
01/01/2017 01:30:45 GMT01/01/2017 01:30:45 GMTError (4)68010302DHCP WAN IP - *
01/01/2017 01:29:49 GMT01/01/2017 01:29:49 GMTError (4)68000407TOD established
Time Not EstablishedTime Not EstablishedNotice (6)84000510Downstream Locked Successfully
01/01/2017 01:27:06 GMT01/01/2017 01:27:06 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
01/01/2017 01:27:03 GMT01/01/2017 01:27:03 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
01/01/2017 01:27:03 GMT01/01/2017 01:27:03 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
01/01/2017 01:27:03 GMT01/01/2017 01:27:03 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
01/01/2017 01:26:32 GMT01/01/2017 01:26:32 GMTError (4)68010302DHCP WAN IP - *
01/01/2017 01:25:49 GMT01/01/2017 01:25:49 GMTError (4)68000407TOD established
01/01/2017 01:25:40 GMT01/01/2017 01:25:40 GMTCritical (3)82000200No Ranging Response received - T3 time-out
01/01/2017 01:25:35 GMT01/01/2017 01:25:35 GMTNotice (6)84000510Downstream Locked Successfully
01/01/2017 01:25:21 GMT01/01/2017 01:25:21 GMTCritical (3)82000600Unicast Maintenance Ranging attempted - No response - Retries exhausted
0 Kudos
Reply
  • 17
  • 0
  • 0
Pazmatron
Tuning in
67 Views
Message 2 of 6
Flag for a moderator

Re: drop outs/ ping spikes

and again...

 

Network Log

First TimeLast TimePriorityError NumberDescription
01/01/2017 15:15:51 GMT01/01/2017 15:15:51 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/01/2017 15:15:50 GMT01/01/2017 15:15:50 GMTCritical (3)82000400Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
01/01/2017 15:15:22 GMT01/01/2017 15:15:22 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
01/01/2017 15:15:20 GMT01/01/2017 15:15:20 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
01/01/2017 15:15:19 GMT01/01/2017 15:15:19 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
01/01/2017 15:15:18 GMT01/01/2017 15:15:18 GMTWarning (5)84020200Lost MDD Timeout
01/01/2017 15:15:17 GMT01/01/2017 15:15:17 GMTWarning (5)84020200Lost MDD Timeout
01/01/2017 15:15:17 GMT01/01/2017 15:15:17 GMTWarning (5)84020200Lost MDD Timeout
01/01/2017 15:15:17 GMT01/01/2017 15:15:17 GMTWarning (5)84020200Lost MDD Timeout
01/01/2017 15:15:17 GMT01/01/2017 15:15:17 GMTWarning (5)84020200Lost MDD Timeout
01/01/2017 15:15:17 GMT01/01/2017 15:15:17 GMTWarning (5)84020200Lost MDD Timeout
01/01/2017 15:15:17 GMT01/01/2017 15:15:17 GMTWarning (5)84020200Lost MDD Timeout
01/01/2017 15:15:17 GMT01/01/2017 15:15:17 GMTWarning (5)84020200Lost MDD Timeout
01/01/2017 15:15:16 GMT01/01/2017 15:15:16 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
01/01/2017 15:15:13 GMT01/01/2017 15:15:13 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
01/01/2017 15:15:13 GMT01/01/2017 15:15:13 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
01/01/2017 15:15:12 GMT01/01/2017 15:15:12 GMTCritical (3)82000200No Ranging Response received - T3 time-out
01/01/2017 15:15:11 GMT01/01/2017 15:15:11 GMTCritical (3)82000200No Ranging Response received - T3 time-out
01/01/2017 15:15:10 GMT01/01/2017 15:15:10 GMTCritical (3)82000200No Ranging Response received - T3 time-out
01/01/2017 15:15:09 GMT01/01/2017 15:15:09 GMTWarning (5)84020200Lost MDD Timeout

Upstream   US-1 US-2 US-3 US-4

Channel Type2.0N/AN/AN/A
Channel ID25N/AN/AN/A
Frequency (Hz)45800000N/AN/AN/A
Ranging StatusSuccessN/AN/AN/A
Modulation16QAMN/AN/AN/A
Symbol Rate (Sym/sec)5120000N/AN/AN/A
Mini-Slot Size4N/AN/AN/A
Power Level (dBmV)58.21N/AN/AN/A
T1 Timeouts0000
T2 Timeouts0000
T3 Timeouts7000
T4 Timeouts0000

 

Downstream   DS-1 DS-2 DS-3 DS-4 DS-5 DS-6 DS-7 DS-8

Frequency (Hz)186750000N/AN/AN/AN/AN/AN/AN/A
Lock Status(QAM Lock/FEC Sync/MPEG Lock)LockedUnlockedUnlockedUnlockedUnlockedUnlockedUnlockedUnlocked
Channel ID0N/AN/AN/AN/AN/AN/AN/A
Modulation256QAMUnknownUnknownUnknownUnknownUnknownUnknownUnknown
Symbol Rate (Msym/sec)6.952000N/AN/AN/AN/AN/AN/AN/A
Interleave DepthI=12
J=17
N/AN/AN/AN/AN/AN/AN/A
Power Level (dBmV)-21.79N/AN/AN/AN/AN/AN/AN/A
RxMER (dB)25.93N/AN/AN/AN/AN/AN/AN/A
Pre RS Errors193564N/AN/AN/AN/AN/AN/AN/A
Post RS Errors191822N/AN/AN

 looks like loss of power

0 Kudos
Reply
  • 17
  • 0
  • 0
Pazmatron
Tuning in
66 Views
Message 3 of 6
Flag for a moderator

Re: drop outs/ ping spikes

left box for an hour but did not reconnect until switch off and on

01/01/2017 16:31:11 GMT01/01/2017 16:31:11 GMTError (4)68010302DHCP WAN IP -*
01/01/2017 16:30:14 GMT01/01/2017 16:30:14 GMTError (4)68000407TOD established
Time Not EstablishedTime Not EstablishedNotice (6)84000510Downstream Locked Successfully
01/01/2017 16:28:50 GMT01/01/2017 16:28:50 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
01/01/2017 16:28:49 GMT01/01/2017 16:28:49 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
01/01/2017 16:28:46 GMT01/01/2017 16:28:46 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
01/01/2017 16:28:44 GMT01/01/2017 16:28:44 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
01/01/2017 16:28:42 GMT01/01/2017 16:28:42 GMTNotice (6)84000510Downstream Locked Successfully
01/01/2017 16:28:41 GMT01/01/2017 16:28:41 GMTWarning (5)84020300MDD message timeout
01/01/2017 16:28:41 GMT01/01/2017 16:28:41 GMTWarning (5)84020200Lost MDD Timeout
01/01/2017 16:28:26 GMT01/01/2017 16:28:26 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
01/01/2017 16:28:25 GMT01/01/2017 16:28:25 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
01/01/2017 16:28:23 GMT01/01/2017 16:28:23 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
01/01/2017 16:28:22 GMT01/01/2017 16:28:22 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
01/01/2017 16:28:19 GMT01/01/2017 16:28:19 GMTCritical (3)84000500SYNC Timing Synchronization failure - Loss of Sync
01/01/2017 16:28:14 GMT01/01/2017 16:28:14 GMTNotice (6)84000510Downstream Locked Successfully
01/01/2017 16:28:14 GMT01/01/2017 16:28:14 GMTWarning (5)84020300MDD message timeout
01/01/2017 16:28:14 GMT01/01/2017 16:28:14 GMTWarning (5)84020200Lost MDD Timeout
01/01/2017 16:27:50 GMT01/01/2017 16:27:50 GMTNotice (6)84000510Downstream Locked Successfully
01/01/2017 16:27:50 GMT01/01/2017 16:27:50 GMTWarning (5)84020300MDD message timeout
0 Kudos
Reply
  • 17
  • 0
  • 0
Pazmatron
Tuning in
44 Views
Message 4 of 6
Flag for a moderator

Re: drop outs/ ping spikes

so after many days the issue is still not fixed. I'm still getting service timeouts, see below, and I get told that it will not be fixed tell maybe march because they have cabling problems. addtionally I keep getting promised compensation which I haven’t seen yet, totally unacceptable service.

 

05/01/2017 19:37:50 GMT05/01/2017 19:37:50 GMTError (4)68000407TOD established
05/01/2017 19:37:41 GMT05/01/2017 19:37:41 GMTCritical (3)82000200No Ranging Response received - T3 time-out
05/01/2017 19:37:33 GMT05/01/2017 19:37:33 GMTNotice (6)84000510Downstream Locked Successfully
05/01/2017 19:37:17 GMT05/01/2017 19:37:17 GMTCritical (3)82000600Unicast Maintenance Ranging attempted - No response - Retries exhausted
05/01/2017 19:37:17 GMT05/01/2017 19:37:17 GMTCritical (3)82000300Ranging Request Retries exhausted
05/01/2017 19:37:17 GMT05/01/2017 19:37:17 GMTCritical (3)82000600Unicast Maintenance Ranging attempted - No response - Retries exhausted
05/01/2017 19:37:16 GMT05/01/2017 19:37:16 GMTCritical (3)82000300Ranging Request Retries exhausted
05/01/2017 19:37:15 GMT05/01/2017 19:37:15 GMTCritical (3)82000200No Ranging Response received - T3 time-out
05/01/2017 19:37:15 GMT05/01/2017 19:37:15 GMTCritical (3)82000200No Ranging Response received - T3 time-out
05/01/2017 19:37:14 GMT05/01/2017 19:37:14 GMTCritical (3)82000200No Ranging Response received - T3 time-out
05/01/2017 19:37:14 GMT05/01/2017 19:37:14 GMTCritical (3)82000200No Ranging Response received - T3 time-out
05/01/2017 19:37:13 GMT05/01/2017 19:37:13 GMTCritical (3)82000200No Ranging Response received - T3 time-out
05/01/2017 19:37:13 GMT05/01/2017 19:37:13 GMTCritical (3)82000200No Ranging Response received - T3 time-out
05/01/2017 19:37:11 GMT05/01/2017 19:37:11 GMTCritical (3)82000200No Ranging Response received - T3 time-out
05/01/2017 19:37:11 GMT05/01/2017 19:37:11 GMTCritical (3)82000200No Ranging Response received - T3 time-out
05/01/2017 19:37:10 GMT05/01/2017 19:37:10 GMTCritical (3)82000200No Ranging Response received - T3 time-out
05/01/2017 19:37:10 GMT05/01/2017 19:37:10 GMTCritical (3)82000200No Ranging Response received - T3 time-out
05/01/2017 19:37:09 GMT05/01/2017 19:37:09 GMTCritical (3)82000200No Ranging Response received - T3 time-out
05/01/2017 19:37:09 GMT05/01/2017 19:37:09 GMTCritical (3)82000200No Ranging Response received - T3 time-out
05/01/2017 19:37:08 GMT05/01/2017 19:37:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
0 Kudos
Reply
  • 17
  • 0
  • 0
Pazmatron
Tuning in
30 Views
Message 5 of 6
Flag for a moderator

Re: drop outs/ ping spikes

still happening virgin not fixed Smiley Sad very unhelpful

08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
08/01/2017 12:27:08 GMT08/01/2017 12:27:08 GMTCritical (3)82000200No Ranging Response received - T3 time-out
0 Kudos
Reply
  • 4.21K
  • 89
  • 271
Moderator
Moderator
17 Views
Message 6 of 6
Flag for a moderator

Re: drop outs/ ping spikes

Hi Pazmatron

 

Thanks for posting. I'm very sorry to hear that you have been having some problems with your broadband connection recently. Thanks for providing this info from the hub for us to take a look at.

 

There are a lot of timeouts occurring and some problems showing with your power levels. We'll need to arrange an engineer visit to get this fixed so I'll send you a PM to get this booked in.

 

Speak soon 

Ty


The do's and don'ts. Keep the community welcoming for all. Follow the house rules


0 Kudos
Reply