Cisco 2811 Pobe

Answered Question
Feb 10th, 2010

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,

I have this problem too.
0 votes
Correct Answer by spremkumar about 6 years 10 months ago

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

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
spremkumar Thu, 02/11/2010 - 03:18

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

bapatsubodh Thu, 02/11/2010 - 16:31

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

Actions

This Discussion

Related Content