When using CPE to connect to Genieacs and refresh nodes, if a commit is submitted for refresh more than ten or dozens of times, there will always be a Session too long to complete error. Do I need to configure something to avoid this error? Because there are thousands of nodes submitted by CPE, this problem often occurs. Is there any way to solve it
Why are you doing an explicit commit?
It’s usually not required to call this function as it called implicitly at the end of the script and when accessing any property of the promise-like object returned by the declare() function. Calling this explicitly is only necessary if you want to control the order in which parameters are configured.
What problem are you actually trying to solve?
The specific problem is described in the above picture. When a commit is submitted, an error will occur. It is necessary to resubmit it many times before the desired node can be refreshed.
I want to know how to solve the error of Session too long to complete caused by cpe refreshing too many nodes submitted, and what config file needs to be modified for genieacs
Don’t refresh the entire tree. There is no need to refresh the entire data model.
I don’t quite understand what you mean. If you don’t need to refresh the entire node, just refresh a single node? If it is refreshing a single node, how can it be refreshed without this node? For example, if a node is searched directly but not displayed, how can the refresh of this node be submitted? At this point, it is necessary to refresh the Device node, which is the overall node of the device tree. There will be a problem of Session too long to complete.
The second question is, I want to extend the functionality of this genieacs. How do I compile the code on GitHub? Because the code wiki is not very detailed, can the session too long to complete described above be eliminated by modifying the code or modifying the configuration file of genieacs installed on Linux? If the code can be modified, how can it be modified, how can it be compiled, and are there any relevant materials and detailed documentation provided.
Lets start at the beginning. Are you trying to refresh the entire parameter model for every device on your network?
Yes, when the CPE device refreshes the system and reconnects to Genieacs, the previously refreshed device nodes have disappeared and need to be refreshed to commit the entire device. However, once the commit is made, the issue of Session too long to complete will occur. Now we need to solve this problem
Do you mean factory default aka bootstrap?
This is inaccurate. You do not need to refresh the entire device before its added to GenieACS. This was the behavior in v1.0. But has not been the case for 8 years or so.
Where I’m going with all these questions is you are making things much harder on your self, and slower for your customers by trying to refresh the entire device parameter model. Only refresh the parameters you actually care about. I guarantee you don’t need 99% of the data thats returned from the CPE.
Only in my lab do I refresh the entire parameter data model for a particular model of router. I do this to see if the vendor exposed new/different capabilities and to see what they “fixed” or “improved”
Yes, after resetting the CPE to factory settings and reconfiguring the connection to Genieacs, if the node I want is not displayed on Genieacs, I will refresh the entire Device node. This time, there will be a problem of session too long to complete, as shown in the image above. Now I don’t know how to refresh the individual node I want, so I need help
Hello, are you still there? I need help
The solution is to not refresh the entire data model. I’ve pointed this out numerous times. There is absolutely no need or purpose served by refreshing the entire data model on a router deployed to a customer premise.
So, I need to refresh a single node, but as shown in the picture, the node has not been refreshed. What do you mean by not refreshing the entire device? Please give an example
Refreshing Device. or InternetGatewayDevice. would be refreshing the entire device. And there is absolutely no need to do that.
You’ve obfuscated everything about your device so I can’t even tell you which data model version it supports.