Verify the Endpoint Update in the FMC
When an APIC endpoint is pulled and pushed to the FMC, it’s put into a network object named SitePrefix_TenantName_ApplicationProfileName_ApplicationEPGName .
Procedure
Step 1 |
Log in to the FMC. |
Step 2 |
Click . |
What to do next
For troubleshooting purposes, you can track endpoints in the APIC's EP Tracker and Object Store Browser:
Additional notes:
-
During the push process, the REST operation (POST, PUT, or DELETE) is determined based on the comparison of what data is on the APIC and what is on the FMC.
-
For diff calculation, each tenant updates only the data of its own tenant.
-
When all endpoints are deleted from an APIC endpoint group (EPG), the corresponding object group on the FMC gets deleted too. But if the object group is referenced or used in any access rule on the FMC, because there is a dependency, the object group cannot get deleted. In this case, we keep the group name and put the localhost IP address, 127.0.0.1, inside the group instead.