Skip to main content
Question

xFinity configuration contains invalid TLV 4


I am trying to get new xFinity service using a new DOCSIS 3.1 Arris G36 gateway.  The activation process with the xFinity app stalls and eventually times out at the ‘testing connections’. In the modem WAN status, all phases prior to ‘Registration’ are marked ‘Complete’ with Registration usually marked ‘Not Started’.  Of particular note, the phase immediately prior to registration, ‘Configuration’ is marked ‘Complete’.

In the Event log, I see the following (actual MAC addresses redacted):

    Config File Rejected due to invalid or Unexpected TLV 4; CM-MAC=*; CMTS-MAC=*; CM-QOS=1.1; CM-VER=3.1

A cursory look for ‘TLV 4’ information suggests this is the part of the configuration where the service provider (xFinity) declares the service level for the connection, in my own words ‘Speeds and quality of service’.   (Editorial note: I don’t consider the Configuration phase ‘Complete’ if the content is being rejected)

Anyone hazard a guess what would be in the configuration, TLV 4 specifically, that Arris G36 doesn’t recognize?  I’ve seen elsewhere that CM-QOS and CM-VER are standardized parts of all rejection error messages and are not highlighting the specific content problem. I signed up for 500 MBPs service. If the TLV information is encoded as enumerations, one would think such a speed would have a valid encoding known to Arris.

An alternate theory is that xFinity has the capability to send different configurations depending on the customer device, and the new off-the-shelf G36 is being sent configuration for their lease/loaner devices.  The fact that configuration contains speed information, which varies by customer subscription, suggests they have the ability to respond to TFTP requests with different configuration files by customer connection.

Its difficult to imagine xFinity claiming to support this device yet sending it configuration it cannot understand unless there is yet another Arris recent firmware update they applied in their test environment but aren’t pushing out to customers.  Perish the thought: they made a change to the configuration file(s) and never tested it with all supported devices.

None of this rang any faint bells with two different ‘xFinity Advanced Tech Support’ agents, who kept wanting me to change nonsensical things like WiFi SSIDs and the administrative password with endless power cycling wastes of time.  I don’t think they have any idea what DOCSIS is or that a configuration file is downloaded during modem power-on. I’m not convinced the second agent knows the difference between the LAN and WAN sides.   Hopefully the tech that comes to the house knows the phone number of someone in the xFinity back office that fixes these configuration files (or has a newer Arris firmware download).

3 replies

  • Author
  • 8 replies
  • August 6, 2025

Can no one at Commscope weigh in on any known vulnerabilities in the firmware to TLV 4 content from xFinity?  Is there any way to turn on additional diagnostic tracing to dump the CM config file or at least isolate the particular TLV 4 sub-value triggering the rejection?   Hard to believe I’m the first or only person bumping into this incompatibility.


  • Author
  • 8 replies
  • August 6, 2025

Update:  Never Mind.  Comedy of errors.

The xFinity coax wasn’t even connected at the pedestal despite xFinity literature distributed by the apartment office suggesting activation was going to be as easy as using the app to associate the line, account, and CM-MAC address. The [good] signal I was connecting to was from Service Electric, and of course I have no account with them.  None of the three coax outlets here have any sort of labelling.

Almost a incompetent as the old ‘is the device plugged in?’, I guess the potential is growing for a need to ask: ‘is the device connected to a port for *your* service provider?’ and then be prepared to answer the response “how would I know?”.


Forum|alt.badge.img+42

Make the gateway displays a solid blue LED light, indicating that it is successfully connected to the internet via the service provider.

Once the gateway is activated, log in to its web interface. Navigate to: Gateway > Connection > WAN

  1. Look for the WAN IP Address (IPv4). 

  2. If a public IP address is displayed, it confirms that the gateway has been successfully activated by the internet service provider. 

  3. If no IP address is shown, the gateway has not been activated, and further troubleshooting may be required.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings