Expert

Re: Upstream light blinking on Technicolor TC4310

This is a TWC leased modem?

And 6183's are obsolete...

Lead Moderator

Re: Upstream light blinking on Technicolor TC4310

I can clearly see your levels are off. Please contact us directly to schedule a technician.

 

Please include your account number, your availability for a technician and a good call ahead number.

Private Message

 


Regards,
Julia R.
TWC-Social Media Customer Care
Moderator - TWC Community Forums

Participant

Re: Upstream light blinking on Technicolor TC4310

Yes it's leased. However I recall the SB6183 (personally owned, and returned due to no IPv6) had the same problem. I am following up with the support person who just replied below.

Participant

Re: Upstream light blinking on Technicolor TC4310

Something just changed. Hopefully it will stay like this, otherwise TWC has to come out.

 

Status

Connection  :  This page displays information on the status of the cable modem's HFC and IP network connectivity.

Startup Procedure
Procedure    Status    Comment
Acquire Downstream Channel         Locked
Connectivity State    OK    Operational
Boot State    OK    Operational
Configuration File    OK    
Security    Enabled    BPI+

Downstream Channel
Channel    Lock Status    Modulation    Channel ID    Symbol Rate    Frequency    Power    SNR
1    Locked    QAM256    6    5360537    675000000 Hz    8.9 dBmV    41.4 dB
2    Locked    QAM256    16    5360537    615000000 Hz    9.5 dBmV    43.3 dB
3    Locked    QAM256    15    5360537    621000000 Hz    9.6 dBmV    43.3 dB
4    Locked    QAM256    14    5360537    627000000 Hz    9.4 dBmV    43.1 dB
5    Locked    QAM256    13    5360537    633000000 Hz    9.6 dBmV    43.3 dB
6    Locked    QAM256    12    5360537    639000000 Hz    9.5 dBmV    43.0 dB
7    Locked    QAM256    11    5360537    645000000 Hz    9.4 dBmV    43.1 dB
8    Locked    QAM256    10    5360537    651000000 Hz    9.1 dBmV    42.8 dB
9    Locked    QAM256    9    5360537    657000000 Hz    8.9 dBmV    42.8 dB
10    Locked    QAM256    8    5360537    663000000 Hz    8.8 dBmV    42.6 dB
11    Locked    QAM256    7    5360537    669000000 Hz    8.6 dBmV    42.4 dB
12    Locked    QAM256    5    5360537    681000000 Hz    8.9 dBmV    42.6 dB
13    Locked    QAM256    4    5360537    687000000 Hz    8.9 dBmV    42.5 dB
14    Locked    QAM256    3    5360537    693000000 Hz    8.6 dBmV    42.3 dB
15    Locked    QAM256    2    5360537    699000000 Hz    8.4 dBmV    42.2 dB
16    Locked    QAM256    1    5360537    705000000 Hz    8.6 dBmV    42.3 dB

Upstream Channel
Channel    Lock Status    Modulation    Channel ID    Symbol Rate    Frequency    Power
1    Locked    QAM64    43    5120 Ksym/sec    30600000 Hz    46.3 dBmV
2    Locked    QAM16    41    2560 Ksym/sec    18500000 Hz    45.0 dBmV
3    Locked    QAM64    42    5120 Ksym/sec    23300000 Hz    45.8 dBmV
4    Locked    QAM16    44    2560 Ksym/sec    37000000 Hz    47.3 dBmV

CM IP Address    Duration    Expires
fe80:********5dff:fec1:43f7/64    D: 24896 H: 15 M: 43 S: 56    Thu Mar 31 13:14:18 2016


Current System Time: Thu Mar 31 13:14:18 2016

Expert

Re: Upstream light blinking on Technicolor TC4310

copy and paste the error log . I need to see if there was any sort of dropout when this changed. if there was none there is an intermittent.

if there was a minute +, twc may have been changing out an amplifier module.

 there have to be TLV lines in the log, if there's several, TWC was replacing then readjusting the upstream gain.

 if you are still seeing upstream changes and TLV lines, and it's after dark, I doubt TWC is still working out on the street and you're going to need to call TWC back

 

 

Back to the distro box... How many suites in your building and is there a single large 5/8- 1" line coming into it?

 

did you see if he attached your line to a 2,3 or 4 way hanging splitter? Or did it go to a tapoff on the hardline?

 

 

 

 

Participant

Re: Upstream light blinking on Technicolor TC4310

This problem had existed for a week or more. Today after posting here and contacting support, I remoted in and refreshed the modem status page. At the time I had two channels up, but power had dropped from the 50s to the 40s. That looked interesting, so I triggered a power cycle. When the modem came back up, I had four channels and powers in the mid-40s. It has been stable for a couple hours since then. Power is not bouncing around and channels have not gone away. I did one more power cycle after that and all four channels came up.

 

This is an old GTE Americast installation, with a square metal box. Not sure how many suites each of those boxes serve. I was not standing over the tech when he did the outside install. I saw him remove the cover but did not closely observe. I recall a fat cable coming into the box and some splitters.

 

If it goes back to losing channels and high power, I will arrange to be home next week for a service call.

 

    Connection
    Password
    Event Log
    Initial Scan

Status

SNMP Event Log  :  This page displays the contents of the SNMP event log.

 Time      Priority      Description
 Thu Mar 31 14:12:48 2016       Error (4)      Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=e0:88:...
 Thu Mar 31 14:12:48 2016       Error (4)      Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=e0:88:...
 Thu Mar 31 22:12:34 2016       Notice (6)      Overriding MDD IP initialization parameters; IP provisioning ...
 Thu Mar 31 22:12:32 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 22:12:25 2016       Error (4)      Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=e0:88:...
 Thu Mar 31 22:12:25 2016       Error (4)      Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=e0:88:...
 Time Not Established      Warning (5)      DHCP WARNING - Non-critical field invalid in response ;CM-MAC...
 Time Not Established      Notice (6)      Honoring MDD; IP provisioning mode = IPv4
 Thu Mar 31 20:42:06 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 10:59:54 2016       Critical (3)      Received Response to Broadcast Maintenance Request, But no Un...
 Thu Mar 31 18:58:06 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 10:51:11 2016       Critical (3)      Started Unicast Maintenance Ranging - No Response received - ...
 Thu Mar 31 18:29:29 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 16:33:09 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 08:32:53 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 16:32:29 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 08:32:14 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 16:31:51 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 08:31:41 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 16:31:16 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 08:31:02 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 16:30:36 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 08:30:23 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 16:29:56 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 08:29:45 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 08:29:39 2016       Critical (3)      SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
 Thu Mar 31 16:29:05 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 08:28:50 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 08:28:44 2016       Critical (3)      SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
 Thu Mar 31 16:28:00 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 08:27:47 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 08:27:41 2016       Critical (3)      SYNC Timing Synchronization failure - Failed to acquire QAM/Q...

Expert

Re: Upstream light blinking on Technicolor TC4310

Looks like they repaired a bad line amp.

 Keep an eye on this

 

Participant

Re: Upstream light blinking on Technicolor TC4310

It was fine yesterday, back to high power and two channels today. There is an intermittent fault somewhere.

Expert

Re: Upstream light blinking on Technicolor TC4310

paste/ printout both the current sig level and error log page and get twc out... This is an intermittent issue that they need to fix.  Woman Mad

 This cannot be remotely fixed it needs a tech out

The call center is pretty much useless on intermittent issues and will try to cancell this

Get your call transferred to tier 3 and tell them the level s that are changing and the channel# upstream seem to sometimes be 4 @ the good +45 dBmv but usually around 2 @ 51-52 dBmv and then 1 @ +57 dBmv

 

 whatever is bad has at least 3 steps

 

 

Participant

Re: Upstream light blinking on Technicolor TC4310

It is back to the two channels and low fifties. I replied to the private message from support.

 

Upstream Channel (Partial Service)
Channel    Lock Status    Modulation    Channel ID    Symbol Rate    Frequency    Power
1    Locked    QAM64    43    5120 Ksym/sec    30600000 Hz    51.0 dBmV
2    Locked    QAM16    41    2560 Ksym/sec    18500000 Hz    51.5 dBmV [DOWN]
3    Locked    QAM64    42    5120 Ksym/sec    23300000 Hz    51.0 dBmV [DOWN]
4    Locked    QAM16    44    2560 Ksym/sec    37000000 Hz    52.2 dBmV

 

Status

SNMP Event Log  :  This page displays the contents of the SNMP event log.

 Time      Priority      Description
 Fri Apr 01 11:13:16 2016       Critical (3)      Received Response to Broadcast Maintenance Request, But no Un...
 Fri Apr 01 08:39:31 2016       Error (4)      Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=e0:88:...
 Fri Apr 01 08:39:31 2016       Error (4)      Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=e0:88:...
 Fri Apr 01 16:39:23 2016       Notice (6)      Overriding MDD IP initialization parameters; IP provisioning ...
 Fri Apr 01 16:39:21 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Fri Apr 01 16:39:14 2016       Error (4)      Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=e0:88:...
 Fri Apr 01 16:39:14 2016       Error (4)      Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=e0:88:...
 Time Not Established      Warning (5)      DHCP WARNING - Non-critical field invalid in response ;CM-MAC...
 Time Not Established      Notice (6)      Honoring MDD; IP provisioning mode = IPv4
 Fri Apr 01 07:14:44 2016       Critical (3)      16 consecutive T3 timeouts while trying to range on upstream ...
 Fri Apr 01 07:14:44 2016       Critical (3)      Unicast Maintenance Ranging attempted - No response - Retries...
 Fri Apr 01 07:14:44 2016       Critical (3)      Started Unicast Maintenance Ranging - No Response received - ...
 Fri Apr 01 07:54:03 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 22:12:32 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 20:42:06 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 10:59:54 2016       Critical (3)      Received Response to Broadcast Maintenance Request, But no Un...
 Thu Mar 31 18:58:06 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 10:51:11 2016       Critical (3)      Started Unicast Maintenance Ranging - No Response received - ...
 Thu Mar 31 18:29:29 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 16:33:09 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 08:32:53 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 16:32:29 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 08:32:14 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 16:31:51 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 08:31:41 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 16:31:16 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 08:31:02 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 16:30:36 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 08:30:23 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 16:29:56 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 08:29:45 2016       Critical (3)      No Ranging Response received - T3 time-out;CM-MAC=e0:88:5d:c1...
 Thu Mar 31 08:29:39 2016       Critical (3)      SYNC Timing Synchronization failure - Failed to acquire QAM/Q...