/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .super-nav { display: flex; justify-content: flex-end; align-items: center; margin: 0 auto; max-width: 1264px; padding-left: 40px; padding-right: 40px; height: 40px; text-align: right; } .super-nav a { color: #34427c; margin-right: 20px; padding: 10px; text-decoration: none; } .super-nav a:hover, .super-nav a:focus { background-color: #f7f9fa; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 0; } .footer-image { background-image: url("/themes/kaseya/assets/images/footerImage.png"); height: 500px; background-repeat: no-repeat; background-size: cover; margin-top: -100px; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer-main-content { background-color: #000; padding: 100px 0; } .footer .footer-col-title { color: #ffffff; font-weight: 700; font-size: 13px; padding-bottom: 10px; text-transform: uppercase; } .footer .footer-link { color: #9b9ca0; text-decoration: none; } .footer .footer-link:hover, .footer .footer-link:focus, .footer .footer-link:active { text-decoration: underline; } .footer-main-content .footer-link { padding-top: 10px; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-main-content-row { align-items: flex-start; } .footer-bottom-content { padding: 10px; align-items: center; } .footer-col { padding: 0 3px; display: flex; flex-direction: column; } .footer-col-copyRight { justify-content: flex-start; color: #9b9ca0; flex: 1; display: flex; } .footer-last-col { flex-direction: row; } .footer-last-col .footer-link { padding-right: 10px; text-transform: uppercase; } @media screen and (max-width: 768px) { .super-nav { padding-right: 0; } .footer-image { height: 250px; } .footer-main-content { padding: 40px 0; } .footer .footer-col-title { padding-top: 10px; } .footer-row:not(.footer-main-content-row) { display: block; } .footer-col:not(.footer-main-content-col) { width: 100%; text-align: center; padding: 10px 0; } .footer-main-content-col { width: 50%; } .footer-last-col { flex-direction: column; } .footer-last-col .footer-link { padding-bottom: 10px; } } /*# sourceMappingURL=styles.css.map */ Ask the Community Groups

Traverse Traverse

Network Discovery runs in a loop and resulted as error/stale

PROBLEM:

Network discovery runs in a loop and later the status becomes STALE.

IDENTIFICATION:

Example: Sample discovery logs from <Traverse_Home>\topology\logs\discovery.txt

14:34:55 . loopmon noAddr - --------- Extensions --------------
14:34:55 . loopmon noAddr - Number of extensions: 5
14:34:55 . loopmon noAddr - ext-layer3 complete: false
14:34:55 . loopmon noAddr - ext-l3routing: Percent: 0 numExpect: 1 processed: 0 qSize: 0 inPlay: 0 bSent: 0 bRcved: 0
14:34:55 . loopmon noAddr - L3vex: Percent: 0 numExpect: 1 processed: 0 qSize: 0 inPlay: 0 bSent: 0 bRcved: 0
14:34:55 . loopmon noAddr - ext-conn complete: false
14:34:55 . loopmon noAddr - ConnPr: Percent: 100 numExpect: 4 processed: 4 qSize: 0 inPlay: 0 bSent: 1234 bRcved: 1352
14:34:55 . loopmon noAddr - ext-layer2 complete: false
14:34:55 . loopmon noAddr - ext-vmware complete: false
14:34:55 . loopmon noAddr - ext-rpt complete: false
14:34:55 . loopmon noAddr - Percent Complete: 40
14:36:55 . loopmon noAddr - ************** Progress *****************

Discovery in loop appears as above, it starts running in a loop with a keyword (loopmon) and percentage complete shows less than 100.

RESOLUTION:

Configuration on BVE

Check site.properties file in <Traverse_Home>\plugin
If it is not available then create a site.properties on the same path and add the below parameter.

traverse.discovery.network.timeout=120

Save the configuration file
Restart the correlation summary engine (CSE) and Internal communication bus (JMS) on BVE instance

Configuration on DGE/DGEx

Take a backup of "<Traverse_Home>\topology\config\config.default" file
Make below changes in original "config.default" and save the configuration

IPDAllowSuspiciousIP  false
IPDPingPrimerPeriod  0

Restart the data gathering engine on DGE/DGEx instance where the problematic discovery configured
Run the problematic discovery from webapp ( by navigating to ADMINISTRATOR -> DISCOVERY)

If the network discovery still fails. Kindly zip <Traverse_Home>topology & <Traverse_Home>logs directory from DGE/ DGEx and attach it to an opened ticket with support. Please do not attach them here.

APPLIES TO

9.5 and above

REFERENCE:

Traverse: Troubleshooting device discovery or device dependency issues

PT- #321408