Forum Discussion
Log: [api-status-warning] ltm/monitor/https, properties : deprecated : cipherlist, compatibility
After Upgrading v12 to v13 we see api-status-warning logs. Obviously this is just a cosmetic issue.
the logs are generated by the following Monitor configuration:
modify https monitor_name {
adaptive disabled
cipherlist DEFAULT
compatibility enabled
destination *:*
time-until-up 0
.......
}
is there an other way to eliminate the "compatibility enabled" than modifying bigip.conf and reloading the configuration or to re-create each Monitor without this line?
I tried:
(tmos)# edit /ltm monitor https monitor_name
(tmos)# modify /ltm monitor https monitor_name
Thanks for your help!
- Nathan_F__F5_
Employee
Hi rolf,
If you want to completely remove them then I believe the only option is to delete those them via bigip.conf as you mentioned. That said, I created a new HTTPS monitor and then reviewed the properties of it via CLI and found that by default both of them are simply set to "none" as seen in the snippet below.
root@(v13A)(cfg-sync Standalone)(Active)(/Common)(tmos)# list ltm monitor https https_test all-properties
ltm monitor https https_test {
adaptive disabled
adaptive-divergence-type relative
adaptive-divergence-value 25
adaptive-limit 200
adaptive-sampling-timespan 300
app-service none
cert none
cipherlist none
compatibility none
defaults-from https
description none
destination *:*
interval 5
ip-dscp 0
key none
manual-resume disabled
partition Common
password none
recv none
recv-disable none
reverse disabled
send "GET /\r\n"
With that in mind, it looks like neither of them can be modified via tmsh due to being deprecated. I believe that this means the only way to get rid of them is to either delete them from the bigip.conf as you previously mentioned, or edit bigip.conf and change them both the "none". It's also possible that if you delete them that they might automatically be recreated with the default values of "none".
I hope this helps to answer your question.
-Nathan F
- rolf
Cirrus
Hi Nathan,
I was not aware about the compatibility none attribute. I think this will do the job.
Thanks a lot,
Rolf
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com