Cable Forum - View Single Post

SirThomas · 24-05-2021, 02:50

Morning Chaps!
Just wondering if anyone else had seen this sort of behaviour before...

A little background - The heavy utilisation on the graph seemed to start around the time I started a VM trial a few months back (pods). That spike seems to crop up almost every night, and doesn't tally with any of my home backup tasks etc. Perhaps a diagnostic upload dump, I thought at the time...

The last few nights I've seen drops and oddities. I had drops every night (just after midnight) a couple of months back, but VM insisted it was because of my poor levels - They were bad, but weren't causing the drops as far as I could see.

Hub3 is showing a red LED (not pink) - I'm in modem mode, but no idea what that means, VM don't seem to know either!

Downstream is now from 0>-2 dBmV, Upstream from 42>44.

The T3/T4's aren't great, but what the devil is an ATOM restart?
When the connection dies, it'll sit for at least 10mins before it (might) come back with packet loss, or by then I've normally power-cycled. No LED status change or ping to 100.1 at that point.

Tom
944fc9a739f6aa2cf7e0ec0b933ed5384d8cb611.png

Spoiler:

24-05-2021, 02:50	#1
SirThomas cf.addict Join Date: May 2010 Location: PO9 - Havant Services: Vodafone 80x20 Backup, MixTV & V6, Vivid 350, Hub3 & RT-AC87u Posts: 126	Dropouts and logging oddities... Morning Chaps! Just wondering if anyone else had seen this sort of behaviour before... A little background - The heavy utilisation on the graph seemed to start around the time I started a VM trial a few months back (pods). That spike seems to crop up almost every night, and doesn't tally with any of my home backup tasks etc. Perhaps a diagnostic upload dump, I thought at the time... The last few nights I've seen drops and oddities. I had drops every night (just after midnight) a couple of months back, but VM insisted it was because of my poor levels - They were bad, but weren't causing the drops as far as I could see. Hub3 is showing a red LED (not pink) - I'm in modem mode, but no idea what that means, VM don't seem to know either! Downstream is now from 0>-2 dBmV, Upstream from 42>44. The T3/T4's aren't great, but what the devil is an ATOM restart? When the connection dies, it'll sit for at least 10mins before it (might) come back with packet loss, or by then I've normally power-cycled. No LED status change or ping to 100.1 at that point. *Tom* 944fc9a739f6aa2cf7e0ec0b933ed5384d8cb611.png Spoiler: Most Recent Logs: Time Priority Description 23/05/2021 23:17 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out 23/05/2021 23:16 notice NOTICE ATOM is restarted as part of Self Healing Mechanism 23/05/2021 23:08 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out 23/05/2021 23:06 Warning! Lost MDD Timeout; 23/05/2021 23:06 critical SYNC Timing Synchronization failure - Loss of Sync; 23/05/2021 23:06 Warning! RCS Partial Service; 23/05/2021 23:06 critical SYNC Timing Synchronization failure - Loss of Sync; 23/05/2021 02:30 critical No Ranging Response received - T3 time-out; 23/05/2021 02:29 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; 23/05/2021 02:23 Warning! Lost MDD Timeout; 23/05/2021 02:22 critical SYNC Timing Synchronization failure - Loss of Sync; 23/05/2021 02:22 Warning! RCS Partial Service; 23/05/2021 02:22 critical SYNC Timing Synchronization failure - Loss of Sync; 22/05/2021 15:17 critical No Ranging Response received - T3 time-out; 21/05/2021 22:56 Error DHCP RENEW WARNING - Field invalid in response v4 option; 21/05/2021 07:36 critical No Ranging Response received - T3 time-out; 20/05/2021 07:20 Warning! Lost MDD Timeout;