DragonFly On-Line Manual Pages

Search: Section:  

ciscoconfr(8)          DragonFly System Manager's Manual         ciscoconfr(8)


NAME

       ciscoconfr


SYNOPSIS

       ciscoconfr router log-entry


AVAILABILITY

       This program has been installed successfully on FreeBSD 2.2.6-RELEASE,
       Linux RedHat 4.2, Solaris 2.5.1, IRIX 5.3 and HP/UX 10.20. Feedback
       regarding other platforms is welcome.


DESCRIPTION

       ciscoconfr will retrieve configuration from a Cisco router using
       rsh(1), and store it under RCS source control in the directory
       /usr/local/share/cisco (this directory was specified on this host at
       install time).

       Blank lines, comments and other garbage are automagically pruned from
       the router configuration to prevent unnecessary RCS deltas being formed
       from insignificant changes.

       ciscoconfr is intended to be run automatically by ciscoconfd(8) to
       maintain a configuration history for multiple routers.

       Parameters for ciscoconfr are as follows:

       router           A router's host name in a format suitable to be passed
                        to rsh(1)

       log-entry        A log entry to provide supporting information when
                        checking the changed configuration in using ci(1)


ROUTER CONFIGURATION

       The user which ciscologr runs as must be permitted to issue enable
       commands to routers using rsh(1).  To allow this to happen, some
       configuration of the appropriate routers is necessary. The following
       example allows the user "jabley" to issue enable-mode commands via rsh
       from the host 203.97.2.226:

       ip rcmd rsh-enable

       ip rcmd remote-host jabley 203.97.2.226 jabley enable


SECURITY

       Warning!  Do not type these commands into your router without a
       thorough understanding of the security implications for your network.


VERSION

       1.00 (6 Apr 1998)

       More recent versions may be available; check for details at
       http://www.patho.gen.nz/~jabley/


BUGS

       If a router's non-volatile RAM is otherwise engaged (e.g. by a "write
       mem" issued by an operator, or by a slave-sync in units with multiple
       route processors), the configuration retrieved from the router will be
       the single line `Non-Volatile memory is in use' .

       This should only happen infrequently as long as ciscologr(8) is not run
       so often that the instinctive post-configuration "write mem" is always
       caught.

       Frequency of running ciscologr can be reduced by sensible application
       of the -t parameter to ciscologd(8).


SEE ALSO

       ciscoconfd(8), rsh(1), ci(1), co(1)


AUTHOR

       Joe Abley <jabley@automagic.org>

                                  6 Apr 1998                     ciscoconfr(8)

Search: Section: