I have the following faults I receive while trying to configure a routed sub-interface for an IPN in the infra tenant
I do see that the interface is configured, but I cannot ping it locally. In contrast, I can ping the IPN interface to the other enterprise switch:
here, we see there are no static routes configured:
yet, when I review operational (supposedly) data from the node, I see a static route configured with the offending, overlapping, next-hop:
what I find interesting is that the route that has this bad next-hop is a host route to the TEP of APIC #3 in the cluster and the preference is very much different than the default preference. I'm guessing this must have been an artifact of when this fabric was configured as a multi-site fabric. It has been since converted to multi-pod; however, this issue may be only tangential to the actual root cause in this case.
During troubleshooting, I added these two other routes and then deleted them. They now also show up in this view, and I believe that to be incorrect as well. You see, by lack of the left-side drop down arrow, there is no next-hop attached to either of these.
Lastly, I cannot delete these static routes from this screen:
I have checked the other interfaces and validated there are no overlapping IPs configured. I have validated that if I set the interface some other IP address, the interface does come up and is pingable. To me, unless there is another place to configure static routes that I have not checked, this appears to be buggy behavior. I've not found anything in the bug search yet. Also, I've been trying to get with TAC on this for some days now, but so far, I've not been able to connect with them. I'm thinking of trying to delete these via the REST API, but I haven't pulled the trigger on that yet.
Any thoughts on this?
