Rookie

Would some one check out my RF parameters please?

I have been having latency / consistancy issues with wired internetconnection during peak hours of usage. have gathered alot of logs with mtr over a few weeks span. issue been going on for about 5 months, had many techs come out , level 3 rep put something to "engineers" with my data and never got back to me.  figured I would throw these up to make sure that there is NOTHING else that i can do before i go absolute ham ( polite ) on tech support. thank you so much in advance , i am sure you know exactly how frustrating this has been    

 Downstream

 DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
Downstream 113555.00 MHz2.90 dBmV40.95 dB256QAM3298624304934
Downstream 29531.00 MHz2.70 dBmV40.37 dB256QAM230148685210
Downstream 310537.00 MHz3.00 dBmV40.95 dB256QAM229038338000
Downstream 411543.00 MHz3.00 dBmV40.95 dB256QAM231473366600
Downstream 512549.00 MHz3.30 dBmV40.95 dB256QAM232438970200
Downstream 61483.00 MHz3.60 dBmV40.95 dB256QAM231760620510
Downstream 714561.00 MHz2.80 dBmV40.95 dB256QAM233366882210
Downstream 815567.00 MHz3.10 dBmV40.37 dB256QAM229267786100
Downstream 917579.00 MHz2.70 dBmV40.37 dB256QAM240309117900
Downstream 1018585.00 MHz2.50 dBmV40.95 dB256QAM303418161100
Downstream 1119591.00 MHz2.80 dBmV40.95 dB256QAM313999594300
Downstream 1220597.00 MHz3.00 dBmV40.95 dB256QAM307595418300
Downstream 1321603.00 MHz2.40 dBmV40.95 dB256QAM312152299180
Downstream 1422609.00 MHz2.90 dBmV40.95 dB256QAM317706930780
Downstream 1523615.00 MHz2.80 dBmV40.37 dB256QAM317921906480
Downstream 1624621.00 MHz2.40 dBmV40.95 dB256QAM315605834510

 

Upstream

 UCIDFreqPowerChannel TypeSymbol RateModulation
Upstream 1224.20 MHz46.00 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 2437.00 MHz46.50 dBmVDOCSIS2.0 (ATDMA)2560 kSym/s16QAM
Upstream 3330.60 MHz45.50 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 4119.40 MHz45.25 dBmVDOCSIS1.x (TDMA)2560 kSym/s16QAM

 

 

 Interface Parameters
Interface NameProvisionedStateSpeed (Mbps)MAC address
LAN Port 1EnabledUp1000(Full)D4:05:98:31:CD:51
LAN Port 2EnabledDown-----D4:05:98:31:CD:51
LAN Port 3EnabledDown-----D4:05:98:31:CD:51
LAN Port 4EnabledDown-----D4:05:98:31:CD:51
CABLEEnabledUp-----D4:05:98:31:CD:52
MTAPassUp-----D4:05:98:31:CD:53

 

 

I also see people post event logs so...

 

DOCSIS(CM) Events

 

Date TimeEvent IDEvent LevelDescription
8/17/2016 9:26680106006DHCP Renew - lease parameters time server-72.183.77.48;tftp file-?BEWGlxXUBZgxzVIK56i1@CueotZl9tjndi66ztPEodaR7lwiZA_z_ modified;CM-MAC=d4:05:98:31:cd:52;CMTS-MAC=00:17:10:86:76:d4;CM-QOS=1.1;CM-VER=3.0;
8/17/2016 21:13820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:31:cd:52;CMTS-MAC=00:17:10:86:76:d4;CM-QOS=1.1;CM-VER=3.0;
8/20/2016 21:26680106006DHCP Renew - lease parameters tftp file-?BEWGlxXUBZgxzVIK56i1@Cueotbks9yAu53xXNO+VqxeiqIav3F9P modified;CM-MAC=d4:05:98:31:cd:52;CMTS-MAC=00:17:10:86:76:d4;CM-QOS=1.1;CM-VER=3.0;
8/21/2016 0:27820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:31:cd:52;CMTS-MAC=00:17:10:86:76:d4;CM-QOS=1.1;CM-VER=3.0;
8/24/2016 9:26680106006DHCP Renew - lease parameters time server-72.183.77.8;tftp file-?BEWGlxXUBZgxzVIK56i1@CueotYtHi7S6AKsY7KrL9Q3luQlCMvn_ modified;CM-MAC=d4:05:98:31:cd:52;CMTS-MAC=00:17:10:86:76:d4;CM-QOS=1.1;CM-VER=3.0;
8/24/2016 9:53820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:31:cd:52;CMTS-MAC=00:17:10:86:76:d4;CM-QOS=1.1;CM-VER=3.0;
8/27/2016 21:26680106006DHCP Renew - lease parameters tftp file-?BEWGlxXUBZgxzVIK56i1@Cueote8K8MYTuHiDcdsvb637mDqSLtrx modified;CM-MAC=d4:05:98:31:cd:52;CMTS-MAC=00:17:10:86:76:d4;CM-QOS=1.1;CM-VER=3.0;
8/28/2016 2:13820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:31:cd:52;CMTS-MAC=00:17:10:86:76:d4;CM-QOS=1.1;CM-VER=3.0;
8/31/2016 9:26680106006DHCP Renew - lease parameters tftp file-?BEWGlxXUBZgxzVIK56i1@CueotaIoZwcqgjVUg5GAozgwM+DMw3U3 modified;CM-MAC=d4:05:98:31:cd:52;CMTS-MAC=00:17:10:86:76:d4;CM-QOS=1.1;CM-VER=3.0;
8/31/2016 13:16820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:31:cd:52;CMTS-MAC=00:17:10:86:76:d4;CM-QOS=1.1;CM-VER=3.0;
9/3/2016 21:26680106006DHCP Renew - lease parameters time server-72.183.82.37;tftp file-?BEWGlxXUBZgxzVIK56i1@CueotREBdu69B0bjl83rSCDTP79SB3_Z modified;CM-MAC=d4:05:98:31:cd:52;CMTS-MAC=00:17:10:86:76:d4;CM-QOS=1.1;CM-VER=3.0;
9/4/2016 1:28820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:31:cd:52;CMTS-MAC=00:17:10:86:76:d4;CM-QOS=1.1;CM-VER=3.0;
9/7/2016 9:26680106006DHCP Renew - lease parameters time server-72.183.77.8;tftp file-?BEWGlxXUBZgxzVIK56i1@CueotaZ4KyO3MG6CxdADj9rW0elrNjer modified;CM-MAC=d4:05:98:31:cd:52;CMTS-MAC=00:17:10:86:76:d4;CM-QOS=1.1;CM-VER=3.0;
9/7/2016 10:59820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:31:cd:52;CMTS-MAC=00:17:10:86:76:d4;CM-QOS=1.1;CM-VER=3.0;
9/10/2016 21:26680106006DHCP Renew - lease parameters time server-72.183.77.48;tftp file-?BEWGlxXUBZgxzVIK56i1@CueotZwiDvQTW3v3WVKMPCoK6oB85_+6 modified;CM-MAC=d4:05:98:31:cd:52;CMTS-MAC=00:17:10:86:76:d4;CM-QOS=1.1;CM-VER=3.0;
9/11/2016 12:51820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:31:cd:52;CMTS-MAC=00:17:10:86:76:d4;CM-QOS=1.1;CM-VER=3.0;
9/29/2016 21:0924171643086Unit has been restored to factory defaults from a software issued command;CM-MAC=d4:05:98:31:cd:52;CMTS-MAC=00:01:5c:55:12:41;CM-QOS=1.1;CM-VER=3.0;
9/29/2016 21:09840007005RCS Partial Service;CM-MAC=d4:05:98:31:cd:52;CMTS-MAC=00:01:5c:55:12:41;CM-QOS=1.1;CM-VER=3.0;
10/12/2016 16:17680106006DHCP Renew - lease parameters time server-72.183.77.58;tftp file-?BEWGlxzUBZgxzVIK9XGx@CvVxsUVQi6I6kt_RU33fZtpwDqqo+7v_ modified;CM-MAC=d4:05:98:31:cd:52;CMTS-MAC=00:17:10:87:29:a0;CM-QOS=1.1;CM-VER=3.0;
10/12/2016 17:49820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:31:cd:52;CMTS-MAC=00:17:10:87:29:a0;CM-QOS=1.1;CM-VER=3.0;

 

 PacketCable(MTA) Events

 

Date TimeEvent IDDescription
8/13/2016 18:3326MTA PROV: Successful!
8/13/2016 18:333Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
8/13/2016 18:3314Power Supply Telemetry Log - BATTERY MISSING
8/13/2016 19:024000960006New time has been retrieved from ToD server.
8/13/2016 19:1314Power Supply Telemetry Log - BATTERY MISSING
8/13/2016 19:1316MTA TFTP: Successful
8/13/2016 19:1326MTA PROV: Successful!
8/13/2016 19:133Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
8/13/2016 23:4914Power Supply Telemetry Log - BATTERY MISSING
8/13/2016 23:4916MTA TFTP: Successful
8/13/2016 23:4926MTA PROV: Successful!
8/13/2016 23:493Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
8/17/2016 9:264000960006New time has been retrieved from ToD server.
8/24/2016 9:264000960006New time has been retrieved from ToD server.
9/3/2016 21:264000960006New time has been retrieved from ToD server.
9/7/2016 9:264000960006New time has been retrieved from ToD server.
9/10/2016 21:264000960006New time has been retrieved from ToD server.
9/29/2016 21:0816MTA TFTP: Successful
9/29/2016 21:0826MTA PROV: Successful!
9/29/2016 21:083Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
9/29/2016 21:083Voice Line State Change, Line Number = 2, Prev State = OOS, New State = IS
9/29/2016 21:0814Power Supply Telemetry Log - BATTERY MISSING
9/29/2016 21:1216MTA TFTP: Successful
9/29/2016 21:1226MTA PROV: Successful!
9/29/2016 21:123Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
9/29/2016 21:123Voice Line State Change, Line Number = 2, Prev State = OOS, New State = IS
9/29/2016 21:1214Power Supply Telemetry Log - BATTERY MISSING
10/12/2016 15:4716MTA TFTP: Successful
10/12/2016 15:4726MTA PROV: Successful!
10/12/2016 15:473Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
10/12/2016 15:4714Power Supply Telemetry Log - BATTERY MISSING
10/12/2016 16:174000960006New time has been retrieved from ToD server.
7 REPLIES 7
Expert

Re: Would some one check out my RF parameters please?

Austin/Dallas?

figures....

unplug the modem for 5 minutes, power it back up and post the signal page again.

 

Rookie

Re: Would some one check out my RF parameters please?

you are a beast on the forums. cool stuff, thanks for being there .

Downstream

DCID Freq Power SNR Modulation Octets Correcteds Uncorrectables
Downstream 1 13 555.00 MHz 3.70 dBmV 40.95 dB 256QAM 989650 0 0
Downstream 2 3 495.00 MHz 5.10 dBmV 40.95 dB 256QAM 164814 0 0
Downstream 3 4 501.00 MHz 4.40 dBmV 40.37 dB 256QAM 153455 0 0
Downstream 4 5 507.00 MHz 4.10 dBmV 40.95 dB 256QAM 153233 0 0
Downstream 5 6 513.00 MHz 4.00 dBmV 40.95 dB 256QAM 170195 0 0
Downstream 6 7 519.00 MHz 4.00 dBmV 40.95 dB 256QAM 170212 0 0
Downstream 7 8 525.00 MHz 4.00 dBmV 40.95 dB 256QAM 160438 0 0
Downstream 8 9 531.00 MHz 3.80 dBmV 40.37 dB 256QAM 160234 0 0
Downstream 9 10 537.00 MHz 3.90 dBmV 40.95 dB 256QAM 159839 0 0
Downstream 10 11 543.00 MHz 4.00 dBmV 40.95 dB 256QAM 164146 7 0
Downstream 11 12 549.00 MHz 4.20 dBmV 40.95 dB 256QAM 161948 0 0
Downstream 12 1 483.00 MHz 4.60 dBmV 40.95 dB 256QAM 163591 0 0
Downstream 13 14 561.00 MHz 3.60 dBmV 40.95 dB 256QAM 146852 0 0
Downstream 14 15 567.00 MHz 3.90 dBmV 40.95 dB 256QAM 159139 0 0
Downstream 15 16 573.00 MHz 4.10 dBmV 40.37 dB 256QAM 152206 0 0
Downstream 16 24 621.00 MHz 3.60 dBmV 40.95 dB 256QAM 165718 0 0
Reset FEC Counters
Upstream

UCID Freq Power Channel Type Symbol Rate Modulation
Upstream 1 2 24.20 MHz 45.25 dBmV DOCSIS2.0 (ATDMA) 5120 kSym/s 64QAM
Upstream 2 4 37.00 MHz 45.25 dBmV DOCSIS2.0 (ATDMA) 2560 kSym/s 16QAM
Upstream 3 3 30.60 MHz 45.25 dBmV DOCSIS2.0 (ATDMA) 5120 kSym/s 64QAM
Upstream 4 1 19.40 MHz 45.25 dBmV DOCSIS1.x (TDMA) 2560 kSym/s 16QAM
Expert

Re: Would some one check out my RF parameters please?

It looks like there was some sort of intermittent that caused the DS partial service error a few days ago.  Was trying to see if anything is obviously bad ... it's not.

 See if you get high correcteds on a channel or more DS partial service errors, then repost the signal page, see what channels dropped out.

 Could be a highly intermittent ingress issue on a couple cjhannels like 489 mHz.

 

Rookie

Re: Would some one check out my RF parameters please?

Downstream

 DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
Downstream 113555.00 MHz3.20 dBmV40.37 dB256QAM48355744300
Downstream 22489.00 MHz4.50 dBmV40.95 dB256QAM390932148180
Downstream 33495.00 MHz4.70 dBmV40.95 dB256QAM38954124780
Downstream 44501.00 MHz4.00 dBmV40.37 dB256QAM39093790600
Downstream 55507.00 MHz3.70 dBmV40.95 dB256QAM39361027900
Downstream 66513.00 MHz3.50 dBmV40.95 dB256QAM39637412900
Downstream 77519.00 MHz3.40 dBmV40.95 dB256QAM39699599900
Downstream 88525.00 MHz3.50 dBmV40.95 dB256QAM39296505800
Downstream 99531.00 MHz3.20 dBmV40.37 dB256QAM41040111900
Downstream 1010537.00 MHz3.40 dBmV40.95 dB256QAM41184931600
Downstream 1111543.00 MHz3.40 dBmV40.95 dB256QAM41354529100
Downstream 1212549.00 MHz3.70 dBmV40.37 dB256QAM41729098300
Downstream 131483.00 MHz4.20 dBmV40.95 dB256QAM41276138800
Downstream 1414561.00 MHz3.20 dBmV40.37 dB256QAM41877959600
Downstream 1515567.00 MHz3.40 dBmV40.95 dB256QAM42224096100
Downstream 1616573.00 MHz3.70 dBmV40.95 dB256QAM41733460900
Reset FEC Counters

 

10/22/2016 7:00680106006DHCP Renew - lease parameters tftp file-?BEWGlxzUBZgxzVIK9XGx@CvVxsUxIJqiswFDCo24FFU3hvhB+sHou modified;CM-MAC=d4:05:98:31:cd:52;CMTS-MAC=00:17:10:87:29:a0;CM-QOS=1.1;CM-VER=3.0;
10/22/2016 23:48820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:31:cd:52;CMTS-MAC=00:17:10:87:29:a0;CM-QOS=1.1;CM-VER=3.0;
Expert

Re: Would some one check out my RF parameters please?

nothing obviously wrong. Sorry...Woman Frustrated

Rookie

Re: Would some one check out my RF parameters please?

all good, thank you for looking
Highlighted
Sharer

Re: Would some one check out my RF parameters please?

Heheyaha I wish my signal page looked that good!

 

If you continue to get timeouts (T3/T4), that's a problem.

 

If you aren't getting those and you're still having issues, try the modem in bridge mode to rule out the all-in-one router.  Obviously, you'll need another router or will have to live with one device for a while to troubleshoot.