Menu
Reply
  • 2.4K
  • 129
  • 295
Forum Team
Forum Team
542 Views
Message 11 of 15
Flag for a moderator

Re: SH3 LATENCY ISSUE AGAIN

Hello numar781

I am more than happy to take a look at this for you 

I will need to send you a private message to pass security 

Let me know if you wish to do so 

Regards 

Gareth_L

 

0 Kudos
Reply
  • 10
  • 0
  • 0
numar781
Joining in
447 Views
Message 12 of 15
Flag for a moderator

Re: SH3 LATENCY ISSUE AGAIN

still no help, virgin media support is truly useless. Thinking about looking some place else.

0 Kudos
Reply
  • 10
  • 0
  • 0
numar781
Joining in
351 Views
Message 13 of 15
Flag for a moderator

Re: SH3 LATENCY ISSUE AGAIN

 
Upstream bonded channelsChannel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1536999544.871512016 qam2
2393988734.725512016 qam4
3462001974.875512016 qam3
4603000534.875512016 qam1


Upstream bonded channelsChannel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000
Downstream bonded channelsChannel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
12990000002.240256 qam21
21950000002.440256 qam8
32030000002.240256 qam9
4211000000240256 qam10
52190000001.940256 qam11
62270000001.740256 qam12
72350000001.740256 qam13
82430000001.540256 qam14
92510000001.540256 qam15
102590000001.540256 qam16
11267000000240256 qam17
122750000001.940256 qam18
13283000000240256 qam19
142910000001.940256 qam20
153070000002.240256 qam22
163150000002.240256 qam23
173230000002.540256 qam24
18427000000340256 qam25
194350000002.740256 qam26
204430000002.440256 qam27
214510000002.240256 qam28
22459000000240256 qam29
23467000000240256 qam30
244750000001.940256 qam31


Downstream bonded channelsChannel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked40.960
2Locked40.940
3Locked40.930
4Locked40.950
5Locked40.960
6Locked40.940
7Locked40.940
8Locked40.900
9Locked40.300
10Locked40.300
11Locked40.950
12Locked40.950
13Locked40.960
14Locked40.360
15Locked40.940
16Locked40.970
17Locked40.340
18Locked40.3180
19Locked40.9150
20Locked40.9210
21Locked40.3270
22Locked40.9290
23Locked40.3310
24Locked40.9220
0 Kudos
Reply
  • 10
  • 0
  • 0
numar781
Joining in
350 Views
Message 14 of 15
Flag for a moderator

Re: SH3 LATENCY ISSUE AGAIN

still need help

 

 
Network LogTime Priority Description
12/07/2019 19:14:22criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 19:14:22criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 19:14:23criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 19:14:23criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 19:14:23criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 19:14:23criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 19:14:24criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 19:14:24criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 19:14:24criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 19:14:24criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 19:14:25criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 19:14:25criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 19:14:25criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 19:14:25criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 19:14:26criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 19:14:26criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 19:14:27criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 19:14:27criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 19:14:28criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 19:14:28criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
  • 36
  • 1
  • 4
Bradlewis
On our wavelength
348 Views
Message 15 of 15
Flag for a moderator

Re: SH3 LATENCY ISSUE AGAIN

Did you ever respond to Gareth_L like he asked?
0 Kudos
Reply