Getting a 202 via NBI/API, working via GUI

Help
1

Hi There,

I had a CPU issue a few days back. I then added extra CPUs to the CWMP and the DB.

Then after the DB CPU update the connections started dropping like crazy. The CWMP log just showed dropped connections.

image
image1338×952 46.1 KB

I then changed the devices to inform every 4hours and not every hour.

Had a timing issue… think I have that sorted.

Now when sending a task to the device via the NBI I get a 202 back, but doing it via the GUI it works.

image
image1579×196 9.87 KB

The services are on 3 different servers. We had that problem previously and sorted it by making sure the time is in sync. I did change it back but am still getting the 202 back.

Doing it via the GUI works everytime, but not via the NBI. I still think somehow the task is written in the DB but the device already informed in/ or it seems that way. But I am struggling to prove this.

My Connection request timeout is set to 30000

I have ONTs and ATAs connected to the service. The ATAs works fine.

202 Task queued but not processed

Any idea or help would be greatly appreciated

2

Started the NBI service on the CWMP and then the call and task works. But from the NBI itself still failing. Still pointing to a timing issue… I think anyway

3

Enable debug logging for the CPE in question?

The “Connection dropped” happens because the CPE terminates the connection while the CWMP process is still communicating with the CPE. I would ask Huawei to fix this. I suspect that once this is resolved, the other issue will be resolved too.