Thank you for your paticence, we have some update for you.
First of all, K30252226 information is when we operate via Configuration utility not tmsh, threfore we fixed and update title and some information.
Also we put info the logs when manually enabled in Additional Information section.
Regarding audit log, you can see its state with these combinations.
-- Enabled "pool_member_new_session_enable 2 pool_member_monitor_state 3".
-- Disabled "pool_member_new_session_enable 1 pool_member_monitor_state 3".
-- Forced Offline "pool_member_new_session_enable 1 pool_member_monitor_state 20".
We can see those numbers in F5-BIGIP-LOCAL-MIB file.
K13322: Overview of BIG-IP MIB files
-- pool_member_new_session_enable:
ltmPoolMemberNewSessionEnable OBJECT-TYPE
SYNTAX INTEGER {
user-disabled(1), <----------- !!!
user-enabled(2), <----------- !!!
monitor-enabled(3),
monitor-disabled(4)
}
-- pool_member_monitor_state:
ltmPoolMemberMonitorState OBJECT-TYPE
SYNTAX INTEGER {
unchecked(0),
checking(1),
inband(2),
forced-up(3), <----------- !!!
up(4),
down(19),
forced-down(20), <----------- !!!
irule-down(22),
inband-down(23),
down-manual-resume(24),
disabled(25)
}
Changes via Configuration utility we can also see in TMSH command results. For example, "pool_member_new_session_enable" is session and "pool_member_monitor_state" is state
CloudDocs Home > F5 TMSH Reference > ltm pool
-- Disabled:
# tmsh
(tmos)# list ltm pool pool_example pool_example members { 192.168.0.59:http { session state } }
ltm pool pool_example {
members {
192.168.0.59:http {
session user-disabled <----------- !!!
state up
}
}
}
-- Forced Offline:
# tmsh
(tmos)# list ltm pool pool_example pool_example members { 192.168.0.59:http { session state } }
ltm pool pool_example {
members {
192.168.0.59:http {
session user-disabled <----------- !!!
state user-down <----------- !!!
}
}
}
Regarding more comprehensive list, we are checking. We might send a message you directory.
Cirrus
