Implementing SSL Orchestrator - Management with BIG-IQ
Introduction This article is part of a series on implementing BIG-IP SSL Orchestrator. It includes high availability and central management with BIG-IQ. Implementing SSL/TLS Decryption is not a tri...
Published Jan 21, 2020
Version 1.0KevinGallaugher
Employee
Joined November 15, 2019
KevinGallaugher
Employee
Joined November 15, 2019
dragonflymr
Jan 28, 2020Cirrostratus
Hi,
I am a bit lost at the step starting with "When complete click the link to Complete import tasks."
- SSL Orchestrator is not selected for import for first node i5800-11.pmelab.internal, but is selected for Import on second node - is that on purpose - so SSLO should be imported only on one node?
- What is step "For the Location choose to Create New or Use Existing. In this example we Use Existing Location, “pmelab”. Click Deploy then Yes." required for? It's described next to Importing SSLO service. So I would assume (like with LTM) that in this step configuration already existing on BIG-IP node is imported into BIG-IQ, but it looks like SSLO config is pushed form BIG-IQ to BIG-IP node...quite confused :-(
Last but not least, BIG-IQ support for SSLO is a bit lagging in versions. As far as I understand from Interoperability Matrix for F5 SSL Orchestrator with BIG-IP and BIG-IQ highest supported version is 5.5, 5.6 (14.1.2.1). When support for 15.1.x is expected?