This message by itself does not point out a problem. Rather it describes a symptom that could stem from a number of reasons such as the device handling more connections than it has been designed for, large volumes of 3DES encryption taking place or high amount of SSH activity. In our case the solution turned out to be simple lowering of the xlate timeout and timeout conn. Next we did a clear xlate followed by clear arp and things were fine.
