We are struggling to create Relationship between Network Devices (IP-Switch) and Windows Servers

RitamB
Tera Contributor

3 weeks ago

Hi Community,

 

We have go live with Network Discovery on Previous Month in our Horizontal Discovery. But we are Seeing that Although there are around 13k active and deployed Windows Servers are there but we have seeing that only few Hundred Windows Servers have created L3 relationship (IP Connections :: IP Connections) with Network Devices, Although we run Discovery schedule ranges based on Windows Servers and Network Devices on daily basis. Can anyone Suggested why it is happening. Appreciated any help. 

0 Helpfuls
  • 379 Views
3 REPLIES 3

Kieran Anson
Kilo Patron

3 weeks ago

If you look at a server CI that has the missing relationship, check whether the CI has associated network cards with a valid IP address specified. Also check whether there are TCP/IP related records for the CI. 

 

 

0 Helpfuls

RitamB
Tera Contributor
In response to Kieran Anson

3 weeks ago

We have checked that There is valid IP address specified also we have checked there is TCP/IP related records for the CI which are basic Network Configuration. rather than this what else we can check.

0 Helpfuls

Kieran Anson
Kilo Patron
In response to RitamB

2 weeks ago

Couple things to check

 

Do your window devices have related cmdb_ci_ip_address records that have an install status of installed, as well as the referenced NIC in an installed status

 

For the network devices, dscy_route_interface holds the information to cover the routing ranges for routers. If this is incomplete, your servers won't associate correctly.

 

Property 'glide.discovery.L3_mapping.use_location' will add a constrain where the location field needs to match across servers / network devices. Set this to false if location data is not being populated

0 Helpfuls