Hello,
I am new to GenieACS and TR-069 in general and am having issues when trying to connect to a BEC 6900 LTE CPE. When trying to summon the device I get the error too many commit iterations in the cwmp log following multiple cpeFaultCode=“9005” cpeFaultString=“Invalid parameter name” messages. I’m not even sure where to start troubleshooting this. I’m running Genie pretty much straight out of the box with no alterations. I’d appreciate any help I can get.
Thanks in advance
You will need to enable the debug log for the device to see which parameter the CPE is complaining about.
Thanks, I appreciate the response. I apologize for taking so long to respond but I’ve done what you’ve suggested. There’s a lot of information and I can see the blocks with the error but not any specific parameter. Here’s a snip of one of those blocks, there’s plenty that are in the debug output structured the same way.
event: outgoing HTTP response
timestamp: 2022-05-12T20:24:57.255Z
remoteAddress: “::ffff:0.0.0.0”
deviceId: 600347-BEC%206900%2DR21-6003474EB0E7
connection: 2022-05-12T20:24:52.018Z
statusCode: 200
headers:
content-length: 566
server: GenieACS/1.2.8+20211027200938
soapserver: GenieACS/1.2.8+20211027200938
content-type: text/xml; charset=“utf-8”
body: >-
event: incoming HTTP request
timestamp: 2022-05-12T20:24:57.289Z
remoteAddress: “::ffff:x.x.x.x”
deviceId: 600347-BEC%206900%2DR21-6003474EB0E7
connection: 2022-05-12T20:24:52.018Z
localPort: 7547
method: POST
url: /
headers:
host: x.x.x.x:7547
cookie: session=d81b572202792151
user-agent: easycwmp-billion
content-type: text/xml; charset=“utf-8”
soapaction: “”
content-length: “769”
body: |
user-agent: easycwmp-billion ?
put a return statement at the start of your provisioning scripts so they won’t do anything. Do a summon at the device page. Do you get an error? If not, problem is with a parameter set at your provisioning scripts.
9xxx series errors are client errors. 9005 means you are trying to set a parameter the CPE doesn’t support setting, or your are setting it to a value that is unsupported. Or you are trying to retrieve parameters that the CPE doesn’t think exist. I’ve seen this with some CPEs where they report they report instances that doesn’t actually exist. For example, the Zyxel’s we have; they report 10 instances under Device.WiFi, but if you try and retrieve the parameters for instances 9 and 10, the CPE returns a 9005 error.
Your SOAP output above looks like it got clobbered by discourse so I’m unable to make any sorts of guesses as to what the parameter might be. In the future, use something like pastebin or three backticks ``` followed by a new line to include debug data with your message. This prevents discourse from mucking with it.
Example:
# REQUEST Mon Mar 01 2021 16:17:52 GMT-0900 (AKST)
{"host":"127.0.0.1:7547","user-agent":"CV2_TR69_CPE_04_00","soapaction":"","content-type":"text/xml","x-forwarded-for":"172.27.242.23","x-forwarded-host":"172.24.254.12:7548","x-forwarded-server":"juneacs-dev.admin.aptalaska.net","content-length":"3221","connection":"Keep-Alive"}
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:cwmp="urn:dslforum-org:cwmp-1-0">
<SOAP-ENV:Header>
<cwmp:ID SOAP-ENV:mustUnderstand="1">897236964</cwmp:ID>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<cwmp:Inform>
<DeviceId>
<Manufacturer>SmartRG</Manufacturer>
<OUI>3c9066</OUI>
<ProductClass>963138_T281_C</ProductClass>
<SerialNumber>SR555AA077-xxxxxxxxxx</SerialNumber>
</DeviceId>
<Event SOAP-ENC:arrayType="cwmp:EventStruct[1]">
<EventStruct>
<EventCode>2 PERIODIC</EventCode>
<CommandKey></CommandKey>
</EventStruct>
</Event>
<MaxEnvelopes>1</MaxEnvelopes>
<CurrentTime>2021-03-01T16:17:52+00:00</CurrentTime>
<RetryCount>0</RetryCount>
<ParameterList SOAP-ENC:arrayType="cwmp:ParameterValueStruct[0008]">
<ParameterValueStruct>
<Name>InternetGatewayDevice.DeviceSummary</Name>
<Value xsi:type="xsd:string">InternetGatewayDevice:1.4[](Baseline:1, EthernetLAN:1, WiFiLAN:1, ADSLWAN:1, EthernetWAN:1, Time:1, IPPing:1, CaptivePortal:1, ATMLoopback:1, DSLDiagnostics:1, QoS:1, DeviceAssociation:1, UDPConnReq:1, X_CLEARACCESS_COM_Cns:1, X_CLEARACCESS_COM:1), X_CISCO_COM_CAH:1, X_SMARTRG_COM_CAF:1, X_SMARTRG_COM_DIAG:1</Value>
</ParameterValueStruct>
<ParameterValueStruct>
<Name>InternetGatewayDevice.DeviceInfo.SpecVersion</Name>
<Value xsi:type="xsd:string">1.0</Value>
</ParameterValueStruct>
<ParameterValueStruct>
<Name>InternetGatewayDevice.DeviceInfo.HardwareVersion</Name>
<Value xsi:type="xsd:string">SR555ac</Value>
</ParameterValueStruct>
<ParameterValueStruct>
<Name>InternetGatewayDevice.DeviceInfo.SoftwareVersion</Name>
<Value xsi:type="xsd:string">2.6.2.5</Value>
</ParameterValueStruct>
<ParameterValueStruct>
<Name>InternetGatewayDevice.DeviceInfo.ProvisioningCode</Name>
<Value xsi:type="xsd:string"></Value>
</ParameterValueStruct>
<ParameterValueStruct>
<Name>InternetGatewayDevice.ManagementServer.ConnectionRequestURL</Name>
<Value xsi:type="xsd:string">http://xxx.xxx.xxx.xxx:30005/</Value>
</ParameterValueStruct>
<ParameterValueStruct>
<Name>InternetGatewayDevice.ManagementServer.ParameterKey</Name>
<Value xsi:type="xsd:string">(null)</Value>
</ParameterValueStruct>
<ParameterValueStruct>
<Name>InternetGatewayDevice.WANDevice.1.WANConnectionDevice.2.WANIPConnection.1.ExternalIPAddress</Name>
<Value xsi:type="xsd:string">xxx.xx.xxx.xxx</Value>
</ParameterValueStruct>
</ParameterList>
</cwmp:Inform>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
# RESPONSE Mon Mar 01 2021 16:17:52 GMT-0900 (AKST)
{"Server":"GenieACS/1.1.3","SOAPServer":"GenieACS/1.1.3","Content-Type":"text/xml; charset=\"utf-8\"","Set-Cookie":"session=633fa2400bdf938c"}
<?xml version="1.0" encoding="UTF-8"?>
<soap-env:Envelope xmlns:soap-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:cwmp="urn:dslforum-org:cwmp-1-0">
<soap-env:Header>
<cwmp:ID soap-env:mustUnderstand="1">897236964</cwmp:ID>
</soap-env:Header>
<soap-env:Body>
<cwmp:InformResponse>
<MaxEnvelopes>1</MaxEnvelopes>
</cwmp:InformResponse>
</soap-env:Body>
</soap-env:Envelope>
Yeah sorry about that. Here’s a better text block for you to see while I try your suggestions.
---
event: outgoing HTTP response
timestamp: 2022-05-12T20:24:52.850Z
remoteAddress: "::ffff:x.x.x.x"
deviceId: 600347-BEC%206900%2DR21-6003474EB0E7
connection: 2022-05-12T20:24:52.018Z
statusCode: 200
headers:
content-length: 566
server: GenieACS/1.2.8+20211027200938
soapserver: GenieACS/1.2.8+20211027200938
content-type: text/xml; charset="utf-8"
body: >-
<?xml version="1.0" encoding="UTF-8"?>
<soap-env:Envelope xmlns:soap-enc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:cwmp="urn:dslforum-org:cwmp-1-2"><soap-env:Header><cwmp:ID
soap-env:mustUnderstand="1">180b9f2162a0007</cwmp:ID></soap-env:Header><soap-env:Body><cwmp:GetParameterNames><ParameterPath></ParameterPath><NextLevel>1</NextLevel></cwmp:GetParameterNames></soap-env:Body></soap-env:Envelope>
---
event: incoming HTTP request
timestamp: 2022-05-12T20:24:52.884Z
remoteAddress: "::ffff:x.x.x.x"
deviceId: 600347-BEC%206900%2DR21-6003474EB0E7
connection: 2022-05-12T20:24:52.018Z
localPort: 7547
method: POST
url: /
headers:
host: x.x.x.x:7547
cookie: session=d81b572202792151
user-agent: easycwmp-billion
content-type: text/xml; charset="utf-8"
soapaction: ""
content-length: "769"
body: |
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<soap_env:Envelope
xmlns:soap_env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:soap_enc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:cwmp="urn:dslforum-org:cwmp-1-2">
<soap_env:Header>
<cwmp:ID soap_env:mustUnderstand="1">180b9f2162a0007</cwmp:ID>
</soap_env:Header>
<soap_env:Body>
<soap_env:Fault>
<faultcode>Client</faultcode>
<faultstring>CWMP fault</faultstring>
<detail>
<cwmp:Fault>
<FaultCode>9005</FaultCode>
<FaultString>Invalid parameter name</FaultString>
</cwmp:Fault>
</detail>
</soap_env:Fault>
</soap_env:Body>
</soap_env:Envelope>
---
If I’m reading this correctly, you are trying to refresh the root of the device? Are you doing this via the API or a provision script?
I’ve tried refreshing the root or just a specific parameter and get the same log output. I’m doing this through the web interface. After adding the return statements to the default provisioning script I now get just a SOCKET HANGUP ERROR in the logs and the web interface just says the device is unreachable. I can see the ping running and it has low latency so I know it can be reached from the server. The debug is short but still included
---
event: outgoing HTTP request
timestamp: 2022-05-31T22:23:41.992Z
remoteAddress: x.x.x.x
deviceId: 600347-BEC%206900%2DR21-6003474EB0E7
connection: null
remotePort: "7547"
method: GET
url: /
headers:
host: x.x.x.x:7547
error: socket hang up
It sounds to me like the CPE isn’t behaving correctly. I’d create lots of detailed logs and loop in BEC. They will likely only respond if you can provide very detailed logs.
This has been resolved. I worked with BEC and they found some issues on their end. They wrote me some new firmware the incorporated the fixes and things seem to be working well.