cancel
Showing results for 
Search instead for 
Did you mean: 

Question about Signal Levels

Alex4161
I'm a senior contributor

I had a look at my signal levels and see the following:

 

Downstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB)
1 657000000 256QAM 2.300 17 36.387
2 561000000 256QAM 3.100 2 35.780
3 567000000 256QAM 2.500 3 35.595
4 573000000 256QAM 3.600 4 35.780
5 579000000 256QAM 4.400 5 35.780
6 585000000 256QAM 4.900 6 36.387
7 591000000 256QAM 6.300 7 36.387
8 597000000 256QAM 6.500 8 37.356
9 603000000 256QAM 6.200 9 36.610
10 609000000 256QAM 5.000 10 36.387
11 615000000 256QAM 3.700 11 36.610
12 621000000 256QAM 2.600 12 35.780
13 633000000 256QAM 2.800 13 35.780
14 639000000 256QAM 3.400 14 36.387
15 645000000 256QAM 4.000 15 35.780
16 651000000 256QAM 2.800 16 36.387
17 555000000 256QAM 3.800 1 35.780
18 663000000 256QAM 3.000 18 35.780
19 669000000 256QAM 3.300 19 35.780
20 675000000 256QAM 3.300 20 36.387
21 681000000 256QAM 3.700 21 36.387
22 687000000 256QAM 3.700 22 36.610
23 693000000 256QAM 2.900 23 36.610
24 699000000 256QAM 2.900 24 36.387
25 705000000 256QAM 2.000 25 35.780
26 711000000 256QAM 1.000 26 35.780
27 717000000 256QAM 0.100 27 35.780
28 723000000 256QAM -1.100 28 34.926
29 825000000 256QAM 0.900 29 35.595
30 831000000 256QAM 0.400 30 35.780
31 837000000 256QAM 0.000 31 35.780
32 843000000 256QAM -0.300 32 35.595
OFDM Downstream Overview
Receiver FFT type Subcarr 0 Frequency(MHz) PLC locked NCP locked MDC1 locked PLC power(dBmv)
0 NA NA NO NO NO NA
1 4K 275600000 YES YES YES 8.400002
Upstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Bandwidth
1 38595687 ATDMA - 64QAM 39.250 3 3200000
2 30596000 ATDMA - 64QAM 35.250 1 6400000
3 23700000 ATDMA - 64QAM 33.500 2 6400000
OFDM/OFDMA Overview
Channel Index State lin Digital Att Digital Att BW (sc's*fft) Report Power Report Power1_6 FFT Size
0 DISABLED 0.5000 0.0000 0.0000 -inf -1.0000 4K
1 DISABLED 0.5000 0.0000 0.0000 -inf -1.0000 4K

 

Is it normal to have the Channel ID not equal the Port ID?  I am seeing channel 1/17 and port ID numbers flipped.

 

 

***Edited Labels***

17 REPLIES 17

Re: Question about Signal Levels

gp-se
I'm an advisor

@Alex4161 It is normal that the channel ID and channel number don't match, nothing to worry about.

This is my signal levels for example, notice my upload levels:

1 591000000 256QAM -2.600 31  38.605
2 363000000 256QAM -1.000 10  38.983
3 369000000 256QAM -1.000 11  38.605
4 375000000 256QAM -0.800 12  38.983
5 381000000 256QAM -0.900 13  38.983
6 387000000 256QAM -1.200 14  38.605
7 393000000 256QAM -0.600 15  38.983
8 399000000 256QAM -1.300 16  38.605
9 405000000 256QAM -1.200 17  38.605
10 411000000 256QAM -1.100 18  40.366
11 417000000 256QAM -0.900 19  38.983
12 423000000 256QAM -0.800 20  38.983
13 429000000 256QAM -0.800 21  38.983
14 435000000 256QAM -0.700 22  38.983
15 441000000 256QAM -0.600 23  38.983
16 447000000 256QAM -0.500 24  40.946
17 555000000 256QAM -2.300 25  38.605
18 561000000 256QAM -1.800 26  38.983
19 567000000 256QAM -1.600 27  38.983
20 573000000 256QAM -1.500 28  38.983
21 579000000 256QAM -1.800 29  38.605
22 585000000 256QAM -2.200 30  38.983
23 357000000 256QAM -1.200 9  38.983
24 597000000 256QAM -3.200 32  38.983
25 825000000 256QAM -4.300 53  38.605
26 831000000 256QAM -4.600 54  37.636
27 837000000 256QAM -4.900 55  37.636
28 843000000 256QAM -4.800 56  38.605
29 633000000 256QAM -2.700 37  38.983
30 639000000 256QAM -2.800 38  38.983
31 645000000 256QAM -2.000 39  38.983
32          651000000           256QAM             -1.800          40          38.605
OFDM Downstream Overview
Receiver FFT type Subcarr 0 Frequency(MHz) PLC locked NCP locked MDC1 locked PLC power(dBmv)
0 NA NA NO NO NO NA
1 NA NA NO NO NO NA
Upstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Bandwidth
1 30596000 ATDMA - 64QAM 27.250 1 6400000
2 38596000 ATDMA - 64QAM 30.500 3 3200000
3 23700000 ATDMA - 64QAM 27.250 2 6400000
OFDM/OFDMA Overview
Channel Index State lin Digital Att Digital Att BW (sc's*fft) Report Power Report Power1_6 FFT Size
0 DISABLED 0.5000 0.0000 0.0000 -inf -1.0000 4K
1 DISABLED 0.5000 0.0000 0.0000 -inf -1.0000 4K

Re: Question about Signal Levels

Alex4161
I'm a senior contributor

Thanks for the fast reply.  I wish I had your s/n levels 🙂

Re: Question about Signal Levels

JSS_BRAMPTON
I plan to stick around

Experiencing intermittent issues and CODA-4582U DOCSIS event logs display frequently occuring T3-time-outs.

 

I read somewhere the optimal Signal strength (dBmV) for DownStream is between - 10 dBmV to + 10 dBmV and ideally at 0dBmV with SNR 36~40 dB range with UpStream normally 36~51 dBmV.

 

Opened several cases with Rogers but CSR avoids addressing my signal levels and critical error logs.   Past posts recommend upgrade of equipment at the headend but if I am the only one complaining no one is listening.  Please advise.

 

17 03/15/2020 09:06:11 84000500 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:90:cc:8b;CM-QOS=1.1;CM-VER=3.1;
18 03/15/2020 16:43:50 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:90:cc:8b;CM-QOS=1.1;CM-VER=3.1;
19 03/16/2020 13:28:32 90000000 warning MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:90:cc:8b;CM-QOS=1.1;CM-VER=3.1;
20 03/16/2020 21:47:02 82000200 critical No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=00:17:10:90:cc:8b;CM-QOS=1.1;CM-VER=3.1;

 

 

 

Downstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Signal noise ratio (dB)
1 591000000 256QAM 11.100 7 40.366
2 849000000 256QAM 12.400 2 40.366
3 855000000 256QAM 13.000 3 40.366
4 861000000 256QAM 12.800 4 40.366
5 579000000 256QAM 10.400 5 38.605
6 585000000 256QAM 10.700 6 38.983
7 279000000 256QAM 10.600 1 37.356
8 597000000 256QAM 10.900 8 38.983
9 603000000 256QAM 10.400 9 40.366
10 609000000 256QAM 10.200 10 38.605
11 615000000 256QAM 10.000 11 38.983
12 621000000 256QAM 9.800 12 38.983
13 633000000 256QAM 8.900 13 38.605
14 639000000 256QAM 8.900 14 38.983
15 645000000 256QAM 9.500 15 38.605
16 651000000 256QAM 9.400 16 38.983
17 657000000 256QAM 9.100 17 37.636
18 663000000 256QAM 8.900 18 38.983
19 669000000 256QAM 8.400 19 37.636
20 675000000 256QAM 8.600 20 37.356
21 681000000 256QAM 9.300 21 38.605
22 687000000 256QAM 9.600 22 38.605
23 693000000 256QAM 9.700 23 38.983
24 699000000 256QAM 9.400 24 38.605
25 705000000 256QAM 9.000 25 38.605
26 711000000 256QAM 9.100 26 38.605
27 717000000 256QAM 8.900 27 38.605
28 723000000 256QAM 8.700 28 38.605
29 825000000 256QAM 11.600 29 38.983
30 831000000 256QAM 11.900 30 40.366
31 837000000 256QAM 12.400 31 40.366
32 843000000 256QAM 11.900 32 40.366
OFDM Downstream Overview
Receiver FFT type Subcarr 0 Frequency(MHz) PLC locked NCP locked MDC1 locked PLC power(dBmv)
0 NA NA NO NO NO NA
1 4K 275600000 YES YES YES 10.300003
Upstream Overview
Port ID Frequency (MHz) Modulation Signal strength (dBmV) Channel ID Bandwidth
1 30596000 ATDMA - 64QAM 26.000 7 6400000
2 36996000 ATDMA - 64QAM 27.250 8 6400000
3 22100000 ATDMA - 64QAM 28.500 5 3200000
4 25300000 ATDMA - 64QAM 28.750 6 3200000
OFDM/OFDMA Overview
Channel Index State lin Digital Att Digital Att BW (sc's*fft) Report Power Report Power1_6 FFT Size
0 DISABLED 0.5000 0.0000 0.0000 -inf -1.0000 4K
1 DISABLED 0.5000 0.0000 0.0000 -inf -1.0000 4K

Re: Question about Signal Levels

@JSS_BRAMPTON your downstream DOCSIS 3.0 (chan 1 to 32) signal levels are too high, even by Rogers standards.  The signal to noise ratios are fine as are the QAM levels. 

 

The upstream DOCSIS 3.0 channels are a little low compared to what we normally see, however, if you're in an apartment/condo/highrise or in a house that is very close to the neighbourhood node, those levels would make sense.  

 

The Downstream DOCSIS 3.1 OFDM channel would also be running at a very high level, but, the actual aggregated signal level, QAM level and signal to noise ratios are not presented in the user interface.  Tech support has access to that data, so you would have to ask tech support specifically if the OFDM signal level, QAM level and signal to noise ratio were within spec.  The QAM level should e at 1024 for this modem when the signal levels and signal to noise ratios are within acceptable ranges. 

 

If the Customer Service Rep ran an signal check on the modem, that would produce a pass/fail indication, but, you would have specifically ask the CSR to check the OFDM data.  

 

Fwiw, I refer you to the following thread regarding latency and packet loss that has been observed on the Rogers network over the last two months:

 

https://communityforums.rogers.com/t5/Internet/Brutal-latency-ping-Recently/td-p/454780

 

This is an ongoing problem where Rogers is completely silent as to the cause and any potential changes to correct the situation.  There are hundreds (?) of complaints in that thread, in a corresponding reddit thread and direct complaints from most if not all of the TPIAs that use Rogers network, to no avail I would say.  This might explain the problems that you are currently seeing, beyond anything that might be occurring due to your signal levels. 

 

Personal opinion, you need a tech to install a 9 dB attenuator to drop the downstream signal levels.  That will cause the upstream levels to rise by the same amount, but, after the attenuator, the outbound signal levels will be the same, and that will probably be fine as the outbound signal levels are controlled by the Cable Modem termination System (CMTS), so, if they needed to run at at higher level, the CMTS would command the modem to run at a higher output level. 

 

Edit:  a DOCSIS 3.0 modem on the Rogers network will typically run at 36 to 40 dBmV for upstream transmit power levels.  The 4582 historically runs in the 30 to 32 dBmV range, so your upstream signal levels are a little low, but, they might be absolutely fine if the signal level and signal to noise ratios at the arriving end (neighbourhood node) are ok.  

Re: Question about Signal Levels

JSS_BRAMPTON
I plan to stick around
Thank you for your enlightenment. The Rogers utility box is right outside my home. Today I was lucky to get a CSR who noted signal issues and opened a ticket to dispatch another tech to troubleshoot issues outside. I will make a note of your recommendations and share with the tech. Thank you.

Re: Question about Signal Levels

The tech will be able to access the modem signal levels before he or she arrives at your home.  His or her immediate thought should be to drop the downstream signal levels down to 0 dBmV.  A 9 dB attenuator will almost achieve that so that your downstream signal levels end up with a -0.4 to 4 dBmV range.   That's not too bad. 

 

A normal attenutor will also drive up the outbound signal levels by the same amount.  In your case, that won't be an issue. 

 

There is a Forward Path Attenuator that can be used to drop the downstream signal levels while leaving the upstream signal levels as they are.  I don't know if Rogers uses the Forward Path Attenuators or if they stick to the typical attenuators that are used throughout the industry.  

Re: Question about Signal Levels

Taab
I plan to stick around

Wanted to know if my signals are fine. I've been having major ping issues and packet loss while pinging Rogers' primary DNS (Approx. 21%).

 

Downstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDSignal noise ratio (dB)
1615000000256QAM7.3001140.366
2603000000256QAM7.100940.366
3609000000256QAM7.2001040.366
4597000000256QAM7.000840.366
5279000000256QAM13.300143.377
6579000000256QAM7.700540.366
7585000000256QAM7.500640.946
8591000000256QAM7.500740.366
9621000000256QAM7.6001240.366
10633000000256QAM6.8001340.366
11639000000256QAM6.6001440.366
12645000000256QAM6.6001540.366
13651000000256QAM6.8001640.946
14657000000256QAM6.7001740.946
15663000000256QAM6.5001840.366
16669000000256QAM6.4001940.366
17675000000256QAM6.6002040.366
18681000000256QAM6.4002140.366
19687000000256QAM6.8002240.946
20693000000256QAM6.7002340.366
21699000000256QAM6.7002440.366
22705000000256QAM6.7002540.366
23711000000256QAM6.7002640.366
24717000000256QAM6.5002740.366
25723000000256QAM6.0002840.946
26825000000256QAM6.0002940.366
27831000000256QAM5.8003040.366
28837000000256QAM5.4003140.366
29843000000256QAM5.1003240.366
30849000000256QAM4.800240.366
31855000000256QAM4.800340.366
32861000000256QAM4.400440.366
OFDM Downstream Overview
ReceiverFFT typeSubcarr 0 Frequency(MHz)PLC lockedNCP lockedMDC1 lockedPLC power(dBmv)
0NANANONONONA
14K275600000YESYESYES10.800003
Upstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDBandwidth
122100000ATDMA - 64QAM21.00013200000
236996000ATDMA - 64QAM19.75046400000
330596000ATDMA - 64QAM19.50036400000
425300000ATDMA - 64QAM22.25023200000
OFDM/OFDMA Overview
Channel IndexStatelin Digital AttDigital AttBW (sc's*fft)Report PowerReport Power1_6FFT Size
0DISABLED0.50000.00000.0000-inf-1.00004K
1DISABLED0.50000.00000.0000-inf-1.0000

4K

Re: Question about Signal Levels

JSS_BRAMPTON
I plan to stick around

@Datalink last evening I looked out and saw a Senior Rogers tech working on the tap.  I spoke to him and he was kind enough to quickly move my service through a splitter and a 6 dB attenuator. Readings improved and he recommended I swap the modem.  My tech visit is scheduled for March 19 and I am now tempted to ask the tech to replace the 6 for 9 dB attenuator, to drop the signal further, as you suggested.

 

Downstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDSignal noise ratio (dB)
1669000000256QAM5.3001934.346
2849000000256QAM8.800236.610
3855000000256QAM9.000337.356
4861000000256QAM9.000437.636
5579000000256QAM7.300535.595
6585000000256QAM7.600635.595
7591000000256QAM7.900736.387
8597000000256QAM7.700835.595
9603000000256QAM7.100935.780
10609000000256QAM7.0001035.595
11615000000256QAM7.0001135.595
12621000000256QAM7.1001235.595
13633000000256QAM5.2001333.957
14639000000256QAM3.8001433.377
15645000000256QAM4.3001533.487
16651000000256QAM4.5001633.957
17657000000256QAM4.8001733.957
18663000000256QAM5.1001833.957
19279000000256QAM7.600135.084
20675000000256QAM5.8002034.484
21681000000256QAM6.1002135.084
22687000000256QAM6.4002234.926
23693000000256QAM6.5002335.084
24699000000256QAM6.3002435.084
25705000000256QAM6.1002534.926
26711000000256QAM6.1002635.084
27717000000256QAM5.9002734.926
28723000000256QAM5.9002834.926
29825000000256QAM7.8002936.387
30831000000256QAM8.4003036.610
31837000000256QAM9.0003136.610
32843000000256QAM8.5003236.610
OFDM Downstream Overview
ReceiverFFT typeSubcarr 0 Frequency(MHz)PLC lockedNCP lockedMDC1 lockedPLC power(dBmv)
0NANANONONONA
14K275600000YESYESYES7.400002
Upstream Overview
Port IDFrequency (MHz)ModulationSignal strength (dBmV)Channel IDBandwidth
130596000ATDMA - 64QAM35.75076400000
236996000ATDMA - 64QAM35.75086400000
322100000ATDMA - 64QAM37.50053200000
425299824ATDMA - 64QAM37.25063200000
OFDM/OFDMA Overview
Channel IndexStatelin Digital AttDigital AttBW (sc's*fft)Report PowerReport Power1_6FFT Size
0DISABLED0.50000.00000.0000-inf-1.00004K
1DISABLED0.50000.00000.0000-inf-1.00004K

Re: Question about Signal Levels

@Taab & @JSS_BRAMPTON 

I would say BOTH of yours are on the high side.

'within spec' are + or - 10.
And both of them are getting up there or over.
Optimally should be close to 0.

So definitely would be worth getting a tech out to take a look at things.
Even just putting in a splitter, etc, which would drop down the signal level a bit.

Re: Question about Signal Levels

JSS_BRAMPTON
I plan to stick around

@Gdkitty & @Datalink & @gp-se   

 

Besides game lagging reported by my 10 yr old, I have a VOIP service that goes down almost daily, when port 5060 gets locked and my PAPT2 fails to register. 

 

So in anticipation of tomorrow's Tier II tech visit, I ran some stats (as seen from Brutal-latency-ping-Recently).  Besides asking him to reduce the downstream signal closer to 0dB - is there anything, you see, I ought to bring to his attention? 

 

Tracing route to www.google.com [172.217.164.228] over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms hitronhub.home [192.168.0.1]
2 18 ms 10 ms 10 ms 99.234.60.1
3 12 ms 9 ms 10 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 16 ms 9 ms 10 ms 209.148.235.73
5 13 ms 20 ms 10 ms 209.148.233.38
6 * * * Request timed out.
7 14 ms 19 ms 13 ms 74.125.244.161
8 11 ms 11 ms 9 ms 216.239.42.619 18 ms 14 ms 9 ms yyz12s05-in-f4.1e100.net [172.217.164.228]

Trace complete.

 

1.  Ping statistics for 99.234.60.1:
Packets: Sent = 3600, Received = 3589, Lost = 11 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 317ms, Average = 16ms

 

2.  Ping statistics for 64.71.255.204:
Packets: Sent = 3440, Received = 2528, Lost = 912 (26% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 509ms, Average = 11ms

 

3.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| hitronhub.home - 100 | 264 | 1 | 1 | 1 | 1 | 1 |
| 99.234.60.1 - 1 | 1275 | 1265 | 6 | 15 | 182 | 13 |
| gw01.ajax.phub.net.cable.rogers.com - 1 | 1283 | 1275 | 3 | 13 | 244 | 9 |
| 209.148.235.57 - 1 | 1287 | 1280 | 5 | 14 | 110 | 15 |
| 209.148.235.42 - 1 | 1299 | 1295 | 8 | 16 | 383 | 15 |
| 72.14.222.87 - 1 | 1283 | 1275 | 6 | 15 | 174 | 10 |
| 108.170.250.241 - 1 | 1298 | 1294 | 6 | 14 | 106 | 12 |
| 216.239.35.233 - 1 | 1306 | 1304 | 6 | 15 | 511 | 13 |
| dns.google - 1 | 1295 | 1290 | 5 | 13 | 246 | 10 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

 

Re: Question about Signal Levels

@JSS_BRAMPTON how's that for service.  Wish I could take credit for that, lol 🙂

 

Ok, as @Gdkitty indicated, your signal levels are still high, so yes, they could drop by another 3 dB.  However, looking at the signal levels it would appear that there's a noise issue on the cable line that runs from the neighbourhood node to your local tap.  My guess is that the noise source is fairly close to your home, unless its putting out enough noise that its affecting the entire line to a very large extent.  If you look at the before and after results, you can see the drop in signal to noise ratio in the upper DOCSIS 3.0 channels (1 to 32).   For a 6 dB drop in signal level, you also dropped about 6 db in signal to noise ratio.  

 

Personally I wouldn't want the signal to noise ratio to drop any further, so I'd hold off on any further signal drop by installing a 9 dB attenuator.  I think you'll run into problems due to the signal to noise ratio if you drop the signal level any further.  

 

I think at the present time you should have a chat with tech support to determine if the senior tech raised a ticket last night for another senior tech or maintenance crew to look at the noise levels in your neighbourhood.  Following that the conversation can take one of two directions, one, there is another senior tech or maintenance crew already assigned to a ticket to track down the noise, or two, the Customer Service Rep looks at the noise level up and down the line and raises a ticket to do the same.  I think that should be the first step before another tech arrives to swap the attenuators.  If so, then tomorrow's tech should be postponed for now. 

 

If you have a chat with tech support please let us know how it went.  

 

Edit:  looking at your ping test results, the test to the DNS is pretty ugly.  Can you run a short test, 50 pings and post the results, just to see what it looks like when its running?  Run:

 

ping -n 50 64.71.255.204

 

Please post that entire test, from start to finish when its done.  

Re: Question about Signal Levels

JSS_BRAMPTON
I plan to stick around

@Datalink  Hi... Sorry I guess I was still editing my post when you responded.

Here is the test ping -n 50 64.71.255.204 requested by yourself:

 

Pinging 64.71.255.204 with 32 bytes of data:
Reply from 64.71.255.204: bytes=32 time=94ms TTL=58
Reply from 64.71.255.204: bytes=32 time=21ms TTL=58
Request timed out.
Request timed out.
Request timed out.
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Reply from 64.71.255.204: bytes=32 time=11ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=18ms TTL=58
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Reply from 64.71.255.204: bytes=32 time=31ms TTL=58
Reply from 64.71.255.204: bytes=32 time=11ms TTL=58
Reply from 64.71.255.204: bytes=32 time=16ms TTL=58
Reply from 64.71.255.204: bytes=32 time=18ms TTL=58
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Reply from 64.71.255.204: bytes=32 time=18ms TTL=58
Reply from 64.71.255.204: bytes=32 time=13ms TTL=58
Reply from 64.71.255.204: bytes=32 time=30ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Reply from 64.71.255.204: bytes=32 time=13ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=39ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=16ms TTL=58
Reply from 64.71.255.204: bytes=32 time=20ms TTL=58
Reply from 64.71.255.204: bytes=32 time=18ms TTL=58
Request timed out.
Request timed out.
Reply from 64.71.255.204: bytes=32 time=18ms TTL=58
Reply from 64.71.255.204: bytes=32 time=44ms TTL=58
Reply from 64.71.255.204: bytes=32 time=15ms TTL=58
Request timed out.
Request timed out.
Reply from 64.71.255.204: bytes=32 time=13ms TTL=58
Reply from 64.71.255.204: bytes=32 time=34ms TTL=58
Reply from 64.71.255.204: bytes=32 time=51ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=16ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=19ms TTL=58
Reply from 64.71.255.204: bytes=32 time=15ms TTL=58
Reply from 64.71.255.204: bytes=32 time=32ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=28ms TTL=58
Reply from 64.71.255.204: bytes=32 time=13ms TTL=58
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Request timed out.
Request timed out.

Ping statistics for 64.71.255.204:
Packets: Sent = 50, Received = 34, Lost = 16 (32% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 94ms, Average = 22ms

Re: Question about Signal Levels

@JSS_BRAMPTON here's an experiment I'd like you to try if you have the time and patience.  If so I'd like you to run two command prompts simultaneously.  To do that start one command prompt and then simply hold down the shift key and select the command prompt again to start the second instance.  

 

1.  For the first command prompt, run a ping test to the DNS:  ping -t 64.71.255.204

     Start that test and just let it run.  To terminate it at some point use Ctrl +c

 

2.  For the second command prompt, type in a trace command to the DNS but, don't fire that until you see a "Request timed out."  The instant you see the time out, hit enter to start the trace.  What I'm hoping is that you'll start the trace during a series of time outs, two or three timeouts in a row.  I'd like to see what that looks like, if you can manage to pull that off.  Looking at the ping results, its looks like you don't have to wait very long before a series of time outs occur.  Its a bit of a guessing game when you trigger the trace, you won't know if you've hit the right multiple time out sequence until the trace is actually running and you see any additional time outs occur.  To quickly reenter the trace command when its done, hit the arrow up key when your curser is in the second command box to return to the previously entered command.  If you were using a series of commands, you can arrow up or down throughout the commands to reuse previously entered commands.  In this case, arrow up and simply wait for the next "Request timed out." to occur and hit enter to rerun the trace.  

 

How does that movie opening go "Your mission if you choose to accept it"......  Something like that.

 

Time and patience permitting, if possible:)  Hopefully it might produce something that @RogersAndy or @RogersTony  can use to forward to the engineers.  No guarantees but, worth a look to see what it produces.

 

Also when you have time, can you run the following IPV6 trace and ping to the primary IPV6 DNS:

 

tracert 2607:f798:18:10:0:640:7125:5204

 

ping -n 50 2607:f798:18:10:0:640:7125:5204

 

Please post those results as well.  To post the trace, please copy the trace results, paste them into a text editor and wipe out the entire portion of the hop #1 address to the right of the 2607 portion of the prefix.  That hop #1 address is the modem's address which shouldn't be posted in an open forum.  After wiping out most of that address please post the results.   

Re: Question about Signal Levels

JSS_BRAMPTON
I plan to stick around

@Datalink Mission accepted - ran several trace routes, trying to sync requests to time outs seen; for some reason IPV6 trace and ping to the primary IPV6 DNS failed.  Hope this sheds some light as to what's going on here. 

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms hitronhub.home [192.168.0.1]
2 16 ms 17 ms 10 ms 99.234.60.1
3 8 ms 8 ms 8 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 10 ms 7 ms 8 ms 209.148.232.229
5 8 ms 11 ms 8 ms 209.148.227.157
6 12 ms * 10 ms 10.202.47.161
7 9 ms * * dns.cp.net.rogers.com [64.71.255.204]
8 * * 10 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.


tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms hitronhub.home [192.168.0.1]
2 8 ms 8 ms 15 ms 99.234.60.1
3 11 ms 9 ms 8 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 9 ms 12 ms 9 ms 209.148.232.229
5 11 ms 8 ms 9 ms 209.148.227.157
6 * 10 ms * 10.202.47.161
7 * 9 ms 9 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 * 1 ms 2 ms hitronhub.home [192.168.0.1]
2 48 ms 9 ms 10 ms 99.234.60.1
3 7 ms 7 ms 8 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 11 ms 9 ms 9 ms 209.148.232.229
5 11 ms 8 ms 8 ms 209.148.227.157
6 22 ms 10 ms 9 ms 10.202.47.161
7 * 9 ms 9 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 * 1 ms 1 ms hitronhub.home [192.168.0.1]
2 48 ms 10 ms 7 ms 99.234.60.1
3 9 ms 10 ms 7 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 9 ms 9 ms 8 ms 209.148.232.229
5 9 ms 10 ms 9 ms 209.148.227.157
6 10 ms 10 ms * 10.202.47.161
7 10 ms 12 ms 8 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 * 1 ms 1 ms hitronhub.home [192.168.0.1]
2 8 ms 8 ms 10 ms 99.234.60.1
3 9 ms 4 ms 9 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 10 ms 9 ms 14 ms 209.148.232.229
5 10 ms 9 ms 10 ms 209.148.227.157
6 18 ms 13 ms 7 ms 10.202.47.161
7 * 10 ms 9 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms hitronhub.home [192.168.0.1]
2 29 ms 10 ms 10 ms 99.234.60.1
3 9 ms 9 ms 9 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 9 ms 9 ms 9 ms 209.148.232.229
5 9 ms 12 ms 10 ms 209.148.227.157
6 15 ms 9 ms 10 ms 10.202.47.161
7 9 ms * 9 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms hitronhub.home [192.168.0.1]
2 11 ms 10 ms 9 ms 99.234.60.1
3 9 ms 8 ms 7 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 8 ms 9 ms 10 ms 209.148.232.229
5 8 ms 10 ms 7 ms 209.148.227.157
6 13 ms 9 ms 10 ms 10.202.47.161
7 10 ms 11 ms 8 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms hitronhub.home [192.168.0.1]
2 7 ms 9 ms 10 ms 99.234.60.1
3 11 ms 7 ms 9 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 15 ms 9 ms 8 ms 209.148.232.229
5 10 ms 10 ms 12 ms 209.148.227.157
6 10 ms 31 ms 16 ms 10.202.47.161
7 9 ms * * dns.cp.net.rogers.com [64.71.255.204]
8 11 ms 9 ms * dns.cp.net.rogers.com [64.71.255.204]
9 * * * Request timed out.
10 * 8 ms 11 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 * 1 ms <1 ms hitronhub.home [192.168.0.1]
2 9 ms 14 ms 10 ms 99.234.60.1
3 7 ms 7 ms 6 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 10 ms 9 ms 10 ms 209.148.232.229
5 11 ms 9 ms 8 ms 209.148.227.157
6 14 ms 10 ms * 10.202.47.161
7 9 ms 7 ms 9 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms * <1 ms hitronhub.home [192.168.0.1]
2 10 ms 8 ms 10 ms 99.234.60.1
3 9 ms 9 ms 7 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 10 ms 9 ms 8 ms 209.148.232.229
5 9 ms 10 ms 10 ms 209.148.227.157
6 * * 9 ms 10.202.47.161
7 10 ms 9 ms 8 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms hitronhub.home [192.168.0.1]
2 10 ms 9 ms 17 ms 99.234.60.1
3 9 ms 11 ms 10 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 9 ms 9 ms 10 ms 209.148.232.229
5 15 ms 11 ms 10 ms 209.148.227.157
6 9 ms 8 ms 10 ms 10.202.47.161
7 9 ms 6 ms 7 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms hitronhub.home [192.168.0.1]
2 10 ms 9 ms 9 ms 99.234.60.1
3 9 ms 10 ms 11 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 11 ms 13 ms 9 ms 209.148.232.229
5 11 ms 7 ms 8 ms 209.148.227.157
6 10 ms * 9 ms 10.202.47.161
7 * 8 ms 9 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms hitronhub.home [192.168.0.1]
2 11 ms 8 ms 10 ms 99.234.60.1
3 8 ms 8 ms 10 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 13 ms 11 ms 10 ms 209.148.232.229
5 9 ms 16 ms 9 ms 209.148.227.157
6 65 ms * 8 ms 10.202.47.161
7 10 ms 9 ms 7 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 * <1 ms 1 ms hitronhub.home [192.168.0.1]
2 10 ms 9 ms 11 ms 99.234.60.1
3 9 ms 8 ms 11 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 17 ms 11 ms 24 ms 209.148.232.229
5 14 ms 9 ms 7 ms 209.148.227.157
6 10 ms * 11 ms 10.202.47.161
7 11 ms 8 ms * dns.cp.net.rogers.com [64.71.255.204]
8 8 ms 7 ms 19 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms hitronhub.home [192.168.0.1]
2 9 ms 9 ms 9 ms 99.234.60.1
3 11 ms 10 ms 8 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 10 ms 9 ms 10 ms 209.148.232.229
5 508 ms 7 ms 9 ms 209.148.227.157
6 10 ms * 9 ms 10.202.47.161
7 * 11 ms 19 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms hitronhub.home [192.168.0.1]
2 8 ms 8 ms 9 ms 99.234.60.1
3 10 ms 9 ms 7 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 9 ms 12 ms 11 ms 209.148.232.229
5 10 ms 8 ms 11 ms 209.148.227.157
6 * 12 ms 9 ms 10.202.47.161
7 * 10 ms 9 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms hitronhub.home [192.168.0.1]
2 9 ms 10 ms 10 ms 99.234.60.1
3 8 ms 8 ms 9 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 10 ms 9 ms 10 ms 209.148.232.229
5 10 ms 10 ms 8 ms 209.148.227.157
6 11 ms 12 ms 8 ms 10.202.47.161
7 13 ms * 8 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms hitronhub.home [192.168.0.1]
2 10 ms 10 ms 16 ms 99.234.60.1
3 10 ms 8 ms 8 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 11 ms 10 ms 10 ms 209.148.232.229
5 10 ms 10 ms 10 ms 209.148.227.157
6 * * * Request timed out.
7 * 9 ms 10 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms hitronhub.home [192.168.0.1]
2 8 ms 13 ms 8 ms 99.234.60.1
3 11 ms 8 ms 8 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 9 ms 10 ms 10 ms 209.148.232.229
5 9 ms 8 ms 11 ms 209.148.227.157
6 14 ms 14 ms 10 ms 10.202.47.161
7 * 10 ms 8 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms hitronhub.home [192.168.0.1]
2 10 ms 6 ms 10 ms 99.234.60.1
3 9 ms 15 ms 8 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 11 ms 11 ms 10 ms 209.148.232.229
5 9 ms 10 ms 10 ms 209.148.227.157
6 9 ms 8 ms * 10.202.47.161
7 7 ms 8 ms 8 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms hitronhub.home [192.168.0.1]
2 8 ms 8 ms 7 ms 99.234.60.1
3 11 ms 9 ms 9 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 11 ms 10 ms 9 ms 209.148.232.229
5 8 ms 9 ms 8 ms 209.148.227.157
6 * 15 ms 9 ms 10.202.47.161
7 7 ms * 7 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms hitronhub.home [192.168.0.1]
2 9 ms 8 ms 9 ms 99.234.60.1
3 8 ms 9 ms 9 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 11 ms 9 ms 9 ms 209.148.232.229
5 10 ms 9 ms 9 ms 209.148.227.157
6 17 ms 17 ms 9 ms 10.202.47.161
7 * 64 ms * dns.cp.net.rogers.com [64.71.255.204]
8 9 ms 9 ms 9 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms hitronhub.home [192.168.0.1]
2 10 ms 61 ms 49 ms 99.234.60.1
3 9 ms 7 ms 16 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 11 ms 13 ms 9 ms 209.148.232.229
5 9 ms 9 ms 9 ms 209.148.227.157
6 9 ms 12 ms 9 ms 10.202.47.161
7 8 ms 10 ms 8 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms hitronhub.home [192.168.0.1]
2 12 ms 12 ms 8 ms 99.234.60.1
3 7 ms 9 ms 8 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 9 ms 11 ms 8 ms 209.148.232.229
5 9 ms 12 ms 8 ms 209.148.227.157
6 11 ms 11 ms 11 ms 10.202.47.161
7 * 9 ms * dns.cp.net.rogers.com [64.71.255.204]
8 * 10 ms 8 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms * * hitronhub.home [192.168.0.1]
2 12 ms 11 ms 8 ms 99.234.60.1
3 7 ms 7 ms 14 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 9 ms 8 ms 10 ms 209.148.232.229
5 11 ms 9 ms 10 ms 209.148.227.157
6 10 ms * 11 ms 10.202.47.161
7 12 ms 10 ms 9 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 * 1 ms 1 ms hitronhub.home [192.168.0.1]
2 14 ms 10 ms 8 ms 99.234.60.1
3 9 ms 7 ms 12 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 12 ms 9 ms 10 ms 209.148.232.229
5 9 ms 8 ms 8 ms 209.148.227.157
6 11 ms 11 ms 10 ms 10.202.47.161
7 * * * Request timed out.
8 8 ms * 8 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms hitronhub.home [192.168.0.1]
2 10 ms 9 ms 8 ms 99.234.60.1
3 10 ms 9 ms 9 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 12 ms 13 ms 9 ms 209.148.232.229
5 9 ms 10 ms 9 ms 209.148.227.157
6 * 65 ms 9 ms 10.202.47.161
7 9 ms 7 ms 8 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms hitronhub.home [192.168.0.1]
2 11 ms 10 ms 9 ms 99.234.60.1
3 8 ms 11 ms 9 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 8 ms 12 ms 10 ms 209.148.232.229
5 10 ms 9 ms 9 ms 209.148.227.157
6 * 11 ms 12 ms 10.202.47.161
7 * * * Request timed out.
8 14 ms * 11 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 2607:f798:18:10:0:640:7125:5204

Tracing route to dns.cp.net.rogers.com [2607:f798:18:10:0:640:7125:5204]
over a maximum of 30 hops:

1 Transmit error: code 1231.

Trace complete.

 

tracert 2607:f798:18:10:0:640:7125:5204

Tracing route to dns.cp.net.rogers.com [2607:f798:18:10:0:640:7125:5204]
over a maximum of 30 hops:

1 Transmit error: code 1231.

Trace complete.


ping -n 50 2607:f798:18:10:0:640:7125:5204

 

Pinging 2607:f798:18:10:0:640:7125:5204 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.

 

Ping statistics for 2607:f798:18:10:0:640:7125:5204:
Packets: Sent = 50, Received = 0, Lost = 50 (100% loss),

 

Re: Question about Signal Levels

JSS_BRAMPTON
I plan to stick around
Tech was here today and noted noise at the tap end. Will open ticket with the relevant department - 72 hours to update.

Lost registration on both my VOIP phones and SIP ports were locked.

Waiting on Rogers

Re: Question about Signal Levels

@JSS_BRAMPTON did the tech do anything while he was there, swap connectors, check the external cable? Or did he just note the noise problem and kick that along to someone else?

 

Thanks very much for the traces.  They don't contain the data that I was hoping for but thanks very much for giving it a go.  I was hoping that you would see some huge discrepancy from hop #2 (CMTS) or possibly from another router downstream.  There are a couple of higher returns from hop #2 in the group and a single high point in a downstream router, but, thats it.  So, that's a little surprising at this point.  Going to have to think about this .....

 

If and when you have time, can you have a look at the following:

 

1.  Log into your modem and navigate to the BASIC .... GATEWAY FUNCTION tab.  Have a look at the Router mode.  Is it in Dual mode or IPV4 mode?  Thats it for this step. 

 

2.  If the Router mode is in Dual mode, at a command prompt, run the following commands:  

 

ipconfig

 

ipconfig/all

 

What you should see is that the ethernet or wifi adapter has an IPV6 address starting with 2607.  If you look at the following page, the second example (Newer Next) shows the display with IPV6 running. 

 

https://www.cellstream.com/reference-reading/tipsandtricks/121-ipv6-windowslinux-command-line-exampl...

 

So, you should see that the adapter has an IPV6 address or group of IPV6 addresses first, then an IPV4 address.  There may be more than one temporary IPV6 address.  

 

So, if you do see an IPV6 or group of IPV6 addresses starting with 2607 (Rogers), but IPV6 trace and ping is failing, that implies that the CMTS is not configured properly for IPV6 ops.  Yes, you're getting an IPV6 prefix assignment from the CMTS, but, the CMTS isn't allowing IPV6 data to return to the pc.  Thats a CMTS configuration error of some type, which seems to be common these days for some reason. 

 

 

 

 

 

 

Re: Question about Signal Levels

JSS_BRAMPTON
I plan to stick around
Tech tested my connection, eliminating any backfeed from the other (8+3) subscribers and concluded noise was at the headend level. He ran his tests inside stating all was to spec and after he refers the noise issue to the relevant team, service should improve in 72 hours.

Modem is set on IPv4.

VOIP service acted up again after rebooting modem found SIP ports locked... now a daily painful routine.
Topic Stats
  • 17 replies
  • 4848 views
  • 3 Likes
  • 6 in conversation