Loading...
Loading...
Router might report pending objects due to bd-efp-bind reason in the logs: ROUTER#show log | i DP_FAILED *Jul 3 10:31:48.406: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: F0/0: fman_fp_image: bd-efp-bind: bd 1509, efp 4243656 download to DP failed *Jul 3 11:52:58.730: %FMFP-3-OBJ_DWNLD_TO_DP_FAILED: F0/0: fman_fp_image: bd-efp-bind: bd 1511, efp 4243660 download to DP failed Output of show platform software object-manager fp active statistics will also report pending-issue-update / error-objects related to the BDI / bridge-domain being configured.
Issue happens when race condition between creation/delete of multicast traffic (Upon receving new IGMP joins/leave) AND manual creation of a BDI interface being applied on a service-instance. In some cases, this leads to internal resources being incorrectly reused causing the BD-EFP-BIND (binding the BDI interface to the service instance) to fail.
The EFP/BDI interface affected by the pending object won't work until the router is reloaded to clear the pending-objects. Alternative is to use a different BDI interface number and different bridge-domain number. Note that there is also a probability that the issue may also appear with the newly created BDI interface.
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.