9200 multicast resources

[richyvrlimited]

seeing a lot of the following in our stacked 9200 switch logs

%FED_L3M_ERRMSG-3-RSRC_ERR: Switch 4 R0/0: fed: Failed to allocate hardware resource for Adjacency - rc:FED_L3_MCAST_OUT_OF_RESOURCES

if I run 

show platform hard fed switch active fwd-asic resource tcam utilization

then it's obviously not an erroneous error

CAM Utilization for ASIC [0]
Table Subtype Dir Max Used %Used V4 V6 MPLS Other
------------------------------------------------------------------------------------------------------
Mac Address Table EM I 16384 268 1.64% 0 0 0 268
Mac Address Table TCAM I 256 21 8.20% 0 0 0 21
L3 Multicast EM I 1024 764 74.61% 764 0 0 0
L3 Multicast TCAM I 256 256 100.00% 250 6 0 0
L2 Multicast TCAM I 1024 11 1.07% 3 8 0 0

is there any way of adjusting the platforms resources to provide more L3 multicast resources to the TACM?

sho sdm perfer vlan/advanced doesn't look like it changes the number of available mcast entries, just wondering if there's an alternative method or if I'm stuck. Replacement of the switches isn't an option, they're new in to replace 3560's.

Many thanks

[Georg Pauwen]

Hello,

the bug below might apply. Workaround is to reload the switch...

Cat3k/Cat9k- OBJ_DWNLD_TO_DP_FAILED after exceeding hardware capacity for adjacency table
CSCvs61571
Customer Visible
Notifications
Save Bug
Open Support Case
Description
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 fwd-asic resource tcam utilization 0
sh platform hardware fed switch fwd-asic resource rewrite utilization 0
sh platform hardware fed switch 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 f0 statistics

Workaround:
- Reload switch