Skip to content

Create an F5 BIG-IP LTM machine

Create an F5 BIG-IP Local Traffic Manager (LTM) machine so Certificate Manager - SaaS can discover the certificates in the SSL profiles on your BIG-IP system and provision certificates to it. Certificate Manager - SaaS connects to the BIG-IP iControl REST API through a VSatellite.

Before you begin

  • The System Administrator, PKI Administrator, or Resource Owner role. If you have the Resource Owner role, you must own or belong to at least one team.
  • An active VSatellite that can reach the BIG-IP management interface on port 443, or on the port you set for the machine.
  • The hostname or IP address of the BIG-IP management interface.
  • BIG-IP version 13 or later.
  • A BIG-IP account with administrative permissions. Provisioning a certificate to the device administration page requires the Administrator role.

To create an F5 BIG-IP LTM machine

  1. Sign in to Certificate Manager - SaaS.
  2. Click Installations > Machines.
  3. Click New, and then select F5 BIG-IP LTM.
  4. On the Properties step, in Name, enter a name for the machine.
  5. For Owning Team, choose the team that owns the machine. System Administrators and PKI Administrators can choose any team. Resource Owners can choose only a team they own or belong to.
  6. For VSatellite, choose a VSatellite that can reach the machine. A VSatellite that's the primary of a high availability group shows its number of active replicas, and Certificate Manager - SaaS can run the machine's operations on any healthy VSatellite in the group.

  7. In F5 BIG-IP LTM Address/Hostname, enter the hostname or IP address of the BIG-IP management interface.

  8. (Optional) In Port, enter the port of the management interface if it isn't 443. If you leave it empty, Certificate Manager - SaaS uses 443.
  9. For Credential Type, choose how to provide the credentials:

    • Enter Credentials to enter the credentials in the next step. This is the default.
    • Select Credentials to use shared credentials from a credential manager integration. Then, for Credential, choose the credential.

    Note

    Select Credentials requires the credential manager capability, which requires additional licensing. Without it, Credential shows No credentials are available. System Administrators and PKI Administrators can choose any credential. Resource Owners can choose only the credentials that belong to their teams.

  10. If you chose Enter Credentials, enter the Username and Password of the BIG-IP account. If you chose Select Credentials, the stored account needs the same BIG-IP access.

    Note

    Certificate Manager - SaaS encrypts the credentials you enter and doesn't display them again. On the machine's Properties tab, they appear masked. To keep a stored credential when you edit the machine, leave its masked value unchanged. Keep your own secure record of the credentials in case you need them again.

  11. Click Test Access. After the connection succeeds, click Continue. The Discovery step opens.

    Note

    A successful test confirms that Certificate Manager - SaaS can sign in to the iControl REST API and that the BIG-IP version is 13 or later. It doesn't check the account's permissions. Certificate Manager - SaaS doesn't verify the BIG-IP server certificate, but the connection is still encrypted.

  12. (Optional) For Resource Types to Discover, choose which certificates to discover. If you don't choose a type, discovery finds both.

    • Both Monitors and Virtual Servers
    • Monitors: certificates in the server SSL profiles that HTTPS monitors use.
    • Virtual Servers: certificates in the client SSL profiles that virtual servers use.
  13. (Optional) In Partition(s), enter a comma-separated list of the partitions to discover. The default is Common. If you leave the field empty, discovery searches every partition.

    Important

    Discovery filters on the partition of each SSL profile, but the installation it records uses the partition of the profile's certificate. When you provision to that installation later, Certificate Manager - SaaS looks for the certificate, its private key, and the SSL profile in that one partition. Keep each SSL profile in the same partition as its certificate.

  14. (Optional) To skip certificates that have already expired, enable Exclude expired certificates.

  15. (Optional) To skip SSL profiles that no virtual server or monitor uses, enable Exclude certificates that are not in use by either a virtual server or a monitor. Otherwise, discovery also finds the certificates in those unused profiles.

    Note

    If Certificate Manager - SaaS can't read a certificate in a PEM certificate file, for example a CA certificate issued on a Brainpool elliptic curve, discovery skips that certificate and continues. If the website certificate itself can't be read, discovery skips that SSL profile. If a certificate in a DER (binary) certificate file can't be read, discovery stops with an error. Discovery also skips client SSL profiles that have more than one certificate key chain, and it doesn't find the certificate that secures the device administration page.

  16. (Optional) To discover certificates on a schedule, enable Schedule. For Repeat every, choose Day, Week, or Month, and then in At, enter the time. For Week, select the days of the week. For Month, enter the days in Day of month. Times are in Coordinated Universal Time (UTC).

  17. Click Continue. The Provisioning step opens.
  18. (Optional) To provision certificates on a schedule, enable Schedule. For Repeat every, choose Day, Week, or Month, and then in At, enter the time. For Week, select the days of the week. For Month, enter the days in Day of month. Times are in Coordinated Universal Time (UTC).

    Scheduled provisioning pushes only certificates that are queued for deployment, such as renewed certificates, so renewals install during the window you choose.

  19. Click Finish.

What's next?

After you create the machine, provision a certificate to it. You can also run discovery on the machine at any time to track the certificates in your SSL profiles.