Forum Discussion
Native SNI support for Health Monitoring
- Feb 10, 2022
I have tried this in the past on v13.x 🙂 and it showed unexpected behaviours. The in-tmm monitoring was brought up and it caused multiple other pools to go down. Later investigation showed that it consumed huge memory as the version was having a bug. So we turned it off and sticked back to external monitor.
Also to note, if once upgrades from v11 to v13, the upgry process by default appends a SSL profile to the monitor. So need to make sure they remove those profiles or add right profile before turning on in-tmm monitoring.
I'm sure with the latest bug fixes, it should be stable, make sure your infra is on that version. Don't start off with the production and later have a face palm 😉
- Feb 14, 2022
Hi ErikM,
On my part, I use In-TMM monitoring on a version v14.x to be able to use Authenticate Name option on Server SSL profile to perform a CN check of the backend server certificates
No problem for the past 2 years, it's stable and does the job well 🙂
Check ☑️ and thanks!
But actually the thing i'm curious to find out is what your experiences are. In our case it would mean a conversion from our installed base of HM's towards something that is very sparsly documented. And that's a real jump into deep water in a production environment. One thing that is not documented for instance is what kind of monitors are actually supported. And how will existing HM's converse -if even- when in-TMM is the chosen way.
Thanks,
Erik
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