Upgrade router firmware give me Stale

hi

i have CPE try to push new firmware to it , but it give me “stale” and not applied

after 3 times i see the ACS push it over fs log but still see "stale "

how i can fix this and get success request if the CPE received the info

same issue if i need to reset the CPE

summon button work normally

What data is in the log on the CPE? That will usually give you a good indication of what the underlying issue is.

Hi Akcoder

it give me like this

tr69c:error:73.440:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:73.477:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:73.543:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:73.572:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:73.635:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:73.663:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:73.731:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:73.795:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:73.855:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:73.884:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:73.908:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:74.014:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:74.041:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:79.087:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:79.158:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:79.221:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:79.284:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:79.307:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:79.342:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:79.374:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:79.447:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:79.495:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:79.555:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:79.616:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:79.677:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:79.744:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:79.804:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:79.941:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:80.005:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:200.137:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:200.173:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:200.235:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:200.264:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:200.329:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:200.353:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:200.420:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:200.523:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:200.586:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:200.613:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:200.636:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:200.734:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:200.760:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:200.824:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:200.890:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:200.951:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:201.015:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:201.040:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:201.063:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:201.089:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:201.142:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:201.202:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:201.264:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:201.326:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:201.386:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:201.446:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:201.690:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:201.817:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:201.880:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:384.747:retrySessionConnection:210:ACS connect failed, retryCount = 1, backOffTime = 5000ms
tr69c:error:384.987:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:385.028:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:385.089:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:385.113:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:385.173:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:385.199:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:385.261:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:385.322:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:385.388:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:385.411:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:385.433:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:385.527:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:385.550:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:385.614:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:385.678:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:385.741:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:385.805:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:385.828:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:385.852:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:385.877:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:385.945:testBoolean:761:unexpected string ==>1<==, returning 1
rmmod: can’t unload ‘bcm_enet’: Resource temporarily unavailable

hi

any update to my problem , also i have same issue when summon the device , it give me no contact with this device

note if i retry more time to push the firmware its go after 3 -4 time of pushing and i do ip table to forward 7547 cwmp traffic to port 80 because the tr069 url in my CPE with port 80

These lines in the log are normal for the broadcom tr69 client. I would suggest looking in the cwmp and fs log files, and setting the logging level to debug on the CPE and trying again.

tr69c:error:385.852:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:385.877:testBoolean:761:unexpected string ==>1<==, returning 1
tr69c:error:385.945:testBoolean:761:unexpected string ==>1<==, returning 1

Hi akcoder

cwmp log :

2019-12-02T09:30:40.020Z [INFO] 85.114.108.132 000ef4-KW5262BC15A-000ef4c40c91: Inform; cpeRequestId=“1804289383” informEvent=“6 CONNECTION REQUEST” informRetryCount=0
2019-12-02T09:30:40.116Z [INFO] 85.114.108.132 000ef4-KW5262BC15A-000ef4c40c91: ACS request; acsRequestId=“16ec5f296050000” acsRequestName=“Download” acsRequestCommandKey=“16ec5f296050000”
2019-12-02T09:30:40.218Z [INFO] 85.114.108.132 000ef4-KW5262BC15A-000ef4c40c91: ACS request; acsRequestId=“16ec5f296050100” acsRequestName=“GetParameterNames”
2019-12-02T09:30:40.268Z [INFO] 85.114.108.132 000ef4-KW5262BC15A-000ef4c40c91: ACS request; acsRequestId=“16ec5f296050101” acsRequestName=“GetParameterNames”
2019-12-02T09:30:40.355Z [INFO] 85.114.108.132 000ef4-KW5262BC15A-000ef4c40c91: ACS request; acsRequestId=“16ec5f296050102” acsRequestName=“GetParameterNames”
2019-12-02T09:30:40.406Z [INFO] 85.114.108.132 000ef4-KW5262BC15A-000ef4c40c91: ACS request; acsRequestId=“16ec5f296050103” acsRequestName=“GetParameterNames”
2019-12-02T09:30:40.490Z [INFO] 85.114.108.132 000ef4-KW5262BC15A-000ef4c40c91: ACS request; acsRequestId=“16ec5f296050104” acsRequestName=“GetParameterNames”
2019-12-02T09:30:40.536Z [INFO] 85.114.108.132 000ef4-KW5262BC15A-000ef4c40c91: ACS request; acsRequestId=“16ec5f296050105” acsRequestName=“GetParameterNames”
2019-12-02T09:30:40.622Z [INFO] 85.114.108.132 000ef4-KW5262BC15A-000ef4c40c91: ACS request; acsRequestId=“16ec5f296050106” acsRequestName=“GetParameterNames”
2019-12-02T09:30:40.703Z [INFO] 85.114.108.132 000ef4-KW5262BC15A-000ef4c40c91: ACS request; acsRequestId=“16ec5f296050107” acsRequestName=“GetParameterNames”
2019-12-02T09:30:40.790Z [INFO] 85.114.108.132 000ef4-KW5262BC15A-000ef4c40c91: ACS request; acsRequestId=“16ec5f296050108” acsRequestName=“GetParameterNames”
2019-12-02T09:30:40.836Z [INFO] 85.114.108.132 000ef4-KW5262BC15A-000ef4c40c91: ACS request; acsRequestId=“16ec5f296050109” acsRequestName=“GetParameterNames”
2019-12-02T09:30:40.881Z [INFO] 85.114.108.132 000ef4-KW5262BC15A-000ef4c40c91: ACS request; acsRequestId=“16ec5f29605010a” acsRequestName=“GetParameterNames”

then i see this :
2019-12-02T09:37:51.667Z [ERROR] 85.114.108.131: Session timeout; sessionTimestamp=1575279439397 deviceId=“000ef4-KW5262BC15A-000ef4c40c91”
2019-12-02T09:40:10.321Z [INFO] 85.114.108.130 000ef4-KW5262BC15A-000ef4c40c91: Inform; cpeRequestId=“1804289383” informEvent=“M Download,7 TRANSFER COMPLETE,1 BOOT,4 VALUE CHANGE” informRetryCount=0

@miami1983, you can set the config value for cwmp.downloadTimeout parameter, which will be enough to transfer the firmware from ACS to CPE. You can calculate the possible value using the bandwidth and size of the firmware.

@zaidka wrote about this - Configuring Genieacs 1.2.0-beta

There should be no need for this. A lot of CPE do not properly terminate the session when they get a download request. A lot of them will immediately start the download request and leave the CWMP session to timeout. It can be frustrating when you are trying to debug file download issues, but its usually not an issue.

just what i need to see any action taken give me green success

how it be done ?