Forum Discussion
protocol profiles
- Apr 16, 2021
As with most custom profiles, they are based on a Parent Profile. In other words, the custom profile is a child of the parent. As such, unless a setting is customized in the child by, as you indicated, ticking the custom box beside it, its value will be inherited from its parent profile. So, if the setting changes in the parent profile, the child will also inherit that change.
When you tick a setting in a child profile, you effectively disconnect that setting from the parent. You can leave the setting in the child as-is or change it to meet your application delivery needs. Once ticked, if the setting in the parent profile changes, the child is not affected.
This concept of inheritance applies to all BIG-IP LTM profiles, including TCP protocol profiles.
As with most custom profiles, they are based on a Parent Profile. In other words, the custom profile is a child of the parent. As such, unless a setting is customized in the child by, as you indicated, ticking the custom box beside it, its value will be inherited from its parent profile. So, if the setting changes in the parent profile, the child will also inherit that change.
When you tick a setting in a child profile, you effectively disconnect that setting from the parent. You can leave the setting in the child as-is or change it to meet your application delivery needs. Once ticked, if the setting in the parent profile changes, the child is not affected.
This concept of inheritance applies to all BIG-IP LTM profiles, including TCP protocol profiles.
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