Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
You don't. Something to open a TAC case for.
Understand, certain features of IOS dynamically use memory, and as IOS doesn't garbage collect, so memory fragmentation is normal. However, if you're low on free memory, this memory fragmentation may cause issues (when processes are unable to obtain the memory they want). The solution is to insure there's adequate free memory. (Either increase RAM in device or stop using some features that use much internal memory.)
It's also possible, bugs in IOS will allocate and not release RAM, i.e. a memory leak. For these either you'll need Cisco to investigate, or you might try determining if newer IOS version has already corrected issue.
