Multiple Servers have wrong "IP Connection::IP connection" with Routers/Switches that are not directly connected - Support and Troubleshooting

Multiple Servers have wrong "IP Connection::IP connection" with Routers/Switches that are not directly connected Issue .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } }  Servers from one region are showing IP connection::IP connection with multiple different switches and routers that do not seem to be valid.

One server has IP Connection :: IP connection relationship with more than 100 routers. Most of these routers are located in a different region when compared to servers Release .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } All

Cause .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } If you look at the SNMP-Routing input, You can see the following input from the switch. From this we create a router interface with dest_ip_network as 10.0.0.0/8

76 10.0.0.0 255.0.0.0 0.0.0.0 3

-when discovery completes it will generate a discovery device complete event. Then, that event will trigger a script action, which will call the script include, which is the "L3 Mapping script". In that logic, it will search the dscy_route_interface table for hi_ip and lo_ip.

-So, if you are scanning any computers or servers that fall within these ranges, you will get these "IP connection::IP connection" relationships created between those devices to this switch accordingly.

-In some cases, this may be a valid route on the switch because of the configuration of the switch. You can ignore this by making some modifications to L3 Mapping script include.

Resolution .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } If you would like to ignore this dest_ip_network, please add the following line in L3 Mapping script include to ignore the dest_ip_network 10.0.0.0/8 as it will have huge range(10.0.0.1-10.255.255.255). As said above, if you are scanning any server which is in range (10.0.0.1-10.255.255.255), it will create a IP connection::IP connection with the router.

Please add the following to ignore this dest_ip_network

after below line (around 98):

var gr = new GlideRecord("dscy_route_interface");

add: gr.addQuery("dest_ip_network","!=","10.0.0.0/8");

Please note, there may be other dscy_route_interface records that are causing the connection to be created. If adding the above query to exclude route "10.0.0.0/8" does not resolve the issue, check the dscy_route_interface table for other matching networks - or alternatively view the dscy_route_interface records for one of the routers that continues to have the relationships created. If you are able to confirm that another large network is defined in the dscy_route_interface table, add it as another query similar the above, making sure that the query exactly matches the "dest_ip_network" field of the dscy_route_interface table.

To provide an example - if there were to be a dscy_route_interface for a router with dest_ip_network "169.0.0.0/8", you could add the following query at the same position as the above mentioned query:

gr.addQuery("dest_ip_network","!=","169.0.0.0/8");

Further troubleshooting information can be found in the following Knowledge Article:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0598422