Cloud Load Balancers ORD region migration FAQ

This article provides answers to frequently asked questions about the
Cloud Load Balancers migration in the ORD region.

{{< accordion title="Why is there a migration?" col="in" href="accordion1" >}}

We are migrating Cloud Load Balancers onto newer hardware to provide you
with an enhanced experience. Specifically, you will benefit in the
following ways:

• An improved Cloud Load Balancer provisioning experience
• Enhancements to mitigate resource oversubscription
• Architectural improvements that allow for better fault tolerance
  {{< /accordion >}}
  {{< accordion title="How will the migration work?" col="in" href="accordion2" >}}

The migration is simple. During your planned migration window we will
perform the following tasks:

1. Set your load balancer into a PENDING_UPDATE status
2. Duplicate the load balancer configuration onto the new hardware
3. Pass traffic to the load balancer

After those steps are we will set your load balancer status back to
ACTIVE.
{{< /accordion >}}
{{< accordion title="What is the expected impact to my load balancer?" col="in" href="accordion3" >}}

You can expect up to 15 seconds of downtime per migrated load balancer,
although 1 to 2 seconds of downtime is more realistic. Downtime for this
maintenance specifically means that all connections are dropped and
session persistence, if enabled, is reset until the migration is
completed. You might also see up to 1 minute of degradation (for
example, sporadic timeouts or some dropped connections).
{{< /accordion >}}
{{< accordion title="What options are available to avoid disruption due to the migration?" col="in" href="accordion4" >}}

The following options are available:

• Temporarily create a load balancer in another region and leverage
  the public endpoints of your cloud servers.

  Note: This is not
  recommended for SSL terminated load balancers.

• Move the load balancer and applicable nodes to a different region.

• Temporarily leverage DNS load balancing to your cloud servers.

{{< /accordion >}}
{{< accordion title="Do I need to make any update to my configurations?" col="in" href="accordion5" >}}

If you have a firewall between your Cloud load balancer and other
devices you may be required to update your policy settings due to the
fact that the ServiceNet IP address will change. Follow the instructions
outlined in the article, Using Cloud Load Balancers with RackConnect,
to set up the appropriate policies so that you are not affected by the
ServiceNet IP changes.
{{< /accordion >}}
{{< accordion title="Can I self-migrate my load balancer?" col="in" href="accordion6" >}}

We do not recommend self-migrating your load balancer because you will
lose the static IP address that is currently assigned to your instance.
We have planned the migration to ensure a smooth transition of your
existing IP addresses.