Configuration of relationships between CI's

[Riya25]

How to find if downstream and upstream relationships of a CI is right or not.

And currently there are CIs for which downstream Relationships contain same switches for all objects across the Globe.

How to find the root cause of this?

Thanks in advance.

[DuaneNMore]

This relationship imay be getting created because the Server has an address which is in the range of an Exit Routing rule for the Network Devices. Here is my suggestion. Open Up 2 tabs; one with the CI record for WTZ-AM-ASHBURN-CORE, and one with the CI record for POL-MAL-ESX001. 

In the switch (which may also be a router) look at the Exit Routing Rules Related List.

For the Server look at CI IPs related List

I assert that one of the CI IPs lives in an IP Address for an Exit Routing Rule.

We have a standard practice to put a 10.0.00/8 Routing rule in Some class of Routers. Then some of our Linux Servers use the 10. range for cluster heartbeats or some other function. because the IP address appears to be in a Direct Routing rule for some router; they appear to be "next" to each other. 

Mark it correct and helpful if applicable.

Thanks and regards,

Duane

[Riya25]

Hello Duane,

Thank you for the reply.

I am new to this,so sorry if i am asking lame questions.

Can you please be kind to explain that the fields which i have attached in the screenshot are the ones which needs to be compared and how they are related,what is the use of Exit interface rules.

And if it is true what you are saying ,can you please explain me how this issue can be solved?

[DuaneNMore]

I am uncertain how to fix this. IMHO I think the problem is that SN is building these relationships on Dest IP Networks which have no interface.

So in IP Switch(2), 192.168.0.0/16 would include the last 8 IP addresses on the ESX Server. 

So in IP Switch (1), 10.0.0.0/8 would include the first 5 addresses on the ESX Server.

Neither 192.168.0.0/16 or 10.0.0.0/8 has a router interface. 

Poking around the DeviceL3Mapping script includes it seems as though it is checking the status of the interface of the Exit Routing Rule interface.