Community Forums

Lose connection multiple times a day

Reply

Lose connection multiple times a day

SOLVED
Go to solution
Highlighted
tdouglas00
tdouglas00
Rookie
‎10-23-2017 09:48 AM
‎10-23-2017 09:48 AM

Lose connection multiple times a day

Anyone mind helping me with my crazy connection?

 Hardware Information
 
System:ARRIS DOCSIS 3.0 / PacketCable 2.0 Touchstone Residential Gateway
HW_REV: 6
VENDOR: Arris Interactive, L.L.C.
BOOTR: 2.2.0.27
SW_REV: 9.1.103J6.SIP.PC20.TW
MODEL: TG1672G
Serial Number:F6FBPM7EV602195
Battery Charger FW Rev:03.30
Options: 
 Firmware Build and Revisions
Firmware Name:TS0901103J6_033116_16XX.GW_PC20_TW
Firmware Build Time:Thu Mar 31 06:34:08 EDT 2016
eSAFE 0 FW Revision:TS0901103J6_033116_ARRIS_GW

 

DOCSIS(CM) Events

 

Date TimeEvent IDEvent LevelDescription
10/23/2017 4:06820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:f9:0a:e2;CMTS-MAC=00:01:5c:7c:82:5e;CM-QOS=1.1;CM-VER=3.0;
10/23/2017 4:06820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:05:98:f9:0a:e2;CMTS-MAC=00:01:5c:7c:82:5e;CM-QOS=1.1;CM-VER=3.0;
10/23/2017 4:07820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:f9:0a:e2;CMTS-MAC=00:01:5c:7c:82:5e;CM-QOS=1.1;CM-VER=3.0;
10/23/2017 4:08820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:05:98:f9:0a:e2;CMTS-MAC=00:01:5c:7c:82:5e;CM-QOS=1.1;CM-VER=3.0;
10/23/2017 4:08820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:f9:0a:e2;CMTS-MAC=00:01:5c:7c:82:5e;CM-QOS=1.1;CM-VER=3.0;
10/23/2017 10:26820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:05:98:f9:0a:e2;CMTS-MAC=00:01:5c:7c:82:5e;CM-QOS=1.1;CM-VER=3.0;
10/23/2017 10:28820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:f9:0a:e2;CMTS-MAC=00:01:5c:7c:82:5e;CM-QOS=1.1;CM-VER=3.0;
10/23/2017 10:28820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:05:98:f9:0a:e2;CMTS-MAC=00:01:5c:7c:82:5e;CM-QOS=1.1;CM-VER=3.0;
10/23/2017 10:30820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:f9:0a:e2;CMTS-MAC=00:01:5c:7c:82:5e;CM-QOS=1.1;CM-VER=3.0;
10/23/2017 10:30820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:05:98:f9:0a:e2;CMTS-MAC=00:01:5c:7c:82:5e;CM-QOS=1.1;CM-VER=3.0;
10/23/2017 10:31820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:f9:0a:e2;CMTS-MAC=00:01:5c:7c:82:5e;CM-QOS=1.1;CM-VER=3.0;
10/23/2017 10:31820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:05:98:f9:0a:e2;CMTS-MAC=00:01:5c:7c:82:5e;CM-QOS=1.1;CM-VER=3.0;
10/23/2017 10:32820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:f9:0a:e2;CMTS-MAC=00:01:5c:7c:82:5e;CM-QOS=1.1;CM-VER=3.0;
10/23/2017 10:33820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:05:98:f9:0a:e2;CMTS-MAC=00:01:5c:7c:82:5e;CM-QOS=1.1;CM-VER=3.0;
10/23/2017 10:33820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:f9:0a:e2;CMTS-MAC=00:01:5c:7c:82:5e;CM-QOS=1.1;CM-VER=3.0;
10/23/2017 10:34820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:05:98:f9:0a:e2;CMTS-MAC=00:01:5c:7c:82:5e;CM-QOS=1.1;CM-VER=3.0;
10/23/2017 10:34820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:f9:0a:e2;CMTS-MAC=00:01:5c:7c:82:5e;CM-QOS=1.1;CM-VER=3.0;
10/23/2017 10:36850102005TCS Partial Service;CM-MAC=d4:05:98:f9:0a:e2;CMTS-MAC=00:01:5c:7c:82:5e;CM-QOS=1.1;CM-VER=3.0;
10/23/2017 10:36850103005Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;CM-MAC=d4:05:98:f9:0a:e2;CMTS-MAC=00:01:5c:7c:82:5e;CM-QOS=1.1;CM-VER=3.0;
10/23/2017 10:37820004003Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:05:98:f9:0a:e2;CMTS-MAC=00:01:5c:7c:82:5e;CM-QOS=1.1;CM-VER=3.0;

 

 PacketCable(MTA) Events

 

Date TimeEvent IDDescription
10/17/2017 14:0116MTA TFTP: Successful
10/17/2017 14:0126MTA PROV: Successful!
10/17/2017 14:013Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
10/17/2017 14:323Voice Line State Change, Line Number = 1, Prev State = IS, New State = OOS
10/17/2017 14:3314Power Supply Telemetry Log - BATTERY MISSING
10/17/2017 14:3416MTA TFTP: Successful
10/17/2017 14:3426MTA PROV: Successful!
10/17/2017 14:343Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
10/18/2017 14:343Voice Line State Change, Line Number = 1, Prev State = IS, New State = OOS
10/18/2017 15:5214Power Supply Telemetry Log - BATTERY MISSING
10/18/2017 15:5216MTA TFTP: Successful
10/18/2017 15:5226MTA PROV: Successful!
10/18/2017 15:523Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
10/21/2017 20:4214Power Supply Telemetry Log - BATTERY MISSING
10/21/2017 20:4216MTA TFTP: Successful
10/21/2017 20:4226MTA PROV: Successful!
10/21/2017 20:423Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
10/23/2017 0:593Voice Line State Change, Line Number = 1, Prev State = IS, New State = OOS
10/23/2017 1:1216MTA TFTP: Successful
10/23/2017 1:1226MTA PROV: Successful!
10/23/2017 1:123Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
10/23/2017 1:1214Power Supply Telemetry Log - BATTERY MISSING
10/23/2017 1:303Voice Line State Change, Line Number = 1, Prev State = IS, New State = OOS
10/23/2017 4:0914Power Supply Telemetry Log - BATTERY MISSING
10/23/2017 4:0916MTA TFTP: Successful
10/23/2017 4:0926MTA PROV: Successful!
10/23/2017 4:093Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
10/23/2017 10:263Voice Line State Change, Line Number = 1, Prev State = IS, New State = OOS
10/23/2017 10:3616MTA TFTP: Successful
10/23/2017 10:3626MTA PROV: Successful!
10/23/2017 10:363Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
10/23/2017 10:3614Power Supply Telemetry Log - BATTERY MISSING
RF Parameters

Downstream

 DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
Downstream 115753.00 MHz-6.90 dBmV38.61 dB256QAM2823217300
Downstream 21669.00 MHz-7.10 dBmV38.61 dB256QAM2227623000
Downstream 32675.00 MHz-7.10 dBmV38.98 dB256QAM2256451200
Downstream 43681.00 MHz-6.70 dBmV38.98 dB256QAM2322686300
Downstream 54687.00 MHz-7.10 dBmV38.61 dB256QAM2773397500
Downstream 65693.00 MHz-7.20 dBmV38.61 dB256QAM2125024200
Downstream 76699.00 MHz-7.20 dBmV38.98 dB256QAM2059200800
Downstream 87705.00 MHz-6.80 dBmV38.98 dB256QAM2359437100
Downstream 98711.00 MHz-6.60 dBmV38.98 dB256QAM2013153200
Downstream 109717.00 MHz-6.70 dBmV38.98 dB256QAM2613986400
Downstream 1110723.00 MHz-6.90 dBmV40.37 dB256QAM2092548600
Downstream 1211729.00 MHz-7.10 dBmV38.98 dB256QAM2804475600
Downstream 1312735.00 MHz-7.00 dBmV38.61 dB256QAM2961519700
Downstream 1413741.00 MHz-6.90 dBmV38.98 dB256QAM2918761800
Downstream 1514747.00 MHz-6.80 dBmV38.61 dB256QAM2438855500
Downstream 1616759.00 MHz-7.10 dBmV38.98 dB256QAM2657723400
Reset FEC Counters

Upstream

 UCIDFreqPowerChannel TypeSymbol RateModulation
Upstream 1224.20 MHz51.00 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 2437.00 MHz----------------
Upstream 3330.60 MHz----------------
Upstream 4119.40 MHz52.00 dBmVDOCSIS1.x (TDMA)2560 kSym/s16QAM

 

 Status
System Uptime:1 d: 14 h: 08 m
Computers Detected:staticCPE(2), dynamicCPE(2)
CM Status:Telephony-Reg Complete
Time and Date:Mon 2017-10-23 10:47:22

 

 Interface Parameters
Interface NameProvisionedStateSpeed (Mbps)MAC address
LAN Port 1EnabledUp1000(Full)D4:05:98:F9:0A:E1
LAN Port 2EnabledDown-----D4:05:98:F9:0A:E1
LAN Port 3EnabledDown-----D4:05:98:F9:0A:E1
LAN Port 4EnabledDown-----D4:05:98:F9:0A:E1
CABLEEnabledUp-----D4:05:98:F9:0A:E2
MTAPassUp-----D4:05:98:F9:0A:E3

 

Hopefully im posting the right information. There is no cable splitter but i do remember having issues with the "drop" outside about a year ago.

0 Enjoys
3 REPLIES 3
MsRaye
Expert
‎10-23-2017 10:37 AM
‎10-23-2017 10:37 AM

Re: Lose connection multiple times a day

You have a splitter in line and it has open ports. It needs to be removed... Looks like a 4 way per the levels... 

Trace line from the outside grounding block to the modem.

Or call TWC out...

 

0 Enjoys
tdouglas00
tdouglas00
Rookie
‎10-23-2017 10:58 AM
‎10-23-2017 10:58 AM

Re: Lose connection multiple times a day

found it! It seems my connection is a bit more stable and i am actually achieving download ordered download speeds. Ill keep track of the event log/connection for the next 24 hours.. will see what happens. thank you!

MsRaye
Expert
‎10-23-2017 11:08 AM
‎10-23-2017 11:08 AM

Re: Lose connection multiple times a day

US must have 4 channels and be lower than +51 dBmv to work and below +49 dBmv to be stable.

 DS should be in the -5 to + 8 dBmv range for best stability.  Open splitter ports are a MAJOR issue as they trash Qam 256 with very minute bits of noise and ingress. It's the major issue in most all node congestion/ slow speeds.... Not only the affected customer but everyone else on that coaxial node....

 

0 Enjoys