Hi all,
To help others with troubleshooting CPE faults, see below:
On 20/11/15 03:40, Zaid Abdulla wrote in
https://github.com/zaidka/genieacs/issues/120
You'll need to patch the code. Look at the function getParameterNames
in tasks.coffee. You can add a condition there to skip that particular
parameter.
For me, two things that were important when tracking down the CPE fault.
One was to add the following line into config/config.json which helps to
find which exact request generates the 9002 fault response. Normally
they are batched up in lots of 32 requests.
"TASK_PARAMETERS_BATCH_SIZE" : 1,
Restart genieacs, delete the device in the gui, get the device to
connect again, use tcpflow to see the request just before the fault.
Request:
<?xml version="1.0" encoding="UTF-8" ?>
<soap-env:Envelope
xmlns:soap-enc="http://schemas.xmlsoap.org/soap/encoding/";
<http://schemas.xmlsoap.org/soap/encoding/>
xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/";
<http://schemas.xmlsoap.org/soap/envelope/>
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
<http://www.w3.org/2001/XMLSchema>
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
<http://www.w3.org/2001/XMLSchema-instance>
xmlns:cwmp="urn:dslforum-org:cwmp-1-0">
<soap-env:Header>
<cwmp:ID
soap-env:mustUnderstand="1">572abd67dd05c6b2464530e2</cwmp:ID>
</soap-env:Header>
<soap-env:Body>
<cwmp:GetParameterValues>
<ParameterNames soap-enc:arrayType="xsd:string[1]">
<string>InternetGatewayDevice.WANDevice.1.WANConnectionDevice.1.X_0819A6_Network</string>
</ParameterNames>
</cwmp:GetParameterValues>
</soap-env:Body>
</soap-env:Envelope>
Response:
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
<http://schemas.xmlsoap.org/soap/envelope/>
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/";
<http://schemas.xmlsoap.org/soap/encoding/>
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
<http://www.w3.org/2001/XMLSchema>
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
<http://www.w3.org/2001/XMLSchema-instance>
xmlns:cwmp="urn:dslforum-org:cwmp-1-0">
<SOAP-ENV:Header>
<cwmp:ID
SOAP-ENV:mustUnderstand="1">572abd67dd05c6b2464530e2</cwmp:ID>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>Client</faultcode>
<faultstring>CWMP fault</faultstring>
<detail>
<cwmp:Fault>
<FaultCode>9002</FaultCode>
<FaultString>Internal error</FaultString>
</cwmp:Fault>
</detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
The below diff shows how to skip parameterNames with certain strings.
[ genieacs/lib]# diff -u tasks.coffee.orig tasks.coffee
--- tasks.coffee.orig 2016-05-04 17:25:35.222022149 +1000
+++ tasks.coffee 2016-05-06 13:04:20.778349934 +1000
@@ -69,7 +69,8 @@
task.session.parameterNames ?= []
if deviceUpdates?.parameterNames?
for p in deviceUpdates.parameterNames
- if not common.endsWith(p[0], '.')
+ name=p[0]
+ if not common.endsWith(p[0], '.') and not
~name.indexOf('.X_0819A6') and not ~name.indexOf('.X_CMCC')
task.session.parameterNames.push(p[0])
if status & STATUS_COMPLETED
The above was helpful to me, I hope it can help others when they connect
up shiny new devices that have issues.
Report your findings back to the vendor to fix, these workarounds are
just to help you understand where the problem is.
Oh yeah, and don't do this on your production servers, set up a dev
server and point a single CPE to it.
Cheers, Stuart
On 02/12/15 07:20, Agustín Bertamoni wrote:
In "H" versión web interface has access to event log viewer, it's
depends of the user, try with admin user in web.
BR
STECHS - Ing. Agustin Bertamoni
Móvil: (+54911) 62183226
Skype: abertamoni-stechs
Av. Boyacá 372 Piso 4º Oficina 401 (C1406BHF)
Buenos Aires, Argentina
On Tue, Dec 1, 2015 at 4:22 PM, Ivan Revyakin <i...@revyakin.net
<mailto:i...@revyakin.net>> wrote:
Hello Agustin,
Yes, HG8245H works fine, but HG8245 is not HG8245H, it's another
generation of this ONT.
I guess you right -- this is device related issue. The Fault Code
rises all time.
>> Device internal log has more information of this issue?
Could you help me how it possible to do? Which CLI commands should
be used?
Thanks
2015-12-01 19:56 GMT+03:00 Agustín Bertamoni
<abertam...@stechs.com.ar>:
Ivan
Seems to be device related issue, we are testing GenieACS with
HG8245H and works ok.
Few questions: -always fails in GetParameterValues? with the
sames attributes?, Device internal log has more information of
this issue? (via web interface can access to tr69 logs)
I hope I've helped
BR
STECHS - Ing. Agustin Bertamoni
Móvil: (+54911) 62183226
Skype: abertamoni-stechs
Av. Boyacá 372 Piso 4º Oficina 401 (C1406BHF)
Buenos Aires, Argentina
On Tue, Dec 1, 2015 at 9:00 AM, Ivan Revyakin
<i...@revyakin.net> wrote:
Hello.
I have two devices:
* Huawei HG8245*H*
* Huawei HG8245
HG8245*H* works good with GenieACS, but HG8245 does not.
HG8245 returns 9002 Code (Fault Code) in the one of replays.
Capture files (*.pcap) for these two devices are here:
https://yadi.sk/d/tfrCoLIakschm
* In "HG8245_fault.pcap" file Fault Code can be found in
packet #339.
* "HG8245H_Ok.pcap" file is good with no errors.
Can anyone help me why HG8245 returns Fault?
The version of HG8245 is V1R006C01S201
The version of HG8245*H* is V3R013C10S108
The version of GenieACS is 1.0 (git clone
https://github.com/zaidka/genieacs.git --branch v1.0)
_______________________________________________
Users mailing list
Users@lists.genieacs.com
http://lists.genieacs.com/mailman/listinfo/users
