- My View
I am currently discovery routers and switches for a customer but for some reason the source ip (the ip used to discover the device) is not being mapped to any field in the cmdb, for instance, we discovered a router using the ip 10.50.199.100 so our customer is expecting to have this source ip (10.50.199.100) in some field in the cmbd, but this ip is not at any attribute of the ci, neither ip_address or any related list such as network adapters or CI IPs.
I went through the payloads and noticed that discovery is ignoring ip addresses with IfType 24 which seems to be loopbacks,
Does anybody knows Why are loopbacks interfaces/ip adrresses ignored? how can I change this behaviour?
Business Critical: Significant Impact
Affected Users: All Users
Start Date: 2017-03-23 14:19:52
Loopback interfaces are virtual. They do not have any hardware associated with them. This might be the reason why it is being ignored. A workaround for this is to write a BR to update the IP address used during scanning to the IP address of this CI after the record has been inserted (or an async BR).
There are a few properties on the Discovery properties page which define how to treat different interfaces on Network equipment 1) physical interfaces, 2) switched interfaces and 3) virtual interfaces,
I don't see 24 as a default value in any of these 3 properties on our system.
Have you attempted to add the interface type to the Virtual Interface property (glide.discovery.virtual_interface_types) on the discovery properties page?