Operational_Status in F5 Load Balancer Discovery

[William Mo]

When I am doing the F5 Load Balancer discovery, I  found that the device keep change to Non-Operational for operational_status field. This is very weird to me. So I took a deep look, and figured out something as below.

In the F5 Load Balancer pattern, step "4. Get Failure Status ID" reads the OID "iso.org.dod.internet.private.enterprises.f5.bigipTrafficMgmt.bigipSystem.sysCM.sysCmFailoverStatus.sysCmFailoverStatusId". and for this FailoverStatus, there is a F5 document to describe the meaning.

https://support.f5.com/csp/article/K14399

In my environment, the status is 3, standby.  and then in Pattern step "7. Set Failover status"

EVAL(javascript:var rtrn = '';if (${failureStatusId}=='4' || ${failureStatusIdOld}=='3') {    rtrn='1';}else {rtrn='2';})

If the status is not 4-active, all will be set to non-operational for operational_status.

This is not really make sense to me. Even it is standby, but it should be as operational status, or DR standby. 

[Community Alums]

@William Mo have you found anything new since your original post? i am particularly interested in how Service Mapping might be handling the Failover Status / operational_status?

[William Mo]

thanks for checking in. but there is no update

[theroz]

Hi - 

I am experiencing the same issue with NetScaler load balancer pattern discovery. My secondary load balancer is being set to "Non-Operational" (Failover Status=2). This is expected behavior according to ServiceNow support KB0681774.

The question I can't figure is the reasoning for this as both my primary and secondary load balancer CIs are needed for change and ITSM processes. 

Does anyone have an idea as to the logic behind this?