If we disable L3 mapping in Discovery, will sa_network_paths still get populated by Service Mapping

[Martin Grosskop]

We are currently running Discovery with glide.discovery.L3_mapping = true.
And this in turn is creating a high volume of IP Connection::IP Connection relationships.
Which in turn brings in lots of Impacted Services to our Changes when we Refresh Impacted Services.

Whilst the links are genuine, our users don't quite get why their services are listed as impacted, when the link is quite a tenuous link via L3 - in some cases to routers running in other countries.

But we do not want to lose the ability for Service Mapping to display the Network Path between servers when you click on "Show Network Path".

From the digging we have done, it appears that the Network Path in Service Mapping is produced by reading the sa_networks_path table.

So if we set glide.discovery.L3_mapping = false, will we then stop creating IP Connection::IP Connection relationships, but Service Mapping will still be able to display the Network Path between two servers based on the trace route command Service Mapping issues while building a Service Map?

[pratiksha5]

Hi Martin, 

Did you find what they are using to crate the network path? I mean which pattern? I have to create the map for switches and can re-use the same pattern to do that. Awaiting your response.  

[Martin Grosskop]

Sorry but this refers to something that occurred at an organisation I last worked for 4 years ago.

My memory of what we uncovered back then is now a bit rusty:(