Menu
Reply
  • 20
  • 0
  • 0
Snowy90
Joining in
410 Views
Message 11 of 33
Flag for a moderator

Re: Super Hub 3 no valid ip address

whats the easiest way to post the logs?

They are very long!
0 Kudos
Reply
  • 20
  • 0
  • 0
Snowy90
Joining in
410 Views
Message 12 of 33
Flag for a moderator

Re: Super Hub 3 no valid ip address

Up stream log.PNGDownstream logs.PNGNetwork log.PNG

0 Kudos
Reply
  • 20
  • 0
  • 0
Snowy90
Joining in
407 Views
Message 13 of 33
Flag for a moderator

Re: Super Hub 3 no valid ip address

Down Stream

1234750000-0.938256 qam13
2170750000-0.538256 qam5
3178750000-0.738256 qam6
4186750000-0.738256 qam7
5194750000-0.738256 qam8
6202750000-0.538256 qam9
7210750000-0.538256 qam10
8218750000-0.938256 qam11
9226750000-0.938256 qam12
10242750000-138256 qam14
11250750000-0.538256 qam15
12258750000-0.938256 qam16
13266750000-0.738256 qam17
14274750000-1.238256 qam18
15282750000-0.938256 qam19
16290750000-0.738256 qam20
17298750000-0.538256 qam21
18306750000-0.438256 qam22
19314750000-0.538256 qam23
20322750000-0.538256 qam24
21402750000-0.538256 qam25
22410750000-0.238256 qam26
23418750000-0.740256 qam27
24426750000-0.538256 qam28



Downstream bonded channels

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

1Locked38.940
2Locked38.950
3Locked38.650
4Locked38.650
5Locked38.950
6Locked38.660
7Locked38.600
8Locked38.660
9Locked38.640
10Locked38.610
11Locked38.960
12Locked38.640
13Locked38.950
14Locked38.650
15Locked38.950
16Locked38.960
17Locked38.650
18Locked38.950
19Locked38.950
20Locked38.900
21Locked38.950
22Locked38.950
23Locked40.310
24Locked38.910

 

Up stream 

1537000005.1512064 qam2
2603000005.1512064 qam1
3462000005.1512064 qam3
4394000095.1512064 qam4



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000
0 Kudos
Reply
  • 20
  • 0
  • 0
Snowy90
Joining in
406 Views
Message 14 of 33
Flag for a moderator

Re: Super Hub 3 no valid ip address

Network Log

Time Priority Description

05/09/2019 09:09:8Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/09/2019 09:09:8Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2019 12:44:20criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/09/2019 04:36:32ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/09/2019 04:29:4criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/09/2019 08:10:18ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/09/2019 12:06:36ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/09/2019 08:36:32criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/09/2019 13:55:14Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/09/2019 13:55:14criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/09/2019 13:55:15Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/09/2019 13:55:15criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/09/2019 13:55:19Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/09/2019 13:55:20Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/09/2019 13:56:21criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/09/2019 13:56:22Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/09/2019 13:56:37criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/09/2019 13:56:56Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/09/2019 22:53:3criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/09/2019 23:31:30Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
  • 11.8K
  • 1.08K
  • 2.56K
griffin
Alessandro Volta
367 Views
Message 15 of 33
Flag for a moderator

Re: Super Hub 3 no valid ip address

Your upstream power levels are at max transmit and need VM to take a closer look.
there looks like there is a touch of intermittent noise on the downstream.

It maybe worth giving the coax cable from the Hub to the cable entry point checking obvious signs of damage and all connectors are hand tight.

You will need to contact VM for resolution, either by waiting here about a week until a VM Forum Team Member picks up the thread, or give them a call on 150 from a VM line or 0345 454 1111 for a quicker response.

0 Kudos
Reply
  • 20
  • 0
  • 0
Snowy90
Joining in
355 Views
Message 16 of 33
Flag for a moderator

Re: Super Hub 3 no valid ip address

can you tell me what the logs should look like?
Any obvious pointers?

I will check the connections
0 Kudos
Reply
  • 1.76K
  • 94
  • 189
Forum Team
Forum Team
353 Views
Message 17 of 33
Flag for a moderator

Re: Super Hub 3 no valid ip address

Hi there @Snowy90

 

Cheers for your posts and the logs that you have supplied - they've helped us take a look at your services. 

 

Your upstream are within specification but are at the higher end of what we would usually expect (max is usually around 54 and you're getting around 51).

 

What we have done is contact the Area Manager to ask their thoughts of what the best course of action would be in this situation - they may be able to check them out without a visit or advise if a new Hub would be the best option. 

 

Once we have any reply, we'll be back in touch (usually takes a couple of days for a reply)

 

in the meantime, check the connections and keep us posted on how things are at your end. 

 

Cheers

Katie - Forum Team


New around here? To find out more about the Community check out our Getting Started guide


0 Kudos
Reply
  • 11.8K
  • 1.08K
  • 2.56K
griffin
Alessandro Volta
351 Views
Message 18 of 33
Flag for a moderator

Re: Super Hub 3 no valid ip address

Ideally you should only see the DHCP errors, and some registration messages when the Hub boots up like the TOD and IP messages.

To understand the logs you need to understand the Docsis registration, ranging and station maintenance processes, and have a bit of artistic interpretation as the logs are far from comprehensive. Further reading here.

In your case, there is a period where the Hub is not picking up the SYNC message from VM's CMTS.
The Hub uses this message to update it's clock to match the CMTS's clock.
If the SYNC is not received, usually due to downstream noise, the Hub need to wait for the next SYNC to continue.
The odd loss of SYNC is not problematic, but as your logs are showing repeated loss of SYNCs in a short space of time, then this can affect performance.

0 Kudos
Reply
  • 11.8K
  • 1.08K
  • 2.56K
griffin
Alessandro Volta
349 Views
Message 19 of 33
Flag for a moderator

Re: Super Hub 3 no valid ip address


@Katie_WT wrote:

Hi there @Snowy90

 

Cheers for your posts and the logs that you have supplied - they've helped us take a look at your services. 

 

Your upstream are within specification but are at the higher end of what we would usually expect (max is usually around 54 and you're getting around 51).

 

What we have done is contact the Area Manager to ask their thoughts of what the best course of action would be in this situation - they may be able to check them out without a visit or advise if a new Hub would be the best option. 

 

Once we have any reply, we'll be back in touch (usually takes a couple of days for a reply)

 

in the meantime, check the connections and keep us posted on how things are at your end. 

 

Cheers


The max transmit for 4 upstream channels is 51dBmV using 64QAM.
If they are two upstream channels, then halve the power. max transmit for two upstream channels is 54dBmV at 64QAM.

0 Kudos
Reply
  • 20
  • 0
  • 0
Snowy90
Joining in
339 Views
Message 20 of 33
Flag for a moderator

Re: Super Hub 3 no valid ip address

Thanks for the explanation, way over my head!

 

And thanks to the VM guys hopefully will get to the bottom of this

0 Kudos
Reply