02-10-2010 07:17 PM - edited 03-04-2019 07:28 AM
Hi,
I am getting the following message while configuring the ip sla,
Router(config)#ip sla 20085
%No memory left to create probes
Would anyone let me know what is the problem?
Thanks,
Solved! Go to Solution.
02-11-2010 03:18 AM
Hi
As far as i know it clearly says that you dont have enough free memory to configure the new probe,you might hve either exhausted your memory or utilized by other processes. You need to free up the memory or upgrade the memory.
You can use show processes memory to verify the memory utilized by the processes , also you can use show memory | free | detailed to verify the same.
If its not a critical site and can afford some downtime better to reload the box and check to flush up the memory as well.
regds
02-11-2010 03:18 AM
Hi
As far as i know it clearly says that you dont have enough free memory to configure the new probe,you might hve either exhausted your memory or utilized by other processes. You need to free up the memory or upgrade the memory.
You can use show processes memory to verify the memory utilized by the processes , also you can use show memory | free | detailed to verify the same.
If its not a critical site and can afford some downtime better to reload the box and check to flush up the memory as well.
regds
02-11-2010 11:12 AM
Thanks I have resolved the issue by rebooting the router.
.
02-11-2010 12:04 PM
You still have a buggy IOS (memory leak) and need to upgrade it.
02-11-2010 03:21 AM
Try reloading the router to begin with.
02-11-2010 04:31 PM
Hi,
We have faced a similar problem ( not exactly ip sla ). even on 7500 series router. ( we can say a higher end router ). There was one process that was
eating up the memory and it was not releasing it back to "free memory". After we rebooted the router slowly slowly it started eating up the memory upto 95 %. We exactly pointed out the process and raised a TAC with Cisco. And it was answered immediately as it was a known case with that particular IOS. ( cavets ). IOS was upgraded and we resolved this problem. ( Unfortunately this upgraded IOS was with some another issue )
As mentioned in earlier posts. Most likely your problem will get resiloved after you upgrade the IOS in which this "bug" is fixed.
Thanks
Subodh
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide