The main motivation for this enhancement is the fact that customer usually do not need to keep binary configuration downloaded and saved every day - speaking about binary configurations, where it is very problematic or even impossible to determine whether something relevant was changed or not.
The good but not only one example is driver for Aruba ClearPass Policy Manager, where the binary configuration is different by every run, but the change is usually just in generated time where the binary configuration was generated - the time is incorporated in the files that are part of the binary configuration generated by the device itself, so we can say yes there was a change, but in fact nothing important or relevant was changed - app data are the same, device configuration is the same.
Such behavior leads to generating and downloading the binary configuration by every take snapshot run, which makes the take snapshot task running much longer and also the NA DB is growing by saving big binary data - one ClearPass binary configuration may take 20 - 100MB. Our current setting is keeping the device configuration for 365 days and running the daily take snapshot every day, so in worst case this binary configuration for one device may occupy 100MB x 365 ~= 36,5 GB space in the NA DB.
To mitigate such behavior we would have one good idea that would be worth implementing.
As example I would give you some options, we already have for F5_JS driver:
<!-- F5 binary config size upper limit in KB - request from Vadim Tugai -->
As you can see, the first option is the threshold for the binary config – if it exceeds then binary config will not be downloaded, the second option is for getting the binary meaning the binary config will be downloaded with every take snapshot even when “retrieve binary config” check box is unchecked. And my idea here was make another option something like this:
<option name="Drivers/F5_JS/schedulerbinarycron">* * * * 3</option>
So this first option will enable or disable the schedulerbinary for the specific driver, by default it will be disabled, second option will work with cron format – above example means retrieve the binary config with take snapshot every Wednesday (any take snapshot task that will be scheduled on Wednesday will force the binary config retrieving).
I think that this idea is not so complicated for implementing – as you can see, we already have some options for specific driver in place, so I would expect it would be feasible do it also for ClearPass driver, test it and later use it for other drivers as well 😊
As the workaround we could schedule the separate take snapshot task with enabling the binary config for every Wednesday. I understand that for one specific device or devices we can try this workaround. But this is definitely not our way we want to go, as it could end in tons of specific tasks for specific devices, for specific customer (we have multiple customers on one NA server). We went to keep it simple having 1 take snapshot task for all devices for all customers and rather configure the binary config scheduling options either as custom variable for device access settings or as rcx option in adjustable_options.rcx file for specific driver.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.