Skip site navigation (1)Skip section navigation (2)

FreeBSD Manual Pages


home | help

       MakeRancidConf -	Generate rancid	Configuration

       This worker will	generate a rancid configuration	for all	devices	in

       Optionally you can provide configuration	to control the output, however
       the defaults are	sane for rancid	versions 3.x and will create one
       rancid group called "default" which contains all	devices. Those devices
       not discovered successfully within the past day will be marked as
       "down" for rancid to skip.  Configuration is saved to the ~/rancid
       subdirectory of Netdisco's home folder.

       Note that this only generates the router.db files, you will still need
       to configure rancid's .cloginrc and schedule "rancid-run" to run.

       You could run this worker at 09:05 each day using the following

	    when: '5 9 * * *'

       Since MakeRancidConf is a worker	module it can also be run via

	~/bin/netdisco-do makerancidconf

       Skipped devices and the reason for skipping them	can be seen by using

	~/bin/netdisco-do makerancidconf -D

       Here is a complete example of the configuration,	which must be called
       "rancid". All keys are optional:

	  rancid_cvsroot:  '$ENV{NETDISCO_HOME}/rancid'	# default
	  rancid_conf:	   '/etc/rancid'		# default
	  down_age:	   '1 day'			# default
	  delimiter:	   ';'				# default
	  default_group:   'default'			# default
	    groupname1:	   'host_group1_acl'
	    groupname2:	   'host_group2_acl'
	    vname1:	   'host_group3_acl'
	    vname2:	   'host_group4_acl'
	    - 'host_group5_acl'
	    - ''
	  by_ip:	   'host_group6_acl'
	  by_hostname:	   'host_group7_acl'

       Note that the default directory for writing files is not
       /var/lib/rancid so you may wish to set this in "rancid_cvsroot",
       (especially if migrating	from the old "netdisco-rancid-export" script).

       Any values above	that are a host	group ACL will take either a single
       item or a list of network identifiers or	device properties. See the ACL
       control-lists> wiki page	for full details. We advise you	to use the
       "host_groups" setting and then refer to named entries in	that, for

	  coredevices: ''
	  edgedevices: ''
	  grp-nxos:    'os:nx-os'

	    core_devices: 'group:coredevices'
	    edge_devices: 'group:edgedevices'
	    cisco-nx:	  'group:grp-nxos'
	  by_ip:	  'any'

       Do not forget that rancid also needs configuring	when adding a new
       group, such as scheduling the group to run, adding it to	rancid.conf,
       setting up the email config and creating	the repository with

       The location where the rancid configuration (rancid.types.base and
       rancid.types.conf) is installed.	It will	be used	to check the existence
       of device types before exporting	the devices to the rancid
       configuration. If no match is found the device will not be added	to

       The location to write rancid group configuration	files (router.db)
       into. A subdirectory for	each group will	be created.

       This should be the same or greater than the interval between regular
       discover	jobs on	your network. Devices which have not been discovered
       within this time	will be	marked as "down" to rancid.

       The format is any time interval known and understood by PostgreSQL,
       such as at

       Set this	to the delimiter character for your router.db entries if
       needed to be different from the default,	the default is ";".

       Put devices into	this group if they do not match	any other groups

       This dictionary maps rancid group names with configuration which	will
       match devices in	the Netdisco database.

       The left	hand side (key)	should be the rancid group name, the right
       hand side (value) should	be a Netdisco ACL
       control-lists> to select	devices	in the Netdisco	database.

       If the device vendor in Netdisco	is not the same	as the rancid vendor
       script or device	type, configure	a mapping here.

       The left	hand side (key)	should be the rancid device type, the right
       hand side (value) should	be a Netdisco ACL
       control-lists> to select	devices	in the Netdisco	database.

       Note that vendors might have a large array of operating systems which
       require different rancid	modules. Mapping operating systems to rancid
       device types is a good solution to use the correct device type.

	  grp-ciscosb:	 'os:ros'

	    cisco-sb:	 'group:grp-ciscosb'

       Netdisco	ACL
       control-lists> to identify devices that will be excluded	from the
       rancid configuration.

       Netdisco	ACL
       control-lists> to select	devices	which will be written to the rancid
       config as an IP address,	instead	of the DNS FQDN	or SNMP	hostname.

       Netdisco	ACL
       control-lists> to select	devices	which will have	the unqualified
       hostname	written	to the rancid config. This is done simply by stripping
       the "domain_suffix" configuration setting from the device FQDN.

       o   <>

       o   <>

       o   <>

perl v5.32.1		      App::Netdisco::Worker::Plugin::MakeRancidConf(3)


Want to link to this manual page? Use this URL:

home | help