Some time ago I received request to automate file transfer between FTP server and Development systems. Both, FTP server and Development system, are Windows-based. FTP server was running FTP over SSL only, so that automatically eliminated built-in Windows FTP command-line app. As I was using WinSCP in the past decided to do quick check if it is possible to use it in batch mode, so I can create script and run it on Windows Task Scheduler to automate whole process.
In this article you can find description of parameters in rancid.conf. By changing parameters in this file you can impact the way RANCID will behave, collect and process collected information. You can also define type of version control repository and email notifications as well as many other option.
RANCID is a great automation tool which allows you to collect configuration from network devices and store in repository with version control (CVS or SVN). In this article I will show you how to install RANCID and prepare to work on openSUSE 11.4 with subversion as repository for configs.
Having repository with network devices configuration might be also part of disaster recovery planning as in case of failure it will be easy to pull recent configuration from repository and apply on replacement router or switch.
To demonstrate commands I’m using copy&paste from PuTTY while executing step-by-step what is described in this article.
Quick installation how-to for Nagios on openSUSE 11.4 “Celadon” platform. Same procedure applies to other versions of opeSUSE platform. I’m using version 11.4 for my LAB purposes.
If you need to capture configuration of Windows-based DHCP server for documentation or review purposes, this might be handy:
netsh -r lab-dc-01 dhcp server dump > C:\dhcp-lab-dc-01.txt
NOTE: lab-dc-01 in example command is name of the Windows server which has DHCP installed.
Example DHCP server dump from Windows Server 2008 R2 you can see here. It contains one scope for subnet 172.16.90.0/24, option for DNS and default gateway defined.
Here is quick script which connects to Active Directory, reads all computer accounts from Organization Unit (OU) indicated in script and then pings all computers found in that OU. It might be handy if all server accounts are located in one OU.