Re: [rancid] Fortigate additional tweaks and device filters

2018-08-03 Thread Nick Nauwelaerts
Subject: Re: [rancid] Fortigate additional tweaks and device filters Thu, Aug 02, 2018 at 09:25:30AM -0500, Chris Wopat: > > Wed, Aug 01, 2018 at 08:37:03AM +, Nick Nauwelaerts: > >> hm, > >> i actually like to have those versions in the output. if something breaks >

Re: [rancid] Fortigate additional tweaks and device filters

2018-08-01 Thread Nick Nauwelaerts
hm, i actually like to have those versions in the output. if something breaks my first reaction tends to be: "what changed?", and rancid is usually the first place i check. would it be an option to control this with FILTER_OSC , even though its not quite it's intended application? thx //

Re: [rancid] Fortigate additional tweaks and device filters

2018-08-05 Thread Nick Nauwelaerts
i wouldnt mind testing at all, atm running a 800c cluster on 5.2, and expecting a 500e cluster with 5.6 by the end of the month. // nick > On 03 Aug 2018, at 22:08, heasley wrote: > > Fri, Aug 03, 2018 at 03:34:05PM +0000, Nick Nauwelaerts: >> i guess the fortinet module

Re: [rancid] Fortigate additional tweaks and device filters

2018-08-01 Thread Nick Nauwelaerts
mailto:h...@shrubbery.net] Sent: Wednesday, August 1, 2018 17:35 To: Nick Nauwelaerts Cc: Doug Hughes ; rancid-discuss@shrubbery.net Subject: Re: [rancid] Fortigate additional tweaks and device filters Wed, Aug 01, 2018 at 08:37:03AM +, Nick Nauwelaerts: > hm, > i actually like to h

Re: [rancid] error after migrating to new server

2018-10-16 Thread Nick Nauwelaerts
also, it seems you installed it under /usr/bin, best practices for rancid & package management in general is not do this. perhaps install it under the rancid user's homedir & make sure $HOME/bin is in your $PATH first. second option is that you used a vendor provided rancid package instead of

Re: [rancid] 3.9 release?

2019-01-08 Thread Nick Nauwelaerts
k here. // nick -Original Message- From: heasley [mailto:h...@shrubbery.net] Sent: Wednesday, January 9, 2019 01:11 To: Nick Nauwelaerts Cc: rancid-discuss@shrubbery.net Subject: Re: [rancid] 3.9 release? Tue, Jan 08, 2019 at 10:20:11PM +, Nick Nauwelaerts: > no chance then for aerohive suppo

Re: [rancid] aerohive/hiveos support

2019-01-11 Thread Nick Nauwelaerts
> -Original Message- > From: heasley [mailto:h...@shrubbery.net] > Sent: Wednesday, January 9, 2019 21:54 > To: Nick Nauwelaerts > Cc: rancid-discuss@shrubbery.net > Subject: Re: [rancid] aerohive/hiveos support > > Wed, Dec 19, 2018 at 09:23:57PM +, Nic

[rancid] aerohive/hiveos support

2018-12-19 Thread Nick Nauwelaerts
(also included: removal of fortinet/fnrancid references since it's now a module & a few minor nitpicks) support for aerohive/hiveos access points: login script ahlogin: * originally by erik muller: https://github.com/ermuller/rancid-stuff. * should be up to date with the latest changes of svn

Re: [rancid] Extreme 200-series switches

2019-03-26 Thread Nick Nauwelaerts
heya, while i don't have extreme devices, the code seems to live in lib/exos.pm.in. i would guess temperature & diskspace and such could perhaps be gated with the FILTER_OSC setting (see man rancid.conf), fortigate.pm.in has some examples which can get you started. rancid.pm.in has some helper

Re: [rancid] [SPAM?] Cisco NX "chatty" with Power info

2019-03-08 Thread Nick Nauwelaerts
what version of rancid & nx-os are you running? i notice you only have 1 column less as me, you seem to miss "actual output". // nick From: Rancid-discuss [mailto:rancid-discuss-boun...@shrubbery.net] On Behalf Of FF Sent: Friday, March 8, 2019 18:05 To: rancid-discuss@shrubbery.net

Re: [rancid] Fortigate VDOMs

2019-03-08 Thread Nick Nauwelaerts
what version of fortios was this tested on, since on my 5.6.8 both fortigate & fortigate-full pull vdom configs. // nick From: Rancid-discuss [mailto:rancid-discuss-boun...@shrubbery.net] On Behalf Of Linux Threads Sent: Friday, March 8, 2019 12:44 To: rancid-discuss@shrubbery.net Subject:

Re: [rancid] Unable to figure out "end of run not found"

2019-06-19 Thread Nick Nauwelaerts
iirc: ; is to seperate commands and wil execute the whole command string without checking the return value of the previous command && will do the same, but if previous command returns not null (you can check the return code of the previous command with "echo $?") it will end the command list.