Menu
Reply
On our wavelength
  • 149
  • 14
  • 27
Registered: ‎22-02-2017
Message 1 of 5 (83 Views)

SHub 2 Power Levels Uneven

[ Edited ]

The Downstream log below shows a spread of about 3dB with the highest level being 8.69. I believe this is at the top end of acceptable but can see from the errors that errors are proportional to the level. Can a VM rep please comment. Apologies for the lack of formatting.

Downstream Log

DS-1DS-2DS-3DS-4DS-5DS-6DS-7DS-8Frequency (Hz)203000000211000000219000000227000000235000000243000000251000000259000000Lock Status(QAM Lock/FEC Sync/MPEG Lock)LockedLockedLockedLockedLockedLockedLockedLockedChannel ID12345678Modulation256QAM256QAM256QAM256QAM256QAM256QAM256QAM256QAMSymbol Rate (Msym/sec)6.9520006.9520006.9520006.9520006.9520006.9520006.9520006.952000Interleave DepthI=12
J=17I=12
J=17I=12
J=17I=12
J=17I=12
J=17I=12
J=17I=12
J=17I=12
J=17

PowerLevel (dBmV)8.65 7.95 6.88 6.90 7.37 6.89 5.86 5.17

RxMER(dB)39.40 38.98 38.26 38.26 39.40 38.98 38.26 38.26

PreRS Errors7642 7192 511 3912 24 14 14 9

PostRS Errors00000000

 Network Log

LogFirst TimeLast TimePriorityError NumberDescription14/03/2017 19:57:05 GMT14/03/2017 19:57:05 GMTError (4)68010400DHCP REBIND WARNING - Field invalid in response14/03/2017 19:56:06 GMT14/03/2017 19:56:06 GMTError (4)68010100DHCP RENEW sent - No response for IPv414/03/2017 19:55:11 GMT14/03/2017 19:55:11 GMTError (4)68010100DHCP RENEW sent - No response for IPv414/03/2017 19:53:20 GMT14/03/2017 19:53:20 GMTError (4)68010100DHCP RENEW sent - No response for IPv414/03/2017 19:49:39 GMT14/03/2017 19:49:39 GMTError (4)68010100DHCP RENEW sent - No response for IPv414/03/2017 19:42:16 GMT14/03/2017 19:42:16 GMTError (4)68010100DHCP RENEW sent - No response for IPv414/03/2017 19:27:30 GMT14/03/2017 19:27:30 GMTError (4)68010100DHCP RENEW sent - No response for IPv414/03/2017 18:57:58 GMT14/03/2017 18:57:58 GMTError (4)68010100DHCP RENEW sent - No response for IPv414/03/2017 17:58:54 GMT14/03/2017 17:58:54 GMTError (4)68010100DHCP RENEW sent - No response for IPv414/03/2017 16:00:47 GMT14/03/2017 16:00:47 GMTError (4)68010100DHCP RENEW sent - No response for IPv414/03/2017 12:04:32 GMT14/03/2017 12:04:32 GMTError (4)68010100DHCP RENEW sent - No response for IPv414/03/2017 04:12:02 GMT14/03/2017 04:12:02 GMTError (4)68010100DHCP RENEW sent - No response for IPv413/03/2017 12:27:01 GMT13/03/2017 12:27:01 GMTError (4)68010100DHCP RENEW sent - No response for IPv408/03/2017 16:58:06 GMT08/03/2017 16:58:06 GMTError (4)68010302DHCP WAN IP - 82.13.74.20808/03/2017 16:57:01 GMT08/03/2017 16:57:01 GMTError (4)68000407TOD establishedTime Not EstablishedTime Not EstablishedNotice (6)84000510Downstream Locked Successfully

Reply
0 Kudos
Forum Team
  • 3.34K
  • 113
  • 270
Registered: ‎04-07-2016
Message 2 of 5 (53 Views)

Re: SHub 2 Power Levels Uneven

Hi vircom,

 

Thanks for posting!

 

I've run diagnostics on your equipment and your power levels are looking fine at the moment. Are you experiencing any issues with your connection?

 

Speak soon Smiley Very Happy

 

Josh


Tech fan? Have you read our Digital life blog yet? Check it out


Reply
0 Kudos
On our wavelength
  • 149
  • 14
  • 27
Registered: ‎22-02-2017
Message 3 of 5 (43 Views)

Re: SHub 2 Power Levels Uneven

[ Edited ]

Hi Josh, thanks for checking my levels.

Over the last few days I have bee getting thousands of pre and post RS errors showing in the Downstream log. I have just reset and the counters and the errors are still occuring at a high rate. I have not posted the log as the errors are increasing minute by minute. The other data are very close to the previous post of Downstream​ log.

What has changed is I am getting regular entries in the Network log The entries vary but today it looks like this


Network Log
First Time Last Time Priority Error Number Description
24/03/2017 03:44:48 GMT 24/03/2017 03:44:48 GMT Error (4) 68010302 DHCP WAN IP - ***********
24/03/2017 03:44:03 GMT 24/03/2017 03:44:03 GMT Error (4) 68000407 TOD established
24/03/2017 03:43:57 GMT 24/03/2017 03:43:57 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
24/03/2017 03:43:55 GMT 24/03/2017 03:43:55 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
24/03/2017 03:43:50 GMT 24/03/2017 03:43:50 GMT Notice (6) 84000510 Downstream Locked Successfully
24/03/2017 03:43:39 GMT 24/03/2017 03:43:39 GMT Error (4) 68000407 TOD established
24/03/2017 03:43:27 GMT 24/03/2017 03:43:27 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
24/03/2017 03:43:25 GMT 24/03/2017 03:43:25 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
24/03/2017 03:43:20 GMT 24/03/2017 03:43:20 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
24/03/2017 03:43:16 GMT 24/03/2017 03:43:16 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
24/03/2017 03:43:12 GMT 24/03/2017 03:43:12 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
24/03/2017 03:43:09 GMT 24/03/2017 03:43:09 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
24/03/2017 03:43:07 GMT 24/03/2017 03:43:07 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
24/03/2017 03:43:07 GMT 24/03/2017 03:43:07 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
24/03/2017 03:43:06 GMT 24/03/2017 03:43:06 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
24/03/2017 03:42:52 GMT 24/03/2017 03:42:52 GMT Notice (6) 84000510 Downstream Locked Successfully
24/03/2017 03:42:52 GMT 24/03/2017 03:42:52 GMT Warning (5) 84020300 MDD message timeout
24/03/2017 03:42:52 GMT 24/03/2017 03:42:52 GMT Warning (5) 84020200 Lost MDD Timeout
24/03/2017 03:42:11 GMT 24/03/2017 03:42:11 GMT Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
24/03/2017 03:42:03 GMT 24/03/2017 03:42:03 GMT Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out


I have checked my connections and there has been no problems with TV picture quality. Can you check whether there is a network fault that is not shown when I check Service Status via My VM or suggest any other reason for these recent problem?

 

 

 

[MOD EDIT: Personal and private information has been removed from this post. Please do not post personal or private information in your public posts. Please review the Forum Guidelines]

Reply
0 Kudos
On our wavelength
  • 149
  • 14
  • 27
Registered: ‎22-02-2017
Message 4 of 5 (30 Views)

Re: SHub 2 Power Levels Uneven

Thanks for deleting the IP I just looked at the log again and realised it was there but you got to it for me first.
Reply
0 Kudos
On our wavelength
  • 149
  • 14
  • 27
Registered: ‎22-02-2017
Message 5 of 5 (18 Views)

Re: SHub 2 Power Levels Uneven

The network problems and errors appear to have settled over the last couple of days so I have cleared the network log and reset the error counts. I also found an old 3dB forward path attenuator and tried fitting this before the SHub. My Downstream levels are now around 2 to 3 dB across all channels, which looks better and gives a bit more headroom.
Reply
0 Kudos