Welcome to the Netflix Partner Help Center. Have a question or need help with an issue? Send us a ticket and we'll help you to a resolution.


Upgrading older OCAs in a site, through an RMA or similar process, can provide enhanced reliability and efficiency - often resulting in reduced requirements for power, ports, and rack space. However, when replacing some or all of the OCAs in a site, it is important to understand best practices and plan out the physical upgrade process to ensure minimal negative impact to the traffic offload that the OCAs in a site provide.

The following flow chart describes the general decision process and deployment steps involved when you are replacing the OCAs in a site. Additional detail is provided below the chart.



First, consider the overall space and power resources in the site:

  • Do you have sufficient space and power at the site to bring all of the new OCAs online, while keeping the old OCAs online and serving customer traffic?

1 - If YES - you do have sufficient space and power at the site to keep all OCAs (both old and new) online at the same time:

  1. Install all of the new OCAs.

    See this article for more details.

  2. Wait for all of the new OCAs to complete their burn-in process (typically, a 2-day process) and begin to serve live traffic.

    For more information on the burn-in process and how to monitor it in the Partner Portal, see this article.

  3. If we have requested that you e-waste the old OCA(s), ensure that they are properly decommissioned first. For more information, see: Decommissioning an end-of-life OCA
  4. After the decommission process completes, take the OCA(s) offline and e-waste them.

Your process is complete.

If NO - you do not have sufficient space and power at the site to keep both old and new OCAs online at the same time, consider your backup / failover resources:

  • Do you have sufficient spare capacity in one or more backup / failover site(s) to serve the traffic that is currently being served by the set of old OCAs that you are replacing?

2 - If YES - you do have sufficient spare capacity in one or more backup / failover site(s):

  1. Ensure that you have advertised the same set of BGP prefixes to the the failover / backup site(s) that are advertised to the OCAs in the site where you are performing the replacement.

    This step ensures that customer traffic has a graceful failover path as the old OCAs are being taken out of service.

  2. One at a time, decommission each old OCA, power down and uninstall it, then replace it with a new OCA.
  3. Wait for the new OCA to complete its burn-in process and begin to serve live traffic.
  4. Repeat steps 2-3 for each old OCA that you are replacing.
  5. E-waste the old OCA(s).

Your process is complete.

3 - If NO - you do not have sufficient capacity in a backup / failover site:


  • This case is similar to case 2. However, the lack of backup / failover traffic sources will require you to more carefully and gradually perform steps 2-5 above, pausing after each replacement and monitoring any undesirable traffic shifts to sources outside your network and/or offload degradation.


If you have any questions about this process, please open a ticket.


Was this article helpful?
0 out of 0 found this helpful