F5 Logo MyF5
Search
  1. MyF5 Home
  2. F5 Guided Configuration for SSL Orchestrator: Setup 17.0.0.1-10.1
  3. Setting up F5 Guided Configuration for SSL Orchestrator in High Availability
Manual Chapter : Setting up F5 Guided Configuration for SSL Orchestrator in High Availability

Applies To:

Show Versions Show Versions

F5 SSL Orchestrator

  • 17.0.0
Manual Chapter

Setting up F5 Guided Configuration for SSL Orchestrator in High Availability

Overview: Setting up F5 Guided Configuration for SSL Orchestrator in high availability

This section describes how to deploy F5 SSL Orchestrator high availability (HA). SSL Orchestrator HA configuration and deployment ensures a decrease in downtime and eliminates single points of failure. The deployment of SSL Orchestrator’s HA works with the BIG-IP device groups support to sync the 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 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.
SSL Orchestrator high availability deployment is supported for use only with SSL Orchestrator versions 2.1 and later.

Set up BIG-IP ISO with F5 Guided Configuration for SSL Orchestrator in high availability

To ensure that your F5 SSL Orchestrator high availability (HA) deployment succeeds, it is critical that you closely follow each deployment step, as well as the assumptions and dependencies, for both devices in the device group. In addition, you should adhere to all prerequisites. If the systems in the device group are not configured consistently, the deployment synchronization process may suffer errors or fail. You would require two devices that are a part of the sync-failover group. The Port Lockdown setting should be either Allow All, Allow Default, or Allow Custom.
To install and setup the BIG-IP ISO with SSL Orchestrator Guided Configuration in HA, you will perform the following tasks to ensure your HA deployment succeeds:
  • Configure the network for HA.
    • Configure the ConfigSync and Failover IP address.
    • Add a device to the local trust domain.
    • Create a Sync-Failover device group.
    A Sync-Only device group is not supported.
  • Synchronize the device group.
  • Set up a basic configuration for deployment.

Assumptions and dependencies

To ensure that your 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: Manual and auto 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: 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 Interception Rules screen (
    SSL Orchestrator
    Interception Rules
    ) for each peer device in order to see all modified changes.

Prerequisites

Before configuring the network for HA, make sure these prerequisites are in place:
  • The information used to configure your devices is identical on both devices. Without identical information on both devices, the HA deployment process can suffer from errors or fail.
  • The latest version of BIG-IP SSL Orchestrator is successfully installed on both devices.
  • Successfully set up an HA ConfigSync device group prior to starting the configuration. See the section
    Configuring the network for high availability
     and its subsections to ensure that this prerequisite has been properly completed. For additional information, refer to the
    BIG-IP Device Service Clustering: Administration
     document, section
    Managing Configuration Synchronization
    .
  • SSL Orchestrator is installed with the appropriate license information using the SSL Orchestrator Setup Utility (or the CLI) and made sure your device setup information is identical on both devices:
    • While using the SSL Orchestrator Setup Utility, you have noted the details used for NTP and DNS setup and made sure they will be identical on both devices. To verify duplication, on the Main tab, click
      System
      Configuration
      Device
      and select
      NTP
       or
      DNS
      .
    • Ensure that any certificates used in the configuration are copied to all devices.
    • Ensure that information is identical on all devices. This information should include any of the following that are needed:
      • Client network
      • External network
      • Decrypt zone network
      • Decrypt zone control network
      • Networks providing access to ICAP devices and Receive-only devices
    • Ensure that the log publishers are configured and named the same.
    • Ensure that all systems use the same interfaces for any services. (If interface 1.1 is used to send traffic to an inline Layer 2 device on system A, then interface 1.1 must also be used on systems B, C, and D.)
    Do not attempt to duplicate the configuration by saving and restoring a user configuration set (UCS) file from one machine to the other, or any other cloning approach. There are several IDs that must be unique that will also be duplicated, causing additional problems.

Configuring the network for high availability

You can specify the settings for VLAN HA and self IP addresses on the active device to configure your network for high availability. If needed, you can configure all devices involved in the high availability group for HA.
This network connects the various devices and must be a common Layer-2 network between all devices.
  1. On the Main tab, click
    Network
    VLANs
    .
    The VLAN List screen opens.
  2. Click
    Create
    .
    A New VLAN screen opens where you can configure your new VLAN.
  3. In the
    Name
     field, type the name (for example,
    ha_vlan
    ).
  4. For the
    Interfaces
     setting:
    1. From the
      Interface
       list, select an interface number.
    2. From the
      Tagging
       list, select tagging as desired for your network.
    3. Click
      Add
      .
      The interface you selected appears in the
      Interfaces
       list as a tagged service.
  5. Click
    Finished
    .
    Next to the F5 logo, your device status appears showing
    ONLINE (ACTIVE)
     and
    Standalone
     with green indicators showing their status as up and running.
  6. On the Main tab, click
    Network
    Self IPs
    .
    The Self IP List screen opens.
  7. Click
    Create
    .
    A New Self IP screen opens where you can configure your new self IP.
  8. In the
    Name
     field, type the self IP name (for example,
    ha_self
    ).
  9. In the
    IP Address
     field, type the IP address for the device.
  10. In the
    Netmask
     field, type the netmask for the device.
  11. From the
    VLAN/Tunnel
     list, select the VLAN name (
    ha_vlan
    ).
  12. Click
    Finished
    .

Configuring ConfigSync and failover IP addresses

Before creating the device group, you should configure the configuration synchronization (ConfigSync) and Failover IP addresses for each BIG-IP system in the device group. The ConfigSync address is the IP address that the system uses when synchronizing configuration with peer devices, and the failover address is the IP address that the system uses for network failover.
  1. On the Main tab, click
    Device Management
    Devices
    .
    The Devices List screen opens.
  2. Click your device in the device list.
    The properties screen for the device opens.
  3. Click
    ConfigSync
    .
    The screen shows the ConfigSync Configuration area, with the local address of the device.
  4. From the
    Local Address
     list, select the VLAN address (
    ha_vlan
    ).
  5. Click
    Update
    .
  6. Click
    Failover Network
    , and then click
    Add
    .
    The New Failover Unicast Address screen opens.
  7. In the
    Address
     field, make sure that the VLAN address (
    ha_vlan
    ) is present.
  8. Click
    Repeat
    .
  9. After the screen refreshes, from the
    Address
     list, select the Management Address.
    Connection Mirroring is not supported.
  10. Click
    Finished
    .
    The Failover Unicast Configuration area lists both the VLAN HA (
    ha_vlan
    ) and Management Address devices.

Adding a device to local trust domain

Any BIG-IP devices that you intend to add to a device group must first be members of the same local trust domain. When a BIG-IP device joins the local trust domain, it establishes a trust relationship with peer BIG-IP devices that are members of the same trust domain. For example, if you are creating a device group with two members, you must log in to one of the devices and join the other device to that system's local trust domain. The devices can then exchange their device properties and device connectivity information.
  1. On the Main tab, click
    Device Management
    Device Trust
    .
    The Device Trust screen opens.
  2. On the menu bar, click
    Device Trust Members
     to view peer and subordinate device settings.
    The Device Trust Members screen opens.
  3. Click
    Add
    .
    The Device Trust screen opens, showing Retrieve Device Credentials (Step 1 of 3).
  4. From the
    Device Type
     list, select
    Peer
    .
  5. In the
    Device IP Address
     field, type the IP address of your device.
  6. Click
    Retrieve Device Information
    .
    The screen shows Verify Device Certificates (Step 2 of 3).
  7. Click
    Device Certificate Matches
    .
    The screen shows Add Device (Step 3 of 3).
  8. In the
    Name
     field, type the name of the device you are adding.
  9. Click
    Add Device
    .
    At the upper right, next to the F5 logo, the status of your device should show
    ONLINE (ACTIVE)
     and
    Connected
    , with a green indicator next to them showing its active and connected status.

Creating a sync-failover device group

For an HA configuration, you need to establish failover capability between two or more BIG-IP devices. Then, if an active device in a sync-failover device group becomes unavailable, the configuration objects fail over to another member of the device group, and traffic processing is unaffected. You perform this task on any one of the authority devices within the local trust domain.
A Sync-Only device group is not supported.
  1. On the Main tab, click
    Device Management
    Device Groups
    .
    The Device Group List screen opens.
  2. Click
    Create
    .
    The New Device Group screen opens.
  3. In the General Properties area, name your new device group and select the group type.
    1. In the
      Name
       field, type the name of your device group.
    2. From the
      Group Type
       list, select
      Sync-Failover
      .
  4. For the
    Configuration
     setting, retain the
    Basic
     configuration type, and then select members and define the sync type.
    1. In the
      Members
       setting, select available devices from the
      Available
       list and add them to the
      Includes
       list.
    2. From the
      Sync Type
       list, select
      Manual with Incremental Sync
      .
  5. Click
    Finished
    .
The Device Groups list screen opens, listing your new device group. The ConfigSync Status column will indicate
waiting Initial Sync
.

Synchronizing the device group

For an HA configuration, you need to synchronize the BIG-IP® configuration data from the local device to the devices in the device group. This synchronization ensures that devices in the device group operate properly. When synchronizing self IP addresses, the BIG-IP system synchronizes floating self IP addresses only.
  1. Next to the F5 logo, click
    Awaiting Initial Sync
    .
    On the Main tab, you can also click
    Device Management
    Overview
    .
    The Device Management Overview screen opens, showing your Device Groups.
  2. In the Sync Issues area, select
    ha
     to expand the Devices and Sync Options areas of the screen.
  3. In the Devices area, select the device showing
    Changes Pending
    .
  4. In the Sync Options area, select
    Push the selected device configuration to the group
    .
  5. Click
    Sync
    .
You have now completed your F5 SSL Orchestrator HA deployment. You can now navigate to SSL Orchestrator configuration menu. If the RPM is not yet installed, it will auto-install the on-box RPM. Once the RPM is installed, you can proceed in setting up your SSL Orchestrator configuration for deployment.

Overview: Upgrading BIG-IP ISO with F5 Guided Configuration for SSL Orchestrator in high availability

Refer to the Update or Upgrade the F5 SSL Orchestrator chapter in the
BIG-IP update and upgrade
 guide for detailed steps on installing and upgrading to the newest version of SSL Orchestrator in high availability. F5 recommends you follow the procedures that match your current version details when upgrading to the newest version of SSL Orchestrator:

Upgrade BIG-IP ISO to a major or point release version with F5 Guided Configuration for SSL Orchestrator in high availability

Perform the following task to upgrade your BIG-IP ISO to a major, or point, release version with SSL Orchestrator in high availability (HA). Make sure you review all Assumptions and dependencies and verify all Prerequisites prior to starting the upgrade.
During the SSL Orchestrator RPM upgrade, use the message's table for explanations that may appear during the process and provide insight on the upgrade or issues that may need to be resolved. Make sure you review all Assumptions and dependencies and verify all Prerequisites prior to starting the upgrade.

Upgrading BIG-IP ISO to a major or point release version with F5 Guided Configuration for SSL Orchestrator in high availability

Verify all Prerequisites before starting the upgrade
  1. If your HA device pair are not in sync, perform a manual configuration sync and take a UCS backup on to both devices.
  2. Download the target ISO from https://downloads.f5.com/esd/product.jsp?sw=BIG-IP&pro=big-ip_v17.x and select 17.0.0 from the list to see all the available downloads for the
    17.0.0
     version of BIG-IP.
  3. To upload the new ISO on both devices, perform the following steps (this process can be initiated on both devices in parallel and in any sequence):
    1. Using the management IP, on the Main tab, click
      System
      Software Management
      Image List
      and click
      Import
      .
    2. Click
      Choose File
       and select the newly downloaded ISO and click
      Import
      .
  4. Update the standby box:
  5. Perform the below steps to install the new ISO:
    1. On the Main tab, click
      System
      Software Management
      Image List
      .
    2. Select the check box next to the software image to be installed and click
      Install
      .
      Do not perform any configuration changes until the image installation is complete. This screen will continue to refresh to display the install status.
  6. After the image installation successfully completes, perform the following steps to boot into the new partition:
    1. On the Main tab, click
      System
      Software Management
      Boot Locations
      .
    2. Click on the
      Boot Location
       where the new software image is installed. The General Properties screen appears.
    3. Click
      Activate
       and
      OK
       on the confirmation dialog and wait until the device is fully booted into the new partition.
  7. After the standby device successfully boots, verify that the software upgrade was successful by checking the logs (restnoded, restjavad, ltm) for errors.
    Do not click on any tab or link on the SSL Orchestrator menu, submenu, or screen during the verification.
  8. Update the active device
  9. Perform the below steps to install the new ISO:
    1. On the Main tab, click
      System
      Software Management
      Image List
      .
    2. Select the check box next to the software image to be installed and click
      Install
      .
      Do not perform any configuration changes until the image installation is complete. This screen will continue to refresh to display the install status.
  10. Boot into the new partition:
    1. On the Main tab, click
      System
      Software Management
      Boot Locations
      .
    2. Click on the
      Boot Location
       where the new software image is installed. The General Properties screen appears.
    3. Click
      Activate
       and
      OK
       on the confirmation dialog and wait until the device is fully booted into the new partition.
  11. After the active device successfully boots, verify that the software upgrade was successful by checking the logs (restnoded, restjavad, ltm) for errors.
    Do not click on any tab or link on the SSL Orchestrator menu, submenu, or screen during the verification.
  12. Verify HA is in a good state after both devices are on same ISO version. Use manual steps for the verification. See the following section for manual steps: Verifying the high availability device pair before installing the ISO.
    Do not click on any tab or link on the SSL Orchestrator menu, submenu, or screen during the verification.
    Do not proceed further if HA is not in a good state. You must fix all HA issues before proceeding.
  13. The
    Changes Pending
     warning will appear on top left side of the screen. Click on the message and perform the device sync.
  14. Perform the same steps described above for the second box after the first box installation is complete.
  15. After verifying a successful ISO upgrade, on the Main tab, click
    SSL Orchestrator
    Configuration
    to auto upgrade SSL Orchestrator with the new on-box RPM. If you do not want to upgrade to the on-box package version, use the package management UI to upload the new RPM.
    Once the SSL Orchestrator screen loads, do not click on any tab or link on the SSL Orchestrator menu, submenu, or screen.
    After installing the RPM, it may take some time to re-build the HA.
    Once the RPM is installed on both devices and the HA status is good, the configuration upgrade will begin and will take additional time based on your system speed and setup.
    During the SSL Orchestrator RPM upgrade, the following messages may appear providing insight on the upgrade or issues that may need to be resolved:
    Message
    Explanation
    Loading SSL Orchestrator Configuration. Any configuration changes are not allowed until the configuration is fully loaded.
    This message appears when the UI is loaded but the HA verification did not yet start. This message may not appear on fast system.
    Validating SSL Orchestrator Setup. Any configuration changes are not allowed until the validation in progress.
    This message appears when the system is attempting to verify the state of the device (for example, if the device is either HA or standalone or what is the health of HA state).
    The SSL Orchestrator configuration cannot upgrade due to an invalid BIG-IP HA setup. Wait 2 minutes for self-recovery. If HA remains invalid, select HA-Status for more details and correct the issues. Configuration changes are not allowed until all HA issues are resolved.
    This message appears on a HA device (this will not appear for a standalone device) when the HA setup is not valid. This event is common during the RPM upgrade process because the new RPM installation involves restarting the restnoded and and the HA status will become invalid for a short period of time. Most often, when the restnoded restart finishes, the HA status returns to a good state. However, even after restnoded restarts and is up and running, this message may appear because the system cannot recover by itself. For more details about this message, click on the HA Status icon from the SSL Orchestrator configuration screen.
    Upgrading SSL Orchestrator configuration(s). Configuration changes are not allowed until the upgrade process is complete.
    This message appears on the HA device which is triggering the upgrade and starts the deployment and means that the HA verification has passed (both devices are in a good state and the configuration upgrade has begun).
    The upgrade process is now complete.
    This message appears once the upgrade process has completed.
    The upgrade process is running on a peer device <<MANAGEMENT_IP>>. Configuration changes are not allowed until the upgrade process is complete.
    This message appears on a HA device that is not initiating the configuration upgrade. The configuration upgrade is triggered only on one device. In this case, the MANAGEMENT_IP is the management IP of the device in which the configuration upgrade is triggered.
    The upgrade process cannot determine the device configuration. Configuration changes are not allowed until the upgrade process is complete.
    This message appears when the system is not able to determine the HA status. This may be caused by a coding exception or a framework issue (for example, when a call to a rest URL is failing).
  16. On the Main tab, click
    iApps
    Application Services
    Applications LX
    and validate that the system is still deploying a configuration. If system is deploying a configuration, wait on this screen until all deployments are complete.
  17. In case of an error, perform the following troubleshooting step:
    1. Correct the configuration and trigger the upgrade again by clicking on the blinking red icon at the top right side of the UI.
  18. After the upgrade is successful and there are no configurations in error state, initiate a configuration sync. Click
    Sync
    .
    You have now completed your upgrade.
  19. After a successful upgrade, if you want to install a different version of the SSL Orchestrator RPM, perform the following steps:
    1. On the Main tab of an active box, click
      SSL Orchestrator
      Configuration
      and click on the
      Upgrade SSL Orchestrator
       link.
    2. Select a new RPM and click
      Upload and install
      .
    3. Wait until the installation completes and the screen is refreshed.
    4. Repeat the same steps above for the second box.
      Before continuing with any further configurations, log in to the standby device and validate that the standby device also upgraded to the new RPM version.

Upgrade BIG-IP ISO to a major or point release version with SSL Orchestrator and Access Policy Manager (APM) in high availability

Perform the following task to upgrade your BIG-IP ISO to a major, or point, release version with SSL Orchestrator and APM in high availability (HA). Make sure you review all Assumptions and dependencies and verify all Prerequisites prior to starting the upgrade.

Upgrading BIG-IP ISO to a major or point release version with SSL Orchestrator and Access Policy Manager (APM) in high availability

Before upgrading the BIG-IP ISO to a major or point release version with SSL Orchestrator and APM in high availability, review the assumptions and dependencies above and verify all prerequisites before starting the upgrade.
  1. If your HA device pair are not in sync, perform a manual configuration sync and take a UCS backup on to both devices.
  2. Download the target ISO from https://downloads.f5.com/esd/product.jsp?sw=BIG-IP&pro=big-ip_v17.x and select 17.0.0 from the list to see all the available downloads for the
    17.0.0
     version of BIG-IP.
  3. To upload the new ISO on both devices, perform the following steps (this process can be initiated on both devices in parallel and in any sequence):
    1. Using the management IP, on the Main tab, click
      System
      Software Management
      Image List
      and click
      Import
      .
    2. Click
      Choose File
       and select the newly downloaded ISO.
    3. Click
      Import
      .
  4. Updating the standby device
  5. Perform the below steps to install the new ISO:
    1. From the Main tab, click
      System
      Software Management
      Image List
      .
    2. Select the check box next to the software image to be installed and click
      Install
      .
    Do not perform any configuration changes until the image installation is complete. This screen will continue to refresh to display the install status.
  6. After the image installation successfully completes, perform the following steps to boot into the new partition:
    1. On the Main tab, click
      System
      Software Management
      Boot Locations
      .
    2. Click on the
      Boot Location
       where the new software image is installed. The General Properties screen appears.
    3. Click
      Activate
       and
      OK
       on the confirmation dialog and wait until the device is fully booted into the new partition.
  7. After the standby device successfully boots, verify that the software upgrade was successful by checking the logs (restnoded, restjavad, ltm) for errors.
    Do not click on any part of the SSL Orchestrator menu or submenu in the UI.
Flushing out the old APM session
The following steps are a part of the available content at the following location: https://support.f5.com/csp/article/K25872674.
  1. After the standby device has been upgraded and booted into the new volume, select
    Force Offline
     on the [active] device to trigger a failover to this newly upgraded device:
    Device Management
    Devices
    <Device_Name(self)> Force Offline
    . The newly upgraded device will take over as the active device.
  2. Once the upgraded device takes over as active, you must restart the upgraded device again:
    System
    Configuration
    Device
    General
    Reboot
    .
    This extra step or additional restart is required to flush out any of the old sessions which may have been introduced from the previously active device while on the older version of the software.
  3. Wait for the upgraded device to come back up.
  4. Once the upgraded device becomes the active device, you are now ready to update the second device.
Updating the second device by installing the new ISO
Perform the following steps to install the new ISO on the second device:
  1. From the Main tab, click
    System
    Software Management
    Image List
    .
  2. Select the check box next to the software image to be installed and click
    Install
    .
    Do not perform any configuration changes until the image installation is complete. This screen will continue to refresh to display the install status.
  3. Boot into the new partition:
    1. On the Main tab, click
      System
      Software Management
      Boot Locations
      .
    2. Select the
      Boot Location
       the new software image is installed (this will appear on the General Properties screen).
    3. Click
      Activate
       and
      OK
       and wait until the device fully boots into the new partition.
  4. After the device successfully boots and comes back up, bring it back online by selecting
    Release Offline: Device Management
    Devices
    <Device_Name(self)> Release Offline
    . This device should be standby.
  5. Verify the software successfully upgrades on the device and review the logs for errors.
    Do not click on any tab or link on the SSL Orchestrator menu, submenu, or screen.
  6. Verify HA is in a good state after both devices are on same ISO version. Use manual steps for the verification. See the following section for manual steps:
    Verifying the high availability device pair before installing the ISO
    .
    Do not click on any tab or link on the SSL Orchestrator menu, submenu, or screen.
    Do not proceed further if HA is not in a good state. You must fix all HA issues before proceeding.
  7. The
    Changes Pending
     warning will appear on the top left side of the screen. Click on the message and perform the device sync.
  8. This step must be performed separately on both boxes
     After verifying HA, on the Main tab, click
    SSL Orchestrator
    Configuration
    to auto upgrade SSL Orchestrator with the new on-box RPM. If you do not want to upgrade to the on-box package version, use the package management UI to upload the new RPM.
    Once the SSL Orchestrator screen loads, do not click on any tab or link on the SSL Orchestrator menu, submenu, or screen.
    After installing the RPM, it may take some time to re-build the HA.
    Once the RPM is installed on both devices and the HA status is good, the configuration upgrade will begin and will take additional time based on system speed and setup.

Diagnosing and fixing a high availability deployment

Use the following methods to help diagnose, verify, and fix a failed high availability (HA) deployment:
  • Perform alternate upgrade if standard upgrade fails
  • Verify your deployment and view the logs.
  • Verify the RPM file version on both devices.
  • Configure your deployment settings and redeploy.
  • Review the error logs and perform any necessary recovery steps.

Performing alternate upgrade if standard upgrade fails

Install new ISO on both devices.
Perform the following tasks if your standard upgrade fails:
  1. Boot into new partition on both the active first device and the standby second device.
  2. Click the
    Changes Pending
     warning that appears on the top left side of the screen where the
    In Sync
     message was for both the devices.
  3. Navigate to
    Device Management
    Overview
    and click
    Sync
    .
  4. Wait for the
    In Sync
     message to appear in the top left side of the screen. Press
    Sync
     again if the message does not appear.
  5. When the
    In Sync
     message appears on both the devices, verify that the App LX blocks match in
    iApps
    Application Services
    Applications LX
    . Upload the RPM file by following either step 6 or step 7.
  6. Upload the RPM file using
    iApps
    Import
    .
    1. Upload the required RPM using
      iApps
      Package Management LX
      Import
      for the active device.
    2. Once the upload completes, upload the required RPM using
      iApps
      Package Management LX
      Import
      for the standby device.
    3. Once the upload completes, click
      SSL Orchestrator
      Configuration
      on both devices.
      Do not click Sync yet!
    Clicking
    Sync
     too soon could put the HA pair of devices into an unrecoverable error state.
  7. Or use the Onboard (default) RPM.
    1. If the Application LX blocks match for both devices, click
      SSL Orchestrator
      Configuration
      on the active device.
    2. The top panel displays a
      Invalid BIG-IP HA Setup...
       message on a red horizontal bar.
    3. Click
      SSL Orchestrator
      Configuration
      on the standby device. This loads the onboard (default) RPM for the standby box and closes the
      Software Version Mismatch
       message on the active box.
    4. The black vertical upgrade arrow on the upper-right flashes red.
      Do not press it!
    Clicking the red arrow could put the HA pair of devices into an unrecoverable error state.
  8. Wait until the
    CMI sync has not been triggered after deploying configuration. Please initiate CMI sync
     message appears on the active device. Navigate to
    Device Management
    Overview
    and click
    Sync
    .
  9. Wait for the
    In Sync
     message to appear in the top left side of the screen. Press
    Sync
     again if the message does not appear for both devices.
  10. When both devices reach an
    In Sync
     state, click
    SSL Orchestrator
    Configuration
    on both devices.
  11. Verify that their topologies display and various IR's, services, service chains, security policies, and SSL configurations match.
Upgrade should be complete.

Verifying deployment and viewing logs

You can verify your deployment by verifying that the required virtuals, profiles, and BIG-IP LTM and network objects have been created, checking that the RPM files are in sync, and reviewing logs for failures, for example.
Because the initial device in the HA device group repeats the configuration requests and propagates the configuration to other BIG-IP devices, make sure you verify the initial configured device first, followed by each device in the HA device group. If the initial device deployment configuration fails, all other device configuration deployments will not successfully be configured.
  1. Verify that all expected and required virtuals, profiles, and BIG-IP LTM and network objects (route-domains, VLANs, self IPs) have been created on each device in the HA device group.
    These will be items beginning with the name given to the application (for example, if the application was named SSLO, verify that all of the items named | Summary SSL Orchestrator 15.1.0 | 9 SSLO_* are the same on all devices).
  2. Ensure that all RPM file versions are identical.
  3. Verify your deployment with, or without, services.
  4. Review the following logs for failures:
    • /var/log/restnoded/restnoded.log
    • /var/log/restjavad.0.log

Verifying the RPM file version on both devices

After a successful F5® SSL Orchestrator™ HA deployment, verify that the latest version of the SSL Orchestrator zip file is installed on both devices.
The following details are for SSL Orchestrator versions 14.1.x-5.x or higher.
  1. On the Main tab, click
    SSL Orchestrator
    Configuration
    .
    The SSL Orchestrator screen opens.
  2. For both devices, validate the SSL Orchestrator RPM Version number showing in the top right banner. You can also hover your mouse over the information icon for more detailed version information.
If the versions are not identical, you must install an updated RPM file and verify that both devices are identically configured.

Configuring deployment settings and redeploying

If your configured deployment continues to fail, you can remove and reconfigure all deployment settings.
  1. Remove all configurations present on all devices.
  2. For all devices, individually configure each section in the F5® SSL Orchestrator™ deployment settings and select
    Finished
    . Verify that all new objects are properly synced and deployed.
    If synchronization or deployment issues persist after deploying after each section, attempt to deploy after updating each item (instead of after each section) in the SSL Orchestrator deployment settings and verify that all new objects are properly synced and deployed.

Reviewing error logs and performing recovery steps

You can review log messages to help you debug system activity and perform recovery steps. Refer to the
Setting up F5 Guided Configuration for SSL Orchestration logs settings
 section of this document for more information on generating logs and setting the level of logging you want the system to perform.
  1. Verify that all BIG-IP® LTM® and network objects are present on each of the devices in the HA device group.
  2. If the configuration deployment fails on each device, review the logs:
    • /var/log/restnoded/restnoded.log
    • /var/log/restjavad.0.log
  3. Use the following REST GET command to determine the state of the deployed device block in the REST storage:
    • curl -s -k -u admin:admin
       https://localhost/mgmt/shared/iapp/blocks
      | json-format
  4. Since failure scenarios can vary, after reviewing the logs, attempt the following recovery steps:
    1. Redeploy SSL Orchestrator.
      If this succeeds, you have recovered from the failure situation.
    2. Undeploy SSL Orchestrator.
      By undeploying, a cleanup of MCP objects on each of the devices occurs while also cleaning up required data properties within the block stored in REST storage. If this succeeds, attempt to redeploy again.
    3. If redeploy or undeploy fails, do the following:
      1. From command line (back door),
        run > touch /var/config/rest/iapps/enable
        .
      2. Refresh the SSL Orchestrator menu UI.
      3. Select the deployed application from the list and delete the application.
      4. Redeploy and undeploy again.
      5. Once done, remove the file
        rm -f /var/config/rest/iapps/enable
        .
    4. If these recovery steps do not work, you may need to clean up the REST storage.
For more detailed information on setting up HA, see the
BIG-IP Device Service Clustering: Administration
 document.
Contact Support Contact Support

Have a Question?

Support and Sales >

About F5

Education

F5 Sites

Support Tasks




©2023 F5, Inc. All rights reserved.


Trademarks Policies Privacy California Privacy Do Not Sell My Personal Information