Emiel Zwart
asked on
Config Cisco Switch
If I look in a Cisco switch I see the config.txt file. Every time I save the running config (copy r s or write) then the config.txt is updated with the current timestamp. I thought that when I save a running config it saves in the nvram of the switch and not in the flash memory. However when I look in a router then I can't see a config.txt. So how is this possible? Thnx in advance.
what is the question , please share details of the Swith an router models
ASKER
I have tried it on a 3560 swtich and 1841 router. The question is why does the switch save the config to config.txt and the router doesn't. They both have nvram.
Note that with Cisco L2 switches configs are written to memory and nvram at the same time. The running config and startup-config are the same always. See this blog:
http://tech-on-tech.blogspot.com/2007/04/cisco-tip-saving-configuration-changes_01.html
http://tech-on-tech.blogspot.com/2007/04/cisco-tip-saving-configuration-changes_01.html
ASKER
Can you tell me what the reason is that the Switch does saves it 2 times and the Router only once to nvram?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
intresting,
Don, do you have a link to this information about where the fiels get saved.
I know on some switchs when you do a "DIR" for cirtian file systems you get a almulgation of seperate file systems.
also does any one know the difference between a
write commands
and the copy run start?
is this a throw back from them both. where copy run start. copies the data to the nvram
where as write copied the config to the flash memory.
so now both commands copy the running config to both the nvram and the flash.
Don, do you have a link to this information about where the fiels get saved.
I know on some switchs when you do a "DIR" for cirtian file systems you get a almulgation of seperate file systems.
also does any one know the difference between a
write commands
and the copy run start?
is this a throw back from them both. where copy run start. copies the data to the nvram
where as write copied the config to the flash memory.
so now both commands copy the running config to both the nvram and the flash.
No.
Most platforms today are saving the config in flash.
"write memory" is the "legacy" version of "copy running-config startup-config". They perform the exact same function. Cisco has been saying they will discontinue the write commands for years but they're still around.
Most platforms today are saving the config in flash.
"write memory" is the "legacy" version of "copy running-config startup-config". They perform the exact same function. Cisco has been saying they will discontinue the write commands for years but they're still around.