I don't know about all platforms, but you CAN enter simultaneous configs
sessions on 2501 and 12000 routers, I just tested it.
What you cannot do is have simultaneous views of or writes to the
startup-config (NVRAM), if you try you get;
NCS_Test2501#sh start
%% Non-volatile configuration memory is being accessed, Try again later
SL-R12-01#sh conf
%% Non-volatile configuration memory is being accessed, Try again later
NCS_Test2501#wri
startup-config file open failed (Device or resource busy)

On the 10K's the following message is given when simultaneous global
configuration mode sessions are attempted:
SP-R10-01#conf t
Redundant RPs - Simultaneous configs not allowed:locked from doddsb on vty1

I am not aware of a command that you can issue that will tell you who is in
config mode,
"who" or "sh users" will tell you who is logged into the router but not what
mode they are in.

Not sure if this helps you, but hope so
Brad

""Igor Vilensky""  wrote in message
news:[EMAIL PROTECTED]
> Greetings,
>
> I wrote a very simple script which logs to a router, executes a
> configuration command ( usually 'username xxx password xxx'), and exits.
> It has been pointed out that if somebody else is in global command mode it
> might be trouble.
> I know that problems occur when two people try to edit a unix text file at
> the same time.
> Is there any mechanism IOS utilizes to safeguard against conflicts of this
> nature?
> In case it is problematic, I would like to know how to determine if
anybody
> else is in global config mode.
> Given that, my script could wait until nobody else is in that mode and
then
> execute the command.
>
> Thanks for your consideration.
> Will summarize.
>
> Igor Vilensky
> REM Inc.
> Systems Administrator
> 952-836-2201




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=64092&t=64092
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to