infrastructure service map
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi Client is expecting service map which looks like this
BxxCore01
|
FGT-PRI-Bxx01
|
BxxHCC01
|
BxxHVN01/02
|
BxxFS01 / BxxAPP01 / BxxSQL01 /BXXDC01
this is located at a on shore and its on-prem . I have tried using top-down mapping but its showing only servers client expecting switches and firewall as well. How can i achieve this servicemap. I am suggesting manual map creation but client is bit skeptical about i.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
From the screenshot, it looks like the expectation is to see the complete infrastructure path:
Switch → Firewall → Windows Cluster → Hyper-V → Servers
I would first validate the CMDB relationships and Discovery results before changing the Service Mapping configuration.
A few things I would check:
- Validate the CIs in CMDB
Make sure the switch, firewall, Windows cluster, Hyper-V hosts and downstream servers are correctly discovered and classified. - Check the CI relationships
Go to the relevant CIs and verify the expected relationships are present in CMDB. For network devices, Discovery can create Layer 2 relationships such as server-to-switch and switch-to-switch based on CDP, LLDP and ARP information. - Check the application service CI list
I would check the CI List for the mapped service as well as the graphical map. This helps determine whether the infrastructure CIs are being discovered as part of the service but are not appearing in the visualization. - Validate Discovery for the network devices
For the IP switch, verify that Discovery has the required IP information, SNMP credentials and connectivity to the device. The Network Switch pattern also creates the relevant network-related CI information and relationships. - Validate the Service Mapping entry point
Remember that Top-Down Service Mapping starts from the application/service entry point and follows the dependencies it discovers. It is not intended to simply create a complete network topology starting from the switch.
If the customer's requirement is specifically to show the complete network infrastructure topology, rather than the dependencies required by an application service, I would also look at Discovery/CMDB Dependency Views rather than trying to force the complete network topology into Service Mapping.
So, before making any customization, I would start with CMDB relationships → Discovery results → Service Mapping CI list → Service Mapping entry point. That should help identify whether the issue is with discovery, relationships, or simply how the service map is being visualized.
Useful references:
- Service Mapping – Map a single application service (Zurich)
- Network Switch Discovery
- Layer 2 Discovery / Network Connections
I would not recommend manually creating the network relationships just to make the map look like the customer's diagram. First establish whether those relationships can be correctly discovered and represented in CMDB.
