[rancid] Rancid Ignore Devices

[Moorehead, Bryan D [EQ]]

Is it possible to instruct RANCID to ignore certain devices? We have wildcards in our .cloginrc device definitions, and I have a list of devices that for various reasons need to not be queried.


Thanks,
Bryan

[Arnold Nipper]

Post by Moorehead, Bryan D [EQ]
Is it possible to instruct RANCID to ignore certain devices? We have
wildcards in our .cloginrc device definitions, and I have a list of
devices that for various reasons need to not be queried.

.cloginrc tells clogin *how* to log into a device.

*Which* device to walk through your devices is stored in
~rancid/*/router.db.

Either omit them the devices which should be ignored or set their status
to "down".




Arnold

[Andrew Brennan]

Simply leave them out of your router.db file?

Post by Moorehead, Bryan D [EQ]
Is it possible to instruct RANCID to ignore certain devices? We have wildcards in our .cloginrc device definitions, and I have a list of devices that for various reasons need to not be queried.
Thanks,
Bryan

[Moorehead, Bryan D [EQ]]

Got it. I'm very new to RANCID ( if that is not already obvious ) and am trying to get a feel for it.

[Sam Munzani]

Not always the case. Some times you want them in router.db but flag them
to down state because you know the device is going through maintenance
and will not be reachable for some time.

I usually do following
# router.db content
device-x:cisco:up
device-y:cisco:down # this will be excluded from backup.

Hope this helps,
Sam

Post by Andrew Brennan
Simply leave them out of your router.db file?

Post by Moorehead, Bryan D [EQ]
Is it possible to instruct RANCID to ignore certain devices? We have wildcards in our .cloginrc device definitions, and I have a list of devices that for various reasons need to not be queried.
Thanks,
Bryan

_______________________________________________
Rancid-discuss mailing list
http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss

[Gregory W Zill]

And since we distribute e-mails to the RANCID network engineering group,
we add a fourth field, as in

1234-asa:cisco:up
1234-pix:cisco:down:fw upgrade to 1234-asa on 20080524
1234-juniper:netscreen:down:new fw implementation on 20080615

The router.db change will be broadcast to the group once.

Post by Sam Munzani
Some times you want them in router.db but flag them
to down state because you know the device is going through maintenance
and will not be reachable for some time.
I usually do following
# router.db content
device-x:cisco:up
device-y:cisco:down # this will be excluded from backup.