<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 12/19/18 11:03 AM, Lê Văn Vượng wrote:<br>
<blockquote type="cite"
cite="mid:CKebu7HdhMGrjz48Zgh_13UZXq41Wvpefgm21U69oWS2oWPELb8umAKfAK-7lfXtu0_c1MUoWL-MLRD2jN9e5PPgwta7_sgjBvSGOTi3LXU=@protonmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div>Hi George,<br>
</div>
<div>I was enable "Connection Request" on CPE device and ACS can
reach CPE. However, just some devices can not refresh while
other device still successful.<br>
</div>
</blockquote>
<p>To investigate what's the root cause of the problem you can use
incremental approach: <br>
</p>
<p>1. Instead of hitting "Refresh" button, try to refresh one
particular object and check if it's successful (<span
class="long-text param-path">InternetGatewayDevice.ManagementServer.PeriodicInformEnable</span><span
class="long-text param-path"> seems to be a good candidate</span>).
If that works, you know that "Connection Request" mechanism works
with this CPE so you can dig deeper. <br>
</p>
<p>2. Try to compare software versions between two devices (one for
which refresh works with one for which it fails) maybe they are
different. If this is the case, make sure that the same problem
exists with other devices with the same software version.</p>
<p>3. Debug your ACS and CPE. In many cases you can find a lot of
information in your logs.</p>
<p>4. Capture network trace on ACS and if possible on CPE, compare
them. You'lll have a view of actual data transfered on the wire.</p>
<p>5. Discuss your findings with your vendor providing traces, debug
logs, etc.</p>
<p>Hope this helps.</p>
<p>Regards,</p>
<p>George<br>
</p>
</body>
</html>