Discovery setting Loadbalancer operational status to 'non-operational'

[Cirrus]

Good afternoon,

We have virtual Citrix NetScaler VPX instances running on SDX Appliances. The VPX instances have been discovered as CIs, however Discovery set the Operational Status field as ‘non-operational’. As a result of this our service mapping is failing. We have to manually change their status to ‘operational’ for service mapping to work, which is not ideal.

The problem we are having is when the NetScalers are re-discovered on the next scheduled run, Discovery sets the status back to ‘non-operational’. Obviously we can put rules in place to stop Discovery overwriting our manual changes, but we feel we shouldnt need to. Has anyone experienced a similar issue discovering loadbalancers, as nothing in the local config suggests that 'status' has been defined.

[Chuck Tomasi]

As with any integration, you want to check what payload is coming back. Remember, Discovery only asks the questions that you prescribe. If you aren't seeing a status in the response, then the probe is likely not asking it. Check to see if there is a way to get the operational status from the VPX instances and add that to your classifier. Once you ask the question, then sensor can be added/modified to react to it and set your operational status field accordingly.

[Chuck Tomasi · Accepted solution]

FYI - A response to this post was featured on the Community Live Stream video. I invite you to watch the episode.

Video: Community Live Stream - 2019-10-14 - Developer Community - ServiceNow Community