For Cisco routers/switches, I use the no service conifg
in production.
What's the impact for the production system if I use the service config
command when I have the configuration already loaded in my devices?
%Error opening tftp://255.255.255.255/cisconet.cfg (Timed out)
%Error opening tftp://255.255.255.255/cbrvbc01-tgobc02-confg (Timed out)
%Error opening tftp://255.255.255.255/cbrvbc01.cfg (Timed out)
%Error opening tftp://255.255.255.255/network-confg (Timed out)
%Error opening tftp://255.255.255.255/cisconet.cfg (Timed out)
Security? Network traffic? Others?
Best Answer
The
service config
command is used to load configuration files on boot. It should have no impact to your current configuration unless you reboot.It's worth noting that even Cisco considers configuration autoloading an unneeded vulnerability. It's default is off, and probably for good reason.