Yep, we have RANCID, but that was precisely the problem - while I can certainly do a config diff and see the changes from baseline at audit time, it is impossible to see who made the changes and also which config change corresponds to which change request...
-- Stefan Fouant Principal Network Engineer NeuStar, Inc. - http://www.neustar.biz GPG Key ID: 0xB5E3803D On Wed, Jul 23, 2008 at 9:32 AM, Jose Madrid <[EMAIL PROTECTED]> wrote: > Going back to Christian's point, Rancid doesn't know who made the > changes and if there are multiple changes between rancid run-times, it > will pick up various changes and not just the one in particular. I > currently use a mixture of rancid and logs from devices to see who > logged in at a time nearest when the change was picked up. This is > less than ideal solution, but all we currently have. _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
