![]() ![]() Workaround: Follow these steps to display the IP offset values: ![]() This issue is fixed, and now all the available offset values are displayed correctly. Previously, while creating a new L2 service, the desired IP offset value was not displayed, impacting the generation of internal IPv4 and IPv6 addresses. However, the BIG-IP admin still has the ability to enable the pool member, which will make the SSL Orchestrator application read-only. So, by default the SSLO app is no longer read-only. When BIG-IQ is connected to BIG-IP the SSL Orchestrator app will create the LTM pool named sslo_bigiqMonitor, but the pool member added will be 'Forced Offline'. SSL Orchestrator no longer incorrectly locks the UI in read-only mode upon discovery by BIG-IQ. That is, when a BIG-IQ discovered a BIG-IP running SSL Orchestrator, the BIG-IP would lock the SSL Orchestrator UI in read-only mode.įix: This issue is fixed. Previously, BIG-IQ could not manage SSL Orchestrator versions 9.0 and above. Workaround: Exit the configuration and try again. DEPLOYMENT_NAME will be replaced by the name of the configuration that is getting upgraded/modified.įixed the issue where there was an inactive Deploy button when modifying the deployed service. ![]() Note: The DEPLOYMENT_TYPE will be replaced by the actual deployment type such as, Topology, service, policy, SSl Settings, and so on. Adding a new instance, or modifying or deleting an existing instance, is not allowed." Add new, modify and delete of existing deployed instances are not allowed."įix: Modified the code to include the following message: Previously, during SSL Orchestrator RPM Upgrade the following message appeared which was not intuitive: ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |