Top Dow Mapping not discovering network devices
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
My organization is trying to move our CMDB Service Map from Manual mapping to Top Down mapping. I recently tried to do a Top Down map for our main website application service alongside the manually mapped servers the website is hosted on. The top down map discovers the Netscaler and the Microsoft IIS server, but then stops before it hits the servers where it's hosted. No network equipment, no continued pathing, just ends. Why would this be the case?
- Labels:
-
Service Graph
-
Service Graph Connector
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @jxgulotta ,
I have been following the below checklist if any errors in Service mapping. See if this helps.
- Top-Down Service Mapping Troubleshooting Checklist:
1. Discovery Configuration
Are Discovery credentials (Windows, SNMP, SSH, etc.) correctly configured for all layers (IIS, backend servers, network devices)?
Is MID Server properly placed to access all components (especially backend servers)?
Are Discovery schedules running successfully and covering all relevant IP ranges?
2. Network Visibility
Are network devices (routers, switches, firewalls) between IIS and backend servers discovered?
Is SNMP enabled on network devices for topology mapping?
Are firewall rules allowing traffic between MID Server and backend servers?
3. Traffic and Connection Analysis
Is NetFlow or traffic monitoring enabled between IIS and backend servers?
Is SSL termination happening at Netscaler? If yes, is traffic between Netscaler and backend servers visible?
Are non-standard ports being used that might not be captured by default patterns?
4. Service Mapping Patterns
Are Service Mapping patterns for the application correctly defined and active?
Are custom patterns needed for proprietary or non-standard services?
Are entry points (URL, port, protocol) correctly configured for Top Down mapping?
5. Server Discovery Status
Are backend servers successfully discovered and classified in CMDB?
Do backend servers have application services identified (e.g., Tomcat, SQL, etc.)?
Are there duplicate CI entries causing mapping conflicts?
6. Manual Mapping Conflicts
Are manually mapped servers interfering with Top Down mapping?
Have you tried removing manual mappings temporarily to test Top Down discovery?
Is merge behavior between manual and Top Down maps configured correctly?
7. Logs and Diagnostics
Have you reviewed Service Mapping logs for errors or discovery gaps?
Are there mapping errors or skipped steps in the Top Down trace?
Have you enabled debug mode for deeper insight into mapping behavior?
8. CMDB Health
Is the CMDB data model aligned with Service Mapping requirements?
Are relationships between CIs (hosted on, runs on, depends on) correctly defined?
Are there orphaned CIs or outdated entries affecting mapping?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago