Load Sharing via Secondary Link - Part 2

Let's look at the routing behaviour from the reverse direction now i.e.R5 to R1

Traceroute shows

We can see that even if the outbound path from R1 for the destination 2.2.2.2 was R1-R2-R3-R4-R5, the return path is R5-R4-R2-R1 which means that it prefers the primary CPE for inbound routing. We have an asymmetric routing issue.

Load Sharing via Secondary Link - Part 1

If you are working for a service provider then you may have seen that it is quite  a common practice to install two circuits and two CPEs at a customer site for the resiliency purpose. One of these circuits act as primary and carry all the inbound/outbound traffic. The second circuit acts as a backup and not used unless the primary circuit or the CPE fails.

Here is the diagram showing the scenario

On customer Site A, we have two CPEs, R2 as the primary and R3 as the backup. R1 represents a customer device on the LAN.  This customer has another remote office Site B which is shown as R5 (Single CPE). R4 is the service provider router.

CDP neighbor details

When we have two L3 switches connected with multiple SVI, when we do show cdp neighbor details which SVI's IP we suppose to see when we run this command?