Possible New Automation Script on Indeni: "Cluster members have mismatching Kernel builds"

Possible New Automation Script on Indeni: "Cluster members have mismatching Kernel builds"
0

We have had reported incidents where our automated script that captures the Hotfix take for each cluster member captures Takes that are old on the system. So if the device had R77.30 HFA 70 and was recently upgraded to HFA 216, Indeni would collect HFA 70 incorrectly.


I did some further digging and identified how this script can be improved on. The problem is that the script actually does not work on certain builds!


To explain this: the command "installed_jumbo_take -n" only works on more recent builds. What I discovered is that some of the clustered CP devices in our lab do not have matching builds. What were the symptoms? Indeni simply failed to trigger the alert because the secondary/passive pair did not support the command with its older build.


This brings up an interesting concern, should an end user be made aware that their cluster members have mismatching software builds? Should we also inform the user that Indeni is hindered by our data collection because it assumes that it can run the same command across a clustered pair?

The command "installed_jumbo_take -n" only works for newer takes of jumbo hotfix, but for older versions of jumbo, or older versions of check point we run all the other possible commands to get the jumbo take as well. Which do you mean does not work?