Manual Chapter : Setting up F5 Guided Configuration for SSL Orchestrator

Applies To:

Show Versions Show Versions

F5 SSL Orchestrator

  • 17.0.0
Manual Chapter

Setting up F5 Guided Configuration for SSL Orchestrator

Overview: Setting up F5 Guided Configuration for SSL Orchestrator

If you do not have an existing SSL Orchestrator add-on license, or a previous version of SSL Orchestrator installed, then to install the F5 Guided Configuration for SSL Orchestrator 17.0.0-10.0 download the image from downloads.f5.com. For complete step-by-step installation instructions, see the
BIG-IP Systems: Upgrading Software
guide. The F5 Guided Configuration for SSL Orchestrator 10.0 image is packaged with the F5 BIG-IP 17.0.0 image.
The minimum ISO version required to support SSL Orchestrator 10.0 is BIG-IP 17.0.0.
Refer to the Update or Upgrade the F5 SSL Orchestrator chapter in the
BIG-IP update and upgrade
guide, if you have an existing add-on license or want to upgrade to the newest version of SSL Orchestrator. These procedures walk you through the detailed installation and upgrade details of existing SSL Orchestrator applications and RPMs before installing the new ISO image.
If you are upgrading from SSL Orchestrator version 13.x.x or 14.0.x (known as the forklift upgrade), you must follow the recommended upgrade procedure to undeploy your previous SSL Orchestrator deployments. This procedure includes uninstalling your previous version of the application. If these steps are not followed, further manual steps are required to reset your environment and undeploy the previous version found in the
F5 Guided Configuration for SSL Orchestrator: Upgrade Recovery
guide.
These upgrade steps are required since in some cases previously deployed SSL Orchestrator configurations cannot be rolled forward or imported into the new version of SSL Orchestrator. Following one of the recommended upgrade procedures will assist you in preparing your system for a clean installation.
If you are implementing a high availability environment for SSL Orchestrator, refer to the Update or Upgrade the F5 SSL Orchestrator chapter in the
BIG-IP update and upgrade
guide for more detailed information.
After upgrading SSL Orchestrator from version 5.x, 6.x, or 7.x, one or more existing configurations may show an error due to inconsistent egress information. For example, if the System Setting in version 7.0 had an egress setting of IPv4 while the topology setting was IPv6, the IPv6 topology’s egress setting will show an error after the upgrade. To fix, locate the error(s) and update the configuration with the correct egress information (such as egress gateway pool or SNAT settings) and redeploy.
Refer to the F5 SSL Orchestrator Deployment guide for details on managing and creating topologies and services.

Setting up F5 Guided Configuration for SSL Orchestrator logs settings

The SSL Orchestrator Settings option in the Logs menu can be used to enable logging for selected facilities at various levels of severity to describe the system messages. Facilities describe the specific element of the system generating the message: Per-Request Policy, FTP, IMAP, POP3, SMTPS, SSL Orchestrator Generic.
Each available level describes the severity of the message and are listed in order of the severity of the messages they handle. Generally, higher levels contain all the messages for lower levels. For example, the Alert level will generally also report all messages from the Emergency level, and the Debug level will generally also report all messages for all levels.

Setting up logs settings

Use the following procedure to set up your SSL Orchestrator logs settings with specific severity levels.
  1. On the Main tab, click
    SSL Orchestrator
    Logs
    Settings
    . The Logs Settings screen opens.
  2. If the
    Enable
    check box is not pre-selected, select the check box to see the available levels for each facility. The default severity is Debug.
  3. For each facility, you can select from the following log setting severities:
    • Emergency
      : Specifies the emergency system panic messages.
    • Alert
      : Serious errors that require administrator intervention.
    • Critical
      : Critical errors, including hardware and filesystem failures.
    • Error
      : Non-critical, but possibly very important, error messages.
    • Warning
      : Warning messages that should at least be logged for review.
    • Notice
      : Messages that contain useful information but may be ignored.
    • Information
      : Messages that contain useful information but may be ignored.
    • Debug
      : Messages that are only necessary for troubleshooting.
  4. Click
    Save
    .