Menu
Reply
Highlighted
  • 16
  • 1
  • 0
Norbert_K
On our wavelength
613 Views
Message 1 of 15
Flag for a moderator

weird connection issues (still)

Hi,

 

A week ago I have contacted the support team with an issue I'm having since weeks at this point.

I received a replacement HUB with the help of Alex_RM, and today the problem returned.

Please take a look at these graphs:

19/9

20/9

21/9

22/9

Any ideas?

0 Kudos
Reply
Highlighted
  • 16
  • 1
  • 0
Norbert_K
On our wavelength
609 Views
Message 2 of 15
Flag for a moderator

Re: weird connection issues (still)

Downstream bonded channels

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

11387500008.538256 qam1
21467500008.438256 qam2
31547500008.338256 qam3
41627500008.138256 qam4
5170750000838256 qam5
6178750000838256 qam6
71867500007.638256 qam7
81947500007.440256 qam8
92027500007.338256 qam9
10210750000738256 qam10
112187500006.938256 qam11
122267500006.638256 qam12
132347500006.438256 qam13
142427500006.338256 qam14
15250750000638256 qam15
162587500005.938256 qam16
17266750000638256 qam17
182747500005.638256 qam18
192827500005.938256 qam19
202907500005.938256 qam20
21298750000638256 qam21
223067500006.138256 qam22
23314750000638256 qam23
24322750000638256 qam24



Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked38.91306814634
2Locked38.91318615299
3Locked38.91209516581
4Locked38.91118817390
5Locked38.9868119838
6Locked38.9962718959
7Locked38.9934719183
8Locked40.31050617975
9Locked38.61094717540
10Locked38.91157416870
11Locked38.91190416727
12Locked38.91225216491
13Locked38.61244916324
14Locked38.91299515548
15Locked38.61301415621
16Locked38.91310515119
17Locked38.91334313894
18Locked38.91264613929
19Locked38.91253713136
20Locked38.995728454
21Locked38.91236210436
22Locked38.9116339429
23Locked38.9118258077
24Locked38.9116646863
0 Kudos
Reply
Highlighted
  • 16
  • 1
  • 0
Norbert_K
On our wavelength
608 Views
Message 3 of 15
Flag for a moderator

Re: weird connection issues (still)

Upstream bonded channels

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

1462000003.9512064 qam3
2394000003.9512064 qam4
3258000003.825512064 qam6
4326000003.85512064 qam5



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000
0 Kudos
Reply
Highlighted
  • 16
  • 1
  • 0
Norbert_K
On our wavelength
607 Views
Message 4 of 15
Flag for a moderator

Re: weird connection issues (still)

General Configuration

Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
cmreg-vmdg505-rtsl10016u-b.cm



Primary Downstream Service Flow

SFID786146
Max Traffic Rate117000047
Max Traffic Burst42600
Min Traffic Rate0



Primary Upstream Service Flow

SFID786145
Max Traffic Rate10500047
Max Traffic Burst16320
Min Traffic Rate0
Max Concatenated Burst16320
Scheduling TypeBestEffort
0 Kudos
Reply
Highlighted
  • 12.91K
  • 513
  • 1.18K
legacy1
Alessandro Volta
581 Views
Message 5 of 15
Flag for a moderator

Re: weird connection issues (still)

Put the hub in modem mode and get your own wireless router with 1Gb ports.

0 Kudos
Reply
Highlighted
  • 16
  • 1
  • 0
Norbert_K
On our wavelength
520 Views
Message 6 of 15
Flag for a moderator

Re: weird connection issues (still)

Dude, it was fine for almost a year. 

Why would I do that if it's clearly a fault with the current set up? Won't solve the problem.

Tried modem mode and the problem is the same anyway.

0 Kudos
Reply
  • 11.48K
  • 256
  • 1.57K
horseman
Alessandro Volta
508 Views
Message 7 of 15
Flag for a moderator

Re: weird connection issues (still)

Symptoms reflect known TBB-BQM "resource" issue on Hub/SH 3 from 6xx to 613 firmware versions! Easily clarified by enabling alternative BQM ICMP host's: eg f8lure@mouslike.com ..... Normally I'd emphasise the point of ALWAYS browsing the mere 2.3 million posts that include these specific issue.... and many SuperUser escalations since 2015 that have been escalated but can't be published here.

EDIT: I should also add that OP's "tap" may  not be optimal but that requires onsite visit to cab AND confirmation that no additional online termination exists on incoming feed.....   Enabling alternate ICMP/BQM and Publishing NetworkLog and refreshed Upstream/Downstream stats for this V100 service may also reveal further clues?

Regards Tony
"Life is a Binary Inspired Turing Computed Hologram"(don't PM or @Mention me - in case ignoring you offends)
DEFROCKED
Highlighted
  • 16
  • 1
  • 0
Norbert_K
On our wavelength
498 Views
Message 8 of 15
Flag for a moderator

Re: weird connection issues (still)

Hi,

 

I'll post some refreshed data when I get home later on.

Seems like the drop out I also have is a common issue, still couldn't find an answer.

I suppose it's got something to do with with wires/connectors outside the house as everything was replaced internally, including cable between hub and PC and the hub itself.

Do you know how could I possibly get an engineer out? I'm trying to avoid talking to customer services as they are useless.

Thanks

0 Kudos
Reply
Highlighted
  • 16
  • 1
  • 0
Norbert_K
On our wavelength
482 Views
Message 9 of 15
Flag for a moderator

Re: weird connection issues (still)

Here's an update.

ATM I got a white light on the hub3.

22-9 updated and 23-9

Cable Modem StatusItem Status Comments

Acquired Downstream Channel (Hz)
138750000
Locked
Ranged Upstream Channel (Hz)
46200000
Locked
Provisioning State
Online

Downstream bonded channels

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

11387500008.538256 qam1
21467500008.338256 qam2
31547500008.138256 qam3
41627500008.138256 qam4
5170750000838256 qam5
6178750000838256 qam6
71867500007.538256 qam7
81947500007.339256 qam8
92027500007.138256 qam9
102107500006.838256 qam10
112187500006.638256 qam11
122267500006.538256 qam12
132347500006.138256 qam13
14242750000638256 qam14
152507500005.838256 qam15
162587500005.638256 qam16
17266750000638256 qam17
182747500005.838256 qam18
19282750000638256 qam19
20290750000638256 qam20
212987500006.338256 qam21
223067500006.538256 qam22
233147500006.438256 qam23
243227500006.138256 qam24



Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked38.61310114634
2Locked38.91321015299
3Locked38.91210716581
4Locked38.91119817390
5Locked38.9869919838
6Locked38.9963718959
7Locked38.9935719183
8Locked39.31055017975
9Locked38.61095717540
10Locked38.91160016870
11Locked38.91191216727
12Locked38.91227316491
13Locked38.91247616324
14Locked38.91301915548
15Locked38.91304615621
16Locked38.91312815119
17Locked38.91336813894
18Locked38.91269513929
19Locked38.91256713136
20Locked38.696208454
21Locked38.61239310436
22Locked38.9116589429
23Locked38.6118618077
24Locked38.9116836863

 

Upstream bonded channels

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

1462000003.9512064 qam3
2394000003.9512064 qam4
3257999413.825512064 qam6
4326000003.85512064 qam5



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

 

0 Kudos
Reply
Highlighted
  • 16
  • 1
  • 0
Norbert_K
On our wavelength
481 Views
Message 10 of 15
Flag for a moderator

Re: weird connection issues (still)

General Configuration

Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
cmreg-vmdg505-rtsl10016u-b.cm



Primary Downstream Service Flow

SFID786146
Max Traffic Rate117000047
Max Traffic Burst42600
Min Traffic Rate0



Primary Upstream Service Flow

SFID786145
Max Traffic Rate10500047
Max Traffic Burst16320
Min Traffic Rate0
Max Concatenated Burst16320
Scheduling TypeBestEffort

 

Network Log

Time Priority Description

22/09/2019 18:58:50Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/09/2019 18:58:50criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/09/2019 18:58:50Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/09/2019 18:58:53criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/09/2019 18:58:53Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/09/2019 18:58:53criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/09/2019 18:58:53Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/09/2019 18:58:54criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/09/2019 18:58:55Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/09/2019 18:58:56criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/09/2019 18:59:4Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/09/2019 18:59:5criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/09/2019 18:59:6Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/09/2019 18:59:6criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/09/2019 18:59:7Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/09/2019 18:59:9criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/09/2019 18:59:9Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/09/2019 18:59:10criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/09/2019 18:59:12Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/09/2019 11:03:1criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

0 Kudos
Reply