Unsupported DCIs change to disabled

Started by Andrew, October 20, 2016, 07:21:17 PM

Previous topic - Next topic

Andrew

I have a situation where a DCI  becomes disabled on many nodes due to an unsupported value, because I am pushing out an updated script.  Up to this point, I have been using the management console to re-enable the DCI on each node, which resolves the issue, but is very time consuming because I have to drill down into each node.  Is there a way to have a node recover from an unsupported value on it's own (automatically re-enable the DCI), or be able to select many nodes at one time and re-enable the DCI?  Thanks, Andrew

Victor Kirhenshtein

Hi,

actually server will periodically (every 10th poll) check unsupported DCIs and re-activate them if agent responds. You can also write nxshell script to walk all nodes and re-activate all unsupported DCIs.

Best regards,
Victor