That ASA (like any L3 device) would not pass broadcasts unless you are in L2 (transparent) mode.

Something else is happening if  you ASA is in Routed mode.

Please try to explain the symptoms as Federico suggested.

I  would start by checking the logs.

PK

Thanks for your interest :

My ASA is in routed mode

with proxy cache enable for all interfaces

I have enabled the thread detection

and anti-spoofing protection

I detected a constent UDP broadcast flow with a source address network (mismatch conf from a swith from a secondary network site) logged on 2 interfaces bringing VLANs

the ASA as classified it as an ATTACK so all the paquets was dropped

and logged

Resulting ASA  stopped all forwards on the interfaces infected.

Due to the emergency service quality i decided to take another ASA to load the same conf file --> all communication gone well

But when i took the first blocked ASA and reset ,reload conf it still remind in this state untill i disable enable proxy cache ...

"My point of view " :

first : the cache arp as been corrupted

second : due to an over counting dropped paquets it crashed

finaly : due to an over counting dropped paquets it put itself on a sort of security mode and disable forwards on the infected interrfaces

regards ...