Event Synchronization and Missing Event Handling

Provided VNI: 1006 already consumed in fabric

Symptom Condition Workaround
EPG create fails with VNI resource not being available in the fabric. Execute EPG create, delete, and re-create CLI in quick succession:
  1. Create EPG/Networks with user-provided VNI parameter.
  2. Delete EPG.
  3. Create EPG again with the same parameters as in step 1.
 Provide a wait of 30 seconds between the create and delete CLI on the same EPG.

vrf delete from epg and re-adding vrf to epg fails intermittently

Symptom Condition Workaround
EPG update "vrf-add" operation fails with the reason as VRF to be added has conflicting VRF on the switch. Execute EPG update "vrf-add", "vrf-delete", and "vrf-add" operation CLI in quick succession:
  1. Update EPG for operation vrf-add.
  2. Update EPG for operation vrf-delete.
  3. Update the same EPG again with operation vrf-add for the same VRF which was deleted in step 2.
 Wait of 30 seconds between the EPG update vrf-add and vrf-delete operations on the same EPG.

vrf_route_target_mapping error while creating epg (after vrf delete)

Symptom Condition Workaround
When VRF is added and deleted to/from and Endpoint Group, in quick succession, multiple times, events received from inventory service can get interleaved with the commands.

This causes EFA command execution path to find database entries that are yet to be deleted due to previous command run.

 Issue is observed when vrf-add and vrf-delete operation is executed multiple times on Endpoint Group in quick succession. Wait for a few minutes before executing the vrf-add again on Endpoint Group.

Inventory device update fails to change device table router-ip field

Symptom Condition Workaround
If the router-id is changed on the device (add/delete/modified), the device table router-ip field will not change after you do inventory device update. It's found that inventory did detect the diff and generate the RouterBgpUpdatedMsg to Tenant. Tenant did not handle this message. Add hook in the RouterBgpUpdatedMsg on tenant handler to set the RouterIP, so that the Tenant DB will have the same value with the device after update.

REST opertations aren't retried (as applicable) during the service boot

Symptom Condition Workaround
REST opertations aren't retried (as applicable) during the service boot up. The status aren't set for all the REST operations AFTER publishing all the necessary events on the message bus. For all the REST operations, set the status AFTER publishing all the necessary events on the message bus.
9036924-01 Rev AA