04-14-2014 07:00 AM - edited 03-07-2019 07:05 PM
I have a stack of 2x 3850's(WS-C3850-48T) running flash:cat3k_caa-universalk9.SPA.03.03.02.SE.150-1.EZ2.bin.
A few day's a go i had a hanging console session after executing a "sh run | i " command, i wasnt able to clear the session.
This resulted in the following problem:
NLXXX-MER-CI3850-01#wr
startup-config file open failed (Device or resource busy)
I cant save the configuration.
The device is working OK and i can change the configuration but there is no way of saving it.
So after googling for a while i decided to reboot the stack after that everything was OK.
I just did a "sh run int" will being logging in using SSH and again the session hangs.
Now i was able to clear the session but still the same issue:
NLXXX-MER-CI3850-01#wr
startup-config file open failed (Device or resource busy)
Attached is a 'sh ver"
Solved! Go to Solution.
04-14-2014 07:47 AM
Hi,
Its due to bug. The concern is as a result of the NVRAM locking. The trigger condition for this concern is the presence of KRON configurations on the 3850.
By any chance have you configured Kron?
Regards
Inayath
Plz rate all usefull posts.
05-17-2014 05:24 PM
Hello Marc,
This behaviour is due to a bug that is know to be fixed in release 03.03.03SE using an EEM script to replace the kron job.
The startup-config and running-config on the controller become unavailable after running a kron job.
The workaround is to reload the controller. To avoid this condition, use Embedded Event Manager (EEM) with the timer event to schedule the required task.
04-14-2014 07:47 AM
Hi,
Its due to bug. The concern is as a result of the NVRAM locking. The trigger condition for this concern is the presence of KRON configurations on the 3850.
By any chance have you configured Kron?
Regards
Inayath
Plz rate all usefull posts.
04-15-2014 12:15 AM
Yes i have a small kron configuration script active in the configuration.
I will remove the kron script and then i will have to reboot the stack again.
But since i cant write the config to startup it will be there after the reboot so i will then have to quickly remove it i guess :) or is there a workaround ?
05-17-2014 05:24 PM
Hello Marc,
This behaviour is due to a bug that is know to be fixed in release 03.03.03SE using an EEM script to replace the kron job.
The startup-config and running-config on the controller become unavailable after running a kron job.
The workaround is to reload the controller. To avoid this condition, use Embedded Event Manager (EEM) with the timer event to schedule the required task.
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