cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

Who Me Too'd this topic

Commit Error: failed to handle CONFIG_UPDATE_START Issue

L1 Bithead

Hi All,

 

I think  most of you had experienced this failure issue once in your worklife 🙂 🙂This error reason is mostly because config memory usage is too high.

>debug dataplane show cfg-memstat statistics

As we all know the number of custom url is limited and we will likely face this commit issue after this limit exceed. But we can not be aware whether the limit exceed unless this commit issue occured. Therefore this issue might become annoying to figure out. 

I would like to ask for your advice there is any method to detect early diagnosis before this limit exceed. Also do you know a way or command to clear config memory?

 

I believe this topic will be helpful to so many of you to overcome this issue if we can find out some solution 🙂🙂

 

Thanks

Regards

Who Me Too'd this topic