Has anyone seen this before? This is definitely a first for me.
Here is the problem:
If I telnet to a router and execute the "sh start" command and then try to execute it again using another remote telnet session, the startup config will not open up.
The error message I get is the following:
%Error opening nvram:/startup-config (Device or resource busy)
The way to eliminate this message is to terminate the original telnet session OR return to the command prompt in the original telnet window. In other words, when executing the "sh start" command, do not leave it where there is still "-more-" configuration to view. Type any letter to break it and get back to the command prompt. If you do that, the "sh start" command will work from the second telnet session.
I think this is weird behavior and I have never seen it before. Cisco does have a webpage that dicusses it, but it doesnt elaborate on whether this is a bug or normal behavior or why this happens. They also dont tell you about returning to the command prompt on the initial session to get it to work on the second one. All they tell you to do is terminate the original session.