Ask the Community
Groups
Network Discovery runs in a loop and resulted as error/stale - Connect IT Community | Kaseya
<main> <article class="userContent"> <p><strong>PROBLEM:</strong></p> <p>Network discovery runs in a loop and later the status becomes STALE.</p> <p><strong>IDENTIFICATION:</strong></p> <p><em>Example</em>: Sample discovery logs from <Traverse_Home>\topology\logs\discovery.txt</p> <pre class="code codeBlock" spellcheck="false" tabindex="0">14:34:55 . loopmon noAddr - --------- Extensions --------------<br>14:34:55 . loopmon noAddr - Number of extensions: 5<br>14:34:55 . loopmon noAddr - ext-layer3 complete: false<br>14:34:55 . loopmon noAddr - ext-l3routing: Percent: 0 numExpect: 1 processed: 0 qSize: 0 inPlay: 0 bSent: 0 bRcved: 0<br>14:34:55 . loopmon noAddr - L3vex: Percent: 0 numExpect: 1 processed: 0 qSize: 0 inPlay: 0 bSent: 0 bRcved: 0<br>14:34:55 . loopmon noAddr - ext-conn complete: false<br>14:34:55 . loopmon noAddr - ConnPr: Percent: 100 numExpect: 4 processed: 4 qSize: 0 inPlay: 0 bSent: 1234 bRcved: 1352<br>14:34:55 . loopmon noAddr - ext-layer2 complete: false<br>14:34:55 . loopmon noAddr - ext-vmware complete: false<br>14:34:55 . loopmon noAddr - ext-rpt complete: false<br><strong>14:34:55 . loopmon noAddr - Percent Complete: 40</strong><br>14:36:55 . loopmon noAddr - ************** Progress *****************</pre> <p>Discovery in loop appears as above, it starts running in a loop with a keyword (<strong>loopmon</strong>) and <strong>percentage complete</strong> shows less than 100. </p> <p> </p> <p><strong>RESOLUTION:</strong></p> <p><em>Configuration on BVE</em></p> <ul><li>Check site.properties file in <Traverse_Home>\plugin </li> <li>If it is not available then create a <strong>site.properties</strong> on the same path and add the below parameter.</li> </ul><pre class="code codeBlock" spellcheck="false" tabindex="0">traverse.discovery.network.timeout=120</pre> <ul><li>Save the configuration file</li> <li>Restart the correlation summary engine (CSE) and Internal communication bus (JMS) on BVE instance</li> </ul><p><em>Configuration on DGE/DGEx</em></p> <ul><li>Take a backup of<strong> "</strong><Traverse_Home>\topology\config\config.default<strong>" </strong> file</li> <li>Make below changes in original "config.default" and save the configuration</li> </ul><pre class="code codeBlock" spellcheck="false" tabindex="0">IPDAllowSuspiciousIP false<br>IPDPingPrimerPeriod 0</pre> <ul><li>Restart the data gathering engine on DGE/DGEx instance where the problematic discovery configured</li> <li>Run the problematic discovery from webapp ( by navigating to ADMINISTRATOR -> DISCOVERY)</li> </ul><p>If the network discovery still fails. Kindly zip <em><Traverse_Home>topology</em> & <em><Traverse_Home>logs</em> directory from DGE/ DGEx and attach it to an opened ticket with support. Please do not attach them here.</p> <p> </p> <p><strong>APPLIES TO</strong></p> <p>9.5 and above</p> <p><strong>REFERENCE:</strong></p> <p><a rel="nofollow" href="https://kaseya.vanillacommunities.com/kb/articles/aliases/kaseya/hc/en-gb/articles/229045288-Traverse-Troubleshooting-device-discovery-or-device-dependency-issues">Traverse: Troubleshooting device discovery or device dependency issues</a></p> <p>PT- #321408</p> <p> </p> <p> </p> <p> </p> </article> </main>