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.

During the burn-in period of OCA deployment, multiple checks are run on the appliance. You will receive periodic emails with the results of the checks, which run approximately every 24 hours until all checks pass.

The current state of the deployment and turn-up checks is displayed in the Partner Portal on the Overview page for each OCA that is under deployment.

turn-up-checks.jpg

The appliance will not start serving client traffic until all checks pass and acceptable offload can be achieved. When the system is ready, the Netflix Open Connect Operations team will automatically enable the system to serve clients and will continue to monitor its performance.

This article provides detailed information about each check:

Network Interface and PSU Checks

Several checks verify that the network interfaces and power supply units (PSUs) that were included with the OCA were properly installed, are functional, and are not flapping or reporting errors. For general instructions and troubleshooting information for network interface errors, see the following related articles:

Network Configuration

This check verifies that the expected number of network interfaces are present and that light levels are adequate.

Troubleshooting Notes:

  • OCAs are shipped to you with the expected number of supported optics connectors and cables. You should only use the parts that were included in the shipment, and ensure that you install and cable all included optics.
  • Only single-mode or multi-mode fiber connections are supported. Direct Attach cabling (also known as DAC, TwinAx, CR, Cu, or copper) is incompatible.

  • If you have replaced the optical modules due to incorrect part types being requested or delivered, please open a ticket to request that new optics be shipped to you.

  • Follow the general instructions and troubleshooting information above as needed.

Network Errors

This check verifies that there are no input errors on the network interfaces.

Troubleshooting Notes:

Network Flaps

This check verifies that the network interfaces are not flapping.

Troubleshooting Notes:

Power Supplies

This check verifies that the installed power supply(s) (PSUs) that were included with the OCA are functioning and reporting their status appropriately to our monitoring systems. 

Troubleshooting Notes:


Connectivity and Reachability Checks

The following series of checks verify that the OCA has the required connectivity to serve Netflix traffic, communicate with our control plane services in AWS, and can be successfully reached for monitoring and administrative tasks. When you are troubleshooting connectivity issues:

  • Ensure that all required ports are open as described in the Network configuration section of the Deployment Guide.
  • Ensure there are no firewalls, proxies, anti-DDoS protection, or third party caching infrastructure installed that may be interfering with connectivity.

  • For additional troubleshooting information, see Viewing connectivity metrics for an OCA

HTTP Connectivity

This check verifies basic HTTP connectivity by making a request and verifying that the expected response code is returned. This connectivity is required to communicate with our control plane services and to serve Netflix traffic.

Troubleshooting Notes:

  • Follow the general connectivity troubleshooting information above.

Basic Reachability

This check verifies that the OCA responds to pings from outside your network.

Troubleshooting Notes:

SSH Manageability

This check verifies that the OCA is reachable via SSH from our AWS instances. This connectivity is required for monitoring and administrative tasks.

Troubleshooting Notes:

  • Follow the general connectivity troubleshooting information above.

IPMI Configuration

This check verifies that the OCA is able to communicate with the Netflix endpoint that performs IPMI bundle updates.

Troubleshooting Notes:

  • Verify that there are no firewalls, filters or ACLs which are preventing access to https://hw-oca.oc.netflix.com.

  • Follow the general connectivity troubleshooting information above.

NTP Synchronization

This check verifies that the OCA is able to properly synchronize its clock using Network Time Protocol (NTP).

Troubleshooting Notes:

  • Ensure that UDP port 123 (and all other required ports as described above) is open.
  • Follow the general connectivity troubleshooting information above.

Fill Checks

The following checks verify that the OCA is able to download content updates (nightly fill) at the required speed. For general information and requirements for fill traffic, see the following articles:

Fill Performance

This check verifies that the OCA is successfully able to request and download a sufficient percentage of required content updates during the fill window.

Troubleshooting Notes:

  • Ensure that there are no errors on your network interfaces, or heavy congestion between the site and Netflix fill sites on the internet during the fill window.

  • Consult the general fill information above as needed.

Fill Speed

This check verifies that the OCA is able to download content updates at the required speed.

Troubleshooting Notes:

  • Ensure that there are no errors on your network interfaces, or heavy congestion between the site and Netflix fill sites on the internet during the fill window.

  • Consult the general fill information above as needed.

BGP and Traffic Checks

The following checks validate that the OCA has an established BGP session and is learning and reporting routes. BGP must be configured properly so that the OCA can serve Netflix traffic to client devices within your network. For general information about BGP configurations and advertisements, see the following information:

BGP IPv4/IPv6, Unexpected BGP Connection Attempts

These checks validate that IPv4 / IPv6 BGP sessions between the OCA and its BGP peer are properly configured and established, and verifies that the OCA is learning advertised routes via its BGP session(s). A failing check for Unexpected BGP Connection Attempts indicates that the OCA is receiving BGP connection requests from outside of your ASN.

Troubleshooting Notes:

  • OCAs are configured before they are shipped, based on the network and BGP configurations that you specified in the Site Survey form. Ensure that the configuration is expected and correct after installation.
  • After the OCA begins reporting data to our control plane, you can view network and BGP configurations in the Open Connect Partner Portal.
  • You can view the routes that are being heard by each OCA and look for route inconsistencies within a site using the Route Explorer tool.
  • If you need to make changes to the network configuration or BGP session configuration for an OCA after delivery and installation, follow these steps.

Inconsistent BGP Advertisements

This check verifies that all OCAs within the site are learning the same number of routes. All OCAs in the same site must serve the same customers and receive identical BGP prefix advertisements.

Troubleshooting Notes:

  • You can view the routes that are being heard by each OCA and look for route inconsistencies within a site using the Route Explorer tool.

Traffic Levels

During the end of the burn-in cycle, the OCA will start to serve live test traffic when it is able to do so. This check verifies that test traffic is being served at the levels that were predicted during the site design process with your Partner Engagement Manager (PEM).

Troubleshooting Notes:

  • Ensure that you are advertising via BGP to the OCA all of the routes that you plan to serve from the site.
  • You can view the routes that are being heard by each OCA and look for route inconsistencies within a site using the Route Explorer tool.
  • If traffic patterns have changed since you discussed them with your PEM and you feel that the traffic levels reported in this check are expected, open a ticket to get help with this issue.

Incomplete OCA Return Form (if applicable)

If this OCA is a replacement for a failed OCA via our RMA return process and we are requesting that you return the failed OCA, this check will run. In most cases, we ask you to E-Waste the failed OCA, but in some cases we ask that you return the failed OCA to Netflix for analysis and repair. This check verifies that the required OCA Return Form has been completed in our Partner Forms application.

Notes:

 

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