Disabled LB pool returns an alert - disabledbyparent

[Tontonitch]

Hello Gerhard,

In the scope of F5 load balancers monitoring, I've discovered a case for which I think the returned status is not the expected one.
Indeed, we can disable

[root@server ~]# /usr/lib64/nagios/plugins/check_nwc_health -V
check_nwc_health $Revision: 8.3.1.1 $ [http://labs.consol.de/nagios/check_nwc_health]
[root@server ~]#

[root@server ~]# /usr/lib64/nagios/plugins/check_nwc_health --community xxx --hostname xxx --mode pool-complections --name /appX/pool_appXY
CRITICAL - pool /appX/pool_appXY is disabledbyparent, avail state is green, active members: 0 of 2, connections: 0, pool /appX/pool_appXY is disabledbyparent, avail state is green, active members: 0 of 2, connections: 0 (not enough active members (0, min is 1)), member /Common/member1:80 has 0 connections (from max 10M), member /Common/member2:80 has 0 connections (from max 10M) | 'member_/Common/member1_80_connections_pct'=0%;85;95;0;100 'member_/Common/member1_80_connections'=0;;;; 'member_/Common/member2_80_connections_pct'=0%;85;95;0;100 'member_/Common/member2_80_connections'=0;;;; 'pool_/appX/pool_appXY_completeness'=0%;51:;26:;0;100 'pool_/appX/pool_appXY_servercurconns'=0;;;;
[root@server ~]#

As you can see, the pool has been disabled by the network team:
pool /appX/pool_appXY is disabledbyparent

So this is an expected situation to have 0 active members for that pool. The expected result would be an OK state.

Some other info below, that could be useful.

[root@server ~]# /usr/lib64/nagios/plugins/check_nwc_health --community xxx --hostname xxx --mode pool-complections --name /appX/pool_appXY -vvv | grep -i disabled
ltmPoolMbrStatusEnabledState: disabled
ltmPoolMemberDisabledParentType: 0
ltmPoolMemberSessionStatus: disabled
ltmPoolMbrStatusDetailReason: Pool member is available, user disabled
ltmPoolMbrStatusEnabledState: disabled
ltmPoolMemberDisabledParentType: 0
ltmPoolMemberSessionStatus: disabled
ltmPoolDisabledParentType: 0
ltmPoolStatusDetailReason: The children pool member(s) might be disabled
ltmPoolStatusEnabledState: disabledbyparent
info: pool /appX/pool_appXY is disabledbyparent, avail state is green, active members: 0 of 2, connections: 0 (not enough active members (0, min is 1))
ltmPoolMbrStatusEnabledState: disabled
ltmPoolMemberDisabledParentType: 0
ltmPoolMemberSessionStatus: disabled
ltmPoolMbrStatusDetailReason: Pool member is available, user disabled
ltmPoolMbrStatusEnabledState: disabled
ltmPoolMemberDisabledParentType: 0
ltmPoolMemberSessionStatus: disabled
CRITICAL - pool /appX/pool_appXY is disabledbyparent, avail state is green, active members: 0 of 2, connections: 0, pool /appX/pool_appXY is disabledbyparent, avail state is green, active members: 0 of 2, connections: 0 (not enough active members (0, min is 1)), member /Common/member1:80 has 0 connections (from max 10M), member /Common/member2:80 has 0 connections (from max 10M)
pool /appX/pool_appXY is disabledbyparent, avail state is green, active members: 0 of 2, connections: 0 (not enough active members (0, min is 1))
[root@server ~]#

BR,
Yannick