Hi Guys,
We are facing issues related with windows server discovery which are hosted on Azure Virtual Machines. According to Azure documentation each Azure VM have arp table with ips assigned to same MAC address 12:34:56:78:9a:bc. It helps Azure to manage Layer 3 traffic.
https://cloudnetworking.io/2019/01/15/azure-virtual-networking-basics/
These seems to lead to big problem when doing horizontal discovery.
The table discovery_net_arp_table have multiple entries for came CI name and multiple entries fr same IP (See picture 1). Now when system tries to do discovery of device which has multiple entries it fails with the following message ( see log below ).
Is this a bug in ServiceNow that it is not aware of such setup for windows deployed in Azure or we missed something during configuration ?
Found duplicate records in lookup table [discovery_net_arp_table] using fields [ip_address,mac_address] and reference field [cmdb_ci],Too many other errors,Abandoning processing payload item '{"className":"cmdb_ci_ip_address", "values":{"discovery_source":"ServiceNow","ip_version":"4", "install_status":"1","netmask":"255.255.255.0","ip_address": "10.115.5.23","sys_class_name":"cmdb_ci_ip_address"}, "internal_id":"95ca6f5a5f4xxxx", "sys_object_source_info":{"source_name":"ServiceNow"}, "settings":{},"sys_ire_info":{"ire_received_time": "2020-12-15 13:15:37"}}', since its depends on payload item '{"className":"cmdb_ci_win_server","values":{"os_address_width" :"64","short_description":"","default_gateway":"10.115.5.1", "chassis_type":"Desktop","virtual":"true","u_deployment_type": "Public","os_domain":"xxx","cpu_core_thread":"1", "cpu_manufacturer":"xxx", "sys_class_name":"cmdb_ci_win_server","cpu_count":"1", "manufacturer":"7b
Picture 1
