Guest

Preview Tool

Cisco Bug: CSCvs61571 - Cat3k/Cat9k- OBJ_DWNLD_TO_DP_FAILED after exceeding hardware capacity for adjacency table

Last Modified

Nov 10, 2020

Products (8)

  • Cisco Catalyst 9500 Series Switches
  • Cisco Catalyst 9500 Series Switches
  • Cisco Catalyst 3850 Series Switches
  • Cisco Catalyst 3650 Series Switches
  • Cisco Catalyst 9600 Series Switches
  • Cisco Catalyst 9200 Series Switches
  • Cisco Catalyst 9300 Series Switches
  • Cisco Catalyst 9400 Series Switches

Known Affected Releases

16.9.4

Description (partial)

Symptom:
After exceeding the hardware capacity of the switch for the number of adjacencies, it is expected that the packet forwarding for some prefixes won't work. The switch will show following error message when the hardware limit is crossed:

FED_L3_ERRMSG-3-RSRC_ERR: Switch # R0/0: fed: Failed to allocate hardware resource for adj entry due to hardware resource exhaustion

However, in some cases the switch keeps experiencing packet forwarding issues for some prefixes, even when the extra resources are already freed up from the hardware table and the number of adjacencies is again below the limit. When this happens, switch shows following error message:

%FMFP-3-OBJ_DWNLD_TO_DP_FAILED: Switch # R0/0: fman_fp_image: adj <>, Flags None download to DP failed

Conditions:
1. The trigger for the issue is to exceed the adjacency hardware capacity of the switch. Hardware capacity can be monitored with the help of following commands:

sh platform hardware fed switch <active/standby> fwd-asic resource tcam utilization 0
sh platform hardware fed switch <active/standby> fwd-asic resource rewrite utilization 0
sh platform hardware fed switch <active/standby> fwd-asic resource utilization 0
sh adjacency summary


2. Once the number of adjacencies is again below the limit and there's enough space in hardware for all the resources, switch should be able to forward the traffic in a regular way, but due to this bug, it may experience issues to program/remove some of the adjacencies from data-plane. If that's the case, it will throw the %FMFP-3-OBJ_DWNLD_TO_DP_FAILED error for those adjacencies. Object manager errors can be monitored with the help of following command:

show platform software object-manager switch <active/standby> f0 statistics
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.