Menu
Reply
  • 4
  • 0
  • 0
jmslcs
Tuning in
372 Views
Message 1 of 29
Flag for a moderator

Hub 3 randomly rebooting

Hi,

Just looking for a bit of advice with what might be going on with my router. Yesterday thought the day it was randomly rebooting, to try and resolve the issue and check logs, I tried logging in to the router. I was unable to as the password was incorrect, although I'm fairly sure of the password and hadn't changed it, so only way to get back in would be a reset. After the reset all seemed will for about an hour then it got stuck in a constant cycle of rebooting. I left it over night and it seems fine today but not sure for how long.

When I've checked the logs this morning (as below) it is showing some critical errors at around 8am, but I cant figure out how to get more of the logs as they only show a few seconds from this morning and nothing further. Is there a way?

All throughout the VM website was showing no issues in my area. The testing wanted to book an engineer, but wanted to see if a simple router swap would fix the issue. Also worth noting that my routers bottom light is constantly red no matter where it is situated even directly in front of a fan lol! (unless in modem mode it shows a different colour? I feel like I've read pink somewhere but I could be wrong)

Time Priority Description

05/02/2020 08:24:43criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2020 08:24:44criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2020 08:24:44criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2020 08:24:45criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2020 08:24:45criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2020 08:24:46criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2020 08:24:46criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2020 08:24:47criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2020 08:24:47criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2020 08:24:48criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2020 08:24:48criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2020 08:24:49criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2020 08:24:49criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2020 08:24:50criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2020 08:24:50criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2020 08:24:51criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2020 08:24:52criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2020 08:24:52criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2020 08:25:23criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2020 11:22:51criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

I don't want to post a huge post, so if any more logs are needed I'll add them in. Thanks in advanced 🙂

0 Kudos
Reply
Highlighted
  • 1.07K
  • 52
  • 143
MikeRobbo
Knows their stuff
370 Views
Message 2 of 29
Flag for a moderator

Re: Hub 3 randomly rebooting

Have you checked the 'Check Service Status' at the top of the page?

If nothing is showing try phoning 0800 561 0061, this will tell you of more local issues that may not be affecting the area.

Firstly set up a BQM at thinkbroadband.com - this will give you an insight into what is happening with the signal coming into the property, it will take a few hours to get any kind of trend showing.

then

It may be a good idea to carry out a factory reset on the Hub …

With the Hub Powered on use a paperclip or similar do a pinhole reset.

Depress the pinhole switch for a timed 60 seconds then release.

DO NOT reboot the hub but allow it 5 to 10 minutes for it to boot itself up.

Once a steady white and no other lights are illuminated check your system again.

then

Type 192.168.0.1 into your browser URL bar and press enter.  When the page appears DO NOT LOG IN but click ‘Check Router Status’. Copy and paste the contents of each tab onto here, a Guru will be along soon to decipher the info.

Highlighted
  • 6.6K
  • 511
  • 1.1K
Tudor
Legend
362 Views
Message 3 of 29
Flag for a moderator

Re: Hub 3 randomly rebooting

Those T3’s usually indicate a noise ingress problem. Phone customer services and report the problem. 


Tudor
There are 10 types of people: those who understand binary and those who don't and F people out of 10 who do not understand hexadecimal c1a2a285948293859940d9a49385a2
Highlighted
  • 4
  • 0
  • 0
jmslcs
Tuning in
343 Views
Message 4 of 29
Flag for a moderator

Re: Hub 3 randomly rebooting

Hi Mike,

Thanks for coming back to me.

I had been checking the service status throughout and it was indicating no issues. I completed the factory reset and that's when the issue become worse although it doesn't seem like there are any issues today.

Thanks for the heads up re BQM I've set this up and will keep an eye over the next few hours. I find it strange that the only logs showing are from this morning. No logs from last night after the reset and I did check last night but didn't keep them and I did see logs.

Just spoken with CS they're telling me there is a fault in the area, although this doesn't show online. Should be fixed by the 12th 🙄

0 Kudos
Reply
Highlighted
  • 4
  • 0
  • 0
jmslcs
Tuning in
326 Views
Message 5 of 29
Flag for a moderator

Re: Hub 3 randomly rebooting

Acquired Downstream Channel (Hz)
402750000
Locked
Ranged Upstream Channel (Hz)
32600000
Locked
Provisioning State
Online

 

Downstream:

14027500003.240256 qam25
21947500004.940256 qam8
32027500004.440256 qam9
42107500004.540256 qam10
52187500004.340256 qam11
6226750000440256 qam12
72347500003.940256 qam13
82427500003.740256 qam14
92507500003.240256 qam15
10258750000340256 qam16
112667500002.740256 qam17
122747500002.440256 qam18
132827500002.540256 qam19
142907500002.240256 qam20
152987500002.538256 qam21
163067500002.540256 qam22
173147500002.240256 qam23
18322750000340256 qam24
194107500002.940256 qam26
20418750000340256 qam27
214267500002.540256 qam28
224347500002.738256 qam29
234427500002.540256 qam30
244507500001.940256 qam31

 

1Locked40.300
2Locked40.360
3Locked40.950
4Locked40.9100
5Locked40.360
6Locked40.960
7Locked40.960
8Locked40.360
9Locked40.950
10Locked40.370
11Locked40.9120
12Locked40.3120
13Locked40.960
14Locked40.3140
15Locked38.950
16Locked40.3220
17Locked40.300
18Locked40.300
19Locked40.930
20Locked40.944912
21Locked38.93050
22Locked38.9420
23Locked40.3120
24Locked40.3860

 

Upstream

1326000004.375512064 qam3
2537000564.625512064 qam5
3258000004.325512064 qam4
4394000004.375512064 qam2
5462000004.525512064 qam1

 

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000
5ATDMA0000

 

Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
vca69834ncxv9873254k;fg87dsfd;k
SFID686
Max Traffic Rate402500089
Max Traffic Burst42600
Min Traffic Rate0
SFID685
Max Traffic Rate38500089
Max Traffic Burst42600
Min Traffic Rate0
Max Concatenated Burst42600
Scheduling TypeBestEffort
0 Kudos
Reply
Highlighted
  • 4
  • 0
  • 0
jmslcs
Tuning in
293 Views
Message 6 of 29
Flag for a moderator

Re: Hub 3 randomly rebooting

100% packet loss 

I feel like such a noob for the life of me I can’t add in my graph, either way it’s red 😂

https://www.thinkbroadband.com/broadband/monitoring/quality/share/2a20b8f8d09fae38d7e02cfc6ed189c3d1...

0 Kudos
Reply
Highlighted
  • 3.42K
  • 158
  • 269
Forum Team
Forum Team
279 Views
Message 7 of 29
Flag for a moderator
Helpful Answer

Re: Hub 3 randomly rebooting

Hi jmslcs,

 

Thanks for posting and welcome to the community. 

 

I am sorry to hear of the rebooting issue with the router and I fully understand the annoyance and inconvienience this would cause. From checking our systems, there is an SNR (signal to noise ratio) affecting the service in your area and the estimated fix date is the 12th February 2020.

 

The fault reference is F007764790 for your records.

 

Kind regards,

John_GS
Forum Team

Need a helpful hand to show you how to make a payment? Check out our guide - "How to pay my Virgin Media bill"

Highlighted
  • 12
  • 0
  • 0
duncan60
Joining in
178 Views
Message 8 of 29
Flag for a moderator

Re: Hub 3 randomly rebooting

HI guys

I am a newbie here but have same problems with intermittent rebooting.

here are logs.

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

12510000006.540256 qam15
2139000000738256 qam1
31470000007.138256 qam2
41550000007.138256 qam3
51630000007.340256 qam4
61710000007.438256 qam5
71790000007.338256 qam6
81870000007.338256 qam7
91950000007.138256 qam8
10203000000738256 qam9
112110000006.938256 qam10
122190000006.940256 qam11
132270000006.940256 qam12
142350000006.840256 qam13
152430000006.638256 qam14
162590000006.440256 qam16
172670000006.340256 qam17
18275000000640256 qam18
19283000000640256 qam19
20291000000640256 qam20
212990000006.338256 qam21
223070000006.440256 qam22
233150000006.540256 qam23
243230000006.440256 qam24

 

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

1394000363.825512064 qam12
2461999883.775512064 qam11
3536999863.825512064 qam10
4603000173.775512064 qam

9

 

 

 

 

 

 

 

 

Network Log

Time Priority Description

31/01/2020 20:52:58criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2020 10:56:46criticalRanging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2020 10:56:46criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2020 10:56:47criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/02/2020 01:58:11criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/02/2020 02:01:0criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/02/2020 12:25:52criticalRanging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/02/2020 12:25:52criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/02/2020 12:25:52criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/02/2020 12:27:48criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/02/2020 12:30:32criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/02/2020 05:06:1ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/02/2020 09:20:25criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/02/2020 17:11:4ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/02/2020 17:47:17criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/02/2020 23:29:4criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/02/2020 23:31:52criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/02/2020 13:12:48criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/02/2020 13:12:48criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/02/2020 21:35:20critical

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

 

any help would be appreciated.

 

regards

 

duncan

0 Kudos
Reply
Highlighted
  • 1.02K
  • 45
  • 68
Forum Team
Forum Team
163 Views
Message 9 of 29
Flag for a moderator

Re: Hub 3 randomly rebooting

Hello duncan60

 

Thanks for taking the time to post on the forums and welcome to the community. Sorry to hear of the service issues and rebooting of the Hub.

 

Can you confirm how long this has been happening for and if this is effecting anyone else in your area (if you know)?

 

Rob

0 Kudos
Reply
Highlighted
  • 12
  • 0
  • 0
duncan60
Joining in
141 Views
Message 10 of 29
Flag for a moderator

Re: Hub 3 randomly rebooting

hi Rob
thanks for your quick response.
it has beien going on since end of January and i dont know if anyone else in area is experiencing same problem.
here is updated log from today as still disconnecting.
regards

duncan

Refresh data
Network Log
Time Priority Description
02/02/2020 10:56:46 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2020 10:56:47 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/02/2020 01:58:11 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/02/2020 02:01:0 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/02/2020 12:25:52 critical Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/02/2020 12:25:52 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/02/2020 12:25:52 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/02/2020 12:27:48 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/02/2020 12:30:32 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/02/2020 05:06:1 Error DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/02/2020 09:20:25 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/02/2020 17:11:4 Error DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/02/2020 17:47:17 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/02/2020 23:29:4 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/02/2020 23:31:52 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/02/2020 13:12:48 critical Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/02/2020 13:12:48 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/02/2020 21:35:20 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/02/2020 05:02:13 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/02/2020 05:04:28 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Refresh data
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 267000000 6.1 40 256 qam 17
2 139000000 6.8 38 256 qam 1
3 147000000 7 38 256 qam 2
4 155000000 7 38 256 qam 3
5 163000000 7 40 256 qam 4
6 171000000 7.1 38 256 qam 5
7 179000000 7 38 256 qam 6
8 187000000 7.1 38 256 qam 7
9 195000000 7 40 256 qam 8
10 203000000 6.9 38 256 qam 9
11 211000000 6.8 38 256 qam 10
12 219000000 6.6 40 256 qam 11
13 227000000 6.6 40 256 qam 12
14 235000000 6.6 40 256 qam 13
15 243000000 6.5 40 256 qam 14
16 251000000 6.4 40 256 qam 15
17 259000000 6.3 40 256 qam 16
18 275000000 5.9 40 256 qam 18
19 283000000 5.9 40 256 qam 19
20 291000000 6 40 256 qam 20
21 299000000 6 38 256 qam 21
22 307000000 6.1 40 256 qam 22
23 315000000 6.4 40 256 qam 23
24 323000000 6.3 40 256 qam 24


Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 40.3 7 0
2 Locked 38.9 0 0
3 Locked 38.6 5 0
4 Locked 38.9 7 0
5 Locked 40.3 5 0
6 Locked 38.9 4 0
7 Locked 38.6 8 0
8 Locked 38.9 4 0
9 Locked 40.3 6 0
10 Locked 38.9 5 0
11 Locked 38.9 5 0
12 Locked 40.3 8 0
13 Locked 40.3 10 0
14 Locked 40.3 6 0
15 Locked 40.3 8 0
16 Locked 40.3 6 0
17 Locked 40.9 5 0
18 Locked 40.3 8 0
19 Locked 40.3 7 0
20 Locked 40.9 6 0
21 Locked 38.9 3 0
22 Locked 40.3 6 0
23 Locked 40.3 6 0
24 Locked 40.9 14 0

Refresh data
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 39400000 4.05 5120 64 qam 12
2 32599986 4.025 5120 64 qam 13
3 46199971 3.475 5120 64 qam 11
4 53699959 4.1 5120 64 qam 10


Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 0 0
2 ATDMA 0 0 0 0
3 ATDMA 0 0 0 0
4 ATDMA 0 0 0 0
0 Kudos
Reply