How to configure persistent static route on cRIO-9068

[BradM]

Reddata,

If you've not done system configuration through MAX or SysAPI calls, I can't think of any other mechanism that would cause customizations to the network interface to be lost. Basically, if you have a short list of operations that you did (outside of normal VI app development and deployment, unless those apps used SysAPI calls), that may help jog my memory or provide clues.

[Reddata]

I spoke too quickly: In my changelog I found a deployment of NI TimeSync to all three chassis. If this is the issue, one of the three chassis surviving the update seems odd. Would deploying NI TimeSync revert ifplugd.script?

[BradM]

I have a sneaking suspicion that the CDF files (metadata for installable packages through MAX) for the two different target types (x64 vs. Zynq) is to blame for the differing behavior.

As such, I can absolutely believe that installing something that works with networking stuff (as TimeSync will) could impact interface customizations.