Forum Discussion
nitass
May 27, 2013Employee
i understand it is by design.
sol6514: BIG-IP may not reflect the expected status for virtual servers that use iRules or HTTP classes to select a pool
http://support.f5.com/kb/en-us/solutions/public/6000/500/sol6514.html?sr=18068062
[root@ve10:Active] config b virtual bar list
virtual bar {
snat automap
pool foo
destination 172.28.19.252:80
ip protocol 6
}
[root@ve10:Active] config b pool foo|grep -i pool\ member
+-> POOL MEMBER foo/200.200.200.101:80 inactive,down
[root@ve10:Active] config snmpwalk -v 2c -c public localhost F5-BIGIP-LOCAL-MIB::ltmVsStatusAvailState.\"bar\"
F5-BIGIP-LOCAL-MIB::ltmVsStatusAvailState."bar" = INTEGER: red(3)
[root@ve10:Active] config
[root@ve10:Active] config
[root@ve10:Active] config
[root@ve10:Active] config b rule myrule list
rule myrule {
when CLIENT_ACCEPTED {
pool foo2
}
}
[root@ve10:Active] config b virtual bar rule myrule
[root@ve10:Active] config b pool foo2|grep -i pool\ member
+-> POOL MEMBER foo2/200.200.200.111:80 active,up
[root@ve10:Active] config snmpwalk -v 2c -c public localhost F5-BIGIP-LOCAL-MIB::ltmVsStatusAvailState.\"bar\"
F5-BIGIP-LOCAL-MIB::ltmVsStatusAvailState."bar" = INTEGER: green(1)