![F5 Herculon SSL Orchestrator Скачать руководство пользователя страница 39](http://html.mh-extra.com/html/f5/herculon-ssl-orchestrator/herculon-ssl-orchestrator_setup_535213039.webp)
Setting up Herculon SSL Orchestrator in a High
Availability Environment
Overview: Setting up Herculon SSL Orchestrator in a high availability
environment
This section describes how to deploy F5
®
Herculon
™
SSL Orchestrator
™
high availability (HA). Herculon
SSL Orchestrator HA configuration and deployment ensures a decrease in downtime and eliminates
single points of failure. The deployment of Herculon SSL Orchestrator’s HA works with the BIG-
IP
®
device groups support to sync the Herculon SSL Orchestrator specific configuration items, and is
transparent to the user.
The deployment occurs after completing a configuration change and selecting Deploy. The deployment
request is first routed to one of the devices in the HA device group. This first device configures the
device where the request is received. After successful deployment on that device, the request is repeated
on other BIG-IP devices.
With Herculon SSL Orchestrator installed onto a dedicated system with failover, it automatically takes
over in case of system failure. Data is synchronized between the two systems, ensuring high availability
and consistent protection.
Note: Herculon SSL Orchestrator high availability deployment is supported for use only with the
Herculon SSL Orchestrator configuration utility versions 2.1 and later.
Assumptions and dependencies
To ensure that your Herculon SSL Orchestrator HA deployment succeeds, it is critical that you closely
review and follow all assumptions and dependencies.
• HA Setup: BIG-IP HA (CMI) must be set to Active-Standby mode with network failover. See the
BIG-IP Device Service Clustering: Administration
document for detailed information on Active-
Standby HA mode.
• HA Setup: If the deployed device group is not properly synced or RPM packages are not properly
syncing, make sure your HA self IP (for example,
ha_self
)
Port Lockdown
setting is not set to
Allow None
. On the Main tab, click
Network
>
Self IPs
and click your
ha_self
. If
Port Lockdown
is set to
Allow Custom
, check that the HA network port 443 is open on self IP.
• BIG-IP HA Devices: Only manual sync is supported.
• BIG-IP HA Devices: Devices in each BIG-IP HA pair must be the same model and run the same
version of TMOS
®
(including any hotfixes). Except for the management interface, you must configure
both devices to use the same arrangement of network interfaces, trunks, VLANs, self IPs (address and
subnet mask), and routes. For example, if one BIG-IP device is connected to a specific VLAN/subnet
using interface 1.1, the other BIG-IP device must also be connected to that VLAN/subnet using
interface 1.1. If the BIG-IP device configurations do not match, this implementation will not deploy
correctly, and HA failover will not work.
• User Experience: Deployment must be initiated from the active HA BIG-IP device.
• User Experience: If the environment is changed from non-HA to HA, or from HA to non-HA, the
application must be redeployed.
• User Experience: You can refresh the SSL Configuration screen (
SSL Orchestrator
>
Configuration
) for each peer device in order to see all modified changes.
Содержание Herculon SSL Orchestrator
Страница 1: ...F5 Herculon SSL Orchestrator Setup Version 13 1 3 0 ...
Страница 2: ......
Страница 6: ...What is F5 Herculon SSL Orchestrator 6 ...
Страница 26: ...Setting Up a Basic Configuration 26 ...
Страница 38: ...Importing and Exporting Configurations for Deployment 38 ...
Страница 54: ...Using Herculon SSL Orchestrator Analytics 54 ...