Re: Cisco running-config replication



In article <431edfa5$0$25584$4d4eb98e@xxxxxxxxxxxxxxxxxxx>,
Pilu <Pilu@xxxxxxxxxx> wrote:
:I would like to configure a spare router to automatically download the
:running-config every hour of the production router..

:What is possible to do with cisco?

:My routers are Cisco 2610xm and 2811

The 2610xm is, I'm fairly sure, not sophisticated enough to do
that, so it would have to be operated upon by the outside.

I don't know if the 2811 is sophisticated enough; if it is,
it would have to be by some funky tcl programming, and I do
not -remember- the 28xx as having tcl [but could easily be wrong.]
Exactly what you can do with tcl is not well documented, I have
read.


:It is possible to easily schedule a config replication process?

:What do you suggest for me?

Are the 2610xm and 2811 configured the same right down to the
interface names? And do they support the same configuration file
versions and the same features? I would doubt it: the 2811 is
an integrated services router that supports a bunch of features
not available on the 2610xm.


Anyhow, what I would suggest is that you use SNMP to trigger
a tftp upload of the configuration you want to replicate, to
a tftp server, and that then you use SNMP to trigger a tftp
download of that file to the other router. You will find that
a -lot- easier than trying to program tcl right on one of the
routers.

The 2610xm is, I am sure, not designed to be able to handle
configuration failover.


Does your production router configuration really change often
enough to make copying it once an hour worthwhile? Are there
several people authorized to modify its configuration
"on the fly" ?

With SNMP you might be able to detect the time of the last
configuration write, and only bother with the upload/download
if a change had been made. That probe would probably be
fairly light-weight -- you could probably schedule that kind
of check every 10 minutes or so. And if you do upload onto a tftp
server, then you could check for differences in the configurations
[beyond the comment that gives the time the configuration was written]
and skip the download if there are no differences.


I wonder, though, whether you wouldn't be better off *not*
automating the configuration transfer, and instead set up HSRP
failover between the routers.

--
The rule of thumb for speed is:

1. If it doesn't work then speed doesn't matter. -- Christian Bau
.



Relevant Pages

  • Re: SBS 2003 Misconfigured?
    ... Netgear router because it has 8 ports, utilizes UPNP (at least it did it ONCE ... You mentioned that you assigned the ISP IP to netopia AND the netgear. ... You *can* configure the netopia to operate in bridged mode, but in this configuration, it is literally acting as modem, converting DSL/ATM traffic to ethernet and would not hold a public IP of its own. ... Quickbooks on my server (I know, I shouldn't but I HAVE to because another ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Misconfigured?
    ... I agree, with what I could have / should have done as far as the router, ... Why didn't you just disconnect the Netgear and not touch the Netopia? ... Which, based on the configuration you gave, is part of the ...
    (microsoft.public.windows.server.sbs)
  • Re: OT:--CISCO EXPERTS...
    ... boxes and Cisco routers connected to these with X21 cable. ... You mention steep learning curve but if I can just get ino router maybe can ... > want to consider any risk of providing them with an insecure configuration ... >>> Telnet access should also be disabled leaving connection via SSH or ...
    (microsoft.public.windows.server.sbs)
  • credentinals issue in cisco router. please advice all the cisco masters in the list!
    ... I am posting here the configuration of the router. ... interface FastEthernet0 ... ip route 192.168.0.0 255.255.0.0 Tunnel8 ...
    (Security-Basics)
  • Home DSL configuration BNCP problems
    ... The router information is as follows: ... With the posted configuration the dsl link is actually up and also the ... Outbound bridge packet dropped, BNCP state is Listen ... Vi2 BNCP: TIMEout: State Listen ...
    (comp.dcom.sys.cisco)