Yes, it can be overridden. So people needing the "asa" hack can do it - for you it should be ok now, Adam turned it back to cisco :-)
Tom
On 08/01/2016 18:54, David Wilkinson wrote:
I don't think so, just checked an older standalone rancid install I have . It is running 2.3.8 and doesn't have the "asa" type in the in the vendor list. So it would fail with 2.3 as well.
Maybe it is very old versions of rancid which have an "asa" type?
Is there away in the config file to override it, which would then allow Cisco ASAs to be changed to "asa" for the older/customised Rancid installs?
On 08/01/16 15:52, Tom Laermans wrote:
Might be different rancid v2 (asa) vs v3 (cisco) ?
Do we need 2 mapping tables? We already have a setting for v2 and v3 (for the separator).
Tom
On 2016-01-08 16:51, Adam Armstrong wrote:
Hmm. This is annoying, there are rancid installs which only work with this set to ASA!
I've set it back to cisco, since that was our original setting.
adam.
On 08/01/2016 11:23:54, David Wilkinson observium@noroutetohost.net wrote:
Hi,
We have recently updated our version and the generate rancid script is now using the wrong type for the Cisco ASA devices. The type used for the Cisco ASA should be "cisco", it has recently changed so it sets the type to be "asa" This causes rancid to fail with an unknown type. Can this be corrected?
We are using rancid 3.1. Observium: 0.16.1.7396 (rolling)
Regards
David
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium